DVB-T-Adapters not registered properly (i.e. AF9015)

[criticalmess]

Binary package hint: udev

After inserting dvb-t adapter with af9015 chip (anttip-modules are configured and installed, firmware is also present), system (following dmesg) recognizes dvb-t-device, registered that adapter and says that it's working.

On my mashine (karmic) it used to make new directory /dev/dvb/adapter0 and work with me-tv instantly;
but on my friends mashine (also karmic) it only creates this right in /dev/: dvb0.demux0, dvb0.dvr0, dvb0.net0, dvb0.frontend0

I found that http://ubuntuforums.org/showthread.php?t=1278275

This actions did not solve the problem. Any idea how to mae it work?

[Scott James Remnant (Canonical) (canonical-scott)]

Please run "apport-collect 478288"

[Jerry (priegog)]

Architecture: amd64
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
MachineType: ASUSTeK Computer Inc. K50IN
NonfreeKernelModules: nvidia
Package: udev 147~-6.1
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=0fbb4b8d-7394-4871-b378-1f30a958a89e ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/22/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 213
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IN
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr213:bd07/22/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: K50IN
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Jerry (priegog)]

I'm (obviously) not the one who submitted the bug, but I did it anyways (I have the same model USB DVB tuner). I ran the command with the card plugged in. Hope this gets rolling, but as far as I understand from what I've read, this could be solved by updating the included firmare version.

[Ralf Luther (ralf-luther)]

Hi,

as for my first post, I'd like to say that I own the same adapter and it works properly with Me-TV and the karmic release version (after upgrading the firmware by the system "Hardware Drivers"). As far as I can see the system did'nt find the firmware for the adapter.
Could it be that the firmware isn't installed or must be renamed?
As far as I can see, your system tries to find the Firmware file for 3 times and gives it up afterwards.

[criticalmess (criticalmess)]

I started this bug. i have no more access on that machine but i am very familar with the manual installation of that af9015 chip. I am very sure that the firmware for the device on my friends computer was in place. But the problem should not be firmware-related because since jaunty and of course for karmic this tv-stick was working for my machine right out-of-the-box on plugin and still does on lucid. Anyway i will have access to that mashine again on wednesday to make his sound working again. I dont run Karmic anymore as for Alpha-testing Lucid. So far i cannot further investigate except of few hours on wednesday, so dont really except me providing further informations... i have no bug, but please read what the bug is targeting at carefully.

[carldjames (carldjames)]

Architecture: i386
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Acer Aspire 5520
NonfreeKernelModules: nvidia
Package: udev 147~-6.1
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic root=UUID=7fa9bdd0-e9c6-4317-8d4c-ea27f96c0082 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
Uname: Linux 2.6.31-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare
dmi.bios.date: 03/06/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.32
dmi.board.name: Fuquene
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV1.32:bd03/06/2008:svnAcer:pnAspire5520:pvrV1.32:rvnAcer:rnFuquene:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5520
dmi.product.version: V1.32
dmi.sys.vendor: Acer

[madbiologist (me-again)]

It looks like kernel 2.6.33 will help - see http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fnext%2Fpatch-v2.6.33-rc8-next-20100222.bz2;z=3043

[criticalmess (criticalmess)]

See i was rather pointing to the rtl chip, your one is not a MSI digivox with a af9015 or tealtek chip...
Since mine AF9015 always worked marvelous i guess someone with a Realtek chip based DVB-T-USB device should respond.

[criticalmess (criticalmess)]

Ooops i mean another one with a AF9015 based DVB-T-USB-Device should respond to close it.
@carldjames: for you device try to start a specific bug and note the Model-Device-Name and the chip it is working with.