August DVB-T210

derp derp · 2014-02-11T22:48:40+00:00

Hi. Was wondering if this was compatible with tvheadend as there's not much information from users about this device. Does anyone have one? Is it working wel...

Ben Rometsch

OK well I tracked down those versions and interestingly it now all seems much more stable. Have attempted tuning several times over a few hours and nothing has crashed yet. Thanks for the help Graham.

Paul Williams

Any chance you could post a link to the 2.1.6 firmware so I can test?

Mine is showing a newer version (2.1.9), it works initially but falls over after less than an hour and cant tune anything.

Ben Rometsch

Try this:

https://db.tt/2eoUBS0S

Also attached to this message

Hopefully that works.

Unfortunately after a few days the stick crashed and I needed to reboot the pi to get things working again :( I guess a drastic solution would be to reboot in the night...Does anyone know what is causing things to fail?

Graham H

Try this...

Ben Rometsch

Ha I think we replied at the same time Graham!

Paul Williams

Thanks for the quick response, I will give it a go and report back :)

Olli Salonen

I see Antti has done some work with the device. Would be interesting to hear if it works better with the dvbsky driver :
https://git.linuxtv.org/anttip/media_tree.git/log/?h=mygica_t230_pt360

Paul Williams

Excuse my ignorance but how do I test that?

Do I just build the media_tree from source and install as described here:

https://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers

Paul Williams

Well I built and installed the full media_tree from git this morning and all looking good so far, fingers crossed....

dmesg | grep dvb
fb6609280db902bd5d34445fba1c926e95e63914 [media] dvb_frontend: Use memdup_user() rather than duplicating its implementation
fb6609280db902bd5d34445fba1c926e95e63914 [media] dvb_frontend: Use memdup_user() rather than duplicating its implementation
[ 14.899309] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
[ 15.135170] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 15.135503] dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 15.423526] dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
[ 15.423937] dvb-usb: schedule remote query interval to 100 msecs.
[ 15.423957] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 15.423976] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
[ 15.659075] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 15.659511] dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 15.670387] dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
[ 15.670911] dvb-usb: schedule remote query interval to 100 msecs.
[ 15.670932] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 15.670960] usbcore: registered new interface driver dvb_usb_cxusb
[ 96.532071] si2168 11-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'

[ 97.610843] si2168 9-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'

(I have 2 of the same devices plugged in)

Paul Williams

One thing I have noticed, my channels were scanned with my Sundtek tuner originally and I have a second copy of most muxes that are plus or minus 0.25Mhz different (is this down to tuner sensitivity?).

Any channels mapped that are mapped to the 0.25Mhz different muxes play fine using the Sundtek but fail with the DVB-T210's.

Think if I set up a new network for the DVB-T210's, let that scan in the working muxes for these tuners and then map the services found to existing channels again using merge same name its the easiest way to resolve this, unless anyone had any other suggestions?

Ben Rometsch

Paul Williams wrote:
> Well I built and installed the full media_tree from git this morning and all looking good so far, fingers crossed....
>
> dmesg | grep dvb
> fb6609280db902bd5d34445fba1c926e95e63914 [media] dvb_frontend: Use memdup_user() rather than duplicating its implementation
> fb6609280db902bd5d34445fba1c926e95e63914 [media] dvb_frontend: Use memdup_user() rather than duplicating its implementation
> [ 14.899309] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
> [ 15.135170] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
> [ 15.135503] dvb_create_media_entity: media entity 'dvb-demux' registered.
> [ 15.423526] dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
> [ 15.423937] dvb-usb: schedule remote query interval to 100 msecs.
> [ 15.423957] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
> [ 15.423976] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
> [ 15.659075] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
> [ 15.659511] dvb_create_media_entity: media entity 'dvb-demux' registered.
> [ 15.670387] dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
> [ 15.670911] dvb-usb: schedule remote query interval to 100 msecs.
> [ 15.670932] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
> [ 15.670960] usbcore: registered new interface driver dvb_usb_cxusb
> [ 96.532071] si2168 11-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
> [ 97.610843] si2168 9-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
>

