Video device assignment seems incorrect
 

I might be having some kind of a cross up in my 13.37 OS.
Here is what dmesg|egrep video gets:
Since my webcam (0c45:60fc) is V4L2 I presume that this means my webcam should be on /dev/video0.
When I run my mplayer command, I get numerous errors if I make /dev/video0 the assignment.
I currently am not using bttv so out of ignorance I made the assignment /dev/video1. The same command almost works. It takes a picture (at least an image file is produced), counts frames and decrements 1 less. However, there is NO monitor image and no image produced in the image file save a green background within a black frame. This assignment produces NO errors. This leads me to think that there could be a cross-up someplace.
I am wondering if there could be a crossed or partially crossed up assignment within the OS. I recall from 12.1 that the assigning of devices on bootup was problematic and at times it would be video0 and at others video1.
Is there someplace in /proc where I can see how it has video0/1 assigned to various products? Any help appreciated.
I am using the sn9c102 (sn9c105 included) driver but use of gspca_sonixj has same problem as I recall. Use of other cameras is not an option as it has been used with several scientific tools.

On my system

Video device assignment seems incorrect
 

Thanks, that mimics what is said by lsusb so that helps.
My quandary is still the difference I get between the lsusb and dmesg in the first post. I thought, possibly wrongly, that the 4-1 was "bus 4 device 1" was not agreeing with the lsusb output. And the fact that it tries to work under video1 and quits before getting anywhere under video0 as dmesg says is the device assignment.

For me, this command streams the camera output to the screen.
You could try installing guvcview from http://slackbuilds.org/ as it allows you to experiment with various camera settings. This may be required with your device.

Video device assignment seems incorrect
 

I appreciate suggesting alternative software but my needs are to use mplayer. I tried UR command and get:

With my system I see
I suspect a driver problem. In post #1
However I did find this concerning your device ID
http://lists.debian.org/debian-kerne.../msg00121.html

Video device assignment seems incorrect
 

Re: YUYV I had a recollection that I had had used that before but do not recall the outcome. Will test a bit later.
I had seen the reference already which is why I have tested it tho this camera has worked before with sn9c102 under 12.1.
With 12.1 I had had a problem where the camera and bttv would be assigned different videoX at different times which drove me crazy. I had resolved it in a script which checked /proc/asound/card but that output is different now and that particular condition does not seem to exist now. Hence why I was looking for info in /proc thinking something was possibly getting crossed up between lsusb and what was actually assigned. That was amplified when my script works with NO errors using the video no. assigned to bttv just that my camera is either not sensing the image or the image is somehow not getting thru as I get the on screen frame for video just a green background and no image and the assigned number for the camera was getting all errors.

Shall await the results of your testing trying the two different drivers.

Video device assignment seems incorrect
 

Sorry to be so tardy but ran into boot time "unable to enumerate" error caused by printer being in the ON state which lead to a long search. As it was USB related I had to run it to ground first.
Here is the state of the machine's testing:
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0c45:60fc Microdia PC Camera with Mic (SN9C105)

lsmod |grep sn9c
sn9c102 141903 0
videodev 57461 7 tuner,tvaudio,tda7432,msp3400,bttv,v4l2_common,sn9c102

dmesg| egrep video
[ 3.926718] Linux video capture interface: v2.00
[ 4.522586] usb 4-1: V4L2 device registered as video0
[ 5.966645] bttv0: registered device video1

Here is SN9C102 test (some lines trimmed for brevity):
FOR VIDEO1:
FOR VIDEO0:
Here is test for gspca_sonix:
modprobe -r sn9c102
modprobe gspca_sonixj
lsmod | egrep gspca
gspca_sonixj 22227 0
gspca_main 21348 1 gspca_sonixj
videodev 57461 7 gspca_main,tuner,tvaudio,tda7432,msp3400,bttv,v4l2_common
That was all that was changed

dmesg | egrep video
[ 3.926718] Linux video capture interface: v2.00
[ 4.522586] usb 4-1: V4L2 device registered as video0
[ 5.966645] bttv0: registered device video1
[ 2039.986198] usb 4-1: V4L2 device video0 deregistered *NOTE

