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...

Graham H

Crni Gruja wrote:
> Try this one Graham
>

> Cheers

Thanks, I will certainly try but I'm not sure how to build from a local linux-media.tar. If I run ./build doesn't it still go away and download the latest git?

Also, do I need the kernel source, and if so, does that just come from kernel.org and where do I put it?

Sorry for my ignorance.
G

Crni Gruja

Graham Horner wrote:

> Thanks, I will certainly try but I'm not sure how to build from a local linux-media.tar. If I run ./build doesn't it still go away and download the latest git?

In the attachment is modified build script to use local linux-media from 2014-11-25

That is how I made it and it works.

> Also, do I need the kernel source, and if so, does that just come from kernel.org and where do I put it?

You need kernel source from your own Linux distribution NOT from kernel.org

Graham H

Thanks again, Crni. Got it working, now!! I must learn to speak perl.

Crni Gruja

Graham Horner wrote:
> Thanks again, Crni. Got it working, now!! I must learn to speak perl.

Also, many thanks to Crazy Cat who modified tuner driver for this device.

Olli Salonen

Any Geniatech T230 users here that could test if my OpenELEC build works fine for you?

http://openelec.tv/forum/71-pvr-live-tv/74370-build-with-geniatech-t230-support

noggin

Quick question. Are the patches for the original August T210 in the standard Ubuntu 14.10 distro and/or the standard V4L media_build, or do we still need to patch ? Have been using OpenElec for ages, but thought I'd roll-my-own Ubuntu-based TV server and wanted to check.

Olli Salonen

If I remember correctly, the T210 patches are in kernel 3.17. Which kernel the Ubuntu 14.10 has?

And yes, they're in media_build - no need to do any extra patching.

Graham H

Olli Salonen wrote:
> Any Geniatech T230 users here that could test if my OpenELEC build works fine for you?
>

> http://openelec.tv/forum/71-pvr-live-tv/74370-build-with-geniatech-t230-support

Nice work, Olli! Set up Openelec on the RPi with your build and tvheadend found all the channels expected in UK with the August T210v2. In fact, it worked better than the CrazyCat/Crni setup on Linux Mint (which has so far failed to find any T2 broadcasts.) Managed to record a SD (DVB-T) broadcast from tvheadend but so far Kodi can't get any video real time, only audio. I doubt this has anything to do with your driver. I read I need to buy a MPEG2 decoder.

HD (T2) broadcasts display and record fine.

Upgraded to OE 5.0 and support was lost.

HTH

Graham H

Has anyone got tvheadend to pick up UK freeview channel numbers with this dongle? I thought it was just never going to work, but after this bugfix https://tvheadend.org/issues/2583 I now get LCNs for BBC-B only. I'm wondering if there's something in the driver that works with T2 signals but not with DVB-T. Any pointers to troubleshooting this would be appreciated since entering LCNs by hand is a PITA.

@Stephen: are you using the T210v2 to get those LCNs?
[edit] OK, thanks, saw your post on the issues page, so anyone with a T210v2 (0572:c688) got this to work?

Ish Ramjan

Hi,

First off, thanks for the work that's being done here, it's great.

I need some help and my Google-fu is failing me. I've trying to get an August T210 v2 working and this thread had proved very helpful but I'm stuck with errors that appear to have been resolved for others, but I can't seem to get round using the same resolutions. Wondering if anyone can offer any advice/suggestions?

I got the error -22 just like Crni and Graham Horner using the latest media_build, the version posted by Crni 24 days ago resolved that issue and my device was recognised once I put the firmware files in the correct folder.

I could now select it in Tvheadend, but I wasn't able to see any channels. I noticed when I dmesg | grep dvb, that there seems to be an issue loading dvb-tuner-si2158-a20-01.fw, and I've assumed that's because I had not applied 0003-cxusb-Geniatech-T230-support.patch mentioned earlier in the thread.

I'm now running into a very similar issue as Kevin Panton who was getting an error "can't select all drivers at ./build line 490, but I've already tried the patch file posted by Deri James, but with the same result.

Any ideas?

Edit: I'm using kernel 3.19 with Ubuntu server 14.04. If I build without the 0003-cuxb patch it succeeds but then I can tune anything and get the error loading dvb-tuner previously mentioned.

