You are not logged in.
Hi,
Begging for some help with a dv camcorder.
I have a PV-GS200 Panasonic Camcorder. The DV connection works in XP and in Ubuntu with the same PC, camera and cable. With Archlinux it fails. I have searched the forums and it seems that other people have gone through simular problems, none of the threads helped me to get this working. It must be a config issue or a difference in kernel / modules. Is there any clear documentation for setting up dv devices?
I have also tried this on 2 Archlinux i686 machines and both have the same problem. Here are some details.
The problem
dvgrab
Error: no camera exists
as root:
dvgrab
Error: no camera exists
kino reports
WARNING: raw1394 kernel module not loaded or failure to read/write /dev/raw1394
the same when run as root
in terminal it loops on:
iec61883Reader::StartThread on port 0
The config
tail -f /var/log/messages
Jun 30 16:23:05 egypt firewire_core: created device fw1: GUID 0080458051262199, S100
Jun 30 16:23:05 egypt firewire_core: phy config: card 0, new root=ffc1, gap_count=5
Jun 30 16:23:05 egypt ieee1394: raw1394: /dev/raw1394 device initialized
Jun 30 16:23:05 egypt NOTE: The dv1394 driver is unsupported and may be removed in a future Linux release. Use raw1394 instead.
lsmod |grep 1394
dv1394 17244 0
raw1394 24028 0
ohci1394 28720 1 dv1394
ieee1394 79288 3 dv1394,raw1394,ohci1394
ls -l /dev/raw1394
crw-rw---- 1 root video 171, 0 2008-06-30 16:23 /dev/raw1394
groups
lp wheel network video audio optical storage camera users
thanks for any suggestions
This is frustrating, I place a fresh install of debian etch on another partition on the same machine, add myself to the relevant group for raw1394 (disk in this case) and fire up kino, kdenlive or dvgrab and they all work out of the box. There must be something obviously wrong with either the way I have configured both my laptop and desktop to use archlinux or something is inherently wrong with archlinux and the way it sets up 1394 devices.
Last edited by alleyoopster (2008-07-08 07:24:34)
Offline
(dv1394 is not needed, firewire_ohci and firewire_core are in development and currently in conflict with current stable module ohci1394)
These modules need to be blacklisted in /etc/rc.conf
MOD_BLACKLIST=(dv1394 firewire_ohci firewire_core)raw1394 and ohci1394 are needed here (also /etc/rc.conf)
MODULES=(mii sis900 fuse nvidia w83627hf raw1394 ohci1394)This is the reply I got back from the linux1394 mailing list
You have both ohci1394 and firewire-ohci loaded. The latter is an alternative to ohci1394. (And firewire-core on top of it is an alternative to ieee1394 + raw1394 and video1394 and to some degree dv1394.) At some point in the future, firewire-ohci will certainly replace ohci1394 entirely, but at the moment the kernel sources contain both drivers so that people can choose between the future (but still buggy) drivers or the "legacy" stable drivers.
People should set up either their kernel configuration or their userspace configuration in a way that ensures that only the desired drivers are at work. You most certainly want only ohci1394 + ieee1394 + raw1394 for now.
If you configured the kernel yourself, simply switch off the new drivers in the kernel configurator and rebuild and reinstall and reload the modules.
If this is not self-built but from a kernel package,
- "modprobe -r firewire-ohci ohci1394 && modprobe ohci1394"
- blacklist or move or delete the new drivers (see links below) to
prevent that the problem reappears after the next reboot,
- report to the kernel packager that he needs to change the kernel
configuration or needs to provide a proper module blacklist.
The last step is important; please take the time for it.Some more info can be found in these texts:
wiki.linux1394.org/JujuMigration
http://git.kernel.org/?p=linux/kernel/g … re/Kconfig
--
Stefan Richter
I raised a bug for this. Bug #10858 http://bugs.archlinux.org/task/10858
Last edited by alleyoopster (2008-07-08 13:18:11)
Offline