Load module i get error : Failed to attach demod(Solved)

[xfileslv]

Hello.

Try load module cx231xx, and see error :
tbs5280fe: module license 'TurboSight Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
cx231xx: Failed to attach demod 0
cx231xx: Cx231xx dvb Extension initialized

I use lasted drivers v120814 and i tested in older driver v120617, this same problem.

Please help to find solution, why not load frontend (/dev/dvb/adapter0 and /dev/dvb/adapter1) .

OS : Linux Slackware 13.37

Thanks.

Code: Select All Code

root@server:~# uname -a
Linux server 2.6.34.12-1-smp #2 SMP Sat Aug 18 00:30:50 EEST 2012 i686 Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz GenuineIntel GNU/Linux

Code: Select All Code

ls -la /dev/dvb/
/bin/ls: cannot access /dev/dvb/: No such file or directory

Code: Select All Code

root@server:~# lsusb
Bus 001 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 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 14f7:0004 TechniSat Digital GmbH AirStar TeleStick 2
Bus 001 Device 003: ID 734c:5280 TBS Technologies China
root@server:~#

Code: Select All Code

root@server:~# lsmod
Module                  Size  Used by
tbs5280fe               9652  0
cx231xx_dvb             9030  0
dvb_core               73024  1 cx231xx_dvb
cx25840                40116  1
cx231xx               137021  1 cx231xx_dvb
cx2341x                15056  1 cx231xx
videobuf_vmalloc        3535  1 cx231xx
videobuf_core          13007  2 cx231xx,videobuf_vmalloc
v4l2_common             4138  3 cx25840,cx231xx,cx2341x
videodev               76352  4 cx25840,cx231xx,cx2341x,v4l2_common
media                   7837  1 videodev
ir_lirc_codec           3623  0
lirc_dev                7659  1 ir_lirc_codec
ir_mce_kbd_decoder      3642  0
ir_sony_decoder         1735  0
ir_jvc_decoder          1861  0
ir_rc6_decoder          2213  0
ir_rc5_decoder          1733  0
ir_nec_decoder          2213  0
i2c_core               13875  5 tbs5280fe,cx25840,cx231xx,v4l2_common,videodev
rc_core                12679  8 cx231xx,ir_lirc_codec,ir_mce_kbd_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,ir_nec_decoder
xt_tcpudp               1803  4
iptable_filter           852  1
ip_tables               9209  1 iptable_filter
x_tables                9736  3 xt_tcpudp,iptable_filter,ip_tables
8250_pci               20107  0
8250                   20219  1 8250_pci
serial_core            14660  1 8250
e1000e                162538  0

Code: Select All Code

root@server:~# modprobe cx231xx

