Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
[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
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.
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
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.
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.
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.
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 ?
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.
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.