Please do not refer to the Haupauge support pages. They are so bad, there is literal no useful information on these pages. The information is either outdated or unrelated for people running docker.
I Update to version 1.22.0.4163. Unfortunately, the problem does not seem to be fixed.
Still same error in my tuner log:
Mar 10, 2021 20:25:59.143 [] WARN - [E] dvb_channel_scanner_t::do_scan_attempt. Tune failed for 857833,,,8,,
Mar 10, 2021 20:25:59.182 [] INFO - [I] web_service_t::process_device_status
Mar 10, 2021 20:25:59.182 [] INFO - [I] v4l::DeviceGetList_impl. getting v4l device list
Mar 10, 2021 20:25:59.182 [] INFO - [I] v4l::DeviceGetList_impl. Successfully opened frontend /dev/dvb/adapter0/frontend0
Mar 10, 2021 20:25:59.184 [] INFO - [I] web_service_t::process_device_status
Mar 10, 2021 20:25:59.184 [] INFO - [I] v4l::DeviceGetList_impl. getting v4l device list
Mar 10, 2021 20:25:59.184 [] INFO - [I] v4l::DeviceGetList_impl. Successfully opened frontend /dev/dvb/adapter0/frontend0
Mar 10, 2021 20:25:59.186 [] INFO - [I] web_service_t::process_get_scanners
Mar 10, 2021 20:25:59.186 [] INFO - [I] v4l::DeviceGetList_impl. getting v4l device list
Mar 10, 2021 20:25:59.186 [] INFO - [I] v4l::DeviceGetList_impl. Successfully opened frontend /dev/dvb/adapter0/frontend0
Mar 10, 2021 20:25:59.193 [] INFO - [I] CTVSStreamSource::TuneTransponder. Transponder tuning request: diseqc 0, freq 858167, modulation 0, polarization 0, symbol rate 0, LOF 8, LNB selection signal 0, FEC 0
Mar 10, 2021 20:25:59.193 [] INFO - [I] Tuning request. 858167, 8, 0, 0, 0, 0, 0
Mar 10, 2021 20:25:59.195 [] INFO - [I] Exiting streaming thread for tuner 0, frontend 0
Mar 10, 2021 20:25:59.205 [] WARN - [W] CV4lTunersStreamSrc::Start. pthread_setschedparam failed 1
Mar 10, 2021 20:25:59.205 [] INFO - [I] Starting streaming thread for tuner 0, frontend 0
Hi @sa2000,
The drivers for all Hauppauge tuners are included in the Linux kernel for some time already (~v4.7 for DualHD), however the firmware isn’t loaded by default. On their website they currently only describe driver installation (on Ubuntu) which isn’t needed anymore. On the bottom of the page you shared (Hauppauge Support | Linux), they mention a firmware installation but only point to an outdated Ubuntu package.
On a German FAQ they describe some firmware steps but is also outdated (they link to the OpenELEC pages here as well for the firmware files):
https://www.hauppauge.de/site/support/support_faq.php?n=FAQ.Linux
The following pages for the specific models give some good pointers on e.g. checking kernel messages for missing firmware but also outdated.
https://linuxtv.org/wiki/index.php/Hauppauge
In short, the Hauppauge manuals could really use an overhaul and in it’s current state, are pretty useless.
On the Plex page, there is a note saying “Ensure your tuner device firmware/driver is up-to-date.” on the page below.
Maybe adding a note here saying e.g. on Linux to check for kernel messages if they run into issues, look for something like:
“firmware file ‘dvb-demod-siXXXX-YY.fw’ not found”
Maybe there is also a possibility to detect this in Plex and give a clear warning on this (or in the log files at least).
Anyhow, for me it was a bit strange. I checked for missing firmware ~five times and just completely overlooked the error. Could have sworn I installed the correct one initially.
We already refer to their linux web page on our Supported DVR Tuners and Antennas | Plex Support article
The definitive information for drivers and firmware for the Hauppauge products must come from Hauppauge
Thanks for the detail. We will get in touch with Hauppauge to ask for a review of their linux related support information
where exactly does this appear ?
Hi @Broekmanium did you find this error inside the docker container dmesg or in dmesg on your host system?
Thanks!
That would be very much appreciated @sa2000! Thanks.
Hi @obtain-disk,
I’m not using Docker for Plex however I’m sure you should see the error on your host system and give your docker container access to the specific USB device. Adding the user “plex” to the “video” group (inside the container) should do the trick for USB tuners in terms of access (tuners are automatically in that group).
For docker I’m pretty sure you have to forward the entire DVB device section, add to your Docker file:
devices:
- /dev/dvb:/dev/dvb
On top of that make sure that the “plex” user is added to the correct “video” group ID as mentioned before, as this can depend on which system the container is built from.
Run:
grep plex /etc/group
and
grep video /etc/group
and make sure the ID (986 for me below) are the same in both results (if not you can resolve this by supplying an environment variable to the container).
# grep plex /etc/group
video:x:986:plex
media:x:1001:plex,sonarr,qbittorrent,radarr
# grep video /etc/group
video:x:986:plex
Do note that the firmware is not included on most Linux distros so if you can’t remember installing it, you probably have to.
To check the firmware error in the kernel messages:
- Unplug the USB tuner
- Start a tail on the kernel messages (dmesg -w)
- Insert the USB tuner, you should see a few messages about it including the firmware message if its missing (also look for other errors). Note that if you have never unplugged it the message might be long gone already.
Hope this helps, good luck 
Update on Hauppauge support information
Hauppauge have made improvements to the support pages and were looking into adding scripts for getting the firmware installed
Related web pages
https://www.hauppauge.com/pages/support/support_linux.html
https://www.hauppauge.com/pages/support/support_linux.html#firmware
https://www.hauppauge.com/pages/support/support_linux.html#plex
@Broekmanium thanks for the detailed write up. I dug deeper but I could not pin point the exact problem.
I think it is either a problem with missing firmware or a permissions problem.
For the first Problem I downloaded the mentioned firmware on the support page. → did not work.
For the permission problem i tried al kind of things. conclusion: tvheaded works with exactly the same permission settings. Which lets me believe the problem might be caused by the firmware.
Anyway I will report back a soon as i have an update.
@sa2000 thanks for the links. I had a look at those pages but it still seems outdated to me. I am in contact with the Hauppage support, I will give them the same feedback.
It seems like the DVB setup page got an update.
I am currently running version 1.22.3.4523 on the same system as described in my opening post.
I installed the haupage firmware using the following commands inside my docker container:
add-apt-repository ppa:b-rad/kernel+mediatree+hauppauge
apt-get install linux-firmware-hauppauge
The error messages in my tuner logs changed after updateing + firmware installation.
error messages now look like this:
May 21, 2021 22:05:54.267 [0x7fe9ecea5700] INFO - [I] onetv_factory::DeviceGetListEx >>
May 21, 2021 22:05:54.267 [0x7fe9ecea5700] WARN - [W] onetv_factory::DeviceGetListEx. libusb_init returned an error -99
May 21, 2021 22:05:54.267 [0x7fe9ecea5700] INFO - [I] device_manager_t::get_device_list. Device soloHD, id dvb#v4l#0#/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0, tuners 1, state 0, standards 3
May 21, 2021 22:05:54.268 [0x7fe9eeea9700] INFO - [I] web_service_t::process_device_status
May 21, 2021 22:05:54.268 [0x7fe9eeea9700] INFO - [I] v4l::DeviceGetList_impl. getting v4l device list
May 21, 2021 22:05:54.268 [0x7fe9eeea9700] INFO - [I] v4l::DeviceGetList_impl. Successfully opened frontend /dev/dvb/adapter0/frontend0
May 21, 2021 22:05:54.270 [0x7fe9ed6a6700] INFO - [I] web_service_t::process_get_scanners
May 21, 2021 22:05:54.270 [0x7fe9ed6a6700] INFO - [I] v4l::DeviceGetList_impl. getting v4l device list
May 21, 2021 22:05:54.270 [0x7fe9ed6a6700] INFO - [I] v4l::DeviceGetList_impl. Successfully opened frontend /dev/dvb/adapter0/frontend0
May 21, 2021 22:05:54.284 [0x7fe9ee6a8700] INFO - [I] web_service_t::process_device_status
May 21, 2021 22:05:54.284 [0x7fe9ee6a8700] INFO - [I] v4l::DeviceGetList_impl. getting v4l device list
May 21, 2021 22:05:54.284 [0x7fe9ee6a8700] INFO - [I] v4l::DeviceGetList_impl. Successfully opened frontend /dev/dvb/adapter0/frontend0
May 21, 2021 22:05:54.286 [0x7fe9edea7700] INFO - [I] web_service_t::process_get_scanners
May 21, 2021 22:05:54.286 [0x7fe9edea7700] INFO - [I] v4l::DeviceGetList_impl. getting v4l device list
May 21, 2021 22:05:54.286 [0x7fe9edea7700] INFO - [I] v4l::DeviceGetList_impl. Successfully opened frontend /dev/dvb/adapter0/frontend0
May 21, 2021 22:05:54.301 [0x7fe9e77fe700] INFO - [I] web_service_t::process_device_status
May 21, 2021 22:05:54.301 [0x7fe9e77fe700] INFO - [I] v4l::DeviceGetList_impl. getting v4l device list
May 21, 2021 22:05:54.301 [0x7fe9e77fe700] INFO - [I] v4l::DeviceGetList_impl. Successfully opened frontend /dev/dvb/adapter0/frontend0
May 21, 2021 22:05:54.303 [0x7fe9e77fe700] WARN - [E] web_service_t::get_device_status. get_device_info returned error for device dvb#v4l#0#/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0
May 21, 2021 22:05:54.304 [0x7fe9e6ffd700] INFO - [I] web_service_t::process_device_status
May 21, 2021 22:05:54.304 [0x7fe9e6ffd700] INFO - [I] v4l::DeviceGetList_impl. getting v4l device list
May 21, 2021 22:05:54.304 [0x7fe9e6ffd700] INFO - [I] v4l::DeviceGetList_impl. Successfully opened frontend /dev/dvb/adapter0/frontend0
Do you guys have a clue what could be the problem? I have been looking to the permissions, however they seem to be alright.
Thanks!
1 Like
I have the same issue using a usb RTL2838UHIDIR.
It used to work before, but if I want to set it up now it is recognised but does not scan channels.
I also have the pretty much same logs …
Not sure what else to try.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
