[linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping
vnonas at otenet.gr
Sat Feb 23 13:35:49 CET 2008
Just replying to myself.
Nobody has the same problems that I have with Skystar HD? Can someone
please explain the current status of the driver? Is this the expected
behavior, or I am doing something wrong?
NONAS EUAGGELOS wrote:
> I have a Skystar HD. I use multiproto from here (checked it out yesterday):
> It compiles fine, all needed modules are loaded automatically upon boot.
> This is my dmesg:
> saa7146: found saa7146 @ mem f88f2000 (revision 1, irq 21) (0x13c2,0x1019).
> saa7146 (0): dma buffer size 192512
> DVB: registering new adapter (TT-Budget S2-3200 PCI)
> adapter has MAC addr = 00:d0:5c:67:dd:91
> input: Budget-CI dvb ir receiver saa7146 (0) as /class/input/input3
> stb0899_write_regs [0xf1b6]: 02
> stb0899_write_regs [0xf1c2]: 00
> stb0899_write_regs [0xf1c3]: 00
> _stb0899_read_reg: Reg=[0xf000], data=82
> stb0899_get_dev_id: ID reg=[0x82]
> stb0899_get_dev_id: Device ID=, Release=
> _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x00000400], Offset=[0xf334], Data=[0x444d4431]
> _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x00000400], Offset=[0xf33c], Data=[0x00000001]
> stb0899_get_dev_id: Demodulator Core ID=[DMD1], Version=
> _stb0899_read_s2reg Device=[0xfafc], Base address=[0x00000800], Offset=[0xfa2c], Data=[0x46454331]
> _stb0899_read_s2reg Device=[0xfafc], Base address=[0x00000800], Offset=[0xfa34], Data=[0x00000001]
> stb0899_get_dev_id: FEC Core ID=[FEC1], Version=
> stb0899_attach: Attaching STB0899
> stb6100_attach: Attaching STB6100
> DVB: registering frontend 0 (STB0899 Multistandard)...
> I use scan from here:
> It does not compile, I use the binary I found in the archive.
> I use szap2 from here:
> It does compile.
> My kernel is:
> My problems are:
> - When I scan the same transponder more than once, sometimes I get some services, sometimes I get no services.
> - When I zap (with szap2) to a station more than once, sometimes I get a lock, sometimes I get no lock.
> - I have also tried with vdr 1.4.7(old DVB API) and 1.5.14 (new dvb API). Both versions can tune to only one channel, the "Active" channel from previous vdr shutdown. When you change channel the signal is lost. I suppose it relates to the zap problem.
> I would appreciate your help / suggestions.
> Thank you very much.
> linux-dvb mailing list
> linux-dvb at linuxtv.org
More information about the linux-dvb