Skip to contentSkip to conversation

probs with af901x on mythbuntu

linux-dvb pjama 3 participants 9 messages May 5, 2008 – May 11, 2008 Media (V4L/DVB)

lore
Share & tools
lore

pjama

author
#0 lore raw

Hi,
I have a DigitalNow TinyTwin DVB-T Receiver which I believe to be a Afatech 9015 (9013?) TV card on a USB stick. It works just fine in Windoze but I'm trying to get it going in MythBuntu 8.04.

I've compiled and installed the bleeding edge af9015-74e494a9496 drivers from http://linuxtv.org/hg/~anttip/af9015 and dvb-usb-af9015.fw ver 4.95.0 from http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/

however I cant get it to find any TV stations with kaffeine or scan. Kaffiene just doesn't find anything, scan gives me:

peter@SunU20:~$ sudo scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-Brisbane
scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-Brisbane
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
main:2247: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 16 Device or resource busy
peter@SunU20:~$

Relevant stuff from dmesg

[   33.795048] input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:02.1/usb1/1-2/1-2:1.1/input/input1
[   33.807958] input,hidraw0: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:00:02.1-2
....
[ 6666.511668] af9015_usb_probe: interface:0
[ 6666.513096] af9015_identify_state: reply:02
[ 6666.513101] dvb-usb: found a 'DigitalNow TinyTwin DVB-T Receiver' in warm state.
[ 6666.513517] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 6666.514236] DVB: registering new adapter (DigitalNow TinyTwin DVB-T Receiver)
[ 6666.514982] af9015_eeprom_dump:
[ 6666.546073] 00: 2a 88 9b 0b 00 00 00 00 d3 13 26 32 00 02 01 02
[ 6666.578049] 10: 03 80 00 fa fa 10 40 ef 01 30 31 30 31 30 39 31
[ 6666.610025] 20: 34 30 36 30 30 30 30 31 ff ff ff ff ff ff ff ff
[ 6666.642003] 30: 00 01 3a 01 00 08 02 00 da 11 00 00 1e ff ff ff
[ 6666.673980] 40: ff ff ff ff ff 08 02 00 da 11 00 00 1e ff ff ff
[ 6666.705956] 50: ff ff ff ff ff 24 00 00 04 03 09 04 10 03 41 00
[ 6666.737931] 60: 66 00 61 00 74 00 65 00 63 00 68 00 10 03 44 00
[ 6666.769901] 70: 56 00 42 00 2d 00 54 00 20 00 32 00 20 03 30 00
[ 6666.801885] 80: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00
[ 6666.833861] 90: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff
[ 6666.865838] a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6666.897814] b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6666.929790] c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6666.961767] d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6666.993743] e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6667.025712] f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6667.027720] af9015_read_config: xtal:2 set adc_clock:28000
[ 6667.031717] af9015_read_config: IF1:4570
[ 6667.035715] af9015_read_config: MT2060 IF1:0
[ 6667.037704] af9015_read_config: tuner id1:30
[ 6667.039708] af9015_read_config: spectral inversion:0
[ 6667.045704] af9013: firmware version:4.73.0
[ 6667.045926] DVB: registering frontend 0 (Afatech AF9013 DVB-T)...
[ 6667.046223] af9015_tuner_attach:
[ 6667.046228] af9015_set_gpio: gpio:1 gpioval:03
[ 6667.087916] mxl500x_attach: Attaching ...
[ 6667.087924] mxl500x_attach: MXL500x tuner succesfully attached
[ 6667.087929] dvb-usb: DigitalNow TinyTwin DVB-T Receiver successfully initialized and connected.
[ 6667.087933] af9015_init:
[ 6667.087936] af9015_init_endpoint: USB speed:3
[ 6667.109656] af9015_download_ir_table:
[ 6667.361511] usbcore: registered new interface driver dvb_usb_af9015
peter@SunU20:~$ sudo lsusb -v
[sudo] password for peter:

