Having wrestled as a newbie with this problem in the face of a dearth of
information on the subject I thought I would pass on my experience to
others. I was unable to load a win4lin kernel on my dual boot scsi machine
with COL2.4. I would receive kernel panic messages because the scsi modules
(scsi_mod, aic7xxx etc.)would report as mismatched. The solution finally
came when I realized how the scsi mods are loaded into the kernel by initrd.
My system would show the initrd line in grub as follows:
Title=Win4Lin
Root=(hd0,4)
Kernel=/boot/win4lin vga-274 debug=2 root=/dev/sda5
initrd=/boot/initrd-2.2.14.gz
The solution came to me following the reading of an article titled "SCSI
Boot Time" (www.calderasystems.com/SxS/scsboot.htm)which described loading
of the scsi driver with initrd and how to do it with the "mkinitrd" command.
The article cautioned "You may have to put the kernel version after
mkinitrd.sh". You can see above that is the wrong kernel version! The above
should have read as follows:
Title=Win4Lin
Root=(hd0,4)
Kernel=/boot/win4lin vga-274 debug=2 root=/dev/sda5
initrd=/boot/initrd-2.2.14w4l.gz (the name of the win4lin kernel)
Once done, no problems. So if you are ever faced with loading win4lin on a
scsi box and get mismatched modules with a kernel panic, this just might be
the solution.
Mathew Mandeltort
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
http://lists.netraverse.com/mailman/listinfo/win4lin-users
