Hi,
I have a PCTV 292e USB TV tuner stick. Apparently Linux includes support for it from kernel 3.16:
https://linuxtv.org/wiki/index.php/PCTV_Systems_tripleStick_T2_(292e)
I am able to use the stick on a Raspberry Pi using OpenELEC without having to do anything at the command line, but was hoping to plug it directly into my Omnia and run tvheadend in an LXC container to stream over WAN.
My understanding (from the Turris DVB wiki page) is that I need Turris to recognise the stick before I can share it with the LXC container.
It appears my Omnia is running a 4.4 kernel:
root@turris:~# uname -r
4.4.134-8f7f4132dc88fb7034ce9648e5961be5-0
I’ve downloaded the firmware file indicated by the linuxtv.org wiki page into /lib/firmware/:
root@turris:~# ls -l /lib/firmware/
drwxr-xr-x 1 root root 14 Mar 29 1957 ath10k
-rw-r--r-- 1 root root 6919 Jun 9 20:38 dvb-demod-si2168-b40-01.fw
However, all I see in dmesg relating to the stick is:
[ 8.000823] usb 3-1: new high-speed USB device number 2 using xhci-hcd
Apologies - although I’ve used Linux for a while as a user/admin, I don’t have much experience of hardware. I’m not sure what further information is useful for troubleshooting this sort of thing.
lsusb -t seems to indicate there’s no driver for the device:
root@turris:~# lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
lsusb -v does identify the device:
root@turris:~# lsusb -v -s 3:2
Bus 003 Device 002: ID 2013:025f PCTV Systems
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2013 PCTV Systems
idProduct 0x025f
bcdDevice 1.00
iManufacturer 3 PCTV
iProduct 1 PCTV 292e
iSerial 2 0013940319
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
So can I assume the issue is that the Turris kernel doesn’t have the necessary device drivers compiled in? If so, is the right thing to do to submit a ticket requesting the addition of the drivers? (I’m not sure how to identify what drivers to request, though…)
Many thanks for any advice.