From: Antti Palosaari <crope@iki.fi>
To: Jelle de Jong <jelledejong@powercraft.nl>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: Afatech AF9013 DVB-T not working with mplayer radio streams
Date: Fri, 03 Jul 2009 01:44:28 +0300 [thread overview]
Message-ID: <4A4D384C.3090101@iki.fi> (raw)
In-Reply-To: <4A4C7349.2080705@powercraft.nl>
On 07/02/2009 11:43 AM, Jelle de Jong wrote:
> Some extra information about the lockups of my AF9015, this is a serious
> blocker issue for me. It happens when I watch a channel with totem-xine
> and switch to an other channel, the device is then unable to lock to the
> new channel, and totem-xine hangs. There are no messages in dmesg.
>
> Rebooting the system does not help getting the device working again, the
> only way i found is to replug the usb device and this is not an option
> for my systems because the usb devices are hidden.
I have seen that also with Totem-xine few times. Totem-xine hags totally
and it must be killed. But after that my device starts working without
replug (if I remember correctly). One thing could be power issue. If you
have possibility to test with powered USB -hub please do.
> Is there an other USB DVB-T device that works out of the box with the
> 2.9.30 kernel? Could somebody show me a link or name of this device so I
> can buy and test it?
DibCOM based sticks are usually good choice. There is many models from
many vendors, TerraTec, Artec (Artec T14BR is sold here in Finland 20-30e).
DibCOM also uses big USB block size which seems to reduce system load.
Look examples from here:
http://www.linuxtv.org/wiki/index.php/User:Hlangos
Could someone explain why USB block size have so big effect to load?
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2009-07-02 22:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 8:07 Afatech AF9013 DVB-T not working with mplayer radio streams Jelle de Jong
2009-06-30 20:12 ` Jelle de Jong
2009-07-02 8:43 ` Jelle de Jong
2009-07-02 16:09 ` Devin Heitmueller
2009-07-02 20:51 ` Jelle de Jong
2009-07-02 21:18 ` Devin Heitmueller
2009-07-02 22:44 ` Antti Palosaari [this message]
2009-07-02 22:29 ` Antti Palosaari
2009-07-03 16:01 ` Jelle de Jong
2009-07-10 1:05 ` Devin Heitmueller
2009-07-10 8:25 ` Jelle de Jong
2009-07-10 12:09 ` Antti Palosaari
2009-07-10 15:16 ` Devin Heitmueller
2009-07-10 15:40 ` Jelle de Jong
2009-07-10 17:09 ` Devin Heitmueller
2009-07-10 17:09 ` Devin Heitmueller
2009-07-10 21:12 ` Antti Palosaari
2009-07-10 23:11 ` Antti Palosaari
2009-07-11 10:31 ` Jelle de Jong
2009-07-11 11:48 ` Jelle de Jong
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=4A4D384C.3090101@iki.fi \
--to=crope@iki.fi \
--cc=jelledejong@powercraft.nl \
--cc=linux-media@vger.kernel.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