Bus 002 Device 002: ID 13d3:3226 IMC Networks
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00

 bDeviceClass            0 (Defined at Interface level)
 bDeviceSubClass         0
 bDeviceProtocol         0
 bMaxPacketSize0        64
 idVendor           0x13d3 IMC Networks
 idProduct          0x3226
 bcdDevice            2.00
 iManufacturer           1 Afatech
 iProduct                2 DVB-T 2
 iSerial                 3 010101010600001
 bNumConfigurations      1
 Configuration Descriptor:
   bLength                 9
   bDescriptorType         2
   wTotalLength           71
   bNumInterfaces          2
   bConfigurationValue     1
   iConfiguration          0
   bmAttributes         0x80
     (Bus Powered)
   MaxPower              500mA
   Interface Descriptor:
     bLength                 9
     bDescriptorType         4
     bInterfaceNumber        0
     bAlternateSetting       0
     bNumEndpoints           4
     bInterfaceClass       255 Vendor Specific Class
     bInterfaceSubClass      0
     bInterfaceProtocol      0
     iInterface              0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x81  EP 1 IN
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x02  EP 2 OUT
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x84  EP 4 IN
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x85  EP 5 IN
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
   Interface Descriptor:
     bLength                 9
     bDescriptorType         4
     bInterfaceNumber        1
     bAlternateSetting       0
     bNumEndpoints           1
     bInterfaceClass         3 Human Interface Device
     bInterfaceSubClass      0 No Subclass
     bInterfaceProtocol      1 Keyboard
     iInterface              0

HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.01
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 65
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 16
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00

 bDeviceClass            0 (Defined at Interface level)
 bDeviceSubClass         0
 bDeviceProtocol         0

bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

Any assistance appreciated.

WARNING: I'm not all that familiar with TV cards/sticks in general please write slowly ;)

Peter

Signature · 9 lines
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
#1 lore raw

Hi :)

have you stopped mythtvbackend?
Command is afaik /etc/init.d/mythtvbackend stop.
I had the same thing with mythbuntu

Quoted 180 lines · pjama

Hi,
I have a DigitalNow TinyTwin DVB-T Receiver which I believe to be a Afatech 9015 (9013?) TV card on a USB stick. It works just fine in Windoze but I'm trying to get it going in MythBuntu 8.04.

I've compiled and installed the bleeding edge af9015-74e494a9496 drivers from http://linuxtv.org/hg/~anttip/af9015 and dvb-usb-af9015.fw ver 4.95.0 from http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/

however I cant get it to find any TV stations with kaffeine or scan. Kaffiene just doesn't find anything, scan gives me:

peter@SunU20:~$ sudo scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-Brisbane
scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-Brisbane
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
main:2247: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 16 Device or resource busy
peter@SunU20:~$

Relevant stuff from dmesg

[   33.795048] input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:02.1/usb1/1-2/1-2:1.1/input/input1
[   33.807958] input,hidraw0: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:00:02.1-2
....
[ 6666.511668] af9015_usb_probe: interface:0
[ 6666.513096] af9015_identify_state: reply:02
[ 6666.513101] dvb-usb: found a 'DigitalNow TinyTwin DVB-T Receiver' in warm state.
[ 6666.513517] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 6666.514236] DVB: registering new adapter (DigitalNow TinyTwin DVB-T Receiver)
[ 6666.514982] af9015_eeprom_dump:
[ 6666.546073] 00: 2a 88 9b 0b 00 00 00 00 d3 13 26 32 00 02 01 02
[ 6666.578049] 10: 03 80 00 fa fa 10 40 ef 01 30 31 30 31 30 39 31
[ 6666.610025] 20: 34 30 36 30 30 30 30 31 ff ff ff ff ff ff ff ff
[ 6666.642003] 30: 00 01 3a 01 00 08 02 00 da 11 00 00 1e ff ff ff
[ 6666.673980] 40: ff ff ff ff ff 08 02 00 da 11 00 00 1e ff ff ff
[ 6666.705956] 50: ff ff ff ff ff 24 00 00 04 03 09 04 10 03 41 00
[ 6666.737931] 60: 66 00 61 00 74 00 65 00 63 00 68 00 10 03 44 00
[ 6666.769901] 70: 56 00 42 00 2d 00 54 00 20 00 32 00 20 03 30 00
[ 6666.801885] 80: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00
[ 6666.833861] 90: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff
[ 6666.865838] a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6666.897814] b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6666.929790] c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6666.961767] d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6666.993743] e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6667.025712] f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 6667.027720] af9015_read_config: xtal:2 set adc_clock:28000
[ 6667.031717] af9015_read_config: IF1:4570
[ 6667.035715] af9015_read_config: MT2060 IF1:0
[ 6667.037704] af9015_read_config: tuner id1:30
[ 6667.039708] af9015_read_config: spectral inversion:0
[ 6667.045704] af9013: firmware version:4.73.0
[ 6667.045926] DVB: registering frontend 0 (Afatech AF9013 DVB-T)...
[ 6667.046223] af9015_tuner_attach:
[ 6667.046228] af9015_set_gpio: gpio:1 gpioval:03
[ 6667.087916] mxl500x_attach: Attaching ...
[ 6667.087924] mxl500x_attach: MXL500x tuner succesfully attached
[ 6667.087929] dvb-usb: DigitalNow TinyTwin DVB-T Receiver successfully initialized and connected.
[ 6667.087933] af9015_init:
[ 6667.087936] af9015_init_endpoint: USB speed:3
[ 6667.109656] af9015_download_ir_table:
[ 6667.361511] usbcore: registered new interface driver dvb_usb_af9015
peter@SunU20:~$ sudo lsusb -v
[sudo] password for peter:

Bus 002 Device 002: ID 13d3:3226 IMC Networks
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00

 bDeviceClass            0 (Defined at Interface level)
 bDeviceSubClass         0
 bDeviceProtocol         0
 bMaxPacketSize0        64
 idVendor           0x13d3 IMC Networks
 idProduct          0x3226
 bcdDevice            2.00
 iManufacturer           1 Afatech
 iProduct                2 DVB-T 2
 iSerial                 3 010101010600001
 bNumConfigurations      1
 Configuration Descriptor:
   bLength                 9
   bDescriptorType         2
   wTotalLength           71
   bNumInterfaces          2
   bConfigurationValue     1
   iConfiguration          0
   bmAttributes         0x80
     (Bus Powered)
   MaxPower              500mA
   Interface Descriptor:
     bLength                 9
     bDescriptorType         4
     bInterfaceNumber        0
     bAlternateSetting       0
     bNumEndpoints           4
     bInterfaceClass       255 Vendor Specific Class
     bInterfaceSubClass      0
     bInterfaceProtocol      0
     iInterface              0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x81  EP 1 IN
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x02  EP 2 OUT
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x84  EP 4 IN
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x85  EP 5 IN
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
   Interface Descriptor:
     bLength                 9
     bDescriptorType         4
     bInterfaceNumber        1
     bAlternateSetting       0
     bNumEndpoints           1
     bInterfaceClass         3 Human Interface Device
     bInterfaceSubClass      0 No Subclass
     bInterfaceProtocol      1 Keyboard
     iInterface              0

HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.01
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 65
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 16
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00

 bDeviceClass            0 (Defined at Interface level)
 bDeviceSubClass         0
 bDeviceProtocol         0

bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

Quoted 7 lines

Any assistance appreciated.

WARNING: I'm not all that familiar with TV cards/sticks in general please write slowly ;)

Peter

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

author
#2 lore raw
Quoted 6 lines · Bastiaan Wentink

Hi :)

have you stopped mythtvbackend?
Command is afaik /etc/init.d/mythtvbackend stop.
I had the same thing with mythbuntu

Hi Bastiann,
Thanks for the reply. You are exactly right. Mythbuntu has locked the cardfor it's own selfish use. "sudo /etc/init.d/mythtv-backend stop" will kill it.

OK next problem. I now get:

peter@SunU20:~$ sudo scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-Brisbane
scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-Brisbane
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 226500000 1 3 9 3 1 1 0
initial transponder 177500000 1 2 9 3 1 2 0
initial transponder 191625000 1 3 9 3 1 1 0
initial transponder 219500000 1 3 9 3 1 1 0
initial transponder 585625000 1 2 9 3 1 2 0
Quoted 1 line
Quoted 1 line
Quoted 1 line

