linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simone Crippa <simone.crippa@gmx.net>
To: linux-hotplug@vger.kernel.org
Subject: wait_for_sysfs, udev
Date: Wed, 27 Oct 2004 10:46:22 +0000	[thread overview]
Message-ID: <200410271246.22679.simone.crippa@gmx.net> (raw)

Hello,

I plugged in into my USB port a palm tungsten and tried to hotplug, which 
resulted in the daemon.log entry:

Oct 27 12:34:54 nx7000 wait_for_sysfs[8184]: error: wait_for_sysfs needs an 
update to handle the device '/devices/pci0000:00/0000:00:1d.0/usb1/1-2' 
properly, please report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 27 12:34:54 nx7000 wait_for_sysfs[8186]: error: wait_for_sysfs needs an 
update to handle the device 
'/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0' properly, please report 
to <linux-hotplug-devel@lists.sourceforge.net>

I have a Debian system (testing) with udev 0.034-1, hotplug 
0.0.20040329-1 and libsysfs1 1.1.0-1 . Don't know what is relevant, if you 
need more info, mail me back.

Since I have reported a similar error message before, I already tried with 
udev version 0.040 from:

http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-040.tar.gz

it resulted in the same error:

Oct 27 12:38:06 nx7000 wait_for_sysfs[8484]: either wait_for_sysfs (udev 040) 
needs an update to handle the device 
'/devices/pci0000:00/0000:00:1d.0/usb1/1-2' properly (no bus device link) or 
the sysfs-support of your device's driver needs to be fixed, please report to 
<linux-hotplug-devel@lists.sourceforge.net>
Oct 27 12:38:06 nx7000 wait_for_sysfs[8486]: either wait_for_sysfs (udev 040) 
needs an update to handle the device 
'/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0' properly (no bus device 
link) or the sysfs-support of your device's driver needs to be fixed, please 
report to <linux-hotplug-devel@lists.sourceforge.net>

Further info:

root@nx7000:~# ls 
-l /sys/devices/pci0000\:00/0000\:00\:1d.0/usb1/1-2/1-2\:1.0/
insgesamt 0
-r--r--r--  1 root root 4096 2004-10-27 12:34 bAlternateSetting
-r--r--r--  1 root root 4096 2004-10-27 12:34 bInterfaceClass
-r--r--r--  1 root root 4096 2004-10-27 12:34 bInterfaceNumber
-r--r--r--  1 root root 4096 2004-10-27 12:34 bInterfaceProtocol
-r--r--r--  1 root root 4096 2004-10-27 12:34 bInterfaceSubClass
-r--r--r--  1 root root 4096 2004-10-27 12:34 bNumEndpoints
-rw-r--r--  1 root root 4096 2004-10-27 12:34 detach_state
-r--r--r--  1 root root 4096 2004-10-27 12:34 iInterface
drwxr-xr-x  2 root root    0 2004-10-27 12:34 power
drwxr-xr-x  3 root root    0 2004-10-27 12:34 ttyUSB0
drwxr-xr-x  3 root root    0 2004-10-27 12:34 ttyUSB1
root@nx7000:~# ls 
-l /sys/devices/pci0000\:00/0000\:00\:1d.0/usb1/1-2/1-2\:1.0/ttyUSB1/
insgesamt 0
-rw-r--r--  1 root root 4096 2004-10-27 12:34 detach_state
drwxr-xr-x  2 root root    0 2004-10-27 12:34 power
root@nx7000:~# ls 
-l /sys/devices/pci0000\:00/0000\:00\:1d.0/usb1/1-2/1-2\:1.0/ttyUSB0/
insgesamt 0
-rw-r--r--  1 root root 4096 2004-10-27 12:34 detach_state
drwxr-xr-x  2 root root    0 2004-10-27 12:34 power


I hope I can help further. Is it possible that there are so many errors left 
in udev? Before I switched from devfs to udev some weeks ago, I didn't have 
these problems.


Greatings, Simone


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2004-10-27 10:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27 10:46 Simone Crippa [this message]
2004-10-27 20:04 ` wait_for_sysfs, udev Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200410271246.22679.simone.crippa@gmx.net \
    --to=simone.crippa@gmx.net \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).