Coder Social home page Coder Social logo

tbsdtv / linux_media Goto Github PK

View Code? Open in Web Editor NEW

This project forked from ljalves/linux_media

171.0 48.0 80.0 2.24 GB

TBS linux open source drivers

Home Page: https://github.com/tbsdtv/linux_media/wiki

License: Other

Makefile 0.20% C 98.26% Assembly 0.79% C++ 0.03% Shell 0.35% Perl 0.10% Awk 0.01% Python 0.18% Yacc 0.01% Lex 0.01% UnrealScript 0.01% Gherkin 0.01% XS 0.01% Roff 0.02% Clojure 0.01% M4 0.01% sed 0.01% SmPL 0.01% Raku 0.01% Rust 0.05%

linux_media's Introduction

Linux kernel
============

There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.  The formatted documentation can also be read online at:

    https://www.kernel.org/doc/html/latest/

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.

linux_media's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

linux_media's Issues

Make error in Debian 9 / Kernel 4.9

CC [M] /root/media_build/v4l/cx231xx-dvb.o
/root/media_build/v4l/cx231xx-dvb.c: In function 'start_streaming':
/root/media_build/v4l/cx231xx-dvb.c:426:11: error: implicit declaration of function 'cx231xx_init_bulk_ts2' [-Werror=implicit-function-declaration]
return cx231xx_init_bulk_ts2(dev, CX231XX_DVB_MAX_PACKETS,
^~~~~~~~~~~~~~~~~~~~~
/root/media_build/v4l/cx231xx-dvb.c: In function 'stop_streaming':
/root/media_build/v4l/cx231xx-dvb.c:450:4: error: implicit declaration of function 'cx231xx_uninit_bulk_ts2' [-Werror=implicit-function-declaration]
cx231xx_uninit_bulk_ts2(dev);
^~~~~~~~~~~~~~~~~~~~~~~
/root/media_build/v4l/cx231xx-dvb.c: In function 'register_dvb':
/root/media_build/v4l/cx231xx-dvb.c:716:1: warning: label 'fail_create_graph' defined but not used [-Wunused-label]
fail_create_graph:
^~~~~~~~~~~~~~~~~
/root/media_build/v4l/cx231xx-dvb.c: In function 'dvb_init':
/root/media_build/v4l/cx231xx-dvb.c:828:67: error: subscripted value is neither array nor pointer nor vector
demod_i2c = cx231xx_get_i2c_adap(dev, dev->board.demod_i2c_master[i]);
^
/root/media_build/v4l/cx231xx-dvb.c:1362:67: error: subscripted value is neither array nor pointer nor vector
tbs_cx_mac(cx231xx_get_i2c_adap(dev, dev->board.demod_i2c_master[0]), i, mac);
^
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.9.0-2-common/scripts/Makefile.build:298: recipe for target '/root/media_build/v4l/cx231xx-dvb.o' failed
make[5]: *** [/root/media_build/v4l/cx231xx-dvb.o] Error 1
/usr/src/linux-headers-4.9.0-2-common/Makefile:1507: recipe for target 'module/root/media_build/v4l' failed
make[4]: *** [module/root/media_build/v4l] Error 2
Makefile:150: recipe for target 'sub-make' failed
make[3]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-4.9.0-2-amd64'
Makefile:51: recipe for target 'default' failed
make[1]: *** [default] Error 2
make[1]: Leaving directory '/root/media_build/v4l'
Makefile:26: recipe for target 'all' failed
make: *** [all] Error 2

TBS 6285 not scanning DVB-C

Setup: unRAID 6.2.4 w/ Open Source drivers.

Issue: Scanning the DVB-C source, no information back from TVHeadend.
Action 1: Reverted to a Windows 10 machine, running NextPVR on the same card, same settings - and it worked, pulling down several hundred channels.

Action 2: Reverted to unRAID 6.2.4 compiled with the TBS Official DVB-C drivers and retried. Success. Same amount of channels have been retrieved as per the Windows instance.

Conclusion: So, there's some kind of bug in the open source drivers for the TBS 6285 card in DVB-C mode. The error messages consistently stated a Poll Timeout.

Additional Info:
Frequency of Mux: 571000000
Symbol Rate: 6952000
Delivery: DVB-C

Drivers - latest used as of 23/12/2016.

I'm now running unRAID 6.2.4 with the TBS Official drivers for over 24 hours it's solid, but it's not a continuing solution for me, as I will also be putting some DVB-S signals in there and I'm not sure if the DVB-C drivers will work with the DVB-S.

So, if anyone has any suggestions on how to implement the Open Source drivers and have them work with a DVB-C source and also with a DVB-S and DVB-T, I'd be most grateful.

Not all the frontends are registering - Signal in astra cesbo not correct- frontend order

1: I have a mix of cards in my server 6905, 6909, 6985.
I have a total of 8 tbs 6985 tuners. 2 x cards as you can see only 1 is registering.
2: In astra cesbo the TBS 6985 is not showing the correct Signal / BER
3: Also the frontend does not stay in order on reboots.
How to fix these issues? Thank you

13.376247] [] saa716x_tbs6985_frontend_attach+0x7c/0x290 [saa716x_budget]
[ 13.376325] [] saa716x_tbs6985_frontend_attach+0x7c/0x290 [saa716x_budget]
[ 13.376524] [] saa716x_tbs6985_frontend_attach+0x7c/0x290 [saa716x_budget]
[ 13.376592] [] saa716x_tbs6985_frontend_attach+0x7c/0x290 [saa716x_budget]
[ 13.667619] SAA716x Budget 0000:0b:00.0: DVB: registering adapter 12 frontend 0 (TurboSight TBS 6985 DVB-S/S2)...
[ 37.306148] TBSECP3 driver 0000:08:00.0: DVB: registering adapter 7 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 37.418134] TBSECP3 driver 0000:08:00.0: DVB: registering adapter 13 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 37.537891] TBSECP3 driver 0000:08:00.0: DVB: registering adapter 14 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 37.649365] TBSECP3 driver 0000:08:00.0: DVB: registering adapter 15 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 37.769246] TBSECP3 driver 0000:08:00.0: DVB: registering adapter 16 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 37.839632] TBSECP3 driver 0000:08:00.0: DVB: registering adapter 17 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 37.910876] TBSECP3 driver 0000:08:00.0: DVB: registering adapter 18 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 37.988692] TBSECP3 driver 0000:08:00.0: DVB: registering adapter 19 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 38.115250] TBSECP3 driver 0000:0a:00.0: DVB: registering adapter 20 frontend 0 (TurboSight TBS 6905 DVB-S/S2 )...
[ 38.236218] TBSECP3 driver 0000:0a:00.0: DVB: registering adapter 21 frontend 0 (TurboSight TBS 6905 DVB-S/S2 )...

"ts discontinuity" issue with TBS6909

Hi,

I installed the latest open source drivers but TBS6909 works very unstable. Lots of "TS discontinuity" errors. If I lock to the same frequency using TBS6905 or TBS6910 no errors at all.

Then I switch back to closed source drivers v160219 and TBS6909 works fine.

OS: Ubuntu 16.04 (64 Bit)
Kernel: 4.4.0-42-generic
DVBlast 3.0

ISDBT: Err setting tuner params

I have two TBS6522 and two TBS6528, I can't make them tune into an ISDBT channel in Linux.

I tried installing them on 5 different machines with fresh Ubuntu and CentOS install, and with different kernels going from 3.10 to 4.4.

Using kernel 4.4 and Ubuntu the driver was able to register the adapters and frontends but is unable to tune/lock into any frequency.

$ uname -a
Linux localhost 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Here I'm using dvbv5-zap, but I tried with several other tools and all of them get the same result.

$ dvbv5-zap -c channel.conf "EPTV Campinas" -P -r
$ cat /etc/var/syslog
...
kernel: [ 5977.720769] si2183 0-0067: err setting tuner params
kernel: [ 5977.721033] si2183 0-0067: set_params failed=-22
...

When I use scan I get an "tuning failed" error. I also executed with the dvb-fe-tool -d ISDBT command.
I never worked with linux drivers but if someone can point where I have to look, maybe I can find the problem...

"ts discontinuity" issue with TBS6991SE

Hi,

I have the same issues as seen in #16 but for TBS6991SE and only for some channels such as: AutoMotorSport HD on S16E0 11470 V 30000. I get around 500-600 discontinuities per second.
The same channels tunned on a 6909 works without any issues.

MOI Pro AMD, FW: 2.0.0.1
OS: CentOS Linux release 7.2.1511
Kernel: 4.4.19-1.el7.elrepo.x86_64
DVBlast 3.1

Assign inputs to tuner pairs

Here in New Zealand, we have only one real satellite source, Optus D1, and all the transponders on it that are used for free-to-air channels (Freeview) or pay channels (Sky TV) are transmitted from it using horizontal polarisation. Our receiving dishes are normally using just a single local oscillator - that is what Sky TV installs when you sign up with them and also what most third party installers use. The latest dish variant (which I have) has two LNBs, so that Sky can sell you a second set-top box without having to change the dish. So I currently have one LNB connected to my STB, and the other to a splitter and then to two DVB-S2 tuners in my MythTV PC. I have bought a TBS6909 8 tuner DVB-S2 card to replace the two separate DVB-S2 tuners, but if I use the current drivers in mode=1, I would have to provide a signal on all four of the card's inputs. To do that, I would need to split the signal in a 4-way splitter, which might cause the signal level to be too low for good reception. Since the MXL5xx chip used on the TBS6909 allows internal mapping of the inputs to the tuner pairs, I thought it would be much better if I could just modify the drivers to allow me to use a single input to run all 8 tuners. When I looked at the mxl5xx.c file, I found that was in fact pretty easy to do, and I now have it working. There is an additional "inputs" parameter on the mxl5xx driver which allows assigning of the inputs to the tuner pairs when using mode=1, but defaults to the current mode=1 setup if it is missing:

root@lith:~/projects/tbs6909-drivers/media_build# modinfo mxl5xx
filename: /lib/modules/4.4.0-38-generic/kernel/drivers/media/dvb-frontends/mxl5xx.ko
license: GPL
author: Ralph Metzler
description: MXL5XX driver
srcversion: 6D1D7AE4BB71F44228F09B0
depends:
vermagic: 4.4.0-38-generic SMP mod_unload modversions
parm: mode:Multi-switch mode: 0=quattro/quad 1=normal direct connection (int)
parm: inputs:Input number (0-3) for each of the 4 tuner pairs. Default is 0,1,2,3. Only used if mode=1. (array of short)

I have attached a git diff of my changes.
diff.txt

build error after 4d616f9

I got this error after commit 4d616f9 (update the si2168 snr,ber... interface).
gcc 5.3 - cross compiling

/tbs-oss-2016-07-26/media_build/v4l/si2168.c: In function 'si2168_read_snr':
/tbs-oss-2016-07-26/media_build/v4l/si2168.c:201:5: error: 'struct si2168_dev' has no member named 'snr'
  dev->snr=52428;
     ^
/tbs-oss-2016-07-26/media_build/v4l/si2168.c:202:45: error: 'struct si2168_dev' has no member named 'snr'
  *snr = (dev->fe_status & FE_HAS_LOCK) ? dev->snr : 0;
                                             ^
/tbs-oss-2016-07-26/media_build/v4l/si2168.c: In function 'si2168_read_ucblocks':
/tbs-oss-2016-07-26/media_build/v4l/si2168.c:247:9: error: 'struct si2168_dev' has no member named 'stat_resp'
  if (dev->stat_resp & 0x10) {
         ^
/tbs-oss-2016-07-26/media_build/v4l/si2168.c: In function 'si2168_init':
/tbs-oss-2016-07-26/media_build/v4l/si2168.c:500:9: error: 'struct si2168_dev' has no member named 'warm'
  if (dev->warm) {
         ^
/tbs-oss-2016-07-26/media_build/v4l/si2168.c: In function 'si2168_sleep':
/tbs-oss-2016-07-26/media_build/v4l/si2168.c:738:9: error: 'struct si2168_dev' has no member named 'version'
  if (dev->version > ('B' << 24 | 4 << 16 | 0 << 8 | 11 << 0))
         ^
/tbs-oss-2016-07-26/media_build/v4l/si2168.c:739:6: error: 'struct si2168_dev' has no member named 'warm'
   dev->warm = false;
      ^
scripts/Makefile.build:264: recipe for target '/tbs-oss-2016-07-26/media_build/v4l/si2168.o' failed
make[4]: *** [/tbs-oss-2016-07-26/media_build/v4l/si2168.o] Error 1

TBS 6909 low signal compared to 6905

6909 lower signal.

Test channel = Channel 5 using Astra Cesbo
Card 6909 Signal = 53% SNR = 50%
Card 6905 Signal = 62% SNR = 50%
The SNR is the same and the signal is a about 10% less on the 6909
Now the difference in signal is that due to the Card Tuner model or the Driver?
Thank you

TBS5520 no frontend was attached error

Hi all,
I compiled the open source drivers successfully but when I reboot or replug the USB I get the next errors (excerpt):

[    4.441206] dvb-usb: found a 'TBS 5520 USB2.0' in cold state, will try to load a firmware
[    4.443600] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[    4.443638] iTCO_wdt: Found a Lynx Point TCO device (Version=2, TCOBASE=0x1860)
[    4.443939] dvb-usb: downloading firmware from file 'dvb-usb-tbs5520-01.fw'
[    4.443940] tbs5520: start downloading tbs5520 firmware
....
[    4.567295] tbs5520: end downloading tbs5520 firmware
[    4.567300] dvb-usb: found a 'TBS 5520 USB2.0' in warm state.
[    4.567360] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    4.567370] dvbdev: DVB: registering new adapter (TBS 5520 USB2.0)
[    4.567371] dvb-usb: MAC address: 00:00:00:00:00:00
[    4.570003] i2c i2c-9: avl6882: attach failed family id mismatch
[    4.570031] TBS5520: frontend attach failed
[    4.570032] dvb-usb: no frontend was attached by 'TBS 5520 USB2.0'
[    4.570101] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:14.0/usb3/3-2/input/input16
[    4.570129] dvb-usb: schedule remote query interval to 150 msecs.
[    4.570130] dvb-usb: TBS 5520 USB2.0 successfully initialized and connected.
[    4.570151] usbcore: registered new interface driver tbs5520
[    4.587549] dvb-usb: TBS 5520 USB2.0 successfully deinitialized and disconnected.
[    4.679804] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[    4.683377] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
[    4.898198] Adding 16777212k swap on /dev/sdb2.  Priority:-1 extents:1 across:16777212k FS
[    5.596719] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
[    5.643190] systemd-journald[552]: Received request to flush runtime journal from PID 1
[    5.919327] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[    6.105886] EXT4-fs (sdb4): mounted filesystem with ordered data mode. Opts: (null)
[    6.241300] usb 3-2: new high-speed USB device number 8 using xhci_hcd
[    6.409808] usb 3-2: New USB device found, idVendor=734c, idProduct=5520
[    6.409810] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.409811] usb 3-2: Product: TBS 5520
[    6.409812] usb 3-2: Manufacturer: TBS-Tech
[    6.410259] dvb-usb: found a 'TBS 5520 USB2.0' in cold state, will try to load a firmware
[    6.410283] dvb-usb: downloading firmware from file 'dvb-usb-tbs5520-01.fw'
[    6.410284] tbs5520: start downloading tbs5520 firmware
[    6.519233] tbs5520: end downloading tbs5520 firmware
[    6.519236] dvb-usb: found a 'TBS 5520 USB2.0' in warm state.
[    6.519275] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    6.519329] dvbdev: DVB: registering new adapter (TBS 5520 USB2.0)
[    6.519331] dvb-usb: MAC address: 00:00:00:00:00:00
[    6.522579] i2c i2c-9: avl6882: found id=0xb family_id=0x68624955
[    6.528843] i2c i2c-9: r848: Rafael R848 successfully attached
[    6.528844] tbs5520: TBS5520: frontend attached

[    6.528993] dvb-usb: no frontend was attached by 'TBS 5520 USB2.0'
[    6.529147] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:14.0/usb3/3-2/input/input17
[    6.529177] dvb-usb: schedule remote query interval to 150 msecs.
[    6.529178] dvb-usb: TBS 5520 USB2.0 successfully initialized and connected.

With all any DVB device is present in the system.

Some data about my system:
Fedora 25 Workstation
4.10.8-200.fc25.x86_64

Thanks.

TBS5922SE firmware load issue in >4.9.0

tbs5922se_load_firmware function is using the stack, which is not allowed anymore, same as described here:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=43fab9793c1f44e665b4f98035a14942edf03ddc

leads to

[    6.889846] dvb-usb: found a 'TBS 5922SE DVBS2 USB2.0' in cold state, will try to load a firmware
[    6.918837] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5923.fw'
[    6.921355] tbs5922se: start downloading TBS5922SE firmware
[    6.923863] ------------[ cut here ]------------
[    6.926291] WARNING: CPU: 1 PID: 214 at drivers/usb/core/hcd.c:1584 usb_hcd_map_urb_for_dma+0x3ac/0x570 [usbcore]
[    6.928855] transfer buffer not dma capable
[    6.931350] Modules linked in: dvb_usb_tbs5922se(E+) tas2101(E) dvb_usb(E) i2c_mux(E) dvb_core(E) rc_core(E) intel_rapl(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) kvm(E) irqbypass(E) crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E) pcbc(E) aesni_intel(E) snd_hda_codec_hdmi(E) aes_x86_64(E) joydev(E) snd_hda_codec_realtek(E) snd_hda_codec_generic(E) crypto_simd(E) glue_helper(E) iTCO_wdt(E) iTCO_vendor_support(E) eeepc_wmi(E) cryptd(E) asus_wmi(E) ppdev(E) intel_cstate(E) mxm_wmi(E) evdev(E) sparse_keymap(E) intel_uncore(E) i915(E) drm_kms_helper(E) drm(E) snd_hda_intel(E) hci_uart(E) btbcm(E) btqca(E) btintel(E) bluetooth(E) intel_rapl_perf(E) serio_raw(E) i2c_algo_bit(E) intel_lpss_acpi(E) intel_lpss(E) pcspkr(E) parport_pc(E) mfd_core(E) battery(E) snd_hda_codec(E) mei_me(E)
[    6.948303]  rfkill(E) i2c_i801(E) parport(E) video(E) snd_hda_core(E) snd_hwdep(E) shpchp(E) snd_pcm(E) snd_timer(E) snd(E) soundcore(E) mei(E) button(E) tpm_tis(E) tpm_tis_core(E) acpi_pad(E) tpm(E) acpi_als(E) kfifo_buf(E) industrialio(E) wmi(E) fuse(E) autofs4(E) ext4(E) crc16(E) jbd2(E) fscrypto(E) mbcache(E) hid_generic(E) usbhid(E) sg(E) sd_mod(E) crc32c_intel(E) psmouse(E) xhci_pci(E) ahci(E) xhci_hcd(E) libahci(E) libata(E) r8169(E) mii(E) scsi_mod(E) usbcore(E) fan(E) thermal(E) i2c_hid(E) hid(E) fjes(E)
[    6.956487] CPU: 1 PID: 214 Comm: systemd-udevd Tainted: G            E   4.11.0-rc1 #1
[    6.958099] Hardware name: System manufacturer System Product Name/H110M-R, BIOS 3016 12/27/2016
[    6.959653] Call Trace:
[    6.960959]  ? dump_stack+0x5c/0x77
[    6.962268]  ? __warn+0xc4/0xe0
[    6.963579]  ? warn_slowpath_fmt+0x5f/0x80
[    6.964768]  ? usb_hcd_map_urb_for_dma+0x3ac/0x570 [usbcore]
[    6.965882]  ? usb_hcd_submit_urb+0x1e0/0xa50 [usbcore]
[    6.966993]  ? update_load_avg+0x58a/0xa30
[    6.968089]  ? usb_start_wait_urb+0x6d/0x170 [usbcore]
[    6.969181]  ? usb_control_msg+0xdc/0x130 [usbcore]
[    6.970129]  ? cache_alloc_refill+0x12e/0x330
[    6.971064]  ? tbs5922se_op_rw.constprop.3+0xd7/0x120 [dvb_usb_tbs5922se]
[    6.972000]  ? tbs5922se_load_firmware+0x9e/0x210 [dvb_usb_tbs5922se]
[    6.972930]  ? dvb_usb_download_firmware+0xa8/0xf0 [dvb_usb]
[    6.973873]  ? dvb_usb_device_init+0x3e6/0x6e0 [dvb_usb]
[    6.974741]  ? tbs5922se_probe+0x21/0x30 [dvb_usb_tbs5922se]
[    6.975584]  ? usb_probe_interface+0x152/0x300 [usbcore]
[    6.976415]  ? driver_probe_device+0x2be/0x460
[    6.977236]  ? __driver_attach+0xd6/0xe0
[    6.978059]  ? driver_probe_device+0x460/0x460
[    6.978883]  ? bus_for_each_dev+0x67/0xb0
[    6.979658]  ? bus_add_driver+0x40/0x260
[    6.980440]  ? driver_register+0x57/0xd0
[    6.981198]  ? usb_register_driver+0x7c/0x140 [usbcore]
[    6.981960]  ? 0xffffffffc047b000
[    6.982718]  ? tbs5922se_module_init+0x1b/0x1000 [dvb_usb_tbs5922se]
[    6.983493]  ? do_one_initcall+0x4e/0x1b0
[    6.984268]  ? do_init_module+0x5a/0x1fa
[    6.985038]  ? load_module+0x2320/0x28b0
[    6.985807]  ? __symbol_put+0x60/0x60
[    6.986583]  ? vfs_read+0x114/0x130
[    6.987397]  ? security_capable+0x41/0x60
[    6.988156]  ? SYSC_finit_module+0x8e/0xe0
[    6.988908]  ? entry_SYSCALL_64_fastpath+0x1e/0xad
[    6.989675] ---[ end trace 9508d8c55348bb58 ]---
[    6.990441] tbs5922se: error while transferring firmware
[    6.991203] tbs5922se: could not restart the USB controller CPU.
[    6.991955] tbs5922se: could not restart the USB controller CPU.

TBS 5927 does not load firmware

Worked/still works with previous 4.8 kernel, but not since 4.9 was put into the tree.

Dec 24 07:00:54 backend kernel: [ 4.676551] usbcore: registered new interface driver tbs5927
Dec 24 07:10:30 backend kernel: [ 590.171382] usb 1-4: New USB device found, idVendor=734c, idProduct=5927
Dec 24 07:10:30 backend kernel: [ 590.172544] dvb-usb: found a 'TurboSight TBS 5927 DVB-S/S2' in cold state, will try to load a firmware
Dec 24 07:10:30 backend kernel: [ 590.172551] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5927.fw'
Dec 24 07:10:30 backend kernel: [ 590.172553] tbs5927: start downloading TBS5927 firmware
Dec 24 07:10:30 backend kernel: [ 590.172565] tbs5927: error while transferring firmware
Dec 24 07:10:30 backend kernel: [ 590.172628] tbs5927: could not restart the USB controller CPU.
Dec 24 07:10:30 backend kernel: [ 590.172679] tbs5927: could not restart the USB controller CPU.

Does the same commands work on centos 6

Hi I been using ubuntu 14>04 but i am going to change to Centos 6 for stability.
Does the same commands work on centos as i have never used the os before.
Thank you.

Not compilable with kernel 4.8

It's not possible to compile drivers with kernel 4.8 it looks like that dma attributes change from structure to unsigned int.

Build error

Hi

Tried a reinstall today on Ubuntu 16.04. Make fails with the following:

/home/anders/Opensrc/media_build/v4l/dvb_net.c: In function 'dvb_net_setup':
/home/anders/Opensrc/media_build/v4l/dvb_net.c:1344:5: error: 'struct net_device' has no member named 'max_mtu'
dev->max_mtu = 4096;

Mix cards TBSECP3 frontend 0 attach failed

@crazycat69
Hello.
I have just upgraded with 2 x 6909 and 2 x 6905
With the 6905 I get TBSECP3 frontend 0 attach failed - TBSECP3 frontend 1 attach failed
I tried with a spare 6905 card and same error so i know the card is not faulty.
Please see screen shot, any idea how to fix?
Thank you.

dmesg

TBS 6205 and 6209

Hello
I have TBS 6205 and 6209 insttaled with latest driver .. But DVB-C not work .. i can use only DVB-T ..
any idea

multiple cards not appearing

I have system with multiple cards
1 x tbs 6909 Octo
1 x tbs 6985 quad

I have installed latest version drivers but only octo card shows,
I install tbs v161031.zip drivers and both cards appear.

TBS 6982, Kernel 4.9

Hi,

Building and Installation went fine,
and driver seems to work ok.

But the logs get spammed with messages like this (about every second five lines):

dvb_demux: dvb_dmx_swfilter_section_packet: dvb_demux.c discontinuity detected 184 bytes lost

Cheers,
Max

Does not compile for Linux Kernel 4.8.0-2

Hi,
I'm using Debian with Kernel 4.8.0-2 and tried to install this driver as described in the wiki.
However, I just get a message that patches could not be applied when I run 'make'.

Using the 'master'-branch instead of 'latest' seems to work, as I can compile and install, but when I run 'make reload' a big proportion of the modules does not exist.
Especially when i run 'modprobe saa716x_budget int_type=1' the module does not exist.

TBS 6522: Add DVB-S2X Support (feature request)

Since the driver installer replaces the media subsystem of the kernel anyway, can DVB-S2X Support added without too much hassle? As i understand it, this would mean adding new types of mudulation, rolloff and FEC values but no changes to the base DVB-S2 system.

kernel 3.2.0 not compiling

I need to compile tbs drivers on ubuntu kernel 3.2.0-41-generic, can someone help me solve this issue?

