[mythtv-users] xorg.conf example for TV
Warren
warren-lists at icruise.com
Fri Mar 24 15:57:10 UTC 2006
awrobinson at nc.rr.com wrote:
> Since I asked, I thought I should post the answer. Here is the xorg.conf
> file that allowed me to see MythTV on my TV. The video card is an nVidia
> 5200 with a VGA and an S-Video connector. The TV is the main screen on
> the right. The monitor is a secondary screen on the left. There was some
> trial and error involved as the X server would fail, I'd look through
> the log to see if it gave me a clue as to why, I would remove or comment
> out what appeared to be the offending feature, then try to start X
> server again.
>
> There are still two, uh, issues I could use help with.
>
> 1. The active area on the TV is not square. It looks like a
> parallelogram, with the left-hand corners lower than the corresponding
> right-hand corners. At first I thought it might be a sign of interlacing
> problems, but the picture is otherwise clean with no flickering. This is
> a very old TV and I am running the signal through an S-Video to RF
> converter, so I cannot swear the problem is with the Linux box. Anyone
> have any ideas of what might cause this?
>
> 2. The active area on the TV is a letterbox, with considerable blank
> area at the top and bottom of the screen. I assume this is a result of
> the resolution of the display, which I think is 800x600 at the moment.
> Anyone know a resolution better suited to an old 19 inch analog TV?
>
> Thanks!
>
> Andrew Robinson
>
>
>
> # XFree86 4 configuration garnered from the MythTV-Users mailing list
>
> Section "ServerLayout"
> Identifier "Default Layout"
> Screen 0 "Screen TV"
> Screen 1 "Screen CRT" LeftOf "Screen TV"
> InputDevice "Mouse0" "CorePointer"
> InputDevice "Keyboard0" "CoreKeyboard"
> EndSection
>
> Section "Files"
>
> # RgbPath is the location of the RGB database. Note, this is the name
> of the # file minus the extension (like ".txt" or ".db"). There is
> normally # no need to change the default.
> # Multiple FontPath entries are allowed (they are concatenated together)
> # By default, Red Hat 6.0 and later now use a font server independent of
> FontPath "unix/:7100"
> RgbPath "/usr/X11R6/lib/X11/rgb"
> ModulePath "/usr/X11R6/lib64/modules/extensions/nvidia"
> ModulePath "/usr/X11R6/lib64/modules/extensions"
> ModulePath "/usr/X11R6/lib64/modules"
> FontPath "unix/:7100"
> EndSection
>
> Section "Module"
> Load "dbe"
> Load "extmod"
> Load "fbdevhw"
> Load "glx"
> Load "record"
> Load "freetype"
> Load "type1"
> Load "v4l"
> Load "dri"
> EndSection
>
> Section "InputDevice"
> # Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
> # Option "Xleds" "1 2 3"
> # To disable the XKEYBOARD extension, uncomment XkbDisable.
> # Option "XkbDisable"
> # To customise the XKB settings to suit your keyboard, modify the #
> lines below (which are the defaults). For example, for a non-U.S.
> # keyboard, you will probably want to use:
> # Option "XkbModel" "pc102"
> # If you have a US Microsoft Natural keyboard, you can use:
> # Option "XkbModel" "microsoft"
> #
> # Then to change the language, change the Layout setting.
> # For example, a german layout can be obtained with:
> # Option "XkbLayout" "de"
> # or:
> # Option "XkbLayout" "de"
> # Option "XkbVariant" "nodeadkeys"
> # If you'd like to switch the positions of your capslock and # control
> keys, use:
> # Option "XkbOptions" "ctrl:swapcaps"
> # Or if you just want both to be control, use:
> # Option "XkbOptions" "ctrl:nocaps"
> #
> Identifier "Keyboard0"
> Driver "keyboard"
> Option "XkbRules" "xfree86"
> Option "XkbModel" "pc105"
> Option "XkbLayout" "us"
> EndSection
>
> Section "InputDevice"
> Identifier "Mouse0"
> Driver "mouse"
> Option "Protocol" "IMPS/2"
> Option "Device" "/dev/input/mice"
> Option "ZAxisMapping" "4 5"
> Option "Emulate3Buttons" "yes"
> EndSection
>
> Section "Monitor"
> Identifier "CRT"
> VendorName "Monitor Vendor"
> ModelName "Optiquest Q41"
> HorizSync 30.0 - 48.0
> VertRefresh 50.0 - 90.0
> Option "dpms"
> EndSection
>
> Section "Monitor"
> Identifier "TV"
> VendorName "Monitor Vendor"
> ModelName "Sony TV"
> HorizSync 30 - 50
> VertRefresh 60
> Option "dpms"
> EndSection
>
> Section "Device"
> Identifier "nvidia TV"
> Driver "nvidia"
> BusId "PCI:1:0:0"
> VendorName "Videocard vendor"
> Option "ConnectedMonitor" "TV"
> Option "TVStandard" "NTSC-M"
> Option "TVOutFormat" "SVIDEO"
> Option "NvAgp" "1"
> Option "TVOverScan" "1.0"
> Screen 0
> EndSection
>
> Section "Device"
> Identifier "nvidia CRT"
> Driver "nvidia"
> BusId "PCI:1:0:0"
> VendorName "Videocard vendor"
> Option "ConnectedMonitor" "CRT"
> Screen 1
> EndSection
>
> Section "Screen"
> Identifier "Screen CRT"
> Device "nvidia CRT"
> Monitor "CRT"
> DefaultDepth 24
> SubSection "Display"
> Viewport 0 0
> Depth 16
> Modes "800x600" "640x480"
> EndSubSection
> SubSection "Display"
> Viewport 0 0
> Depth 24
> Modes "1152x864" "1024x768" "800x600" "640x480"
> EndSubSection
> EndSection
>
> Section "Screen"
> Identifier "Screen TV"
> Device "nvidia TV"
> Monitor "TV"
> DefaultDepth 24
> SubSection "Display"
> Viewport 0 0
> Depth 24
> Modes "800x600" "640x480"
> EndSubSection
> EndSection
>
> Section "DRI"
> Group 0
> Mode 0666
> EndSection
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
You do not show a modeline here. If you could find the modeline being
used from the log file, perhaps that can be tuned by changing the
numbers to increase the height of the image.
W
More information about the mythtv-users
mailing list