Thanks, so I’ve followed the guide as outlined on your github page. (installed the PPA, updated and installed the two packages). I’ve then rebooted but when I do a uname its not showing mediatree but “4.17.19-041719-generic” this is the kernel I manually upgraded in order to get the tuner working (needed to be .16 onward).
Is this the problem? How can I get your kernel to be applied?
Thanks
I originally followed the steps from here when I first set it up on Ubuntu 19.04 (Disco)
http://www.hauppauge.com/pages/support/support_linux.html#plex
Thanks Eddy, I think I might have caused a problem by manually updating my kernel to a version not listed on Brad’s github. I presume I might need to do something like downgrade the kernel to something listed then reapply the patch.
Although I’m not 100% on that.
Thanks
Hitting the escape key during boot will bring you into the grub boot menu. Select ‘advanced options’ or something similar, then choose the newest mediatree kernel you have installed.
Great thanks, so in the advanced options I have the attached. I’m taking a guess that the mediatree kernel is the one highlighted? As in 4.15.0-65201910101111-generic? Is that correct?
When I attempt to use 4.15.0-66 I am unable to find my tuner (as I believe I need .16 onward for that to work). Therefore when using the 4.15.0-65201910101111-generic it does allow me to again see the tuner so I’m thinking this is the patched kernel?
Although, when I attempt to do a scan I am unable to see HD channels, only the original SD channels.
Am I doing everything correct here?
Update: doing a uname gives me 4.15.0-65201910101111-generic #1+mediatree+hauppauge-Ubuntu so I think its the correct kernel?
I am able to see HD channels via Kaffeine as before.
Thanks
@NDInnovations I see there now an eoan distro on the PPA, which I’ve changed my software updater to point to, although doing a sudo apt update didn’t seem to find anything new (although maybe it found it when it did an update through the software updater GUI).
Doing a uname -a gives the following
Linux FujiServe 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
And from the grub menu the other options didn’t seem to be any use (just older versions of the kernel).
Is there something I’ve missed or I am now using your patched kernel?
(I can’t find HD channels in Plex still).
I haven’t pushed the kernel to the main ppa yet. Only the firwmare package is there currently. You can try and install the packages manually from my staging area:
https://launchpad.net/~b-rad/+archive/ubuntu/test-test-hw-staging/+packages
Download and install everything but the buildinfo package.
If they work for you please let me know.
I may well have done something wrong, but after installing the following packages
linux-modules-extra-5.3.0-19201910301314-generic_5.3.0-19201910301314.1+mediatree+hauppauge_amd64.deb
linux-modules-5.3.0-19201910301314-generic_5.3.0-19201910301314.1+mediatree+hauppauge_amd64.deb
linux-image-5.3.0-19201910301314-generic_5.3.0-19201910301314.1+mediatree+hauppauge_amd64.deb
linux-headers-5.3.0-19201910301314_5.3.0-19201910301314.1+mediatree+hauppauge_all.deb
linux-headers-5.3.0-19201910301314-generic_5.3.0-19201910301314.1+mediatree+hauppauge_amd64.deb
and then rebooting, it doesn’t seem to boot up. Selecting the kernel so I can see the boot messages it gets stuck early on loading initial ram disk (or some similar message).
Reverting back to the default kernel and I can boot up Ubuntu
Hmm…well that’s certainly not good. I’ll be doing testing after lunch.
As I say I could’ve missed something
I see the same thing in a vm. No errors. Nothing “bad” displayed. Seemingly ok boot process…then just stops and nothing. I guess Ubuntu did something in Eoan I have to figure out 
@NDInnovations I see you’ve been working on the packages, how’s it looking?
They’re all good to go now and I’ll be pushing them all to the main repo today.
However, if like in another thread its an “xbox one” tuner, then nothing I do specifically targets it. MS decided to go bargain discount on that device, it is not hauppauge rebadge and contains antiquated parts that have never been used by hauppauge. Therefore there’s nothing I can do.
Excellent, look forward to giving those a go. Thanks for the update 
I’ve updated the packages from the PPA this evening and it seems to find HD channels in the scan, but I’m not able to tune to them.
Using w_scan again it seems to find them, but they don’t appear in the final list at the end.
Any ideas why?
w_scan GB result 20191112.txt (51.2 KB)
uname -a result is
Linux FujiServe 5.3.0-19201911071317-generic #0+mediatree+hauppauge-Ubuntu SMP Thu Nov 7 21:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
@NDInnovations do you have any recommendations for my issue above with the latest files from the PPA?
If w_scan finds them, and it looks like it found 137 programs, then the driver works. w_scan cannot get channel names, NIT for frequencies, or supply data if the driver is not working. Since it gets all of this, the issue would reside with Plex. If you want to be positive, then have w_scan generate a vlc playlist file and open it up in vlc.
Thanks for the reply, but there’s no HD channels in the VLC playlist generated from w_scan
dvb.zip (3.0 KB)
Do you think the driver is working correctly?
Is there a way I can remove the driver and anything else associated with the USB tuner to give it a fresh install?
What device are you using? I only support Hauppauge devices and those which happen to use the same chips.
Hauppauge WinTV DualHD connected on USB. It was working nicely on the previous version of Ubuntu before I upgraded
