Tvheadend

Anthony Thomas wrote:

That's a fantastic bit of work.
I'm running a number of tuners on a low power Intel Atom system, which meant compilation also took ages.

Note that I've reduced the setting for Max Devices from 8 down to 2 in the menuconfig - easy to increase again if you need to.

Has there been any improvements over time to improve the drivers for the sensitivity of these tuners?
Because I still suffer from some breakups and pixelisation.

That's interesting! I was getting similar problems from another of these tuners attached to a Slice (Raspberry Pi Compute Module 3 based media player) running Tvheadend under LibreELEC which vanished when I upgraded to the most recent LE release. The Release Notes pointed to this post: https://forum.libreelec.tv/thread/4235-dvb-issue-since-le-switched-to-kernel-4-9-x/?postID=75965#post75965 which suggests a more generic problem with USB tuners on recent Linux kernels. It doesn't look like the fix is straightforward, but also may be nothing to do with the Xbox stick drivers. The Xbox tuner I have attached to my x86 (also Atom) system is only serving low bitrate Radio streams and behaves faultlessly, perhaps due to the low traffic level.

I was getting similar problems from another of these tuners attached to a Slice running Tvheadend under LibreELEC

LE 8.2.3 fixed that particular problem - idk if this helps at the Xbox Stick

That works great, makes life much easier to setup some Xbox tuners on another system.

Any idea which modules to enable in the .config file for an Astrometa DVB-C/T2 tuner based...
Realtek RTL2832P
Panasonic MN88473
Rafael Micro R828D

Works out of the box normally, but obviously the minimal config disables it.

Edit - actually ignore that, I added mn88473 to the file and maybe that worked.
Either way, the tuner is now showing.

C vH wrote:

I was getting similar problems from another of these tuners attached to a Slice running Tvheadend under LibreELEC

LE 8.2.3 fixed that particular problem - idk if this helps at the Xbox Stick

It made a big difference in my case - using the Xbox stick on 8.2.2 I was getting some pixellation and recordings onto the Slice Hard Disk, especially HD recordings, would always get multiple TVH Transport Errors. After 8.2.3 upgrade it plays and records with no errors at all. After reading the thread linked above I'm not sure there is a definitive, universal solution to the problem but the workaround in LE 8.2.3 seems effective, at least as a stopgap until a more permanent cure is in place.

How would we apply this patch on raspbian? I see it's already present in the 4.14 kernel on git, but afaik not in the master branch, so I can't grab it with rpi-update.

recompile your kernel

Hi guys, I've been following this thread off and on for the past 6 months and finally installed the tuner in my original rpi model 'b'. A big thanks to all the guides on here, it took ages to compile but it got there in the end. Also installed minisatip and my tvheadend server found the Xbox tuner straight away. My only problem is that when I scan cable (vm) channels it doesn't find anything. Are there any particular settings I need to enter.

Ryan Blackburn wrote:

Hi guys, I've been following this thread off and on for the past 6 months and finally installed the tuner in my original rpi model 'b'. A big thanks to all the guides on here, it took ages to compile but it got there in the end. Also installed minisatip and my tvheadend server found the Xbox tuner straight away. My only problem is that when I scan cable (vm) channels it doesn't find anything. Are there any particular settings I need to enter.

Have you added an initial known working mux?
That is usually what is required then it will discover the rest of the muxes automatically.

You might need to do a search for some mux lists for other set-top-boxes and go from there. They usually differ per region, but if you find a working mux you should be good to go.

Also, if you get it working, let me know how well HD channels work in terms of occasional pixelisation.

I've scanned a known frequency, that i've got coming through on my stb, is that not enough?

Ryan Blackburn wrote:

I've scanned a known frequency, that i've got coming through on my stb, is that not enough?

That should be enough.
Are all the parameters correct?

Particularly the symbol rate.

Yes they seem fine..it's really strange. Almost like the usb tuner is defaulting to DVB-T all the time rather than switching to dvb-c when asked. I tested dvb-t and that scans just fine.

Ryan Blackburn wrote:

Yes they seem fine..it's really strange. Almost like the usb tuner is defaulting to DVB-T all the time rather than switching to dvb-c when asked. I tested dvb-t and that scans just fine.

Think i know what it is as virgin scans fine under dvbv5 in terminal. There isn't an option in my tvheadend to select dvb-c annex a? Any ideas..

Hi guys,
I'm watching this thread and similar one on libreelec forum for some time. Thanks for all tips. Couple months ago i was asking about continuity problems and errors in DVB-C. I found no solution... till yesterday. I changed muxes frequencies by adding 500kHz. So my tuner found 10 muxes and one of them was 122MHz so i changed it to 122,5MHz and now i got no problems in receiving.
So maybe it will help some of you.

Michael C. wrote:

Hi guys,
I'm watching this thread and similar one on libreelec forum for some time. Thanks for all tips. Couple months ago i was asking about continuity problems and errors in DVB-C. I found no solution... till yesterday. I changed muxes frequencies by adding 500kHz. So my tuner found 10 muxes and one of them was 122MHz so i changed it to 122,5MHz and now i got no problems in receiving.
So maybe it will help some of you.

Michael,

What settings do you use in tvheadend? Any chance of sending me some screenshots..

I can upload some screenshots in 2 hours when i will be back at home.

Michael C. wrote:

I can upload some screenshots in 2 hours when i will be back at home.

Hi dude, sorry to be a pain but did you have any joy with the screenshots.

Cheers

Hi,
sorry for so late response- hard weekend :)
Like you see i have plenty of muxes which were found by the tuner. I'm using only 4 of them and i added 500kHz(122.5MHz) or 700kHz(210.7MHz) to the relevant muxes. Rest of the muxes are encrypted, so i don't need them.
This config works for me.
Cheers

Hello all! Now that Linux 4.15 has been out for a while, can anybody tell me if this driver is included in the mainline kernel? The LinuxTV wiki says "A patch has been submitted to add support to mainline kernels. Possible inclusion earliest in kernel 4.15"

can anybody tell me if this driver is included in the mainline kernel?

https://github.com/torvalds/linux/commit/c4d84547d5ae4fafe2dde649deaf10047ef34d00

adds it to the kernel, starting with v4.16-rc1 -> so 4.16 is the first kernel that includes it

Hi,
Has anyone managed to get an Rpi2 with kernel v4.14.y working with the Xbox Tuner? I'm trying to fix the reception issues. I updated the kernel using rpi-update, which worked fine, but obviously removed the driver support. So I tried to rebuild following the cut down build process, this worked once I'd download the kernel headers using rpi-source. But when I rebooted I had issues with the driver;

[ 6.783119] dvb_usb: disagrees about version of symbol rc_register_device
[ 6.783149] dvb_usb: Unknown symbol rc_register_device (err -22)
[ 6.783220] dvb_usb: disagrees about version of symbol rc_free_device
[ 6.783241] dvb_usb: Unknown symbol rc_free_device (err -22)
[ 6.783295] dvb_usb: disagrees about version of symbol rc_allocate_device
[ 6.783305] dvb_usb: Unknown symbol rc_allocate_device (err -22)
[ 6.784012] dvb_usb: disagrees about version of symbol rc_unregister_device
[ 6.784030] dvb_usb: Unknown symbol rc_unregister_device (err -22)

After cleaning and rebuilding a few times, I gave up, reverted back to kernel v4.9.35-v7+ and rebuilt the drivers again. There was an issue with the repo yesterday, but that got fixed so I'm back up and running. Before I try again, has anyone else got it working?

Anthony

Yes - to get it to build i needed to make one alteration otherwise I got the symbol issue with remote controller support.

Try make menuconfig, then change ‘Remote Controller Support’ from <M> to <*>. By default it builds remote controller support as modules and that always leads to the error above. Switching to built in to the kernel sorts that issue out.

However I find limited success in using this at present as in the UK 2 particular DVB-T2 muxes fail to tune properly - seeming to take 5-10 seconds to stabilise using this device, but works fine with others muxes. Both muxes are fine with other tuners, so looks like there are some issues remaining.

Thanks for the response, I might give it another go then with the changes you suggest ...

Anthony

Thanks!
It works. Hopefully no more transport errors, if it tunes.

Anthony

C vH wrote:

can anybody tell me if this driver is included in the mainline kernel?

https://github.com/torvalds/linux/commit/c4d84547d5ae4fafe2dde649deaf10047ef34d00

adds it to the kernel, starting with v4.16-rc1 -> so 4.16 is the first kernel that includes it

Ahh thanks for the clarification!

I updated the wiki too, just in case