alex ponomarev wrote:
If you're talking about console, try to look trough output of "dmesg | grep
'usb' " there must be something about your USB HID keyboard, may be some
errors about it. Also look through "lsusb", is your keyboard mentioned here?
Sorry, I forgot to say, I'm talking about console.
-----------------------------
obelix ~ # dmesg | grep 'usb'
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usb usb1: configuration #1 chosen from 1 choice
usb usb2: configuration #1 chosen from 1 choice
usb 2-1: new low speed USB device using ohci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usb-storage
input: USB HID v1.00 Keyboard [ USB Multimedia Keyboard ] on
usb-0000:00:02.0-1
input: USB HID v1.00 Device [ USB Multimedia Keyboard ] on
usb-0000:00:02.0-1
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
obelix ~ # lsusb
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 002: ID 099a:713a Zippy Technology Corp.
Bus 002 Device 001: ID 0000:0000
-----------------------------
It seems usb-keyboard is there (at least in dmesg output),
but it simply does not work at all. Even NumLock & SysLock
keys do not switch checklights on/off. It is like frozen...
Jarry
--
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.
