From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: ieee1394
Date: Sun, 23 Jan 2005 20:14:59 +0000 [thread overview]
Message-ID: <1106511300.4660.15.camel@localhost.localdomain> (raw)
In-Reply-To: <41F3F0AC.2040200@mac.com>
On Sun, 2005-01-23 at 18:45 +0000, Mark R Biggerstaff wrote:
> Hi,
>
> I have recieved the following errors when connecting my firewire drive
> to my pc
> running Fedora Core 3.
> Jan 23 17:57:34 aluminum wait_for_sysfs[3877]: error: unknown bus,
> please report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
> Jan 23 17:57:34 aluminum wait_for_sysfs[3877]: either wait_for_sysfs
> (udev 039) needs an update to handle the device
After an installation of the available fedora udev update, the
wait_for_sysfs messages will not be printed. If your device isn't
working as expected you should ask on the ieee1394 list as it isn't a
hotplug or udev issue.
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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-01-23 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 18:45 ieee1394 Mark R Biggerstaff
2005-01-23 20: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=1106511300.4660.15.camel@localhost.localdomain \
--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).