Hi there, I'm trying to get a couple of webcams going in Linux. One is a firewire card and one is a USB. They are both loaded on my system and are partially usable (e.g. Firewire one works in Gnome Meeting). My question is how does /dev/video0 come into existence with video 4 linux (aka v4l)? I have tried using mknod and that can create it but it doesn't make it usable. I've hunted around the web heaps and not found much at all. Questions: - is there a magic step to create /dev/video0 automatically and I haven't set it up? - or is it that my drivers aren't really working well? Ian
On Wed, Sep 21, 2005 at 09:40:11AM +1200, Ian McDonald wrote:
Questions: - is there a magic step to create /dev/video0 automatically and I haven't set it up? - or is it that my drivers aren't really working well?
Assuming you are using a recent distro (ubuntu 5.04, debian sarge, etc) then this device file should be created by udev when the device is attached, either when the module is loaded or during boot if support is compiled statically into the kernel. My pci tv tuner card gets /dev/video0 on boot (I have the support compiled in) and my usb webcam gets /dev/video1 when I plug it in. The usb webcam gets /dev/video0 if it is plugged in on boot. I could fix this with a custom udev rule but I can't be bothered :p John
My pci tv tuner card gets /dev/video0 on boot (I have the support compiled in) and my usb webcam gets /dev/video1 when I plug it in. The usb webcam gets /dev/video0 if it is plugged in on boot. I could fix this with a custom udev rule but I can't be bothered :p
Thanks John - unfortunately that is what I suspected. I am running Sarge. They both have kernel modules that load but give limited functionality in other areas by the look of it. I think my alternatives now are to write a better driver or to buy a new webcam (unless anybody has some they don't want and can give away!) Ian
does anyone out there has a copy of the current version of FreeBSD. blank cds for exchange. thanks bo
Hi. A wee while back I was moving house. When it came time to move the computers I ran a few routine checks before closing down the machines to move them. My Debian server was running fsck when the power was pulled out (mad rush to clean up etc and the plug for the computer was pulled out instead of the one for the vacuum cleaner). So, that install was completely and utterly hosed. I tried for a few days to recover the entire thing, gave up, threw another drive in and hit it with Slackware (which I highly recommend btw). So now, I've still got the old drive with all the data on it. The drive originally had 4 partitions - 2x ext3, 1x ext2, 1x swap. I'd like to try and recover some of that data if possible (or more precisely Megan would like me to recover that data) so can anyone give me any advice?? I've tried all the usual things, using e2fsck, fsck with alternate/backup superblocks, gpart, e2salvage etc and haven't had any luck. Any advice would be appreciated Cheers. Shane.
participants (4)
-
Bo Wang -
Ian McDonald -
John R. McPherson -
Shane Taylor