But is there any hardware working without porting drivers stopped working after you make backporting
There were some reports, but I don't remember which. I don't have any DVB dongle.
jernej i have a usb dvb-s2, which is a clone of geniatech hdstar. This device is called DS3000 revision 2.1.
I can use it on ubuntu 14.04 which has 3.19.0-59-generic kernel.
I guess porting the firmware from ubuntu to arm is not enough to make it work. What am i missing?
Geniatech MyGica T230 seems to work fine in your OpenELEC
also made it run on current Armbian H3 with modprobe --force
Does it work with native 3.4 drivers?
jernej replied at 2016-6-18 18:24
Does it work with native 3.4 drivers?
the T230?
it works with the backported media_build drivers you include
it wont work with vanilla 3.4 as officially in kernel >3.19 only
First, I want to say a big thank you to jernej for your fantastic work!
My posting is in this thread as the issue is a backported driver. I have a MyGica T230 which is recognized without problems in the 05-10 build, but not the 06-02 one. This is an excerpt of the dmesg log:
[ 20.809668] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
[ 20.809676]d3f5193019443ef8e556b64f3cd359773c4d377b Merge tag 'v4.6-rc1' into patchwork
[ 20.809683]f55532a0c0b8bb6148f4e07853b876ef73bc69ca Linux 4.6-rc1
[ 20.809689]d5a38f6e4668b3110a66cd96ce2096184bf66def Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client
[ 20.844678] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
[ 22.075435] gmac0: probed
[ 22.075855] gmac0 gmac0: eth0: eth0: PHY ID 00441400 at 0 IRQ poll (gmac0-0:00)
[ 22.103597] 8021q: 802.1Q VLAN Support v1.8
[ 22.990274] dvb-usb: bulk message failed: -110 (1/0)
[ 23.100769] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 23.101065] DVB: registering new adapter (Mygica T230 DVB-T/T2/C)
[ 23.101107] usb 3-1: media controller created
[ 23.104137] dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 23.133843] i2c i2c-1: Added multiplexed i2c bus 2
[ 23.133881] si2168 1-0064: Silicon Labs Si2168 successfully attached
[ 25.140261] dvb-usb: bulk message failed: -110 (6/0)
[ 27.140264] dvb-usb: bulk message failed: -110 (6/0)
[ 27.140331] si2157: probe of 2-0060 failed with error -121
[ 27.141229] dvb-usb: no frontend was attached by 'Mygica T230 DVB-T/T2/C'
[ 27.142500] dvb-usb: schedule remote query interval to 100 msecs.
[ 27.902199] state:1 valid
[ 27.902215] state:3 valid
[ 27.902221] state:7 valid
[ 29.140244] dvb-usb: bulk message failed: -110 (2/0)
[ 29.140277] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 29.140469] usbcore: registered new interface driver dvb_usb_cxusb
[ 31.140395] dvb-usb: bulk message failed: -110 (1/0)
[ 33.240258] dvb-usb: bulk message failed: -110 (1/0)
[ 35.340229] dvb-usb: bulk message failed: -110 (1/0)
[ 37.440271] dvb-usb: bulk message failed: -110 (1/0)
The "dvb-usb: bulk message failed: -110 (1/0)" error is then repeated often.
Let me describe for what I use my OPi PC: As as selfmade receiver and recorder for the newly introduced DVB-T2 with H.265 in Germany. As tvheadend can stream over network, I could attach the stick to my RasPi, which has a recent kernel and stream to the OPi, but that means running 2 devices.
If it is too much hassle for you and slows you down from important improvements, then drop the backported drivers. If I understand it correctly, it is an issue of a few months only until there is a mainline kernel for the OPi and then we have the drivers back.
Edited by giaur500 at 2016-6-23 18:30
Actually, due to missing vsync, dvb-t on OPI is generally useless. You will get jerky image with horizontal artiffacts (unless your dvb-t is not interlaced) - especially on dynamic scenes. So 1080i (hd) and 576i (sd) dvb-t is rather horrible experience. I would not recommend it, so dvb drivers don't matter. There is 720p dvb-t standard also, but it's not widely used.
In summary, I think there is nothing to fight for now. First need to focus on vsync, then dvb-t in later time. I however got sad news from jernej, this is difficult and no chance in near future.
have any of you tried the armbian with 4.x kernel as a dvb host to stream on lan? would that help the dvb drivers work?
giaur500 replied at 2016-6-23 18:20
Actually, due to missing vsync, dvb-t on OPI is generally useless. You will get jerky image with hor ...
German public television (I watch only public TV) uses 720p for DVB-C and DVB-S. All broadcasters in Germany will use 1080p for DVB-T2 (you can see at https://de.wikipedia.org/wiki/DVB-T2_HD#Senderangebot_Pilotmux (in German, but numbers are the same in English)).
So the vsync issue is no problem for me. Indeed, if I stream the DVB-T2 stream from another device and use Kodi on the OPi PC the picture is perfect :)