On Friday 19 January 2007 11:26, Roberto Malinverni wrote:
> Pardon my jumping in - I admit I haven't read all the discussion, so maybe
> this has already been said.
First, thanks for answering. I'm sorry that this is such a long reply, but
I'm trying to gather/give as much info as possible.
> Anyway, I notice that your "rules" file is number 83:
No, that was Paulo's. Mine is 98. Somewhere among all the reading I did was
the advice to give it as high a number as possible, so that it was the last
to run.
> do you think it's
> possible that some preceeding rule interferes here with what you want to
> do?
I'm very much a newbie at this, so I really don't know.
> My custom udev rules file (for removable and optical media) is number
> 20 and it is processed before the default one (number 60 IIRC). Also, I
> added the "lastrule" option to each entry I created, to be sure that no
> other rules are parsed for the devices I'm interested in.
Could you tell me more about the 'lastrule' option - how it works, what syntax
is needed to set it, etc.?
I notice that if I run udevtrigger, listing /dev/DCplus gives me one link,
which is almost immediately changed to another:
[anne@david ~]$ ls -al /dev/DC10plus
lrwxrwxrwx 1 root root 15 Jan 19 11:17 /dev/DC10plus -> bus/usb/005/005
[anne@david ~]$ ls -al /dev/DC10plus
lrwxrwxrwx 1 root root 4 Jan 19 11:17 /dev/DC10plus -> ram7
Udevtest gives me much more info:
udevtest /class/video4linux/video0
main: looking at device '/class/video4linux/video0' from
subsystem 'video4linux'
udev_rules_get_name: add symlink 'video'
udev_rules_get_name: add symlink 'DC10plus'
udev_rules_get_name: no node name set, will use kernel name 'video0'
udev_device_event: device '/class/video4linux/video0' already in database,
validate currently present symlinks
udev_node_add: creating device node '/dev/video0', major = '81', minor = '0',
mode = '0660', uid = '0', gid = '0'
udev_node_add: creating symlink '/dev/video' to 'video0'
udev_node_add: creating symlink '/dev/DC10plus' to 'video0'
main: run: 'socket:/org/kernel/udev/monitor'
main: run: '/lib/udev/udev_run_devd'
main: run: 'socket:/org/freedesktop/hal/udev_event'
main: run: '/sbin/pam_console_apply /dev/video0 /dev/video /dev/DC10plus'
Does that give any clues as to why it doesn't work?
I've just tried a reboot, and this time there was a bootup message that
creating /devDC10plus failed.
Jan 19 11:50:55 david kernel: MJPEG[0]: Zoran ZR36067 (rev 2) irq: 193,
memory: 0xea014000
Jan 19 11:50:55 david kernel: MJPEG[0]: subsystem vendor=0x1031 id=0x7efe
Jan 19 11:50:55 david kernel: ZORAN: 1 card(s) found
Jan 19 11:50:55 david kernel: DC10plus[0]: zr36057_init() - initializing
card[0], zr=f8b260c0
Jan 19 11:51:30 david udevd-event[3642]: udev_node_symlink:
symlink(audio, /dev/DC10plus) failed: File exists
Jan 19 11:51:32 david udevd-event[4161]: udev_node_symlink:
symlink(ram11, /dev/DC10plus) failed: File exists
Clearly it wasn't removed at shutdown. The old link that remains is pointing
to video0, when it should be video1, which explains some of what appears
above.
Looking at 'messages' there are many SELinux entries such as
Summary
SELinux is preventing /sbin/pam_console_apply (pam_console_t) "getattr"
access to device /dev/video0.
I can give more detail from sealert if it helps.
The first need, I think, is to try to find out why /dev/DC10plus was not
removed at shutdown.
Anne
