Bruce, Ken and Alan, Thank you for the responses (all 3 of which arrived exactly the same minute). I have solved the problem with your help. Below is what I did.
> Try 'make defconfig' on the system and compare the .config to waht you > have. I have un-tarred kernel on my host system (not in chroot). 'make defconfig' yielded an expected .config file. The only difference between used config were DEFAULT_HOSTNAME, EFI_STUB, UEVENT_HELPER and UEVENT_HELPER_PATH. To be sure it's a kernel issue and not messed up base system I've tried to boot LFS with my Arch Linux kernel. It turned out to be a bad idea, kernel panicked with something mount related. I have looked through lspci and lsmod on my host system and found out that I have Intel USB xHCI HC controller; USB 3.0 support (XHCI HCD mentioned by Ken) is present on my host system but isn't enabled for the LFS kernel. After rebuilding the kernel with CONFIG_USB_XHCI_HCD=m CONFIG_USB_XHCI_PCI=m # CONFIG_USB_XHCI_PLATFORM is not set both the internal and the USB keyboard work \o/ > There is no LOGLEVEL 8. Quote from the book (section 7.6.5), possibly misunderstood by me: > Valid levels are from "1" (no messages) to "8". The default > level is "7". > That's because your kernel config has something set in the Kernel Hacking part of the kernel configuration. I don't recall the exact item. Found that CONFIG_DEBUG_STACK_USAGE (from Kernel hacking --> Memory Debugging --> Stack utilization instrumentation) is indeed the cause of the messages. Thank you once again and have a nice Sunday. --- Andrew -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