tune to: 226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE

WARNING: >>> tuning failed!!!

Quoted 1 line
Quoted 1 line
Quoted 1 line

tune to: 226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning failed)

< repeated several times with a different channel but similar failed message >

WARNING: >>> tuning failed!!!

Quoted 1 line
Quoted 1 line
Quoted 1 line

tune to: 585625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed)

WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.
peter@SunU20:~$

Now (while donning my flame proof suit), I must confess that I hadn't thoroughly gone through the mailing list (google failed me) but since posting I've discovered a few things....

1) in dmesg where it says "af9013: firmware version:4.73.0" Does this mean it found version 4.73.0 on the device or in the /lib/firmware/kernel<blah>/dvb_usb_af9015 file? I believe I installed version 4.95.0 (but being a binary file it's hard to confirm). Should they match, Can I upgrade the device or should I downgrade the dvb_usb_af9015 file?

2) A post from Antti back in the beginning of April (http://www.linuxtv.org/pipermail/linux-dvb/2008-April/025267.html) says the driver works but tuning fails because of the MXL5005 tuner. Bummer! Antti, did you get the usb sniff that you were after? If not, can you recommend an application that can dump a suitable file?

Cheers
peter

Signature · 9 lines
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
#3 lore raw
Quoted 3 lines · pjama

Now (while donning my flame proof suit), I must confess that I hadn't thoroughly gone through the mailing list (google failed me) but since posting I've discovered a few things....

1) in dmesg where it says "af9013: firmware version:4.73.0" Does this mean it found version 4.73.0 on the device or in the /lib/firmware/kernel<blah>/dvb_usb_af9015 file? I believe I installed version 4.95.0 (but being a binary file it's hard to confirm). Should they match, Can I upgrade the device or should I downgrade the dvb_usb_af9015 file?

yes (you have old one), install the new one. Probably it does not matter but it is still better use newest available.

Quoted 1 line

2) A post from Antti back in the beginning of April (http://www.linuxtv.org/pipermail/linux-dvb/2008-April/025267.html) says the driver works but tuning fails because of the MXL5005 tuner. Bummer!

It (now) should work, even both tuners. You should use different devel-tree:
http://linuxtv.org/hg/~anttip/af9015-mxl500x-copy-fw/

Using both tuners same time got it hangs, due to broken mutex lock for i2c-bus. I have been a little busy now to fix this, but probably in this week I got it fixed.

Quoted 1 line

Antti, did you get the usb sniff that you were after? If not, can you recommend an application that can dump a suitable file?

Thanx for help but I have got needed logs already.

Quoted 4 lines

Cheers
peter

Antti

Signature · 6 lines
http://palosaari.fi/

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
author
#4 lore raw

Hi Antti,
You're a legend!

Quoted 12 lines · Antti Palosaari
Quoted 10 lines · pjama

Now (while donning my flame proof suit), I must confess that I hadn't thoroughly gone through the mailing list (google failed me) but since posting I've discovered a few things....

1) in dmesg where it says "af9013: firmware version:4.73.0" Does this mean it found version 4.73.0 on the device or in the /lib/firmware/kernel<blah>/dvb_usb_af9015 file? I believe I installed version 4.95.0 (but being a binary file it's hard to confirm). Should they match, Can I upgrade the device or should I downgrade the dvb_usb_af9015 file?

Quoted 2 lines

yes (you have old one), install the new one. Probably it does not matter but it is still better use newest available.

Do you mean in /lib/firmware/kernel.... ? Do you have a copy of the latest firmware. I think my source may be suspect.

Quoted 9 lines
Quoted 5 lines

2) A post from Antti back in the beginning of April
(http://www.linuxtv.org/pipermail/linux-dvb/2008-April/025267.html)
says the driver works but tuning fails because of the MXL5005 tuner. Bummer!

It (now) should work, even both tuners. You should use different devel-tree:
http://linuxtv.org/hg/~anttip/af9015-mxl500x-copy-fw/

Yes you are right. A recompile with these drivers has scan and kaffeine finding channels now.
A quick test of kaffein confirms it works. The only problem I've seen is that one HDTV channel has no audio but I'm not sure this is related to the driver.

Quoted 4 lines

Using both tuners same time got it hangs, due to broken mutex lock for i2c-bus. I have been a little busy now to fix this, but probably in this week I got it fixed.

I can now watch TV while I wait ;)

