Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just bought a FireWire card and installed IEEE1394, raw1394 and ohci1394. However, when I ran lspci my FireWire card didn't show up. What's up with that? I tried it in a few different pci slots and got nothing. Is there something I can do to make it show up?
I'm running Fedora Core 3 if that matters.
AFAIK lspci just reads the system bus and dumps out what it sees. This should be unrelated to any support, drivers or lack of them in Linux. So, if you plugged the card into the PCI bus and it didn't show up in lspci then your motherboard didn't recognize it. Have you made sure it is firmly seated? Does it have any status lights or anything else on it that would indicate that it powers up when you power up the computer? Can you see the BIOS POST messages on boot and do they show the firewire card? If the BIOS sees it but lspci does not then that is a stumper, but most likely if it's not in lspci then the BIOS can't see it either.
If it doesn't show up in lspci you can try a couple things. Triple check that it is fully seated in the PCI slot. Make sure there is no odd BIOS settings that would disable the PCI bus or a specific PCI slot. Return the card and tell them where you bought it that your computer's BIOS doesn't find it; Make them give you a new one to try, or your money back if a replacement doesn't work either.
P.S. I'm guessing you dont have Windows installed, or if you do it also doesn't recognize the card. Not that this matters much, but missing in lspci likely means Windows wouldn't find it either, in case you are thinking of installing that to see if it works.
Initially I managed to have my firewire port on my nforce2 board to work. It was with kernel 2.4.26.
To have it to work I had to install the libraw1394 and from the source directory run make dev. It created the device in /dev and started working in kino and others. Even after a reboot it stayed in /dev.
But now I installed a 2.6.10 kernel and tried the same but after reboot, the raw1394 device disapears from /dev.
So from I just read from you, can I run the mknod command that you listed above, copy the device in /etc/udev/devices/raw1394 and then it should work? Is that command good for any firewire controler? Or is it some details I should be aware of?
Also can you explain and detail the mknod command for me so I understand better what it means?
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 18.104.22.168, KDE 3.5.8 and KDE 4.0 beta, Plu
mknod is used to create device files. read the man files on it ' man mknod '. The one for the firewire is a standard one I use on mine with to problems so far. It was found on the internet somewhere. Since FC3 does a poor job of creating device files when needed, it needs to be created manually. Once created it can be add to the udev rules and it will be restored after a bootup. Same is needed to be done if using VmWare. That is in the release notes on FC3.
actually kernel did recognize my ieee1394 card but not with udev...i have tried to create my own udev rules (follow guide from gentoo linux website) but still not working....some how the raw1394 doesn't show up in /dev after i plug in the video cam
i just completed fresh install slack 10.1 with kernel 2.6.10 and i'll try it again...