Tvheadend

Not sure about that version of the stick on Raspbian Jessie. Jan Kowalski got it working on LibreELEC, but the kernel and linuxtv software (media_build) used in that distro are usually builds that include all the latest patches for better "TV" hardware support. You could always try the instructions here:

https://www.linuxtv.org/wiki/index.php/Geniatech_T230C

but it may be worth switching to LibreELEC if you only intend using the RPI as a tvheadend+Kodi box.

Good luck!

I don't know much about jessie lite but it doesn't sound like a good starting point for a media server. Why not the full Raspbian?

Thank you!

I made it work on LibreELEC too, it works almost out of the box. It was able to stream the whole MX. But I don't need GUI and KODI. It takes resources. I need naked and the simpliest OS for IP streamer.

I also installed dvb-apps hoping it will help. Unfortunately, no effect.

Well perhaps you should start with a distro that works and gradually strip out the packages you don't need. You could start with Raspbian and take out the bits that are not in the Lite version until it stops working! Or start with OSMC which is more like a real Debian and doesn't have X, browsers, office suites or any of that baggage.

Graham H wrote:

Well perhaps you should start with a distro that works and gradually strip out the packages you don't need. You could start with Raspbian and take out the bits that are not in the Lite version until it stops working! Or start with OSMC which is more like a real Debian and doesn't have X, browsers, office suites or any of that baggage.

Or use the awesome raspbian-ua-netinstall. That's as bare bones as you can get (plus it's configurable).

Dmytro Iatskyi wrote:

But I don't need GUI and KODI. It takes resources. I need naked and the simpliest OS for IP streamer.

In that case I'd stick with Raspbian (or either of Graham's or Mark's suggestions) and then grab the latest media_build and any required kernel patches and build them all yourself. I used to custom build them before support for the T210v2 was in the default Raspbian media_build. Lots of messing about, and you have to remember to rebuild stuff if a new kernel comes out, but it could be your only choice at this point in time.

Deri James wrote:

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.
I find that it is much more stable if I use a USB3 socket rather than USB2.

Interesting, for me USB3.0 or actually xhci is having errors, but USB 2.0 ehci works just fine.

Mar 30 18:31:21 bogey kernel: [ 281.859368] dvb-usb: recv bulk message failed: -110
Mar 30 18:31:21 bogey kernel: [ 281.860379] dw2102: i2c transfer failed.

Same is with both Intel B85 chipset (Asus B85M-E) or Renesas Technology Corp. uPD720201 USB 3.0 Host Controller
So I need to disable XHCI in my bios settings to set ports to legacy mode, so all motherboard USB ports are then USB2.0 / ehci.
Then I can plug T220 to any of the motherboard USB port and it works fine.

I'm at Ubuntu 16.04.2 LTS 4.8.0-45-generic #48~16.04.1-Ubuntu

Here is syslog together with VDR startup, so the errors come when VDR started.

