dvgrab: Error: no camera exists

Dieter@be · 2009-09-09 19:15:33

Hi,
I'm trying to capture DV video with dvgrab, but it gives me the error "Error: no camera exists"
I've looked around a lot on the interwebs and tried many things, but no avail
- it worked on Gentoo so the hardware is fine
- i also tried as root, same shit
- tried plugging in and out the FW cable also doesn't help. tried several ports as well.

* arch linux i686 (all latest packages from core/testing)
* canopus advc110
* 6pin firewire cable
* some VIA-based firewire pci card.

[dieter@dieter-p4sci-arch orig]$ lsmod | grep 1394
video1394              15740  0 
dv1394                 18428  0 
ohci1394               30196  2 video1394,dv1394
raw1394                25724  0 
ieee1394               85324  4 video1394,dv1394,ohci1394,raw1394

[dieter@dieter-p4sci-arch orig]$ ls -alh /dev/*1394*
crw-rw---- 1 root video 171, 0 2009-09-07 22:42 /dev/raw1394
crw-rw-rw- 1 root root  172, 0 2009-09-09 20:50 /dev/video1394

/dev/dv1394:
total 0
drwxr-xr-x  2 root root       60 2009-09-09 20:51 .
drwxr-xr-x 14 root root     5.6K 2009-09-09 20:51 ..
crw-rw----  1 root video 171, 32 2009-09-09 20:51 0

[dieter@dieter-p4sci-arch orig]$ groups
wheel bitlbee video users


[dieter@dieter-p4sci-arch orig]$ lspci
00:00.0 Host bridge: Intel Corporation 82875P/E7210 Memory Controller Hub (rev 02)
00:03.0 PCI bridge: Intel Corporation 82875P/E7210 Processor to PCI to CSA Bridge (rev 02)
00:06.0 System peripheral: Intel Corporation 82875P/E7210 Processor to I/O Memory Interface (rev 02)
00:1c.0 PCI bridge: Intel Corporation 6300ESB 64-bit PCI-X Bridge (rev 02)
00:1d.0 USB Controller: Intel Corporation 6300ESB USB Universal Host Controller (rev 02)
00:1d.1 USB Controller: Intel Corporation 6300ESB USB Universal Host Controller (rev 02)
00:1d.4 System peripheral: Intel Corporation 6300ESB Watchdog Timer (rev 02)
00:1d.5 PIC: Intel Corporation 6300ESB I/O Advanced Programmable Interrupt Controller (rev 02)
00:1d.7 USB Controller: Intel Corporation 6300ESB USB2 Enhanced Host Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 0a)
00:1f.0 ISA bridge: Intel Corporation 6300ESB LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 6300ESB SATA Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 6300ESB SMBus Controller (rev 02)
01:01.0 Ethernet controller: Intel Corporation 82547GI Gigabit Ethernet Controller
02:01.0 PCI bridge: Intel Corporation 80331 [Lindsay] I/O processor (PCI-X Bridge) (rev 07)
03:0e.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID (rev 07)
04:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev ff)
04:09.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
04:0a.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller

dmesg (full at http://sprunge.us/ejBh)

[dieter@dieter-p4sci-arch orig]$ dmesg | grep 1394
ieee1394: raw1394: /dev/raw1394 device initialized
ohci1394 0000:04:02.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Runaway loop while stopping context: ...
ohci1394: fw-host0: Runaway loop while stopping context: ...
ohci1394: fw-host0: Runaway loop while stopping context: ...
ohci1394: fw-host0: Runaway loop while stopping context: ...
ohci1394: fw-host0: OHCI-1394 165.165 (PCI): IRQ=[21]  MMIO=[f1000000-f10007ff]  Max Packet=[65536]  IR/IT contexts=[32/32]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
ohci1394: fw-host0: Serial EEPROM has suspicious values, attempting to set max_packet_size to 512 bytes

Dieter@be · 2009-09-26 07:38:43

*bump*
plz help me
kthxbye

eviltoaster · 2009-10-14 17:16:04

Dieter@be wrote:

*bump*
plz help me
kthxbye

Did you solved it?

Dieter@be · 2009-10-14 19:39:18

eviltoaster wrote:

Dieter@be wrote:
*bump*
plz help me
kthxbye
Did you solved it?

no :(

1LordAnubis · 2009-10-14 20:39:41

Looks similar to an older thread: http://bbs.archlinux.org/viewtopic.php?id=38826

kdenlive has a good article: http://www.kdenlive.org/user-manual/tro … re-capture

Perhaps its a udev permission problem?

Dieter@be · 2009-11-14 09:44:50

1LordAnubis wrote:

Looks similar to an older thread: http://bbs.archlinux.org/viewtopic.php?id=38826
Perhaps its a udev permission problem?

that older thread is different I think, it seems to be about buggy packages (which should be fixed by now) on arch x86_64.
it can't be a permission problem since even doing it as root doesn't work.

interesting though, according tho kdenlive article, it seems like we have an outdated firewire stack on Arch

Last edited by Dieter@be (2009-11-14 09:48:35)

hakova · 2009-11-16 04:37:33

Hi there,

I have both Mandriva 2009.1 and Arch installed on different partitions and I have the same/similar problem. When I connect my camera and turn it on, I get exactly the same error messages from dmesg in both OSs http://pastebin.com/m1ea1d02c. Neither Kino, nor Cheese recognizes the camera. The funny thing is I was using the same camera, Firewire card and PC combination with Mandriva 2008 and earlier versions without a glitch. At those times, the kernel modules for firewire were named differently (firewire_ohci, and alike), rather than the norm today (raw1394). I humbly believe that this is due to a buggy kernel module. I just don't know how to confirm it and if confirmed, how to make people be aware of it.

hakova · 2009-11-26 04:11:18

After days of experimenting, I figured that Ubuntu Live CD comes with two sets
of firewire drivers: the old stack (ohci1394) and the new stack
(firewire-ohci). To test both stacks, I booted up with it. The default driver
was the old stack (i.e. ohci1394) I got similar dmesg output as with Mandriva
2010.0 and Arch linux distributions:

...
[ 1176.161958] ohci1394: fw-host0: isochronous cycle too long
[ 1176.614334] ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
[ 1176.640319] ohci1394: fw-host0: SelfID received, but NodeID invalid
(probably new bus reset occurred): 0000FFC0
[ 1177.088015] ohci1394: fw-host0: isochronous cycle too long
[ 1177.291242] ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
[ 1177.352254] ohci1394: fw-host0: SelfID received, but NodeID invalid
(probably new bus reset occurred): 0000FFC0
[ 1177.764016] ohci1394: fw-host0: isochronous cycle too long
[ 1177.978286] ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
[ 1177.978456] ohci1394: fw-host0: SelfID received, but NodeID invalid
(probably new bus reset occurred): 0000FFC0
[ 1177.981364] ohci1394: fw-host0: SelfID received, but NodeID invalid
(probably new bus reset occurred): 0000FFC0
[ 1177.988203] ohci1394: fw-host0: SelfID received, but NodeID invalid
(probably new bus reset occurred): 0000FFC0
[ 1178.063864] ohci1394: fw-host0: SelfID received, but NodeID invalid
(probably new bus reset occurred): 0000FFC0
[ 1178.131585] ohci1394: fw-host0: SelfID received, but NodeID invalid
(probably new bus reset occurred): 0000FFC0
...

Next, I removed ohci1394 module, and loaded firewire-ohci. After
connecting the camera and turning it on, I got the following dmesg
output:

[ 1644.060012] firewire_ohci: Added fw-ohci device 0000:05:05.0, OHCI
version 1.10
[ 1644.060058] firewire_ohci: swap not done yet
[ 1644.060068] firewire_ohci: swap not done yet
[ 1644.560136] firewire_core: created device fw0: GUID 00004c010000490f, S400
[ 1671.987013] firewire_ohci: node ID not valid, new bus reset in progress
[ 1671.987601] firewire_ohci: node ID not valid, new bus reset in progress
[ 1671.987789] firewire_core: skipped bus generations, destroying all nodes
[ 1672.484035] firewire_core: rediscovered device fw0
[ 1672.499212] firewire_core: created device fw1: GUID 00804580113274b5, S100
[ 1672.499218] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
[ 1672.523070] ieee1394: raw1394: /dev/raw1394 device initialized

Nice, right? Then I did "sudo dvgrab -i" with the following output:

Found AV/C device with GUID 0x00804580113274b5
Going interactive. Press '?' for help.
q=quit, p=play, c=capture, Esc=stop, h=reverse, j=backward scan, k=pause
l=forward scan, a=rewind, z=fast forward, 0-9=trickplay, <space>=play/pause
Winding Stoppede" 00:28:42:26 "" sec
Winding Stoppedd" 00:28:30:28 "" sec
Capture Startedd" 00:28:30:28 "" sec
"Playing" 00:28:31:21 "" 0.00 sec
"": damaged frame near: timecode 00:33:44.27 date 2009.11.14 14:29:08
This means that there were missing or invalid FireWire packets.
"dvgrab-001.dv": 104.37 MiB 912 frames timecode 00:29:02.08 date
2009.11.14 14:22:57
Capture Stopped
Warning: 1 damaged frames.
"Playing Paused" 00:29:02:17 "" sec

Yey! I just captured a 30 second segment! I watched the segment and
confirmed that it was viewable and audible. It basically worked.

Now my questions are as follows:

1. Do I have to compile my own kernel for the new firewire stack to be included
as a module, or is it available as a binary package anywhere?

2. For future releases of Arch, would you please consider including both
drivers/modules in the default kernel?

Regards.

Dieter@be · 2009-12-08 21:36:09

good to hear that hakova!
I read that the arch package of 2.6.32 uses the new firewire stack. it's in the testing repo, so we can start playing..

Dieter@be · 2010-01-09 18:10:48

*damn* no result with 2.6.32 either
(note i'm using a different pc then last time, because the new kernel doesn't recognize my via firewire card anymore. this one has nvidia firewire)

dmesg only says:

firewire_core: phy config: card 0, new root=ffc1, gap_count=5
firewire_core: giving up on config rom for node id ffc1

dieter@dieter-ws-a7n8x-arch ~ ls -alh /lib/modules/2.6.32-ARCH/ | egrep 'fire|ieee1394|ohci'
-rw-r--r-- 1 root root 221 Jan 8 18:33 modules.ieee1394map
dieter@dieter-ws-a7n8x-arch ~ sudo modprobe ieee1394map
FATAL: Module ieee1394map not found.
dieter@dieter-ws-a7n8x-arch ~ lsmod | egrep 'fire|ieee1394|ohci'
firewire_ohci 20266 0
firewire_core 37529 1 firewire_ohci
crc_itu_t 1041 1 firewire_core
ohci_hcd 19732 0
usbcore 118921 4 usbhid,ohci_hcd,ehci_hcd
dieter@dieter-ws-a7n8x-arch ~ lspci
00:00.0 Host bridge: nVidia Corporation nForce2 IGP2 (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
00:05.0 Multimedia audio controller: nVidia Corporation nForce Audio Processing Unit (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:0c.0 PCI bridge: nVidia Corporation nForce2 PCI Bridge (rev a3)
00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE 1394) Controller (rev a3)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:0a.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
01:0b.0 RAID bus controller: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 01)
02:01.0 Ethernet controller: 3Com Corporation 3C920B-EMB Integrated Fast Ethernet Controller [Tornado] (rev 40)
03:00.0 VGA compatible controller: nVidia Corporation NV30 [GeForce FX 5800] (rev a2)

Last edited by Dieter@be (2010-01-09 18:12:14)

Dieter@be · 2010-01-10 15:08:37

I gave up and choose the method which cost me the least time..

dieter@dieter-ubuntu-ws-a7n8x:~$ dmesg | grep ieee
[ 4.084190] ieee1394: Host added: ID:BUS[0-00:1023] GUID[00e0180000359142]
[ 4.085110] ieee1394: Node added: ID:BUS[0-01:1023] GUID[002011011501cd5f]
[ 25.735329] ieee1394: raw1394: /dev/raw1394 device initialized
dieter@dieter-ubuntu-ws-a7n8x:~$ lsmod | egrep 'ieee|fire'
ieee1394 86596 3 dv1394,raw1394,ohci1394
dieter@dieter-ubuntu-ws-a7n8x:~$ cat /etc/de
debconf.conf debian_version default/ defoma/ deluser.conf depmod.d/
dieter@dieter-ubuntu-ws-a7n8x:~$ cat /etc/debian_version
squeeze/sid

works like a charm. I'll do my DV work in kubuntu for now

funny · 2010-03-26 20:35:05

Hi,
I have a prablem with firewire too.
Dvgrab finds my caremra at firewire but when I start recording from one dvgrab has problems.

dvgrab /home/Data/Video/Magdalenka/m1
Found AV/C device with GUID 0x08004601040a7d03
Waiting for DV...
Capture Started

"/home/Data/Video/Magdalenka/m1001.dv": damaged frame near: timecode 00:00:00.24 date 2067.02.15 22:26:25
This means that there were missing or invalid FireWire packets.
^C"/home/Data/Video/Magdalenka/m1001.dv": 3.16 MiB 23 frames timecode 00:00:00.24 date 2067.02.15 22:26:25
Capture Stopped
Warning: 1 damaged frames.

lsmod:
lsmod
Module Size Used by
fuse 58757 2
ext2 62873 1
snd_seq_dummy 1439 0
firewire_ohci 23601 0
snd_seq_oss 29023 0
firewire_core 43019 1 firewire_ohci
snd_seq_midi_event 5316 1 snd_seq_oss
snd_intel8x0 26575 1
ohci_hcd 21485 0
crc_itu_t 1273 1 firewire_core
nvidia 8024326 24
snd_seq 50558 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 5181 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_ac97_codec 108885 1 snd_intel8x0
snd_pcm_oss 39011 0
snd_mixer_oss 17299 1 snd_pcm_oss
ac97_bus 1150 1 snd_ac97_codec
snd_pcm 70222 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
ppdev 5910 0
snd_timer 18799 2 snd_seq,snd_pcm
snd 57408 11 snd_seq_oss,snd_intel8x0,snd_seq,snd_seq_device,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
i2c_nforce2 5520 0
lp 8684 0
edac_core 34056 0
psmouse 57028 0
soundcore 6095 1 snd
parport_pc 31260 1
ehci_hcd 35082 0
shpchp 31012 0
k8temp 3379 0
evdev 8825 8
snd_page_alloc 7033 2 snd_intel8x0,snd_pcm
sg 25275 0
forcedeth 52476 0
serio_raw 4440 0
button 4714 0
processor 30310 0
thermal 11834 0
pcspkr 1795 0
edac_mce_amd 6785 0
parport 29923 3 ppdev,lp,parport_pc
pci_hotplug 26576 1 shpchp
i2c_core 18137 2 nvidia,i2c_nforce2
usbcore 140517 3 ohci_hcd,ehci_hcd
rtc_cmos 8904 0
rtc_core 14631 1 rtc_cmos
rtc_lib 1810 1 rtc_core
ext4 334960 2
mbcache 5466 2 ext2,ext4
jbd2 80162 1 ext4
crc16 1273 1 ext4
sr_mod 15043 0
cdrom 36354 1 sr_mod
sd_mod 26313 6
pata_acpi 3288 0
pata_amd 10948 0
ata_generic 3111 0
sata_nv 21639 4
floppy 55998 0
libata 152308 4 pata_acpi,pata_amd,ata_generic,sata_nv
scsi_mod 92676 4 sg,sr_mod,sd_mod,libata

lspci:
00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1)
00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1)
00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2)
00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1)
00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2)
00:09.0 IDE interface: nVidia Corporation nForce3 Serial ATA Controller 2 (rev a2)
00:0a.0 IDE interface: nVidia Corporation nForce3 Serial ATA Controller (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2)
00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV36 [GeForce FX 5700LE] (rev a1)
02:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 46)

I use 64bit archlinux (Gnome 2.28.2, core 2.6.32) @ AMD Athlon 64 Processor 2800+,
I have the same problem on 32bit Arch.

Do somebody help me?

Thanks

funny · 2010-04-13 07:15:29

Do you realy mean that no solution is on archlinux? I read that on ubuntu is this problem solved. But the same solution don't work on arch. I dont want use ubuntu, but I need process my video.

Dieter@be · 2010-04-18 15:51:01

funny wrote:

Do you realy mean that no solution is on archlinux? I read that on ubuntu is this problem solved. But the same solution don't work on arch. I dont want use ubuntu, but I need process my video.

that's right. i spent way too much time trying to fix this, eventually i gave up and used ubuntu.

Arch Linux

#1 2009-09-09 19:15:33

dvgrab: Error: no camera exists

#2 2009-09-26 07:38:43

Re: dvgrab: Error: no camera exists

#3 2009-10-14 17:16:04

Re: dvgrab: Error: no camera exists

#4 2009-10-14 19:39:18

Re: dvgrab: Error: no camera exists

#5 2009-10-14 20:39:41

Re: dvgrab: Error: no camera exists

#6 2009-11-14 09:44:50

Re: dvgrab: Error: no camera exists

#7 2009-11-16 04:37:33

Re: dvgrab: Error: no camera exists

#8 2009-11-26 04:11:18

Re: dvgrab: Error: no camera exists

#9 2009-12-08 21:36:09

Re: dvgrab: Error: no camera exists

#10 2010-01-09 18:10:48

Re: dvgrab: Error: no camera exists

#11 2010-01-10 15:08:37

Re: dvgrab: Error: no camera exists

#12 2010-03-26 20:35:05

Re: dvgrab: Error: no camera exists

#13 2010-04-13 07:15:29

Re: dvgrab: Error: no camera exists

#14 2010-04-18 15:51:01

Re: dvgrab: Error: no camera exists

Board footer