ZimaOS does not support casually installing host kernel firmware with Ubuntu-style apt install linux-firmware-... commands. ZimaOS is an appliance-style system, and IceWhale explicitly told users that host firmware should be integrated into the OS release rather than manually copied in.
The source case involved a Hauppauge WinTV-NOVA-S2 USB DVB-S2 tuner that needed a firmware blob before Tvheadend or Plex could use it. IceWhale agreed to integrate the firmware in a future release and asked the user to test it.
Why Ubuntu Commands Do Not Translate Directly
Ubuntu package managers can write firmware into a mutable host filesystem. ZimaOS is not a generic Debian installation with the same package workflow.
Kernel Firmware Must Be Available to the Host
Many DVB, Wi-Fi, and other devices ask the host kernel for firmware during initialization. A Docker container cannot fix that if the host never initializes the hardware.
Step 1: Identify the Exact Device and Missing Blob
lsusb
dmesg | grep -i -E 'firmware|dvb|usb'Record the USB/PCI IDs, driver name, and exact missing filename.
Step 2: Confirm Firmware Source and License
Provide the official vendor/kernel-firmware source and redistribution information when asking IceWhale to bundle it.
Step 3: Request OS Integration
IceWhale said users could not add host firmware themselves for security reasons and that the team could integrate a specific blob when there was a clear use case.
Step 4: Test After a Release Includes It
Reconnect the device and inspect dmesg. You want the driver to initialize without “firmware file not found” before configuring Tvheadend or Plex.
Pass the Device into the App Separately
After the host recognizes a DVB tuner, a Docker app may still need the relevant /dev/dvb devices mapped into the container. Host firmware and container access are separate layers.
Do Not Confuse Userspace and Kernel Firmware
Some apps load their own models/data files and those can be mounted into a container. Firmware requested by a kernel driver is different.
The hardware troubleshooting guide helps structure the report.
How Linux Firmware Loading Works
When a kernel driver initializes hardware, it can call the Linux firmware loader and request a named blob from the host firmware paths. If that file is missing, the driver may bind only partially or refuse to expose the final device node.
The upstream {A("https://docs.kernel.org/driver-api/firmware/request_firmware.html","Linux firmware loader documentation","Understand how kernel drivers request firmware from the host operating system")} explains this host-level mechanism.
Confirm the Driver Exists Before Requesting Only Firmware
A firmware blob cannot help if ZimaOS lacks the kernel driver for the device. Check dmesg and module information to determine whether the driver loads and then asks for firmware, or whether the hardware is unsupported earlier in the stack.
Container Passthrough Comes After Host Detection
For Tvheadend, Plex, or another app, first make sure the host exposes the tuner under /dev/dvb. Only then configure Docker device mappings and application permissions.
Retest After Every ZimaOS Upgrade
If IceWhale integrates the firmware into a release, confirm the tuner still initializes after later major updates. Keep the exact hardware IDs in your notes so regression reports are reproducible.
Understand the Linux Firmware Loader
Kernel drivers commonly request a named firmware blob during device initialization. The upstream Linux firmware loader documentation explains that this happens at the host-kernel level, before most application containers can use the device.
If the driver is present but the requested blob is missing, an OS-integrated firmware update is the clean fix. If the driver itself is missing, adding only the blob will not make the hardware work.
FAQ
Can I apt install linux-firmware on ZimaOS?
Do not treat ZimaOS like Ubuntu; IceWhale's support position was to integrate required host firmware.
Can Docker include the missing firmware?
Not if the host kernel needs it before the device exists for the container.
What should I check after integration?
Use dmesg and hardware enumeration to confirm clean initialization.
Does firmware require a desktop GUI?
No. Kernel/device firmware works on a headless server.
