From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bus specific file unavailable
Date: Tue, 16 Aug 2005 23:14:31 +0000 [thread overview]
Message-ID: <20050816231431.GB11750@vrfy.org> (raw)
In-Reply-To: <430262BE.9010002@fastmail.fm>
On Wed, Aug 17, 2005 at 08:03:42AM +1000, Arthur Hartwig wrote:
> 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.
Update your udev! Especially if you run a recent kernel. Your combination of
udev and the kernel will not work correctly.
Kay
-------------------------------------------------------
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
prev parent reply other threads:[~2005-08-16 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 22:03 Bus specific file unavailable Arthur Hartwig
2005-08-16 23:14 ` Kay Sievers [this message]
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=20050816231431.GB11750@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).