LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (http://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   /dev/raw1394 troubles (http://www.linuxquestions.org/questions/linux-hardware-18/dev-raw1394-troubles-275690/)

DaveQB 01-09-2005 09:19 AM

/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.


Code:

root@xpbeast linux-2.6.8.1-12mdk]# lspci | grep FireWire
00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE 1394) Controller (rev a3)

Here's my 1394 modules at default

Code:

[root@xpbeast linux-2.6.8.1-12mdk]# lsmod | grep 1394
ohci1394              30788  0
ieee1394              292056  1 ohci1394

I then issue a modprobe dv1394

Code:

[root@xpbeast linux-2.6.8.1-12mdk]# modprobe dv1394
[root@xpbeast linux-2.6.8.1-12mdk]# lsmod | grep 1394
dv1394                17196  0
ohci1394              30788  1 dv1394
ieee1394              292056  2 dv1394,ohci1394

And then ......

Code:

[root@xpbeast linux-2.6.8.1-12mdk]# modprobe raw1394
[root@xpbeast linux-2.6.8.1-12mdk]# lsmod | grep 1394
raw1394                24492  0
dv1394                17196  0
ohci1394              30788  1 dv1394
ieee1394              292056  3 raw1394,dv1394,ohci1394

Kino still reports nothing, even when launched as root.

So then ....

Code:

[root@xpbeast linux-2.6.8.1-12mdk]# ll /dev/ra
radio  ram10  ram14  ram4    ram8
radio0  ram11  ram15  ram5    ram9
ram0    ram12  ram2    ram6    random
ram1    ram13  ram3    ram7

So then i give this a try

Code:

[root@xpbeast linux-2.6.8.1-12mdk]# mknod -m 666 /dev/raw1394 c 171 0
Still no cigar.

:(

This is curious in my /var/log/messages

Code:

Jan  9 19:48:35 xpbeast rc.sysinit: Initializing firewire controller (ohci1394):  succe            eded
Jan  9 19:48:35 xpbeast ieee1394.agent[1403]: ... no drivers for IEEE1394 product 0x/0x            /0x
Jan  9 19:48:36 xpbeast ieee1394.agent[1599]: ... no drivers for IEEE1394 product 0x/0x            /0x
Jan  9 19:48:36 xpbeast ieee1394.agent[1590]: ... no drivers for IEEE1394 product 0x/0x


Any ideas guys ????? pleaseeeeee

jml75 01-09-2005 08:47 PM

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.

DaveQB 01-10-2005 03:01 PM

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 ??)

Code:

[root@xpbeast WildCard]# cp -rp /dev/raw1394 /etc/udev/devices/raw1394
cp: cannot create special file `/etc/udev/devices/raw1394': No such file or directory


Chhers for the reply.

DaveQB 01-11-2005 10:00 PM

Anyone ???? :cry:

:D

DaveQB 01-19-2005 07:25 AM

Anyone at all ???

iscurrah 01-22-2005 03:30 AM

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.)

ValidiusMaximus 01-22-2005 10:52 AM

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.

tachyonwill 01-22-2005 06:44 PM

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.

DaveQB 01-22-2005 07:12 PM

Quote:

Originally posted by iscurrah
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.)

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

Code:

Jan 22 20:37:21 xpbeast ieee1394.agent[1408]: ... no drivers for IEEE1394 product 0x/0x/0x
Jan 22 20:37:22 xpbeast ieee1394.agent[1595]: ... no drivers for IEEE1394 product 0x/0x/0x
Jan 22 20:37:22 xpbeast ieee1394.agent[1610]: ... no drivers for IEEE1394 product 0x/0x/0x
Jan 22 20:40:03 xpbeast kernel: ieee1394: raw1394: /dev/raw1394 device initialized

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
Quote:

devfsd in use!!!

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.

DaveQB 01-22-2005 07:21 PM

Quote:

Originally posted by tachyonwill
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.

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

ValidiusMaximus 01-22-2005 11:37 PM

Quote:

Originally posted by DaveQB
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.

iscurrah 01-25-2005 03:11 AM

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

Iain.

iscurrah 01-25-2005 03:17 AM

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.

DaveQB 01-25-2005 06:45 AM

Quote:

Originally posted by iscurrah
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.

iscurrah 01-25-2005 11:20 AM

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 :-(


All times are GMT -5. The time now is 11:09 AM.