From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev device nodes won't come back
Date: Wed, 29 Sep 2004 10:22:24 +0000 [thread overview]
Message-ID: <1096453344.5070.11.camel@localhost.localdomain> (raw)
In-Reply-To: <415A5FCA.2000805@nodivisions.com>
On Wed, 2004-09-29 at 03:10 -0400, Anthony DiSante wrote:
> Hello,
>
> I'm running udev 030 on a Gentoo / 2.6.8 system, and I'm having some trouble
> with my tv tuner card. While trying to get things working, I noticed that
> the /dev/v4l directory was only present when the bttv module was loaded.
> But at one point after a system lockup, /dev/v4l was there even though bttv
> was *not* loaded.
>
> So I deleted /dev/v4l expecting it to be properly re-created when I loaded
> bttv... but that didn't happen. How can I fix this?
Does running /sbin/udevstart create the node?
What is in the db?
[kay@pim ~]$ udevinfo -q all -p /sys/class/video4linux/video0
P: /sys/class/video4linux/video0
N: video0
T: c
M: 020660
S: video
O: root
G: root
F: /etc/udev/rules.d/50-udev.rules
L: 33
U: 45486
What does udevtest print?
[kay@pim ~]$ udevtest /sys/class/video4linux/video0
version 032
looking at '/class/video4linux/video0'
configured rule in '/etc/udev/rules.d/50-udev.rules' at line 33 applied, 'video0' becomes '%k'
creating device node '/dev/video0', major = '81', minor = '0', mode = '020660', uid = '0', gid = '0'
How does the corresponding /sys-device entry look like?
[kay@pim ~]$ tree /sys/class/video4linux/
/sys/class/video4linux/
`-- video0
|-- bridge
|-- brightness
|-- contrast
|-- custom_id
|-- dev
|-- device -> ../../../devices/pci0000:00/0000:00:1d.1/usb3/3-1
|-- driver -> ../../../bus/usb/drivers/usb
|-- exposure
|-- hue
|-- model
|-- name
|-- saturation
`-- sensor
Good luck,
Kay
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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-09-29 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 7:10 udev device nodes won't come back Anthony DiSante
2004-09-29 10:22 ` Kay Sievers [this message]
2004-09-29 18:46 ` Anthony DiSante
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=1096453344.5070.11.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).