since i have updated my system, i am unable to connect my dv-camcorder to my firewire-card.
when i power on my dv-camcorder dmesg says:
firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: created new fw device fw1 (0 config rom retries, S100) ieee1394: raw1394: /dev/raw1394 device initialized NOTE: The dv1394 driver is unsupported and may be removed in a future Linux rele ase. Use raw1394 instead. firewire_core: giving up on config rom for node id ffc1
If i then disconnect and reconnect it, dmesg says the following:
firewire_core: BM lock failed, making local node (ffc0) root. firewire_core: phy config: card 0, new root=ffc0, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: created new fw device fw1 (0 config rom retries, S100)
I have tried a canon mv700 as well as a canon xm1, both lead to the same problem. I have tried to connect my camcorder also to my notebook which also runs the latest version of arch, but leads to the same problem too.
I think there is a problem with the new kernel or something. Two weeks ago, before updating my system, everything works well.
Any suggestions or ideas?
Anyone with similar problems?
Last edited by smove (2008-05-06 19:32:14)
Same problem here.
I've been using Kino with my Panasonic PV-GS29 for quite some time until the most recent upgrade.
Everything seems fine, device /dev/raw1394 is created but no go beyond this point.
successfully got handle
current generation number: 0
0 card(s) found
Something must be broken in latest kernel I guess.
I solved this problem. Since kernel 2.6.22 there is a new firewire-stack available called 'juju'. Because of it´s experimental state it is not recommend to use it. In the current kernel-package the old and the new firewire-modules are included but the new instable ones are used by default. To fix the problem you have to blacklist the new firewire-modules.
Create the following file:
blacklist firewire-ohci blacklist firewire-sbp2
Reboot your system and try to use your firewire again. Look if the old modules are loaded instead of the new firewire-* ones. I dont understand why the new firewire-modules are used by default in the new kernel-packages. Refering to http://wiki.linux1394.org/JujuMigration … 857ee71b93 it is not recommended to use the new modules yet.
Thank you smove. Worked here too using your solution
Thanks, smove! That worked perfectly.
New firewire stack seems to work fine with latest 2.6.25 kernel, but I wasn't able to get nvidia drivers to compile with it so had to go back to 2.6.24.