/media/media_build/v4l/mtv23x.c:2113:2: warning: passing argument 3 of 'regmap_read' makes pointer from integer without a cast [enabled by default]
regmap_read(dev->regmap,0x14,(int)&GVBB);
^
In file included from /media/media_build/v4l/mtv23x_priv.h:6:0,
from /media/media_build/v4l/mtv23x.c:1:
include/linux/regmap.h:135:5: note: expected 'unsigned int *' but argument is of type 'int'
int regmap_read(struct regmap *map, unsigned int reg, unsigned int *val);
^
CC [M] /media/media_build/v4l/gx1503.o
/media/media_build/v4l/gx1503.c: In function 'gx1503_probe':
/media/media_build/v4l/gx1503.c:519:8: warning: passing argument 3 of 'i2c_add_mux_adapter' makes integer from pointer without a cast [enabled by default]
gx1503_select, gx1503_deselect);
^
In file included from /media/media_build/v4l/gx1503_priv.h:7:0,
from /media/media_build/v4l/gx1503.c:1:
include/linux/i2c-mux.h:35:21: note: expected 'u32' but argument is of type 'struct i2c_client *'
struct i2c_adapter *i2c_add_mux_adapter(struct i2c_adapter *parent,
^
/media/media_build/v4l/gx1503.c:519:8: error: too many arguments to function 'i2c_add_mux_adapter'
gx1503_select, gx1503_deselect);
^
In file included from /media/media_build/v4l/gx1503_priv.h:7:0,
from /media/media_build/v4l/gx1503.c:1:
include/linux/i2c-mux.h:35:21: note: declared here
struct i2c_adapter *i2c_add_mux_adapter(struct i2c_adapter *parent,
^
/media/media_build/v4l/gx1503.c:517:12: warning: assignment from incompatible pointer type [enabled by default]
dev->muxc = i2c_add_mux_adapter(client->adapter,&client->dev,
^
/media/media_build/v4l/gx1503.c: In function 'gx1503_remove':
/media/media_build/v4l/gx1503.c:556:2: warning: passing argument 1 of 'i2c_del_mux_adapter' from incompatible pointer type [enabled by default]
i2c_del_mux_adapter(dev->muxc);
^
In file included from /media/media_build/v4l/gx1503_priv.h:7:0,
from /media/media_build/v4l/gx1503.c:1:
include/linux/i2c-mux.h:42:5: note: expected 'struct i2c_adapter *' but argument is of type 'struct i2c_mux_core *'
int i2c_del_mux_adapter(struct i2c_adapter *adap);
^
make[3]: *** [/media/media_build/v4l/gx1503.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [module/media/media_build/v4l] Error 2
make[2]: Leaving directory /usr/src/linux-headers-3.2.0-41-generic' make[1]: *** [default] Error 2 make[1]: Leaving directory /media/media_build/v4l'
make: *** [all] Error 2

Please help how to install on centos 6

Hi.
I have a server that i changed from ubuntu to centos as ubuntu always updates the kernal
I am unable to get it installed on centos using the guide.
Is there anything extra i need to install or add to get it installed?
Thank you

5281 usb dual tuner stopped working

I am using a tbs5281 dual usb tuner alongside two tbs5220 usb sticks in a dvr system. This setup was working fine, with 4 adapters showing up as expected under /dev/dvb.

Updated to latest git and now only the two 5220s show up under /dev/dvb and in tvheadend (and work fine). However the 5281 now shows up under /dev/v4l and is not detected in tvheadend.

driver install error

make[1]: *** No rule to make target '../linux/drivers/media/platform/s5p-tv/Kconfig', needed by 'Kconfig'. Stop.
make[1]: Leaving directory '/home/administrator/tbsdriver/media_build/v4l'
Makefile:26: recipe for target 'all' failed
make: *** [all] Error 2

Which DVB card to buy, TBS6290 or TBS6290SE?

TBS6290SE is already supported, but TBS6290 is a little cheaper.
What's the difference between this two model?
Is TBS6290 deprecated?
I'd like to buy TBS6290 and write the driver code for it as an exercise if this task is easy.

Recompile on Kernel update

Hello Guys,

Is there a faster way to get media tree after kernel update, than a script that checks the right folders and starts compiling if neccessary?
I've read in other forums, the media tree is too big for dkms.

Compile fails with Kernel 4.10.0

CC [M] /root/build/tbsdriver/media_build/v4l/videobuf-dma-sg.o
/root/build/tbsdriver/media_build/v4l/videobuf-dma-sg.c: In function 'videobuf_vm_fault':
/root/build/tbsdriver/media_build/v4l/videobuf-dma-sg.c:442:21: error: 'struct vm_fault' has no member named 'virtual_address'
(unsigned long)vmf->virtual_address,
^
/root/build/tbsdriver/media_build/v4l/videobuf-dma-sg.c:56:42: note: in definition of macro 'dprintk'
printk(KERN_DEBUG "vbuf-sg: " fmt , ## arg)
^
/root/build/tbsdriver/media_build/v4l/videobuf-dma-sg.c:448:46: error: 'struct vm_fault' has no member named 'virtual_address'
clear_user_highpage(page, (unsigned long)vmf->virtual_address);
^
make[3]: *** [/root/build/tbsdriver/media_build/v4l/videobuf-dma-sg.o] Error 1
make[2]: *** [module/root/build/tbsdriver/media_build/v4l] Error 2
make[2]: Leaving directory /usr/src/kernels/4.10.0-1.el7.elrepo.x86_64' make[1]: *** [default] Error 2 make[1]: Leaving directory /root/build/tbsdriver/media_build/v4l'
make: *** [all] Error 2

TBS5281 card DVB-C network: invalid checksum problem

I'm using a TBS5281 card with Tvheadend 4.2 for receiving DVB-C channels and the Silicon Labs Si2168 opensource TBS driver at most of the channels generate the following error messages in log file of Tvheadend:

TS: Silicon Labs Si2168 : DVB-C #0/DVB-C network/250MHz/TV2: MPEG2VIDEO @ #201 Continuity counter error (total 1557)
TS: Silicon Labs Si2168 : DVB-C #0/DVB-C network/250MHz/TV2: MPEG2AUDIO @ #210 Continuity counter error (total 252)
TS: Silicon Labs Si2168 : DVB-C #0/DVB-C network/250MHz/TV2: TELETEXT @ #220 Continuity counter error (total 191)
TS: Silicon Labs Si2168 : DVB-C #0/DVB-C network/250MHz/TV2: MPEG2AUDIO @ #211 Continuity counter error (total 236)
TS: Silicon Labs Si2168 : DVB-C #0/DVB-C network/250MHz/TV2: MPEG2VIDEO @ #201 Corrupted PES header (errors 1)
pmt: 250MHz in DVB-C network: invalid checksum (len 55, errors 1)
eit: 250MHz in DVB-C network: invalid checksum (len 1718, errors 40)

If I use the proprietary TBS driver everything works correctly. Could somebody help to me?

BR,
Schneci

tbs 6205

I use 2 x 6205 tuner's connected to the pci slots of Asus z270g motherboard and i am using ubuntu server 16.04 with last open source drivers compiled from git.

The backend i am using with those driver's is tvheadend, and it works really good with total number of tuners of first 6205 but as soon as it keeps start using the tuners from the second 6205, i get tuner failed, and continuity errors.

Any ideas?

linux-4.12.x and up: saa716x failes to build (has to change msi-x to the new pci_alloc_irq_vectors api)

linux-4.12-rc1: saa716x failes to build due to

https://patchwork.kernel.org/patch/9667025/

Failing with:

drivers/media/pci/saa716x/saa716x_pci.c: In function ‘saa716x_enable_msix’:
drivers/media/pci/saa716x/saa716x_pci.c:46:8: error: implicit declaration of function ‘pci_enable_msix’ [-Werror=implicit-function-declaration]
ret = pci_enable_msix(pdev, saa716x->msix_entries, SAA716x_MSI_MAX_VECTORS);
^~~~~~~~~~~~~~~

Obviously, there are quite a few more places where the build should fail, if it continued after the first failure.

I really hope that you guys can patch saa716x so it can live past linux-4.12.x.
Kind regards,
Tycho.

TBS 6909 Kernel 4.4.0-71 - TBSECP3 frontend 0 attach failed.

Hi. @crazycat69
Just updated my kernel and updated my card drivers now i get TBSECP3 frontend attach failed.
I dont know whats going on it says registering and failed on the same numbers but not showing 32 tuners?
What to do thank you.

[ 36.502707] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 0 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 36.579398] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 36.700700] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 2 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 36.796576] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 3 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 36.916593] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 4 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 37.028659] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 5 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 37.109126] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 6 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 37.230788] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 7 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 62.453879] TBSECP3 driver 0000:07:00.0: DVB: registering adapter 8 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 62.552673] TBSECP3 driver 0000:07:00.0: DVB: registering adapter 9 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 62.625264] TBSECP3 driver 0000:07:00.0: DVB: registering adapter 10 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 62.695869] TBSECP3 driver 0000:07:00.0: DVB: registering adapter 11 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 62.799870] TBSECP3 driver 0000:07:00.0: DVB: registering adapter 12 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 62.919852] TBSECP3 driver 0000:07:00.0: DVB: registering adapter 13 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 62.988065] TBSECP3 driver 0000:07:00.0: DVB: registering adapter 14 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 63.084404] TBSECP3 driver 0000:07:00.0: DVB: registering adapter 15 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[ 63.209636] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 0 attach failed
[ 63.209637] TBSECP3 driver 0000:09:00.0: frontend attach failed
[ 63.365895] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 1 attach failed
[ 63.365896] TBSECP3 driver 0000:09:00.0: frontend attach failed
[ 63.481883] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 2 attach failed
[ 63.481884] TBSECP3 driver 0000:09:00.0: frontend attach failed
[ 63.593715] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 3 attach failed
[ 63.593716] TBSECP3 driver 0000:09:00.0: frontend attach failed
[ 63.753893] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 4 attach failed
[ 63.753894] TBSECP3 driver 0000:09:00.0: frontend attach failed
[ 63.905860] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 5 attach failed
[ 63.905861] TBSECP3 driver 0000:09:00.0: frontend attach failed
[ 64.025849] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 6 attach failed
[ 64.025850] TBSECP3 driver 0000:09:00.0: frontend attach failed
[ 64.185843] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 7 attach failed
[ 64.185844] TBSECP3 driver 0000:09:00.0: frontend attach failed
[ 64.297841] TBSECP3 driver 0000:0a:00.0: TBSECP3 frontend 0 attach failed
[ 64.297842] TBSECP3 driver 0000:0a:00.0: frontend attach failed
[ 64.453818] TBSECP3 driver 0000:0a:00.0: TBSECP3 frontend 1 attach failed
[ 64.453819] TBSECP3 driver 0000:0a:00.0: frontend attach failed
[ 64.561545] TBSECP3 driver 0000:0a:00.0: TBSECP3 frontend 2 attach failed
[ 64.561546] TBSECP3 driver 0000:0a:00.0: frontend attach failed
[ 64.685385] TBSECP3 driver 0000:0a:00.0: TBSECP3 frontend 3 attach failed
[ 64.685387] TBSECP3 driver 0000:0a:00.0: frontend attach failed
[ 64.841859] TBSECP3 driver 0000:0a:00.0: TBSECP3 frontend 4 attach failed
[ 64.841860] TBSECP3 driver 0000:0a:00.0: frontend attach failed
[ 64.961833] TBSECP3 driver 0000:0a:00.0: TBSECP3 frontend 5 attach failed
[ 64.961834] TBSECP3 driver 0000:0a:00.0: frontend attach failed
[ 65.073801] TBSECP3 driver 0000:0a:00.0: TBSECP3 frontend 6 attach failed
[ 65.073802] TBSECP3 driver 0000:0a:00.0: frontend attach failed
[ 65.185676] TBSECP3 driver 0000:0a:00.0: TBSECP3 frontend 7 attach failed
[ 65.185677] TBSECP3 driver 0000:0a:00.0: frontend attach failed

