linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* findkeyboards - no device node found
@ 2011-10-25 23:09 John Serock
  2011-10-26  9:06 ` Martin Pitt
  0 siblings, 1 reply; 2+ messages in thread
From: John Serock @ 2011-10-25 23:09 UTC (permalink / raw)
  To: linux-hotplug

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: findkeyboards - no device node found
  2011-10-25 23:09 findkeyboards - no device node found John Serock
@ 2011-10-26  9:06 ` Martin Pitt
  0 siblings, 0 replies; 2+ messages in thread
From: Martin Pitt @ 2011-10-26  9:06 UTC (permalink / raw)
  To: linux-hotplug

Hello John,

John Serock [2011-10-25 19:09 -0400]:
> 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:

What a weird coincidence, I also used findkeyboards again this morning
because I got a PM for a keymap fix, and noticed the very same
problem. I'm not sure when this got broken, or whether it's due to a
kernel or udev change, but this fixes it:

  http://git.kernel.org/?p=linux/hotplug/udev.git;a=commit;häb7a9be03441db21d459cbb9c08400377c3556d

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-10-26  9:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-10-25 23:09 findkeyboards - no device node found John Serock
2011-10-26  9:06 ` Martin Pitt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).