****************
* Start building *
****************
make -C /home/tkball/media_build/v4l allyesconfig
make[1]: Entering directory `/home/tkball/media_build/v4l'
make[2]: Entering directory `/home/tkball/media_build/linux'
Applying patches for kernel 3.19.0-031900rc2-generic
patch -s -f -N -p1 -i ../backports/api_version.patch
patch -s -f -N -p1 -i ../backports/pr_fmt.patch
patch -s -f -N -p1 -i ../backports/debug.patch
patch -s -f -N -p1 -i ../backports/drx39xxj.patch
patch -s -f -N -p1 -i ../backports/0003-cxusb-Geniatech-T230-support.patch
1 out of 1 hunk FAILED
2 out of 6 hunks FAILED
make[2]:* [apply_patches] Error 1
make[2]: Leaving directory `/home/tkball/media_build/linux'
make[1]:* [allyesconfig] Error 2
make[1]: Leaving directory `/home/tkball/media_build/v4l'
make:* [allyesconfig] Error 2
can't select all drivers at ./build line 490.

Graham H

I didn't need that patch but was building from an earlier kernel. There is a trivial warning on one of the firmware files about renaming it but it works without renaming. If you can watch TV with vlc using Capture device there's probably nothing wrong with the driver.

Can you describe better what 'wasn't able to see any channels' means. Do you have any muxes showing and is tvh scanning?

Ish Ramjan

Edit: should probably mentioned this is a headless Ubuntu server.

I can manually add muxes and they are all showing at 100%, but no services are being discovered when scanned. Network, NetworkID and MuxID remain blank.

I've not tried VLC.

This is the error I see when I dmesg | grep dvb. I've replaced dvb-tuner-si2158* a couple of times in case it was corrupted

[ 2.989599] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
[ 3.238446] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 3.262336] dvb-usb: schedule remote query interval to 100 msecs.
[ 3.262361] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 3.263673] usbcore: registered new interface driver dvb_usb_cxusb
[ 5.360527] dvb-usb: recv bulk message failed: -110
[ 5.912574] si2168 2-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 15.777685] si2157 3-0060: firmware file 'dvb-tuner-si2158-a20-01.fw' is invalid

Graham H

Oh dear. This one works for me. I suppose you can't expect to tune any channels if your tuner isn't working.

Olli Salonen

The firmware posted by Graham is correct. It's also exactly the same file as in the OpenELEC github repo: https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-tuner-si2158-a20-01.fw

Do note that if you download from the above github repo, you will need to click the "Raw" button to get the raw binary file! The file length should be divideable with 17, and if not, you will get the error about invalid firmware file.

Ish Ramjan

Edit: Thanks Olli too, this explains why I was getting the issue, I hadn't selected raw on that file.

Thanks Graham, this moves me a step forwards. No longer getting the invalid error. Still getting "recv bulk message failed: -110", and I don't know if this is an issue.

Rescanning now, will give it 15 mins to see if any services appear.

:~$ dmesg | grep dvb
[ 3.114524] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
[ 3.374440] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 3.461737] dvb-usb: schedule remote query interval to 100 msecs.
[ 3.461801] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 3.461843] usbcore: registered new interface driver dvb_usb_cxusb
[ 5.560671] dvb-usb: recv bulk message failed: -110
[ 5.992937] si2168 2-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 15.886479] si2157 3-0060: downloading firmware from file 'dvb-tuner-si2158-a20-01.fw'

Ish Ramjan

OK, no luck with getting any services, but I assume that will be the unresolved -110 error. When scanning the log is showing status changed to No signal. I've checked with a Windows laptop at the same location, plugged into the same aerial with this adapter and the signal is strong, no issues with SD or HD content, so I'm confident there is a signal.

Could this be related to the 0003-cxusb-Geniatech-T230-support.patch?

