Moderator Control Panel ]

Can't scan (Kernel 2.6.39-5)

Can't scan (Kernel 2.6.39-5)

Postby pspmann » Thu Oct 13, 2011 1:19 am

Hello,

I recently buy a TBS5922 and I received it today.
I use Debian squeeze with 2.6.39-5 kernel (from squeeze-backports).
When i try to scan with my-tv or kaffeine : it freeze (the program) around 17% (he finds channels) and the LED changes color: a green moment, another red. I need to restart.

dmesg when i put my receiver :

[ 146.367928] usb 1-5: new high speed USB device number 3 using ehci_hcd
[ 146.500349] usb 1-5: New USB device found, idVendor=734c, idProduct=5922
[ 146.500353] usb 1-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 146.797596] Disabling lock debugging due to kernel taint
[ 146.827746] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in cold state, will try to load a firmware
[ 146.868463] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5922.fw'
[ 146.871103] tbsqbox22: start downloading TBSQBOX firmware
[ 146.887974] usb 1-5: USB disconnect, device number 3
[ 146.987755] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in warm state.
[ 146.987813] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 146.987833] DVB: registering new adapter (TBS QBOX22 DVBS2 USB2.0)
[ 146.987839] tbsqbox22: read eeprom failed
[ 146.989896] dvb-usb: MAC address reading failed.
[ 147.373327] tbs5922fe: module license 'TurboSight Proprietary: http://www.tbsdtv.com' taints kernel.
[ 147.675562] TurboSight TBS 5922 Frontend Attaching...
[ 147.699563] TurboSight TBS 5922 Frontend:
[ 147.699565] tbs5922fe - attach failed
[ 147.699652] dvb-usb: no frontend was attached by 'TBS QBOX22 DVBS2 USB2.0'
[ 147.701910] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/input/input6
[ 147.702010] dvb-usb: schedule remote query interval to 150 msecs.
[ 147.702016] dvb-usb: TBS QBOX22 DVBS2 USB2.0 successfully initialized and connected.
[ 147.702074] usbcore: registered new interface driver tbsqbox22
[ 147.735929] dvb-usb: TBS QBOX22 DVBS2 USB2.0 successfully deinitialized and disconnected.
[ 148.639309] usb 1-5: new high speed USB device number 4 using ehci_hcd
[ 148.772980] usb 1-5: New USB device found, idVendor=734c, idProduct=5922
[ 148.772986] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 148.772990] usb 1-5: Product: TBS-5922
[ 148.772994] usb 1-5: Manufacturer: TBS-Tech
[ 148.772997] usb 1-5: SerialNumber: 001
[ 148.773377] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in cold state, will try to load a firmware
[ 148.777170] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5922.fw'
[ 148.780917] tbsqbox22: start downloading TBSQBOX firmware
[ 148.899234] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in warm state.
[ 148.899287] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 148.899420] DVB: registering new adapter (TBS QBOX22 DVBS2 USB2.0)
[ 149.016895] dvb-usb: MAC address: 00:22:**:**:**:**
[ 149.016897]
[ 149.319130] TurboSight TBS 5922 Frontend Attaching...
[ 149.363411] QBOX22: TBS5922FE attached.
[ 149.660035] DVB: registering adapter 0 frontend 0 (TurboSight TBS 5922 DVBS/S2 frontend)...
[ 149.660686] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/input/input7
[ 149.660760] dvb-usb: schedule remote query interval to 150 msecs.
[ 149.660765] dvb-usb: TBS QBOX22 DVBS2 USB2.0 successfully initialized and connected.


EDIT : When i try to scan (not at start):

[ 731.905188] TurboSight TBS 5922 Frontend:
[ 731.905190] tbs5922fe - Current Delivery System and Mode are unknown


EDIT 2 : I tried with kernel 2.6.38-8

Scan works better but it stop to 57% and kaffeine/metv freezes. (Led green..)
Kaffeine says : "dvbdevice::frontendevent : tuning failed"

Thanks.
pspmann
 
Posts: 5
Joined: Thu Oct 13, 2011 1:12 am

