> > I have tried to boot an allyesconfig, and to no shock, failed, though it > > built fine. Hardware is a pain. Just thought it was worth one try. > > Well, since you provide no further log messages or such, it's hard to say the > reason why it failed. I suggest to do "make defconfig" and "make > allyesconfig", then compare both .config files. By using grep and diff, I > think slowly you can find out which config item that doesn't work for your > hardware specification.. > > However, is allmodconfig expected to boot normally (assuming proper creation > > of initrd)? I.e., if it doesn't, it's "Bad Thing" and not "Don't Do > > That"...? > > > Sometimes yes sometimes no. I think the problem lies not on which one created > as module or native kernel part, but which one is enabled and which one is > not. Just for example, IIRC there is old IDE emulation that is needed so that > the Linux kernel is bootable inside Qemu but it's no longer enabled by "make > defconfig". There could be more issues like this, but this is the only one I > know. Well I was just hoping it generally was expected to work, because I'm having some problems with hardware right now and I really don't want to do a binary search through the config options and I also don't want my kernel build to take an hour. Oh well. As to why it failed, for some inexplicable reason, it detected my entire IDE subsystem as SCSI and hung while trying to access the root device. It'll take longer to get all the crap weeded out than it will to fiddle my config. Oh well. I guess all*config options are purely for testing and not ever meant to run. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
