[mythtv-users] The nvidia-settings tool and Myth (keeping
overscan right)
Dewey Smolka
dsmolka at gmail.com
Mon Mar 14 13:56:13 UTC 2005
It took me a while to fix the screen size after I upgraded -- I
accidentally lost all my original config files -- but I finally got
the size right by tweaking the mode lines in XF86Config.
Note: This is MythTV 0.17 from Knoppmyth R5V12. I'm using an Nvidia
Geforce 2 with S-video out to the TV only.
Before I added the extra mode lines, Myth would display to the TV at
800x600, leaving about 1" to 1.5" of unused space on the left and
right sides of the screen. With these settings, the display reaches
all the way to the right side of the screen and almost all the way to
the left side without having to monkey around with nvtv or
nvidia-settings.
Here are the relevant lines from XF86Config-4: [I commented out the
DDC-probed settings to prevent the system from going to 800x600. This
may not be a necessary step. The lines that work are the ones under
the "Inserted from gossamer-threads" comment.]
________________________
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "true"
Option "TVStandard" "NTSC-M"
Option "ConnectedMonitor" "TV"
Option "TVOutFormat" "SVIDEO"
Option "NoLogo" "1"
Option "TVOverScan" "0.8"
VendorName "KDS"
ModelName "KDS1983"
HorizSync 30 - 50 # DDC-probed
VertRefresh 60 # DDC-probed
# TV fullscreen mode or DVD fullscreen output.
# 768x576 @ 79 Hz, 50 kHz hsync
ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630
# 768x576 @ 100 Hz, 61.6 kHz hsync
ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
# Inserted from gossamer-threads.com/lists/users/42881#42881
Modeline "720x576/50p" 27.15 720 736 880 896 576 578 579 606 # 27 MHz, 3
0.3 kHz, 50.0 Hz
Modeline "768x576/50p" 29.09 768 792 936 960 576 578 579 606 # 29 MHz, 3
0.3 kHz, 50.0 Hz
Modeline "800x600/50p" 31.60 800 824 968 1000 600 602 603 632 # 32 MHz,
31.6 kHz, 50.0 Hz
Modeline "1024x768/50p" 44.80 1024 1056 1200 1280 768 770 772 808 # 45 M
Hz, 35.0 kHz, 43.3 Hz
Modeline "640x480/50p" 20.20 640 656 800 800 480 482 483 505 # 20 MHz, 2
5.2 kHz, 50.0 Hz
# These are the DDC-probed settings reported by your monitor.
# 1600x1200, 75.0Hz; hfreq=93.75, vfreq=75.00
#ModeLine "1600x1200" 202.50 1600 1664 1856 2160 1200 1201 1204 1250 +
hsync +vsync
# 1280x1024, 85.0Hz; hfreq=91.15, vfreq=85.02
#ModeLine "1280x1024" 157.50 1280 1344 1504 1728 1024 1025 1028 1072 +
hsync +vsync
# 1152x864, 75.0Hz; hfreq=67.50, vfreq=75.00
#ModeLine "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900 +
hsync +vsync
# 1024x768, 85.0Hz; hfreq=68.68, vfreq=85.00
#ModeLine "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 +
hsync +vsync
# 1024x768, 75.0Hz; hfreq=60.02, vfreq=75.03
#ModeLine "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800 +
hsync +vsync
# 1024x768, 70.0Hz; hfreq=56.48, vfreq=70.07
#ModeLine "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 -
hsync -vsync
# 800x600, 85.0Hz; hfreq=53.67, vfreq=85.06
#ModeLine "800x600" 56.25 800 832 896 1048 600 601 604 631 +
hsync +vsync
# 800x600, 75.0Hz; hfreq=46.88, vfreq=75.00
#ModeLine "800x600" 49.50 800 816 896 1056 600 601 604 625 +
hsync +vsync
# 800x600, 72.0Hz; hfreq=48.08, vfreq=72.19
#ModeLine "800x600" 50.00 800 856 976 1040 600 637 643 666 +
hsync +vsync
# 800x600, 60.0Hz; hfreq=37.88, vfreq=60.32
#ModeLine "800x600" 40.00 800 840 968 1056 600 601 605 628 +
hsync +vsync
# 640x480, 85.0Hz; hfreq=43.27, vfreq=85.01
#ModeLine "640x480" 36.00 640 696 752 832 480 481 484 509 -
hsync -vsync
# 640x480, 75.0Hz; hfreq=37.50, vfreq=75.00
#ModeLine "640x480" 31.50 640 656 720 840 480 481 484 500 -
hsync -vsync
# 640x480, 60.0Hz; hfreq=31.47, vfreq=59.94
#ModeLine "640x480" 25.17 640 648 744 784 480 482 484 509 -
hsync -vsync
EndSection
[...]
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 24
SubSection "Display"
Depth [each display subsection]
Modes "640x480"
EndSubSection
___________________________
This has worked well for me, and seems a better solution than loading
tweaks through scripts.
If anyone wnats the full XF86Config-4 file, let me know
On Mon, 14 Mar 2005 13:00:55 +0000, Neil Bird <neil at fnxweb.com> wrote:
> 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
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
>
More information about the mythtv-users
mailing list