I could use some help troubleshooting findkeyboards. It is not finding my keyboard. I'm not sure if the issue is in the findkeyboards script or if it is something else. Once the findkeyboards script failed, I tried manually running the udevadm commands it uses. Here is what I am seeing: /lib/udev$ udevadm info --version 173 /lib/udev$ ./findkeyboards AT keyboard: no device node found /lib/udev$ echo $? 5 /lib/udev$ udevadm trigger --dry-run --verbose --property-match=ID_INPUT_KEYBOARD=1 /sys/devices/platform/i8042/serio0/input/input4 /sys/devices/platform/i8042/serio0/input/input4/event4 /lib/udev$ udevadm info --query=name --path=/sys/devices/platform/i8042/serio0/input/input4/ no device node found /lib/udev$ udevadm info --query=name --path=/sys/devices/platform/i8042/serio0/input/input4/event4/ input/event4 It looks like the findkeyboards script can't find the device node for the first (input4) device, which causes the script to exit with status 5 before it checks the second (event4) device. I'm not sure whether the input4 device should have a device node or not. Any troubleshooting help would be appreciated. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