FOR VIDEO1:
FOR VIDEO0:
Looks to me like it is using video1 (which it shouldn't) but cannot create an image as I get the "green" window inset which used to contain what the camera saw.
gspca_sonixj while available does not seem to work for video0 as it looks like that got deregistered (see *NOTE) when I pulled it in.

Have you tried using
From http://wigglit.ath.cx/slackware_botl....log.01Apr2010
This provides some background https://groups.google.com/forum/?fro...ia/aOoFlwE3Vfk

Video device assignment seems incorrect
 

The command: LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so mplayer -tv device=/dev/video0 tv://
(I think) is just assuring that a v4l to v4l2 conversion is available. The camera has run with just v4l2_common before so doubt the preload helps however when run with video0 now it gets same display as when run with video1 + a multicolored band across the top of the display about 10 pixels thick. So some improvement tho don't have an explanation of why video1 was trying to work and now video0 is trying to work with the preload. Need to look further into LD_PRELOAD's functionality.
Here are some of the errors video0 + preload gave:
tv.c: norm_from_string(pal): Bogus norm parameter, setting default.
v4l2: ioctl enum norm failed: Invalid argument
Error: Cannot set norm!
Selected input hasn't got a tuner!
v4l2: Cannot get fps
v4l2: ioctl set mute failed: Invalid argument
v4l2: ioctl query control failed: Invalid argument
tried command with video1 and got no errors plus it took a snapshot and created the .png file.
Wish I weren't so stubborn or I'd just buy another camera.

[QUOTE][v4l2: Cannot get fps/QUOTE]
I do not see this error although I see the four previous errors. Have you tried using the additional parameters in the quote in post #10?

U said U are getting some of the same errors. Is URs working?
Or are the errors non-impacting?
Scanned thru wiggleit and the googles stuff but must have missed what U refer to. Which params and which reference. I have tried so many combinations of parameters unsuccessfully that is why I am here. I did note that MLadden had the reverse of my videos, i.e. he had video0 for tv and video1 for camera which is the reverse of mine. That is the part that has my mind spinning because it seems to try to work with the video assigned to the tv but blows up when it uses the video assigned to the USB camera.
Here is my latest/greatest
vidv=video1
TV="-tv driver=v4l2:device=/dev/${vidv}:width=640:height=480:norm=NTSC:chanlist=us-cable:noaudio:outfmt=i420"
OUT="-fps 25 -cache 128"
PIC="-hue 0 -brightness 0 -contrast 0 -saturation 0 -aspect 4:3"LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so mplayer tv:// $TV $OUT $PIC -vf screenshot -vo xv,x11,
This was its environment:
lsmod | egrep v4l
v4l2_common 5259 5 tuner,tvaudio,tda7432,msp3400,bttv
videodev 57461 7 sn9c102,tuner,tvaudio,tda7432,msp3400,bttv,v4l2_common
v4l1_compat 13666 1 videodev
i2c_core 16421 14 tuner_simple,tuner,tvaudio,tda7432,msp3400,nouveau,drm_kms_helper,bttv,drm,v4l2_common,i2c_algo_bit, tveeprom,videodev,i2c_viapro
Is my understanding correct that the .../libv4l/v4l2convert.so is basically allowing v4l2 to run a v4l device? Or is it just degrading v4l2 to v4l?

Yes - As implied by post #4
LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so mplayer tv:// -tv \ driver=v4l2:width=640:height=480:fps=25:device=/dev/video1 -vo xv
From the link in post #10
I have also seen posts about this device needing a 32-bit library. Are you running 64-bit?

Regarding working or non-impacting errors query:
Was trying to determine if URs was working did U have errors or not so that I could expect same.

The command string: LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so mplayer tv:// -tv \ driver=v4l2:width=640:height=480:fps=25:device=/dev/video1 -vo xv
kind of works on this system. Using video1 it tries to employ the bttv which is NOT correct. Green screen in black frame with multicolored 1/4" band of pixels at the top
With video0 it is similar but adds a 3/4" band below of scattered I-bars on a green background which oscillates on/off. Just that suggests this is on the right track, just missing stuff or added too much.

I disregarded info on sn9c105 as the info I gathered said that that was included within sn9c102 at least for the 06fc camera.

I was not able to find a definition in the 2 refs U gave regarding the function of v4l2convert. That one where U found the command line was hard to follow when I looked for it. But for now I don't thing it matters.

Am using 32-bit desktop.

This is getting a bit long and I should now tear into this command via substitutions and see if I can make it work. Its good to know it is working 4 U.
I will open another if I can find no solution. I will come back if I have a solution for my configuration and post it.