[mythtv-users] The nvidia-settings tool and Myth (keeping overscan
right)
Neil Bird
neil at fnxweb.com
Mon Mar 14 13:00:55 UTC 2005
Around about 08/03/05 17:21, Jim Oltman typed ...
> For me, this isn't a solution. When I reboot my machine with a
> different OVERSCAN setting, it actually takes on the screen with the
> SHOW/HIDE DETAILS because that fills in the entire screen just like I
> want. When it goes into KDE, it doesn't keep that overscan. This is
> confusing to me because I thought that in the SHO/HIDE details screen,
> X has already been started. Am I missing something?
I've noticed that X/nvidia-drivers occasional reset such things as
the overscan, and if this happens, nvdia-settings only re-asserts this
if it *thinks* the value's changed (hence running that doesn't do
anything as the last formally applied setting is the correct one).
<Alt-Ctrl-F1> console swapping does it, e.g.
My workaround is that I have mythfrontend in a loop in my auto-start
script (so if it crashes it auto-restarts unless I've 'touch'ed
/tmp/myth.die).
I've also saved an alternate .nvidia-setttings file with a subtly
different overscan bvalue, and in the re-run loop, I call
nvidia-settings twice in succession (once with the alt. file, once with
the real one) before mythfrontend.
This causes a minor jiggle, but at least it auto-fixes it if it's
gone wrong. That plus the 'power off' fix [kills/starts the front-end]
from Jarod's site means it's quite easy to get around.
You could always irxec a script to do just nvidia-settings if you've
a spare button.
--
[neil at fnx ~]# rm -f .signature
[neil at fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil at fnx ~]# exit
More information about the mythtv-users
mailing list