so we need to compile this kernel and the internal tuner will start working?
I do not think so. It is not enough. We also need the right device tree for this box.
Hi All,
I have GTMEDIA GTT-2 box. I managed to build the driver for dvb tuner and it works with no issues (except for signal reporting statistics which supports only old style dvb API and I’m not sure shows proper values).
The driver is included in the dvb-latest addon and available on my CoreELEC fork (here).
To build it:
DEVICE=Amlogic-ng ./scripts/create_addon dvb-latest
or use prebuilt version:
driver.dvb.dvb-latest-21.2.0.zip (3.6 MB)
The driver for cxd2878 family (GTT-2 includes cxd2856 demodulator + mxl603 tuner) of dvb emulators was taken from here. I don’t know if this driver will work with GTC or GTS.
With small cleanups, my branch could be merged into upstream CoreELEC repo if maintainers are interested.
Another problem that I had with this box was installation to emmc with kernel version 4.9 (on 3.14 no issues). Actually the problem was with unstable emmc driver ? It was crashing when writing / reading data to / from emmc. To solve that I upgraded the bootloader partition. There is no upgrade from GTMEDIA available, and I used the update for MECOOL KI PRO. The upgrade file is named KI_PRO_AVL6862-NHG47L-20190314.112408.V0213.img and I downloaded it from here. I only uploaded bootloader partition from this image file (be aware that it will change the ir wakeup code to the one used on KI PRO box).
Thank you for your distribution!
Please make a PR to the correct repo:
Please respect others work and pick directly, at best original commits so the author and commit message stay preserved.
thx
@Portisch ok, i’ll try to make a PR. Any hints on how to preserve original commits? I used git format-patch on source repo and git am on media_tree_aml repo but there is like 10 commits related to cxd2878 driver files and folder structures are different between repos so the result is that the driver files end up in separate folder. I can move them to the proper location in separate commit but I’m not sure od all this make sense.
yes, this would be the way. the paths must be fixed, sure.
or you give us the list of commits (SHAs) what need to be picked and we can try to merge them.
I created experimental DVB support for GTMedia GTC based on:
- CoreELEC 21.3
- Amlogic 4.9 kernel
- media_tree_aml commit:
5de4194a41241aea6c821aa8c39465859aaaf5f6
Supported hardware
- Sony CXD2856
- MxL603 for DVB-T/T2/C
- AV2018 for DVB-S/S2
- INN8186 LNB voltage controller
Tested functionality
- DVB-T2 tuning and playback
- DVB-S2 tuning and playback
- TVHeadend 4.3
- 13/18 V polarization switching
- DiSEqC motor operation
- Cold switching between terrestrial and satellite modes
The device exposes one hybrid frontend. DVB-T/T2/C and DVB-S/S2
cannot be used simultaneously.
dtb.img (54.2 KB)
driver.dvb.dvb-latest-21.3.0.zip (3.6 MB)
is support Availink avl6862?
I am using your latest DVB driver package (driver.dvb.dvb-latest-21.3.0.zip) on my GTMedia GTC (S905D). However, I am still getting the i2c wrm err(-6) error and crash loop during tuning, even with the LNB coaxial cable disconnected.
diseqc: failed to set voltage (e=No such device or address) mpegts: 12092V in LNB 6-7.0W:Nilesat-20 - tuning on GTMedia GTC CXD2856 hybrid #0 : DVB-S #0 2026-09-07 09:13:51.632 diseqc: failed to set voltage (e=No such device or address)
My device is GTMedia GTS, still getting i2c wrm err(-6).