Re: Can't scan (Kernel 2.6.39-5)

Postby luni » Thu Oct 13, 2011 3:42 am

Hi,

I observe the same behavior with the scan tool from the DVB Apps. It scans and finds about 800 channels and crashes then. The crash occurs reproducibly at the same frequency.

Thanks
Lutz
luni
 
Posts: 4
Joined: Thu Oct 13, 2011 3:37 am

Re: Can't scan (Kernel 2.6.39-5)

Postby pspmann » Fri Oct 14, 2011 7:44 pm

Same result with Ubuntu 11.10 (Kernel 3) .... and new drivers published yesterday. It blocks always to the same point and "lock" led turns on ... turns off ...

A part of the log : (dmesg)

[....]
[ 703.024196] DEBUG: 5922 tune checked
[ 703.116116] DEBUG: 5922 tune checked
[ 703.208162] DEBUG: 5922 tune checked
[ 703.300209] DEBUG: 5922 tune checked
[ 703.392129] DEBUG: 5922 tune checked
[ 703.484176] DEBUG: 5922 tune checked
[ 703.576221] DEBUG: 5922 tune checked
[ 703.668268] DEBUG: 5922 tune checked
[ 703.776200] DEBUG: 5922 tune checked
[ 703.868244] DEBUG: 5922 tune checked
[ 703.976177] DEBUG: 5922 tune checked
[ 704.068221] DEBUG: 5922 tune checked
[ 704.184287] DEBUG: 5922 tune checked
[ 704.276197] DEBUG: 5922 tune checked
[ 704.432274] DEBUG: 5922 tune checked
[ 704.524195] DEBUG: 5922 tune checked
[ 704.616241] DEBUG: 5922 tune checked
[ 704.708287] DEBUG: 5922 tune checked
[ 704.800208] DEBUG: 5922 tune checked
[ 704.892253] DEBUG: 5922 tune checked
[ 704.988179] DEBUG: 5922 tune checked
[ 705.152510] DEBUG: 5922 tune sent
[ 705.172268] DEBUG: 5922 tune checked
[ 705.200157] DEBUG: 5922 tune checked
[ 705.228171] DEBUG: 5922 tune checked
[ 705.256185] DEBUG: 5922 tune checked
[ 705.284200] DEBUG: 5922 tune checked
[ 705.308461] DEBUG: 5922 tune finished
[ 705.320218] DEBUG: 5922 tune checked
[ 705.400258] DEBUG: 5922 tune checked
[ 705.472169] DEBUG: 5922 tune checked
[ 705.564091] DEBUG: 5922 tune checked
[ 705.656139] DEBUG: 5922 tune checked
[ 705.748183] DEBUG: 5922 tune checked
[ 705.840103] DEBUG: 5922 tune checked
[ 705.932152] DEBUG: 5922 tune checked
[ 706.024197] DEBUG: 5922 tune checked
[ 706.116116] DEBUG: 5922 tune checked
[ 706.208287] DEBUG: 5922 tune checked
[ 706.300208] DEBUG: 5922 tune checked
[ 706.392129] DEBUG: 5922 tune checked
[ 706.484174] DEBUG: 5922 tune checked
[ 706.576221] DEBUG: 5922 tune checked
[ 706.668144] DEBUG: 5922 tune checked
[ 706.760190] DEBUG: 5922 tune checked
[ 706.852109] DEBUG: 5922 tune checked
[ 706.944156] DEBUG: 5922 tune checked
[ 707.036202] DEBUG: 5922 tune checked
[ 707.128122] DEBUG: 5922 tune checked
[ 707.220168] DEBUG: 5922 tune checked
[ 707.312215] DEBUG: 5922 tune checked
[ 707.404136] DEBUG: 5922 tune checked
[ 707.496181] DEBUG: 5922 tune checked
[ 707.588103] DEBUG: 5922 tune checked
[ 707.680148] DEBUG: 5922 tune checked
[ 707.772195] DEBUG: 5922 tune checked
[ 707.864115] DEBUG: 5922 tune checked
[ 707.956163] DEBUG: 5922 tune checked
[ 708.048208] DEBUG: 5922 tune checked
[ 708.140128] DEBUG: 5922 tune checked
[ 708.232177] DEBUG: 5922 tune checked
[ 708.324095] DEBUG: 5922 tune checked
[ 708.416142] DEBUG: 5922 tune checked
[ 708.508191] DEBUG: 5922 tune checked
[ 708.600110] DEBUG: 5922 tune checked
[ 708.692155] DEBUG: 5922 tune checked
[ 708.808217] DEBUG: 5922 tune checked
[ 708.916270] DEBUG: 5922 tune checked
[ 709.008192] DEBUG: 5922 tune checked
[ 709.124249] DEBUG: 5922 tune checked
[ 709.244180] DEBUG: 5922 tune checked
[ 709.496181] DEBUG: 5922 tune checked
[ 709.588238] DEBUG: 5922 tune checked
[ 709.680273] DEBUG: 5922 tune checked
[ 709.772194] DEBUG: 5922 tune checked
[ 709.864240] DEBUG: 5922 tune checked
[ 709.964165] DEBUG: 5922 tune checked
[ 710.056211] DEBUG: 5922 tune checked
[ 734.212173] DEBUG: 5922 tune sent
[ 740.232057] DEBUG: 5922 tune checked
[ 746.252192] DEBUG: 5922 tune checked
[ 752.272078] DEBUG: 5922 tune checked
[ 758.292087] DEBUG: 5922 tune checked
[ 764.312098] DEBUG: 5922 tune checked
[ 770.332108] DEBUG: 5922 tune checked
[ 776.352118] DEBUG: 5922 tune checked
[ 782.372128] DEBUG: 5922 tune checked
[ 788.392137] DEBUG: 5922 tune checked
[ 794.412148] DEBUG: 5922 tune checked
[ 800.432157] DEBUG: 5922 tune checked
[ 806.452168] DEBUG: 5922 tune checked
[ 812.472178] DEBUG: 5922 tune checked
[ 818.492187] DEBUG: 5922 tune checked
[ 824.512072] DEBUG: 5922 tune checked
[ 830.532083] DEBUG: 5922 tune checked
[ 836.552093] DEBUG: 5922 tune checked
[ 842.572142] DEBUG: 5922 tune checked
[....]
pspmann
 
Posts: 5
Joined: Thu Oct 13, 2011 1:12 am

Re: Can't scan (Kernel 2.6.39-5)

Postby luni » Sun Oct 16, 2011 11:59 pm

Steven,
are TBS working on that issue? The box runs under mythtv without problems but since the scan is not working correctly I only get a couple of channels. BTW: Scanning with mythTV crashes the FW as well. Is there any workaround? Do you have an Idea when you will fix that? I'm thinking of buying a TBS6984 but I'm worried that I get the same issues there...
Regards
Lutz
luni
 
Posts: 4
Joined: Thu Oct 13, 2011 3:37 am

Re: Can't scan (Kernel 2.6.39-5)

Postby cody » Mon Oct 24, 2011 5:21 pm

luni Wrote:Steven, are TBS working on that issue?


no, because there we don't have such issue:

- for example it seems user "pspmann" has faulty box - it's even more strange that it seems he's using some test driver, because messages like "DEBUG: 5922 tune checked" and "DEBUG: 5922 tune sent" are available only in test driver, which should has been given to him by TBS support and his tests clearly show something is not right with his 5922 hardware and probably it was requested to him to return the box for replacement or it has been already replaced

- that means your problem is entirely different than "pspmann". so, it could be some less general hardware fault, which causes instability or indeed some software issue

luni Wrote:BTW: Scanning with mythTV crashes the FW as well. Is there any workaround? Do you have an Idea when you will fix that?


if it crashes always on the same place during scan most probably that line in your "conf" file for the scan on which it's crashing is wrong and you need to delete it. also, what's the error message after all there is a crash and thus has to be some error reported in 'dmesg'.

luni Wrote:I'm thinking of buying a TBS6984 but I'm worried that I get the same issues there...


you won't, whatever problem you have it's isolated to your 5922 box or some problem with 5922 drivers (which is less likely).
cody
 
Posts: 627
Joined: Tue Apr 13, 2010 11:20 pm

Re: Can't scan (Kernel 2.6.39-5)

Postby pspmann » Wed Oct 26, 2011 7:42 pm

Hello,

I don't use test driver, only official driver which is available on your website.
No problems on Windows.
I'm trying to find a solution with EU support.
pspmann
 
Posts: 5
Joined: Thu Oct 13, 2011 1:12 am

Re: Can't scan (Kernel 2.6.39-5)

Postby luni » Sat Oct 29, 2011 1:50 pm

Hi Codi

if it crashes always on the same place during scan most probably that line in your "conf" file for the scan on which it's crashing is wrong and you need to delete it. also, what's the error message after all there is a crash and thus has to be some error reported in 'dmesg'.


What "conf" file are you refering to? Can you please explain in more detail what to do? I try to post dmesg log on monday but I'm sure it looks like the one pspmann posted already.

Im quite sure that this is a fw/driver issue since the card works without issues under windows. I'm currently using the card with the very limited set of channels it found during the scan and it works without problems. Please have a look at that otherwise the box is useless for me.

Thanks
luni
 
Posts: 4
Joined: Thu Oct 13, 2011 3:37 am

Re: Can't scan (Kernel 2.6.39-5)

Postby luni » Tue Nov 01, 2011 2:44 pm

I also get those messages in the logfiles. BTW this really floods my /var/log .... (I use the driver from your web site)

[1450394.275340] DEBUG: 5922 tune checked
[1450394.331214] DEBUG: 5922 tune checked
[1450394.387233] DEBUG: 5922 tune checked
[1450394.443215] DEBUG: 5922 tune checked

Looks like you have a DEBUG version of the driver on the net !?! I still think your box is a great product if only the driver would work correctly (scanning, logging....)

Regards
luni
luni
 
Posts: 4
Joined: Thu Oct 13, 2011 3:37 am

Re: Can't scan (Kernel 2.6.39-5)

Postby zeuf69 » Sun Nov 20, 2011 2:10 am

Hello,
I m using Ubuntu 10.10 and driver linux-tbs-drivers_111115 and i got exactly the same problem

Code: Select All Code
dmesg | grep 5922


