Le 19/03/2012 20:18, Bruce Dubbs wrote: > Pierre Labastie wrote: >> Also, it might be interesting/necessary to copy the content of /lib/firmware >> to $WDIR. > That directory has always been empty for me. What populates it? > I've always thought of that directory to be for specialized video cards. > That's not needed for BLFS to mount the root file system (the sole > purpose of the initramfs). Is there another use? For example, when building the radeon module (the one with CONFIG_FB_RADEON, not the DRM one), it puts a bunch of files in /lib/firmware/radeon. I cannot say for sure that lacking the files was the reason why my screen went black. I completely disabled the radeon module, and could go forward and find the other errors. I haven't tried to enable radeon since then. >> In the init.in script: >> Not needed (automatically created by devtmpfs): >> mknod -m 640 /dev/console c 5 1 >> mknod -m 664 /dev/null c 1 3 > Do you have any idea where that's done? I looked in the source for the > kernel and util-linux, but can't find it. The `device_add' function (in drivers/base/core.c), which seems to be called by a lot of drivers, calls `dev_tmpfs_create_node'. I am not very familiar with the kernel source, though. >> and udev seems to be not needed either (at least for LVM, >> do not know for raid): vgchange -ay automatically >> creates the special files and symlinks in /dev. > If we were mounting a usb drive as the rootfs, I think it would be > needed to populate /dev. I'm not sure though. > All I can tell is that drivers in drivers/usb call `device_add'. How those drivers are instantiated is to complicated for me...
Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
