On Tue, 26 Mar 2002 02:38, Eduard Bloch wrote: > I have a reproducible problem with USB keyboard on at least two > machines. It is always the same story: if only one USB keyboard is > attached and no AT-style keyboard else, the BIOS legacy emulation stops > working while the hardware initialisation at boot time. BUT: If an > additional "normal" keyboard is connected, Linux does not have any > problem, I can use both keyboards, remove the old keyboard and continue > working with USB keyboard. It sounds like you have some combination of a BIOS problem, and mismatched drivers.
To understand what is happening: 1. When the machine boots under BIOS control, the BIOS can run the usb keyboard, and make it appear as a normal keyboard. This is normally optional in the BIOS [look for an option called "legacy keyboard" or "USB keyboard emulation" or something like that] 2. When the Linux USB host controller code comes up, it "takes over" control. At that point, you need to have all of the support modules loaded, including your keyboard code. So you either need to make the modules be loaded automatically (hotplug system, some other scripting, whatever) or you need to build your USB support into the kernel, or (if you don't need real USB support), don't load any host controller code. > In the first case, when the keyboard is locked, it does help to load the > USB driver, ubskbd.o and keybdev.o, and the keyboard is useable again. I assume that this is "usbkbd.o"? Do you have the hid driver and input driver (hid.o and input.o) either loaded as modules or built into the kernel? If so, you shouldn't be using usbkbd.o. If you don't (or won't) use the "full HID" support, don't load keybdev.o IMNSHO, full HID and usbkbd.o is too confusing, but the maintainer disagrees. [Greg - note another unhappy customer, keep counting them :( ] HTH Brad _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