Mar 30 18:31:10 bogey kernel: [ 270.823414] usb 3-9: new high-speed USB device number 7 using xhci_hcd
Mar 30 18:31:10 bogey kernel: [ 270.952251] usb 3-9: New USB device found, idVendor=1f4d, idProduct=d220
Mar 30 18:31:10 bogey kernel: [ 270.952258] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 30 18:31:10 bogey kernel: [ 270.952263] usb 3-9: Product: USB Device
Mar 30 18:31:10 bogey kernel: [ 270.952266] usb 3-9: Manufacturer: Geniatech
Mar 30 18:31:10 bogey kernel: [ 270.952269] usb 3-9: SerialNumber: 0001
Mar 30 18:31:10 bogey kernel: [ 270.953167] dw2102: su3000_identify_state
Mar 30 18:31:10 bogey kernel: [ 270.953167]
Mar 30 18:31:10 bogey kernel: [ 270.953174] dvb-usb: found a 'Geniatech T220 DVB-T/T2 USB2.0' in warm state.
Mar 30 18:31:10 bogey kernel: [ 270.953183] dw2102: su3000_power_ctrl: 1, initialized 0
Mar 30 18:31:10 bogey kernel: [ 270.953183]
Mar 30 18:31:10 bogey kernel: [ 270.953376] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 30 18:31:10 bogey kernel: [ 270.953446] DVB: registering new adapter (Geniatech T220 DVB-T/T2 USB2.0)
Mar 30 18:31:10 bogey kernel: [ 270.957554] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
Mar 30 18:31:10 bogey kernel: [ 271.012428] tda18271 7-0060: creating new instance
Mar 30 18:31:10 bogey kernel: [ 271.016754] TDA18271HD/C2 detected @ 7-0060
Mar 30 18:31:10 bogey kernel: [ 271.251951] dw2102: Attached TDA18271HD/CXD2820R!
Mar 30 18:31:10 bogey kernel: [ 271.251951]
Mar 30 18:31:10 bogey kernel: [ 271.251961] usb 3-9: DVB: registering adapter 0 frontend 0 (Sony CXD2820R)...
Mar 30 18:31:10 bogey kernel: [ 271.252230] dw2102: su3000_power_ctrl: 0, initialized 1
Mar 30 18:31:10 bogey kernel: [ 271.252230]
Mar 30 18:31:10 bogey kernel: [ 271.252235] dvb-usb: Geniatech T220 DVB-T/T2 USB2.0 successfully initialized and connected.
Mar 30 18:31:10 bogey mtp-probe: checking bus 3, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-9"
Mar 30 18:31:10 bogey mtp-probe: bus: 3, device: 7 was not an MTP device
Mar 30 18:31:14 bogey colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Mar 30 18:31:19 bogey vdr: [2382] VDR version 2.2.0 started
Mar 30 18:31:19 bogey vdr: [2382] codeset is 'UTF-8' - known
Mar 30 18:31:19 bogey vdr: [2382] found 28 locales in ./locale
Mar 30 18:31:19 bogey vdr: [2382] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-dummydevice.so.2.2.0
Mar 30 18:31:19 bogey vdr: [2382] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-live.so.2.2.0
Mar 30 18:31:19 bogey vdr: [2382] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-vnsiserver.so.2.2.0
Mar 30 18:31:19 bogey vdr: [2382] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-epgsearch.so.2.2.0
Mar 30 18:31:19 bogey vdr: [2382] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-femon.so.2.2.0
Mar 30 18:31:19 bogey vdr: [2382] loading /etc/vdr/setup.conf
Mar 30 18:31:19 bogey vdr: [2382] ERROR: unknown config parameter: PrimaryLimit = 0
Mar 30 18:31:19 bogey vdr: [2382] loading /etc/vdr/sources.conf
Mar 30 18:31:19 bogey vdr: [2382] loading /etc/vdr/channels.conf
Mar 30 18:31:19 bogey vdr: [2382] loading /etc/vdr/timers.conf
Mar 30 18:31:19 bogey vdr: [2382] loading /etc/vdr/commands.conf
Mar 30 18:31:19 bogey vdr: [2382] loading /etc/vdr/reccmds.conf
Mar 30 18:31:19 bogey vdr: [2382] loading /etc/vdr/svdrphosts.conf
Mar 30 18:31:19 bogey vdr: [2382] loading /etc/vdr/remote.conf
Mar 30 18:31:19 bogey vdr: [2382] loading /etc/vdr/keymacros.conf
Mar 30 18:31:19 bogey vdr: [2382] ERROR: unknown plugin 'extrecmenu'
Mar 30 18:31:19 bogey vdr: [2382] ERROR: empty key macro
Mar 30 18:31:19 bogey vdr: [2382] ERROR: unknown plugin 'osdteletext'
Mar 30 18:31:19 bogey vdr: [2382] ERROR: empty key macro
Mar 30 18:31:19 bogey vdr: [2382] loading /etc/vdr/folders.conf
Mar 30 18:31:19 bogey vdr: [2384] video directory scanner thread started (pid=2382, tid=2384, prio=high)
Mar 30 18:31:19 bogey vdr: [2382] registered source parameters for 'A - ATSC'
Mar 30 18:31:19 bogey vdr: [2382] registered source parameters for 'C - DVB-C'
Mar 30 18:31:19 bogey vdr: [2382] registered source parameters for 'S - DVB-S'
Mar 30 18:31:19 bogey vdr: [2382] registered source parameters for 'T - DVB-T'
Mar 30 18:31:19 bogey vdr: [2382] probing /dev/dvb/adapter0/frontend0
Mar 30 18:31:19 bogey vdr: [2382] creating cDvbDevice
Mar 30 18:31:19 bogey vdr: [2382] new device number 1
Mar 30 18:31:19 bogey vdr: [2383] video directory scanner thread started (pid=2382, tid=2383, prio=high)
Mar 30 18:31:19 bogey vdr: [2385] epg data reader thread started (pid=2382, tid=2385, prio=high)
Mar 30 18:31:19 bogey vdr: [2385] reading EPG data from /var/cache/vdr/epg.data
Mar 30 18:31:19 bogey kernel: [ 279.862168] dw2102: su3000_power_ctrl: 1, initialized 1
Mar 30 18:31:19 bogey kernel: [ 279.862168]
Mar 30 18:31:19 bogey vdr: [2385] epg data reader thread ended (pid=2382, tid=2385)
Mar 30 18:31:19 bogey vdr: [2384] video directory scanner thread ended (pid=2382, tid=2384)
Mar 30 18:31:19 bogey vdr: [2383] video directory scanner thread ended (pid=2382, tid=2383)
Mar 30 18:31:21 bogey kernel: [ 281.859368] dvb-usb: recv bulk message failed: -110
Mar 30 18:31:21 bogey kernel: [ 281.860379] dw2102: i2c transfer failed.
Mar 30 18:31:21 bogey kernel: [ 281.868577] tda18271: performing RF tracking filter calibration
Mar 30 18:31:23 bogey vdr: [2382] DVB API version is 0x050A (VDR was built with 0x050A)
Mar 30 18:31:23 bogey vdr: [2382] frontend 0/0 provides DVB-T,DVB-T2,DVB-C with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("Sony CXD2820R")
Mar 30 18:31:23 bogey vdr: [2387] frontend 0/0 tuner thread started (pid=2382, tid=2387, prio=high)
Mar 30 18:31:23 bogey vdr: [2382] cTimeMs: using monotonic clock (resolution is 1 ns)
Mar 30 18:31:23 bogey vdr: [2387] cTimeMs: using monotonic clock (resolution is 1 ns)
Mar 30 18:31:23 bogey vdr: [2382] probing /dev/dvb/adapter1/frontend0
Mar 30 18:31:23 bogey vdr: [2382] creating cDvbDevice
Mar 30 18:31:23 bogey vdr: [2382] new device number 2
Mar 30 18:31:23 bogey kernel: [ 284.167664] tda18271: RF tracking filter calibration complete
Mar 30 18:31:23 bogey vdr: [2388] device 1 section handler thread started (pid=2382, tid=2388, prio=low)


