femon -a0 "opening frontend failed: No such file or directory"
|
nigel
Hi folks,
I would appreciate some help with the above error I am getting when trying to get info from my TBS 6903 card mounted in a Debian 11 (Bullseye) desktop machine. Basic Service is being received well and I would like to use MRTG to plot things like Signal Strength and, hopefully, Link Margin. The card is using TBS drivers installed from https://www.tbsdtv.com/download/document/linux/media_build-2022-04-24.tar.bz2 If anyone can point me in the right direction I would be very grateful - I've googled and read all I can find, but nothing seems to answer my question! Many thanks Nigel |
|
|
|
Ernst Lobsiger
On Mon, Dec 26, 2022 at 05:46 AM, nigel wrote:
Basic Service is being received wellNigel, does this mean that the TBS-6903 card has been tuned to C4 and if you issue (as root!) # dvbtraffic -a0 and # dvbtraffic -a1 do work while # femon -a0 and # femon -a1 does not? Ernst |
|
|
|
nigel
Hi Ernst, thanks for your reply. I'm presuming the card is tuned to C4 - not sure how to check that? I've only got Basic Service working at the moment, on this machine ( /etc/tellicast-client.cfg has "INSTANCE_START_ORDER=bas" ) dvbtraffic doesn't work either:- root@debian:/home/nigel# dvbtraffic -a0 root@debian:/home/nigel# dvbtraffic -a1
Does that help any ?? Regards Nigel
On 26/12/2022 16:03, Ernst Lobsiger via
groups.io wrote:
On Mon, Dec 26, 2022 at 05:46 AM, nigel wrote: |
|
|
|
Ernst Lobsiger
Nigel,
your card is not tuned and so your BAS cannot work either *except for* if you get the respective UDP traffic somehow from your SR1 via the LAN. IIRC you had such a situation before. To tune your card you must make sure (service) dvb-eumetcast is properly setup in /etc/dvb-eumetcast.cfg. Have you installed that package at all? If not take the latest (new_versions) that runs without smcroute (distributed e.g. in E1B-Info-Channel-1). Maybe everything is setup but dvb-eumetcast and tellicast-client is just not started automatically (I do setup it that way). You can also tune your card manually (just to check it's working) with # szap-s2 -c /etc/channels.conf -n (line number) Regards, Ernst |
|
|
|
nigel
Oh wow - thank you Ernst. Yes I did have that situation before. I'll do the checks and installations as you say and report back
during this coming week. Hopefully that will resolve my problems. Many thanks for your insight. Regards Nigel On 26/12/2022 17:04, Ernst Lobsiger via
groups.io wrote:
Nigel, |
|
|
|
nigel
Good morning Ernst, For some reason, I had not installed dvb-eumetcast but have now done so, using the latest version in E1B-info-Channel-1, Linux, new versions. I've also checked out /etc/dvb-eumetcast.cfg and made sure its service starts at boot up. Checking on its status, after boot, shows :- ================================================================== root@debian:/home/nigel# systemctl status dvb-eumetcast ================================================================= I've also re installed the tbsdtv
driver mentioned in my earlier email.
lspci -v, as root, shows the card but,
interestingly, it doesn't show what driver is being used - all the
other devices listed show, at the end of the detail, the kernel
module and driver - here are the last two in the list :-
==================================================================
03:00.0 Ethernet controller: Realtek
Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit
Ethernet Controller (rev 03)
Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet Flags: bus master, fast devsel, latency 0, IRQ 17 I/O ports at de00 [size=256] Memory at fddff000 (64-bit, prefetchable) [size=4K] Memory at fddf8000 (64-bit, prefetchable) [size=16K] Expansion ROM at fde00000 [virtual] [disabled] [size=128K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [ac] MSI-X: Enable+ Count=4 Masked- Capabilities: [cc] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 03-00-00-00-68-4c-e0-00 Kernel driver in use: r8169 Kernel modules: r8169 04:00.0 Multimedia controller: TBS Technologies DVB Tuner PCIe Card Subsystem: Device 6903:0001 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at fdcc0000 (32-bit, non-prefetchable) [size=256K] Capabilities: [50] Power Management version 3 Capabilities: [70] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [90] Express Endpoint, MSI 00 Capabilities: [100] Device Serial Number 00-00-00-00-00-00-00-00 ================================================================= Listing /dev/dvb* shows :-
root@debian:/home/nigel# ls -l
/dev/dvb*
ls: cannot access '/dev/dvb*': No such file or directory Running szap2 shows :-
=================================================================
root@debian:/home/nigel# szap-s2 -c
/etc/channels.conf -n 4
reading channels from file '/etc/channels.conf' zapping to 4 'E1B': delivery DVB-S2, modulation QPSK sat 0, frequency 11263 MHz H, symbolrate 33000000, coderate auto, rolloff 0.35 stream_id 1 modcode 0xffffffff vpid 0x1fff, apid 0x1fff, sid 0x0000 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' opening frontend failed: No such file or directory ================================================================= So, I'm no further forward - everything
seems to point to the card not showing up as a /dev/dvb device.
When you get a few spare moments I
would appreciate your further thoughts.
I'm wondering if I should start again,
from a fresh Debian install but would prefer to find out what the
problem is that I have. That way I should learn something !
Many thanks for your help
Regards
Nigel
On 26/12/2022 17:04, Ernst Lobsiger via
groups.io wrote:
Nigel, |
|
|
|
nigel
p.s. I found that the previous UDP traffic WAS coming from the SR1 Management port, via my LAN, as you correctly assumed. I have disconnected that port, for the time being, until I can investigate the SR1 configuration. N On 26/12/2022 17:04, Ernst Lobsiger via
groups.io wrote:
Nigel, |
|
|
|
Ernst Lobsiger
Nigel,
your TBS driver seems not to load properly. I wonder how you have installed it. If your system is up and running you can make a # dmesg | grep -E 'adapter|dvb' and you should see your adapter(s) registering. I have no TBS-6903 setup right now. Below is what I get on ganymed (TBS-5930 USB box) and on luna (TBS-6909X): root@ganymed:~# dmesg | grep -E 'adapter|dvb' [ 7.459662] dvb-usb: found a 'TurboSight TBS 5930 DVB-S/S2/S2x' in cold state, will try to load a firmware [ 7.558244] usb 7-1: firmware: direct-loading firmware dvb-usb-id5930.fw [ 7.558249] dvb-usb: downloading firmware from file 'dvb-usb-id5930.fw' [ 7.680258] dvb-usb: found a 'TurboSight TBS 5930 DVB-S/S2/S2x' in warm state. [ 7.680312] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 7.680475] dvbdev: DVB: registering new adapter (TurboSight TBS 5930 DVB-S/S2/S2x) [ 7.873832] dvb-usb: MAC address: 00:22:ab:c0:5f:40 [ 8.141537] i2c i2c-8: firmware: direct-loading firmware dvb-demod-m88rs6060.fw [ 8.141541] i2c i2c-8: downloading firmware from file 'dvb-demod-m88rs6060.fw' [ 9.688260] usb 7-1: DVB: registering adapter 0 frontend 0 (TurboSight TBS 5930 DVB-S/S2/S2x)... [ 9.688582] dvb-usb: TurboSight TBS 5930 DVB-S/S2/S2x successfully initialized and connected. [ 93.199920] dvb_net: created network interface dvb0_0 [ 93.240442] dvbond0: (slave dvb0_0): Enslaving as an active interface with an up link [ 93.240463] IPv6: ADDRCONF(NETDEV_CHANGE): dvbond0: link becomes ready root@ganymed:~# root@luna:~# dmesg | grep -E 'adapter|dvb' 5546b9ecae90c1b663f6694a83dd384904a425da media: dvb-frontends/stid135: option ts_nosync - TS FIFO Minimum latence mode. 5546b9ecae90c1b663f6694a83dd384904a425da media: dvb-frontends/stid135: option ts_nosync - TS FIFO Minimum latence mode. [ 5.177792] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 7.223490] TBSECP3 driver 0000:03:00.0: DVB: registering adapter 0 frontend 0 (TurboSight TBS 6909x (Octa DVB-S/S2/S2X))... [ 7.223605] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 7.345035] TBSECP3 driver 0000:03:00.0: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6909x (Octa DVB-S/S2/S2X))... [ 7.345191] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 7.446112] TBSECP3 driver 0000:03:00.0: DVB: registering adapter 2 frontend 0 (TurboSight TBS 6909x (Octa DVB-S/S2/S2X))... [ 7.446257] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 7.567953] TBSECP3 driver 0000:03:00.0: DVB: registering adapter 3 frontend 0 (TurboSight TBS 6909x (Octa DVB-S/S2/S2X))... [ 7.568093] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 7.689717] TBSECP3 driver 0000:03:00.0: DVB: registering adapter 4 frontend 0 (TurboSight TBS 6909x (Octa DVB-S/S2/S2X))... [ 7.689867] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 7.811582] TBSECP3 driver 0000:03:00.0: DVB: registering adapter 5 frontend 0 (TurboSight TBS 6909x (Octa DVB-S/S2/S2X))... [ 7.811720] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 7.933330] TBSECP3 driver 0000:03:00.0: DVB: registering adapter 6 frontend 0 (TurboSight TBS 6909x (Octa DVB-S/S2/S2X))... [ 7.933476] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 8.055166] TBSECP3 driver 0000:03:00.0: DVB: registering adapter 7 frontend 0 (TurboSight TBS 6909x (Octa DVB-S/S2/S2X))... root@luna:~# Ooops, on Ganymed I *had* a TBS-6903 before Christmas. And I can still find ... root@ganymed:~# zcat /var/log/dmesg.3.gz | grep -E 'adapter|dvb|6903' [ 6.901489] TBSECP3 driver 0000:01:00.0: TurboSight TBS 6903 DVB-S/S2 [ 6.901898] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 7.515440] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 0 frontend 0 (TurboSight TBS 6903 DVB-S/S2 )... [ 7.515509] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 7.638474] TBSECP3 driver 0000:01:00.0: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6903 DVB-S/S2 )... [ 7.638580] TBSECP3 driver 0000:01:00.0: TurboSight TBS 6903 DVB-S/S2 : PCI 0000:01:00.0, IRQ 16, MMIO 0xfc400000 root@ganymed:~# Hope this helps. I propose we handle that driver problem with PMs. Regards, Ernst Am 27.12.2022 09:52, schrieb nigel: ... So, I'm no further forward - everything seems to point to the card not... |
|
|
|
George Sz
Nigel,
In case if you have Secure Boot on, try disabling it. TBS drivers may not be digitally signed, so they'll refuse to load if you have Secure Boot on. I ran into this problem with the open source drivers which are definitely not signed by default. Regards, George |
|
|
|
nigel
Thank you for that idea, George. I'm very happy to say that my problem is now resolved, thanks to lots of help and advice from Ernst. He has a script that gets all the latest drivers, compiles them locally and installs them That worked like a charm for me this morning. I still don't understand why the TBS method didn't work here but suffice it to say my Debian system is now up and running, receiving the Basic service well. Regards Nigel
On 28/12/2022 11:10, George Sz wrote:
Nigel, |
|
|
|
George Sz
Glad you got it sorted, Nigel.
I just hope that TBS submits their drivers properly so this compilation madness won't be necessary. Maybe one day... Regards, George |
|
|