From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: firewire error
Date: Sun, 28 Nov 2004 03:30:02 +0000 [thread overview]
Message-ID: <1101612602.5271.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20041128004113.70572.qmail@web21007.mail.yahoo.com>
On Sat, 2004-11-27 at 16:41 -0800, Ted Haynes wrote:
> Hi, When I plug in my camcorder (panasonic pvdv400) it
> does not work. Here is the contents of my
> /var/log/messages
> <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
> Nov 27 18:03:26 tower wait_for_sysfs[3471]: either
> wait_for_sysfs (udev 039) needs an update to handle
> the device
> '/devices/pci0000:00/0000:00:0f.0/fw-host0/00804580b0b45088'
> properly (unknown bus) or the sysfs-support of your
> device's driver needs to be fixed, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
> Nov 27 18:03:26 tower wait_for_sysfs[3481]: error:
> unknown bus, please report to
These messages will not be printed with a later udev. But they are not
related to any functional problem problem with your device. You better
look for help at a firewire specific list.
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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:[~2004-11-28 3:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 0:41 firewire error Ted Haynes
2004-11-28 3:30 ` 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=1101612602.5271.3.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).