alias scsi_hostadapter ips
alias scsi_hostadapter1 aic7xxx
alias parport_lowlevel parport_pc
alias eth0 pcnet32
alias eth1 eepro100
alias usb-controller usb-ohci
Originally, scsi_hostadapter pointed to the aix7xxx (which is not used at the moment) but event setting them as above and re-making the initrd file (via "make install" from the top of the kernel source tree) didn't help.
_DHMS
On Friday, Dec 6, 2002, at 18:53 America/New_York, Samuel Flory wrote:
David HM Spector wrote:OK.. I'm stumped. Building working kernels and initial ramdisks under RedHat has always been a bit of a black art. However under RH8 no matter what I do I get a kernel panic (unable to open root fs) when I try to run my custom system.
The kernel I am using is the latest from kernel.org (2.4.20) with the probe all SCSI LUNs turned to support a tape autoloader I want to use on this system and most everything else enabled as a module. I tried to recompile the 2.4.18-18.8.0 kernel sources using RedHat's config file but got zillions of errors ralating to network devices, and God knows what else.
For the 2.4.20 kernel, the make dep;make vmlinux; make modules;make modules_install and then make install all execute without error.
I've tried using rdev to tell the /boot/vmlinuz-2.4.20-custom boot image what disk its on all to no avail (although when I ask it with rdev what its boot disk is I get the correct answer -- sda5 in my case [sda1 is /boot]..)
Has anyone had success building a custom kernel under RH8..?
Your issue is most likely you aren't loading the right driver for your scsi controller. Look in /etc/modules.conf there should a scsi_hostadapter alias. Be sure you either include it built into the kernel or load it in your initrd.
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
