From: Arthur Hartwig <a_hartwig@fastmail.fm>
To: linux-hotplug@vger.kernel.org
Subject: Bus specific file unavailable
Date: Tue, 16 Aug 2005 22:03:42 +0000 [thread overview]
Message-ID: <430262BE.9010002@fastmail.fm> (raw)
My Gentoo 2005.1 (Linux 2.6.12) system has been reporting on startup:
wait_for_sysfs[7376]: either wait_for_sysfs (udev 045) needs an update
to handle the device '/devices/pci0000:00/0000:04.0/i2c-0/0-0048'
properly (bus specific file unavailable) or the sysfs-support of your
device's driver need to be fixed, please report to
<linux-hotplug-devel@lists.sourceforge.net>
I get the same thing reported twice more for devices "49" and '2d'
('49' and '2d' replace the '48' in the above message).
after logging in I see":
# more /sys/bus/i2c/devices/0-002d/name
as99127f
# more /sys/bus/i2c/devices/0-0048/name
as99127f subclient
# more /sys/bus/i2c/devices/0-0049/name
as99127f subclient
I am happy to provide any additional information you might require.
Arthur
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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
next reply other threads:[~2005-08-16 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 22:03 Arthur Hartwig [this message]
2005-08-16 23:14 ` Bus specific file unavailable 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=430262BE.9010002@fastmail.fm \
--to=a_hartwig@fastmail.fm \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.