Trying to boot a machine with an aic7xxx controller card. If I'm using genkernel everything is working as expected and the machine boots. But HIGHMEM is not default, so I enable HIGHMEM and HIGHMEM IO support with genkernel --config. Everything else is left as default. But when I reboot I get a kernel panic (unable to find sda3). It seems like the initrd is never loaded, even though it is built and specified in grub (genkernel without --config works!). What's the difference here? I've tried both 2.4.20-gentoo-r7 and 2.4.22 vanilla-sources. Both experience the same problem. Reproducible: Always Steps to Reproduce: 1. genkernel --config 2. Reboot 3. Actual Results: Kernel panic. Unable to mount root fs on sda3. For some reason it didn't execute the initrd. Expected Results: Booted the initrd and run /linuxrc in it.
After the genkernel build, is there anything in /var/log/genkernel.log? Please paste the contents.
I'm not sure, since I couldn't boot the machine I had to use a LiveCD. When I booted it up again my main concern was to get the machine running (it's a server). I used genkernel again and just compiled the SCSI modules into the kernel (not as modules). But to my recollection, it said something about sd_mod missing or such. When you use genkernel and genkernel --config, isn't the defaults set to from the same source?
sd_mod is for the scsi disks. When did you get this error, during boot time (linuxrc)? Before or after the initrd runs (I am assuming that it runs when you don't have the SCSI mods modular)? As for genkernel --config, yes, we supply you with a base config, then you can modify that to fit your needs (as you did). I will look into if the initrd is created from genkernel --config. the genkernel.log would be very helpful - please post if you can get your hands on it.
But is the base config the same if you use only genkernel and genkernel --config? I had a feeling they're not from the same base. Am I right? To me, it seemed like to whole initrd never got loaded when I booted, even though grub specifically mentions it. The log is not available, it was overwritten by a newer genkernel build. Sorry.
My hands are tied unless I can see that log - would it be possible to recreate the build that failed? I am closing until we get this log.
