On 3/12/07, David A. Gershman <[EMAIL PROTECTED]> wrote: > > I've worked through 6.2 and am still unable to boot. In short, the boot > process stops because my hda drive is not found. Further investigation > finds that udev is not populating /dev with hda...hence the inability > for mounting and fscking later in the boot process. > > I've compiled the kernel with ext2 support compiled in, no modules for > extras (no networking, sound, etc). I've modified the "udev" boot > script to pause between commands and poor out verbosity. I even did an > 'ls' of the /dev directory prior to 'udevsettle' (didn't want to harm > the resulting return value). 'hda' was not listed in /dev.
Sounds like you might be missing the driver for your IDE controller. If you have pciutils on a different partition, could you run "/sbin/lspci -v" and attach the output? It might also be a good idea to attach your kernel configuration. > So my question is actually rather basic I think: > > If udev builds the devices on the fly, does there have to be a rule for > every device you want enabled? i.e. in /etc/udev/rules.d does there > have to be a rule for hda? No, udev will happily create hda using the name the kernel gave it with the default root:root 660 permissions. We have a rule that basically sets the group to disk for /dev/hd*, but it's just a preference. It sounds like there is never a uevent generated by the kernel for this device. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
