[mythtv] Current SVN DVB-S zapping problems (diseqc?)
yeasah at schwide.com
Wed Aug 30 18:38:09 UTC 2006
Lukas Kasprowicz wrote:
> Am Dienstag, 29. August 2006 18:45 schrieb Yeasah Pell:
>> Anyway, if you built with that option on, you can set the b2c2-flexcop
>> "debug" module parameter to various levels. 'tuner' (2) would show the
>> voltage command, 'regs' (32) would show the resultant register changes
>> for a voltage command, 'i2c' (4) would show i2c messages, which might be
>> worth trying (though it's probably pretty verbose), 'info' (1) might
>> show some interesting messages -- the others are probably not
>> interesting for this issue. If you want multiple categories, you can add
>> those values together, i.e. tuner + regs would be debug=34
> The only debug output i get is when loading module with debug=2. It looks like
> Aug 30 19:30:14 [kernel] new rd: 208: 00000200
> Aug 30 19:30:14 [kernel] new wr: 308: 1fff5fff
> Aug 30 19:30:14 [kernel] new wr: 208: 00000200
> Aug 30 19:30:14 [kernel] new rd: 310: 00000000
> Aug 30 19:30:14 [kernel] new wr: 310: 00000000
> I can not use debug=32 because i am not able to switch channels with this
> debug mode. The other do not show any messages in kernel log when starting
> backend and switching one channel.
> Would the debug=2 help you?
I guess it's not terribly surprising that debug=32 kills tuning, it
presumably really messes with the timing to log all that, especially if
the logs are getting spit out to the system console, which is pretty
expensive. That's too bad though.
There isn't any line like "polarity/voltage = xxx" in there with
debug=2? You have two skystar v2.6 cards, right? I would have expected
to see those.
More information about the mythtv-dev