Guillaume Cottenceau wrote:
Alvin Austin <[EMAIL PROTECTED]> writes:The version of 2.2 kernel in cooker contribs is kernel22-2.2.20-9mdk.i586.rpm, so the modules from there is a mismatch between what the install wants (2.2.19) and what's there.
The kernel22 package is not in the current cooker tree, and theYep it's in the contrib.
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 bootYes, yes.
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 ontoNo, the fact is that when the rescue starts, it loads module from
the image/alternative/*2.2.19-BADZ5* disks.
the rescue, not the bootdisks. In the bootdisks, the modules are
correct: you load your network/scsi drivers ok.
Sorry, but I don't understand why booting an install floppy in rescue mode should try to load modules from some other version of the kernel other than what booted with the rescue itself. Common operations like mounting a vfat or ext3 partition fail because those modules can't load because of version mismatch problems. The shell mode prompt even tells the user to type modprobe <module> to load additional modules??? (sorry if I'm missing something that should be obvious here).
You are correct that the scsi and network drivers get loaded properly, though.
Alvin
