I was missled by the syslog update whenever I snap the keyboard on or off (the fragment in the system info and logs attachment).
so I messed around with "udevadm monitor" and looked again at dmesg. When I snap the keyboard on the dmesg says "HID_DG_INPUTMODE out of range -> No inputs registered" (full excerpt attached).
so thats seems to be why /dev/hidraw# spews data but is not heard by X.
Yet I am not clear about why the device is disconnected before and an ACPI error is raised.
yes confirmed. cat /dev/hidraw# spews data.
I was missled by the syslog update whenever I snap the keyboard on or off (the fragment in the system info and logs attachment).
so I messed around with "udevadm monitor" and looked again at dmesg. When I snap the keyboard on the dmesg says "HID_DG_INPUTMODE out of range -> No inputs registered" (full excerpt attached).
so thats seems to be why /dev/hidraw# spews data but is not heard by X.
Yet I am not clear about why the device is disconnected before and an ACPI error is raised.