[mythtv] Current SVN DVB-S zapping problems (diseqc?)

[Yeasah Pell]

>> Please try this: set the spectral inversion values for your multiplexes
>> (or at least the ones that you are using for testing) to the explicit
>> correct value (instead of auto), and see if it gets any better. (In the
>> db, the inversion field has one of three possible values: '0' for no
>> inversion, '1' for inverted, and 'a' for auto -- anything else,
>> including NULL, gets treated as auto)
>>     
> Setting inversion on two test multiplexes to 0 results in the same error no 
> (LMS) only (l--). Signal does not anymore vary between 20 and 60%. It stays 
> between 33 and 37%.
> Setting inversion to 1 results in mythbackend complaining about discarding PES 
> packets and a mythbackend crash.
>
> So this seems not to be exactly what searching for.
>
>   
The crash is certainly not directly related -- in fact, you've found a 
good way to test out the robustness of the mythtv DVB code to a 
corrupted packet stream: set the spectral inversion setting incorrectly. 
I guess it isn't very robust. :-)

I just noticed that there wasn't any mention of voltage commands in the 
log, and then I realized that the set_voltage command is handled by the 
flexcop layer. That has a debug parameter you can turn on too, but only 
if the module was built with the CONFIG_DVB_B2C2_FLEXCOP_DEBUG option 
turned on.

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