Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Could be a BIOS bug (as stated in the output), but that would also have happened with the host linux you used to build LFS. So I doubt that that is the problem.
Do you actually have ehci? Shouldn't that be uhci.
If that is the case: Recompile your kernel without ehci (and, if not activated, with uhci).
0000:00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
0000:00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
0000:00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
0000:00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller (prog-if 20 [EHCI])
You could decide, for the time being, to remove all USB support. Get your box up and running first with the basics. This kernel could also be used later on as a fall-back kernel (extra boot option in grub/lilo). This has the advantage that you can always boot, even if you mess-up your primary kernel and end up with a kernel panic/hang.
The problem you describe are most of the time kernel related, something you (wrongly) activated or did not activate. Finding out which can be a pain, but working systematically will eventually solve the problem.
Don't know if the following is 'old news', but you can use the lspci (-v) command to get some extra info. You could also take a look at the dmesg output that is created by the host system you used (live cd?) and use that as a base.
Not that much to go on, but I hope it helps anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.