Afatech AF9015 with TDA18218HN can't be tunned

Bug #1050521 reported by Antonio Vázquez Blanco
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I've recently bought an Afatech chip based DVB-T usb device.
I've installed dvb-apps and linux-firmware-nonfree for getting it running.

When I try to scan for channels with the following command:
scan /usr/share/dvb/dvb-t/es-Madrid
I get:
scanning /usr/share/dvb/dvb-t/es-Madrid
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 618000000 0 2 9 3 1 3 0
initial transponder 706000000 0 2 9 3 1 3 0
initial transponder 770000000 0 2 9 3 1 3 0
initial transponder 810000000 0 2 9 3 1 3 0
initial transponder 834000000 0 2 9 3 1 3 0
initial transponder 842000000 0 2 9 3 1 3 0
initial transponder 850000000 0 2 9 3 1 3 0
initial transponder 858000000 0 2 9 3 1 3 0
>>> tune to: 618000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to: 618000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 706000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to: 706000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 770000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to: 770000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 810000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to: 810000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 834000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to: 834000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 842000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to: 842000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 850000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to: 850000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 858000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to: 858000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE (tuning failed)
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.

dmesg has some important info:
[ 2614.349901] usb 1-1: new high-speed USB device number 2 using ehci_hcd
[ 2614.748131] Afatech DVB-T 2: Fixing fullspeed to highspeed interval: 10 -> 7
[ 2614.753416] input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:0b.0/usb1/1-1/1-1:1.1/input/input6
[ 2614.753416] generic-usb 0003:15A4:9016.0002: input,hidraw1: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:00:0b.0-1/input1
[ 2614.988492] IR NEC protocol handler initialized
[ 2615.028915] IR RC5(x) protocol handler initialized
[ 2615.053876] IR RC6 protocol handler initialized
[ 2615.074266] IR JVC protocol handler initialized
[ 2615.128150] IR Sony protocol handler initialized
[ 2615.173434] IR MCE Keyboard/mouse protocol handler initialized
[ 2615.232888] lirc_dev: IR Remote Control driver registered, major 250
[ 2615.236633] IR LIRC bridge handler initialized
[ 2616.772019] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware
[ 2616.814439] dvb-usb: did not find the firmware file. (dvb-usb-af9015.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2)
[ 2616.814475] dvb_usb_af9015: probe of 1-1:1.0 failed with error -2
[ 2616.814508] usbcore: registered new interface driver dvb_usb_af9015
[ 2859.426119] usbcore: deregistering interface driver dvb_usb_af9015
[ 2861.490174] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware
[ 2861.514248] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
[ 2862.692331] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state.
[ 2862.692424] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 2862.694453] DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick)
[ 2862.816614] af9013: firmware version:4.95.0.0
[ 2862.925870] DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)...
[ 2863.021597] tda18218: NXP TDA18218HN successfully identified.
[ 2863.039456] Registered IR keymap rc-empty
[ 2863.041201] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0b.0/usb1/1-1/rc/rc0/input7
[ 2863.044057] rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0b.0/usb1/1-1/rc/rc0
[ 2863.044057] dvb-usb: schedule remote query interval to 500 msecs.
[ 2863.044057] dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected.
[ 2863.232318] usbcore: registered new interface driver dvb_usb_af9015

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-23-generic-pae 3.2.0-23.36
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 82801AA-ICH]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu5
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: antonio 1510 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with STAC9700,83,84 at irq 5'
   Mixer name : 'SigmaTel STAC9700,83,84'
   Components : 'AC97a:83847600'
   Controls : 34
   Simple ctrls : 24
Date: Thu Sep 13 19:07:55 2012
HibernationDevice: RESUME=UUID=18dea121-fa7e-4e3d-8cb5-89b3902d6225
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 002: ID 15a4:9016 Afatech Technologies, Inc. AF9015 DVB-T USB2.0 stick
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic-pae root=UUID=a60c583a-40f0-4033-baeb-e37b865d19bf ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic-pae N/A
 linux-backports-modules-3.2.0-23-generic-pae N/A
 linux-firmware 1.79
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Revision history for this message
Antonio Vázquez Blanco (antoniovazquezblanco) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc5-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key needs-upstream-testing
Revision history for this message
Antonio Vázquez Blanco (antoniovazquezblanco) wrote :

Updated kernel to upstream, plugged the device in and found that no dev was created.

Dmesg:

[ 96.756142] usb 1-1: new high-speed USB device number 3 using ehci_hcd
[ 97.055049] usb 1-1: New USB device found, idVendor=15a4, idProduct=9016
[ 97.055054] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 97.055057] usb 1-1: Product: DVB-T 2
[ 97.055060] usb 1-1: Manufacturer: Afatech
[ 97.055063] usb 1-1: SerialNumber: 010101010600001
[ 97.194221] Afatech DVB-T 2: Fixing fullspeed to highspeed interval: 10 -> 7
[ 97.197955] input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:0b.0/usb1/1-1/1-1:1.1/input/input6
[ 97.198259] hid-generic 0003:15A4:9016.0003: input,hidraw1: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:00:0b.0-1/input1
[ 138.820127] init: failsafe main process (641) killed by TERM signal
[ 139.043911] type=1400 audit(1347570131.004:28): apparmor="STATUS" operation="profile_replace" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=1991 comm="apparmor_parser"
[ 139.061701] type=1400 audit(1347570131.024:29): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=1992 comm="apparmor_parser"
[ 139.062509] type=1400 audit(1347570131.024:30): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1992 comm="apparmor_parser"
[ 139.062842] type=1400 audit(1347570131.024:31): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=1992 comm="apparmor_parser"
[ 139.099258] type=1400 audit(1347570131.060:32): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince" pid=1993 comm="apparmor_parser"
[ 139.105330] type=1400 audit(1347570131.068:33): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince//launchpad_integration" pid=1993 comm="apparmor_parser"
[ 139.106608] type=1400 audit(1347570131.068:34): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince//sanitized_helper" pid=1993 comm="apparmor_parser"
[ 139.107904] type=1400 audit(1347570131.068:35): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince-previewer" pid=1993 comm="apparmor_parser"
[ 139.112594] type=1400 audit(1347570131.076:36): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince-previewer//launchpad_integration" pid=1993 comm="apparmor_parser"
[ 140.208463] init: plymouth-stop pre-start process (2138) terminated with status 1

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Incomplete → Triaged
tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Revision history for this message
penalvch (penalvch) wrote :

Antonio Vázquez Blanco, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc6

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Antonio Vázquez Blanco (antoniovazquezblanco) wrote :

I'm sorry this has been stuck for so long.

While ago I moved to Archlinux. I can confirm this device actualy works in my computer with kernel 3.12.7.

Hope it is fixed for other people as well.

Thanks for being so patient and for your time.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.