DVB-T USB receiver Asus U3100/T/RC/NSW

[Henk-Jan]

After plugging in, the kernel seems to recognize the USB-stick.
It needs the AF9035-driver.

How to make it work in Puppy?


Puppy Linux 5.28
sh-4.1# uname -r
2.6.33.2

dmesg:
usb 1-2: new high speed USB device using ehci_hcd and address 7
input: Afa Technologies Inc. AF9035A USB Device as /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1/input/input13
generic-usb 0003:0B05:1779.0005: input: USB HID v1.01 Keyboard [Afa Technologies Inc. AF9035A USB Device] on usb-0000:00:1d.7-2/input1

sh-4.1# lsusb
Bus 001 Device 007: ID 0b05:1779

[peebee]

Hi

I don't think your dvb-t is being recognised properly - you may need to find the appropriate firmware for the AF9035..... the existing firmware is in /lib/modules/all-firmware/dvb-usb-firmware - suggest google for af9035.fw

Try the firmware link here:
http://linuxtv.org/wiki/index.php/Afatech_AF9035

The loading messages for my AF9005 are below.

When you have the tuner being identified and loaded then suggest you look at
http://www.murga-linux.com/puppy/viewto ... =855566915

for some useful clues........

Basically you need to install
linuxtv-DVB-apps-1.1.1.pet
which will give you the scan command

You then need to find the initial frequency file for your transmitter - it may already be in /usr/share/dvb/dvb-t/

Do a scan to create the channels.conf file for your transmitter

put channels.conf into hidden directory .mplayer

run mplayer and select File -> TV -> Open Digital TV

and you should be watching dvb-t

If scan doesn't work for you - you could try w_scan from
http://wirbel.htpc-forum.de/w_scan/index2.html
which doesn't need the initial frequency file

Good luck

Cheers
peebee

Code: Select all

usb 4-1: new full speed USB device using uhci_hcd and address 2
dvb-usb: found a 'Afatech DVB-T USB1.1 stick' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'af9005.fw'
dvb-usb: found a 'Afatech DVB-T USB1.1 stick' in warm state.
dvb-usb: will use the device's hardware PID filter (table count: 32).
DVB: registering new adapter (Afatech DVB-T USB1.1 stick)
DVB: registering adapter 0 frontend 0 (AF9005 USB DVB-T)...
dvb-usb: Afatech DVB-T USB1.1 stick successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9005

[Henk-Jan]

I've found and copied driver dvb-usb-af9035-01.fw to /lib/firmware
Unfortunately the kernel does not associate the stick with the driver:

usb 1-3: new high speed USB device using ehci_hcd and address 4
input: Afa Technologies Inc. AF9035A USB Device as /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.1/input/input10
generic-usb 0003:0B05:1779.0002: input: USB HID v1.01 Keyboard [Afa Technologies Inc. AF9035A USB Device] on usb-0000:00:1d.7-3/input1

[tempestuous]

I don't think your dvb-t is being recognised properly

Yes, it's being recognised as a keyboard! That's because the usbhid driver incorrectly binds to the ASUS U3100mini device.
This can be fixed ... but the bigger issue is that there's no standard DVB driver in Puppy for that device.

you may need to find the appropriate firmware for the AF9035

I've found and copied driver dvb-usb-af9035-01.fw to /lib/firmware

Don't get caught up about firmware - it's just "helper code" for the appropriate driver ... which in this case is missing.

I have just compiled the relevant dvb-usb-af903x driver for Puppy Lucid 5.1 - 5.2.8. Get it here -
http://www.murga-linux.com/puppy/viewto ... 751#584751

[tempestuous]

Moderators - the device under discussion is a USB TV tuner.
It's not a wifi device, and should not be in the Networking > Wireless section of the Hardware forum.

[Henk-Jan]

Thanks for the .pet! After rebooting, dmesg reports an error.
Can you help?

usb 1-3: new high speed USB device using ehci_hcd and address 4
AF903X: af903x_module_init
DRIVER_RELEASE_VERSION : v9.08.14.1
FW_RELEASE_VERSION : v8_8_63_0
API_RELEASE_VERSION : 200.20090402.0
[Device_init] Error 1
dvb_usb_af903x: probe of 1-3:1.0 failed with error -12
usbcore: registered new interface driver dvb_usb_af903x

[tempestuous]

Well the dvb-usb-af903x driver appears to be far from stable, so success is not guaranteed.

First I suggest you reload the driver -

Code: Select all

rmmod dvb-usb-af903x
modprobe dvb-usb-af903x

Then run dmesg again to see if it loaded without error this time.
Even if the error remains, it appears that the driver still fully loaded, so you have a chance it may work.

Go ahead and run w_scan.
Apparently the dvbscan utility won't work.

[Henk-Jan]

Nothing yet .... let me send you a PM!

dvb_usb_af903x: probe of 1-3:1.0 failed with error -12
usbcore: registered new interface driver dvb_usb_af903x
usb 1-3: USB disconnect, address 4
usb 1-3: new high speed USB device using ehci_hcd and address 5
DRIVER_RELEASE_VERSION : v9.08.14.1
FW_RELEASE_VERSION : v8_8_63_0
API_RELEASE_VERSION : 200.20090402.0
[Device_init] Error 1
dvb_usb_af903x: probe of 1-3:1.0 failed with error -12

sh-4.1# w_scan
sh: w_scan: command not found
sh-4.1#

[Henk-Jan]

W_scan works!
Saying that there is no driver loaded ... :

sh-4.1# w_scan
w_scan version 20111011 (compiled for DVB API 5.1)
guessing country 'NL', use -c <country> to override
using settings for NETHERLANDS
DVB aerial
DVB-T Europe
frontend_type DVB-T, channellist 4
output format vdr-1.6
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
main FATAL: ***** NO USEABLE DVB-T CARD FOUND. *****
Please check wether dvb driver is loaded and
verify that no dvb application (i.e. vdr) is running.

[Henk-Jan]

There is a module loaded:

Code: Select all

sh-4.1# modprobe -l|grep af903x
kernel/drivers/media/dvb/dvb-usb/dvb-usb-af903x.ko

but it ends in error:

Code: Select all

usb 1-3: new high speed USB device using ehci_hcd and address 5
        DRIVER_RELEASE_VERSION : v9.08.14.1
        FW_RELEASE_VERSION     : v8_8_63_0
        API_RELEASE_VERSION    : 200.20090402.0
[Device_init] Error 1
dvb_usb_af903x: probe of 1-3:1.0 failed with error -12

[tempestuous]

OK, the driver is clearly failing.
I see that the driver source code was intended for older kernels than Puppy 5.1/5.2 has, so the best chance of success would be to go back to an earlier kernel -
I have just compiled the driver for Puppy 4.3.x here -
http://www.murga-linux.com/puppy/viewto ... 036#585036
With an older kernel the results were different - I was able to use the vendor-supplied version of the driver ...
but the driver is certainly still less than stable.
If this version doesn't work, you're out of options.