Code: Select All Code
(...)
[ 1585.308213] DEBUG: 5922 tune checked
[ 1585.524170] DEBUG: 5922 tune checked
[ 1585.736254] DEBUG: 5922 tune checked
[ 1585.948210] DEBUG: 5922 tune checked
[ 1586.164167] DEBUG: 5922 tune checked
[ 1586.376249] DEBUG: 5922 tune checked
[ 1586.588208] DEBUG: 5922 tune checked
[ 1586.804167] DEBUG: 5922 tune checked
[ 1587.016250] DEBUG: 5922 tune checked
[ 1587.228205] DEBUG: 5922 tune checked
[ 1587.444162] DEBUG: 5922 tune checked
[ 1587.656250] DEBUG: 5922 tune checked
[ 1587.868202] DEBUG: 5922 tune checked
[ 1588.084284] DEBUG: 5922 tune checked
[ 1588.296241] DEBUG: 5922 tune checked
[ 1588.508201] DEBUG: 5922 tune checked
[ 1588.724284] DEBUG: 5922 tune checked
[ 1588.936240] DEBUG: 5922 tune checked
[ 1589.148201] DEBUG: 5922 tune checked
[ 1589.364280] DEBUG: 5922 tune checked
[ 1589.576370] DEBUG: 5922 tune checked
[ 1589.788197] DEBUG: 5922 tune checked
[ 1590.004280] DEBUG: 5922 tune checked
[ 1590.216237] DEBUG: 5922 tune checked
[ 1590.428195] DEBUG: 5922 tune checked
[ 1590.644278] DEBUG: 5922 tune checked
[ 1590.856236] DEBUG: 5922 tune checked
[ 1591.068193] DEBUG: 5922 tune checked
[ 1591.284275] DEBUG: 5922 tune checked
[ 1591.496233] DEBUG: 5922 tune checked
[ 1591.708191] DEBUG: 5922 tune checked
[ 1591.924273] DEBUG: 5922 tune checked
[ 1592.136230] DEBUG: 5922 tune checked
[ 1592.348188] DEBUG: 5922 tune checked
[ 1592.564270] DEBUG: 5922 tune checked
[ 1592.776229] DEBUG: 5922 tune checked
[ 1592.988186] DEBUG: 5922 tune checked
[ 1593.204268] DEBUG: 5922 tune checked
[ 1593.416227] DEBUG: 5922 tune checked
[ 1593.628185] DEBUG: 5922 tune checked
[ 1593.844265] DEBUG: 5922 tune checked
[ 1594.056223] DEBUG: 5922 tune checked
[ 1594.268182] DEBUG: 5922 tune checked
[ 1594.484264] DEBUG: 5922 tune checked
[ 1594.696223] DEBUG: 5922 tune checked
[ 1594.908180] DEBUG: 5922 tune checked
[ 1595.124262] DEBUG: 5922 tune checked
[ 1595.336219] DEBUG: 5922 tune checked
[ 1595.548177] DEBUG: 5922 tune checked
[ 1595.764261] DEBUG: 5922 tune checked
[ 1595.976218] DEBUG: 5922 tune checked
[ 1596.188176] DEBUG: 5922 tune checked
[ 1596.404258] DEBUG: 5922 tune checked
[ 1596.616216] DEBUG: 5922 tune checked
[ 1596.828175] DEBUG: 5922 tune checked
[ 1597.044257] DEBUG: 5922 tune checked
[ 1597.256214] DEBUG: 5922 tune checked
[ 1597.468173] DEBUG: 5922 tune checked
[ 1597.684256] DEBUG: 5922 tune checked
[ 1597.896213] DEBUG: 5922 tune checked
[ 1598.108171] DEBUG: 5922 tune checked
[ 1598.324253] DEBUG: 5922 tune checked
[ 1598.536212] DEBUG: 5922 tune checked
[ 1598.748170] DEBUG: 5922 tune checked
[ 1598.964252] DEBUG: 5922 tune checked
[ 1599.176210] DEBUG: 5922 tune checked
[ 1599.388168] DEBUG: 5922 tune checked
[ 1599.604251] DEBUG: 5922 tune checked
[ 1599.816210] DEBUG: 5922 tune checked
[ 1600.028167] DEBUG: 5922 tune checked
[ 1600.244249] DEBUG: 5922 tune checked
[ 1600.456207] DEBUG: 5922 tune checked
[ 1600.668294] DEBUG: 5922 tune checked
[ 1600.884247] DEBUG: 5922 tune checked
[ 1601.096205] DEBUG: 5922 tune checked
[ 1601.308163] DEBUG: 5922 tune checked
[ 1601.524246] DEBUG: 5922 tune checked
[ 1601.736204] DEBUG: 5922 tune checked
[ 1601.948162] DEBUG: 5922 tune checked
[ 1602.164244] DEBUG: 5922 tune checked
zeuf69
 
Posts: 23
Joined: Sat Nov 05, 2011 4:30 am

Re: Can't scan (Kernel 2.6.39-5)

Postby lofi » Tue Dec 13, 2011 3:30 am

Hello,

these useless messages are created by the binary module:

Code: Select All Code
lofi@sylvester:~/tbs-box/linux-tbs-drivers/v4l$ grep -ri "tune checked" tbs5922*
Binary file tbs5922fe_driver.o.x86 matches
Binary file tbs5922fe_driver.o.x86_64 matches
Binary file tbs5922fe_driver.o.x86_r3 matches


I dont' know why the drivers aren't GPL - if they were it would be easy to debug the code or at least give some additional information to the developers for code improvement.

Best Regards!
lofi
 
Posts: 3
Joined: Tue Dec 13, 2011 2:52 am

Next

Return to Linux

Who is online

Users browsing this forum: No registered users and 2 guests