On Saturday 20 May 2006 17:07, Greg Manning wrote: > On 20 May 2006, at 16:17, Andrew de Quincey wrote: > > On Saturday 20 May 2006 15:33, Greg Manning wrote: > >> On 20/05/06, Andrew de Quincey <adq_dvb@xxxxxxxxxxxxx> wrote: > >>> On Saturday 20 May 2006 14:35, Greg Manning wrote: > >>>> On 20 May 2006, at 14:01, Andrew de Quincey wrote: > >>>>> On Saturday 20 May 2006 12:56, Greg Manning wrote: > >>>>>> On 20 May 2006, at 12:01, Andrew de Quincey wrote: > >>>>>>> On Thursday 18 May 2006 11:42, Greg Manning wrote: > >>>>>>>> Hi, > >>>>>>>> I've got a Pinnacle 300i, which I can't get working. I was on > >>>>>>>> ubuntu breezy > >>>>>>>> stock (2.6.12-10-k7) kernel, which didn't work, so I tried > >>>>>>>> applying patches > >>>>>>>> i found on the mailing list, to no avail. > >>>>>>>> Last night I compiled latest 2.6.12-ck9, which behaved > >>>>>>>> identically > >>>>>>>> to the > >>>>>>>> old kernel (with regard to the pinnacle). I've just tried the > >>>>>>>> patch from > >>>>>>>> http://www.linuxtv.org/pipermail/linux-dvb/2006-May/010152.html > >>>>>>>> there, but that makes no difference either. So I'm currently > >>>>>>>> running latest > >>>>>>>> hg pull, with that patch, and i get these messages in dmesg > >>>>>>>> (these have been the same regardless of what kernel/patch i've > >>>>>>>> been running): > >>>>>>> > >>>>>>> [snip] > >>>>>>> > >>>>>>>> Any ideas what's going on here? > >>>>>>>> (The card works in Windows, so I don't think its a DOA) > >>>>>>> > >>>>>>> Hmm, strange - the card was reported as working with that latest > >>>>>>> patch. Has it > >>>>>>> ever worked in linux? (I saw you tested it in windows so at > >>>>>>> least > >>>>>>> the > >>>>>>> hardware is ok) > >>>>>> > >>>>>> Nope, never worked. Always that same error, too. Makes me > >>>>>> wonder if > >>>>>> there's something unique about my box. No idea what though... > >>>>> > >>>>> Can you send details of an example channel you're trying to tune > >>>>> under linux? > >>>>> Perhaps the demod requires tweaking... > >>>> > >>>> Ok, I think is what you mean (but I'm not sure)... > >>>> > >>>> gm@kimiko:~$ tzap -c channels.conf 'BBC ONE' > >>>> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > >>>> tuning to 722166670 Hz > >>>> video pid 0x0258, audio pid 0x0259 > >>>> status 00 | signal ffff | snr 0000 | ber 00000000 | unc 00000000 | > >>>> status 00 | signal 000f | snr 0000 | ber 00000000 | unc 00000000 | > >>>> status 00 | signal 000f | snr 0000 | ber 00000000 | unc 00000000 | > >>>> status 00 | signal 000f | snr 0000 | ber 00000000 | unc 00000000 | > >>>> status 00 | signal 000f | snr 0000 | ber 00000000 | unc 00000000 | > >>>> ...(every further line identical). > >>>> > >>>> This is accompanied by a whole load of mt352_pinnacle_init called > >>>> messages in the logs. > >>>> The frequency is right (pulled out of a channel.conf from a working > >>>> machine). > >>> > >>> ok, can you send the BBC ONE line from your channels.conf as well > >>> please? > >> > >> ah, sorry. Yes: > >> > >> BBC > >> ONE: > >> 722166670:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANS > >> MI > >> SSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:600:601:4170 > > > > Hmm, just noticed something odd in the driver - > > linux/drivers/media/dvb/frontends/mt352.c/mt352_set_parameters() > > > > line 283, it says: > > > > buf[3] = 0x50; // old > > // buf[3] = 0xf4; // pinnacle > > > > Wanna try swapping those over and see if it does anything? I'll > > find out what > > thats actually doing in the meantime. > > Uhm. My (wonderful*) housemate unplugged my aerial cable. > Things seem to work now. I'll just have a fiddle and see if I can > find what fixed it. > Sorry to be so stupid. > > Greg > *no seriously, he did tidy the lounge. It's just that involved > removing my long cable. LOL :) Lemme know what you find... _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
