From: tom <thomas@ickes-home.de>
To: Antti Palosaari <crope@iki.fi>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] WG: Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
Date: Tue, 22 Jul 2008 20:41:17 +0200 [thread overview]
Message-ID: <1216752077.6686.4.camel@super-klappi> (raw)
In-Reply-To: <48862536.9070906@iki.fi>
Did
make
make install
make rmmod
replug strick
-> lsmod | grep usb
dvb_usb_af9015 23820 1
dvb_usb 22924 1 dvb_usb_af9015
dvb_core 80636 1 dvb_usb
i2c_core 24832 4 mxl5005s,af9013,dvb_usb_af9015,dvb_usb
usbhid 31872 0
hid 38784 1 usbhid
usbcore 146028 6
dvb_usb_af9015,dvb_usb,usbhid,ehci_hcd,ohci_hcd
-> channel scan
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
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 578000000 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: 23/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 602000000 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: 26/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 626000000 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: 29/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 650000000 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: 32/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 674000000 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: 35/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 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
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 794000000 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: 50/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 818000000 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: 53/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 842000000 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: 56/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 866000000 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
openFe:: Device or resource busy
dvbsi: Cant tune DVB
Using DVB device 0:0 "Afatech AF9013 DVB-T"
tuning DVB-T to 898000000 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
Transponders: 63
dvbsi: The end :)
Channels found: 0
Any further ideas or informations which I can provide?
Thanks
Thomas
Am Dienstag, den 22.07.2008, 21:21 +0300 schrieb Antti Palosaari:
> tom wrote:
> > thanks for the quick reply and providing the test!!
> >
> > Should I use 'make rminstall' before I instal the test?
> > And for installing the test, should I use the 'make all'?
>
> make
> make install
> make rmmod
> replug stick
>
> >
> > Thomas
> >
> > Am Dienstag, den 22.07.2008, 19:52 +0200 schrieb Thomas Ickes:
> >> -----Ursprüngliche Nachricht-----
> >> Von: Antti Palosaari [mailto:crope@iki.fi]
> >> Gesendet: Dienstag, 22. Juli 2008 19:21
> >> An: Thomas Ickes
> >> Cc: linux-dvb@linuxtv.org
> >> Betreff: Re: [linux-dvb] Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04
> >>
> >> 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
> >>
> >
>
>
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-07-22 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0MKxQS-1KLM2V1c9L-0001hx@mrelayeu.kundenserver.de>
2008-07-22 18:16 ` [linux-dvb] WG: Problems with MSI Digivox Duo DVB-T USB, Ubuntu 8.04 tom
2008-07-22 18:21 ` Antti Palosaari
2008-07-22 18:41 ` tom [this message]
2008-07-22 18:46 ` Antti Palosaari
[not found] ` <1216754067.6686.7.camel@super-klappi>
2008-07-22 19:21 ` Antti Palosaari
2008-07-22 19:26 ` tom
2008-07-22 19:34 ` Antti Palosaari
2008-07-22 19:35 ` tom
2008-07-22 19:51 ` tom
2008-07-22 20:00 ` tom
2008-07-22 20:07 ` Antti Palosaari
2008-07-22 20:31 ` tom
2008-07-25 8:27 ` tom
2008-07-25 11:10 ` Antti Palosaari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1216752077.6686.4.camel@super-klappi \
--to=thomas@ickes-home.de \
--cc=crope@iki.fi \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox