Moderator Control Panel ]

Solved: TBS6909 driver installation on Proxmox VE 6.3

It's important to keep your driver and software updated.

Solved: TBS6909 driver installation on Proxmox VE 6.3

Postby hsmptg » Wed Feb 10, 2021 7:57 pm

Hi

I have a running TBS6909 on a Proxmox VE (version 5.4 with kernel 4.15.18-14-pve) server.
Now I tried to do the same but now on an updated Proxmox VE (version 6.3 with kernel 5.4.78-2-pve).
I followed the instructions that can be seen here: https://github.com/tbsdtv/linux_media/wiki

After command make allyesconfig I got this:
Code: Select All Code
root@pve:~/media_build# make allyesconfig
...
WARNING: This is the V4L/DVB backport tree, with experimental drivers
         backported to run on legacy kernels from the development tree at:
                http://git.linuxtv.org/media-tree.git.
         It is generally safe to use it for testing a new driver or
         feature, but its usage on production environments is risky.
         Don't use it in production. You've been warned.
CEC_CROS_EC: Requires at least kernel 9.255.255
V4L2_H264: Requires at least kernel 9.255.255
VIDEO_IPU3_CIO2: Requires at least kernel 9.255.255
VIDEO_OMAP3: Requires at least kernel 9.255.255
VIDEO_IMX274: Requires at least kernel 9.255.255
SND_BT87X: Requires at least kernel 9.255.255
INTEL_ATOMISP: Requires at least kernel 9.255.255
VIDEO_HANTRO: Requires at least kernel 9.255.255
VIDEO_ROCKCHIP_VDEC: Requires at least kernel 9.255.255
VIDEO_IPU3_IMGU: Requires at least kernel 9.255.255
Created default (all yes) .config file
./scripts/fix_kconfig.pl
make[1]: Leaving directory '/root/media_build/v4l'

The "Requires at least kernel 9.255.255" sounds like an error, right?

Nevertheless I was able to run the "make -j4" command apparently with no errors:
Code: Select All Code
root@pve:~/media_build# make -j4
...
  LD [M]  /root/media_build/v4l/zd1301.ko
  LD [M]  /root/media_build/v4l/zd1301_demod.ko
  LD [M]  /root/media_build/v4l/zl10036.ko
  LD [M]  /root/media_build/v4l/zl10039.ko
  LD [M]  /root/media_build/v4l/zl10353.ko
  LD [M]  /root/media_build/v4l/zr364xx.ko
make[2]: Leaving directory '/usr/src/linux-headers-5.4.73-1-pve'
./scripts/rmmod.pl check
found 742 modules
make[1]: Leaving directory '/root/media_build/v4l'


It is strange because during the compilation I do not see any reference to the TBS6909 board unlike many others:
Code: Select All Code
root@pve:~/media_build# ls /root/media_build/v4l/tbs69*
ls: cannot access '/root/media_build/v4l/tbs69*': No such file or directory


Finally, after a reboot I do not see any /dev/dvb devices, something that I also can check if I do:
Code: Select All Code
root@pve:~# dmesg | grep frontend
root@pve:~#


Any help on this?
My guess is that kernel 5.4.78-2-pve is too new to these DVB drivers, right?

Regards
Last edited by hsmptg on Thu Feb 11, 2021 1:48 am, edited 1 time in total.
hsmptg
 
Posts: 7
Joined: Sun May 12, 2019 5:13 am

Re: TBS6909 driver installation on Proxmox VE 6.3

Postby hsmptg » Wed Feb 10, 2021 10:04 pm

Hi again

I just noticed in my last post that in the end of command "make -j4" I got:
Code: Select All Code
make[2]: Leaving directory '/usr/src/linux-headers-5.4.73-1-pve'

What is strange since my current kernet is the 5.4.78-2-pve!

The problem was that when I did the "apt update && apt -y upgrade", the kernel was upgraded from the one I had after installing Proxmox VE 6.3 (5.4.73-1-pve) to a new one (5.4.78-2-pve), and since I IMMEDIATELY after that did:
Code: Select All Code
apt-cache search pve-headers
apt install pve-headers-$(uname -r)

The "uname -r" still returned the older kernel version and therefore the linux-headers I used in the driver compilation were the old ones.

So, this time I repeated the process on a new Proxmox installation but this time after the "apt update && apt -y upgrade" I did a reboot and therefore the linux-headers installed after that were already related with the updated kernel 5.4.78-2-pve.

I still got the odd "Requires at least kernel 9.255.255" messages but at least the "make -j4" command ended mentioning the right folder:
Code: Select All Code
root@pve:~/media_build# make -j4
...
  LD [M]  /root/media_build/v4l/zd1301.ko
  LD [M]  /root/media_build/v4l/zd1301_demod.ko
  LD [M]  /root/media_build/v4l/zl10036.ko
  LD [M]  /root/media_build/v4l/zl10039.ko
  LD [M]  /root/media_build/v4l/zl10353.ko
  LD [M]  /root/media_build/v4l/zr364xx.ko
make[2]: Leaving directory '/usr/src/linux-headers-5.4.78-2-pve'
./scripts/rmmod.pl check
found 742 modules
make[1]: Leaving directory '/root/media_build/v4l'


