/dev/dvb passthrough #103
Comments
|
According to the config.yaml addon-tvheadend/tvheadend/config.yaml Lines 20 to 21 in 405f218 At least for |
|
Hi
Thanks in advance! UPDATE: this seems to be an old issue: devices:
...doesn't show the dvb-adapter. Also 1 out of 2 fritzbox/sat>ip is visible. Keeping / dev/dvb as in your config, keeps the fritzbox/sat>ip both visible in tvheadend. |
|
Nice, thanks for the details. I will have a deeper look into the other issue and check what I can do. Could you please let me know which DVB tuner you are using? In case it's not too expensive, I'll consider buying one 😄. Also what's your machine & architecture running HAOS? |
|
Hi
You can see the card from the dmesg: a TBS and a DigitalDevices satix 2
If you are willing to invest time, I have a spare TBS here and I can send
it to you.
Regards
R
Op di 13 feb. 2024 21:44 schreef Daniel Figus ***@***.***>:
… Nice, thanks for the details. I will have a deeper look into the other
issue and check what I can do. Could you please let me know which DVB tuner
you are using? In case it's not too expensive, I'll consider buying one 😄.
Also what's your machine & architecture running HAOS?
—
Reply to this email directly, view it on GitHub
<#103 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD42FMFIXLFOH2KGRAVPSMLYTPGCBAVCNFSM6AAAAABDEFOQRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBSGQ2TOOBXGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Hi, few days ago I post my problem on the link you refer too (GauthamVarmaK/addon-tvheadend#45 (comment)). Your addon config is a little bit different, but I dont think it matter for this issue. |
@rucati: It looks like those are PCI express cards and I just run it on a PI4 - hence I can't use them 😞 . Furthermore I created a discussion #107 about Webgrab+, let's discuss it there. |
|
@rucati I don't think it's a permission issue as in my addon TVHeadend runs as root and should therefore have all authorizations to access the devices. I just added the full device path into the @obert0 Maybe you could also give this a try to avoid the workaround of installing both addon-ons after each other. For the firmware issue, I would like to track this in a separate issue. Could you create a new one in my repository here? |
|
Hi dfigus, |
|
Hi current setup: [ 7.314880] TBSECP3 driver 0000:01:00.0: TurboSight TBS 6205 DVB-T/T2/C root@hassio:~# ls -l /dev/dvb root@hassio:~# ls -l /dev/dvb/adapter0/ crw-rw---- 1 root video 212, 0 14 feb 09:07 demux0 into the container: This still looks as expected. STEP 2: checking whether tvheadend sees the adapter: Yes! Conclusion: I am pretty confident that this isn't a firmware/driver issue. I also tried to change the config.yaml and add all my adapters (0->7), then restart tvheadend, but that doesn't work. Still 1 adapter visible. Extra: I also have a spare TVb-dvb-s2... let me know if your are interested |
|
@rucati Thanks for testing this. So I'm still a bit puzzled why the generic device mapping of Do you still have the other 5.0.1 version installed where it does not work? Can you compare the permissions on Furthermore we might also try add some privileged capabilities to the addon and see whether this resolves the issue. Regarding firmware: As you are running HA supervised, the firmware is already available during boot. The issue from obert0 is due to the missing firmware in HA OS during the early boot stage and it seems that there is currently no way in HA OS for this. Hence a unplug & re-plug works as then the firmware is available. Regarding your TVB-DVB-S2: I could only use it if this is a USB dongle as I don't have a PC with PCIE slot for testing... |
|
Hi Short: permissions seem to be identical, (see below) it is just a matter of explicitly adding the adapter.
Fact: every adapter must be explicitly added to the config. 5.0.1 doesn't show any local adapter. Running edge:only the first adapter is visible, apart from other sat>ip-servers (see screenshot). Obviously, as you explicitly added the first adapter in config.yaml, but it works! Permissions underneath the screenshot: root@b8c699d3-tvheadend:/$ ls -l /dev/dvb 44 = group video from my debian host, the addon doesn't know this group. Running 5.0.1:
root@dae55a80-tvheadend:/$ ls -l /dev/dvb/ |
|
Hi Easy solution: keep your config as is, I can test it and adjust the config.yaml to my settings. Then I copy this into the ../addons/local/ and install it from there! I tested this and so I have all my adaters listed. In my test, I added 2 adapters and now they are listed. This is an acceptable way to keep your repository consistent.
Send me an email about the usb-dongle, if interested. |
|
This approach works, as suggested in See: GauthamVarmaK/addon-tvheadend#45 (comment) First install your repo, copy into local, make changes and then install/start this local copy.
1 issue: if I use 5.0.1 and make the changes to config.yaml, my last fritzbox is not visible anymore. Using edge (see screenshot) shows all adapters! |
|
Hi, I tested both current version and edge. I succeed to make my tuner work on the edge version only with the steps of my other post. (I have just 1 tuner) |
|
@obert0 In vain, the trailing slash doesn't make my adapters visible. For now, this works:
BUT I also follow / use addons from here: https://github.com/alexbelgium/hassio-addons/tree/master/paperless_ngx His json-file sums up a lot of possible hardware, depending on your system, it takes what works. ALSO it includes a config-path so you can add a smb-path to store recordings, apart from your local disk. @dfigus can a config-option to add an export-dir in the docker environment be added? On top, they include multiple hardware options in their json, so it matches somehow with what your system has on offer (1 dvb-adapter or 2 dvb-adapters, of even 8...) |
So to sum it up the config.yaml would really need to list all possible adapters with all sub entities. So maybe I'll add 10 adapters in the config and hope this is suitable for all - I don't have a problem with that as it does not break in case there is no DVB adapters at all (as in my setup). I still wonder why the linuxserver image works with just
Do you mean this section here:
Let's discuss this in a separate discussion #112 to keep the issue focused on the dvb adapters. |
|
@rucati Just to add: I would not recommend to copy it to local and then adjust the I'll add the other adapters in a fresh edge build 2571e8f so you can test it. |
|
Hi
Yes, a list with explicit listed hardware will work, as suggested.
Wildcards don't work.
Thanks for all your support!
Op vr 16 feb. 2024 10:19 schreef Daniel Figus ***@***.***>:
… @obert0 <https://github.com/obert0> In vain, the trailing slash doesn't
make my adapters visible. For now, this works:
1. installing the edge-branch
2. copy it to local and adjust the config.yaml
3. install and run this local branch with all adapters
BUT I also follow / use addons from here:
https://github.com/alexbelgium/hassio-addons/tree/master/paperless_ngx
His json-file sums up a lot of possible hardware, depending on your
system, it takes what works.
So to sum it up the config.yaml would really need to list all possible
adapters with all sub entities. So maybe I'll add 10 adapters in the config
and hope this is suitable for all - I don't have a problem with that as it
does not break in case there is no DVB adapters at all (as in my setup). I
still wonder why the linuxserver image works with just /dev/dvb (as far
as I remember you said it's working for you). Hence I'm not giving up on
this topic 😄. I hope with your spare DVB adapter I can figure it out.
On top, they include multiple hardware options in their json, so it
matches somehow with what your system has on offer (1 dvb-adapter or 2
dvb-adapters, of even 8...)
Do you mean this section here:
https://github.com/alexbelgium/hassio-addons/blob/122815cea7437dfd45118fb8a306ebb831dce616/paperless_ngx/config.json#L8-L65
For example many /dev/sd* are listed here and in most systems only few
like sda might be there. Is this what you mean with that?
ALSO it includes a config-path so you can add a smb-path to store
recordings, apart from your local disk.
@dfigus <https://github.com/dfigus> can a config-option to add an
export-dir in the docker environment be added? (Like the above link) This
allows recordings to be saved on a NAS.
Let's discuss this in a separate discussion #112
<#112> to keep the
issue focused on the dvb adapters.
—
Reply to this email directly, view it on GitHub
<#103 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD42FMEXOLA34P6B43TMSX3YT4QA3AVCNFSM6AAAAABDEFOQRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBYGAYTSOBVGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@rucati I released the updated config.yaml with 9 adapters in 5.0.2, so this should enable all your 8 adapters. Can you please report back if also your Fritz Satip tuners are still fully operational? |
|
Hi I moved from edge to 5.0.2 and everything works as expected This issue can be closed. Enjoy TBS-compiling :-) |
Problem/Motivation
Tvheadend doesn't see the active dvb-adapters
Expected behavior
/dev/dvb/, /dev/dri/ would be respectively mapped to /dev/dvb/, /dev/dri/ inside the addon.
Actual behavior
no cards detected in tvheadend-addon
Steps to reproduce
Proposed changes
/dev/dvb:/dev/dvb as in suggested docker-config from linuxserver.io?
Is there no firmware / linux_media needed in docker?
I compiled minisatip on debian 12, minisatip correctly detects the cards and tvheadend can see these as sat>ip in the addon.
The text was updated successfully, but these errors were encountered: