Thank you. So the kernel clearly sees a new mouse and keyboard, and assigns input devices for both of them. hal even picks it up and creates a keyboard device for you:
so I wonder why it does not work under X (which still uses hal). After plugging in the keyboard, can you please attach /var/log/Xorg.0.log ? For my USB keyboard, it looks like
(II) config/hal: Adding input device HID 05f3:0007
(**) HID 05f3:0007: always reports core events
(**) HID 05f3:0007: Device: "/dev/input/event8"
(II) HID 05f3:0007: Found keys
(II) HID 05f3:0007: Configuring as keyboard
(II) XINPUT: Adding extended input device "HID 05f3:0007" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "us"
so I wonder how it looks for your's. It should at least see _something_, since it's in hal.
It should have ID_USB_*, and ID_CLASS=kbd, etc. It seems that it didn't even run usb_id on that one.
Can you please run
udevadm monitor
then plug in the keyboard, annd watch out for an "add" event which looks like
"/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/input/input12/event10", i. e. ends in "inputXX/eventYY". Then please copy&paste the output of
udevadm test /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/input/input12/event10
Thank you. So the kernel clearly sees a new mouse and keyboard, and assigns input devices for both of them. hal even picks it up and creates a keyboard device for you:
udi = '/org/freedeskt op/Hal/ devices/ usb_device_ 1d6b_1_ 0000_00_ 1d_1_if1_ logicaldev_ input_0' event11' (string) switch, compose: menu' (string)
[...]
info.capabilities = {'input', 'input.keys', 'input.mouse', 'button'} (string list)
input.device = '/dev/input/
input.product = 'USBPS2' (string)
input.x11_driver = 'evdev' (string)
input.xkb.layout = 'us' (string)
input.xkb.model = 'pc104' (string)
input.xkb.options = 'lv3:ralt_
input.xkb.rules = 'base' (string)
[...]
so I wonder why it does not work under X (which still uses hal). After plugging in the keyboard, can you please attach /var/log/Xorg.0.log ? For my USB keyboard, it looks like
(II) config/hal: Adding input device HID 05f3:0007
(**) HID 05f3:0007: always reports core events
(**) HID 05f3:0007: Device: "/dev/input/event8"
(II) HID 05f3:0007: Found keys
(II) HID 05f3:0007: Configuring as keyboard
(II) XINPUT: Adding extended input device "HID 05f3:0007" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "us"
so I wonder how it looks for your's. It should at least see _something_, since it's in hal.
For the udev side, this is indeed a bit poor:
UDEV [1255524718.339876] add /devices/ pci0000: 00/0000: 00:1d.1/ usb7/7- 1/7-1:1. 0/input/ input12/ event10 (input) /devices/ pci0000: 00/0000: 00:1d.1/ usb7/7- 1/7-1:1. 0/input/ input12/ event10 input/event10 /dev/char/ 13:74
UDEV_LOG=3
ACTION=add
DEVPATH=
SUBSYSTEM=input
DEVNAME=
SEQNUM=4318
MAJOR=13
MINOR=74
DEVLINKS=
It should have ID_USB_*, and ID_CLASS=kbd, etc. It seems that it didn't even run usb_id on that one.
Can you please run
udevadm monitor
then plug in the keyboard, annd watch out for an "add" event which looks like pci0000: 00/0000: 00:1d.1/ usb7/7- 1/7-1:1. 0/input/ input12/ event10" , i. e. ends in "inputXX/eventYY". Then please copy&paste the output of
"/devices/
udevadm test /devices/ pci0000: 00/0000: 00:1d.1/ usb7/7- 1/7-1:1. 0/input/ input12/ event10
(with the path that you just determined).
Thanks!