On Tuesday 06 April 2004 18:47, Jesper Sörensen wrote: > Andrew de Quincey wrote: > >>Oh dear, this is the sort of thing that Robert was seeing with the > >> Zetacam. > > Oh dear in fact. I thought that "Valid DVB CAM detected" meant that > there was hope for this CAM. If this one is broken too, is there any > chance a new Conax CAM would work or are all Conax CAMs doomed too?
I really can't say; with the ZetaCAM, Robert was able to do the equivalent of all the same stuff, but it failed in the link initialisation as well. > I'm sorry I can't test this with Windows (it's not installed on that > machine). If nothing else works I'll try installing Windows or testing > this in another machine, but I can't do that until this weekend at the > earliest... If you're willing to give it a go under windows thats great! No problems about having to wait a few days. > dvb_ca_en50221_link_init > dvb_ca_en50221_wait_if_status > STATUS: 43 Er, weird! That status is printed just after the comms interface is reset. And its showing both a READ and a WRITE transfer error.... no data has been transferred at that point... > dvb_ca_en50221_wait_if_status succeeded timeout:0 > dvb_ca_en50221_wait_if_status > STATUS: 43 > dvb_ca_en50221_wait_if_status failed timeout:101 > dvb_ca_en50221_read_data > dvb_ca: DVB CAM link initialisation failed :( > > I'm willing to continue testing as long as you're willing to send > patches. :-) I know C but I have no experience with this low level stuff > so I'm not sure how much I can help. Thanks, I'll try and think of something else to test... -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
