From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: ERROR IN LOGFILE
Date: Thu, 25 Nov 2004 16:10:40 +0000 [thread overview]
Message-ID: <1101399040.13444.21.camel@localhost.localdomain> (raw)
In-Reply-To: <1101377945.5937.2.camel@localhost>
On Thu, 2004-11-25 at 11:19 +0100, Sasa Ostrouska wrote:
> Hi to all of you !!
>
> I played today with my quickcam and saw the following message in the
> /var/log/messages
> I use slackware-current and I would like to know more about that.
> Can somebody explain me how can I get rid of that error message ?
> Nov 25 11:14:05 localhost wait_for_sysfs[5761]: either wait_for_sysfs
> (udev 042) needs an update to handle the device
> '/class/video4linux/video0' properly (no device symlink) or the
> sysfs-support of your device's driver needs to be fixed, please report
> to <linux-hotplug-devel@lists.sourceforge.net>
It's cause the driver of your camera does not create a link in sysfs to
the physical device behind the videodevice. This is needed for modern
hardware integration or udev's BUS= matches.
How does "ls -l /sys/class/video4linux/video0" look like?
What's the name of the module? Is it in the stock kernel?
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
next prev parent reply other threads:[~2004-11-25 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 10:19 ERROR IN LOGFILE Sasa Ostrouska
2004-11-25 16:10 ` Kay Sievers [this message]
2004-11-25 16:47 ` Sasa Ostrouska
2004-11-25 17:13 ` 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=1101399040.13444.21.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).