TBS5990 Single interface working only

Using Linux raspberrypi 4.4.50-v7+ Kernel

Build works, both adapters and frontends appear.

root@raspberrypi:/etc/modprobe.d# ls /dev/dvb
adapter0 adapter1

However only single adaptor works. in dmesg continuous

[129049.167218] cx231xx 1-1.4:1.1: Unknown tuner type configuring SIF

pi@raspberrypi:~ $ lsusb
Bus 001 Device 004: ID 734c:5990 TBS Technologies China
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pi@raspberrypi:~ $ lsmod
Module Size Used by
cfg80211 428871 0
rfkill 16037 1 cfg80211
av201x 3701 2
cx231xx_dvb_ci 14788 0
tas2101 8975 3 cx231xx_dvb_ci
dvb_core 85726 1 cx231xx_dvb_ci
cx231xx_alsa 5821 0
snd_pcm 75762 1 cx231xx_alsa
snd_timer 19288 1 snd_pcm
snd 51908 3 cx231xx_alsa,snd_timer,snd_pcm
cx25840 48623 1
cx231xx 148837 2 cx231xx_alsa,cx231xx_dvb_ci
cx2341x 17304 1 cx231xx
videobuf_vmalloc 4893 1 cx231xx
videobuf_core 16667 2 cx231xx,videobuf_vmalloc
tveeprom 10846 1 cx231xx
rc_core 17983 1 cx231xx
i2c_mux 2457 2 cx231xx,tas2101
v4l2_common 3929 3 cx2341x,cx231xx,cx25840
videodev 140825 4 cx2341x,cx231xx,cx25840,v4l2_common
media 19205 4 cx231xx,cx25840,videodev,dvb_core
bcm2835_gpiomem 2976 0
bcm2835_wdt 3225 0
uio_pdrv_genirq 3164 0
uio 8000 1 uio_pdrv_genirq
ipv6 347620 30

/etc/modprobe.d/cx231xx.conf
options cx231xx transfer_mode=0
options disable infrared remote support

TBS6903 / Linux 4.10.12 Fedora 25 x86_64 kernel tried to execute NX-protected page - exploit attempt? (uid: 0)

Hi,

Compiled drivers with latest git (even though patches application do fail).

Trying

femon -H

Gives:

  1. femon is killed instantly by the system.
  2. dmesg gives:
[10259.314438] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
[10259.314563] BUG: unable to handle kernel paging request at ffff96b4c6fc0068
[10259.314665] IP: 0xffff96b4c6fc0068
[10259.314715] PGD 3c437d067 
[10259.314717] PUD 80d045063 
[10259.314757] PMD 406e50063 
[10259.314796] PTE 8000000406fc0163