> (I have 2 of the same devices plugged in)

How long had you been running before encountering stick failures? Also what firmware versions are you running? Forgive my ignorance but does compiling media_tree only create new /lib/firmware files or is there other stuff it is doing?

Olli Salonen

Using media_build to compile the drivers in media_tree typically replaces all your media device drivers under /lib/modules. The firmwares in /lib/firmware are mostly closed source binaries that have been ripped from the Windows drivers of the devices. They are just transferred to the device as is when the device is started (plugged in typically). That part will be the same regardless of the operating system.

Ben Rometsch

> fb6609280db902bd5d34445fba1c926e95e63914 [media] dvb_frontend: Use memdup_user() rather than duplicating its implementation

I have some experience compiling stuff but not a huge amount. I ran:

git clone git://linuxtv.org/media_build.git
cd media_build

./build

but it errors out with

./scripts/make_kconfig.pl /lib/modules/4.1.19-v7+/build /lib/modules/4.1.19-v7+/build 1
Preparing to compile for kernel version 4.1.19
File not found: /lib/modules/4.1.19-v7+/build/.config at ./scripts/make_kconfig.pl line 33, <IN> line 4.
Makefile:369: recipe for target 'allyesconfig' failed

make[1]:* [allyesconfig] Error 2

this is on a Raspberry Pi2 running Raspbian. Any ideas?

Paul Williams

I'm not sure about Raspian to be honest, looks like they were having the same issues here:

https://www.raspberrypi.org/forums/viewtopic.php?t=100618

Just to give an update, both my sticks have been idle for 12 hours over night and are still working fine this morning :)

I have attached the firmware that is now being used after the media_tree install but not sure if thats all that is needed?

Olli Salonen

Paul,

Do a "dmesg | grep si2168" and you'll see the firmware version printed out there. I think you have the oldest Si2168 firmware in use. Personally I've had good success with 4.0.11. 4.0.19 was a bit tricky, but I think there are improvements coming into the driver that will make 4.0.19 trouble-free as well.

You can find various SiLabs firmwares here:
http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/ (demod)
http://palosaari.fi/linux/v4l-dvb/firmware/Si2158/ (tuner)

Olli Salonen

Ben,

The way you've tried to use media_build is correct. Although that way will download the latest media_tree and the suggested code is not yet in the media_build, so you would need to compile the specific branch from Antti's development repository.

However, it's a good idea first to compile the normal media_tree to see that everything works.

I've got no idea why it's failing for you. Do you have the kernel sources package installed?

Ben Rometsch

Paul Williams wrote:
> I'm not sure about Raspian to be honest, looks like they were having the same issues here:
>
> https://www.raspberrypi.org/forums/viewtopic.php?t=100618 >
> Just to give an update, both my sticks have been idle for 12 hours over night and are still working fine this morning :)
>

> I have attached the firmware that is now being used after the media_tree install but not sure if thats all that is needed?

That firmware file is v4.0.4 that I have been using.

Zac Daman

I think I have the same problem with T230 and LE alpha. T230 get somehow jammed and needs to reboot the system and change the USB port to make T230 work again.

Normally system looks like:
> LibreELEC (community) Version: 7.90.004
> Kodi:~ # dmesg | grep si2168
> [ 16.136877] si2168 18-0064: Silicon Labs Si2168 successfully attached
> [ 24.049595] si2168 18-0064: found a 'Silicon Labs Si2168-B40'
> [ 24.054944] si2168 18-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
> [ 24.844042] si2168 18-0064: firmware version: 4.0.11
> Kodi:~ # dmesg | grep dvb
> [ 15.878400] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
> [ 16.113468] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
> [ 16.163590] dvb-usb: schedule remote query interval to 100 msecs.
> [ 16.165226] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
> [ 16.165312] usbcore: registered new interface driver dvb_usb_cxusb
> [ 28.873483] si2168 14-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
> [ 29.685284] si2157 15-0060: downloading firmware from file 'dvb-tuner-si2158-a20-01.fw'
> Kodi:~ #
>
After some time (a few hours or max a day) T230 cannot tune and make >100k errors and is not usable any more. And the system looks like:
> LibreELEC (community) Version: 7.90.004
> Kodi:~ # dmesg | grep si2168
> Kodi:~ # dmesg | grep dvb
> [25918.849795] dvb-usb: bulk message failed: -110 (1/0)
> [25920.853418] dvb-usb: bulk message failed: -110 (5/0)
> [25922.856876] dvb-usb: bulk message failed: -110 (1/0)
> [25924.860222] dvb-usb: bulk message failed: -110 (5/0)
> [25926.863533] dvb-usb: bulk message failed: -110 (1/0)
> [25928.867270] dvb-usb: bulk message failed: -110 (5/0)
> [25930.872922] dvb-usb: bulk message failed: -110 (1/0)
> [25932.874158] dvb-usb: bulk message failed: -110 (5/0)
> [25934.879900] dvb-usb: bulk message failed: -110 (1/0)
> [25936.880965] dvb-usb: bulk message failed: -110 (5/0)
> [25938.884508] dvb-usb: bulk message failed: -110 (1/0)
> [25940.887758] dvb-usb: bulk message failed: -110 (5/0)
> [25942.891194] dvb-usb: bulk message failed: -110 (1/0)
> [25944.894866] dvb-usb: bulk message failed: -110 (5/0)
> [25946.897962] dvb-usb: bulk message failed: -110 (1/0)
> [25948.898327] dvb-usb: bulk message failed: -110 (5/0)
> [25950.901686] dvb-usb: bulk message failed: -110 (1/0)
> [25952.905249] dvb-usb: bulk message failed: -110 (5/0)
> [25954.908480] dvb-usb: bulk message failed: -110 (1/0)
> [25956.912072] dvb-usb: bulk message failed: -110 (5/0)
> [25958.915400] dvb-usb: bulk message failed: -110 (1/0)
> [25960.918876] dvb-usb: bulk message failed: -110 (5/0)
> [25962.922235] dvb-usb: bulk message failed: -110 (1/0)
> [25964.925836] dvb-usb: bulk message failed: -110 (5/0)
> [25966.929292] dvb-usb: bulk message failed: -110 (1/0)
> [25968.932723] dvb-usb: bulk message failed: -110 (5/0)
> [25970.936341] dvb-usb: bulk message failed: -110 (1/0)
> [25972.939595] dvb-usb: bulk message failed: -110 (5/0)
> [25974.943155] dvb-usb: bulk message failed: -110 (1/0)

> ... and this shit goes on and on and on.....

Based on this long forum discussion I came to conclusion that I need to try another fw version from 4.0.11 -> 4.0.19 or 4.0.4 -> or maybe newer one if there is a better firmware. And this file update is a problem to me as a rookie Linux user.

I tried to replace the .fw file with other version in /lib/firmware and the system says that I cannot replace file(s) in the Read-only file system. Tried with telnet session and sftp and no luck. Question is how to replace the file?

mpmc

Izak Gambler wrote:
> I think I have the same problem with T230 and LE alpha. T230 get somehow jammed and needs to reboot the system and change the USB port to make T230 work again.
>
> Normally system looks like:
> > LibreELEC (community) Version: 7.90.004
> > Kodi:~ # dmesg | grep si2168
> > [ 16.136877] si2168 18-0064: Silicon Labs Si2168 successfully attached
> > [ 24.049595] si2168 18-0064: found a 'Silicon Labs Si2168-B40'
> > [ 24.054944] si2168 18-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
> > [ 24.844042] si2168 18-0064: firmware version: 4.0.11
> > Kodi:~ # dmesg | grep dvb
> > [ 15.878400] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
> > [ 16.113468] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
> > [ 16.163590] dvb-usb: schedule remote query interval to 100 msecs.
> > [ 16.165226] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
> > [ 16.165312] usbcore: registered new interface driver dvb_usb_cxusb
> > [ 28.873483] si2168 14-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
> > [ 29.685284] si2157 15-0060: downloading firmware from file 'dvb-tuner-si2158-a20-01.fw'
> > Kodi:~ #
> >
> After some time (a few hours or max a day) T230 cannot tune and make >100k errors and is not usable any more. And the system looks like:
> > LibreELEC (community) Version: 7.90.004
> > Kodi:~ # dmesg | grep si2168
> > Kodi:~ # dmesg | grep dvb
> > [25918.849795] dvb-usb: bulk message failed: -110 (1/0)
> > [25920.853418] dvb-usb: bulk message failed: -110 (5/0)
> > [25922.856876] dvb-usb: bulk message failed: -110 (1/0)
> > [25924.860222] dvb-usb: bulk message failed: -110 (5/0)
> > [25926.863533] dvb-usb: bulk message failed: -110 (1/0)
> > [25928.867270] dvb-usb: bulk message failed: -110 (5/0)
> > [25930.872922] dvb-usb: bulk message failed: -110 (1/0)
> > [25932.874158] dvb-usb: bulk message failed: -110 (5/0)
> > [25934.879900] dvb-usb: bulk message failed: -110 (1/0)
> > [25936.880965] dvb-usb: bulk message failed: -110 (5/0)
> > [25938.884508] dvb-usb: bulk message failed: -110 (1/0)
> > [25940.887758] dvb-usb: bulk message failed: -110 (5/0)
> > [25942.891194] dvb-usb: bulk message failed: -110 (1/0)
> > [25944.894866] dvb-usb: bulk message failed: -110 (5/0)
> > [25946.897962] dvb-usb: bulk message failed: -110 (1/0)
> > [25948.898327] dvb-usb: bulk message failed: -110 (5/0)
> > [25950.901686] dvb-usb: bulk message failed: -110 (1/0)
> > [25952.905249] dvb-usb: bulk message failed: -110 (5/0)
> > [25954.908480] dvb-usb: bulk message failed: -110 (1/0)
> > [25956.912072] dvb-usb: bulk message failed: -110 (5/0)
> > [25958.915400] dvb-usb: bulk message failed: -110 (1/0)
> > [25960.918876] dvb-usb: bulk message failed: -110 (5/0)
> > [25962.922235] dvb-usb: bulk message failed: -110 (1/0)
> > [25964.925836] dvb-usb: bulk message failed: -110 (5/0)
> > [25966.929292] dvb-usb: bulk message failed: -110 (1/0)
> > [25968.932723] dvb-usb: bulk message failed: -110 (5/0)
> > [25970.936341] dvb-usb: bulk message failed: -110 (1/0)
> > [25972.939595] dvb-usb: bulk message failed: -110 (5/0)
> > [25974.943155] dvb-usb: bulk message failed: -110 (1/0)
> > ... and this shit goes on and on and on.....
>
> Based on this long forum discussion I came to conclusion that I need to try another fw version from 4.0.11 -> 4.0.19 or 4.0.4 -> or maybe newer one if there is a better firmware. And this file update is a problem to me as a rookie Linux user.
>

>I tried to replace the .fw file with other version in /lib/firmware and the system says that I cannot replace file(s) in the Read-only file system. Tried with telnet session and sftp and no luck. Question is how to replace the file?

I believe you create the folder firmware in your storage path (usually /storage/.config/) somkdir /storage/.config/firmware should do it, place the file there and it'll override the default on next boot.

Ben Rometsch

> (I have 2 of the same devices plugged in)

Hi Paul,

Is your stick stable now with the build you put together?

« Previous Page Next Page »