Keeps me wondering why in the /root/media_build/v4l folder I still do not see any mention to my tbs6909 board when I see a bunch of tbs5xxx boards.

But now, at least I can already see the FAILED attempts during the boot to connect my board:
Code: Select All Code
root@pve:~# dmesg | grep frontend
                4d2b65a0e8661ba2bd20d28d21db99846eafe4a8 media: dvb-frontends/stid135: Extended VGLNA support.
                4d2b65a0e8661ba2bd20d28d21db99846eafe4a8 media: dvb-frontends/stid135: Extended VGLNA support.
                4d2b65a0e8661ba2bd20d28d21db99846eafe4a8 media: dvb-frontends/stid135: Extended VGLNA support.
[    6.543979] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 0 attach failed
[    6.543983] TBSECP3 driver 0000:09:00.0: frontend attach failed
[    6.711355] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 1 attach failed
[    6.711359] TBSECP3 driver 0000:09:00.0: frontend attach failed
[    6.875268] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 2 attach failed
[    6.875278] TBSECP3 driver 0000:09:00.0: frontend attach failed
[    7.047474] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 3 attach failed
[    7.047478] TBSECP3 driver 0000:09:00.0: frontend attach failed
[    7.215376] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 4 attach failed
[    7.215379] TBSECP3 driver 0000:09:00.0: frontend attach failed
[    7.383513] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 5 attach failed
[    7.383516] TBSECP3 driver 0000:09:00.0: frontend attach failed
[    7.551513] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 6 attach failed
[    7.551516] TBSECP3 driver 0000:09:00.0: frontend attach failed
[    7.719378] TBSECP3 driver 0000:09:00.0: TBSECP3 frontend 7 attach failed
[    7.719381] TBSECP3 driver 0000:09:00.0: frontend attach failed

That are pretty close of what I want to see (like the one I used to had in my older Proxmox):
Code: Select All Code
root@pve:~# dmesg | grep frontend
[   33.286869] TBSECP3 driver 0000:0a:00.0: DVB: registering adapter 0 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   33.408993] TBSECP3 driver 0000:0a:00.0: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   33.532632] TBSECP3 driver 0000:0a:00.0: DVB: registering adapter 2 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   33.656702] TBSECP3 driver 0000:0a:00.0: DVB: registering adapter 3 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   33.780999] TBSECP3 driver 0000:0a:00.0: DVB: registering adapter 4 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   33.904987] TBSECP3 driver 0000:0a:00.0: DVB: registering adapter 5 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   34.028999] TBSECP3 driver 0000:0a:00.0: DVB: registering adapter 6 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   34.153004] TBSECP3 driver 0000:0a:00.0: DVB: registering adapter 7 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...


Could you please give me an hint on what to do?
Regards
hsmptg
 
Posts: 7
Joined: Sun May 12, 2019 5:13 am

Re: TBS6909 driver installation on Proxmox VE 6.3

Postby hsmptg » Thu Feb 11, 2021 1:44 am

Hi
Meanwhile I solved the problem!

Instead of using the procedure described here: https://github.com/tbsdtv/linux_media/wiki, I used the one described inside the zip of the "TBS Open Source Linux Driver Offline Package" that can be obtained here: https://www.tbsdtv.com/download/index.html?path=3_13
In the case of my board (TBS6909) I got the "TBS Open Source Linux Driver Offline Package v20201204", where the steps are the following:

Code: Select All Code
wget http://www.tbsdtv.com/download/document/linux/media_build-2020-12-04.tar.bz2
rm -rf /lib/modules/`uname -r`/kernel/drivers/media/
tar jxvf media_build-2020-12-04.tar.bz2
cd media_build
./install.sh
reboot


IMPORTANT:

1. In my case, where I want to install the driver in a Proxmox server where the default user is already the root, I had to edit the install.sh by removing all the "sudo" to avoid errors during the ./install.sh.

2. Do not forget to install the linux-headers (in this case the pve-headers) BEFORE the procedure described above:
Code: Select All Code
apt-cache search pve-headers
apt install pve-headers-$(uname -r)
reboot


After all this, I finally got what I wanted:
Code: Select All Code
root@pve:~# dmesg | grep frontend
[   32.494217] TBSECP3 driver 0000:09:00.0: DVB: registering adapter 0 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   32.617803] TBSECP3 driver 0000:09:00.0: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   32.741035] TBSECP3 driver 0000:09:00.0: DVB: registering adapter 2 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   32.864554] TBSECP3 driver 0000:09:00.0: DVB: registering adapter 3 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   32.988870] TBSECP3 driver 0000:09:00.0: DVB: registering adapter 4 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   33.114499] TBSECP3 driver 0000:09:00.0: DVB: registering adapter 5 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   33.239971] TBSECP3 driver 0000:09:00.0: DVB: registering adapter 6 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
[   33.364305] TBSECP3 driver 0000:09:00.0: DVB: registering adapter 7 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...


Regards
hsmptg
 
Posts: 7
Joined: Sun May 12, 2019 5:13 am


Return to Driver & Software Update

Who is online

Users browsing this forum: No registered users and 15 guests