Alvin Austin <[EMAIL PROTECTED]> writes: > >No, the fact is that when the rescue starts, it loads module from > >the rescue, not the bootdisks. In the bootdisks, the modules are > >correct: you load your network/scsi drivers ok. > > > > > 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.
No doubt about that :). > 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). The other modules loaded during install or during rescue do not come from the packaged kernel. The packaged kernel, kernel22-2.2.20-9mdk.i586.rpm, is the kernel to use *after* the installation. During installation or in the rescue, we use modules corresponding to the install/rescue kernel. These modules are packed in the file named Mandrake/mdkinst/lib/modules.cz-2.2.19-BADZ5 on your install media. I think I've already referred to that file 2 messages ago (Message-ID: <[EMAIL PROTECTED]>). > You are correct that the scsi and network drivers get loaded > properly, though. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
