Tvheadend

Some random thoughts:

Do you see any error messages in your system log or TVH log relating to your adapters?

Could there be a hardware fault with ‘adapter0’?

If you remove all other adapters, does adapter0 show up in TVH?

I read that the Linux Kernel supports a maximum of 8 adapters. Did you rebuild your kernel or something to be able to get 11?

Have you installed the firmware for all of the adapter types?

no error in system log.
all adapters was working well in previous instalation of ubuntu 22 , i just made a new and clean instalation , same ubuntu same drivers and same firmware.
in previus was 12 correctly detected so no limit of 8.

I see sometimes afther a reboot all adapter are listed ( included adapter 0) and afther a new reboot or few more reboot the adapter 0 dissapear again .

TBS firmware/drivers notoriously break after kernel updates. This thread is definitely worth a read https://tvheadend.org/boards/5/topics/27406

dtv2 dtv2 wrote:

I see sometimes afther a reboot all adapter are listed ( included adapter 0) and afther a new reboot or few more reboot the adapter 0 dissapear again .

That sounds like a timing issue. What happens if you restart Tvheadend after boot?

if a use "systemctl restart tvheadend" the adapter 0 is listed correct.

Edit the tvheadend.service file and add "ExecStartPre=/usr/bin/sleep 10" before the existing "ExecStart" line then save/close and "systemctl daemon reload" to update the boot tasks, then make some reboots to test. The change will force a ten second delay in Tvheadend startup to give more time for adapters to finish probing before Tvheadend starts and looks for them.

can you be more specific where is located the file tvheadend.service ?

Probably in /etc/systemd/system/tvheadend.service if using Debian/Ubuntu. If needed "sudo find / -name tvheadend.service" should 'find' it.

seem to be in 3 location, sould have edit all 3?
/usr/lib/systemd/system/tvheadend.service
/etc/systemd/system/multi-user.target.wants/tvheadend.service
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/tvheadend.service

The correct file is /usr/lib/systemd/system/tvheadend.service - the others are symlinks (not files) created by systemd for dependency scheduling.

i added the 10s delay but still the same. (adapter 0 not appear)

[Service]
EnvironmentFile=/etc/default/tvheadend
ExecStartPre=/usr/bin/sleep 10
ExecStart=/usr/bin/tvheadend -f -p /run/tvheadend.pid $OPTIONS

afther many test (reboot and systemctl restart)
afther a reboot adapter 0 appear +- 50% of time.
afther a "systemctl restart tvheadend" adapter 0 appear always.

Experiment with longer sleep values?

i did whit 15 and 20 but same.

Run "journalctl -b0 --no-pager" a couple of mins after booting and pastebin the log output.

Don't find where a systemd file is to edit it with a normal file editor. Instead:

systemctl edit <name of service>

Read up about systemd override files and the whole mechanism if you want to understand why.

atached i post log whit journalctl.

The start of the log is missing so it's not possible to see total time since boot started, however:

jan 31 12:59:07 david-MS-7788 tvheadend⁶⁶⁹: main: Log started
^ Tvheadend is executed
...
jan 31 12:59:09 david-MS-7788 kernel: UBSAN: array-index-out-of-bounds in /home/david/media_build/v4l/mxl58x.c:1024:22
jan 31 12:59:09 david-MS-7788 kernel: index 34084 is out of range for type 'u8 [1]'
^ buggy driver included with TBS media_build; probably needs to be u16 not u8
...
jan 31 12:59:15 david-MS-7788 tvheadend⁶⁶⁹: START: HTS Tvheadend version 4.3-2201~g6229a74aa started, running as PID:669 UID:128 GID:44, CWD:/ CNF:/var/lib/tvheadend
^ Tvheadend completes startup
...
jan 31 12:59:31 david-MS-7788 kernel: TBSECP3 driver 0000:01:00.0: DVB: registering adapter 0 frontend 0 (TurboSight TBS 6909 DVB-S/S2 )...
jan 31 12:59:31 david-MS-7788 kernel: dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter)
jan 31 12:59:31 david-MS-7788 kernel: TBSECP3 driver 0000:01:00.0: MAC address 00:22:ab:92:8c:69
^ adapters start being registered
...
jan 31 12:59:32 david-MS-7788 kernel: TBSECP3 driver 0000:01:00.0: TurboSight TBS 6909 DVB-S/S2 : PCI 0000:01:00.0, IRQ 27, MMIO 0xf7d00000
jan 31 12:59:32 david-MS-7788 kernel: TBSECP3 driver 0000:02:00.0: enabling device (0100 -> 0102)
jan 31 12:59:32 david-MS-7788 kernel: TBSECP3 driver 0000:02:00.0: TurboSight TBS 6904 DVB-S/S2
jan 31 12:59:33 david-MS-7788 kernel: TBSECP3 driver 0000:02:00.0: DVB: registering adapter 11 frontend 0 (TurboSight TBS 6904 DVB-S/S2 )...
jan 31 12:59:33 david-MS-7788 kernel: TBSECP3 driver 0000:02:00.0: TurboSight TBS 6904 DVB-S/S2 : PCI 0000:02:00.0, IRQ 30, MMIO 0xf7c00000
^ last adapter is registered by the kernel
...
jan 31 12:59:33 david-MS-7788 tvheadend⁶⁶⁹: linuxdvb: adapter added /dev/dvb/adapter1
jan 31 12:59:33 david-MS-7788 tvheadend⁶⁶⁹: linuxdvb: adapter added /dev/dvb/adapter2
jan 31 12:59:33 david-MS-7788 tvheadend⁶⁶⁹: linuxdvb: adapter added /dev/dvb/adapter3
jan 31 12:59:33 david-MS-7788 tvheadend⁶⁶⁹: linuxdvb: adapter added /dev/dvb/adapter4
jan 31 12:59:33 david-MS-7788 tvheadend⁶⁶⁹: linuxdvb: adapter added /dev/dvb/adapter5
jan 31 12:59:33 david-MS-7788 tvheadend⁶⁶⁹: linuxdvb: adapter added /dev/dvb/adapter6
jan 31 12:59:33 david-MS-7788 tvheadend⁶⁶⁹: linuxdvb: adapter added /dev/dvb/adapter7
jan 31 12:59:33 david-MS-7788 tvheadend⁶⁶⁹: linuxdvb: adapter added /dev/dvb/adapter8
jan 31 12:59:34 david-MS-7788 tvheadend⁶⁶⁹: linuxdvb: adapter added /dev/dvb/adapter9
jan 31 12:59:34 david-MS-7788 tvheadend⁶⁶⁹: linuxdvb: adapter added /dev/dvb/adapter10
jan 31 12:59:35 david-MS-7788 tvheadend⁶⁶⁹: linuxdvb: adapter added /dev/dvb/adapter11
^ addition of adapter0 is not logged

I'm 'new' to the world of Tvheadend so I'm unsure if the +18 second difference between Tvheadend completing startup (+26 seconds from execution) and the kernel drivers finishing adapter registration is a problem or not, but the later 'tvheadend⁶⁶⁹' messages that show adapters being added to tvheadend do not show adapter0.

Just to test, is there any difference with the sleep value increased to 60 seconds?

NB: It would be interesting to see what is logged in the journal when you manually restart tvheadend.

65 second do the trick, now 3x times rebooted and 3x appear adapter 0.
this fresh install of ubuntu 22 was made to change the old HDD to a new SSD maybe now some process start more fast and that why the delay needed.

Yes it has been reported in other forums that the change from traditional HDD to SSD has affected TVH’s ability to load tuners before the network is up. It seems that the improvements in boot times using SSD as a boot source has had unintended consequences. You can now see that delaying network start times until all related hardware is up can resolve this problem. You can also see that mentioning initially a complete list of hardware and OS along with some form of boot logs would have speeded up the troubleshooting process for others on your behalf.

TBS drivers are worst any kernel update = no driver
Octo tuners load modules very slow, TVH start before this, service restart helping sometime .
use this script CLICK
run install and restart when asked
DON'T USE UEFI & Secure Boot ... USE LEGACY