opi Openelec and dvb_usb_rtl2832u (again)

Xer0

also @jernej, if you want to bother:
https://github.com/igorpecovnik/ ... lt/02-rtl2832.patch
thats the patch which makes his dongle run on Armbian

jernej

Xer0 replied at 2016-6-18 21:10
also @jernej, if you want to bother:
https://github.com/igorpecovnik/lib/blob/master/patch/kernel/su ...

Thanks. I will drop backported drivers and integrate this one.

jernej

vlaho replied at 2016-6-18 15:04
Hi guys,

you might be right - I am not kernel devloper, I don't have your expertise on that,

This build should have support for your cheap dongle:
https://transfer.sh/QCM3m/openel ... r22862-gdcf55f8.tar

vlaho

Hi guys,

thank you for spending your time on this issue - I really appreciate this, and for sure lot of others -
they were asking for rtl2832u support before me;


" RTL2832U is absolutely most common USB DVB-T chip. I could guess it is due to cheap price,
vendor provided reference designs with a huge amount of supported RF tuners and also
vendor provided Linux driver. One notable thing for popularity is surely also possibility of use it as a poor man's SDR."
Antti Palosaari


And re. plain dvb-t :  it will remain in service for a time for fta: public service, local news - you can not force population
to buy new equipment every few years to have acces to public service - and this is exactly use of tv dongle - instant and constant
acces to public service, local news; you know, ordinary people (like me) still want access to fta channels;   dvb-t2 is primary for pay-tv,
but for that I suppose anyone who uses Kodi for that would go IPTV anyways.


Re. your advices:
- I tried to insmod   armbian .ko,  but no luck   -  insmod refuses to load it  due to wrong format.


- I tried installing suggested older distribution, but no luck also:  only dvb_usb_rtl28xxu.ko is present.
  There were  some versions of dvb_usb_rtl28xxu drivers supporting rtl2832u dongle, but they require
   rtl2832 module as dependency and this one is not present in this distribution.


Regards

jernej

vlaho replied at 2016-6-19 12:07
Hi guys,

thank you for spending your time on this issue - I really appreciate this, and for sure lo ...

I linked you above newly compiled update file which should work with your dongle. And one last request - I would like to see vendor & device ID from your dongle (lsusb)

vlaho

this one is  vanilla+fake: has Trektstor printed on it (!) (? why make fake out of vanilla ?):

Bus 004 Device 006: ID 1f4d:c803 G-Tek Electronics Group
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x1f4d G-Tek Electronics Group
  idProduct          0xc803
  bcdDevice            1.00
  iManufacturer           1 Realtek
  iProduct                2 RTL2838UHIDIR
  iSerial                 3 00000001
  bNumConfigurations      1


this one is total no name - but it is pure generic RTL2838U - most probably reference design:


Bus 004 Device 008: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0bda Realtek Semiconductor Corp.
  idProduct          0x2838 RTL2838 DVB-T
  bcdDevice            1.00
  iManufacturer           1 Realtek
  iProduct                2 RTL2838UHIDIR
  iSerial                 3 00000001
  bNumConfigurations      1



Regards

jernej

vlaho replied at 2016-6-19 12:28
this one is  vanilla+fake: has Trektstor printed on it (!) (? why make fake out of vanilla ?):

Bus  ...

Ok, tnx. Both should be supported with this update:
https://transfer.sh/QCM3m/openel ... r22862-gdcf55f8.tar

Xer0

vlaho replied at 2016-6-19 19:28
this one is  vanilla+fake: has Trektstor printed on it (!) (? why make fake out of vanilla ?):

Bus  ...

vlaho replied at 2016-6-19 19:28
this one is  vanilla+fake: has Trektstor printed on it (!) (? why make fake out of vanilla ?):

it's not "fake",
Trekstor is a german distributor who re-labels stuff produced in china, legal and common practice

@insmod: you cant do it with insmod, sadly, because its missing the --force option here
you need to either somehow put the *.ko's into /lib/modules/$uname-r/drivers/
or, symlink/submount them like OpenWRT does it (where rootfs is also read-only)
...and then you can finally use modprobe --force $module (without .ko!)

@jernej: why dropping backported drivers?
i use them on Armbian and they coexist with this patch - media_build just will skip rtl283x then

jernej

Because official OpenELEC has done so a long time ago, probably with a reason. Also I had issues with media_build site, it was unreachable for about a day. This is an issue, because due to a special build system, source is downloaded each time. Some drivers, which works in 3.4, are also not possible to build with media_build repo. Last, but not least, media_build repo has a big fat warning that it's usage is not recommended for production and might have additional bugs... Standard way to improve things is to add patch as it happened in this case.

If you really want media_build drivers, clone my repo, include them and build your own image. I'm done with them for good.

Xer0

jernej replied at 2016-6-19 20:51
Because official OpenELEC has done so a long time ago, probably with a reason. Also I had issues wit ...

mh, do you compile media_build with the script or manually with make?
because once make download untar is run and patches applied, you can recompile any time without altering anything
yeah, the "supported" 3.4 drivers which will fail because hard-coded to x86 arch are annoying, took me long for a final .config

but well, i only need the mygica t230 supported, so i can find my way to get it working on newer builds, yes