issues after kernel update

[DARKHalf]

Hi,
yesterday my distro (xbmcbuntu) made a kernel update and since then I try to get the driver for my tbs6928 running.
I've downloaded tbs-linux-drivers_v140425.zip and made "make && make install". Everything was compiling and install was also successful.
but after a reboot the driver seems not to be loaded properly.

Here is some output:

Code: Select All Code

florian@ftedv-srv:~$ dmesg | grep cx
florian@ftedv-srv:~$
florian@ftedv-srv:~$ dmesg | grep tbs
[    3.766682] tbs6290fe: module license 'TurboSight Proprietary' taints kernel.
florian@ftedv-srv:~$
florian@ftedv-srv:~$ uname -a
Linux ftedv-srv 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
florian@ftedv-srv:~$
florian@ftedv-srv:~$ ls -al /dev/dvb
ls: Zugriff auf /dev/dvb nicht möglich: Datei oder Verzeichnis nicht gefunden
florian@ftedv-srv:~$
florian@ftedv-srv:~$ lsmod | grep tbs
tbs6922fe              22478  0
tbs6928fe              17785  0
tbs6991se              17882  0
tbs6290fe              50747  0
florian@ftedv-srv:~$
florian@ftedv-srv:~$ lspci | grep Multimedia
01:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
florian@ftedv-srv:~$


The strange thing about this is that it seems to load the wrong module or firmware I guess, because dmesg gives output from tbs6290fe.
Oh, and yes: I did the exact steps for compiling and installing the driver. Everything was successful but I do not get the drivers loaded.
Any advice would be great as I'm getting mad.

Regards,
Florian

[SergioDanielG]

Hi DARKHalf.
Did you delete all media drivers from your kernel modules before install tbs-drivers?
If not, try deleting all from your /lib/modules/{your-kernel-version}/kernel/dirvers/media
and reinstall tbs drivers.
Regards.

[DARKHalf]

Hi, yes I did. Additionally I did a complete re-setup of the whole system last night.
Even then I had no success. Even with the clean system the dvb frontend will not be created.
I have no clue what's missing since the driver will give no additional output. Is there a way to
switch v4l to verbose to see if it gives information why it does not set up the dvb frontend?

Regards,
Florian

[DARKHalf]

I thing I found something:

Code: Select All Code

Jun  1 20:43:14 ftedv-srv kernel: [    3.324853] saa716x_core: disagrees about version of symbol dvb_dmxdev_init
Jun  1 20:43:14 ftedv-srv kernel: [    3.324861] saa716x_core: Unknown symbol dvb_dmxdev_init (err -22)
Jun  1 20:43:14 ftedv-srv kernel: [    3.324903] saa716x_core: disagrees about version of symbol dvb_register_adapter
Jun  1 20:43:14 ftedv-srv kernel: [    3.324906] saa716x_core: Unknown symbol dvb_register_adapter (err -22)
Jun  1 20:43:14 ftedv-srv kernel: [    3.324922] saa716x_core: disagrees about version of symbol dvb_dmx_release
Jun  1 20:43:14 ftedv-srv kernel: [    3.324925] saa716x_core: Unknown symbol dvb_dmx_release (err -22)
Jun  1 20:43:14 ftedv-srv kernel: [    3.324938] saa716x_core: disagrees about version of symbol dvb_net_init
Jun  1 20:43:14 ftedv-srv kernel: [    3.324940] saa716x_core: Unknown symbol dvb_net_init (err -22)
Jun  1 20:43:14 ftedv-srv kernel: [    3.324949] saa716x_core: disagrees about version of symbol dvb_dmxdev_release
Jun  1 20:43:14 ftedv-srv kernel: [    3.324952] saa716x_core: Unknown symbol dvb_dmxdev_release (err -22)
Jun  1 20:43:14 ftedv-srv kernel: [    3.324962] saa716x_core: disagrees about version of symbol dvb_frontend_detach
Jun  1 20:43:14 ftedv-srv kernel: [    3.324965] saa716x_core: Unknown symbol dvb_frontend_detach (err -22)
Jun  1 20:43:14 ftedv-srv kernel: [    3.324970] saa716x_core: disagrees about version of symbol dvb_net_release
Jun  1 20:43:14 ftedv-srv kernel: [    3.324973] saa716x_core: Unknown symbol dvb_net_release (err -22)
Jun  1 20:43:14 ftedv-srv kernel: [    3.324980] saa716x_core: disagrees about version of symbol dvb_unregister_frontend
Jun  1 20:43:14 ftedv-srv kernel: [    3.324982] saa716x_core: Unknown symbol dvb_unregister_frontend (err -22)
Jun  1 20:43:14 ftedv-srv kernel: [    3.324990] saa716x_core: disagrees about version of symbol dvb_register_frontend
Jun  1 20:43:14 ftedv-srv kernel: [    3.324993] saa716x_core: Unknown symbol dvb_register_frontend (err -22)
Jun  1 20:43:14 ftedv-srv kernel: [    3.325001] saa716x_core: disagrees about version of symbol dvb_unregister_adapter
Jun  1 20:43:14 ftedv-srv kernel: [    3.325004] saa716x_core: Unknown symbol dvb_unregister_adapter (err -22)
Jun  1 20:43:14 ftedv-srv kernel: [    3.325008] saa716x_core: disagrees about version of symbol dvb_dmx_init
Jun  1 20:43:14 ftedv-srv kernel: [    3.325010] saa716x_core: Unknown symbol dvb_dmx_init (err -22)


Well this seems to be the answer why it is not working. OK, this is a clean setup and compilation did work so far.
I'll have to fiddle around with the saa716x module to see if I can get it working.

[DARKHalf]

Hurray! I've fixed it!
The media folder was not completely clean after my first try of deleting the files.
After I found the above error I've had a second look in the kernel's modules directory.
After deleting all files and reinstalling the driver and doing a reboot the card was initialized properly.
Thanks for the hint SergioDanielG.

[SergioDanielG]

You are welcome and thanks for solution confirmation.
Regards.