Guillaume Cottenceau wrote:

Alvin Austin <[EMAIL PROTECTED]> writes:

[...]


Things go downhill with the other boot disks. - The
hd-2.2.19-BADZ5 and the network-2.2.19-BADZ5 both let you
 install Mandrake, but don't install the aic7xxx_old driver
 into the initrd.img (the aic7xxx gets installed and then you
 can't boot).

Installing with 2.2.19, it should install the kernel22 package,
doesn't it boot?


- If you try to use the 2.2.19 hd or network images in rescue
 mode (to try and run mkinitrd to add the aic7xxx_old driver),
 many modules don't load properly, because the /modules/modules.cz
 on these images is for the 2.4.* kernels not for 2.2.19.  The
 worst thing is that the loop module cannot be loaded, which
 breaks mkinitrd.  The error message is:

Two solutions:

- start with "linux expert" and load the loop.o module when
 prompted for a SCSI module, before the aic7xxx

       or

- mount the CD, extract the loop.o module with packdrake from
 Mandrake/mdkinst/lib/modules.cz-2.2.19-BADZ5 and load it



The kernel22 package is not in the current cooker tree, and the Mandrake Cooker (91B3) installation program gives an error that it can't be found near the end of the install session.

Also, the module loading problem is more general. When you boot from the hd- or network-2.2.19-BADZ5 disks, *none* of the extra modules (ext3, loop, etc.) get loaded because of this bad version problem... A series of error messages flash by on the screen as these disks boot and the /etc/rc.sysinit script gets executed.

It seems like the wrong version of the modules are packaged onto the image/alternative/*2.2.19-BADZ5* disks.

Alvin



Reply via email to