Jan 09 17:54:09.986 dvb: Adapter "Silicon Labs Si2168" Enabled
Jan 09 17:54:10.005 dvb: /dev/dvb/adapter0 opened frontend /dev/dvb/adapter0/frontend0
Jan 09 17:54:10.005 dvb: "/dev/dvb/adapter0" tuning to "674,000 kHz" (Initial autoscan)
Jan 09 17:54:14.042 dvb: "674,000 kHz" on adapter "Silicon Labs Si2168", status changed to No signal
Jan 09 17:54:30.010 dvb: "/dev/dvb/adapter0" tuning to "650,000 kHz" (Initial autoscan)
Jan 09 17:54:34.027 dvb: "650,000 kHz" on adapter "Silicon Labs Si2168", status changed to No signal
Jan 09 17:54:50.007 dvb: "/dev/dvb/adapter0" tuning to "626,000 kHz" (Initial autoscan)
Jan 09 17:54:54.058 dvb: "626,000 kHz" on adapter "Silicon Labs Si2168", status changed to No signal
Jan 09 17:55:10.004 dvb: "/dev/dvb/adapter0" tuning to "526,000 kHz" (Initial autoscan)
Jan 09 17:55:13.034 dvb: "526,000 kHz" on adapter "Silicon Labs Si2168", status changed to No signal
Jan 09 17:55:30.003 dvb: "/dev/dvb/adapter0" tuning to "586,000 kHz" (Initial autoscan)
Jan 09 17:55:34.020 dvb: "586,000 kHz" on adapter "Silicon Labs Si2168", status changed to No signal
Jan 09 17:55:50.003 dvb: "/dev/dvb/adapter0" tuning to "634,200 kHz" (Initial autoscan)
Jan 09 17:55:54.028 dvb: "634,200 kHz" on adapter "Silicon Labs Si2168", status changed to No signal
Jan 09 17:56:10.001 dvb: "/dev/dvb/adapter0" tuning to "658,000 kHz" (Initial autoscan)
Jan 09 17:56:14.040 dvb: "658,000 kHz" on adapter "Silicon Labs Si2168", status changed to No signal
Jan 09 17:56:30.006 dvb: "/dev/dvb/adapter0" tuning to "682,000 kHz" (Initial autoscan)
Jan 09 17:56:34.019 dvb: "682,000 kHz" on adapter "Silicon Labs Si2168", status changed to No signal
Jan 09 17:56:50.003 dvb: "/dev/dvb/adapter0" tuning to "714,000 kHz" (Initial autoscan)
Jan 09 17:56:54.038 dvb: "714,000 kHz" on adapter "Silicon Labs Si2168", status changed to No signal

Graham H

Ish Ramjan wrote:

> Could this be related to the 0003-cxusb-Geniatech-T230-support.patch?

As I said, I didn't use it AFAIK.

Olli Salonen

If you do see message like:

[ 3.114524] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.

You should not need any patch. 0003-cxusb-Geniatech-T230-support.patch adds the code for detection of the device and if your device was detected, the patch is in your kernel modules already.

Do note that due to another issue, there's a problem in the current media_tree. If (and only if) you see the following error:

[ 409.328033] dvb_usb_cxusb: probe of 2-1:1.0 failed with error -22

You will need to apply the patch:

http://www.spinics.net/lists/linux-media/msg85125.html

Here are commands that fetch the current media_build, applies the patch and compiles it. Just tested on Ubuntu linux with kernel 3.18 that this works nicely:

git clone git://linuxtv.org/media_build.git cd media_build wget --no-check-certificate https://patchwork.linuxtv.org/patch/27777/raw/ -O backports/t230.patch sed -i 's/add api_version.patch/add api_version.patch\nadd t230.patch/' backports/backports.txt ./build sudo make install

Do note, that as soon as the patch mentioned above is in the media_tree, the above will not work anymore. After that you should follow the standard way to compile media_build: http://git.linuxtv.org/cgit.cgi/media_build.git/about/

Furthermore, note that your Linux kernel must be compiled with CONFIG_I2C_MUX, otherwise the module will not work. Most of the mainstream distros do have that in.

One more thing, this adapter supports DVB-T, DVB-T2 and DVB-C. Tvheadend 3.4 does not support multiple standards on a single adapter properly - make sure you're using 3.9.

Ish Ramjan

Thanks Olli,

I'm not getting error -22. I followed your instructions anyway as I figured nothing to lose, but I'm getting to the exact same state as before:

[ 3.263673] usbcore: registered new interface driver dvb_usb_cxusb

[ 5.360527] dvb-usb: recv bulk message failed: -110

Any ideas what this error relates to?

Ish Ramjan

FYI seem to have removed this error now, and looking much better when looking at dmesg.

Started to suspect a hardware issue due to what I could Google about the -110 error. Turns out when plugged in whilst using the supplied 6 inch USB extension I get the -110 error, and also with one I had lying around.

When plugged in directly the error is gone, and it is identified, connected and the interface driver is successfully registered.

Here's hoping a scan works now :)

« Previous Page Next Page »