Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: 2.6.10-rc2 + dvb-kernel problem



On Friday 19 Nov 2004 00:55, Joerg Riechardt wrote:
> Andrew de Quincey wrote:
> > On Thursday 18 Nov 2004 23:30, Joerg Riechardt wrote:
> >>Andrew de Quincey wrote:
> >>>On Thursday 18 Nov 2004 22:49, Andrew de Quincey wrote:
> >>>>> it's the Skystar2 Rev. 2.3. On the tin box there is only "Samsung".
> >>>>
> >>>>Hmm, thats a bit annoying :(
> >>>>
> >>>>>According to http://www.vdr-wiki.de/wiki/index.php/SkyStar_2 it is a
> >>>>>Mitel VP310/MT312 tuner. do you need more info?
> >>>>
> >>>>Can you have a look at the board for the demodulator chip? I need to
> >>>> know if it is a VP310 or an MT312... If not, no probs, I'll just have
> >>>> to guess..
> >>>
> >>>Even easier - just use CVS head and try loading the skystar2 module - it
> >>>won't work with tuning or anything, but it will tell you in dmesg which
> >>>chip it detected.
> >>
> >>good idea! so I don't have to open it. I get:
> >>vdr kernel: mt312: Detected Zarlink VP310
> >
> > Ta - give CVS a go now.
>
> vdr kernel: PCI: Found IRQ 5 for device 0000:02:0b.0
> vdr kernel: PCI: Sharing IRQ 5 with 0000:00:1f.4
> vdr kernel: /root/dvb-kernel/build-2.6/skystar2.c: FlexCopII(rev.130)
> chip found
> vdr kernel: /root/dvb-kernel/build-2.6/skystar2.c: the chip has 6
> hardware filters
> vdr kernel: driver_initialize MAC address = ff:ff:ff:ff:ff:ff:00:00
> vdr kernel: DVB: registering new adapter (SkyStar2).
> vdr kernel: master_xfer: write error 0 !
> vdr kernel: message 0: flags=0x0, addr=0x68, buf[0]=0x2, len=2
> vdr kernel: master_xfer: read error !
> vdr kernel: message 0: flags=0x0, addr=0x68, buf=0x0, len=1
> vdr kernel: message 1: flags=0x1, addr=0x68, buf=0x0, len=1
> vdr kernel: master_xfer: read error !
> vdr kernel: message 0: flags=0x0, addr=0xf, buf=0x7f, len=1
> vdr kernel: message 1: flags=0x1, addr=0xf, buf=0x0, len=1
> vdr kernel: mt352_read_register: readreg error (ret == -121)
> vdr kernel: DVB: registering frontend 0 (Zarlink VP310 DVB-S)...
> vdr kernel: PCI: Found IRQ 12 for device 0000:02:0e.0
> vdr kernel: /root/dvb-kernel/build-2.6/skystar2.c: FlexCopII(rev.130)
> chip found
> vdr kernel: /root/dvb-kernel/build-2.6/skystar2.c: the chip has 6
> hardware filters
> vdr kernel: DVB: registering new adapter (SkyStar2).
> vdr kernel: master_xfer: write error 0 !
> vdr kernel: message 0: flags=0x0, addr=0x68, buf[0]=0x2, len=2
> vdr kernel: master_xfer: read error !
> vdr kernel: message 0: flags=0x0, addr=0x68, buf=0x0, len=1
> vdr kernel: message 1: flags=0x1, addr=0x68, buf=0x0, len=1
> vdr kernel: master_xfer: read error !
> vdr kernel: message 0: flags=0x0, addr=0xf, buf=0x7f, len=1
> vdr kernel: message 1: flags=0x1, addr=0xf, buf=0x0, len=1
> vdr kernel: mt352_read_register: readreg error (ret == -121)
> vdr kernel: DVB: registering frontend 1 (Zarlink VP310 DVB-S)...
>
> thanks a lot! it works! do the error messages have a meaning?

Cool! Ah, the errors are just one of the other drivers being a bit noisy - 
I'll sort that out.




Home | Main Index | Thread Index