linux-kernel - PCTV452e unable to tune in Kernel 3.2 RC3 / RC4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAP_ERaEQZH=a1DkbWDgpPHSuk7e=unHsBmtD1=7C4G-pSFnhmg@mail.gmail.com>
Date:	Mon, 5 Dec 2011 13:22:57 +0000
From:	Neil Sutton <sutton.nm@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: PCTV452e unable to tune in Kernel 3.2 RC3 / RC4

Hi all,

I'm trying to make my TT S2-3600 work with Kernel 3.2 - Tried RC3 and
RC4 - (I believe it now supports this adapter via PCTV452e)
So, I enabled the PCTV452e module in the kernel config and the device
detects ok;

[   12.075239] dvb-usb: found a 'Technotrend TT Connect S2-3600' in warm state.
[   12.076620] dvb-usb: will pass the complete MPEG2 transport stream
to the software demuxer.
[   12.080767] dvb-usb: MAC address: 00:d0:5c:64:54:95
[   13.298383] dvb-usb: Technotrend TT Connect S2-3600 successfully
initialized and connected.

But when I try to make any tuning with the device I get no picture and
the following get put to syslog;

Dec  2 01:01:26 MicroServer kernel: [ 1535.331468] dvb-usb: could not
submit URB no. 0 - get them all back
Dec  2 01:01:26 MicroServer kernel: [ 1535.372388] pctv452e: I2C error
-121; AA 97  CC 00 01 -> 55 97  CC 00 00.
Dec  2 01:01:26 MicroServer kernel: [ 1535.385003] pctv452e: I2C error
-121; AA AE  CC 00 01 -> 55 AE  CC 00 00.
Dec  2 01:01:26 MicroServer kernel: [ 1535.444992] pctv452e: I2C error
-121; AA C9  CC 00 01 -> 55 C9  CC 00 00.

The 'URB' errors appear each time the card moves to a new transponder,
the I2C errors appear to be when the card is attempting to lock a
channel within the current transponder.

Does anyone have any thoughts on what might be causing this ? - I've
had a search around but can't really find the problem mentioned
anywhere... the device works fine under the latest liplianin drivers.

I posted this a few days back at the linuxdvb list, but I'm not
entirely sure where this falls, so apologies if this is not the
correct place to report this!

Many Thanks
Neil
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/