On Mon, Jan 09, 2012 at 02:13:37PM -0700, jasonps...@jegas.com wrote: > I have been reading how Bruce Dubbs had this same problem and how ken > said to compile the Kernel with: > > CONFIG_DEVTMPFS=y and CONFIG_DEVTMPFS_MOUNT=y > > This solved Bruce's problem. I found the closest matches for these > settings in the Kernel Configuration screen and they are on by default. > > Bummer is it was looking so hopeful when the kernel started to boot > until I got hit with the colored [FAILS] > > And as best as I could tell (scrolls up pretty fast) it was device not > existant. > > I'll keep hammering, but any ideas are welcome. > > --Jason > I suggested it to someone, but I'm fairly sure wasn't Bruce! I got it from Andy (probably back in October).
The DEVTMPFS was, for me, a workaround where '/' was mounted but none of the other filesystems (particularly, my separate /home) existed because of non-present device nodes (bad kernel config - I'd left in the legacy CONFIG_SYSFS_DEPRECATED). Without knowing which bootscript failed - can you login, or does it shutdown when you press enter ? It seems you have started userspace (i.e. init runs the bootscripts), so perhaps try init=/bin/bash and then step through the scripts in order (rcS.d first). ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
