On 22 January 2014 17:29, Robin wrote:
> Was working a couple of months ago, now it's not.
>
> Sid: 3.12-1-amd64 #1 SMP Debian 3.12.8-1 (2014-01-19) x86_64 GNU/Linux
> and 3.11-2 debian kernels
>
> ls /dev/video
> ls: cannot access /dev/video: No such file or director
Was working a couple of months ago, now it's not.
Sid: 3.12-1-amd64 #1 SMP Debian 3.12.8-1 (2014-01-19) x86_64 GNU/Linux
and 3.11-2 debian kernels
ls /dev/video
ls: cannot access /dev/video: No such file or directory
webcam logitech c920
lsusb
Bus 009 Device 009: ID 046d:082d Logitech, In
ny a few more times to see if this is now consistent regarding the
video devices.
>
> My experience with network cards was that the NAME assignments sometimes
> did not work reliably if I tried to use them to swap two existing
> (kernel) names (i.e. eth0 and eth1). If you have similar
to swap two existing
(kernel) names (i.e. eth0 and eth1). If you have similar problems then
it is probably best to replace the two NAME assignments in the rules by
two SYMLINK directives:
### START ###
SUBSYSTEM=="video4linux", \
ATTR{name}=="BT878 video _Hauppauge _bt878__"
On Wed, Aug 01, 2007 at 11:34:27 -0400, Douglas Allan Tutty wrote:
> On Tue, Jul 31, 2007 at 11:21:27PM +0200, Florian Kulzer wrote:
>
> > This flip-flopping is, AFAIK, more the fault of the newer kernel then
> > the fault of udev. If the kernel would always load the modules in the
> > same order
On Tue, Jul 31, 2007 at 11:21:27PM +0200, Florian Kulzer wrote:
> This flip-flopping is, AFAIK, more the fault of the newer kernel then
> the fault of udev. If the kernel would always load the modules in the
> same order then udev would probably assign the device nodes in a
> consistent manner.
On Tuesday 31 July 2007 23:21, Florian Kulzer wrote:
> On Tue, Jul 31, 2007 at 19:47:51 +0200, Nigel Henry wrote:
> > I've managed to resolve most of my problems on my own, but Udev has
> > beaten me.
> >
> > Sarge is not a problem, as it's using the 2.4.27, or 2.6.8 kernel, and
> > Udev is not in
On Tue, Jul 31, 2007 at 19:47:51 +0200, Nigel Henry wrote:
> I've managed to resolve most of my problems on my own, but Udev has beaten me.
>
> Sarge is not a problem, as it's using the 2.4.27, or 2.6.8 kernel, and Udev
> is
> not in the equation. Etch has a 2.6.8, and a 2.6.17 kernel, and Lenny
On 07/31/2007 12:47 PM, Nigel Henry wrote:
I've managed to resolve most of my problems on my own, but Udev has beaten me.
Sarge is not a problem, as it's using the 2.4.27, or 2.6.8 kernel, and Udev is
not in the equation. Etch has a 2.6.8, and a 2.6.17 kernel, and Lenny has a
2.6.11, and a 2.6
I've managed to resolve most of my problems on my own, but Udev has beaten me.
Sarge is not a problem, as it's using the 2.4.27, or 2.6.8 kernel, and Udev is
not in the equation. Etch has a 2.6.8, and a 2.6.17 kernel, and Lenny has a
2.6.11, and a 2.6.17 kernel. The problem is with the 2.6.17 ke
m the net says to compile a
certain driver against the kernel headers.
But there are no /dev/video* devices. I have put the
v4l module (videodev) using modconf. lsmod gives the
following list:
Module Size Used by
quickcam 91336 0
smbfs 55800 0
usb
-- "Edward Shornock (debian ml)"
<[EMAIL PROTECTED]> wrote:
> On Sun, Jul 16, 2006 at 02:33:46AM -0700, kruton
> wrote:
> > well, the initial goal was to get a webcam
> working.
> > doing some digging i see that there is no
> /dev/video..
> > so
>
On Sun, Jul 16, 2006 at 02:33:46AM -0700, kruton wrote:
> well, the initial goal was to get a webcam working.
> doing some digging i see that there is no /dev/video..
> so
>
> cd /dev; ./MAKEDEV video
>
> seemed like an option.. it said
>
> udev active, device
well, the initial goal was to get a webcam working.
doing some digging i see that there is no /dev/video..
so
cd /dev; ./MAKEDEV video
seemed like an option.. it said
udev active, devices will be created in
/dev/.static/dev/
what is this? how do i get v4l support into the
machine?
and
with+ATI+graphics+card%3F&_done=%2Fgroup%2Flinux.debian.user%2Fbrowse_frm%2Fthread%2F5c0e9592af19359b%2Fd713968e5b497630%3Fq%3DRe%3A+How+to+capture+video+with+ATI+graphics+card%3F%26rnum%3D1%26#doc_86d99632ff843e84
I have the km_drv and km_api_drv modules loaded but there is no /dev/video
Am I ba
Have you tried mknod
mknod /dev/video0 c 81 0
ln -s /dev/video0 /dev/video
see linuxusbguide.sourceforge.net and read the USB-guide for more information
Yes, thanks, this works (and don't forget
chgrp video /dev/video*
either.)
But I had thought that Debian was set
Have you tried mknod
mknod /dev/video0 c 81 0
ln -s /dev/video0 /dev/video
see linuxusbguide.sourceforge.net and read the USB-guide for more information
John Habermann
On Sat, 4 May 2002 09:11, David Wright wrote:
> I am running sid. I just plugged a Logitech Pro 3000 Quick
Try: 'insmode videodev'
Thanks for the tip, but videodev had already been loaded. MAKEDEV still
doesn't prduce a /dev/video. Do you have one?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
video0, which is what
> applications like gnomemeeting look for. If I
> # cd /dev
> # ./MAKEDEV -v update
> it says (after lots else)
> ./MAKEDEV: don't know what "tts" is
> ./MAKEDEV: don't know what "video_capture" is
> ./MAKEDEV: don
update
it says (after lots else)
./MAKEDEV: don't know what "tts" is
./MAKEDEV: don't know what "video_capture" is
./MAKEDEV: don't know what "drm" is
but doesn't generate any /dev/video entries. What do I need to do to get
video capt
m detected.
> Oct 3 16:11:37 eme_lap kernel: pwc Registered as /dev/video0.
>
> Which looks allright to me.
> Any attempts to access /dev/video or /dev/video0 result in:
>
> /dev/video: Operation not permitted
>
> Leaves me pretty clue less...
> Ann
.
Oct 3 16:11:37 eme_lap kernel: usb.c: registered new driver Philips webcam
Oct 3 16:11:37 eme_lap kernel: pwc Philips PCVC680K USB webcam detected.
Oct 3 16:11:37 eme_lap kernel: pwc Registered as /dev/video0.
Which looks allright to me.
Any attempts to access /dev/video or /dev/video0
sounds like the driver may not be loaded right.
havent been following the thread but what kind of device are you trying to
use on /dev/video and what drivers are loaded to use it ?
nate
On Tue, 3 Oct 2000, Erik van der Meulen wrote:
e.van. >On Tue, Oct 03, 2000 at 20:12:45 +0200, Jen
On Tue, Oct 03, 2000 at 20:12:45 +0200, Jens P. Elsner wrote:
> > lrwxrwxrwx1 root root6 Oct 3 17:19 /dev/video ->
> > video0
> >
> > Have I overlooked some obvious thing?
> Yes. /dev/video is a symlink. :)
>
> how about you set
> lrwxrwxrwx1 root root6 Oct 3 17:19 /dev/video ->
> video0
>
> Have I overlooked some obvious thing?
Yes. /dev/video is a symlink. :)
how about you set the right permissions on /dev/video0 ?
jp
. If I start:
xawtv -c /dev/video -geometry 352x288-0+0
I get:
This is xawtv-3.06, running on Linux/i686 (2.2.17)
visual: id=0x22 class=4 (TrueColor), depth=16
x11: 1024x768, 16 bit/pixel, 2048 byte/scanline, DGA, VidMode
can't open /dev/video: Operation not permitted
waitpid: No
* NatePuri <[EMAIL PROTECTED]> writes:
> can't open /dev/video: No such file or directory...
> no video grabber device available.
> When I did a ./MAKEDEV from /dev directory the proggy said
> ./MAKEDEV: don't know how to make device "vide
On Tue, 10 Aug 1999, NatePuri wrote:
> On Mon, Aug 09, 1999 at 10:19:40PM -0700, Syrus Nemat-Nasser wrote:
> > On Mon, 9 Aug 1999, NatePuri wrote:
> >
> > > On Tue, Aug 10, 1999 at 04:48:21AM +0200, Bernhard Rieder wrote:
> > > > ln -s /dev/video0 /dev/video
&
NatePuri wrote:
> Now the problem that I'm having now that it starts up, and I have
> edited the .xawtv file with my channels in it, I just get a blue screen
> and no video.
Looks like you selected a wrong input source.
Do You have a source= in your ~/.xawtv ?
-- ~/.xawtv ---
On Tue, Aug 10, 1999 at 12:09:55PM +0200, Bernhard Rieder wrote:
> NatePuri wrote:
> > > > I don't have /dev/video0 either.
> If you did already MAKEDEV video and it didn't work
> then you have to make your video device manually
>
> mknod /dev/video0 c 81 0
Ok, I did this...
> Also you should be
NatePuri wrote:
> > > I don't have /dev/video0 either.
If you did already MAKEDEV video and it didn't work
then you have to make your video device manually
mknod /dev/video0 c 81 0
Also you should be shure that the kernel loads
msp3400 and tuner. The depencies in the kernel
seem to be broken so t
On Mon, Aug 09, 1999 at 10:19:40PM -0700, Syrus Nemat-Nasser wrote:
> On Mon, 9 Aug 1999, NatePuri wrote:
>
> > On Tue, Aug 10, 1999 at 04:48:21AM +0200, Bernhard Rieder wrote:
> > > ln -s /dev/video0 /dev/video
> >
> > I don't have /dev/video0 either.
On Mon, 9 Aug 1999, NatePuri wrote:
> On Tue, Aug 10, 1999 at 04:48:21AM +0200, Bernhard Rieder wrote:
> > ln -s /dev/video0 /dev/video
>
> I don't have /dev/video0 either.
Did you compile your kernel with support for your video grabber
On Tue, Aug 10, 1999 at 04:48:21AM +0200, Bernhard Rieder wrote:
> ln -s /dev/video0 /dev/video
I don't have /dev/video0 either.
> --
>__ ___
> // )___--"""-.
> \ |,"( /`--"
NatePuri wrote:
>
> When I open xawtv from an xterm I get this error
>
> can't open /dev/video: No such file or directory...
> no video grabber device available.
>
> When I did a ./MAKEDEV from /dev directory the proggy said
> ./MAKEDEV:
When I open xawtv from an xterm I get this error
can't open /dev/video: No such file or directory...
no video grabber device available.
When I did a ./MAKEDEV from /dev directory the proggy said
./MAKEDEV: don't know how to make device "video".
Do I
36 matches
Mail list logo
