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.
I have just completed building LFS 7.1. I have also build KDE 4.8 according to BLFS instructions. Now coming to the problem, my usb keyboard is not working neither in console nor in KDE. It works only in grub menu after that when kernel loads it does not response.
Additional information:
1) I am using kernel 3.2.6
2) usbhid, hid, usbcore and EHCI_HCD are build into kernel image.
3) Earlier i was using PS2 keyboard with PS2 mouse they were working without problem but later when i replaced PS2 keyboard with usb keyboard above problem occurred.
4) I am using udev-181
I don't understand what is the problem have searched google hundred times.
I have just completed building LFS 7.1. I have also build KDE 4.8 according to BLFS instructions. Now coming to the problem, my usb keyboard is not working neither in console nor in KDE. It works only in grub menu after that when kernel loads it does not response.
Additional information:
1) I am using kernel 3.2.6
2) usbhid, hid, usbcore and EHCI_HCD are build into kernel image.
3) Earlier i was using PS2 keyboard with PS2 mouse they were working without problem but later when i replaced PS2 keyboard with usb keyboard above problem occurred.
4) I am using udev-181
First thing that comes to mind: Are all those kernel options static or modular? They need to be static. LFS doesn't use initrd, so make sure all that is needed during the boot process is build statically.
First thing that comes to mind: Are all those kernel options static or modular? They need to be static. LFS doesn't use initrd, so make sure all that is needed during the boot process is build statically.
Hi,
I don't understand by static build but usbhid, hid, usbcore and EHCI_HCD are not build as module but are built in compressed vmlinuz kernel image.
I don't understand by static build but usbhid, hid, usbcore and EHCI_HCD are not build as module but are built in compressed vmlinuz kernel image.
Did you use a * or an M to select them:
Code:
Device Drivers --->
[*] HID Devices --->
<*> USB Human Interface Device (full HID) support
[*] USB support --->
{*} Support for Host-side USB
Are the bold blue parts a star (*) as shown in the above example, or an M, like this:
Code:
{M} Support for Host-side USB
* means build statically, the M means modular. I hope you now understand, so back to my original question: Are all those kernel options static or modular? They need to be static.
One other thing:
Quote:
Originally Posted by Rishabh
Now coming to the problem, my usb keyboard is not working neither in console nor in KDE. It works only in grub menu after that when kernel loads it does not response.
Just to make sure: You are talking about the CLI in runlevel 3 when you say console and not a terminal started from KDE?
means build statically, the M means modular. I hope you now understand, so back to my original question: Are all those kernel options static or modular? They need to be static.
Yes they are all static ( * ) none of them is modular.
Quote:
One other thing:
Just to make sure: You are talking about the CLI in runlevel 3 when you say console and not a terminal started from KDE?
Yes console that i am talking is CLI in runlevel 3 not the KDE terminal.
My second guess would be that you are missing an option. Pointing you to a specific one is a bit hard not knowing what you have(n't) enabled and your specific hardware.
Are you able to (remotely?) log into that LFS machine and fetch log files and/or execute commands?
If so:
- The output of dmesg after a (re)boot would be nice to see,
- Output of both lsusb and lspci would also be nice.
Have you tried:
- a different USB port?
- enabling OHCI_HCD or UHCI_HCD as well?
For one of my Slackware desktops at my university, I needed to enable both ehci_hcd and uhci_hcd to get all the USB ports working. It may well be that you need to do something similar.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.