[10259.314906] Oops: 0011 [#1] SMP
[10259.314953] Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_raw ip6table_security ip6table_mangle ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 iptable_raw iptable_security iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables stv6120(OE) stv0910(OE) amd64_edac_mod edac_mce_amd tbsecp3(OE) edac_core kvm_amd kvm tas2101(OE) irqbypass dvb_core sp5100_tco i2c_mux i2c_piix4 k10temp shpchp acpi_cpufreq tpm_tis tpm_tis_core tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc xfs libcrc32c ata_generic pata_acpi mgag200 drm_kms_helper ttm drm igb serio_raw ptp pata_atiixp pps_core dca 3w_9xxx i2c_algo_bit fjes
[10259.315920] CPU: 8 PID: 2543 Comm: femon Tainted: G           OE   4.10.12-200.fc25.x86_64 #1
[10259.316033] Hardware name: Supermicro H8DGU/H8DGU, BIOS 1.0a    07/01/2010
[10259.316126] task: ffff96b4c29c0000 task.stack: ffffb9f60705c000
[10259.316207] RIP: 0010:0xffff96b4c6fc0068
[10259.316263] RSP: 0018:ffffb9f60705fa60 EFLAGS: 00010202
[10259.316336] RAX: ffff96b4c6dee960 RBX: ffff96b4c6fc0050 RCX: 00000000ffff00f2
[10259.316430] RDX: 0000000000000002 RSI: 0000000000000002 RDI: ffff96b4c6fc0050
[10259.316525] RBP: ffffb9f60705fa80 R08: ffffb9f607060000 R09: 0000000000000000
[10259.316619] R10: 0000000000000002 R11: 0000000000000001 R12: ffffb9f60705fab0
[10259.316714] R13: 0000000000000002 R14: ffffb9f60705fad5 R15: ffff96b4c6d18400
[10259.316810] FS:  00007f73a07f6700(0000) GS:ffff96b8df680000(0000) knlGS:0000000000000000
[10259.316917] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[10259.316995] CR2: ffff96b4c6fc0068 CR3: 0000000809593000 CR4: 00000000000006e0
[10259.317090] Call Trace:
[10259.317137]  ? i2c_transfer+0x83/0xc0
[10259.317197]  read_status+0xc2/0x1740 [stv0910]
[10259.317265]  ? __enqueue_entity+0x6c/0x70
[10259.317339]  dvb_frontend_ioctl_legacy.isra.9+0xaa/0xbc0 [dvb_core]
[10259.317426]  ? check_preempt_wakeup+0x192/0x220
[10259.317491]  ? check_preempt_curr+0x79/0x90
[10259.317550]  ? ttwu_do_wakeup+0x19/0xe0
[10259.317606]  ? ttwu_do_activate+0x6f/0x80
[10259.317663]  ? try_to_wake_up+0x59/0x3d0
[10259.317720]  ? wake_up_process+0x15/0x20
[10259.317779]  ? insert_work+0xa2/0xf0
[10259.317831]  ? __queue_work+0x16a/0x460
[10259.321055]  ? tty_flip_buffer_push+0x2b/0x30
[10259.324282]  dvb_frontend_ioctl+0xb4/0x130 [dvb_core]
[10259.327507]  dvb_usercopy+0x5c/0x1d0 [dvb_core]
[10259.330721]  ? dvb_frontend_ioctl_properties+0xeb0/0xeb0 [dvb_core]
[10259.333918]  ? set_next_entity+0xc3/0x1a0
[10259.337056]  ? pick_next_task_fair+0x4a2/0x4d0
[10259.340135]  ? __switch_to+0x227/0x460
[10259.343140]  dvb_generic_ioctl+0x23/0x40 [dvb_core]
[10259.346122]  do_vfs_ioctl+0xa3/0x5f0
[10259.349113]  ? xen_build_mfn_list_list+0x255/0x420
[10259.352135]  SyS_ioctl+0x79/0x90
[10259.355181]  entry_SYSCALL_64_fastpath+0x1a/0xa9
[10259.358256] RIP: 0033:0x7f73a0114787
[10259.361332] RSP: 002b:00007fffab830958 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[10259.364513] RAX: ffffffffffffffda RBX: 0000000000000029 RCX: 00007f73a0114787
[10259.367633] RDX: 00007fffab830960 RSI: 0000000080046f45 RDI: 0000000000000003
[10259.370674] RBP: 000056103aad5060 R08: 0000000000000000 R09: 0000000000000029
[10259.373629] R10: 0000000000000073 R11: 0000000000000246 R12: 0000000000000029
[10259.376487] R13: 0000000000000001 R14: 00007f73a03d85e0 R15: 00007f73a03d43c0
[10259.379255] Code: 96 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50 0b fc c6 b4 96 ff ff 60 d0 6e c0 ff ff ff ff <60> ac 0a cc b4 96 ff ff 60 e9 de c6 b4 96 ff ff 3c 96 8a c0 ff 
[10259.384882] RIP: 0xffff96b4c6fc0068 RSP: ffffb9f60705fa60
[10259.387610] CR2: ffff96b4c6fc0068
[10259.403014] ---[ end trace 3ecf7e2a4ff3bc2a ]---

Launching again femon -H after that makes the command just being stuck.

Could someone help ?

How to find what version driver i am using?

How do I tell what version driver am I running?
I know I can update, but it would be nice to know what version I am running.
No need to update if i have the latest already installed.
Thank you.

Debian 9 /kernel 4.9.13-1 not compile -again-

/root/tbs_github/media_build/v4l/pt3.c: In function 'pt3_fetch_thread':
/root/tbs_github/media_build/v4l/pt3.c:466:9: error: incompatible types when assigning to type 'ktime_t {aka union ktime}' from type 'long int'
delay = PT3_FETCH_DELAY * NSEC_PER_MSEC;
^
/usr/src/linux-headers-4.9.0-2-common/scripts/Makefile.build:298: recipe for target '/root/tbs_github/media_build/v4l/pt3.o' failed
make[5]: *** [/root/tbs_github/media_build/v4l/pt3.o] Error 1
make[5]: *** Waiting for unfinished jobs....
/usr/src/linux-headers-4.9.0-2-common/Makefile:1507: recipe for target 'module/root/tbs_github/media_build/v4l' failed
make[4]: *** [module/root/tbs_github/media_build/v4l] Error 2
Makefile:150: recipe for target 'sub-make' failed
make[3]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-4.9.0-2-amd64'
Makefile:51: recipe for target 'default' failed
make[1]: *** [default] Error 2
make[1]: Leaving directory '/root/tbs_github/media_build/v4l'
Makefile:26: recipe for target 'all' failed
make: *** [all] Error 2

TBS6704: No signal strength

The mn88436 on the TBS6704 always returns 0 for signal strength. Both DMD_USR_IFAGCMON1 and DMD_USR_IFAGCMON1 return 0. Is this a byproduct of how the mn88436 and mxl603 are connected ( no agc feedback )? As in signal strength is just not available?

Thanks

TBS5281 suspend problem

I'm using the TBS8152 dvb-c USB module with Tvheadend 4.2 in Libreelec 8.0.0 environment. This Libreelec version uses the Linux 4.9.8 version.

I would like to sleep the system is used by Kodi Krypton suspend power-off option, but the system is freezed. If I have disconnected the USB modul from system the suspend process has worked correctly.
In next step I have rebooted and reconnected the USB hardware to Libreelec and I have tested the cx231xx module dependency tree by lsmod command:

lsmod | grep cx
cx231xx_dvb_ci         14873  0
tas2101                 8235  1 cx231xx_dvb_ci
dvb_core               82018  1 cx231xx_dvb_ci
cx25840               138349  1
cx231xx               147335  1 cx231xx_dvb_ci
videobuf_vmalloc        4231  1 cx231xx
videobuf_core          14600  2 cx231xx,videobuf_vmalloc
cx2341x                15535  1 cx231xx
i2c_mux                 4330  2 si2168,cx231xx
v4l2_common             3125  3 cx2341x,cx231xx,cx25840
tveeprom               13169  1 cx231xx
videodev              113087  4 cx2341x,v4l2_common,cx231xx,cx25840
rc_core                17350  4 `imon,rc_imon_pad,cx231xx

If I try to remove cx231xx dvb driver by using rmmod before suspend, it has sent the following message:

rmmod cx231xx
rmmod: ERROR: Module cx231xx is in use by: cx231xx_dvb_ci

After this I try to remove the cx231xx_dvb_ci driver, but rmmod sent a Killed message and after this doesn't removed the module:

rmmod cx231xx_dvb_ci
Killed

I think it doesn't normal message, may be it is a Linux kernel modul problem.

Can somebody help me?

PS: I'm sending some additional information:

modinfo cx231xx
filename:       /lib/modules/4.9.8/updates/cx231xx.ko
version:        0.0.3
license:        GPL
description:    Conexant cx231xx based USB video device driver
author:         Srinivasa Deevi <[email protected]>
firmware:       v4l-cx23885-enc.fw
srcversion:     69AE4B51D811435B01A920C
...
depends:        videobuf-core,videodev,v4l2-common,tveeprom,cx2341x,videobuf-vmalloc,rc-core
vermagic:       4.9.8 SMP mod_unload
parm:           pcb_debug:enable pcb config debug messages [video] (int)
parm:           mpegbufs:number of mpeg buffers, range 2-32 (int)
parm:           mpeglines:number of lines in an MPEG buffer, range 2-32 (int)
parm:           mpeglinesize:number of bytes in each line of an MPEG buffer, range 512-1024 (int)
parm:           v4l_debug:enable V4L debug messages (int)
parm:           core_debug:enable debug messages [core] (int)
parm:           reg_debug:enable debug messages [URB reg] (int)
parm:           alt:alternate setting to use for video endpoint (int)
parm:           tuner:tuner type (int)
parm:           transfer_mode:transfer mode (1-ISO or 0-BULK) (int)
parm:           disable_ir:disable infrared remote support (int)
parm:           i2c_scan:scan i2c bus at insmod time (int)
parm:           i2c_debug:enable debug messages [i2c] (int)
parm:           isoc_debug:enable debug messages [isoc transfers] (int)
parm:           card:card type (array of int)
parm:           video_nr:video device numbers (array of int)
parm:           vbi_nr:vbi device numbers (array of int)
parm:           radio_nr:radio device numbers (array of int)
parm:           video_debug:enable debug messages [video] (int)
modinfo cx231xx_dvb_ci
filename:       /lib/modules/4.9.8/updates/cx231xx-dvb-ci.ko
license:        GPL
author:         Srinivasa Deevi <[email protected]>
description:    driver for cx231xx based DVB cards
depends:        cx231xx,dvb-core,tas2101
vermagic:       4.9.8 SMP mod_unload
parm:           debug:enable debug messages [dvb] (int)
parm:           adapter_nr:DVB adapter numbers (array of short)
modinfo si2168
filename:       /lib/modules/4.9.8/updates/si2168.ko
firmware:       dvb-demod-si2168-b40-01.fw
firmware:       dvb-demod-si2168-a30-01.fw
firmware:       dvb-demod-si2168-a20-01.fw
license:        GPL
description:    Silicon Labs Si2168 DVB-T/T2/C demodulator driver
author:         Antti Palosaari <[email protected]>
alias:          i2c:si2168
depends:
vermagic:       4.9.8 SMP mod_unload
modinfo si2157
filename:       /lib/modules/4.9.8/updates/si2157.ko
firmware:       dvb-tuner-si2141-a10-01.fw
firmware:       dvb-tuner-si2158-a20-01.fw
license:        GPL
author:         Antti Palosaari <[email protected]>
description:    Silicon Labs Si2146/2147/2148/2157/2158 silicon tuner driver
alias:          i2c:si2141
alias:          i2c:si2146
alias:          i2c:si2157
depends:
vermagic:       4.9.8 SMP mod_unload

TBS 6909 - modprobe what?

Hello,

In the TBS (not open source) you do "modprobe tbs_pcie-dvb" to load 6909.
But what do you run in in there open source one?

modprobe tbs_pcie-dvb
modprobe: FATAL: Module tbs_pcie-dvb not found.

TBS-6290 SE DVB CAM not recognized

Hello all,

Yesterday I just compile these nice TBS open source drivers the card works ok, but my SMIT module is not recognized.

dmesg log says:

dvb_ca_en50221: dvb_ca adapter 0: DVB CAM link initialisation failed :(

uname -r
4.4.56-1.el7.elrepo.x86_64
CentOS Linux release 7.3.1611 (Core)

With original closed TBS drivers CI works good.

media_build errors for kernel 4.9

building fails with media_build for kernel 4.9.0

  CC [M]  /LE/tbs/media_build/v4l/e4000.o
  CC [M]  /LE/tbs/media_build/v4l/fc2580.o
  CC [M]  /LE/tbs/media_build/v4l/tua9001.o
  CC [M]  /LE/tbs/media_build/v4l/si2157.o
  CC [M]  /LE/tbs/media_build/v4l/fc0011.o
  CC [M]  /LE/tbs/media_build/v4l/fc0012.o
  CC [M]  /LE/tbs/media_build/v4l/fc0013.o
/LE/tbs/media_build/v4l/tda18273.c:2144:13: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
  .release  = tda18273_release
             ^~~~~~~~~~~~~~~~
/LE/tbs/media_build/v4l/tda18273.c:2144:13: note: (near initialization for 'tda18273_ops.release')
cc1: some warnings being treated as errors
make[4]: *** [scripts/Makefile.build:299: /LE/tbs/media_build/v4l/tda18273.o] Error 1

after disabling TDA18273 I got these errors http://pastebin.com/VHPjXXic

I ended up to disable these modules in media_build/v4l/versions.txt to get it working.

MEDIA_TUNER_TDA18273
MEDIA_TUNER_STV6120
MEDIA_TUNER_R848
MEDIA_TUNER_AV201X

latest version compile fails

/root/builds/media_build/v4l/em28xx-dvb.c:45:31: fatal error: drx39xyj/drx39xxj.h: No such file or directory
#include "drx39xyj/drx39xxj.h"

Build Error Ubuntu 16.04.04 Kernel 4.8.0-34-generic

make[2]: Entering directory '/usr/src/linux-headers-4.8.0-34-generic'
CC [M] /usr/local/src/tbs-oss/media_build/v4l/em28xx-dvb.o
/usr/local/src/tbs-oss/media_build/v4l/em28xx-dvb.c:47:31: fatal error: drx39xyj/drx39xxj.h: No such file or directory
compilation terminated.
scripts/Makefile.build:295: die Regel für Ziel „/usr/local/src/tbs-oss/media_build/v4l/em28xx-dvb.o“ scheiterte

[Kernel 4.9][TBS 6982] VERY slow channel switching

I am using an TBS 6982 with TVheadend on Debian Stretch with the latest kernel 4.9.
I'm using the latest version of this driver.
However, compared to an older version from 08/2016 with Kernel 4.6, I got significantly slower channel switching (about 10 seconds).

I could not find any hints on the cause of these very high switching times. Is this a known problem?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.