Ok, I tried raspbian-ua-netinstall, but during building from CrazyCat repo it returns constant error about lack of memory and kills git process and then stops, although I left the largest amount of memory for RAM. Strange thing, because building process was ok on Jessie Lite with the same amount of memory.

The next step I'd like to make:

I have working LibreELEC image and I want to disable KODI startup on system boot. How can I do this?

Dmytro Iatskyi wrote:

Ok, I tried raspbian-ua-netinstall, but during building from CrazyCat repo it returns constant error about lack of memory and kills git process and then stops, although I left the largest amount of memory for RAM. Strange thing, because building process was ok on Jessie Lite with the same amount of memory.

The next step I'd like to make:

I have working LibreELEC image and I want to disable KODI startup on system boot. How can I do this?

Jessie Lite has swap space, an install using raspbian-ua-netinstall won't, See this to temporarily (or permanently) add your own.

Mark Clarkstone wrote:

Dmytro Iatskyi wrote:

Ok, I tried raspbian-ua-netinstall, but during building from CrazyCat repo it returns constant error about lack of memory and kills git process and then stops, although I left the largest amount of memory for RAM. Strange thing, because building process was ok on Jessie Lite with the same amount of memory.

The next step I'd like to make:

I have working LibreELEC image and I want to disable KODI startup on system boot. How can I do this?

Jessie Lite has swap space, an install using raspbian-ua-netinstall won't, See this to temporarily (or permanently) add your own.

Yes, must be it. Thank you, Mark!

