Well I got round to building the new Image last night.
All I can say is thank you.
The kernel so far at least is working perfect. its found all 4 devices
PCTV 461
PCTV 292e
PCTV 290e
DVbSky 960
I used the following firmware commands
sudo wget https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-demod-si2168-02.fw?raw=true-O /lib/firmware/dvb-demod-si2168-02.fw
sudo wget https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-demod-si2168-b40-01.fw?raw=true-O /lib/firmware/dvb-demod-si2168-b40-01.fw
sudo wget https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-demod-m88ds3103.fw?raw=true-O /lib/firmware/dvb-demod-m88ds3103.fw
I'll try and post some more details on the results after I've tried it for a week or 2.
Thanks again
i use my CT with Sundtek MediaTV Pro III DVB-C/T/T2 and it works like a charm. Driver installation is easy (execute script provided by Sundtek -> done).
Tested on Igors Images with Kernel 3.4.xxx and Kernel 4.1.2 (wheezy! jessie did not work with tvheadend!)
TVheadend 3.4 and 4.0.5 tested.
Its currently in use as tvheadend server for a kodi installation on another machine.
on my system I could see the usb devices in lsusb and dmesg command outputs (lsusb found the stick as "ID 2013:025f PCTV Systems"). If you can't see the USB stick there, i'm afraid i cannot help you. If the stick shows up there, dmesg should output something like:
usb 2-1: New USB device found, idVendor=2013, idProduct=025f
usb 2-1: Product: PCTV 292e
usb 2-1: Manufacturer PCTV
usb 2-1: SerialNumber *somenumber*
this is standard USB device output and also showed up with no working driver. It shows the USB stick is recognized even if no driver is present.
In the compile.sh script i changed the line
KERNEL_CONFIGURE="no" to KERNEL_CONFIGURE="yes". According to your answer you already did this, i just mention it to reproduce all the needed steps
After starting the script, at some point the kernel menuconfig will pop up. Here I selected the following options:
Device Drivers --> I2C-Support --> I2C bus multiplexing support <*>
Device Drivers --> I2C-Support --> Multiplexer I2C Chip Support: All 3 options to <*>
Device Drivers --> Multimedia Support --> Analog TV support [*]
Device Drivers --> Multimedia Support --> Digital TV support [*]
Device Drivers --> Multimedia Support --> AM/FM radio receivers/transmitters support [*]
Device Drivers --> Multimedia Support --> DVB Network support [*]
Device Drivers --> Multimedia Support --> Media USB Adapters [*]
Device Drivers --> Multimedia Support --> Media USB Adapters --> Support for various USB DVB devices v2 <*>, all sub options as module <m> except DVBSky USB support <*>
Device Drivers --> Multimedia Support --> Media USB Adapters --> Empia EM28xx USB devices support <*>
Device Drivers --> Multimedia Support --> Media USB Adapters --> Empia EM28xx analog TV, Video capture and/or webcam support <*>
Device Drivers --> Multimedia Support --> Media USB Adapters --> Empia EM28xx ALSA audio module <M>
Device Drivers --> Multimedia Support --> Media USB Adapters --> DVB/ATSC Support for em28xx based TV cards <*>
Device Drivers --> Multimedia Support --> Media USB Adapters --> Autoselect ancillary drivers (tubers, sensors, i2c, frontends) [*]
I think these options are be everything I changed. After that, the dmesg output shows additional lines when plugging in the stick:
and after downloading the firmware like mentioned in the starting thread, dmesg also shows:
[ 23.848889] si2168 4-0064: found a 'Silicon Labs Si2168-B40'
[ 23.849973] si2168 4-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 24.142642] si2168 4-0064: firmware version: 4.0.4
[ 24.148767] si2157 5-0060: found a 'Silicon Labs Si2157-A30'
[ 24.198515] si2157 5-0060: firmware version: 3.0.5
and now it should work.
Another problem with the stick: It does not start correctly on system boot, i have to unplug and replug it after booting to get it to work. I hope to find a script to "unplug" and "replug" it via console.