Quoted 5 lines
Quoted 3 lines

Antti, did you get the usb sniff that you were after? If not, can you recommend an application that can dump a suitable file?

Thanx for help but I have got needed logs already.

Cool

Quoted 7 lines
Quoted 5 lines

Cheers
peter

Antti

Signature · 9 lines
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
#5 lore raw
Quoted 1 line · pjama

Do you mean in /lib/firmware/kernel.... ? Do you have a copy of the latest firmware. I think my source may be suspect.

/lib/firmware/
/lib/firmware/kernel<version>/

I think both are OK, but other is loaded bigger priority by kernel. I think directory with kernel version has looked first. You have 4.73.0 in other directory and other has 4.95.0 ?

Different firmware files can be found from:
http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/

Quoted 5 lines
Quoted 3 lines

Using both tuners same time got it hangs, due to broken mutex lock for i2c-bus. I have been a little busy now to fix this, but probably in this week I got it fixed.

I can now watch TV while I wait ;)

:)

regards
Antti

Signature · 6 lines
http://palosaari.fi/

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
author
#6 lore raw

Hi Antti,

Quoted 7 lines · Antti Palosaari
Quoted 2 lines · pjama

Do you mean in /lib/firmware/kernel.... ? Do you have a copy of the latest firmware. I think my source may be suspect.

/lib/firmware/
/lib/firmware/kernel<version>/

Quoted 7 lines

I think both are OK, but other is loaded bigger priority by kernel. I think directory with kernel version has looked first. You have 4.73.0 in other directory and other has 4.95.0 ?

Different firmware files can be found from:
http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/

OK I have no firmware in /lib/firmware, it is all in the kernel directory. I have copied the file from the above URL which is the one I've been using and I still get "af9013: firmware version:4.73.0" in dmesg. Full 9015 relevant dmesg below.

I'm not sure it's a problem at this point as I've at least got TV but you may be interested from a developer point of view as there are a few errors in the dmesg.

On a related note: What are the chances of getting the remote that came with the usb stick working? It's this one:
http://www.digitalnow.com.au/images/ProRemote.jpg

Thanks for all your efforts

Peter

dmesg output

