Dvb-t2-geniatech-mygica-t230 don't work

mbailen · 29 December 2018 08:55

Hello.

I just receive my New Vero 4k but TVH doesn’t recognise my dvb-t2, so far It has worked propierly in my Raspberry Pi 3.
Vero4k lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0572:c689 Conexant Systems (Rockwell), Inc. Bus 001 Device 002: ID 2017:1688
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Vero4k dmesg | grep “usb 1-2”
[ 3.167016] usb 1-2: new high-speed USB device number 3 using xhci-hcd
[ 3.307411] usb 1-2: New USB device found, idVendor=0572, idProduct=c689
[ 3.307422] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.307427] usb 1-2: Product: EyeTV Stick
[ 3.307432] usb 1-2: Manufacturer: Geniatech
[ 3.307437] usb 1-2: SerialNumber: 160421
[ 187.231754] usb 1-2: USB disconnect, device number 3
[ 191.444905] usb 1-2: new high-speed USB device number 4 using xhci-hcd
[ 191.585255] usb 1-2: New USB device found, idVendor=0572, idProduct=c689
[ 191.585266] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 191.585272] usb 1-2: Product: EyeTV Stick
[ 191.585277] usb 1-2: Manufacturer: Geniatech
[ 191.585282] usb 1-2: SerialNumber: 160421

Vero4k log:
https://paste.osmc.tv/helekecifu

Thanks in advance.

grahamh · 29 December 2018 09:44

You may be missing the correct firmware files. Have a look at dmesg on the Pi and see which files it’s loading, and copy those files across to /lib/firmware on vero. There are several versions of the firmware files for these sticks.

If that doesn’t work, 0572:c689 will have to be added to the drivers we build. Older versions of the stick were 0572:c688.

mbailen · 29 December 2018 12:14

I have copied the files but nothing has changed .

When you think about adding it?
Can I do something in the meantime?

Thanks.

grahamh · 29 December 2018 12:20

@sam_nazarko can usually do these things within days but I don’t know how busy he is. I can only suggest you use the Pi as the PVR server in the meantime and point the Vero’s PVR client at it if you are using Vero for everything else.

sam_nazarko · 29 December 2018 23:15

If it’s as simple as needing to add the new VID/PID; then you can try forcing the current driver.

Can you show us lsmod output on RPI vs Vero with the dongle attached?

Cheers

Sam

mbailen · 30 December 2018 09:57

Hi, there you are.

Vero4k lsmod:

osmc@osmc:~$ lsmod
Module                  Size  Used by
8021q                  18999  0
btsdio                  3186  0
bluetooth             251531  1 btsdio
6lowpan_iphc            6007  1 bluetooth
iptable_nat             2772  0
nf_conntrack_ipv4       7917  1
nf_defrag_ipv4          1441  1 nf_conntrack_ipv4
nf_nat_ipv4             3566  1 iptable_nat
nf_nat                 12609  2 nf_nat_ipv4,iptable_nat
nf_conntrack           55667  4 nf_nat,nf_nat_ipv4,iptable_nat,nf_conntrack_ipv4
iptable_filter          1478  0
dhd                   723320  0
cfg80211              356403  1 dhd
dwc_otg               231871  0
wifi_dummy               798  0
mali                  196602  5
ir_lirc_codec           4708  3
lirc_dev                7992  1 ir_lirc_codec
meson_ir                3981  0
rc_core                22791  4 lirc_dev,meson_ir,ir_lirc_codec
amlvideodri            11554  0
videobuf_res            5514  1 amlvideodri
videobuf_core          16691  2 amlvideodri,videobuf_res
videodev              148029  1 amlvideodri
media                  21515  1 videodev
ip_tables              16731  2 iptable_filter,iptable_nat
x_tables               18035  2 ip_tables,iptable_filter

Pi3 lsmod:

osmc@pi3:~$ lsmod
Module                  Size  Used by
bnep                   20480  2
hci_uart               20480  1
bluetooth             409600  23 hci_uart,bnep
ecdh_generic           36864  1 bluetooth
8021q                  32768  0
garp                   20480  1 8021q
stp                    16384  1 garp
llc                    16384  2 garp,stp
iptable_nat            16384  0
nf_conntrack_ipv4      16384  1
nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
nf_nat_ipv4            16384  1 iptable_nat
nf_nat                 32768  1 nf_nat_ipv4
nf_conntrack          139264  3 nf_conntrack_ipv4,nf_nat_ipv4,nf_nat
iptable_mangle         16384  0
uinput                 20480  1
iptable_filter         16384  0
rc_total_media_in_hand_02    16384  0
si2157                 16384  1
media                  36864  1 si2157
si2168                 20480  1
i2c_mux                16384  1 si2168
brcmfmac              262144  0
brcmutil               16384  1 brcmfmac
dvb_usb_cxusb          61440  1
rc_rc6_mce             16384  0
dib0070                28672  1 dvb_usb_cxusb
cfg80211              626688  1 brcmfmac
dvb_usb                32768  1 dvb_usb_cxusb
ir_lirc_codec          16384  2
dvb_core              114688  1 dvb_usb
lirc_dev               20480  1 ir_lirc_codec
snd_usb_audio         180224  0
evdev                  24576  4
rfkill                 28672  5 bluetooth,cfg80211
snd_hwdep              16384  1 snd_usb_audio
mceusb                 20480  0
snd_usbmidi_lib        36864  1 snd_usb_audio
rc_core                45056  9 mceusb,rc_total_media_in_hand_02,rc_rc6_mce,dvb_usb_cxusb,ir_lirc_codec,dvb_usb,lirc_dev
snd_rawmidi            32768  1 snd_usbmidi_lib
sg                     32768  0
snd_seq_device         16384  1 snd_rawmidi
snd_bcm2835            32768  0
snd_pcm               114688  2 snd_usb_audio,snd_bcm2835
snd_timer              36864  1 snd_pcm
snd                    86016  8 snd_hwdep,snd_usb_audio,snd_timer,snd_rawmidi,snd_usbmidi_lib,snd_seq_device,snd_bcm2835,snd_pcm
bcm2835_gpiomem        16384  0
bcm2835_thermal        16384  0
uio_pdrv_genirq        16384  0
uio                    20480  1 uio_pdrv_genirq
fixed                  16384  0
ip_tables              24576  3 iptable_mangle,iptable_filter,iptable_nat
x_tables               36864  3 iptable_mangle,ip_tables,iptable_filter
ipv6                  475136  50

sam_nazarko · 30 December 2018 20:25

Ok — I will try and get some time to look in to this shortly

Sam

grahamh · 1 January 2019 17:34

I just found something you could try:

unplug the stick

sudo modprobe  dvb_usb_cxusb
echo "0572 c689" | sudo tee /sys/module/dvb_usb_cxusb/drivers/usb:dvb_usb_cxusb/new_id

plug in the stick

mbailen · 1 January 2019 18:37

Thank you grahamh, I tried but after plug in the stick I have got:
osmc@osmc:~$ dmesg | grep dvb
[ 80.231732] usbcore: registered new interface driver dvb_usb_cxusb
[ 136.447930] dvb_usb_cxusb: probe of 1-2:1.0 failed with error -22

I restart the sistem and I had not out for dmesg |grep dvb.

Then I have got this with dmesg | grep usb:

[ 3.166825] usb 1-2: new high-speed USB device number 3 using xhci-hcd
[ 3.307272] usb 1-2: New USB device found, idVendor=0572, idProduct=c689
[ 3.307283] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.307288] usb 1-2: Product: EyeTV Stick
[ 3.307293] usb 1-2: Manufacturer: Geniatech
[ 3.307298] usb 1-2: SerialNumber: 160421
9165ba166cac5e8c9abda2012ea37cc3430c0b14 [media] usbtv: add sharpness control
9165ba166cac5e8c9abda2012ea37cc3430c0b14 [media] usbtv: add sharpness control
[ 4.524977] dwc_otg: usb0: type: 2 speed: 0, config: 0, dma: 0, id: 0, phy: d0078000, ctrl: 0
[ 4.524991] dwc_otg_driver_probe host only, not probe usb_otg!!!

grahamh · 1 January 2019 20:44

Hmmm. I was just trying something @fzinken suggested. After restarting, you will be back to square one so no surprise there. It’s possible you need to ‘manually’ start other drivers on which dvd_usb_cxusb depends as well. I don’t really know enough about how drivers are loaded to advise you but someone else may.

jahutchi · 1 January 2019 22:11

If it helps i run two of these adapters on a standalone x86_64 machine running debian stretch. I just ran lsmod on there and can see the following modules are loaded to support this device:

dvb_usb
dvb_core
dib0070
dvb_usb_cxusb
si2168
i2c_mux

sam_nazarko · 1 January 2019 22:13

The SI2168 module is supported; so it may just be a case of adding support for the new VID/PID.

grahamh · 1 January 2019 23:51

I would think so.

jahutchi · 2 January 2019 07:01

This is the VID/PID for the T230C rather than the T230. I found some useful info here:
https://www.linuxtv.org/wiki/index.php/Geniatech_T230C

T230 is supported out of the box in linux kernel but not T230C.

Looks like work was done in libreelec to support this dongle.

sam_nazarko · 2 January 2019 08:35

Those patches are for Intel kernels; so won’t be applicable here.

daniel7 · 27 January 2019 18:31

I can confirm the T230C was working on my RPi3 running Archlinux ARM.
Both RPi3 and Vero4k are AArch64 CPUs, no?

sam_nazarko · 27 January 2019 20:15

Yes – but we use an armhf userland; albeit 64-bit kernel on 4K/4K +

Sam

mbailen · 26 April 2019 18:49

Hi.
After April update, the stick stills not working in Vero 4k, I don´t know if I can do somethink now, I hope you are less busy to have a look to this issue.

Thank you.

sam_nazarko · 26 April 2019 20:05

I will update the DVB stack with the next major kernel release

Sam