* [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
@ 2008-07-18 17:55 tom
2008-07-18 18:21 ` Antti Palosaari
0 siblings, 1 reply; 9+ messages in thread
From: tom @ 2008-07-18 17:55 UTC (permalink / raw)
To: linux-dvb
Hello,
since a few days I'm trying hard make this stick running. One basic problem is that I'm not able to find out which chipset is in this
stick.
I have tried af9015 driver and firmware, but it doesn't work.
Does anybody have the same problem or even solved it?
dmesg | grep usb:
[19614.849918] usb 3-3: USB disconnect, address 5
[19618.108978] usb 3-3: new high speed USB device using ehci_hcd and address 6
[19618.244872] usb 3-3: configuration #1 chosen from 1 choice
lsusb -v :
Bus 003 Device 005: ID 1462:8801 Micro Star International
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1462 Micro Star International
idProduct 0x8801
bcdDevice 2.00
iManufacturer 1 Afatech
iProduct 2 DVB-T 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 46
bNumInterfaces 1
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
Thomas
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
2008-07-18 17:55 [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04 tom
@ 2008-07-18 18:21 ` Antti Palosaari
2008-07-18 20:49 ` Antti Palosaari
0 siblings, 1 reply; 9+ messages in thread
From: Antti Palosaari @ 2008-07-18 18:21 UTC (permalink / raw)
To: tom; +Cc: linux-dvb
tom wrote:
> Hello,
> since a few days I'm trying hard make this stick running. One basic problem is that I'm not able to find out which chipset is in this
> stick.
> I have tried af9015 driver and firmware, but it doesn't work.
It looks like AF9015 dual design. I think problem you have is missing
device USB-IDs. I will add those in a next few hours and you can test
then again.
> Does anybody have the same problem or even solved it?
:)
regards
Antti Palosaari
>
> dmesg | grep usb:
>
> [19614.849918] usb 3-3: USB disconnect, address 5
> [19618.108978] usb 3-3: new high speed USB device using ehci_hcd and address 6
> [19618.244872] usb 3-3: configuration #1 chosen from 1 choice
>
>
> lsusb -v :
>
> Bus 003 Device 005: ID 1462:8801 Micro Star International
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> idVendor 0x1462 Micro Star International
> idProduct 0x8801
> bcdDevice 2.00
> iManufacturer 1 Afatech
> iProduct 2 DVB-T 2
> iSerial 0
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 46
> bNumInterfaces 1
> 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
>
> Thomas
>
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
--
http://palosaari.fi
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
2008-07-18 18:21 ` Antti Palosaari
@ 2008-07-18 20:49 ` Antti Palosaari
2008-07-19 8:58 ` tom
0 siblings, 1 reply; 9+ messages in thread
From: Antti Palosaari @ 2008-07-18 20:49 UTC (permalink / raw)
To: tom; +Cc: linux-dvb
Antti Palosaari wrote:
> tom wrote:
>> Hello,
>> since a few days I'm trying hard make this stick running. One basic problem is that I'm not able to find out which chipset is in this
>> stick.
>> I have tried af9015 driver and firmware, but it doesn't work.
>
> It looks like AF9015 dual design. I think problem you have is missing
> device USB-IDs. I will add those in a next few hours and you can test
> then again.
Now it is ready for the test.
http://linuxtv.org/hg/~anttip/af9015/
Antti
--
http://palosaari.fi/
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
2008-07-18 20:49 ` Antti Palosaari
@ 2008-07-19 8:58 ` tom
2008-07-19 12:13 ` tom
0 siblings, 1 reply; 9+ messages in thread
From: tom @ 2008-07-19 8:58 UTC (permalink / raw)
To: Antti Palosaari; +Cc: linux-dvb
Hi Antti,
I have installed the driver. After reboot dmesg gives the following.
dmesg | grep dvb:
[ 1387.281913] dvb-usb: MSI DIGIVOX Duo successfully deinitialized and
disconnected.
[ 1397.029836] dvb-usb: found a 'MSI DIGIVOX Duo' in cold state, will
try to load a firmware
[ 1397.062503] dvb-usb: downloading firmware from file
'dvb-usb-af9015.fw'
[ 760.590855] dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
[ 1397.796493] dvb-usb: found a 'MSI DIGIVOX Duo' in warm state.
[ 1397.796602] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[ 1398.548360] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[ 1399.517422] dvb-usb: MSI DIGIVOX Duo successfully initialized and
connected.
[ 1510.506232] dvb-usb: could not handle pid_parser
[ 1532.502328] dvb-usb: could not handle pid_parser
[ 1555.125203] dvb-usb: could not handle pid_parser
[ 1577.464244] dvb-usb: could not handle pid_parser
[ 1600.496149] dvb-usb: could not handle pid_parser
[ 1622.496391] dvb-usb: could not handle pid_parser
[ 2324.836824] dvb-usb: could not handle pid_parser
[ 2347.650720] dvb-usb: could not handle pid_parser
[ 2371.133792] dvb-usb: could not handle pid_parser
[ 2393.752616] dvb-usb: could not handle pid_parser
[ 2415.895728] dvb-usb: could not handle pid_parser
[ 2437.891824] dvb-usb: could not handle pid_parser
A channel scan with Kaffeine was not successfull. Here the results:
kbuildsycoca running...
Reusing existing ksycoca
/dev/dvb/adapter0/frontend0 : opened ( Afatech AF9013 DVB-T )
/dev/dvb/adapter1/frontend0 : opened ( Afatech AF9013 DVB-T )
0 EPG plugins loaded for device 0:0.
0 EPG plugins loaded for device 1:0.
Loaded epg data : 0 events (0 msecs)
kio (KMimeType): WARNING: KServiceType::offers : servicetype
ThumbCreator not found
kio (KMimeType): WARNING: KServiceType::offers : servicetype
ThumbCreator not found
tom@super-klappi:~$ DvbCam::probe(): /dev/dvb/adapter0/ca0: : No such
file or directory
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 402000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 1/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 490000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 12/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 514000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 15/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 538000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 18/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 562000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 21/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 586000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 24/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 610000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 27/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 698000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 38/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 722000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 41/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 746000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 44/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 770000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 47/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 858000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
.FE_READ_STATUS: Remote I/O error
Transponders: 58/63
Invalid section length or timeout: pid=17
Frontend closed
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 882000000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
ERROR tuning
: Invalid argument
Frontend closed
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Transponders: 63
dvbsi: The end :)
Channels found: 0
Thomas
Am Freitag, den 18.07.2008, 23:49 +0300 schrieb Antti Palosaari:
> Antti Palosaari wrote:
> > tom wrote:
> >> Hello,
> >> since a few days I'm trying hard make this stick running. One basic problem is that I'm not able to find out which chipset is in this
> >> stick.
> >> I have tried af9015 driver and firmware, but it doesn't work.
> >
> > It looks like AF9015 dual design. I think problem you have is missing
> > device USB-IDs. I will add those in a next few hours and you can test
> > then again.
>
> Now it is ready for the test.
> http://linuxtv.org/hg/~anttip/af9015/
>
> Antti
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
2008-07-19 8:58 ` tom
@ 2008-07-19 12:13 ` tom
2008-07-20 12:56 ` Antti Palosaari
0 siblings, 1 reply; 9+ messages in thread
From: tom @ 2008-07-19 12:13 UTC (permalink / raw)
To: Antti Palosaari; +Cc: linux-dvb
results of lsmod | grep dvb:
dvb_usb_af9015 24332 0
dvb_usb 22924 1 dvb_usb_af9015
dvb_core 80636 1 dvb_usb
i2c_core 24832 4 mxl5005s,af9013,dvb_usb_af9015,dvb_usb
usbcore 146028
6 dvb_usb_af9015,dvb_usb,usbhid,ehci_hcd,ohci_hcd
Thomas
Am Samstag, den 19.07.2008, 10:58 +0200 schrieb tom:
> Hi Antti,
> I have installed the driver. After reboot dmesg gives the following.
>
> dmesg | grep dvb:
>
> [ 1387.281913] dvb-usb: MSI DIGIVOX Duo successfully deinitialized and
> disconnected.
> [ 1397.029836] dvb-usb: found a 'MSI DIGIVOX Duo' in cold state, will
> try to load a firmware
> [ 1397.062503] dvb-usb: downloading firmware from file
> 'dvb-usb-af9015.fw'
> [ 760.590855] dvb-usb: generic DVB-USB module successfully
> deinitialized and disconnected.
> [ 1397.796493] dvb-usb: found a 'MSI DIGIVOX Duo' in warm state.
> [ 1397.796602] dvb-usb: will pass the complete MPEG2 transport stream to
> the software demuxer.
> [ 1398.548360] dvb-usb: will pass the complete MPEG2 transport stream to
> the software demuxer.
> [ 1399.517422] dvb-usb: MSI DIGIVOX Duo successfully initialized and
> connected.
> [ 1510.506232] dvb-usb: could not handle pid_parser
> [ 1532.502328] dvb-usb: could not handle pid_parser
> [ 1555.125203] dvb-usb: could not handle pid_parser
> [ 1577.464244] dvb-usb: could not handle pid_parser
> [ 1600.496149] dvb-usb: could not handle pid_parser
> [ 1622.496391] dvb-usb: could not handle pid_parser
> [ 2324.836824] dvb-usb: could not handle pid_parser
> [ 2347.650720] dvb-usb: could not handle pid_parser
> [ 2371.133792] dvb-usb: could not handle pid_parser
> [ 2393.752616] dvb-usb: could not handle pid_parser
> [ 2415.895728] dvb-usb: could not handle pid_parser
> [ 2437.891824] dvb-usb: could not handle pid_parser
>
> A channel scan with Kaffeine was not successfull. Here the results:
>
> kbuildsycoca running...
> Reusing existing ksycoca
> /dev/dvb/adapter0/frontend0 : opened ( Afatech AF9013 DVB-T )
> /dev/dvb/adapter1/frontend0 : opened ( Afatech AF9013 DVB-T )
> 0 EPG plugins loaded for device 0:0.
> 0 EPG plugins loaded for device 1:0.
> Loaded epg data : 0 events (0 msecs)
> kio (KMimeType): WARNING: KServiceType::offers : servicetype
> ThumbCreator not found
> kio (KMimeType): WARNING: KServiceType::offers : servicetype
> ThumbCreator not found
> tom@super-klappi:~$ DvbCam::probe(): /dev/dvb/adapter0/ca0: : No such
> file or directory
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 402000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 1/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 490000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 12/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 514000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 15/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 538000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 18/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 562000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 21/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 586000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 24/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 610000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 27/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 698000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 38/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 722000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 41/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 746000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 44/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 770000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 47/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 858000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> .FE_READ_STATUS: Remote I/O error
>
> Transponders: 58/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Using DVB device 0:0 "Afatech AF9013 DVB-T"
> tuning DVB-T to 882000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> ERROR tuning
> : Invalid argument
> Frontend closed
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> openFe:: Device or resource busy
> dvbsi: Cant tune DVB
> Transponders: 63
> dvbsi: The end :)
> Channels found: 0
>
> Thomas
>
>
> Am Freitag, den 18.07.2008, 23:49 +0300 schrieb Antti Palosaari:
> > Antti Palosaari wrote:
> > > tom wrote:
> > >> Hello,
> > >> since a few days I'm trying hard make this stick running. One basic problem is that I'm not able to find out which chipset is in this
> > >> stick.
> > >> I have tried af9015 driver and firmware, but it doesn't work.
> > >
> > > It looks like AF9015 dual design. I think problem you have is missing
> > > device USB-IDs. I will add those in a next few hours and you can test
> > > then again.
> >
> > Now it is ready for the test.
> > http://linuxtv.org/hg/~anttip/af9015/
> >
> > Antti
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
2008-07-19 12:13 ` tom
@ 2008-07-20 12:56 ` Antti Palosaari
2008-07-20 13:19 ` tom
0 siblings, 1 reply; 9+ messages in thread
From: Antti Palosaari @ 2008-07-20 12:56 UTC (permalink / raw)
To: tom; +Cc: linux-dvb
hello tom
tom wrote:
> results of lsmod | grep dvb:
>
> dvb_usb_af9015 24332 0
> dvb_usb 22924 1 dvb_usb_af9015
> dvb_core 80636 1 dvb_usb
> i2c_core 24832 4 mxl5005s,af9013,dvb_usb_af9015,dvb_usb
> usbcore 146028
> 6 dvb_usb_af9015,dvb_usb,usbhid,ehci_hcd,ohci_hcd
>
> Thomas
>
>
> Am Samstag, den 19.07.2008, 10:58 +0200 schrieb tom:
>> Hi Antti,
>> I have installed the driver. After reboot dmesg gives the following.
>> [ 1532.502328] dvb-usb: could not handle pid_parser
I don't know whats wrong but it looks like coming from PID-filter. You
have only USB1.1 ports?
Driver will disable 2nd tuner / frontend if there is only USB1.1 because
I don't know if there is any way to use PID-filters for 2nd frontend.
Also FE#1 performance is bad in dual tuner device for unknown reason.
But I still don't see reason why your device is not working.
Thats weird situation:
dual mode (2 receivers):
FE#1 bad
FE#2 good
single mode (1 receiver):
FE#1 good
--
http://palosaari.fi/
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
2008-07-20 12:56 ` Antti Palosaari
@ 2008-07-20 13:19 ` tom
2008-07-22 17:03 ` Thomas Ickes
0 siblings, 1 reply; 9+ messages in thread
From: tom @ 2008-07-20 13:19 UTC (permalink / raw)
To: Antti Palosaari; +Cc: linux-dvb
Hello Antti,
based on the techn. spec of my notebook (compaq evo n800w) there are usb
2.0 ports...
I'm lost in space regarding the pid filters, I even don't know what the
pid filter is :-). Sorry, but I'm not using linux for so long...
Maybe someone else have an idea why this is not working.
Thomas
Am Sonntag, den 20.07.2008, 15:56 +0300 schrieb Antti Palosaari:
> hello tom
>
> tom wrote:
> > results of lsmod | grep dvb:
> >
> > dvb_usb_af9015 24332 0
> > dvb_usb 22924 1 dvb_usb_af9015
> > dvb_core 80636 1 dvb_usb
> > i2c_core 24832 4 mxl5005s,af9013,dvb_usb_af9015,dvb_usb
> > usbcore 146028
> > 6 dvb_usb_af9015,dvb_usb,usbhid,ehci_hcd,ohci_hcd
> >
> > Thomas
> >
> >
> > Am Samstag, den 19.07.2008, 10:58 +0200 schrieb tom:
> >> Hi Antti,
> >> I have installed the driver. After reboot dmesg gives the following.
>
> >> [ 1532.502328] dvb-usb: could not handle pid_parser
>
> I don't know whats wrong but it looks like coming from PID-filter. You
> have only USB1.1 ports?
>
> Driver will disable 2nd tuner / frontend if there is only USB1.1 because
> I don't know if there is any way to use PID-filters for 2nd frontend.
> Also FE#1 performance is bad in dual tuner device for unknown reason.
> But I still don't see reason why your device is not working.
>
> Thats weird situation:
> dual mode (2 receivers):
> FE#1 bad
> FE#2 good
> single mode (1 receiver):
> FE#1 good
>
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
2008-07-20 13:19 ` tom
@ 2008-07-22 17:03 ` Thomas Ickes
2008-07-22 17:21 ` Antti Palosaari
0 siblings, 1 reply; 9+ messages in thread
From: Thomas Ickes @ 2008-07-22 17:03 UTC (permalink / raw)
To: 'tom'; +Cc: linux-dvb
Hello,
isn't there anyone who has some hints for me regarding the PID Filter Problems?
Thanks
Thomas
-----Ursprüngliche Nachricht-----
Von: linux-dvb-bounces@linuxtv.org [mailto:linux-dvb-bounces@linuxtv.org] Im Auftrag von tom
Gesendet: Sonntag, 20. Juli 2008 15:19
An: Antti Palosaari
Cc: linux-dvb@linuxtv.org
Betreff: Re: [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
Hello Antti,
based on the techn. spec of my notebook (compaq evo n800w) there are usb
2.0 ports...
I'm lost in space regarding the pid filters, I even don't know what the
pid filter is :-). Sorry, but I'm not using linux for so long...
Maybe someone else have an idea why this is not working.
Thomas
Am Sonntag, den 20.07.2008, 15:56 +0300 schrieb Antti Palosaari:
> hello tom
>
> tom wrote:
> > results of lsmod | grep dvb:
> >
> > dvb_usb_af9015 24332 0
> > dvb_usb 22924 1 dvb_usb_af9015
> > dvb_core 80636 1 dvb_usb
> > i2c_core 24832 4 mxl5005s,af9013,dvb_usb_af9015,dvb_usb
> > usbcore 146028
> > 6 dvb_usb_af9015,dvb_usb,usbhid,ehci_hcd,ohci_hcd
> >
> > Thomas
> >
> >
> > Am Samstag, den 19.07.2008, 10:58 +0200 schrieb tom:
> >> Hi Antti,
> >> I have installed the driver. After reboot dmesg gives the following.
>
> >> [ 1532.502328] dvb-usb: could not handle pid_parser
>
> I don't know whats wrong but it looks like coming from PID-filter. You
> have only USB1.1 ports?
>
> Driver will disable 2nd tuner / frontend if there is only USB1.1 because
> I don't know if there is any way to use PID-filters for 2nd frontend.
> Also FE#1 performance is bad in dual tuner device for unknown reason.
> But I still don't see reason why your device is not working.
>
> Thats weird situation:
> dual mode (2 receivers):
> FE#1 bad
> FE#2 good
> single mode (1 receiver):
> FE#1 good
>
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
2008-07-22 17:03 ` Thomas Ickes
@ 2008-07-22 17:21 ` Antti Palosaari
0 siblings, 0 replies; 9+ messages in thread
From: Antti Palosaari @ 2008-07-22 17:21 UTC (permalink / raw)
To: Thomas Ickes; +Cc: linux-dvb
Thomas Ickes wrote:
> Hello,
>
> isn't there anyone who has some hints for me regarding the PID Filter Problems?
For me it looked like af9015_pid_filter_ctrl() was failing and thats why
errors. I don't have idea why it is failing. But I did special build for
you to test again. Now whole PID-filter is disabled.
http://linuxtv.org/hg/~anttip/af9015_disable_pid_filter/
PID-filtering is needed if we have only USB1.1 ports. PID-filter removes
unnecessary channels from transport stream that it can fit to USB1.1
speed. USB2.0 does not need PID-filtering because it is capable of
transfer whole stream (MUX).
Antti
>
> Thanks
> Thomas
>
> -----Ursprüngliche Nachricht-----
> Von: linux-dvb-bounces@linuxtv.org [mailto:linux-dvb-bounces@linuxtv.org] Im Auftrag von tom
> Gesendet: Sonntag, 20. Juli 2008 15:19
> An: Antti Palosaari
> Cc: linux-dvb@linuxtv.org
> Betreff: Re: [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
>
> Hello Antti,
>
> based on the techn. spec of my notebook (compaq evo n800w) there are usb
> 2.0 ports...
> I'm lost in space regarding the pid filters, I even don't know what the
> pid filter is :-). Sorry, but I'm not using linux for so long...
>
> Maybe someone else have an idea why this is not working.
>
> Thomas
>
> Am Sonntag, den 20.07.2008, 15:56 +0300 schrieb Antti Palosaari:
>> hello tom
>>
>> tom wrote:
>>> results of lsmod | grep dvb:
>>>
>>> dvb_usb_af9015 24332 0
>>> dvb_usb 22924 1 dvb_usb_af9015
>>> dvb_core 80636 1 dvb_usb
>>> i2c_core 24832 4 mxl5005s,af9013,dvb_usb_af9015,dvb_usb
>>> usbcore 146028
>>> 6 dvb_usb_af9015,dvb_usb,usbhid,ehci_hcd,ohci_hcd
>>>
>>> Thomas
>>>
>>>
>>> Am Samstag, den 19.07.2008, 10:58 +0200 schrieb tom:
>>>> Hi Antti,
>>>> I have installed the driver. After reboot dmesg gives the following.
>>>> [ 1532.502328] dvb-usb: could not handle pid_parser
>> I don't know whats wrong but it looks like coming from PID-filter. You
>> have only USB1.1 ports?
>>
>> Driver will disable 2nd tuner / frontend if there is only USB1.1 because
>> I don't know if there is any way to use PID-filters for 2nd frontend.
>> Also FE#1 performance is bad in dual tuner device for unknown reason.
>> But I still don't see reason why your device is not working.
>>
>> Thats weird situation:
>> dual mode (2 receivers):
>> FE#1 bad
>> FE#2 good
>> single mode (1 receiver):
>> FE#1 good
>>
>
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
--
http://palosaari.fi/
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2008-07-22 17:21 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-18 17:55 [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04 tom
2008-07-18 18:21 ` Antti Palosaari
2008-07-18 20:49 ` Antti Palosaari
2008-07-19 8:58 ` tom
2008-07-19 12:13 ` tom
2008-07-20 12:56 ` Antti Palosaari
2008-07-20 13:19 ` tom
2008-07-22 17:03 ` Thomas Ickes
2008-07-22 17:21 ` Antti Palosaari
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox