August DVB-T210

derp derp · 2014-02-11T22:48:40+00:00

Hi. Was wondering if this was compatible with tvheadend as there's not much information from users about this device. Does anyone have one? Is it working wel...

lord slash

Hello Bebetu, unfortunately as you said the PI is too slow to decode H.265 (the last LibreElec Buid can decode it but real time decoding is way too demanding). You can only hear the sound because you don't have the hardware acceleration enabled (you should enable the MMAL acceleration). I have tried the same you did (even though on TVHeadend I was also receiving ZDF HD and the other IRDeto encoded HD Channels) but without success. The only solution I see at the moment is to buy a faster device that supports the H265 format (I read that for example the ODroid C2 does) or to buy a decoder that supports DVB-T2 (I bought this one: https://www.amazon.de/gp/product/B01I5LD2DM/ref=oh_aui_detailpage_o05_s00?ie=UTF8&psc=1 because it supports IRDeto decoding so you can also watch the encoded channels like Pro7 HD as long as they are free - June 2017).
I hope I was helpful, if you have questions feel free to ask!

Bebetu _

Thanks slash. I'll check mmal tonight, I thought it was enabled.
Odroid C2 seems like a good choice and with the support I'm looking for http://forum.odroid.com/viewtopic.php?f=144&t=22887. I'll need Kodi 17 for streaming Amazon Prime and it looks doable too https://codewalkerster.blogspot.de/2016/02/how-to-install-kodi-v170krypton-for-4k.html.

noggin

Bebetu wrote: > I have a Raspberry Pi2 with the with osmc, Kodi 17 Beta6 and TVH. > > I went through installing CrazyCat's drivers (with some pain due mostly to osmc specifics) and the stick is recognized correctly as DVB-T/T2/C. The problem is that I cannot tune into any HD channels and for manually added ones I only get sound. Here are some details: > > [...] > > tvheadend works OK with SD channels but neither wscan nor scan-s2 or via TVH's GUI are able to tune into HD channels in my area (Berlin). I have manually added HD channels from the list here http://www.vdr-wiki.de/wiki/index.php/Channels.conf_DVBT-De-Berlin-Brandenburg but only one works (Das Erste HD) and only sound is available.
> I've also tried the steps here https://tvheadend.org/d/3877-howto-setup-german-dvb-t2-beta-channels with no success either.
>

> Is this because of the Raspberry Pi2 hardware not decoding HEVC/H.265? Any guidance is highly appreciated!

Germany is currently transitioning straight from DVB-T SD 576/50i MPEG2 (which the Pi can decode with no problem - though you do need the additional paid-for MPEG2 licence for high quality decoding) to DVB-T2 HD (& I think a new SD-ish) H265/HEVC format - missing out H264 (aka MPEG4)

The Pi can decode SD and HD MPEG2 and H264 - but can't hardware decode HEVC (aka H265) and falls back on software decoding.

AIUI the DVB-T2 platform in Germany supports 540/50p (NOT 576/50i) for "SD", alongside 720/50p (which is already the German HD standard on DVB-S2) and the new 1080/50p standard (which at least one German broadcaster is adopting)

At broadcast bitrates the Pi is likely to run out of CPU steam...

The ODroid C2 and similar AMLogic S905 platforms are a useful thing to look at BUT beware. Early revisions of the S905 chipset (which were used in some versions of the ODroid C2) have an HEVC decoding bug that can cause perfectly compliant HEVC/H265 DVB streams to break up. Newer devices (Wetek Hub for instance) have the later revision where this bug was fixed. AIUI the latest ODroid C2s may do too - but I don't know if you can guarantee a C2 bought today will be a new model with the revised S905 in it.

There are a LOT of S905 based boxes (with integrated IR receivers, flash storage, WiFi/Bluetooth and PSUs) that come in cheaper than a C2 with all the bits (particularly if you go for eMMC storage rather than uSD on the C2 - and eMMC is a lot faster) - and there are LibreELec builds for some of them.

HOWEVER another thing to beware of is that the S905 Linux kernel is ancient (3.something rather than 4.something). So you won't find support for recent DVB-T2 USB tuners as standard - some tuners have had drivers backported - but the situation is a lot more complex than it is for the Pi...

Of course you could always leave the DVB-T2 tuner connected to the Pi (which has driver support) and run TV Headend on the Pi, streaming the video to the C2 over the network (which is how I cope with using modern T2 tuners and a C2 - though I actually use a Chromebox as a TV Headend server as I have 6 X DVB-T and 3 x DVB-T2 tuners connected - with a custom kernel compiled to get round the 8 tuner maximum default in Linux)

Jan Kowalski

Hi everyone,

So, couple days ago I bougth T230 stick (689) and doesn't working on Raspberry Pi2 with Openelec (tvheadend don't recognize DVB stick).

Is possible to run this device with succsess on RPi2 Openelec?

Crazy Cat

http://cvh.libreelec.tv/

Jan Kowalski

Crazy Cat wrote:

> http://cvh.libreelec.tv/

Thanks CrazyCat. Now TV adapter is visible, bud are two issues :( on Raspberry Pi2:

1. After fresh install LibreELEC DVBdrivers version (1.66, img to SD card) and set CrazyCat-CC in DVB Driver Configuration, T230 (689) is visible in tvheadend adapters, but I can't find any TV channels from DVB-C or even DVB-T (frequwnces, quam and other settings are correct).

2. In LibreELEC after installing TVheadend 4.2 and enabling tvheadend Client, I can't see "TV" on main tab. Is little strange behavior, because when I activate TV i libreELEC settings, information appears that any TV Client aren't activate, so I activate again and nothing happen - still not TV on main tab.

Crazy Cat

check system log, maybe tuner/demod firmwres not installed.

Jan Kowalski

Crazy Cat wrote:

> check system log, maybe tuner/demod firmwres not installed.

This is dmesg:

http://sprunge.us/FAMV

I see few lines with that information:

[ 311.046898] dvb-usb: Mygica T230C DVB-T/T2/C successfully initialized and connected. ... [ 12.792806] si2168 3-0064: Direct firmware load for dvb-demod-si2168-d60-01.fw failed with error -2 [ 12.792836] si2168 3-0064: firmware file 'dvb-demod-si2168-d60-01.fw' not found [ 12.804061] si2157 4-0060: Si2141/2151 reset attempts 1 [ 12.812296] si2157 4-0060: found a 'Silicon Labs Si2141-A10' [ 12.812588] si2157 4-0060: Direct firmware load for dvb-tuner-si2141-a10-01.fw failed with error -2 [ 12.812605] si2157 4-0060: firmware file 'dvb-tuner-si2141-a10-01.fw' not found ... [ 311.348638] si2168 3-0064: Direct firmware load for dvb-demod-si2168-d60-01.fw failed with error -2 [ 311.348678] si2168 3-0064: firmware file 'dvb-demod-si2168-d60-01.fw' not found [ 311.361279] si2157 4-0060: Si2141/2151 reset attempts 1 [ 311.369919] si2157 4-0060: found a 'Silicon Labs Si2141-A10' [ 311.370037] si2157 4-0060: Direct firmware load for dvb-tuner-si2141-a10-01.fw failed with error -2 [ 311.370058] si2157 4-0060: firmware file 'dvb-tuner-si2141-a10-01.fw' not found [ 311.370159] usb 1-1.4: DVB: adapter 0 frontend 0 frequency 0 out of range (42000000..870000000) [ 402.804413] si2168 3-0064: Direct firmware load for dvb-demod-si2168-d60-01.fw failed with error -2 [ 402.804449] si2168 3-0064: firmware file 'dvb-demod-si2168-d60-01.fw' not found [ 402.815322] si2157 4-0060: Si2141/2151 reset attempts 1 [ 402.823494] si2157 4-0060: found a 'Silicon Labs Si2141-A10' [ 402.823628] si2157 4-0060: Direct firmware load for dvb-tuner-si2141-a10-01.fw failed with error -2 [ 402.823648] si2157 4-0060: firmware file 'dvb-tuner-si2141-a10-01.fw' not found

Does it mean that firmware is NOT installed?

Crazy Cat

yes, need firmware files
https://tvheadend.org/d/1695-august-dvb-t210?r=22723#message-22723

Jan Kowalski

Crazy Cat wrote:
> yes, need firmware files

> https://tvheadend.org/d/1695-august-dvb-t210?r=22723#message-22723

But how to put this files to /lib/firmware ? libreELEC on Raspberry Pi2 is read only system.

Crazy Cat

maybe need put to some firmware dir in .storage

Bebetu _

OK, I've progressed with the HEVC setup on my Pi2 (knowing how bad the quality would be though). Last time I didn't have sound & video although the HD channels were found. It turns out (https://tvheadend.org/issues/2940) the osmc version of tvh 4.0.9 doesn't include HEVC support and I've upgraded to the latest using the instructions here https://tvheadend.org/d/3969-unofficial-raspberry-pi-armhf-builds?r=23584

After this and setting-up again tvh, I can actually tune to HD channels with sound and very choppy video. The CPU usage is high as expected and the viewing experience is quite bad. The image though is very good (see attached screenshot).

One thing is different though: with tvh 4.0.9 I used to see one TV adapter with two devices attached, one DVB-T and one DVB-C. This is because the dvb-t230c I'm using has both capabilities (in fact three, T/T2/C). After upgrading to the 4.1.x version, I can only see the DVB-T (see TV-adapters.png).

Is there any reason for the missing DVB-C in the current tvh?

Jan Kowalski

Crazy Cat wrote:

> maybe need put to some firmware dir in .storage

Ok, are GOOD news and BAD news :)

Good news:
- is working :)
- is necessary to create folder "firmware" in /storage/.config and put there over ssh two files from this post: https://tvheadend.org/d/1695-august-dvb-t210?r=22723#message-22723 - reboot and install tvheadend
- now tvheadend can find allDVB-C channels!

- I can watch them via link "Play" inside tvheadend.

Bad news:
- I can't set "Live TV" in LibreELEC :( After installing "tvheadend Client" and enabling "Live TV", after reboot I've got info:"The PVR manager has been enabled without any enabled PVR add-on...". Click "OK" and I see, that tvheadend Client is not active. After active them nothing happen. No "TV" in main bar. After reboot info:"The PVR manager has been enabled without any enabled PVR add-on..." appears again.

- suggestions from here: http://www.wetekforums.com/v/index.php?p=/discussion/27009/solved-tvheadend-htsp-client-not-able-to-find-any-pvr-services and here: http://forum.kodi.tv/showthread.php?tid=120309&pid=993414#pid993414 not working.

Jan Kowalski

Ok, after few days of tests I have my Raspberry Pi2 fully working with Geniatech T230c (0572:c689).

This is procedure of installation and configure:

1. Download and install .img CrazyCat (thanks Cat!) LibreELEC version on Raspberry Pi2:

http://cvh.libreelec.tv/LibreELEC/7.0_Jarvis/RPi2_3/

2. Go to System > DVB Drivers and choose CrazyCat CC. Raspberry will reboot.

3. Login to Raspberry via sshfs:
sshfs root@[Raspberry IP]:/ /media/[your linux profile]/SSH

password is: libreelec

4. On Raspberry go to: /storage/.config and make folder "firmware". Put there two firmware files from this post and reboot Raspberry:

https://tvheadend.org/d/1695-august-dvb-t210?r=22723#message-22723

5. Install tvheadend. System > settings > addons > install from repository > LibreELEC Add-ons > Services > Tvheadend 4.2

6. In web browser go to: http ://[Raspberry Pi IP]:9981, next: Configurations > DVB Inputs

This part depends of your DVB-C or DVB-T provider. Is plenty of detailed tutorials how to configure tvheadend server. At final is necessarily to have in "Services" tab list of TV channels. When you click "Play" on left side, you MUST see playing video in VLC on other software. Then you can go further to next steps.

