Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #187025 > unrolled thread

Video input vs. systemctl enable.

Started bypeter@easthope.ca
First post2017-09-19 20:50 +0200
Last post2017-10-02 02:10 +0200
Articles 20 — 5 participants

Back to article view | Back to linux.debian.user

Contents

  Video input vs. systemctl enable. peter@easthope.ca - 2017-09-19 20:50 +0200
    Re: Video input vs. systemctl enable. Reco <recoverym4n@gmail.com> - 2017-09-19 22:20 +0200
      Re: Video input vs. systemctl enable. peter@easthope.ca - 2017-09-20 00:50 +0200
        Re: Video input vs. systemctl enable. Reco <recoverym4n@gmail.com> - 2017-09-20 08:30 +0200
          USB camera; was Re: Video input vs. systemctl enable. peter@easthope.ca - 2017-09-20 15:40 +0200
            Re: USB camera; was Re: Video input vs. systemctl enable. Reco <recoverym4n@gmail.com> - 2017-09-20 16:10 +0200
              Re: Video input vs. systemctl enable. peter@easthope.ca - 2017-09-20 19:00 +0200
              Re: USB camera;  peter@easthope.ca - 2017-09-21 00:40 +0200
                Re: USB camera; Reco <recoverym4n@gmail.com> - 2017-09-21 13:20 +0200
                  Re: USB camera; peter@easthope.ca - 2017-10-02 02:00 +0200
                    Re: USB camera; Reco <recoverym4n@gmail.com> - 2017-10-02 09:20 +0200
                      Re: USB camera; Reco <recoverym4n@gmail.com> - 2017-10-02 23:20 +0200
                        Re: USB camera; peter@easthope.ca - 2017-11-03 15:40 +0100
                          Re: USB camera; Reco <recoverym4n@gmail.com> - 2017-11-03 16:20 +0100
                            Re: USB camera. peter@easthope.ca - 2017-12-07 05:30 +0100
                          Re: USB camera; deloptes <deloptes@gmail.com> - 2017-11-03 18:10 +0100
                      Re: USB camera; peter@easthope.ca - 2017-10-02 23:50 +0200
              Re: USB camera; was Re: Video input vs. systemctl enable. Curt <curty@free.fr> - 2017-09-21 15:30 +0200
                Re: USB camera; was Re: Video input vs. systemctl enable. anonymous <recoverym4n@gmail.com> - 2017-09-21 18:30 +0200
                Re: USB camera. peter@easthope.ca - 2017-10-02 02:10 +0200

#187025 — Video input vs. systemctl enable.

Frompeter@easthope.ca
Date2017-09-19 20:50 +0200
SubjectVideo input vs. systemctl enable.
Message-ID<urvKQ-xs-55@gated-at.bofh.it>
Hi again,

After upgrade to stretch, "systemctl enable shorewall" 
was necessary to allow shorewall to start automatically.
https://wiki.debian.org/HowTo/shorewall

With a USB camera and a Hauppauge frame-grabber installed, this 
stretch system has no /dev/video*.  Is a "systemctl enable ..." 
required for video input?  

peter@dalton:~$ uname -a
Linux dalton 4.9.0-3-686-pae #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06) i686 GNU
/Linux
peter@dalton:~$ ls -ld /dev/v*
crw-rw---- 1 root tty   7,   0 Sep 19 05:26 /dev/vcs
crw-rw---- 1 root tty   7,   1 Sep 19 05:26 /dev/vcs1
crw-rw---- 1 root tty   7,   2 Sep 19 05:26 /dev/vcs2
crw-rw---- 1 root tty   7,   3 Sep 19 05:26 /dev/vcs3
crw-rw---- 1 root tty   7,   4 Sep 19 05:26 /dev/vcs4
crw-rw---- 1 root tty   7,   5 Sep 19 05:26 /dev/vcs5
crw-rw---- 1 root tty   7,   6 Sep 19 05:26 /dev/vcs6
crw-rw---- 1 root tty   7,   7 Sep 19 05:26 /dev/vcs7
crw-rw---- 1 root tty   7, 128 Sep 19 05:26 /dev/vcsa
crw-rw---- 1 root tty   7, 129 Sep 19 05:26 /dev/vcsa1
crw-rw---- 1 root tty   7, 130 Sep 19 05:26 /dev/vcsa2
crw-rw---- 1 root tty   7, 131 Sep 19 05:26 /dev/vcsa3
crw-rw---- 1 root tty   7, 132 Sep 19 05:26 /dev/vcsa4
crw-rw---- 1 root tty   7, 133 Sep 19 05:26 /dev/vcsa5
crw-rw---- 1 root tty   7, 134 Sep 19 05:26 /dev/vcsa6
crw-rw---- 1 root tty   7, 135 Sep 19 05:26 /dev/vcsa7
crw------- 1 root root 10,  63 Sep 19 05:26 /dev/vga_arbiter
crw------- 1 root root 10, 137 Sep 19 05:26 /dev/vhci
crw------- 1 root root 10, 238 Sep 19 05:26 /dev/vhost-net

Any other ideas?

Thanks,                ... Peter E.




-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                      Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

[toc] | [next] | [standalone]

#187032

FromReco <recoverym4n@gmail.com>
Date2017-09-19 22:20 +0200
Message-ID<urx9U-1zx-21@gated-at.bofh.it>
In reply to#187025
	Hi.

On Tue, Sep 19, 2017 at 11:09:01AM -0700, peter@easthope.ca wrote:
> Hi again,
> 
> After upgrade to stretch, "systemctl enable shorewall" 
> was necessary to allow shorewall to start automatically.
> https://wiki.debian.org/HowTo/shorewall

True.


> With a USB camera and a Hauppauge frame-grabber installed, this 
> stretch system has no /dev/video*.  Is a "systemctl enable ..." 
> required for video input?  

That's highly unlikely. What's really required is to load appropriate
kernel modules. For USB cameras it's uvcvideo usually.

Reco

[toc] | [prev] | [next] | [standalone]

#187043

Frompeter@easthope.ca
Date2017-09-20 00:50 +0200
Message-ID<urzv3-2VK-5@gated-at.bofh.it>
In reply to#187032
*	From: Reco <recoverym4n@gmail.com>
*	Date: Tue, 19 Sep 2017 23:16:15 +0300
> ... load appropriate kernel modules. For USB cameras it's uvcvideo usually.

peter@dalton:~$ lsmod | grep uvc
peter@dalton:~$

Indeed; not loaded as a module.   With several camera related packages 
installed, no dependancy caught it.  Googling 
"site:packages.debian.org uvc driver" returns only packages for 
uvccapture and guvcview on the first page. There is no uvcvideo 
package.   From jessie to stretch, was the driver renamed or 
repackaged?  Wherever it is, it's hidden well.

Thanks,            ... P.



  

-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                      Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#187050

FromReco <recoverym4n@gmail.com>
Date2017-09-20 08:30 +0200
Message-ID<urGGd-7Hy-5@gated-at.bofh.it>
In reply to#187043
On Tue, Sep 19, 2017 at 03:01:03PM -0700, peter@easthope.ca wrote:
> *	From: Reco <recoverym4n@gmail.com>
> *	Date: Tue, 19 Sep 2017 23:16:15 +0300
> > ... load appropriate kernel modules. For USB cameras it's uvcvideo usually.
> 
> peter@dalton:~$ lsmod | grep uvc
> peter@dalton:~$
> 
> Indeed; not loaded as a module.   With several camera related packages 
> installed, no dependancy caught it.  Googling 
> "site:packages.debian.org uvc driver" returns only packages for 
> uvccapture and guvcview on the first page. There is no uvcvideo 
> package.   From jessie to stretch, was the driver renamed or 
> repackaged?  Wherever it is, it's hidden well.

No, it was not renamed. In fact I'm not even sure that it's uvcvideo
kernel module that you need. udev should load modules such as this
without human intervention.

What does 'lsusb' and 'lsusb -t' show for you?

Reco

[toc] | [prev] | [next] | [standalone]

#187059 — USB camera; was Re: Video input vs. systemctl enable.

