[SLE] kernel rebuid and scsi module problem
Hi, Just for fun I rebuilt 2.2.14 kernel with the source from kernel.org. I originally installed suse 6.4 using the scsi "initio" module. In my kernel rebuild, I built scsi support into the kernel, renamed /lib/modules/2.2.14 to .old and did a new "make modules_install". The problem is, upon rebooting, the built-in kernel scsi support finds the scsi card first, then a few lines later, the system tries to load the "initio scsi module" and the system hangs. My only guess is that the initial modular install created some reference to using the initio module, which I don't understand where it's coming from. The only reference I could find was the top line in /etc/rc.config, which had a line: INITRD_MODULES=INITIO I uncommented it , but it had no effect, the problem persisted. What is going on? Why does the system insist on using the module "initio", even though my kernel rebuild dosn't use it? Thanks -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
SuSE, in 6.3, introduced a booting method that uses a ramdisk. It is extremely convenient, since allows you to boot a generic kernel and then load other modules, such as the scsi driver, needed to complete the boot process. You don't have to mess with a different kernel image for every kind of scsi or ide interfaces. A detailed description is found at: http://sdb.suse.de/sdb/en/html/initrd.html If you insist in building such drivers into the kernel, you may need to change your rc.config and lilo.conf to avoid problems. Since you modified rc.config, you have to run mk_initrd to re-build the initrd file in your /boot directory. After that check lilo.conf and run lilo. As an example here is my lilo.conf # append="vga=0x0301" boot=/dev/hda2 compact vga=ext read-only prompt timeout=100 # image = /boot/kernel initrd=/boot/initrd root = /dev/hda7 label = Linux # image = /boot/vmlinuz root = /dev/hdc1 label = Devel # image = /boot/suse initrd=/boot/initrd.suse root = /dev/hda7 label = SuSE As you can see, you can have an initrd for each kernel image. You may need to edit mk_initrd to change the file names, though. Good luck. -- Rafael Herrera Laboratory for Computational Neuroscience University of Pittsburgh http://www.neuronet.pitt.edu/~raffo -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"Rafael E. Herrera" wrote:
As you can see, you can have an initrd for each kernel image. You may need to edit mk_initrd to change the file names, though.
Good luck.
Thanks, that's the info I needed. I knew there was something different since version 6. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (2)
-
raffo@neuronet.pitt.edu
-
zentara@freewwweb.com