I've used linux for a while, but am a newbie when it comes to admin stuff

I have a Redhat 8.0 box that I'd like to setup to boot both Linux 2.4 and 2.6.0, but have not had much luck in adding support for 2.6

I compiled my 2.6 kernel with mostly default settings, adding only debugging support and tried doing a make install. When I did this, the makefile replied that I had no module support for advansys. I looked up .config and found that advansys is a type of SCSI device. The funny thing is that /proc/scsi tells me that I have no scsi devices. (I also happen to know that I have no SCSI devices)

I reran "make xconfig" and unchecked advansys support, looked at the .config to confirm that it was commented out, and did a "make clean && make dep && make && make modules && make modules_install" After that succeeded, I tried a make install

Despite this, it still complained about advansys. I shrugged and manually copied bzImage to /boot and added an entry in my grub configuration, but could not create a new initrd file because mkinitrd also complained about advansys module support being missing.

I tried booting without the initrd file and got

VFS: Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00

I'm not sure how to go from here. Suggestions?

BTW: I'm aware there's a related post from Aug 2003 about this, but it seemed to stop before a solution was mentioned.

"I compiled my 2.6 kernel with mostly default settings, adding only debugging support and tried doing a make install. When I did this, the makefile replied that I had no module support for advansys. I looked up .config and found that advansys is a type of SCSI device. The funny thing is that /proc/scsi tells me that I have no scsi devices. (I also happen to know that I have no SCSI devices)"

Are you using ide-scsi for a CD-RW or CD-R?

"VFS: Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00"

You can either:
create an initrd.

Or make all of the modules that the initrd normally loads resident in the bootable kernel and dispense with initrd. This is what I always do when I compile a kernel.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

"You can either:
create an initrd"

I could not create a new initrd file because mkinitrd complained about advansys module support being missing.

I just noticed after doing a make mrproper and makeconfig that the makefile complains saying
/boot/config-2.4.18-14:2047: trying to assign nonexistent symbol HZ

The thing is, I'm running in the /usr/src/linux-2.6.0 Why would it complain about editing the 2.4 config file?

Also, I don't appear to have a /boot/config-2.6.0 How do I create one?

"The thing is, I'm running in the /usr/src/linux-2.6.0 Why would it complain about editing the 2.4 config file? "

You are probably mixing the 2.6.0 and 2.4 initrd processes somehow but I don't know where the mixup occurs.

"Also, I don't appear to have a /boot/config-2.6.0 How do I create one?"

Copy it from /usr/src/linux

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites