[mythtv-users] nvidia-settings problem & solution
Zach
uid000 at gmail.com
Tue Apr 5 00:06:44 UTC 2005
I don't know if anyone else had this problem, but here's a what I did
to get nvidia-settings to load my config at login:
Most of us have seen the suggestion to use nvidia-settings
--load-config-only & in some sort of login script so that our nvidia
customizations are restored upon login. However my problem was that
it didn't restore the overscan setting for my tvout (and of lesser
importance the flicker filter setting as well).
When i looked at the .nvidia-settings-rc, I noticed that the
nvidia-settings app hadn't written the overscan or flicker filter
setting to it. I don't know if this is a bug or if I just couldn't
figure it out. I do know if I delete .nvidia-settings-rc,
nvidia-settings recreates it next time it is run.
So I manually edited the file--it's syntax is pretty intuitive. I
just copied lines substituting TVOverScan and TVFlickerFilter and
their respective values where appropriate.
For me it ended up being
0/TVOverScan[TV-0]=190
0/TVFlickerFilter[TV-0]=135
I based the syntax upon other similar looking lines.
So now it loads up the overscan setting when I login (remember you
have to use the nvidia-settings --load-config-only & line in some sort
of login script).
One problem remained though: keeping nvidia settings from clobbering
your nvidia-settings-rc file if you ever run it again.
There is more than one way to go about this. I just decided to
restrict the permissions on it. I went over-kill and set ownership to
root:root, with 644 permisions, but leaving ownership alone and
setting permissions to 444 would probably be sufficient. I just
didn't want anything to set the permissions back.
Anyway, hope this is helpful to someone.
Zach
More information about the mythtv-users
mailing list