[   46.545481] af9015_usb_probe: interface:0
[   46.546807] af9015_identify_state: reply:02
[   46.546812] dvb-usb: found a 'DigitalNow TinyTwin DVB-T Receiver' in warm state.
[   46.546915] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   46.548122] DVB: registering new adapter (DigitalNow TinyTwin DVB-T Receiver)
[   46.548513] af9015_eeprom_dump:
[   46.578726] 00: 2a 88 9b 0b 00 00 00 00 d3 13 26 32 00 02 01 02
[   46.610703] 10: 03 80 00 fa fa 10 40 ef 01 30 31 30 31 30 39 31
[   46.642684] 20: 34 30 36 30 30 30 30 31 ff ff ff ff ff ff ff ff
[   46.674656] 30: 00 01 3a 01 00 08 02 00 da 11 00 00 1e ff ff ff
[   46.707638] 40: ff ff ff ff ff 08 02 00 da 11 00 00 1e ff ff ff
[   46.739615] 50: ff ff ff ff ff 24 00 00 04 03 09 04 10 03 41 00
[   46.771592] 60: 66 00 61 00 74 00 65 00 63 00 68 00 10 03 44 00
[   46.803567] 70: 56 00 42 00 2d 00 54 00 20 00 32 00 20 03 30 00
[   46.835551] 80: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00
[   46.867527] 90: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff
[   46.899496] a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   46.931475] b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   46.963448] c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   46.995434] d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   47.027404] e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   47.059380] f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   47.061375] af9015_read_config: TS mode:1
[   47.063379] af9015_read_config: xtal:2 set adc_clock:28000
[   47.067374] af9015_read_config: IF1:4570
[   47.071367] af9015_read_config: MT2060 IF1:0
[   47.073385] af9015_read_config: tuner id1:30
[   47.075368] af9015_read_config: spectral inversion:0
[   47.146320] af9013: firmware version:4.73.0
[   47.166303] DVB: registering frontend 0 (Afatech AF9013 DVB-T)...
[   47.166359] af9015_tuner_attach:
[   47.215903] mxl500x_attach: Attaching ...
[   47.215909] mxl500x_attach: MXL500x tuner succesfully attached
[   47.215914] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   47.216645] DVB: registering new adapter (DigitalNow TinyTwin DVB-T Receiver)
[   47.217008] af9015_copy_firmware:
[   47.378141] af9015: af9015_rw_udev: command failed: 1
[   47.378149] af9015: af9015_copy_firmware: firmware copy cmd failed, err:-1
[   47.378153] af9015_copy_firmware: firmware copy done
[   47.482081] af9015: af9015_rw_udev: command failed: 1
[   47.482089] af9015_copy_firmware: firmware boot cmd status:-1
[   47.585989] af9015: af9015_rw_udev: command failed: 2
[   47.585998] af9015_copy_firmware: firmware status cmd status:-1 fw status:ff
[   47.587994] af9015: af9015_rw_udev: command failed: 1
[   47.588002] af9015_copy_firmware: firmware boot cmd status:-1
[   47.689916] af9015: af9015_rw_udev: command failed: 2
[   47.689924] af9015_copy_firmware: firmware status cmd status:-1 fw status:ff
[   47.691910] af9015: af9015_rw_udev: command failed: 1
[   47.691916] af9015_copy_firmware: firmware boot cmd status:-1
[   47.793831] af9015: af9015_rw_udev: command failed: 2
[   47.793840] af9015_copy_firmware: firmware status cmd status:-1 fw status:ff
[   47.795830] af9015: af9015_rw_udev: command failed: 1
[   47.795835] af9015_copy_firmware: firmware boot cmd status:-1
[   47.897756] af9015: af9015_rw_udev: command failed: 2
[   47.897764] af9015_copy_firmware: firmware status cmd status:-1 fw status:ff
[   47.899756] af9015: af9015_rw_udev: command failed: 1
[   47.899761] af9015_copy_firmware: firmware boot cmd status:-1
[   48.001677] af9015: af9015_rw_udev: command failed: 2
[   48.001685] af9015_copy_firmware: firmware status cmd status:-1 fw status:ff
[   48.003672] af9015: af9015_rw_udev: command failed: 1
[   48.003676] af9015_copy_firmware: firmware boot cmd status:-1
[   48.105610] af9015: af9015_rw_udev: command failed: 2
[   48.105618] af9015_copy_firmware: firmware status cmd status:-1 fw status:ff
[   48.107595] af9015: af9015_rw_udev: command failed: 1
[   48.107599] af9015_copy_firmware: firmware boot cmd status:-1
[   48.209522] af9015: af9015_rw_udev: command failed: 2
[   48.209529] af9015_copy_firmware: firmware status cmd status:-1 fw status:ff
[   48.211518] af9015: af9015_rw_udev: command failed: 1
[   48.211522] af9015_copy_firmware: firmware boot cmd status:-1
[   48.313445] af9015: af9015_rw_udev: command failed: 2
[   48.313452] af9015_copy_firmware: firmware status cmd status:-1 fw status:ff
[   48.315441] af9015: af9015_rw_udev: command failed: 1
[   48.315444] af9015_copy_firmware: firmware boot cmd status:-1
[   48.417366] af9015: af9015_rw_udev: command failed: 2
[   48.417371] af9015_copy_firmware: firmware status cmd status:-1 fw status:ff
[   48.419367] af9015: af9015_rw_udev: command failed: 1
[   48.419371] af9015_copy_firmware: firmware boot cmd status:-1
[   48.521288] af9015: af9015_rw_udev: command failed: 2
[   48.521293] af9015_copy_firmware: firmware status cmd status:-1 fw status:ff
[   48.521298] af9015: af9015_copy_firmware: firmware did not run
[   48.521302] af9015: af9015_af9013_frontend_attach: firmware copy to 2nd frontend failed, will disable it
[   48.521309] dvb-usb: no frontend was attached by 'DigitalNow TinyTwin DVB-T Receiver'
[   48.521315] dvb-usb: DigitalNow TinyTwin DVB-T Receiver successfully initialized and connected.
[   48.521320] af9015_init:
[   48.521322] af9015_init_endpoint: USB speed:3
[   48.565257] af9015_download_ir_table:
[   48.817098] usbcore: registered new interface driver dvb_usb_af9015
Signature · 9 lines
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
#7 lore raw
Quoted 13 lines · pjama

