IEEE 1394 Subsystem Not Responding
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
IEEE 1394 Subsystem Not Responding
Hey everybody,
This is my first post in the forums. I am new to Linux Mint and still pretty new to Linux generally, though I've played with it occasionally. I dumped Windows Vista this morning. So far I love Linux Mint 7 and I have all of my hardware working -- except for my video camera. It is a Sony HandyCam DCR HC-52. My system is a Dell Dimension XPS 720 that is a couple of years old.
I have tried Kino and Cinelerra so far. No luck importing video. Cinelerra tanks (locks up) when I try to record (I think I figured out how to do that!), and Kino complains about the IEEE 1394 subsystem not responding. So... how do I get Mint to activate that subsystem and then recognize my camera?
Just as an aside, Kino looks good. So does Cinelerra, but I feel in WAY over my head there! Any other software suggestions?
Thanks,
Jeff
This is my first post in the forums. I am new to Linux Mint and still pretty new to Linux generally, though I've played with it occasionally. I dumped Windows Vista this morning. So far I love Linux Mint 7 and I have all of my hardware working -- except for my video camera. It is a Sony HandyCam DCR HC-52. My system is a Dell Dimension XPS 720 that is a couple of years old.
I have tried Kino and Cinelerra so far. No luck importing video. Cinelerra tanks (locks up) when I try to record (I think I figured out how to do that!), and Kino complains about the IEEE 1394 subsystem not responding. So... how do I get Mint to activate that subsystem and then recognize my camera?
Just as an aside, Kino looks good. So does Cinelerra, but I feel in WAY over my head there! Any other software suggestions?
Thanks,
Jeff
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: IEEE 1394 Subsystem Not Responding
The firewire problem could be this (explanation and solution)
I could also be that the module is not loaded. What do you get from
You should find at least one module
I could also be that the module is not loaded. What do you get from
Code: Select all
lsmod | grep 1394
Re: IEEE 1394 Subsystem Not Responding
Husse,
I get the following error in Mint-7:
This command worked in Mint-5, not sure about Mint-6.
I have to start Kino from a term with "sudo kino" to be able to capture video from my camera.
Update: The error above occurred without my camera connected and powered on. After connecting and powering on the camera and issuing the command, it worked.
I get the following error in Mint-7:
Code: Select all
$ sudo chmod a+rw /dev/raw1394
[sudo] password for kevin:
chmod: cannot access `/dev/raw1394': No such file or directory
I have to start Kino from a term with "sudo kino" to be able to capture video from my camera.
Update: The error above occurred without my camera connected and powered on. After connecting and powering on the camera and issuing the command, it worked.
Re: IEEE 1394 Subsystem Not Responding
I got this from that command:Husse wrote:The firewire problem could be this (explanation and solution)
I could also be that the module is not loaded. What do you get fromYou should find at least one moduleCode: Select all
lsmod | grep 1394
No idea what any of that means!ohci1394 38576 0
ieee1394 94660 1 ohci1394
Haven't tried any solution to this issue yet. What do the results from that lsmod/grep command indicate?
Thanks much,
Jeff
Re: IEEE 1394 Subsystem Not Responding
Jeff you have the right modules loaded
lsmod is
ls list
mod modules (drivers) in the kernel
a very handy command if you want to see if you have the drivers loaded for your gadget
lsmod can of course be run without argument but you get a long list
lsmod is
ls list
mod modules (drivers) in the kernel
a very handy command if you want to see if you have the drivers loaded for your gadget
lsmod can of course be run without argument but you get a long list
Re: IEEE 1394 Subsystem Not Responding
Changing the file permissions worked! Whoo-hoo!!
Thanks very much for your help!
Thanks very much for your help!
Re: IEEE 1394 Subsystem Not Responding
Changing the file permissions fixes this problem, but it doesn't survive a reboot. Would it be possible to write a shell script to change the file permissions at boot time? If so, how would I go about doing that?
Thanks,
Jeff
Thanks,
Jeff
Re: IEEE 1394 Subsystem Not Responding
If you tell me what you did I might have a fixChanging the file permissions worked!
Re: IEEE 1394 Subsystem Not Responding
Hello Husse,Husse wrote:If you tell me what you did I might have a fixChanging the file permissions worked!
I followed the directions in this link:
http://adventuresinswitching.blogspot.c ... oaded.html
... which basically boils down to issuing this command in Terminal:
That fixes the problem I was having, but it doesn't survive a reboot. Is there a way to automate the change in file permissions at boot so I don't have to run that command in a terminal after every reboot?sudo chmod a+rw /dev/raw1394
Thanks,
Jeff
Re: IEEE 1394 Subsystem Not Responding
Piece of cake
Edit rc.local
Add the code snippet without sudo before exit 0
That's it
Edit rc.local
Code: Select all
gksu gedit /etc/rc.local
That's it
Re: IEEE 1394 Subsystem Not Responding
If you look at my last post you will find the solution to your problem and it will survive a reboot.
Re: IEEE 1394 Subsystem Not Responding
Ouch - there were two in this topic
Anyway with the camera connected.....
It's a bit odd to chmod at every boot but I suspected the device disappearing and reappearing would make it a new device each time - did not consider "error handling" though - what happens if the device is not there?
Anyway with the camera connected.....
It's a bit odd to chmod at every boot but I suspected the device disappearing and reappearing would make it a new device each time - did not consider "error handling" though - what happens if the device is not there?
Re: IEEE 1394 Subsystem Not Responding
Husse,
I believe I was wrong in my previous post about the permissions command surviving a reboot. The /dev/raw1394 device file does not remain after a reboot. It is created "on demand".
Do you think that if the file was manually created and given the correct permissions that this would correct this problem?
I believe I was wrong in my previous post about the permissions command surviving a reboot. The /dev/raw1394 device file does not remain after a reboot. It is created "on demand".
Do you think that if the file was manually created and given the correct permissions that this would correct this problem?
Re: IEEE 1394 Subsystem Not Responding
File - I thought it was a folder
It might work - but I'm not sure what will happen if the folder is there already when you insert a firewire device....
It might work - but I'm not sure what will happen if the folder is there already when you insert a firewire device....
Re: IEEE 1394 Subsystem Not Responding
It is a file in the /dev folder. I think this might be a bug because this problem was not present in Mint-5. You still had to issue the permissions command but the raw1394 file was a permanent fixture and would survive a reboot.
Re: IEEE 1394 Subsystem Not Responding
Damn - I must slow down - I know I must, but...
Of course it is a file - we are talking of the /dev folder - I was thinking of the /media folder
I must slow down I apologize ...
One possibility would be to use fstab to mount it, something like this
This is provided the filesystem is ext3 - if not change to the system used
Add to /etc/fstab as the last entry
With the user option anyone (the user) can mount it
Of course it is a file - we are talking of the /dev folder - I was thinking of the /media folder
I must slow down I apologize ...
One possibility would be to use fstab to mount it, something like this
Code: Select all
/dev/raw1394 /media/firewire ext3 user,noauto 0 0
Add to /etc/fstab as the last entry
Code: Select all
gksu gedit /etc/fstab