Budget TT-1500C and decryption

Firstly, I apologise for posting in English !

I have recently bought a TechnoTrend C-1500, CI and Irdeto CAM from dvbshop for use in New Zealand.

The card works fine under Windows (ONLY to test!!) and scans transponders fine under linux - but won't decrypt pay channels under Linux.

I am running a 32-bit system, have tested 2.6.19 & 2.6.20 kernels (FC5 & FC6) with a recent mercurial snapshot of v4l-dvb.

Every test results in the same errors:
en50221_tl_poll: CAWrite failed" and "en50221_stdcam_llci_poll: Error reported by stack:-2"
"vdr: [2774] ERROR: can't write to CI adapter on device 0: Input/output error"

I also can't access the CAM menu in Linux (ok in Windows)

Can anyone help?

Thanks
Simon

Yes, the flat cable is ok. And the card works fine with the provided software under Windows.

Also, yes, my card has a cable-in and cable-out (so 2x 75 ohm plug/socket).

Can you tell me your kernel version, and what version of v4l-dvb?

Thanks

Zitat

Originally posted by baxternz
<snip>
Can you tell me your kernel version, and what version of v4l-dvb?

Thanks

I've tried it in 2 boxes running :
cat /development/mercurial/v4l-dvb/v4l/.version
VERSION=2
PATCHLEVEL:=6
SUBLEVEL:=19
KERNELRELEASE:=2.6.19-1.2288.2.4.fc5

&

cat /usr/src/development/v4l-dvb/v4l/.version
VERSION=2
PATCHLEVEL:=6
SUBLEVEL:=20
KERNELRELEASE:=2.6.20-1.2944.fc6

Zitat

Originally posted by Dr. Seltsam
I am using this card and the CI since many Kernel versions and have always the latest v4l-dvb hg. It should really work "out of the box" with a recent kernel. I can only guess that the newer card revison needs a modificated driver. The first time we heard about this new revision was a few weeks ago. People reported problems with QAM256 (which works fine with the old revision), but I can`t remember if those guys also tested the CI

Here's my lspci:
02:07.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: Technotrend Systemtechnik GmbH Unknown device 1010
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (3750ns min, 9500ns max)
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fe1ffc00 (32-bit, non-prefetchable) [size=512]

Does this look different to the 1-connector model?

Zitat

Originally posted by Dr. Seltsam
As far as I know it was not yet discovered what the differencies really are ... all we know is the bad handling of QAM256 and now maybe the CI support.

I suggest that you write to the v4l-dvb mailing list:
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

I have been for WEEKS - with no progress!!!!

OK, made some progress with some hacks of dvb_ca_en50221.c and saa7146_i2c.c.

I'm still getting no picture though? My cable provider
only provides encrypted channels, so can't do any testing free-to-air
channels.

Here's my modprobe in dmesg:
saa7146: register extension 'budget_ci dvb'.
ACPI: PCI Interrupt Link [PIN3] enabled at IRQ 15
PCI: setting IRQ 15 as level-triggered
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [PIN3] -> GSI 15 (level, low) ->
IRQ 15
saa7146: found saa7146 @ mem d09e2e00 (revision 1, irq 15) (0x13c2,0x1010).
saa7146 (0): dma buffer size 192512
DVB: registering new adapter (TT-Budget-C-CI PCI).
adapter has MAC addr = 00:d0:5c:67:bf:11
input: Budget-CI dvb ir receiver saa7146 (0) as /class/input/input5
budget_ci: CI interface initialised
DVB: registering frontend 0 (ST STV0297 DVB-C)...

Here's my log from VDR:
Jun 4 22:06:56 media1 kernel: dvb_ca adapter 0: DVB CAM detected and
initialised successfully
Jun 4 22:06:56 media1 vdr: [2359] CAM 1: module ready
Jun 4 22:06:57 media1 vdr: [2363] setting current skin to "sttng"
Jun 4 22:06:57 media1 vdr: [2363] loading
/media/video/vdr-1.5.2/themes/sttng-default.theme
Jun 4 22:06:58 media1 vdr: [2359] CAM 1: Irdeto Access, 01, 06FF, 06FF
Jun 4 22:07:02 media1 vdr: [2355] switching to channel 54
Jun 4 22:07:02 media1 vdr: [2355] setting current skin to "curses"
Jun 4 22:07:06 media1 vdr: [2355] retuning due to modification of channel
54
Jun 4 22:07:06 media1 vdr: [2355] switching to channel 54
Jun 4 22:07:25 media1 vdr: [2374] ERROR: no useful data seen within
10582520 byte of video stream
Jun 4 22:07:31 media1 vdr: [2355] switching to channel 2
Jun 4 22:07:32 media1 vdr: [2355] retuning due to modification of channel 2
Jun 4 22:07:32 media1 vdr: [2355] switching to channel 2
Jun 4 22:07:54 media1 vdr: [2380] ERROR: no useful data seen within
10576880 byte of video stream

Here's my kernel messages:
dvb_ca adapter 0: DVB CAM detected and initialised successfully

Can anyone suggest any other testing I can do?? It looks like it should be
working?

Thanks