Hi Antti,

Quoted 10 lines · Antti Palosaari
Quoted 2 lines · pjama

Do you mean in /lib/firmware/kernel.... ? Do you have a copy of the latest firmware. I think my source may be suspect.

/lib/firmware/
/lib/firmware/kernel<version>/

I think both are OK, but other is loaded bigger priority by kernel. I think directory with kernel version has looked first. You have 4.73.0 in other directory and other has 4.95.0 ?

Quoted 5 lines
Quoted 3 lines

Different firmware files can be found from:
http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/

OK I have no firmware in /lib/firmware, it is all in the kernel directory. I have copied the file from the above URL which is the one I've been using and I still get "af9013: firmware version:4.73.0" in dmesg. Full 9015 relevant dmesg below.

Is that possible that you are looking firmware file from wrong directory? I mean that you have for example /lib/firmware/kernel-2.6.1/ and /lib/firmware/kernel-2.6.2/ other having 4.73 and the other 4.95? Remove all af9015 firmwares from kernel-x.x.x directories and leave 4.95.0 to /lib/firmware/. Then take unplug stick and boot machine and plug stick again.

I see from dmesg log that firmware copy to 2nd frontend fails. This is due to fact that currently driver has hard coded checksum for 4.95.0.

Quoted 4 lines

I'm not sure it's a problem at this point as I've at least got TV but you may be interested from a developer point of view as there are a few errors in the dmesg.

On a related note: What are the chances of getting the remote that came with the usb stick working? It's this one:
http://www.digitalnow.com.au/images/ProRemote.jpg

It should be polled. There is code for than in the driver already, but it is disabled currently.

Quoted 4 lines

Thanks for all your efforts

Peter

Antti

Signature · 6 lines
http://palosaari.fi/

_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
author
#8 lore raw

Antti Palosaari wrote:
<snip>

Quoted 13 lines
Quoted 5 lines

OK I have no firmware in /lib/firmware, it is all in the kernel directory. I have copied the file from the above URL which is the one I've been using and I still get "af9013: firmware version:4.73.0" in dmesg. Full 9015 relevant dmesg below.

Is that possible that you are looking firmware file from wrong directory? I mean that you have for example /lib/firmware/kernel-2.6.1/ and /lib/firmware/kernel-2.6.2/ other having 4.73 and the other 4.95? Remove all af9015 firmwares from kernel-x.x.x directories and leave 4.95.0 to /lib/firmware/. Then take unplug stick and boot machine and plug stick again.

Quoted 2 lines

I see from dmesg log that firmware copy to 2nd frontend fails. This is due to fact that currently driver has hard coded checksum for 4.95.0.

I double checked the firmware and there was only one copy in /lib/firmware/kernel-blah
It matched the 4.95.0 version. I did as mentioned earlier to boot without USB card plugged in, then plugged in device. It now looks better:

[   55.650921] usb 2-2: new high speed USB device using ehci_hcd and address 4
[   55.703555] usb 2-2: configuration #1 chosen from 1 choice
[   55.706215] af9015_usb_probe: interface:0
[   55.706814] af9015_identify_state: reply:01
[   55.706816] dvb-usb: found a 'DigitalNow TinyTwin DVB-T Receiver' in cold state, will try to load a firmware
[   55.719697] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
[   55.719700] af9015_download_firmware:
[   55.752878] af9015_usb_probe: interface:1
[   55.752920] usb 2-2: USB disconnect, address 4
[   55.755152] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
[   55.755185] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
[   55.846024] usb 2-2: new high speed USB device using ehci_hcd and address 5
[   55.898765] usb 2-2: configuration #1 chosen from 1 choice
[   55.899005] af9015_usb_probe: interface:0
[   55.902273] af9015_identify_state: reply:02
[   55.902276] dvb-usb: found a 'DigitalNow TinyTwin DVB-T Receiver' in warm state.
[   55.902566] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   55.903174] DVB: registering new adapter (DigitalNow TinyTwin DVB-T Receiver)
[   55.903288] af9015_eeprom_dump:
[   55.915696] 00: 2a 88 9b 0b 00 00 00 00 d3 13 26 32 00 02 01 02
[   55.932201] 10: 03 80 00 fa fa 10 40 ef 01 30 31 30 31 30 39 31
[   55.949854] 20: 34 30 36 30 30 30 30 31 ff ff ff ff ff ff ff ff
[   55.963675] 30: 00 01 3a 01 00 08 02 00 da 11 00 00 1e ff ff ff
[   55.978323] 40: ff ff ff ff ff 08 02 00 da 11 00 00 1e ff ff ff
[   55.997833] 50: ff ff ff ff ff 24 00 00 04 03 09 04 10 03 41 00
[   56.014259] 60: 66 00 61 00 74 00 65 00 63 00 68 00 10 03 44 00
[   56.034290] 70: 56 00 42 00 2d 00 54 00 20 00 32 00 20 03 30 00
[   56.050029] 80: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00
[   56.071905] 90: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff
[   56.084186] a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   56.096469] b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   56.108748] c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   56.121032] d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   56.133313] e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   56.148280] f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[   56.149075] af9015_read_config: TS mode:1
[   56.149816] af9015_read_config: xtal:2 set adc_clock:28000
[   56.151353] af9015_read_config: IF1:4570
[   56.152885] af9015_read_config: MT2060 IF1:0
[   56.153653] af9015_read_config: tuner id1:30
[   56.154420] af9015_read_config: spectral inversion:0
[   56.208057] af9013: firmware version:4.95.0
[   56.219005] DVB: registering frontend 0 (Afatech AF9013 DVB-T)...
[   56.219030] af9015_tuner_attach:
[   56.282874] mxl500x_attach: Attaching ...
[   56.282877] mxl500x_attach: MXL500x tuner succesfully attached
[   56.282879] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   56.283100] DVB: registering new adapter (DigitalNow TinyTwin DVB-T Receiver)
[   56.283216] af9015_copy_firmware:
[   56.476723] af9015_copy_firmware: firmware copy done
[   56.517404] af9015_copy_firmware: firmware boot cmd status:0
[   56.557320] af9015_copy_firmware: firmware status cmd status:0 fw status:0c
[   56.559620] af9013: firmware version:4.95.0
[   56.567300] DVB: registering frontend 1 (Afatech AF9013 DVB-T)...
[   56.567322] af9015_tuner_attach:
[   56.567352] mxl500x_attach: Attaching ...
[   56.567353] mxl500x_attach: MXL500x tuner succesfully attached
[   56.567356] dvb-usb: DigitalNow TinyTwin DVB-T Receiver successfully initialized and connected.
[   56.567358] af9015_init:
[   56.567359] af9015_init_endpoint: USB speed:3
[   56.591860] af9015_download_ir_table:
[   56.690500] input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:02.1/usb2/2-2/2-2:1.1/input/input6
[   56.702667] input,hidraw2: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:00:02.1-2
[   59.987029] eth0: no IPv6 routers present
Quoted 11 lines
Quoted 8 lines

I'm not sure it's a problem at this point as I've at least got TV but you may be interested from a developer point of view as there are a few errors in the dmesg.

On a related note: What are the chances of getting the remote that came with the usb stick working? It's this one:
http://www.digitalnow.com.au/images/ProRemote.jpg

It should be polled. There is code for than in the driver already, but it is disabled currently.

Cool. So I guess it has at least been looked at then.

Cheers
Peter

Signature · 9 lines
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb