SlackwareThis Forum is for the discussion of Slackware 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.
I am trying to resolve video capture in Kino and I have found numerous posts in this forum covering this issue, but none that I can find that cover this problem.
The problem seems to be with raw1394. The output of dmesg | grep ieee 1394 is as follows:
As I was half into explaining, your problem could be with a) kernel drivers, b) udev or c) ~somewhere else~.
According to that thread, the problem is with udev not making the device nodes. Further down, they post this solution to making device nodes & permissions permanent:
You were definitly on the right track when you tried makedev, but wrong command!
Code:
#! /bin/sh
test -e /dev/raw1394 || mknod -m 666 /dev/raw1394 c 171 0
This will have to be adjusted to fit into Slack, but in principle if you get that script to run after you've loaded the raw1394 and video1394 modules everything says it should work =)
Good luck - let us know how it goes,
- Piete.
PS: Give me a bell on icq (2505906) or amsn (calinvenuma@hotmail.com) if you'd like to discuss this, or anything else!
Thank you very much for this solution. I tried the script you provided and it worked immediately. My question now is: is this permenant or do I have to install this script to my initd file so that it installs this node at each boot?
I am going to study this little script to understand exactly what it does (particularly the test -e.) I tried makedev because this is a command I am used to in Fedora Core because I have used it. Apparently, Slack does not have this command.
No worries Bob - easy when you know what to look for
I'll save you some trouble on the test -e thing ... from `man test` you'll find the following:
Code:
-e FILE
FILE exists
And from one of my favourite sources, the Advanced Bash-Scripting Guide (http://www.tldp.org/LDP/abs/html/ ) you'll find that || is infact ...the logical OR.
So:
if /dev/raw1394 is true OR if `mknod -m 666 /dev/raw1394 c 171 0` executes correctly then
This script has executed successfully.
Honestly, I'm not sure why they do that, I'd want something more "if doesn't exist / then make node / fi" .. but, hey, it works =)
Basically you now need to call this script (or more accurately,that line) every time you want to use the device node. I suspect there are a few clever ways to force it into the udev startup, however, I personally would add it to /etc/rc.d/rc.local (which is executed well after udev has finished messing around with /dev/). If you'd rather keep the script, then you can set up the start procedure in rc.local by doing something like:
Code:
if [ -x /etc/rc.d/rc.raw1394 ]; then
/etc/rc.d/rc.raw1394
fi
Then you can turn on/off the executable flag, just like every other /etc/rc.d/ script =)
Thanks, piete...this post was worth a month worth of learning. It all makes sense now. Video capturing is available to me now. I am studying scripting now (still early stages), but this goes a long way toward understanding startup scripts better. I do use "Linux in a Nutshell" book for studying commands I read in this forum to understand how they work and what they do, but it is a little dim sometimes and one on one explanations are a lot clearer.
Thanks again,
Bob
BTW, great town, Canterbury, one of the first towns I visited here. I live in Southampton.
if /dev/raw1394 is true OR if `mknod -m 666 /dev/raw1394 c 171 0` executes correctly then
This script has executed successfully.
Honestly, I'm not sure why they do that, I'd want something more "if doesn't exist / then make node / fi" .. but, hey, it works =)
The OR and AND operators make use of something called short circuiting. It goes like this: What is 1 OR x? 1. It doesn't matter what x is, so x never gets evaluated. The only time x gets evaluated is when the first half evaluates to false.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.