Andrew de Quincey wrote: > its not the firmware. > its not the frontend driver (that was a different issue). > > well, pretty obvious where it has to be really; must be a card setup problem > in the OSS code. I'll have a closer check over the next few days.
Like I said before, DiSEqC was always unreliable with my ves1893 card, but I don't know if it is a general problem or if just my card is broken. Anyway, today I got a DiSEqC test box from Eutelsat, and it does not even recognize a single valid bit of DiSEqC data. It recognizes 13(18 volt and tone on/off, so I guess the timings of our DiSEqC stuff must be totally off. I didn't have the time to connect an oscilloscope to investigate further. Maybe tomorrow. The little Spaun DiSEqC test box I use normally recognizes the DiSEqC sequences most of the time, but it is probably much more tolerant that the Eutelsat test box. Does someone know for sure how the DiSEqC signals for a ttpci rev1.3 card with ves1893 are generated? Is this different from all other cards? [I also tried a WinTV-NOVA-CI with stv0299 / SU1278 (TSA5059 synth). DiSEqC works perfect here according to the Eutelsat test box.] Johannes -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
