MyGica (Geniatech) T230 DVB-T/C Stick isn't working in/with TVHeadend!

Good Morning,

yesterday I played a little bit with the RC and the TVHeadend package on my RPi 2 to get my dirt cheap MyGica (Geniatech) T230 DVB-T/C Stick to work, but, no luck, dmesg gave me a strange error:

Cannot add dependency job for unit display-manager.service
ignoring: Unit display-manager.service failed to load: No such file or directory.

Sorry, I’m REALLY no Linux expert, so, it would be nice if somebody could help me to get this thing working! :wink:

In Openelec it’s working like a charm (with an older Kernel) so it should (hopefully) be possible to get this thing working in OSMC! This would be great! :smile:

Thanks a lot!!!

Red_Z

Update: I read a little bit about the problem and maybe I have to enable (or install) KDM, hopefully this solves the problem! I will try it in the afternoon and tell you the results! :wink:

Which version of the Tvheadend package are you using?

I the only one I have managed to use successfully with my PCTV stick is one you compile yourself using the instructions posted by HarryL. I also found that I needed the access control file (both mentioned in OSMC RC Unable to install TVHEADEND - #49 by DBMandrake) and some firmware files I eventually found elsewhere on the net. I have failed to get my WinTV-HVR-900H working, possible due to the firmware files that worked on RASBMC.

Good evening,

have you tried to copy the xc3028L-v36.fw to /lib/firmware?

For my part…

I tried several things to get the Stick working, but I got errors which I do not understand and i can’t solve them…

I think I will wait for Kernel Version 3.19 which should solve the Problem by itself, because of the better DVB Stick support. (Driver implementation)

Hopefully the 3.19 Kernel will be implemented in OSMC soon! :slight_smile:

Just received MyGica T230 DVB-T/C.

Been trying for hours to scan channels but keep getting scan failed. Have installed correct firmware and the channels work fine on PC to rule out signal issue.

Any help would be appreciated.

osmc@osmc:~$ dmesg | grep dvb
[ 5.148233] dvb-usb: found a ‘Mygica T230 DVB-T/T2/C’ in warm state.
[ 5.392768] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.422623] dvb-usb: schedule remote query interval to 100 msecs.
[ 5.422703] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 5.422775] usbcore: registered new interface driver dvb_usb_cxusb
[ 24.809612] si2168 3-0064: downloading firmware from file ‘dvb-demod-si2168-b40-01.fw’
[ 25.560664] si2157 4-0060: downloading firmware from file ‘dvb-tuner-si2158-a20-01.fw’

This is what I get:

[    5.695919] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
[    5.937616] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    5.937891] DVB: registering new adapter (Mygica T230 DVB-T/T2/C)
[    5.960471] i2c i2c-3: Added multiplexed i2c bus 4
[    5.960493] si2168 3-0064: Silicon Labs Si2168 successfully attached
[    5.972923] si2157 4-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[    5.972982] usb 1-1.3: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[    5.973916] input: IR-receiver inside an USB DVB receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/input/input2
[    5.974172] dvb-usb: schedule remote query interval to 100 msecs.
[    5.974280] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[    5.974457] usbcore: registered new interface driver dvb_usb_cxusb
[   17.253213] si2168 3-0064: found a 'Silicon Labs Si2168-B40'
[   17.259220] si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[   17.827481] si2168 3-0064: firmware version: 4.0.4
[   17.838446] si2157 4-0060: found a 'Silicon Labs Si2148-A20'
[   17.851349] si2157 4-0060: downloading firmware from file 'dvb-tuner-si2158-a20-01.fw'
[   18.897107] si2157 4-0060: firmware version: 2.1.6

Mine is an August branded version. There are some different versions of the fw around. Look for August T210 on the tvheadend forum.

Hi graham Thanks for reply i tred few different fw plus the 4.0.4 and 2.1.6 like yours above still no luck.

Is your stick plugged directly into pi or hub?

Theres a fat-fs unmount error in dmesg log not sure if that could cause any issues.

usbcore: registered new interface driver rtl8192cu
[ 5.124581] usbcore: registered new interface driver brcmfmac
[ 5.128332] dvb-usb: found a ‘Mygica T230 DVB-T/T2/C’ in warm state.
[ 5.243062] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Dec 15 2015 18:10:45 version 7.45.41.23 (r606571) FWID 01-cc4eda9c
[ 5.259549] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 5.373845] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.374291] DVB: registering new adapter (Mygica T230 DVB-T/T2/C)
[ 5.386295] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 5.396153] i2c i2c-3: Added multiplexed i2c bus 4
[ 5.396168] si2168 3-0064: Silicon Labs Si2168 successfully attached
[ 5.409355] si2157 4-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[ 5.409403] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)…
[ 5.409900] input: IR-receiver inside an USB DVB receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/input/input2
[ 5.410036] dvb-usb: schedule remote query interval to 100 msecs.
[ 5.410097] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 5.412158] usbcore: registered new interface driver dvb_usb_cxusb
[ 5.907497] uart-pl011 3f201000.uart: no DMA platform data
[ 6.649331] systemd-journald[169]: Received request to flush runtime journal from PID 1
[ 7.514835] smsc95xx 1-1.1:1.0 eth0: hardware isn’t capable of remote wakeup
[ 7.515104] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.657110] brcmfmac: brcmf_add_if: ERROR: netdev:wlan1 already exists
[ 7.657128] brcmfmac: brcmf_add_if: ignore IF event
[ 7.661752] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 7.661770] brcmfmac: power management disabled

Directly.

I doubt it. It’s quite a common message. You could run fsck on it to be sure, though.

When I have a moment, I’ll try my stick on a fresh OSMC install. I had to compile both v4l and tvheadend when I started out but that was 3 years ago so I’d have thought all the necessary stuff would be in the kernel and tvh by now. BTW, are you using tvh? I could never get other linux tools like zap, scan or dvbscan to work.

Yeah using tvh and have it directly connected to pi also.

That be great if you could give it a test again on your side.

Thanks

OK. Fresh install on RPi2, and it all works, although I’m not enjoying what I’m seeing on the TV in Manchester. :cry:

For the record:

  • Install OSMC (May 2 2017) on SD card with Windows installer;
  • Configure WiFi and bluetooth (keyboard);
  • Check for updates (none);
  • Install AppStore TVH;
  • Configure TVH: Network then Adapter;
  • Make sure Adapter is enabled;
  • (no channels found) so checked /lib/firmware - files not there so copied them in;
  • Re-booted and TVH starts finding channels (after a while);
  • Click Map Services to Channels;
  • Back in OSMC Programs - Get more - MyAddons - PVR clients - Tvheadend HTSP Client - Configure;
  • Set username, password - osmc,osmc - otherwise accept defaults;
  • Works!

Thanks for testing graham.

Any chance you can upload the correct firmware files to dropbox or somewhere or show where I can download them.

Tried the openelec firmware didn’t work.

Cheers

That’s odd, because OpenElec put those fw files into their distro years ago. Try these.

Thanks graham I’ll test with those firmware later after work.

The only slight difference I see in your dmesg than mine is that yours says

Silicon Labs Si2148-A20

Whereas mine says

Silicon Labs Si2158-A20

Although they both ask for same fw files so not sure if it should make any difference.

Does your stick show signal strength in tvh? Mine only shows minus values -17.3db etc prob cause of wrong firmware.

Thanks again graham hopefully those fw files will solve it.

Cheers

No. Never has.

Edit: I tell a lie - it’s showing -46dB and SNR of 33dB or thereabouts.

The figures are always minus and -17.3 dBm is a very strong signal. If you’re interested, see this for an explanation of why they are always minus. So maybe not wrong firmware, though -17.3 dBm is suspiciously high.

Thanks for info dill

Although when I use my other dvb-s2 tuner the snr shows green 80% signal strength.

There is a setting in tvh “force old status” that uses old drivers for signal strength but usually doesn’t change much.

I see you corrected the signal strength. -46 dBm seems a lot more likely, but still very good.

I think most people can understand 80% signal strength whereas a dBm value will be meaningless to many.

Wohhoo finally got it working :slight_smile:

Tested on libreelec and it worked out of box so copied fw files and transferred over to OSMC. Channels scanning in now. For those looking for correct fw files that worked for me here details:

si2168 3-0064: found a ‘Silicon Labs Si2168-B40’
[ 24.520109] si2168 3-0064: downloading firmware from file ‘dvb-demod-si2168-b40-01.fw’
[ 25.265708] si2168 3-0064: firmware version: 4.0.11
[ 25.276858] si2157 4-0060: found a ‘Silicon Labs Si2158-A20’
[ 25.278856] si2157 4-0060: downloading firmware from file ‘dvb-tuner-si2158-a20-01.fw’
[ 26.490913] si2157 4-0060: firmware version: 2.1.9

Thanks to @grahamh for testing and helping me out appreciate it bro, you saved me from chucking this stick out of the window :smile: Patience sure is a virtue lol

Cheers

Forgive me if mentioned above, but you guys don’t mention if you are using DVB-C or DVB-T.

I’ve two great OSMC DVB-T2 sticks on my desk, but we need to make a commitment to a large volume. I’m wondering if there’s demand for a good DVB-T2 adapter that’s officially supported.

We plan to include firmware and driver support in OSMC and keep it supported for the forseeable future.

Interested in knowing what you think.

S

Hi Sam

My stick is dvb-t2. I think it also includes dvb-c also.

Yes I think having an offical osmc dvb-t2 in store would solve a lot of headaches. I also had to wait nearly 2 months getting it shipped from China too.

But glad its working now

YW and that’s useful to know. When I last looked, those later versions of the fw did not work with my August stick, which has the same vendor:device ID, so remind me not to have both sticks on the same system!