From: Antti Palosaari <crope@iki.fi>
To: Steve Hill <steve@nexusuk.org>
Cc: linux-media@vger.kernel.org, Marx <acc.for.news@gmail.com>
Subject: Re: pctv452e
Date: Sat, 06 Jul 2013 16:29:34 +0300 [thread overview]
Message-ID: <51D81BBE.4030003@iki.fi> (raw)
In-Reply-To: <4FF1CD63.10003@nexusuk.org>
Hi guys,
I was able to got that device, just because of you, and I cannot
reproduce that error. I ran it many hours against signal from modulator
yesterday and it didn't hang. I used szap && mplayer. Also I ran w_scan.
Only problem I saw was these I2C errors printed.
So you make tests, likely using szap, and say how I can make it hang?
regards
Antti
On 07/02/2012 07:33 PM, Steve Hill wrote:
>
> I've been using a Technotrend TT 3600 USB DVB-S2 receiver for a couple
> of years, which has (largely) been working fine under the S2-liplianin
> pctv452e driver. I've been aware of a lot of documented problems with
> running this receiver under the 3.x kernel, so I've stuck with the 2.6
> series kernels.
>
> Unfortunately I've now had to upgrade to the 3.2.0 kernel for other
> unrelated reasons, and it seems that the device is more or less unusable
> under this kernel. With the stock 3.2.0 kernel, the driver produces
> numerous I2C errors and is quite unreliable. The I2C errors seem to be
> produced exclusively as a result of stb_6100_read_reg() reading register
> F, and notably all calls to stb6100_read_regs() seem to succeed, so I've
> replaced the stb_6100_read_reg() function with a call to
> stb6100_read_regs(), so it reads all the registers and then returns the
> requested one, rather than reading just the requested register. This
> seems to make the I2C errors disappear.
>
> However, the card is still very unreliable - after about 5 minutes of
> receiving a channel (using MythTV), it breaks. No errors logged in
> dmesg, but MythTV logs:
>
> DevRdB(/dev/dvb/adapter0/frontend0) Error: Poll giving up
> DVBSH(/dev/dvb/adapter0/frontend0) Error: Device error detected
> DVBRec(7:/dev/dvb/adapter0/frontend0) Error: Stream handler died
> unexpectedly.
>
>
> Can anyone give me any pointers that might help? I've searched and
> searched and all I can see if people saying that it won't work since the
> DVB-S2 code was integrated into the kernel tree, but I've not seen
> anyone try to figure out _why_ it won't work.
>
> Thanks.
>
--
http://palosaari.fi/
next prev parent reply other threads:[~2013-07-06 13:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 16:33 pctv452e Steve Hill
2012-07-03 7:46 ` pctv452e Marx
2012-07-03 23:04 ` pctv452e Antti Palosaari
2012-07-04 7:51 ` pctv452e Marx
2013-07-06 13:29 ` Antti Palosaari [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-04 16:04 pctv452e Steve Hill
2012-07-04 16:22 ` pctv452e Antti Palosaari
2012-07-04 18:46 ` pctv452e Marx
2012-07-04 18:53 ` pctv452e André Weidemann
2012-07-04 19:01 ` pctv452e Antti Palosaari
2012-07-05 13:14 ` pctv452e Marx
2012-07-05 14:23 ` pctv452e Antti Palosaari
2012-07-06 6:13 ` pctv452e Marx
2012-07-06 9:34 ` pctv452e Antti Palosaari
2012-07-06 11:04 ` pctv452e Marx
2012-07-06 18:24 ` pctv452e Antti Palosaari
2012-07-06 22:23 ` pctv452e Marx
2012-07-07 0:00 ` pctv452e Antti Palosaari
2012-07-07 23:07 ` pctv452e Marx
2012-07-08 12:32 ` pctv452e Antti Palosaari
2012-07-09 6:24 ` pctv452e Marx
2012-07-09 8:42 ` pctv452e Antti Palosaari
2012-07-09 16:44 ` pctv452e Marx
2012-07-09 17:38 ` pctv452e Antti Palosaari
2012-07-09 17:46 ` pctv452e Antti Palosaari
2012-07-10 6:39 ` pctv452e Marx
2012-07-10 9:33 ` pctv452e Antti Palosaari
2012-07-10 21:08 ` pctv452e Marx
2012-07-10 23:13 ` pctv452e Antti Palosaari
2012-07-11 6:25 ` pctv452e Marx
2012-07-11 10:00 ` pctv452e Antti Palosaari
2012-07-09 18:21 ` pctv452e poma
2012-07-10 6:43 ` pctv452e Marx
2012-07-10 15:51 ` pctv452e poma
2012-07-10 15:58 ` pctv452e Devin Heitmueller
2012-07-10 22:54 ` pctv452e poma
2012-08-03 16:56 ` pctv452e Steve Hill
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=51D81BBE.4030003@iki.fi \
--to=crope@iki.fi \
--cc=acc.for.news@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=steve@nexusuk.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;
as well as URLs for NNTP newsgroup(s).