But, nevertheless, how to switch off the KODI in LibreELEC?

You can potentially run either of these two as a boot script (autostart.sh) to kill Kodi

systemctl stop kodi

killall kodi.bin

sudo apt-get remove kodi might do it.

Graham H wrote:

sudo apt-get remove kodi might do it.

Not on Libreelec. It doesn't use the aptitude package system.

Ah! That's one more reason to prefer OSMC

This will stop Kodi from running on Libreelec - http://openelec.tv/forum/64-installation/70097-headless-openelec#163056

Anyone else managed to kill their T230C?

Was working perfectly for some time, until recently it is showing like the signal is very weak with massive amounts of breakup.

Anthony Thomas wrote:

Anyone else managed to kill their T230C?

Was working perfectly for some time, until recently it is showing like the signal is very weak with massive amounts of breakup.

I get this on occasion with the T230 [None C] version. I don't think there is a fix. A retune usually clears it.

I've got two connected to my RPI2 and one of them died after about a year's use. The other one has been going strong for a couple of years now (along with the replacement stick). However, before you write your T230C off as completely dead, you might want to try a cold boot. So, power off (unplug stick if you aren't sure), count to 10, plug back in, power up, test. Every now and then one of my sticks refuses to tune properly, and nothing but a cold boot sorts it out. If I simply reboot the system it doesn't fix it. Worth a try (if you haven't already).

Forgot to say that all my tuners are T220, but the same advice probably applies.

Unfortunately it hasn't worked

I've tried it on a separate system from the RPi that it was originally used on and it's still showing a similar issue.

Though.... I used minisatip to provide the stream and checked the signal quality, when I changed the output on the signal splitter the signal seemingly increased (signal showing green (55%+)) but still breaking up, but marginally less. Need to try another DVB-C adapter I've got to see if it's the device or the signal.

hi

I have a orangepi +2e (http://www.orangepi.org/orangepiplus2e/) as a tv-server (only) and want to buy a geniatech mygica t230 (without C ). The problem is, I can only use kernel 3.4. I read on linuxtv

Drivers are included in kernel 3.19. They can be built with media_build for older kernels

Latest media_build probably doesn't build Geniatech T230 driver on 3.4 kernel anymore

What is the truth ?

Tschau nepo

joey ramone wrote:

hi

I have a orangepi +2e (http://www.orangepi.org/orangepiplus2e/) as a tv-server (only) and want to buy a geniatech mygica t230 (without C ). The problem is, I can only use kernel 3.4. I read on linuxtv
[...]
I have asked in armbian-forum about compiling media-build for T230 and the answer was
[...]

What is the truth ?

I have an OrangePi PC running Armbian & the dev kernel (4.10.0) without issue. Although I don't use my T230 (branded as the August T210v2) with it anymore, it worked fine (on an older dev kernel). I don't see why you can't upgrade your kernel to the dev one. And, if the driver isn't limited by the kernel version it should build just fine, only way to find out is to attempt a build :p

Tschau nepo

I have an OrangePi PC running Armbian & the dev kernel (4.10

I can tell you only that you can't make it work on 3.4.113 kernel. According to RPi log you provided, Astrometa stick uses RTL2832 chip, which is supported on media_build, but only if you have kernel 4.7 or newer. Here is the relevant info: https://git.linuxtv.org/media_build.git/tree/v4l/versions.txt#n4

joey ramone wrote:

[...]
I've tried with a Astrometa stick (mn88473 for dvb-C) and kernel 4.10, the same problems like here https://forum.libreelec.tv/thread-4235.html . Same, cable, same device ... with Raspi3 no problems.

I have the older astrometa (mn88472) but decided to dump it in my "crap drawer" because (at the time) the drivers weren't very good, thankfully crope & the gang have improved them a lot. I really should give it a run on my Banana Pi.

Oh I forgot to mention I only have access to DVB-T so the bitrates are lower.

But I can't compile mn88473 for kernel 3.4

Thanks for the link & while the astrometa driver uses a different module to the MyGica, that page lists the module (si2168) as needing kernel 4.7+!

[...]

that page lists the module (si2168) as needing kernel 4.7+!

What is the solution ?
Perhapts another stick for kernel 3.4, I can't find anything !