kb2qzv
2004-09-24, 07:08 AM CDT
Hi forum,
I've googled and looked for hours...so finally came here.
The camera is Panasonic PV-DV51D. It worked under FC2.
The problem: no /dev/raw1394 entry in dev directory.
dmesg:
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ieee1394: Node resumed: ID:BUS[0-00:1023] GUID[00804580b0c981eb]
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
Interestingly the device gets initialized in the log file:
[root@localhost ~]# cat /var/log/messages | grep ieee
Sep 23 18:15:44 localhost ieee1394.agent[4547]: ... no drivers for IEEE1394 product 0x/0x/0x
Sep 23 18:15:44 localhost ieee1394.agent[4550]: ... no drivers for IEEE1394 product 0x/0x/0x
Sep 23 18:15:44 localhost kernel: ieee1394: raw1394: /dev/raw1394 device initialized
[root@localhost ~]# lspci | grep Fire
00:09.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port
Udevinfo reports that there is something in /sys filesystem:
[root@localhost ~]# udevinfo -a -p /sys/devices/pci0000\:00/0000\:00\:09.2/
[...]
looking at class device '/sys/devices/pci0000:00/0000:00:09.2':
SYSFS{class}="0x0c0010"
SYSFS{detach_state}="0"
SYSFS{device}="0x4001"
SYSFS{irq}="10"
SYSFS{subsystem_device}="0x0010"
SYSFS{subsystem_vendor}="0x1102"
SYSFS{vendor}="0x1102"
I tried to learn the rule making technics and ended up like so:
[root@localhost ~]# cat /etc/udev/rules.d/10-udev.rules
SYSFS{class}="0x0c0010", SYSFS{device}="0x4001", NAME="raw1394"
I'v tried KERNEL="ieee1394" and KERNEL="raw1394" in place of SYSFS{class} but to no avail.
But still there is no /dev/raw1394 device node:
[root@localhost ~]# ls /dev/raw*
ls: /dev/raw*: No such file or directory
I'd be happy to get hints on how to fix it.
I've googled and looked for hours...so finally came here.
The camera is Panasonic PV-DV51D. It worked under FC2.
The problem: no /dev/raw1394 entry in dev directory.
dmesg:
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ieee1394: Node resumed: ID:BUS[0-00:1023] GUID[00804580b0c981eb]
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
Interestingly the device gets initialized in the log file:
[root@localhost ~]# cat /var/log/messages | grep ieee
Sep 23 18:15:44 localhost ieee1394.agent[4547]: ... no drivers for IEEE1394 product 0x/0x/0x
Sep 23 18:15:44 localhost ieee1394.agent[4550]: ... no drivers for IEEE1394 product 0x/0x/0x
Sep 23 18:15:44 localhost kernel: ieee1394: raw1394: /dev/raw1394 device initialized
[root@localhost ~]# lspci | grep Fire
00:09.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port
Udevinfo reports that there is something in /sys filesystem:
[root@localhost ~]# udevinfo -a -p /sys/devices/pci0000\:00/0000\:00\:09.2/
[...]
looking at class device '/sys/devices/pci0000:00/0000:00:09.2':
SYSFS{class}="0x0c0010"
SYSFS{detach_state}="0"
SYSFS{device}="0x4001"
SYSFS{irq}="10"
SYSFS{subsystem_device}="0x0010"
SYSFS{subsystem_vendor}="0x1102"
SYSFS{vendor}="0x1102"
I tried to learn the rule making technics and ended up like so:
[root@localhost ~]# cat /etc/udev/rules.d/10-udev.rules
SYSFS{class}="0x0c0010", SYSFS{device}="0x4001", NAME="raw1394"
I'v tried KERNEL="ieee1394" and KERNEL="raw1394" in place of SYSFS{class} but to no avail.
But still there is no /dev/raw1394 device node:
[root@localhost ~]# ls /dev/raw*
ls: /dev/raw*: No such file or directory
I'd be happy to get hints on how to fix it.