add fw for dvb tuner #1157
Comments
|
It seems that this firmware is not available from the linux-firmware git tree. This would mean I need to create a separate buildroot package and all that, which is a bit much. Also, I am not sure about the license. Usually there is a reason if something doesn't find its way into linux-firmware. |
|
Could you add a mount point to /usr/lib/firmware which is writable for the users, instead of creating a seperate buildroot package, to allow adding fw files by the user itself? |
|
@admin-lm the problem is we already ship firmware with the OS today. So we would have to do it in such a way that we can still ship firmware with the OS, e.g. an overlay or something. The question then is how do we make it accessible exactly, e.g. via container from supervisor? |
MMM ..Strange story. But I completely understand your point. That's why being able to add them by ourselves could be the best way for future (less work for you, If we create mess, it's our problem :) ) But I really don't know how to help tecnically. |
|
I think an overlay for /lib/firmware helps, devices could be made accessible via portainer; /dev/dvb:/dev/dvb |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
hi, how exactly did you solve this problem? devices: I get the TV tuner in the container but unfortunately I don't understand how to add the firmware 🥲 |
|
Hi! I also would like to place 3 necessary files under /lib/firmware (for an AverMedia TD310 DVB-C/T/T2 USB stick). It works like a charm on plain Tvheadend on Raspberry Pi OS, but how on HAOS? |
|
Would it help to have CONFIG_DVB_USB=m added to device-support.config ? |
|
I just found a viable solution to the custom firmware issue for my USB DVB Tuner I was trying to attach to my HAOS setup. There are actually multiple firmware search paths the kernel uses to find firmware files to upload to the device. There is even a option to specify a custom search path, which is what I utilized. @agners I am not sure if the usecase of user specific device firmware is relevant enough to establish a more streamlined solution. The built-in the firmware search paths could be utilized for this. If I understand correctly e.g ‘/lib/firmware/updates/’ could be symlinked\bind mounted to some writeable location within HAOS. If this location would then be exposed to the supervisor there would be a working solution. This should also not interfere with the firmware currently shipped with HAOS. |
Your solution worked, but only after manually reloading the dvb-usb module after each reboot, otherwise the problem persists. Any idea on how to automate this? HAOS doesn't allow automatically running scripts with root permissions AFAIK |
|
Is there any progress about this issue? I also would like to add some firmware files for TVHeadend on my Home Assistant: I saved the files under It would be great to make this possible. Thank you! PS1: PS2: Does this help? |
There is already a solution (I can confirm it works):
|
Yes, that is what #2225 proposes, and it got merged now for OS 10. The directory |
|
But the kernel can be instructed to get the firmware from any folder
accessible to addons (e.g. under /mnt/data/supervisor/share)
…On Mon, Mar 27, 2023, 16:33 Stefan Agner ***@***.***> wrote:
@agners <https://github.com/agners> I am not sure if the usecase of user
specific device firmware is relevant enough to establish a more streamlined
solution. The built-in the firmware search paths could be utilized for
this. If I understand correctly e.g ‘/lib/firmware/updates/’ could be
symlinked\bind mounted to some writeable location within HAOS. If this
location would then be exposed to the supervisor there would be a working
solution. This should also not interfere with the firmware currently
shipped with HAOS.
Yes, that is what #2225
<#2225> proposes,
and it got merged now for OS 10. The directory
/mnt/data/supervisor/firmware is not accessible by default from within
Home Assistant Core/Add-ons. The plan is to have APIs in Supervisor which
allows to manage firmwares.
—
Reply to this email directly, view it on GitHub
<#1157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AECUL5GTHONYXTBMA3YJCU3W6GQMPANCNFSM4VU7W7IQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Yes. With the chosen solution this option is still available to you. 🤷♂️ |
|
Please forgive me, guys, but I am not such an expert and still unsure what this now means for me. After I updated to the latest HA version, what do I have to do to permanently store drivers/firmware files, i.e. where should I store them? Thanks for your patience and advice! :) |
|
You need to follow the instructions given by HahnBenjamin (posted January
8th)
…On Thu, Mar 30, 2023, 17:10 7wells ***@***.***> wrote:
Please forgive me, guys, but I am not such an expert and still unsure what
this now means for me. After I updated to the latest HA version, what do I
have to do to permanently store drivers/firmware files, i.e. where should I
store them? Thanks for your patience and advice! :)
—
Reply to this email directly, view it on GitHub
<#1157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AECUL5CZDSFC23VAYFHGMHLW6WO73ANCNFSM4VU7W7IQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I.e., this is all that's needed?
😎 |
|
Yes, assuming you copied your firmware files into that folder
…On Sat, Apr 1, 2023, 12:15 7wells ***@***.***> wrote:
I.e., this is all that's needed?
firmware_class.path=/mnt/data/supervisor/share/firmware/ must be added to
*cmdline.txt* on the PI SD card.
On the next boot the HAOS will happily load the firmware from the
specified location.
😎
—
Reply to this email directly, view it on GitHub
<#1157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AECUL5HJD5BUDFZRGGI4K33W67533ANCNFSM4VU7W7IQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I just flashed the HAOS image for the RPi 4 fresh to a nano SD card and opened Can I simply append the path, so the Thank you! 😃 |
|
Yes, it must remain one line, with spaces between different commands, it's
also important that you use a pure text editor (like notepad++ on windows)
…On Sat, Apr 1, 2023, 18:25 7wells ***@***.***> wrote:
I just flashed the HAOS image for the RPi 4
<https://github.com/home-assistant/operating-system/releases/download/9.5/haos_rpi4-64-9.5.img.xz>
*fresh* to a nano SD card and opened cmdline.txt in an editor that shows
just this *one line*:
dwc_otg.lpm_enable=0 console=tty1
usb-storage.quirks=174c:55aa:u,2109:0715:u,152d:0578:u,152d:0579:u,152d:1561:u,174c:0829:u,14b0:0206:u
Can I simply append the path, so the cmdline.txt afterwards looks as
follows, i.e. just a blank between "u" and "firmware_class.path" etc.?
(still *one line*)
dwc_otg.lpm_enable=0 console=tty1
usb-storage.quirks=174c:55aa:u,2109:0715:u,152d:0578:u,152d:0579:u,152d:1561:u,174c:0829:u,14b0:0206:u
firmware_class.path=/mnt/data/supervisor/share/firmware/
Thank you! 😃
—
Reply to this email directly, view it on GitHub
<#1157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AECUL5GELSFRNK2PMZDZPR3W7BJJHANCNFSM4VU7W7IQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
@thatsthat There's /mnt but it's empty. What have I missed? |
|
@agners There's /mnt but it's empty. What have I missed? PS: |
|
Hello! Is there really nobody with a hint for me? |
|
I switched to Home Assistant Supervised |
|
Sorry, I don't understand. what you mean. I use this: Home Assistant 2023.5.4 |
|
Has really nobody a hint for my question? |
|
Really sad :( |
|
This is an issue tracker and not a support forum. I've responded to your community post. |
|
Maybe I've missed it, but I asked how to make the path persistent and never saw an answer on this. Sorry to bother you with this and thanks for your patience. 😊 PS: Am I the only one with this problem? |
|
If there is anything else I should add, please let me know. Thank you! |
|
Hi there! I still have no solution for my problem, i.e. any firmware drivers for my DVB-T2 USB stick that I want to store will be removed after a restart. Are there any ways to do this with the recommended HA installation? |
|
Ok, only months later I understand that the paths described obviously meant the underlying system, whereas I logged into HA and placed them there. Well, at least I think that was my problem. I've now managed to get access to the underlying system with ssh via port 22222 and public/private keys and will see if that helps me further. |
|
Sorry for failing to recognize the problem here exactly, glad you found how to progress. Note however, as I posted in this community post and noted in this comment #1157 (comment): The alternative firmware path is available a bit later during boot. For many devices this means that the driver will not be able to load the firmware because the driver is loaded earlier at boot time, leading to the exact same issue. You can work around by hot-plugging the device (if the device is connected through USB or similar). But if not, placing the firmware there likely won't work, unfortunately 😢 I tried to find a solution to that, but from what I understand, there is really no way to tell the kernel to delay loading of firmwares until a later point in time. The HAOS architecture of using a read-only file system really doesn't allow to include firmware into the root partition which is available earlier. So what we are trying to do (add firmware to a mounted location) really seems not to work 😢 If someone has an idea how to implement this, I would be grateful. Until then, for non-hotpluggable device (or people which don't want to work around the limitation), using Supervised is probably the best alternative right now. |
|
Is it possible to simulate hot-plugging? |
|
I feel really embarrassed to bother you and the community with this topic again, but maybe you find my below described observation useful (sorry, if it does not). So I have that DVB-T2 USB stick (AVerMedia TD310) connected to my Raspberry Pi 4 that runs Home Assistant (2023.12.1). I restart my RPi4, log in via ssh (not port 22222 but just 22, i.e. not logged in via the "developer's method") and check if the card appears under TL;DR: First it is, then it isn't. After a reboot of my Raspberry Pi 4 that runs Home Assistant, it's shown: But after about 10 seconds later, it's gone: How can Do you have an idea why it is first shown and then - without me doing anything - "disappearing" again? |
|
After unplugging and replugging it, it's visible again. Is this due to the problem you described in post #1157 (comment)? |
|
As I made progress with this DVB-T2 USB stick and the TVheadend add-on in Home Assistant, I would like to share it here as well for other people who stumble over a similar problem. Please note that there are 2 TVheadend add-ons for HA, and it seems that you need both, i.e. first install one, then deinstall it, then install the other. The details are described in this thread: Good luck! 👍 |
Yeah the replugging is explained by that. I am not sure why the device disappeared above. Once it is there, it should stay there. Unless there is some USB bus problems, but in that case you should see some errors in the host logs. |
I'm trying to modify an existing addon for tvheadend in order to make it compatible with an usb tuner I have at home (MyGica T230C v2) .
The tuner is recognized from tvheadend cofiguration panel but cannot get any channles.
Dmesg confirms USB is recognized properly but I have:
Direct firmware load for dvb-demod-si2168-d60-01.fw failed with error -2Same for
dvb-tuner-si2141-a10-01.fwTried tvheadend on raspbian adding these two files manually as written here https://www.linuxtv.org/wiki/index.php/Geniatech_T230C
and everything works.
Could you please add them to /lib/firmware for hassos build?
files are here: t230C.v2-fw
Thanks a lot.
The text was updated successfully, but these errors were encountered: