Help - Search - Members - Calendar
Full Version: Mandrake Boot Problem
Linuxhelp > Support > Technical Support
Jim
I am trying to install Mandrake on a budy of mine's computer and I am running into problems during the boot sequence.

At the Finding module dependencies check I get the code

QUOTE
Finding module dependencies: Modprobe: modprobe: insmod scanner failed
modprobe: modprobe: insmod ov511 failed


and than it stops booting. Its not frozen because I can get caps and num lock on and off. Its Mandrake 9.2 I just downloaded the ISO and it said it was up to date in the install. I have already tried deleating the partitions and installing it again. Any help please.
hughesjr
There is a hang issue with the usb detect and mandrake 9.2 on at least Sony Vaio fx503....maybe some others as well. Updating to the latest kernel may fix your problem ... (or preventing the usb scan) ....

First try this ... at the boot lilo screen, hit esc and at the prompt type:

linux nousb

If that works, after you get in, download this file:
ftp://ftp.phys.ttu.edu/pub/mandrake/updat...1-1mdk.i586.rpm

Then goto the download directory and do this:

rpm -Uvh kernel-2.4.22.26mdk-1-1mdk.i586.rpm

reboot and select the 2422-26 kernel to boot from...
------------------------------------------------------------------
If that doesn't work, try this:

It is not easy to get the network cards working or switch out the CDROM with another one (to put the new kernel on the system) when booting with the mandrake cd-1 as a rescue disk ... so I recommend you download the latest SystemRescueCD from here ... currently version 0.2.9. Burn and boot from that CD.

Pick your keyboard/lang ... i use 41 for US.

After you get to the command prompt, make a directory to mount your boot mandrake drive in ... i would use /mnt/mandrake ...

mkdir /mnt/mandrake

Now, you need to know your mandrake / {root} directory and /boot directory (if boot is seperate) so you can mount them.

If you don't know the partition numbers, then you can use fdisk to find out...if you installed mandrake on primary master ide drive, do

fdisk -l /dev/hda

if you installed on primary slave, do:

fdisk -l /dev/hdb

(use /dev/hdc for secondary master, /dev/hdd for secondary slave)...

You output should look something like this for the correct drive ... (if dual boot, there may also be some windows partitions)....
CODE
Disk /dev/hda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1          13      104391   83  Linux
/dev/hda2              14        1580    12586927+  83  Linux
/dev/hda3            1581        1711     1052257+  82  Linux swap

In my case, I have a seperate boot and root partition ... boot is /dev/hda1 and root is /dev/hda2. If you have a small and large linux partition, your small one is probably boot and the large one is probably root.

Now we need to mount the mandrake partition(s) ... root first ... then boot

issue the command:

mount /dev/hda2 /mnt/mandrake

(if your root is not /dev/hda2, substitute the proper path)... now you can see if you need to mount a seperate boot directroy ... issue the command:

ls /mnt/mandrake

The output should similar to this:
CODE
ls /mnt/mandrake
bin   dev  halt  initrd  mnt  proc  sbin  usr
boot  etc  home  lib     opt  root  tmp   var
Then issue the command:

ls /mnt/mandrake/boot

If this output is blank, you need to mount a boot partition ... the output looks similar to this:
CODE
ls /mnt/mandrake/boot
System.map                           initrd.img
System.map-2.4.22-10mdk              kernel.h
System.map-2.4.22-21mdk-i686-up-4GB  kernel.h-2.4.22-10mdk
boot.0307                            kernel.h-2.4.22-21mdk-i686-up-4GB
config                               map
config-2.4.22-10mdk                  message
config-2.4.22-21mdk-i686-up-4GB      message-graphic
diag1.img                            message-text
diag2.img                            us.klt
grub                                 vmlinuz
initrd-2.4.22-10mdk.img              vmlinuz-2.4.22-10mdk
initrd-2.4.22-21mdk-i686-up-4GB.img  vmlinuz-2.4.22-21mdk-i686-up-4GB
then you don't need to mount a seperate boot directory.

If you need to mount a boot (the ls was blank) issue the command:

mount /dev/hda1 /mnt/mandrake/boot

(substitute the correct boot partition if not /dev/hda1) ... (do ls /mnt/mandrake/boot again .. it should now have kernel files in it...)

Now we are ready to chroot (change root) to the mandrake ... issue the command:

chroot /mnt/mandrake /bin/bash

Now do cd /tmp and download the latest kernel:

CODE
wget ftp://ftp.phys.ttu.edu/pub/mandrake/updates/9.2/RPMS/kernel-2.4.22.26mdk-1-1mdk.i586.rpm


exit the chroot and unmount the drives and reboot in single user mode like this:

exit
cd /
umount /mnt/mandrake/boot
umount /mnt/mandrake
reboot


When at the Mandrake selection screen, hit esc and do:

failsafe nousb

then do:

rpm -Uvh /tmp/kernel-2.4.22.26mdk-1-1mdk.i586.rpm

reboot and select 2422-26 kernel
------------------------
after either method, you probably want to edit the file /etc/lilo and make the line that starts with

append=" "

for the image=/boot/vmlinuz-2.4.22-26mdk look like the append="" line for the original kernel (the image=/boot/vmlinuz section)(on my system it looks like this):

append=" devfs=mount acpi=ht"
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2017 Invision Power Services, Inc.