TBSDTV Community Forum

Hi,

First off, thanks for creating a DVB device that is supported under Linux - it's what made the choice for me when decing what to buy!

I've got as far as I can with the device, in that the drivers are compiled and running, scan-s2 can pull channel information, szap-s2 can switch to a channel and gnutv is able can to dump video to a file that's watchable in mplayer. Great!

However, the final hurdle seems to be integrating the device into MythTV. I realise this may be a little OT, but there seems to be some subtle interplay between the device and MythTV I'm missing (I've been running MythTV on analogue, DVB-T and DVB-S for years, so I should know my way around it). Has anyone got this particular device working in Myth?

FWIW, I'm pointing to Astra 28.2E, 2D in the UK.

Thanks,

Richard

Code: Select All Code

ankh@hpnas:~$ lsusb
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 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 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 734c:5928
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ankh@hpnas:~$ uname -a
Linux hpnas 2.6.32-37-server #81-Ubuntu SMP Fri Dec 2 20:49:12 UTC 2011 x86_64 GNU/Linux

ankh@hpnas:~$ dmesg
[    9.560705] dvb-usb: found a 'TBS QBOXS2 DVBS2 USB2.0' in cold state, will try to load a firmware
[    9.560712] usb 1-5: firmware: requesting dvb-usb-tbsqbox-id5928.fw
[    9.571112] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5928.fw'
[    9.571119] usb 1-5: firmware: requesting dvb-usb-tbsqbox-id5928.fw
[    9.573717] tbsqboxs2: start downloading TBSQBOX firmware
[    9.587184] IR RC5(x) protocol handler initialized
[    9.598058] IR RC6 protocol handler initialized
[    9.612094] IR JVC protocol handler initialized
[    9.616784] IR Sony protocol handler initialized
[    9.626755] [drm] Initialized drm 1.1.0 20060810
[    9.634347] IR MCE Keyboard/mouse protocol handler initialized
[    9.650495] lirc_dev: IR Remote Control driver registered, major 251
[    9.720082] dvb-usb: found a 'TBS QBOXS2 DVBS2 USB2.0' in warm state.
[    9.720198] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    9.720888] DVB: registering new adapter (TBS QBOXS2 DVBS2 USB2.0)
[   10.103511] QBOXS2: CX24116 attached.
[   10.103765] DVB: registering adapter 0 frontend 0 (Conexant CX24116/CX24118)...
[   10.105307] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:12.2/usb1/1-5/input/input3
[   10.105363] dvb-usb: schedule remote query interval to 150 msecs.
[   10.105368] dvb-usb: TBS QBOXS2 DVBS2 USB2.0 successfully initialized and connected.
[   10.105391] usbcore: registered new interface driver tbsqboxs2
[   10.208043]   alloc irq_desc for 26 on node 0
[   10.208048]   alloc kstat_irqs on node 0
[   19.113004] tbsqboxs2: tbsqboxs2_set_voltage 1
[11384.356404] tbsqboxs2: tbsqboxs2_set_voltage 0
[11390.963296] tbsqboxs2: tbsqboxs2_set_voltage 1
[11399.742032] tbsqboxs2: tbsqboxs2_set_voltage 0
[11404.243141] tbsqboxs2: tbsqboxs2_set_voltage 1
[11421.698713] tbsqboxs2: tbsqboxs2_set_voltage 0
[11447.621982] tbsqboxs2: tbsqboxs2_set_voltage 2
[11569.172051] tbsqboxs2: tbsqboxs2_set_voltage 1

hi Richard,

the way how different applications work with DVB device in Linux is unified - that basically means all DVB applications in Linux use the exact same Application Programming Interface (API) to talk to the device and thus MythTV communicates with our Linux drivers in the exact same way 'scan-s2' and 'szap-s2' do it, which are both working for you. so, that suggests the troubles you're having are entirely related to your MythTV environment - in any case that's not at all related to TBS DVB device or its drivers, because as far as they are running with 'scan-s2' and 'szap-s2' then MythTV can work with it too. so, it's better to seek help in MythTV forums, because it's community-driven open-source project and they have better idea what to suggest in case like yours, e.g. what logs to provide, etc. as far as TBS drivers are concerned on your logs everything seems fine, but that's double confirmed by the fact 'szap-s2' and 'scan-s2' work. sorry, that i can't tell something more concrete.

best regards

OK, have figured it out - I used the settings below for the inital scan in Myth from (http://parker1.co.uk/mythtv_freesat.php) :

Code: Select All Code

Freq: 10847000
Polarity: Vertical
Symbol rate: 23000000
Mod Sys: DVB-S2
FEC: 8/9
Modulation: QPSK
Inversion: leave at auto
Rolloff: leave at 0.35

DK if it was the Mod Sys I was using (DVB-S) that Myth didn't like...