Wrong DVB driver RPi linux 3.15.0

Fake Name

http://forum.xbmc.org/showthread.php?tid=192380&pid=1731753#pid1731753

Since this openelec build for the RPi (which updates the linux kernel to 3.15.0), my RPi recognises my Kworld UB499-2T T09(IT9137) as an Afatech AF9033 (DVB-T). Attempting to play channels with XBMC fails with error 'no free adapter'. Prior to this build loaded the correct driver and worked fine. Can anyone help me to get the RPi / tvheadend to load the correct driver?

I'm on TVH 3.9.681 from https://github.com/OpenELEC/OpenELEC.tv/pull/3250

Thanks in advance

ProfYaffle

Isn't Afatech simply the underlying chipset, vs Kworld as the card? That doesn't mean it's necessarily wrong.

Can you access anything through the tvh web interface? Can you play, or schedule/record? What does the web interface say about networks, muxes, services? Does it list one card or two (I've seen cards/chipsets report independently - on older versions of tvh, at least)? Is the card enabled, configured, etc.?

Sorry, lots of questions there, but let's try to understand the problem properly, at least.

Latty Jordan

I had the same problem, although with Arch Linux rather than openelec. It seems that the latest kernel upgrade helpfully includes lots of firmwares, but rather unhelpfully includes the wrong one for this stick. I fished around in http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ copying them one at a time to /lib/firmware until I found one that worked. It still shows up as an Aftech device but both tuners work fine

Fake Name

Thanks for your replies!

Latty Jordan - I'm glad to hear you managed to find away around this! I'm not sure exactly how to copy files to /lib/firmware though... can you or anyone else please help me locate this directory on the Rpi (openelec)?

Fake Name

OK, so I've been playing around with my setup and I can confirm that Tvheadend does not work when it's using the incorrect 'Afatech AF9033 (DVB-T)' driver.
Prof Yaffle - to answer your questions:
Yes I can access the web interface.
When I updated openelec to this version (and subsequent versions) it was still showing the networks, muxes and services that were already setup. However, the card was not enabled. Enabling the card did nothing. It does report 2 cards.
I was able to cue recordings but they would not play back.

I tried re-scanning all my services but none were found.

I'm now having a problem reverting to my previous setup.
Tvheadend is reporting hundreds of 'bogus' channels. It has found all the correct channels, but my XBMC installations (that use the Rpi as a backend for pvr) are littered with hundreds of channels that should not exist and that don't start. The channels are reported as Channel 32327484, Channel 2367837, Channel 898273623 etc... Attempting to play these channels results in the message 'no free adapter'.
These channels are not shown in the Tvh web interface so I don't know how to get rid of them - the web interface is only showing the correct/expected channels.

I have reset the pvr database and EPG databse in XBMC but the 'bogus' channels keep getting scanned back in.

Is there a way of completely resetting tvheadend on my Rpi?

Thanks again for your help!

Fake Name

Can anyone please help me resolve this. I have been stuck on the above mentioned build of XBMC since June.

Every month or so I try out the latest builds but the RPi continues to recognize my card as an Afatech AF9033. I have been able to get the card to work using this firmware (after removing the 'service.multimedia.tvheadend' folder from Openelec and rescanning everything) but the performance is terrible; it's very slow to switch/start channels and it freezes regularily (even after updating to latest Tvheadend).

I have discovered that replacing the firmware, as suggested by Latty Jordan, is not possible because the file system for Openelec is read-only.

Does anyone have any other ideas? I would really appreciate any help or advice.

Thanks in advance

Anonymous

Can you try a clean build of Openelec 4.0.7. Had same problem with the device being recognised as a AF9033. Now says it's an Kworld UB499-2T T09(IT9137)

Not an expert on the PVR stuff but this version seems to like my K-World UB499. Lost the UK BBC channels last week - seem to be back now. Tried earlier and later builds but none worked.

Get builds here http://archive.openelec.tv/

Fake Name

Thanks. I can confirm that the 4.0.7 build also recognises my Kworld card correclty. It does not really fix the problem though because I then get stuck on that build; the later ones load the Alfatech firmware.

Fake Name

Problem solved :) ... kind of...

I just installed the latest git version of Tvheadend on Arch Linux (as Latty Jordan mentioned earlier) and used the Kworld firmware from this link:

https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-usb-it9137-01.fw

The preformance of Tvheadend is greatly improved. Channels switch almost instantly and play-back smoothly. Also, timeshift is finally working as you would expect :D

I think this demonstrates a problem with how the Kworld UB499-2T T09 is handled in the latest versions of the Linux kernel... but, to be fair, I really don't know enough about Linux. I would love for the issue to be fixed upstream, but for the sake of $35, I'm just going to buy another Rpi; I'll use one as the backend (with Tvheadend on Arch Linux) and the other as the front-end (with the latest Openelec and with Tvheadend disabled).

Thanks to all who tried to help me.

adam b

Ha - that's funny. I just did an install with openELEC 5.0.0 on an Rpi B+ and my Kworld UB435-Q is recognized as an LG Electronics LGDT3305. The driver seems to work on all channels except for 1 though. On that channel I get strange stop/start freeze action. I haven't tried any of the record functions yet so maybe I'll find more issues. Also, changing channels seems to be quite sluggish so maybe the drive is the issue for all my observations.

Maury Markowitz

I know I am replying to an old thread, but...

Does anyone know what changed to get the driver to be associated with this device?

I'm trying on an Odriod, and it is identifying it as a Afatech, like the OP. I assume that somewhere between his attempt and adam's, something changed to fix this?