6. Save all "Play" links of channels to your hard drive by chosse: "Save link as..."

7. Make empty playlist.txt file and put into all text from "Play" files downloaded in point 6. Your playlist file should looks:


#EXTM3U

#EXTINF:-1,CHANNEL 1
http://[Raspberry IP]:9981/stream/service/7cd1560e153447d3af363a6bedfc0907?ticket=4C35509E8BDB6D12E50F3D670C5D7E0D3E87D6B4

#EXTINF:-1,CHANNEL 2
http://[Raspberry IP]:9981/stream/service/1535cff0f5109297a009870a3d3fc494?ticket=7CAC2F03ACBDEC6EA0446DB6F6D68A056303DDD8

#EXTINF:-1,CHANNEL 3
http://[Raspberry IP]:9981/stream/service/000fd21ecc1040d8106be855b9bb28ce?ticket=DA439CB79A72AEC80D62C457F2A6FE2709CF7DFD

#EXTINF:-1,CHANNEL 4
http://[Raspberry IP]:9981/stream/service/4488567945ca63180d49356a7ce1b218?ticket=6AC57B90F81C4BE678862D7306D88DA521ACDA5F

#EXTINF:-1,CHANNEL 5
http://[Raspberry Pi IP]:9981/stream/service/dc793f173e2848e7bf30d13095ca8d20?ticket=B9B03C2DA02C0B0C07D775F69CDAAA75D9806ECA

etc.

Please note, that on begining of playlist file is line: #EXTM3U. Save playlist.txt somewhere on your Raspberry Pi.

8. Activate PVR IPTV Simple Client. Go to: System > Settings > install from repository > LibreELEC Add-ons > PVR Clients > PVR IPTV Simple Client. Go to "Configure". In "General" tab set "Local" in Location field. Below in "MCU Playlist path" set location of your playlist.txt file saved in point 7.

9. Activate Live TV. Go to System > Settings > LiveTV and activate. You will see "TV" on main KODI tab with all channels configured from playlist.txt. Thats all!

This is working for DVB-C and DVB-T. All working fine, and honestly I'm impressed how good this working :) CPU has 10-15%. Video is smooth, no lags. Of course Raspberry Pi2 license keys for MPEG2 and WVC activated.

[EDIT]

Problem with EPG. On TV (dvb-c cable plug to TV) i see EPG, but tvheadend doesn't show any EPG information.

I found some helpfull information about EPG with Raspberry Pi:

http://openelec.tv/forum/71-pvr-live-tv/75761-howto-openelec-raspberry-pi-2-tvheadend

This tutorial require external .xml with EPG. I thought, that EPG information are encoded in DVB-C signal.

Dreamcat 4

Hello again. In regards to geniatech t220 / august t210 verison 1 hardware, and it cannot get HD Channels (T2):

> Do I need to go get some older ubuntu ISO, eg 15.04 and re-test to compare it against the older kernel? Or is there some simpler solution to stay with 16.04 / 4.4 kernel?

Well I tried the following official versions of ubuntu 'desktop.ISO' version.

16.04.1 - FAIL
15.04 - FAIL (live CD)
14.10 - FAIL (live CD)

14.04.3 - OK

some recent debian or other - FAIL (live CD)

uname -a output:

16.04.1 - FAIL

Linux asus-p10s-m 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016 x86_64 GNU/Linux

14.04.3 - OK

Linux p10s-m-series 4.4.0-45-generic #66~14.04.1-Ubuntu SMP Wed Oct 19 15:05:38 UTC 2016 x86_64 x86_64 GNU/Linux

(and also after apt-get upgrade - STILL OK)

Linux p10s-m-series 4.4.0-47-generic #68~14.04.1-Ubuntu SMP Wed Oct 26 19:42:11 UTC 2016 x86_64 x86_64 GNU/Linux

========================================

So that is the information provided.

* Do other people here see the exact same problem on same (v1) revision of the hardware?
* Why is there a regression since the code was added to the official linux tree?
* Should I test on a recent arch linux too?
* Or any other tests i can do on 16.04? For example install a new kernel ?
* Is impossible to fix? What would be the best course of action here ?

