Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#3547 - raw1394 & device
Attached to Project:
Arch Linux
Opened by Claudio Riva (Firetux) - Tuesday, 29 November 2005, 22:28 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 30 November 2005, 14:54 GMT
Opened by Claudio Riva (Firetux) - Tuesday, 29 November 2005, 22:28 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 30 November 2005, 14:54 GMT
|
DetailsI insert modules raw1394 and dmesg say:
[root@p3 ~]# dmesg | grep raw1394 ieee1394: raw1394: /dev/raw1394 device initialized [root@p3 ~]# device /dev/raw1394 doesn't exist but I have [root@p3 ~]# ls -l /dev/raw/raw1394 crw-rw---- 1 root root 171, 0 2005-11-29 23:18 /dev/raw/raw1394 [root@p3 ~]# owner: root and group: root but, if I understand udev rules, the group should be: video [root@p3 ~]# less /etc/udev/rules.d/udev.rules | grep raw # raw devices KERNEL=="raw[0-9]*", NAME="raw/%k" KERNEL=="raw1394", NAME="%k", GROUP="video" [root@p3 ~]# where is the problem? |
This task depends upon
KERNEL=="raw1394", NAME="%k", GROUP="video"
Udev matches the first and will ignore the other one. I don't know where raw[0-9] is used with, but it certainly isn't firewire. Swap the rules and firewire devices should get the right permissions and devicenode.