Frompeter@easthope.ca
Date2017-09-20 15:40 +0200
SubjectUSB camera; was Re: Video input vs. systemctl enable.
Message-ID<urNom-3GY-15@gated-at.bofh.it>
In reply to#187050
*	From: Reco <recoverym4n@gmail.com>
*	Date: Wed, 20 Sep 2017 09:20:18 +0300
> What does 'lsusb' and 'lsusb -t' show for you?

peter@dalton:~$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0bda:0326 Realtek Semiconductor Corp. 
Bus 001 Device 006: ID 045e:00f8 Microsoft Corp. LifeCam NX-6000
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 050d:0121 Belkin Components F5D5050 100Mbps Ethernet
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0d8c:0008 C-Media Electronics, Inc. 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
peter@dalton:~$ lsusb -t
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/3p, 12M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M
    |__ Port 1: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 1: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 1: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 1: Dev 2, If 3, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/3p, 12M
    |__ Port 1: Dev 2, If 0, Class=(Defined at Interface level), Driver=pegasus, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/3p, 12M
    |__ Port 2: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 2: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 2: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 2: Dev 2, If 3, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M
    |__ Port 5: Dev 6, If 0, Class=Video, Driver=, 480M
    |__ Port 5: Dev 6, If 1, Class=Video, Driver=, 480M
    |__ Port 5: Dev 6, If 2, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 5: Dev 6, If 3, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 8: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 480M
peter@dalton:~$ ls -ld /dev/v*
crw-rw---- 1 root tty   7,   0 Sep 20 05:00 /dev/vcs
crw-rw---- 1 root tty   7,   1 Sep 20 05:00 /dev/vcs1
crw-rw---- 1 root tty   7,   2 Sep 20 05:00 /dev/vcs2
crw-rw---- 1 root tty   7,   3 Sep 20 05:00 /dev/vcs3
crw-rw---- 1 root tty   7,   4 Sep 20 05:00 /dev/vcs4
crw-rw---- 1 root tty   7,   5 Sep 20 05:00 /dev/vcs5
crw-rw---- 1 root tty   7,   6 Sep 20 05:00 /dev/vcs6
crw-rw---- 1 root tty   7,   7 Sep 20 05:01 /dev/vcs7
crw-rw---- 1 root tty   7, 128 Sep 20 05:00 /dev/vcsa
crw-rw---- 1 root tty   7, 129 Sep 20 05:00 /dev/vcsa1
crw-rw---- 1 root tty   7, 130 Sep 20 05:00 /dev/vcsa2
crw-rw---- 1 root tty   7, 131 Sep 20 05:00 /dev/vcsa3
crw-rw---- 1 root tty   7, 132 Sep 20 05:00 /dev/vcsa4
crw-rw---- 1 root tty   7, 133 Sep 20 05:00 /dev/vcsa5
crw-rw---- 1 root tty   7, 134 Sep 20 05:00 /dev/vcsa6
crw-rw---- 1 root tty   7, 135 Sep 20 05:01 /dev/vcsa7
crw------- 1 root root 10,  63 Sep 20 05:00 /dev/vga_arbiter
crw------- 1 root root 10, 137 Sep 20 05:00 /dev/vhci
crw------- 1 root root 10, 238 Sep 20 05:00 /dev/vhost-net

Sure enough, lsusb -t shows no driver for bus 1, device 6.  
What do others find for a usb camera in stretch?

Thanks,        ... Peter E.

-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                      Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#187062 — Re: USB camera; was Re: Video input vs. systemctl enable.

FromReco <recoverym4n@gmail.com>
Date2017-09-20 16:10 +0200
SubjectRe: USB camera; was Re: Video input vs. systemctl enable.
Message-ID<urNRo-47n-19@gated-at.bofh.it>
In reply to#187059
	Hi.

On Wed, Sep 20, 2017 at 05:56:22AM -0700, peter@easthope.ca wrote:
> *	From: Reco <recoverym4n@gmail.com>
> *	Date: Wed, 20 Sep 2017 09:20:18 +0300
> > What does 'lsusb' and 'lsusb -t' show for you?
> 
> peter@dalton:~$ lsusb
> Bus 001 Device 006: ID 045e:00f8 Microsoft Corp. LifeCam NX-6000

I got that feeling that things won't be easy, but M$ webcam put this
right into 'hardcore entertainment' category. Marked AO for Adult Only.
Viewer discretion is advised.


> Sure enough, lsusb -t shows no driver for bus 1, device 6.  

And that means it's time to try a magic trick. You need to be root, or
it won't work.

modprobe uvcvideo

echo 045e 00f8 > /sys/module/uvcvideo/drivers/usb\:uvcvideo/new_id

ls -al /dev/video*

Known side effect can include (but not limited to):

- dizziness
- webcam explosions
- kernel panics
- frozen food disappearance

The reason for this is [1]. If the link is to be believed - USB device
with ID 045e:00f8 should be supported by uvcvideo (an in-tree kernel
module). If you're lucky, the only thing that's missing there is a
declaration for aforementioned USB ID.

If the trick does not work I suggest to try the kernel from the
backports.

Reco

[1] https://wiki.debian.org/DeviceDatabase/USB

[toc] | [prev] | [next] | [standalone]

#187067

Frompeter@easthope.ca
Date2017-09-20 19:00 +0200
Message-ID<urQvT-5Dp-15@gated-at.bofh.it>
In reply to#187062
*	From: Reco <recoverym4n@gmail.com>
*	Date: Wed, 20 Sep 2017 17:03:39 +0300
> modprobe uvcvideo
> 
> echo 045e 00f8 > /sys/module/uvcvideo/drivers/usb\:uvcvideo/new_id
> 
> ls -al /dev/video*

root@dalton:/sys/module/uvcvideo/drivers/usb:uvcvideo# echo 045e 00f8 > new_id
root@dalton:/sys/module/uvcvideo/drivers/usb:uvcvideo# cat new_id               
045e 00f8

So far, so good.

root@dalton:/sys/module/uvcvideo/drivers/usb:uvcvideo# ls -al /dev/video*
ls: cannot access '/dev/video*': No such file or directory

Lady Luck definitely not happy today.  =8~(

> If the trick does not work I suggest to try the kernel from the
> backports.

OK, thanks. 

Oddly enough, this camera worked up to a year or two back.  
I don't remember the specifics but afraid that a backport kernel 
will be no better.  Might return to the original problem--troubleshooting 
the Hauppauge WinTV card.  And a bug report might be needed.

Thanks for the patient help,        ... P.

-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                      Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#187068 — Re: USB camera;

Frompeter@easthope.ca
Date2017-09-21 00:40 +0200
SubjectRe: USB camera;
Message-ID<urVOW-J7-7@gated-at.bofh.it>
In reply to#187062
*	From: Reco <recoverym4n@gmail.com>
*	Date: Wed, 20 Sep 2017 17:03:39 +0300
> If the trick does not work I suggest to try the kernel from the
> backports.

Began to create a bug report and found this.
"Your version of linux-image-4.9.0-3-686-pae (4.9.30-2+deb9u3) is newer than 
that in Debian! Do you still want to file a report [y|N|q|?]?"

Why isn't it a plain old stock kernel?  Upgraded to stretch and 
nothing unusual about apt usage here.

peter@dalton:~$ cat /etc/apt/sources.list
# dalton:/etc/apt/sources.list

# mirror.it.ubc.ca = 137.82.116.42
deb     http://137.82.116.42/debian/  stretch main contrib non-free
deb-src http://137.82.116.42/debian/  stretch main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free

# debian.oregonstate.edu = 140.211.166.134
deb     http://140.211.166.134/debian/  stretch main contrib non-free
deb-src http://140.211.166.134/debian/  stretch main contrib non-free

Should I try reverting to a contemporary (older?) kernel?

Thanks,                ... Peter E.


-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                      Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#187074 — Re: USB camera;

FromReco <recoverym4n@gmail.com>
Date2017-09-21 13:20 +0200
SubjectRe: USB camera;
Message-ID<us7Gq-gp-19@gated-at.bofh.it>
In reply to#187068
	Hi.

On Wed, Sep 20, 2017 at 02:49:21PM -0700, peter@easthope.ca wrote:
> *	From: Reco <recoverym4n@gmail.com>
> *	Date: Wed, 20 Sep 2017 17:03:39 +0300
> > If the trick does not work I suggest to try the kernel from the
> > backports.
> 
> Began to create a bug report and found this.
> "Your version of linux-image-4.9.0-3-686-pae (4.9.30-2+deb9u3) is newer than 
> that in Debian! Do you still want to file a report [y|N|q|?]?"
> 
> Why isn't it a plain old stock kernel?  Upgraded to stretch and 
> nothing unusual about apt usage here.

reportbug is teasing you.
Today's kernel update bumped the kernel to 4.9.30-2+deb9u5.
Update the kernel, disregard reportbug warning and file a bugreport.

Reco

[toc] | [prev] | [next] | [standalone]

#187464 — Re: USB camera;

Frompeter@easthope.ca
Date2017-10-02 02:00 +0200
SubjectRe: USB camera;
Message-ID<uvWjo-8sG-9@gated-at.bofh.it>
In reply to#187074
*	From: Reco <recoverym4n@gmail.com>
*	Date: Thu, 21 Sep 2017 14:10:35 +0300
> reportbug is teasing you.
> Today's kernel update bumped the kernel to 4.9.30-2+deb9u5.
> Update the kernel, disregard reportbug warning and file a bugreport.

Now I have the kernel you mention and a /dev/video0.  A little 
progress but still no image. 
"GUVCVIEW: no valid file extension for image file"
A file name problem?  Any simple fix for that?
Any further comments before I make a bug report?

Thanks,              ... Peter E.

peter@dalton:~$ dpkg -l | grep linux-image
ii  linux-image-4.9.0-3-686-pae         4.9.30-2+deb9u5                    i386
        Linux 4.9 for modern PCs
peter@dalton:~$ ls /dev/video*
/dev/video0
peter@dalton:~$ guvcview /dev/video0
GUVCVIEW: version 2.0.4
GUVCVIEW: (config) skiping invalid entry at line 8 ('format', 'MJPG')
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (VIDIOC_G_EXT_CTRLS) failed
V4L2_CORE: using VIDIOC_G_CTRL for user class controls
V4L2_CORE: (VIDIOC_G_EXT_CTRLS) failed
V4L2_CORE: using VIDIOC_G_EXT_CTRLS on single controls for class: 0x009a0000
V4L2_CORE: control id: 0x009a0908 failed to get (error -1)
V4L2_CORE: control id: 0x009a0909 failed to get (error -1)
V4L2_CORE: control id: 0x009a090d failed to get (error -1)
GUVCVIEW: no valid file extension for image file 
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
V4L2_CORE: (VIDIOC_S_FORMAT) Unable to set format: Input/output error
GUCVIEW: could not set the defined stream format
GUCVIEW: trying first listed stream format
V4L2_CORE: (VIDIOC_S_FORMAT) Unable to set format: Input/output error
GUCVIEW: also could not set the first listed stream format
GUVCVIEW: Video capture failed
GUVCVIEW (1): Guvcview error
	 could not start a video stream in the device

(guvcview:14881): Gtk-WARNING **: Theme parsing error: <data>:1:17: not a number

(guvcview:14881): Gtk-WARNING **: Theme parsing error: <data>:1:31: Using Pango syntax for the font: style property is deprecated; please use CSS syntax

(guvcview:14881): Gtk-WARNING **: Theme parsing error: <data>:1:17: not a number

(guvcview:14881): Gtk-WARNING **: Theme parsing error: <data>:1:32: Using Pango syntax for the font: style property is deprecated; please use CSS syntax

(guvcview:14881): Gtk-WARNING **: Theme parsing error: <data>:1:17: not a number

(guvcview:14881): Gtk-WARNING **: Theme parsing error: <data>:1:26: Using Pango syntax for the font: style property is deprecated; please use CSS syntax
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
V4L2_CORE: (VIDIOC_S_PARM) error: Device or resource busy
V4L2_CORE: Unable to set 1/30 fps
Terminated
peter@dalton:~$ 

-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                      Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#187473 — Re: USB camera;

FromReco <recoverym4n@gmail.com>
Date2017-10-02 09:20 +0200
SubjectRe: USB camera;
Message-ID<uw3bb-4nm-5@gated-at.bofh.it>
In reply to#187464
On Sun, Oct 01, 2017 at 04:12:19PM -0700, peter@easthope.ca wrote:
> *	From: Reco <recoverym4n@gmail.com>
> *	Date: Thu, 21 Sep 2017 14:10:35 +0300
> > reportbug is teasing you.
> > Today's kernel update bumped the kernel to 4.9.30-2+deb9u5.
> > Update the kernel, disregard reportbug warning and file a bugreport.
> 
> Now I have the kernel you mention and a /dev/video0.  A little 
> progress but still no image. 
> "GUVCVIEW: no valid file extension for image file"
> A file name problem?  Any simple fix for that?
> Any further comments before I make a bug report?

Try (assuming that you have appropriate device permissions):

mpv tv:// --tv-device=/dev/video0

This guvcview you're using is unable to identify video format that's
coming from your webcam:

> GUCVIEW: could not set the defined stream format

Reco

[toc] | [prev] | [next] | [standalone]

#187503 — Re: USB camera;

FromReco <recoverym4n@gmail.com>
Date2017-10-02 23:20 +0200
SubjectRe: USB camera;
Message-ID<uwgia-Zh-89@gated-at.bofh.it>
In reply to#187473
	Hi.

On Mon, Oct 02, 2017 at 07:28:58AM -0700, peter@easthope.ca wrote:
> From: Reco <recoverym4n@gmail.com>
> Date: Mon, 2 Oct 2017 10:16:20 +0300
> > Try (assuming that you have appropriate device permissions):
> > 
> > mpv tv:// --tv-device=/dev/video0
> 
> peter@dalton:~$ mpv tv:// --tv-device=/dev/video0
> Playing: tv://
> [tv] Selected driver: v4l2
> [tv]  name: Video 4 Linux 2 input
> [tv] your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM was used instead.
> [tv] Selected device: Microsoft® LifeCam NX-6000
> [tv]  Capabilities:  video capture  read/write  streaming
> [tv]  supported norms:
> [tv]  inputs: 0 = Camera 1;
> [tv]  Current input: 0
> [tv]  Current format: MJPEG
> [tv] ioctl set format failed: Input/output error
> [tv] ioctl set mute failed: Invalid argument
> [tv] 0 frames successfully processed, 0 frames dropped.
> Failed to recognize file format.
> 
> Exiting... (Errors when loading file)
> peter@dalton:~$ 
> 
> "Failed to recognize file format." is reminiscent of the problem with 
> guvcview; but MJPEG is no exotic format.  A small idiosyncracy in the 
> camera output is not recognized by the Linux softwares?  Most such 
> bugs would have been fixed years ago.

And that's where my ideas come to an end. The best I can come up with
is:

EIO as a result of ioctl(2) is most certainly undocumented (and highly
unusual) and therefore should be specific to particular kernel module.

I suggest you to file a bug report unless you did it already.

Reco

[toc] | [prev] | [next] | [standalone]

#188554 — Re: USB camera;

Frompeter@easthope.ca
Date2017-11-03 15:40 +0100
SubjectRe: USB camera;
Message-ID<uHLix-5g0-3@gated-at.bofh.it>
In reply to#187503
*	From: Reco <recoverym4n@gmail.com>
*	Date: Mon, 2 Oct 2017 18:50:58 +0300
> I suggest you to file a bug report unless you did it already.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877558

A Labtec/Vivitar camera has a similar failure. Is any USB camera 
working in Debian 9?  

Many packages in 9 are being updated.  Maintainers must be swamped.  
I can be patient until commotion subsides.

Thanks for the help,                    ... Peter E.


-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                      Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#188555 — Re: USB camera;

FromReco <recoverym4n@gmail.com>
Date2017-11-03 16:20 +0100
SubjectRe: USB camera;
Message-ID<uHLVf-5HS-1@gated-at.bofh.it>
In reply to#188554
On Fri, Nov 03, 2017 at 06:54:29AM -0700, peter@easthope.ca wrote:
> *	From: Reco <recoverym4n@gmail.com>
> *	Date: Mon, 2 Oct 2017 18:50:58 +0300
> > I suggest you to file a bug report unless you did it already.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877558
> 
> A Labtec/Vivitar camera has a similar failure. Is any USB camera 
> working in Debian 9?  

This one does, at least right now it did with mpv.
lsusb tells me that it's:

058f:5608 Alcor Micro Corp

Got this one built into a laptop so I doubt it can be purchased separately.

Reco

[toc] | [prev] | [next] | [standalone]

#189628 — Re: USB camera.

Frompeter@easthope.ca
Date2017-12-07 05:30 +0100
SubjectRe: USB camera.
Message-ID<uTVYR-1gg-7@gated-at.bofh.it>
In reply to#188555
*	From: Reco <recoverym4n@gmail.com>
*	Date: Fri, 3 Nov 2017 18:11:57 +0300
> This one does, at least right now it did with mpv.
> lsusb tells me that it's:
> 
> 058f:5608 Alcor Micro Corp

*	From: deloptes <deloptes@gmail.com>
*	Date: Fri, 03 Nov 2017 18:04:40 +0100
> ID 0471:2036 Philips (or NXP) Webcam SPC1030NC
> 
> works very well - already ~10y in use

OK, thanks.

The local consignment shop currently has these 3 cameras in stock.

Logitech M/N: V-UH9,   P/N: 861078-0030
Logitech M/N: V-UAV36, P/N: 861200-0000
Logitech M/N: V-U0006, P/N: 860-000177, PID: LZ944BN

Can anyone confirm one working in Debian 9?

Thanks,                 ... Peter E.



-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                      Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#188557 — Re: USB camera;

Fromdeloptes <deloptes@gmail.com>
Date2017-11-03 18:10 +0100
SubjectRe: USB camera;
Message-ID<uHNDI-6Ni-17@gated-at.bofh.it>
In reply to#188554
peter@easthope.ca wrote:

> *     From: Reco <recoverym4n@gmail.com>
> *     Date: Mon, 2 Oct 2017 18:50:58 +0300
>> I suggest you to file a bug report unless you did it already.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877558
> 
> A Labtec/Vivitar camera has a similar failure. Is any USB camera
> working in Debian 9?
> 
> Many packages in 9 are being updated.  Maintainers must be swamped.
> I can be patient until commotion subsides.
> 
> Thanks for the help,                    ... Peter E.

ID 0471:2036 Philips (or NXP) Webcam SPC1030NC

works very well - already ~10y in use

regards

[toc] | [prev] | [next] | [standalone]

#187509 — Re: USB camera;

Frompeter@easthope.ca
Date2017-10-02 23:50 +0200
SubjectRe: USB camera;
Message-ID<uwgia-Zh-91@gated-at.bofh.it>
In reply to#187473
From: Reco <recoverym4n@gmail.com>
Date: Mon, 2 Oct 2017 10:16:20 +0300
> Try (assuming that you have appropriate device permissions):
> 
> mpv tv:// --tv-device=/dev/video0

peter@dalton:~$ mpv tv:// --tv-device=/dev/video0
Playing: tv://
[tv] Selected driver: v4l2
[tv]  name: Video 4 Linux 2 input
[tv] your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM was used instead.
[tv] Selected device: Microsoft® LifeCam NX-6000
[tv]  Capabilities:  video capture  read/write  streaming
[tv]  supported norms:
[tv]  inputs: 0 = Camera 1;
[tv]  Current input: 0
[tv]  Current format: MJPEG
[tv] ioctl set format failed: Input/output error
[tv] ioctl set mute failed: Invalid argument
[tv] 0 frames successfully processed, 0 frames dropped.
Failed to recognize file format.

Exiting... (Errors when loading file)
peter@dalton:~$ 

"Failed to recognize file format." is reminiscent of the problem with 
guvcview; but MJPEG is no exotic format.  A small idiosyncracy in the 
camera output is not recognized by the Linux softwares?  Most such 
bugs would have been fixed years ago.

Regards,                            ... Peter E.
 

-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                      Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#187078 — Re: USB camera; was Re: Video input vs. systemctl enable.

FromCurt <curty@free.fr>
Date2017-09-21 15:30 +0200
SubjectRe: USB camera; was Re: Video input vs. systemctl enable.
Message-ID<us9Ie-1wS-17@gated-at.bofh.it>
In reply to#187062
On 2017-09-20, Reco <recoverym4n@gmail.com> wrote:
> 	Hi.
>
> On Wed, Sep 20, 2017 at 05:56:22AM -0700, peter@easthope.ca wrote:
>> *	From: Reco <recoverym4n@gmail.com>
>> *	Date: Wed, 20 Sep 2017 09:20:18 +0300
>> > What does 'lsusb' and 'lsusb -t' show for you?
>> 
>> peter@dalton:~$ lsusb
>> Bus 001 Device 006: ID 045e:00f8 Microsoft Corp. LifeCam NX-6000
>
> I got that feeling that things won't be easy, but M$ webcam put this
> right into 'hardcore entertainment' category. Marked AO for Adult Only.
> Viewer discretion is advised.
>

Wouldn't it be helpful to see the dmesg output when he plugs the device
in? Or did we see that already upthread?

I'm reading that this material requires a tweak:

 options uvcvideo quirks=0x100

in

 /etc/modprobe.d/uvcvideo.conf

http://www.linux-hardware-guide.com/2014-01-18-microsoft-lifecam-nx-6000

-- 
"A simpering Bambi narcissist and a thieving, fanatical Albanian
dwarf." Christopher Hitchens, commenting shortly after the nearly
concurrent deaths of Lady Diana and Mother Theresa.

[toc] | [prev] | [next] | [standalone]

#187082 — Re: USB camera; was Re: Video input vs. systemctl enable.

Fromanonymous <recoverym4n@gmail.com>
Date2017-09-21 18:30 +0200
SubjectRe: USB camera; was Re: Video input vs. systemctl enable.
Message-ID<uscwp-3m1-1@gated-at.bofh.it>
In reply to#187078
	Hi.

On Thu, Sep 21, 2017 at 01:22:48PM +0000, Curt wrote:
> On 2017-09-20, Reco <recoverym4n@gmail.com> wrote:
> > 	Hi.
> >
> > On Wed, Sep 20, 2017 at 05:56:22AM -0700, peter@easthope.ca wrote:
> >> *	From: Reco <recoverym4n@gmail.com>
> >> *	Date: Wed, 20 Sep 2017 09:20:18 +0300
> >> > What does 'lsusb' and 'lsusb -t' show for you?
> >> 
> >> peter@dalton:~$ lsusb
> >> Bus 001 Device 006: ID 045e:00f8 Microsoft Corp. LifeCam NX-6000
> >
> > I got that feeling that things won't be easy, but M$ webcam put this
> > right into 'hardcore entertainment' category. Marked AO for Adult Only.
> > Viewer discretion is advised.
> >
> 
> Wouldn't it be helpful to see the dmesg output when he plugs the device
> in? Or did we see that already upthread?

Probably not. lsusb -t is a viable substitute.
I.e. the device is plugged, but there's no appropriate kernel module.
Also I'm allergic to 'journalctl -foobar' output. Way too much noise for
my taste.


> I'm reading that this material requires a tweak:
> 
>  options uvcvideo quirks=0x100
> 
> in
> 
>  /etc/modprobe.d/uvcvideo.conf
> 
> http://www.linux-hardware-guide.com/2014-01-18-microsoft-lifecam-nx-6000

There's a catch. You can pass various options to a kernel module all day
long, but they won't do anything unless the kernel module is loaded.
And that one was not.
Moreover, loading the thing by hand and feeding it a correct USB ID did
not do anything of value.
*Maybe* if uvcvideo is loaded with this quirk *and* fed a USB ID there
would be some difference. An idea worth to check IMO.

Reco

[toc] | [prev] | [next] | [standalone]

#187465 — Re: USB camera.

Frompeter@easthope.ca
Date2017-10-02 02:10 +0200
SubjectRe: USB camera.
Message-ID<uvWt3-jl-11@gated-at.bofh.it>
In reply to#187078
*	From: Curt <curty@free.fr>
*	Date: Thu, 21 Sep 2017 13:22:48 +0000 (UTC)
> I'm reading that this material requires a tweak:
>  options uvcvideo quirks=0x100
> in
>  /etc/modprobe.d/uvcvideo.conf

I was using quirks=0x80 but can try 100 also.

Thanks,            ... Peter E.




-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202                      Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html              Bcc: peter at easthope. ca

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web