walt <w41...@gmail.com> writes: > Yes, it's a trivial fix (everything's trivial if you know how to do it :) > > The /dev directory (before udev starts) is missing the /dev/console > device -- or maybe it's the /dev/null device. Crap, I can't recall > just now but I fixed the problem a week or two ago by using mknod to > create the missing device (I think it was /dev/console). > > Just chroot into your fresh vm and see what's missing from the /dev > directory. Use mknod to create the missing device.
/dev/console and /dev/null are there. Not sure how to tell what is missing if anything... comparing to my running desktop there are herds of devs missing.... But now that I tried booting, I think I'm missing some kind of driver from the kernel build... boot is not able to find my root on sda3. And has a kernel panic. I remember having a heck of a time about scuzy drivers last time too. A couple years ago I didn't think to get the right wording before rebooting into SystemRescueCD and am now chrooted into the vm again. I cannot remember what scsi kernel items to set. I don't think it buslogic .. I did go back and rebuild that into the kernel... but still no go. and still not sure about devs missing either. When building the kernel: I took the config.gz off the minimal install iso as a template for my kernel build. Then turned off some of the more obvious unnecessary gunk. I either turned off something that needs to be on, or just missing a module that I'm not finding. Since the hdd is registering as sda rather than hda... I think that may be what needs something scsi related to be built into the kernel or as module.
