/dev/raw1394 troubles
 

The first time i hooked up my Camcorder and modprobed the appropriate devices it worked in Kino no problems. This was over 12mths ago and it has never worked since :(

I have started up my quest to get my camera working again.
I followed these 2 pages
http://www.jennings.homelinux.net/video_camera.html
https://bugzilla.redhat.com/bugzilla....cgi?id=133798

But no go for me.


Here's my 1394 modules at default

I then issue a modprobe dv1394

And then ......

Kino still reports nothing, even when launched as root.

So then ....

So then i give this a try

Still no cigar.

:(

This is curious in my /var/log/messages


Any ideas guys ????? pleaseeeeee

run ' mknod -m 666 /dev/raw1394 c 171 0 '
then ' copy -rp /dev/raw1394 /etc/udev/devices/raw1394 '
copying is required so it will always be restored on bootup.

Got that from an other tread, http://www.linuxquestions.org/questi...ht=.6+firewire

Try it, it will probably work for you.

hmmm ok, i am using udev now that i have upgraded to Mdk 10.1 so your suggestion did sound promising but .....

(i assumed you ment cp not copy ??)


Chhers for the reply.

Anyone ???? :cry:

:D

Anyone at all ???

Hiya,

What exactly isn't working ? Can you not start Kino ? Is it a Kino specific problem ? Can your OS see your camera when it's connected ?

You're using Mandrake 10.1 with it's 2.6 based kernel. This uses Udev which cannot automatically setup the correct devices /dev/raw1394. Have you tried using the 2.4 kernel that came with Mandrake 10.1 ? This might work for you straight away.

Give me some more information and I'll try to be more helpful.

Iain

(btw... I'm using Mdk 10.1. With my Sony handycam HC14E and the linux 2.6 kernel I can control the camera, but cannot receive any video. with the 2.4 kernel it all works fine.)

I have a similar problem. I have the raw1394 device but kino sez that it cant read or write to it (even as root). I have all those modules loaded for it.

I am on suse 9.2 and mandrake 10.1 and I have a very similar problem. Linux does not seem to want to work with the camcorder. Windows can work with it fine. I can tell that linux knows that the camcorder is there because when try to use gscanbus, if the camcorder is on I get the message in the console, " Error while reading from IEEE1394: : Resource temporarily unavailable ", but when it is off I get no such messages.

Firewire DV camera is not able to be used. Thats whats not working.

"Kino just says no A/V compliant camera detected, either not turned of or not plugged in."

I am getting these messages in my messages log file

Yet in the Mandrake Control Centre the firewire controller is being recognised and says its in working order using module ohci1394.

Its the onboard nForce2 firewire controller.

I can't recall what kernel i was using when it worked that once. May have well been 2.4 on MDK 9.2 not too sure. devfsd was what my system was using while i was on 10.0 mdk until i changed it myself. Kept getting that boot up mesage

I'll give 2.4 another go then, but would rather 2.6 to work to save rebooting. If i gotta reboot i may aswell go to Windows and do which is what i currently have to do.

gscanbus works for me, but doesnt show the camera there. Just has no deviced attached.

It shows it for me then freezes up about 2 seconds after it is finished detecting.

Hi, have you tried running gscanbus from a console within X ? You might get to see some error messages that'll help.

Iain.

DaveQB,

each time you reboot, do you re-create your /dev/raw1394 device ? Do you connect your camera after the boot sequence is complete (after the raw1394 device is created)? Have you tried downloading, compiling and installing the newest raw1394 library ?

Iain.

Yes to all of them except for the last one.

I believe from my checks i had the latest, but via an RPM.

Still the strange thing is, is that it did work once!! But months of re-trying and re-tracing my steps have been futile.

I'll have a hack at trying to install raw1394 from a tarball.

Hmmm,

I admit, I gave up. I installed Slackware 10 - the kernel 2.6.7 from testing, rebooted ... and exactly the same problem. Damn.

So I downloaded the latest stable kernel 2.6.10. Compiled and rebooted it. Same problem. Damn.

So I disabled the eth1394 driver. (IP Networking over Firewire). There were two options to do with this.

Compiled, rebooted and it worked !

So although I no longer have Mandrake installed, what I'd recommend you try is finding in /lib/modules/2.6.8mdk/kernel/drivers/ieee1394/
(or similar path) a file called eth1394.ko. Rename it or move it or something. Reboot and see if this helps.

If it doesn't, try recompiling the kernel, but disabling (don't allow it even as a module) anything to do with IP or networking over IEEE1394.

Below is the IEEE1394 section from my .config file. I think I have am extra line in here that the Mandrake kernal .config file will not have.

Lots of luck !

Iain.

# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=m

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y
# CONFIG_IEEE1394_CONFIG_ROM_IP1394 is not set

#
# Device Drivers
#
CONFIG_IEEE1394_PCILYNX=m
CONFIG_IEEE1394_OHCI1394=m

#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
CONFIG_IEEE1394_SBP2_PHYS_DMA=y
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
CONFIG_IEEE1394_AMDTP=m

PS. Now that it does work, it shows that my computer (Athlon 750MHz, 640Mb) is too slow to capture video via Kino :-(

thanx alot for your post iscurrah

I have disable the eth1394, but only while working on this problem and havent tried to stop it at boot.

Sounds like it could be a good idea.

I'll have a dabble on it. Havent had time to try the last posters idea yet ?? (bring on 40 hour days :D)

and by .config you mean kernel config file ??? in /boot ??

Hi,

if you've got the linux kernel source installed it should be in a directory /usr/src/linux-2.6.8mdk (I think).
There is a file in there called .config - generally don't edit this manually, use 'make menuconfig' instead.

Ever recompiled your kernel before ? If not, check on the net how to do it before starting ! It's not hard, but can easily leave you with a non-booting PC.

Good Luck !

Iain.

I spent 6 hours today setting up my Panasonic NV-GS400 digital video camera. Finally got it working! Your problem is very similar to mine...

I saw my camera deep in /sys/bus/ieee1394/. I saw the kernel recognize it in dmesg and in /var/log/messages. I wrote heaps of udev rules to try and have it make the appropriate devices... They've been commented out since I've got it working. But, each line represents a different try, and I did about 5 permutations of each line before writing a new one. With a reboot between each try, I was pulling my hair out.
I did more reading and it looks like udev and raw1394 are still at odds, Mandrake and Gentoo appear to be the first out of the gate with fixes. I'll have to wait a few years, heh heh.

So, I decided to bypass udev and make the devices myself. First I followed the advice from the source of all things linux and 1394. No luck with (for NTSC). Still got the raw1394 - failed to get handle: No such device errors.

So I looked into modules, how do you get information about them? Did that with the problem drivers, namely raw1394 and dv1394. This is what I got back:
AH! My system uses different minor numbers! (which makes sense since my ieee1394 wasn't set up according to linux1394 files/source - I bought my laptop from LAClinux, and they make custom-tailored kernels to your machine's specific hardware). Remove my bad devices and add some new ones as preferred by my drivers: Sweet. Fire up Kino, and now I can import DV and us the AV/C controls as well! がんばて！

PS: thanks to all you experts out there. I've been googling this forum for a while with weird quirks in my configuration and have always managed to find a solution. ほんとに ありがとう

I was excitted when i first read this, but unfortunately no go here :(


I still gotta try some of the other ideas posted, but time is short; i just want ther damn thing to work, save me booting into Windows just to transfer data from my camera.