You are not logged in.

#1 2012-06-17 05:57:24

Effrafax
Member
Registered: 2012-02-15
Posts: 13

Problems with Leadtek DVT2000DS since kernel 3.3

Hello All,

I have a PC with this TV tuner card in (AF9013/AF9015 chipsets) which worked perfectly with Kaffeine until the kernel 3.3.1 update (the first of the 3.3 series).  Kaffeine reported device not found, despite all the modules and firmware being correctly installed.  The fix was to downgrade back to 3.2.13 kernel.

After Googling around, I found that the drivers for the chipsets used had been rewritten, so assumed some issue with that.  I tested each 3.3-series kernel released, all failed the same way.  I then discovered that there were known issues with USB-based DVB cards, and there were lots of fixes and updates in the 3.4 kernel, so eagerly awaited that.

3.4.2 was finally released yesterday and I upgraded.  Same thing: "Computer (Kaffeine) says 'No'".

To verify this was an Arch issue, and not a kernel/Kaffeine problem, I downloaded the latest Sabayon DVD image, the only other KDE-based distribution with a 3.4 kernel that I could find.  Booted that up, and installed the Kaffeine package: works perfectly.

So, has anyone else had this problem, or similar problems with DVB/DVT cards?

For reference, here's the relevant details of the system:

uname -a                                                                                                                      3:55
Linux sarum 3.4.2-2-ARCH #1 SMP PREEMPT Mon Jun 11 22:27:17 CEST 2012 x86_64 GNU/Linux


lsmod|grep af                                                                                                                 2:17
af9013                 18135  2
dvb_usb_af9015         27317  4
dvb_usb                17288  1 dvb_usb_af9015
rc_core                13088  4 dvb_usb,dvb_usb_af9015,rc_leadtek_y04g0051
i2c_core               20369  5 i2c_i801,dvb_usb,af9013,nvidia,tda18271
usbcore               147533  6 uhci_hcd,dvb_usb,ehci_hcd,usbhid,dvb_usb_af9015


lsusb                                                                                                                       2:13PM
Bus 003 Device 002: ID 0413:6a04 Leadtek Research, Inc.


From dmesg:

[   11.833353] dvb-usb: found a 'Leadtek WinFast DTV2000DS' in warm state.
[   11.833400] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   11.833753] DVB: registering new adapter (Leadtek WinFast DTV2000DS)
[   11.844478] af9013: firmware version 4.95.0.0
[   11.846479] DVB: registering adapter 0 frontend 0 (Afatech AF9013)...
[   11.896632] snd-ca0106: Model 100a Rev 00000000 Serial 100a1102
[   11.981089] tda18271 0-00c0: creating new instance
[   11.984117] TDA18271HD/C2 detected @ 0-00c0
[   12.034581] microcode: CPU1 sig=0x10676, pf=0x1, revision=0x60c
[   12.034880] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[   12.123424] firewire_core 0000:05:03.0: created device fw0: GUID 001e8c000150d8f3, S400
[   12.196640] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   12.197045] DVB: registering new adapter (Leadtek WinFast DTV2000DS)
[   12.404163] af9013: found a 'Afatech AF9013' in warm state.
[   12.407532] af9013: firmware version 4.95.0.0
[   12.413660] DVB: registering adapter 1 frontend 0 (Afatech AF9013)...
[   12.413737] tda18271 0-00c0: attaching existing instance
[   12.496684] Registered IR keymap rc-leadtek-y04g0051
[   12.496796] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1e.0/0000:05:02.2/usb3/3-1/rc/rc0/input17
[   12.496829] rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1e.0/0000:05:02.2/usb3/3-1/rc/rc0
[   12.496831] dvb-usb: schedule remote query interval to 500 msecs.
[   12.496833] dvb-usb: Leadtek WinFast DTV2000DS successfully initialized and connected.
[   12.504200] usbcore: registered new interface driver dvb_usb_af9015
[

From this you can see that the modules are all correctly loaded and linked, and the tuner card is initialised and works as far as the kernel can tell.

I also tried installing Me-TV, but that also has issues: the channel scan wizard just sits there without doing anything visible, and produces no results.

I can't find any relevant bugs logged in Flyspray, so that's probably the next step, but if anyone has any ideas or other useful input, I'd happily listen!

Cheers,
Effrafax.

Offline

Board footer

Powered by FluxBB