root@server:~# dmesg
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
lirc_dev: IR Remote Control driver registered, major 253
IR LIRC bridge handler initialized
Linux media interface: v0.10
Linux video capture interface: v2.00
cx231xx v4l2 driver loaded.
cx231xx #0: New device Turbosight Technolog @ 480 Mbps (734c:5280) with 7 interfaces
cx231xx #0: registering interface 1
cx231xx #0: Identified as TurboSight TBS 5280 (card=16)
cx25840 0-0044: cx23102 A/V decoder found @ 0x88 (cx231xx #0)
cx25840 0-0044:  Firmware download size changed to 16 bytes max length
cx25840 0-0044: firmware: requesting v4l-cx231xx-avcore-01.fw
cx25840 0-0044: loaded v4l-cx231xx-avcore-01.fw firmware (16382 bytes)
cx231xx #0: cx231xx #0: v4l2 driver version 0.0.2
cx231xx #0: cx231xx #0/0: registered device video0 [v4l2]
cx231xx #0: cx231xx #0/0: registered device vbi0
cx231xx #0: V4L2 device registered as video0 and vbi0
usbcore: registered new interface driver cx231xx
tbs5280fe: module license 'TurboSight Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
cx231xx: Failed to attach demod 0
cx231xx: Cx231xx dvb Extension initialized
root@server:~#

[patrickc]

I've just starting looking at this also and get the same problem, not sure how to diagnose it as the tbs5280fe_attach function where I guess the problem is in the closed source part of the drivers and doesn't appear to tell us why it's failing. Using a 3.0 kernel:-

modprobe tbs5280fe
[ 237.338279] tbs5280fe: module license 'TurboSight Proprietary' taints kernel.
[ 237.338360] Disabling lock debugging due to kernel taint

modprobe cx231xx
[ 246.927682] cx231xx v4l2 driver loaded.
[ 246.927775] cx231xx #0: New device Turbosight Technolog @ 480 Mbps (734c:5280) with 7 interfaces
[ 246.927877] cx231xx #0: registering interface 1
[ 246.928472] cx231xx #0: Identified as TurboSight TBS 5280 (card=14)
[ 247.118866] cx25840 5-0044: cx23102 A/V decoder found @ 0x88 (cx231xx #0)
[ 247.140279] cx25840 5-0044: Firmware download size changed to 16 bytes max length
[ 249.163503] cx25840 5-0044: loaded v4l-cx231xx-avcore-01.fw firmware (16382 bytes)
[ 249.198876] cx231xx #0: cx231xx #0: v4l2 driver version 0.0.1
[ 249.277138] cx231xx #0: cx231xx #0/0: registered device video1 [v4l2]
[ 249.277240] cx231xx #0: cx231xx #0/0: registered device vbi1
[ 249.277298] cx231xx #0: V4L2 device registered as video1 and vbi1
[ 249.277433] usbcore: registered new interface driver cx231xx
[ 249.341525] cx231xx: Cx231xx Audio Extension initialized
[ 249.654990] cx231xx: Failed to attach demod 0
[ 249.655344] cx231xx: Cx231xx dvb Extension initialized

Bit stuck to be honest

[cody]

hi All,

because 'xfileslv' sent us email too, just to post here our reply to be aware of the status of this issue:

> hello,
>
> i need to check with my colleagues, because it could be TBS 5280 that is
> currently selling is updated revision and needs some update of the Linux
> driver, because from what you and the other customer posted in the forum
> it seems like Linux driver just doesn't recognize your 5280 hardware.
> so, i will keep you informed.
>

BTW, except you there are no other such complains and it's interesting if you all 5280 users in Linux experience such issue or it's isolated case to you, i.e. the 2 customers complaining here.

[xfileslv]

hi All,

because 'xfileslv' sent us email too, just to post here our reply to be aware of the status of this issue:

Hi, thanks.

[xfileslv]

how many time need for release or fix drivers ?

[cody]

how many time need for release or fix drivers ?

since it's not quite clear at the moment what's exactly wrong and causes the is issue it's hard to say. i'm still checking with my colleagues, because i have early sample of 5280 box and it's working perfectly well in Linux - i tested it in several different Linux installations and different kernels over the last few days.

BTW, something that can speed-up the process of providing fix is if any of you is in country member of the EU - that in order to avoid delays due to custom inspection - then you can contacting us on euro_support@tbsdtv.com to arrange sending your 5280 box for investigation and we will cover the shipping costs. i'm not saying you have faulty 5280 boxes, but since Linux driver works with early 5280 sample i have in my hands, what makes more sense is that subsequently hardware design of 5280 was updated, but the necessary changes weren't included in the Linux driver - that's what i believe and i'm checking with my colleagues, of course the other option is that you have faulty box that needs replacement anyway, i.e. that you need to return it anyway. so, that's one way to proceed in order to be faster.

[patrickc]

Thanks guys,

I'll investigate sending it back as you've suggested but as I'm not in a particular hurry I don't mind waiting till next week for any more information you have, in the mean time I might try it out on Windows to confirm it works as well as re-check my linux TBS drivers are built/distributed right.

[cody]

hi All, we made significant progress on this over the last 2 days, i.e. after my last post - thanks to my colleagues we're investigating remotely with the retail 5280 box on which the problem is reproducible. so, it seems it will be necessary some changes in the driver initialization to be made. so, it's not necessary to send back your boxes - i'm not sure, but i believe at the beginning of the next week we will publish driver update that (hopefully) will solve the issue.

[patrickc]

Thanks guys, good luck fixing.

[cody]

the good news is that the problem is fixed - we already have driver for internal testing that works fine. so, the official update is scheduled for the upcoming Monday.