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

2017-09-21 Thread anonymous
Hi.

On Thu, Sep 21, 2017 at 01:22:48PM +, Curt wrote:
> On 2017-09-20, Reco  wrote:
> > Hi.
> >
> > On Wed, Sep 20, 2017 at 05:56:22AM -0700, pe...@easthope.ca wrote:
> >> *  From: Reco 
> >> *  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



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

2017-09-21 Thread Curt
On 2017-09-20, Reco  wrote:
>   Hi.
>
> On Wed, Sep 20, 2017 at 05:56:22AM -0700, pe...@easthope.ca wrote:
>> *From: Reco 
>> *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.



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

2017-09-20 Thread Reco
Hi.

On Wed, Sep 20, 2017 at 05:56:22AM -0700, pe...@easthope.ca wrote:
> * From: Reco 
> * 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



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

2017-09-20 Thread peter
*   From: Reco 
*   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