[vdr] Re: CAM Read Error

["Lübeck, Harald" <Harald.Luebeck@gft.com>]

My Card a Nexus-s with an 3.5" CI doesn't even show the CAM Menu! I think there is something to do in the firmware. The Multidec Project( on Windows :-( )work's well with this CI. 

-----Original Message-----
From: Adrian Carpenter [mailto:adrian.carpenter@btinternet.com] 
Sent: Dienstag, 8. April 2003 19:23
To: vdr@linuxtv.org
Subject: [vdr] Re: CAM Read Error


I'm slightly more optimistic now that I was a couple of months ago, it's only with the latest driver and version of vdr that it nearly works, it does work with encrypted channels but something cause's it to reset - i never got it to work with the previous versions at all.

I have an STB, so it's not that much of an issue, but I'd like to use VDR because it allows recording to HD etc - functions which my STB doesn't do. Until VDR works 100% i'll keep using the STB and use windows when I want to record a programme.

I've asked the question about the PCI CI interfaces a number of times on the list, I've never recieved a response - I take this to mean that you cannot get them anywhere now.

I know you can get the PCI CI interface for the SkyStar 1 card (Technotrend/Siemens/Hauppauge/SkyStar 1 all apparently the same or similar), but I don't know whether it works with the hauppauge.


----- Original Message -----
From: "Micael Beronius" <micael.beronius@telia.com>
To: "Adrian Carpenter" <vdr@linuxtv.org>
Sent: Tuesday, April 08, 2003 5:21 PM
Subject: [vdr] Re: CAM Read Error


> Hello Adrian,
>
> Well, I have to disappoint you. I have been using windows for some 
> months, since I never got my 1.6 3.5" CI/CAM to work under Linux, so I 
> was very exited when people started to say that this works. But just 
> trying, there's no go for me. I tried both the Metzler and the pre2, 
> none works with encrypted channels. (Viaccess)
>
> With the old driver I could get it to work sort of, by restarting the 
> firmware until I got some response from the CAM, but that was a bit 
> too tedious for me, so I gave up.
>
> Does anyone know if it is possible to get hold of the old 1.3 CI 
> anywhere?
>
>
> Oh, I get Outcommand errors, and I have a P-III, so ..
>
> In detail, I get:
> OutCommand: timeout waiting for COMMAND idle
> SOutCommand error
> outcom error
>  .. repeated.
>
> Micael
>
> Tuesday, April 8, 2003, 5:57:21 PM, you wrote:
>
> AC> Humn, I tried that earlier, I can't say whether or not it works 
> AC> for me
with
> AC> the old firmware because I can't get it to work with the old 
> AC> firmware,
if I
> AC> revert to using it, the "Convergence" logo starts to scroll off 
> AC> the
screen
> AC> and then halts, menawhile on the console I get an error saying
something
> AC> like sync error or outcommand error - VDR doesn't work and 
> AC> generally
run's
> AC> very slowly - the CAM definately for me doesn't work with the old
firmware.
>
> AC> I'm not sure whether the problem with the old firmware is related 
> AC> to
my
> AC> machine, maybe it's because it's an athlon - I seem to remember
outcommand
> AC> problems being due to interrupt issues, but I really can't face
setting my
> AC> my old 500 Mhz PII and installing RedHat 8 and recompiling the 
> AC> kernel
to get
> AC> VDR to work (At least not at the moment!).
>
> AC> Does anybody else have the Rev 1.6 3.5" cam working with either
firmware?
>
> AC> Anyway, thanks for the suggestion Norbert.
>
> AC> Adrian
> AC> ----- Original Message -----
> AC> From: "Norbert Schmidt" <nschmidt-nrw@t-online.de>
> AC> To: <vdr@linuxtv.org>
> AC> Sent: Tuesday, April 08, 2003 4:31 PM
> AC> Subject: [vdr] Re: CAM Read Error
>
>
> >> Adrian Carpenter schrieb:
> >> >
> >> > I read a post from march about someone who was getting this 
> >> > problem, (CAM: Read Error) - I think the person had a PCI CI 
> >> > Interface, and they resolved the problem by reverting back to the 
> >> > older firmware without the LL.
> >> >
> >> > With the latest VDR & pre2 driver, I'm now at the stage where my 
> >> > system will now decode an encrypted channel for maybe 30 seconds 
> >> > or so - before I get a CAM: Read Error in the log file followed 
> >> > by the CAM resetting and it taking maybe 20 seconds to start 
> >> > decoding again - this then repeats forever.
> >> >
> >> > Anybody else got this problem, I know klaus said he's not looking 
> >> > at any LL problems until after the next release, so can anybody 
> >> > tell me if this is still a 3.5" drive bay ci interface related 
> >> > issue, or is it my cam?  I've tried it with 2 different IRDETO 
> >> > CAM's (Both are normal cams, not the All-Cam version) and they 
> >> > both exhibit the same problem.
> >> >
> >> > Also, if I do a replay and fast forward, on the console I get a 
> >> > whole load of OutCommand errors and VDR crashes.
> >> >
> >> > Thanks.
> >> >
> >> > Adrian
> >> >
> >> >
> >> > --
> >> > Info:
> >> > To unsubscribe send a mail to listar@linuxtv.org with 
> >> > "unsubscribe vdr" as subject.
> >> >
> >> >
> >>
> >> Hi Adrian,
> >>
> >> I have got stable vdr working with a 3.5" CI with irdeto allcam 4.7 
> >> SE. I am using the old firmware of the driver.
> >>
> >> See DVB/Driver/av????/firmware-readme for details.
> >>
> >> CU Norbert
> >>
> >>
> >>
> >> -- 
> >> _________________________________________________________________
> >> ** Norbert Schmidt - D-47443 Moers - n.schmidt@t-online.de **
> >>
> >>
> >> --
> >> Info:
> >> To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe 
> >> vdr"
as
> AC> subject.
> >>
>
>
>
> --
> Info:
> To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe 
> vdr" as
subject.
>



-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.



--
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.