Would it be better to give up and instead buy some rPi 3, or Odroid C2 to stay on an older linux? Since the main computer needs newer linux and 14.04 is far too old now. Whatever the extra device is, it would need to be fast enough for 2 of these tuners at once (both HD streams).

Crazy Cat

No any problems with "classic" Geniatech T220 aka august t210 :) Maybe problems with ter/cab signal ?:)

Dreamcat 4

Hi yes CrazyCat during early investgation that was also a suspicion. However I tested again and again.

Most recently I checked & went back, re-check for both 14.04.3 & 16.04. Those 2. And to me its really confirmed. The hardware still detect T2 HD on 14.04 ubuntu version but not new 16.04 ubuntu version. And I changed nothing else, just installed the other one from ISO. And booted into it, installed w_scan. Both were full Hard Disk installation (not liveCD) this time. To eliminate a possibility of in-complete or missing files.

The testing was within days of each other & went back to check again. Nothing else bad. The DVB-T2 signal was also confirmed good (within few hours window) from this same TV aerial cable by comparing on a TV. So no problems there. So sorry but I don't understand how its the signal or the hardware in this particular instance. When the same hardware can detect them on the other OS version. I feel at this point in time a reasonable efforts were taken to eliminate these other common possibility.

On the other hand, I would not surprised either if you guys don't keep going back to check its all still working OK. Since there keep coming newer and slightly different versions of this hardware. Which now to also support.

But I did read this thread a lot also. Historically speaking. And also I went so far as to double-check what exact lines changes was in your patch and also check that all those same modified in all the '.c' files still exist in the upstream official linux kernel. Which they do. So its not like any other guys came along afterward and accidentally taken away again your changes.

So I am really at a loss unless there is some newer breakage that has really been overlooked until now. I.e. interaction to other part of the software thats been changed. Occasionally a few other people might comment they cannot get the T2 HD channels either. Which is assumed same symptom as not patched / or too old linux before 3.17 kernel (when patch became included). But it seems less likely when we are way beyond that time now. And clearly I myself cannot explain it.

The only thing I could find:

Some other guy said somewhere i read. Either way back on this same thread or else it was over on Antii's blog. Sorry I cannot be exact (did not keep the link). But the comment exists nevertheless. And the commentary was vaguely something like saying that newer upstream API got changed. Like the bit so that it can tell the tuner you want to scan for the T2 channels instead of the T1. That mechanism. So in there somewhere is an API a call which tells the driver to specifically to scan for the T2 channels. In Antii's initial (first ever) way with the 290e hardware pre-dated that newer api mechanism. That original way only worked for 290 and could not be standardized for the other hardware. So basically all newer hardware such as this one too (the geniatech t220 / august v1). Or something like that. But also it matches the demonstrated symptom. If at time t220 patch (@ 3.17 kernel) was also pre-dated the new api. I think this is the 'v2 patch' you called it.

Honestly I don't know any of that its just a blind guess. And also because ('noob') does not properly understand actually what specifically in these driver is going on. Or what the comment actually referrers to. Or if its even relevant in this particular case.

So can it really be possible that thenewer linux is now broken while the older one still works? This is why I ask others here for an independant testing confirmation. To be taken more seriously the matter. And because ('noob') is not knowing what else to do specifically.

Deri James

Using my August DVB-T210 on a Mageia 5 box using kernel 4.4.30-desktop-2.mga5 the messages on connecting are:-

Dec 02 15:30:39 pip.chuzzlewit.co.uk kernel: dvb-usb: Geniatech T220 DVB-T/T2 USB2.0 successfully deinitialized and disconnected. Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: usb 1-1.5.4: new high-speed USB device number 10 using ehci-pci Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: usb 1-1.5.4: New USB device found, idVendor=1f4d, idProduct=d220 Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: usb 1-1.5.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: usb 1-1.5.4: Product: USB Device Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: usb 1-1.5.4: Manufacturer: Geniatech Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: usb 1-1.5.4: SerialNumber: 0001 Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: dw2102: su3000_identify_state Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: dvb-usb: found a 'Geniatech T220 DVB-T/T2 USB2.0' in warm state. Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: dw2102: su3000_power_ctrl: 1, initialized 0 Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: DVB: registering new adapter (Geniatech T220 DVB-T/T2 USB2.0) Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: dvb-usb: MAC address: ff:ff:ff:ff:ff:ff Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: tda18271 1-0060: creating new instance Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: TDA18271HD/C2 detected 1-0060 Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: dw2102: Attached TDA18271HD/CXD2820R! Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: usb 1-1.5.4: DVB: registering adapter 0 frontend 0 (Sony CXD2820R)... Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: Registered IR keymap rc-su3000 Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/ Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1- Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: dvb-usb: schedule remote query interval to 150 msecs. Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: dw2102: su3000_power_ctrl: 0, initialized 1 Dec 02 15:30:51 pip.chuzzlewit.co.uk kernel: dvb-usb: Geniatech T220 DVB-T/T2 USB2.0 successfully initialized and connected. Dec 02 15:30:51 pip.chuzzlewit.co.uk mtp-probe[12346]: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1 Dec 02 15:30:51 pip.chuzzlewit.co.uk mtp-probe[12346]: bus: 1, device: 10 was not an MTP device Dec 02 15:31:35 pip.chuzzlewit.co.uk kernel: dw2102: su3000_power_ctrl: 1, initialized 1 Dec 02 15:31:35 pip.chuzzlewit.co.uk kernel: tda18271: performing RF tracking filter calibration Dec 02 15:31:37 pip.chuzzlewit.co.uk kernel: tda18271: RF tracking filter calibration complete Dec 02 15:31:53 pip.chuzzlewit.co.uk kernel: dw2102: su3000_power_ctrl: 0, initialized 1 Dec 02 15:31:53 pip.chuzzlewit.co.uk kernel: dw2102: su3000_power_ctrl: 1, initialized 1

I find that it is much more stable if I use a USB3 socket rather than USB2. It will work on the USB2 port but using this command to test:-

vlc dvb-t2://frequency=626167000:inversion=-1:bandwidth=8:code-rate-hp=0:code-rate-lp=0:modulation=256QAM:transmission=32:guard=1/128

(Which are the parameters for BBC TWO HD in my area).

It fails 70-80% of the time, but using the USB3 port it works every time. The USB2 failures are while it is plugged into a powered hub, whilst the USB3 socket is directly connected to the motherboard. I have a vague recollection that this has been noticed before in this thread. While failing on USB2 vlc spits out loads of ts demux errors.

Dreamcat 4

Thanks for this data point. 'Mageia 5'... interesting. And the vlc command I may give it a try the next time i can go back to it.

In regards to the USB ports: My own host is a c232 chipset board (skylake / LGA1151 / xeon e3v5). The tuners each directly connected to their own dedicated USB 3.0 ports. When changing ubuntu versions i didn't actually unplug / re-plug the device. It was stayed in the exact same USB ports. There are no usb hubs in the way of it. I did try switching over to the other usb 3 and 2 ports once during the course of testing some of the FAIL cases. It didn't make any difference whatsoever.

Anthony Thomas

I've got the T230C that I've been trying to get working with a Raspberry Pi (original Model B) that I use as a minisatip server.

Has anyone managed to get these instructions to work on Raspbian?

git clone https://bitbucket.org/CrazyCat/media_build cd media_build ./build --main-git sudo make install

Do I need various kernel headers and other dependencies apart from the usual compiling packages and the ones mentioned when running the script or is it generally not destined to work?

I've not got the build errors to hand but I can post them another time. Actually, it didn't even work on the RPi1B as the git clone part of the build script sat forever on resolving deltas. On an RPi2 it got to the compiling part but failed.

I have managed to find a way to get the T230C working by using the CVH Libreelec build to install crazycat's DVB drivers and then use TVH as the satip server. It works, but I'd prefer a more trimmed down system with just Raspbian and minisatip.

« Previous Page Next Page »