[mythtv-users] All working - Need help on TV-OUT please!
mark at onnow.net
mark at onnow.net
Fri Oct 8 12:45:34 UTC 2004
I tried putting in the Device section below, and sure enough the monitor output
stops working, but the TV remains blank. I have verified the physical
connections to the TV and that it is ready to take input.
Any other ideas to try?
Thank you,
Mark
Quoting Pete Cable <petercable at gmail.com>:
> You might try changing the line
>
> Option "TwinView"
>
> to read
>
> Option "TwinView" "1"
>
> just to be sure twinview is enabled. If that doesn't work you could
> temporarily switch twinview off and use only the TV output to verify
> that works. Try the following in your "Device" section:
>
> Section "Device"
> Identifier "VESA Framebuffer"
> Driver "nvidia"
> BoardName "Nvidia FX5200"
> Option "NoLogo" "true"
> Option "NvAGP" "1"
> Option "MetaModes" "800x600,800x600"
> Option "TVStandard" "NTSC-M"
> Option "ConnectedMonitor" "TV"
> Option "TwinView" "0"
> Option "TVOverScan" "0.6"
> Option "TVOutFormat" "SVIDEO"
> Option "DigitalVibrance" "0"
> EndSection
>
> which is more or less what I run....
>
> On Thu, 07 Oct 2004 20:32:36 -0400, Matt Hannan
> <matthew.j.hannan at verizon.net> wrote:
> >
> >
> > mark at onnow.net wrote:
> >
> > >Followed the setup instuctions, and what do you know. MythTV works
> fantastic!
> > >
> > >I have one last issue. I am trying to hook it into my TV via SVIDEO.
> > >Hardware:
> > >32" Sony with Svideo in
> > >ASUS GeForce FX 5200
> > >NVidia drivers 6111 installed and working ( NVidia splash screen too )
> > >Single svideo cable between tvout card and TV.
> > >I want to use the monitor and TV if at all possible.
> > >RedHat FC2.
> > >
> > >The monitor works but nothing on the TV. Is the resolution too high?
> What can
> > >I try? Here is my xorg.conf below. I have tried many setups to no avail.
> I
> > >found this config on a google search. It drives my montor fine, but
> nothing to
> > >the TV.
> > >Help at this point, would be really appreciated.
> > >
> > >cat /etc/X11/xorg.conf
> > ># File generated by xf86config.
> > >
> > >#
> > ># Copyright (c) 1999 by The XFree86 Project, Inc.
> > >#
> > ># Permission is hereby granted, free of charge, to any person obtaining a
> > ># copy of this software and associated documentation files (the
> "Software"),
> > ># to deal in the Software without restriction, including without
> limitation
> > ># the rights to use, copy, modify, merge, publish, distribute,
> sublicense,
> > ># and/or sell copies of the Software, and to permit persons to whom the
> > ># Software is furnished to do so, subject to the following conditions:
> > >#
> > ># The above copyright notice and this permission notice shall be included
> in
> > ># all copies or substantial portions of the Software.
> > >#
> > ># THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
> OR
> > ># IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
> MERCHANTABILITY,
> > ># FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
> SHALL
> > ># THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> LIABILITY,
> > ># WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
> OF
> > ># OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
> > ># SOFTWARE.
> > >#
> > ># Except as contained in this notice, the name of the XFree86 Project
> shall
> > ># not be used in advertising or otherwise to promote the sale, use or
> other
> > ># dealings in this Software without prior written authorization from the
> > ># XFree86 Project.
> > >#
> > >
> > ># **********************************************************************
> > ># Refer to the XF86Config(4/5) man page for details about the format of
> > ># this file.
> > ># **********************************************************************
> > >
> > ># NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the
> vesa
> > ># driver instead of the fbdev driver. Thanks to Kenneth Fanyo who
> pointed
> > ># this out to me. :)
> > >
> > ># This XF86Config file is designed for use with the VESA framebuffer.
> > ># This generic interface should work with nearly all video cards
> > ># (although not every card will support every resolution).
> > >
> > ># With the new driver, it should no longer be required to have frame
> buffer
> > ># support in the kernel, or to run it on the console.
> > >#
> > ># Enjoy! :)
> > ># -- volkerdi at slackware.com
> > >#
> > >
> > ># **********************************************************************
> > ># Module section -- this section is used to specify
> > ># which dynamically loadable modules to load.
> > ># **********************************************************************
> > >#
> > >Section "Module"
> > >
> > ># This loads the DBE extension module.
> > >
> > > Load "dbe" # Double buffer extension
> > >
> > ># This loads the miscellaneous extensions module, and disables
> > ># initialisation of the XFree86-DGA extension within that module.
> > > SubSection "extmod"
> > > Option "omit xfree86-dga" # don't initialise the DGA extension
> > > EndSubSection
> > >
> > ># This loads the font modules
> > > Load "type1"
> > > Load "freetype"
> > > Load "speedo"
> > >
> > ># This loads the GLX module
> > > Load "glx"
> > >
> > >EndSection
> > >
> > ># **********************************************************************
> > ># Files section. This allows default font and rgb paths to be set
> > ># **********************************************************************
> > >
> > >Section "Files"
> > >
> > ># 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.
> > >
> > > RgbPath "/usr/X11R6/lib/X11/rgb"
> > >
> > ># Multiple FontPath entries are allowed (which are concatenated
> together),
> > ># as well as specifying multiple comma-separated entries in one FontPath
> > ># command (or a combination of both methods)
> > >#
> > ># If you don't have a floating point coprocessor and emacs, Mosaic or
> other
> > ># programs take long to start up, try moving the Type1 and Speedo
> directory
> > ># to the end of this list (or comment them out).
> > >#
> > >
> > >
> > ># ModulePath can be used to set a search path for the X server modules.
> > ># The default path is shown here.
> > >
> > ># ModulePath "/usr/X11R6/lib/modules"
> > >
> > > FontPath "/usr/X11R6/lib/X11/fonts/local"
> > > FontPath "/usr/X11R6/lib/X11/fonts/misc"
> > > FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled"
> > > FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
> > > FontPath "/usr/X11R6/lib/X11/fonts/Type1"
> > > FontPath "/usr/X11R6/lib/X11/fonts/CID"
> > > FontPath "/usr/X11R6/lib/X11/fonts/Speedo"
> > > FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
> > > FontPath "/usr/local/share/fonts"
> > > FontPath "/usr/share/fonts"
> > > FontPath "/usr/X11R6/lib/X11/fonts"
> > > FontPath "/usr/share/fonts/default"
> > > FontPath "/usr/X11R6/lib/X11/fonts/TTF"
> > >EndSection
> > >
> > ># **********************************************************************
> > ># Server flags section.
> > ># **********************************************************************
> > >
> > >Section "ServerFlags"
> > >
> > ># Uncomment this to cause a core dump at the spot where a signal is
> > ># received. This may leave the console in an unusable state, but may
> > ># provide a better stack trace in the core dump to aid in debugging
> > >
> > ># Option "NoTrapSignals"
> > >
> > ># Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
> > ># (where n is 1 through 12). This allows clients to receive these key
> > ># events.
> > >
> > ># Option "DontVTSwitch"
> > >
> > ># Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
> > ># This allows clients to receive this key event.
> > >
> > ># Option "DontZap"
> > >
> > ># Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
> > ># sequences. This allows clients to receive these key events.
> > >
> > ># Option "DontZoom"
> > >
> > ># Uncomment this to disable tuning with the xvidtune client. With
> > ># it the client can still run and fetch card and monitor attributes,
> > ># but it will not be allowed to change them. If it tries it will
> > ># receive a protocol error.
> > >
> > ># Option "DisableVidModeExtension"
> > >
> > ># Uncomment this to enable the use of a non-local xvidtune client.
> > >
> > ># Option "AllowNonLocalXvidtune"
> > >
> > ># Uncomment this to disable dynamically modifying the input device
> > ># (mouse and keyboard) settings.
> > >
> > ># Option "DisableModInDev"
> > >
> > ># Uncomment this to enable the use of a non-local client to
> > ># change the keyboard or mouse settings (currently only xset).
> > >
> > ># Option "AllowNonLocalModInDev"
> > >
> > ># Set the basic blanking screen saver timeout.
> > >
> > ># Option "blank time" "10" # 10 minutes
> > >
> > ># Set the DPMS timeouts. These are set here because they are global
> > ># rather than screen-specific. These settings alone don't enable DPMS.
> > ># It is enabled per-screen (or per-monitor), and even then only when
> > ># the driver supports it.
> > >
> > ># Option "standby time" "20"
> > ># Option "suspend time" "30"
> > ># Option "off time" "60"
> > >
> > ># On some platform the server needs to estimate the sizes of PCI
> > ># memory and pio ranges. This is done by assuming that PCI ranges
> > ># don't overlap. Some broken BIOSes tend to set ranges of inactive
> > ># devices wrong. Here one can adjust how aggressive the assumptions
> > ># should be. Default is 0.
> > >
> > ># Option "EstimateSizesAggresively" "0"
> > >
> > >EndSection
> > >
> > ># **********************************************************************
> > ># Input devices
> > ># **********************************************************************
> > >
> > ># **********************************************************************
> > ># Core keyboard's InputDevice section
> > ># **********************************************************************
> > >
> > >Section "InputDevice"
> > >
> > > Identifier "Keyboard1"
> > > Driver "Keyboard"
> > ># For most OSs the protocol can be omitted (it defaults to "Standard").
> > ># When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
> > ># uncomment the following line.
> > >
> > ># Option "Protocol" "Xqueue"
> > >
> > ># Set the keyboard auto repeat parameters. Not all platforms implement
> > ># this.
> > >
> > ># Option "AutoRepeat" "500 5"
> > >
> > ># Specifiy 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 European
> > ># keyboard, you will probably want to use one of:
> > >#
> > ># Option "XkbModel" "pc102"
> > ># Option "XkbModel" "pc105"
> > >#
> > ># If you have a Microsoft Natural keyboard, you can use:
> > >#
> > ># Option "XkbModel" "microsoft"
> > >#
> > ># If you have a US "windows" keyboard you will want:
> > >#
> > ># Option "XkbModel" "pc104"
> > >#
> > ># 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"
> > >
> > >
> > ># These are the default XKB settings for X.Org
> > >#
> > ># Option "XkbRules" "xorg"
> > ># Option "XkbModel" "pc101"
> > ># Option "XkbLayout" "us"
> > ># Option "XkbVariant" ""
> > ># Option "XkbOptions" ""
> > >
> > >EndSection
> > >
> > >
> > ># **********************************************************************
> > ># Core Pointer's InputDevice section
> > ># **********************************************************************
> > >
> > >Section "InputDevice"
> > >
> > ># Identifier and driver
> > >
> > > Identifier "Mouse1"
> > > Driver "mouse"
> > >
> > ># On platforms where PnP mouse detection is supported the following
> > ># protocol setting can be used when using a newer PnP mouse:
> > >
> > ># Option "Protocol" "Auto"
> > >
> > ># The available mouse protocols types that you can set below are:
> > ># Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
> > ># Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
> > ># MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
> > ># ThinkingMouse ThinkingMousePS/2 Xqueue
> > > Option "Protocol" "IMPS/2"
> > >
> > ># The mouse device. The device is normally set to /dev/mouse,
> > ># which is usually a symbolic link to the real device.
> > >
> > ># Option "Device" "/dev/mouse"
> > > Option "Device" "/dev/input/mice"
> > ># Option "Device" "/dev/ttyS0"
> > ># Option "Device" "/dev/ttyS1"
> > >
> > ># When using XQUEUE, comment out the above two lines, and uncomment
> > ># the following line.
> > >
> > ># Option "Protocol" "Xqueue"
> > >
> > ># Baudrate and SampleRate are only for some Logitech mice. In
> > ># almost every case these lines should be omitted.
> > >
> > ># Option "BaudRate" "9600"
> > ># Option "SampleRate" "150"
> > >
> > ># Emulate3Buttons is an option for 2-button Microsoft mice
> > ># Emulate3Timeout is the timeout in milliseconds (default is 50ms)
> > >
> > ># Option "Emulate3Buttons"
> > ># Option "Emulate3Timeout" "50"
> > >
> > ># ChordMiddle is an option for some 3-button Logitech mice
> > >
> > ># Option "ChordMiddle"
> > > Option "ZAxisMapping" "4 5"
> > > Option "Buttons" "5"
> > >EndSection
> > >
> > ># Some examples of extended input devices
> > >
> > ># Section "InputDevice"
> > ># Identifier "spaceball"
> > ># Driver "magellan"
> > ># Option "Device" "/dev/cua0"
> > ># EndSection
> > >#
> > ># Section "InputDevice"
> > ># Identifier "spaceball2"
> > ># Driver "spaceorb"
> > ># Option "Device" "/dev/cua0"
> > ># EndSection
> > >#
> > ># Section "InputDevice"
> > ># Identifier "touchscreen0"
> > ># Driver "microtouch"
> > ># Option "Device" "/dev/ttyS0"
> > ># Option "MinX" "1412"
> > ># Option "MaxX" "15184"
> > ># Option "MinY" "15372"
> > ># Option "MaxY" "1230"
> > ># Option "ScreenNumber" "0"
> > ># Option "ReportingMode" "Scaled"
> > ># Option "ButtonNumber" "1"
> > ># Option "SendCoreEvents"
> > ># EndSection
> > >#
> > ># Section "InputDevice"
> > ># Identifier "touchscreen1"
> > ># Driver "elo2300"
> > ># Option "Device" "/dev/ttyS0"
> > ># Option "MinX" "231"
> > ># Option "MaxX" "3868"
> > ># Option "MinY" "3858"
> > ># Option "MaxY" "272"
> > ># Option "ScreenNumber" "0"
> > ># Option "ReportingMode" "Scaled"
> > ># Option "ButtonThreshold" "17"
> > ># Option "ButtonNumber" "1"
> > ># Option "SendCoreEvents"
> > ># EndSection
> > >
> > ># **********************************************************************
> > ># Monitor section
> > ># **********************************************************************
> > >
> > ># Any number of monitor sections may be present
> > >
> > >Section "Monitor"
> > >
> > > Identifier "My Monitor"
> > >
> > ># HorizSync is in kHz unless units are specified.
> > ># HorizSync may be a comma separated list of discrete values, or a
> > ># comma separated list of ranges of values.
> > ># NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
> > ># USER MANUAL FOR THE CORRECT NUMBERS.
> > >
> > ># HorizSync 31.5 - 50.0
> > >
> > > HorizSync 30-96 # multisync
> > ># HorizSync 31.5, 35.2 # multiple fixed sync frequencies
> > ># HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
> > >
> > ># VertRefresh is in Hz unless units are specified.
> > ># VertRefresh may be a comma separated list of discrete values, or a
> > ># comma separated list of ranges of values.
> > ># NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
> > ># USER MANUAL FOR THE CORRECT NUMBERS.
> > >
> > > VertRefresh 50-160
> > >
> > >EndSection
> > >
> > >
> > ># **********************************************************************
> > ># Graphics device section
> > ># **********************************************************************
> > >
> > ># Any number of graphics device sections may be present
> > >
> > >Section "Device"
> > > Identifier "VESA Framebuffer"
> > > Driver "nvidia"
> > > BoardName "Nvidia FX5200"
> > > Option "TwinView"
> > > Option "SecondMonitorHorizSync" "30-50"
> > > Option "SecondMonitorVertRefresh" "60"
> > > Option "MetaModes" "1280x1024, 800x600"
> > > Option "TwinViewOrientation" "Clone"
> > > Option "ConnectedMonitor" "CRT, TV"
> > > Option "TVStandard" "NTSC-M"
> > > Option "TVOutFormat" "SVIDEO"
> > > #VideoRam 4096
> > > # Insert Clocks lines here if appropriate
> > >EndSection
> > >
> > ># **********************************************************************
> > ># Screen sections
> > ># **********************************************************************
> > >
> > ># Any number of screen sections may be present. Each describes
> > ># the configuration of a single screen. A single specific screen section
> > ># may be specified from the X server command line with the "-screen"
> > ># option.
> > >Section "Screen"
> > > Identifier "Screen 1"
> > > Device "VESA Framebuffer"
> > > Monitor "My Monitor"
> > >
> > ># If your card can handle it, a higher default color depth (like 24 or
> 32)
> > ># is highly recommended.
> > >
> > ># DefaultDepth 8
> > ># DefaultDepth 16
> > > DefaultDepth 24
> > ># DefaultDepth 32
> > >
> > ># "1024x768" is also a conservative usable default resolution. If you
> > ># have a better monitor, feel free to try resolutions such as
> > ># "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
> > ># card/monitor can produce)
> > >
> > > #Subsection "Display"
> > > # Depth 8
> > > # Modes "1024x768" "800x600" "640x480"
> > > #EndSubsection
> > > #Subsection "Display"
> > > # Depth 16
> > > # Modes "1024x768" "800x600" "640x480"
> > > #EndSubsection
> > > Subsection "Display"
> > > Depth 24
> > > Modes "1280x1024" "1024x768" "800x600"
> > > EndSubsection
> > > #Subsection "Display"
> > > # Depth 32
> > > # Modes "1280x1024" "1024x768" "800x600"
> > > #EndSubsection
> > >
> > > SubSection "Display"
> > > Depth 24
> > > Modes "1280x1024, 800x600"
> > > EndSubSection
> > >EndSection
> > >
> > ># **********************************************************************
> > ># ServerLayout sections.
> > ># **********************************************************************
> > >
> > ># Any number of ServerLayout sections may be present. Each describes
> > ># the way multiple screens are organised. A specific ServerLayout
> > ># section may be specified from the X server command line with the
> > ># "-layout" option. In the absence of this, the first section is used.
> > ># When now ServerLayout section is present, the first Screen section
> > ># is used alone.
> > >
> > >Section "ServerLayout"
> > >
> > ># The Identifier line must be present
> > > Identifier "Simple Layout"
> > >
> > ># Each Screen line specifies a Screen section name, and optionally
> > ># the relative position of other screens. The four names after
> > ># primary screen name are the screens to the top, bottom, left and right
> > ># of the primary screen. In this example, screen 2 is located to the
> > ># right of screen 1.
> > >
> > > Screen "Screen 1"
> > >
> > ># Each InputDevice line specifies an InputDevice section name and
> > ># optionally some options to specify the way the device is to be
> > ># used. Those options include "CorePointer", "CoreKeyboard" and
> > ># "SendCoreEvents".
> > >
> > > InputDevice "Mouse1" "CorePointer"
> > > InputDevice "Keyboard1" "CoreKeyboard"
> > >
> > >EndSection
> > >
> > >
> > >----------------------------------------------------------------
> > >This message was sent using IMP, the Internet Messaging Program.
> > >
> > >_______________________________________________
> > >mythtv-users mailing list
> > >mythtv-users at mythtv.org
> > >http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> > >
> > >
> > >
> > You have some issues there.
> > I am not 100% sure what that VESA Frame Buffer stuff is, but you need to
> > specify a new Screen and Display section for the TV. Also, do yourself a
> > favor and enable the Dual-Head via the GUI (not sure what desktop you
> > are using, but it should be near the Control Panel or System Tools).
> > This will make the proper edits to xorg.conf. Just set it up with a
> > generic CRT on the secondary head. This is how I got my TV set working
> > the other night. As a matter of fact, here is the file in all its
> > beat-upon glory:
> >
> > ================================================================
> > # Xorg configuration created by system-config-display
> >
> > Section "ServerLayout"
> > Identifier "Multihead layout"
> > Screen 0 "Screen0" LeftOf "Screen1"
> > # Screen 1 "Screen1" 0 0
> > InputDevice "Mouse0" "CorePointer"
> > InputDevice "Keyboard0" "CoreKeyboard"
> > Option "Xinerama" "off"
> > Option "Clone" "on"
> > 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
> > # the X server to render fonts.
> > RgbPath "/usr/X11R6/lib/X11/rgb"
> > ModulePath "/usr/X11R6/lib/modules/extensions/nvidia"
> > ModulePath "/usr/X11R6/lib/modules/extensions"
> > ModulePath "/usr/X11R6/lib/modules"
> > FontPath "unix/:7100"
> > EndSection
> >
> > Section "Module"
> >
> > Load "v4l"
> > Load "dbe"
> > Load "extmod"
> > Load "fbdevhw"
> > Load "glx"
> > Load "record"
> > Load "freetype"
> > Load "type1"
> > # 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 "kbd"
> > 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"
> >
> > # Option "dpms"
> > Identifier "Monitor1"
> > VendorName "GE"
> > ModelName "Small Ass TV"
> > HorizSync 30.0 - 85.0
> > VertRefresh 50.0 - 160.0
> > EndSection
> >
> > Section "Monitor"
> > Identifier "Monitor0"
> > VendorName "Samsung"
> > ModelName "SyncMaster 955df"
> > HorizSync 30.0 - 85.0
> > VertRefresh 50.0 - 160.0
> > Option "dpms"
> > EndSection
> >
> > Section "Device"
> > Identifier "Videocard0"
> > Driver "nvidia"
> > VendorName "Mad Dog"
> > BoardName "NVIDIA GeForce 4 MX (generic)"
> > Option "IgnoreDisplayDevices" "DFP, TV"
> > Option "RenderAccel" "1"
> > # Option "TVStandard" "NTSC-M"
> > # Option "TVOutFormat" "SVIDEO"
> > # Option "TVOverScan" "0.6"
> > # Option "ConnectedMonitor" "TV"
> > EndSection
> >
> > #Section "Device"
> > # Identifier "Videocard1"
> > # Driver "nvidia"
> > # VendorName "Videocard Vendor"
> > # BoardName "NVIDIA GeForce 4 MX (generic)"
> > # BusID "PCI:3:0:0"
> > # Screen 1
> > #EndSection
> >
> > Section "Screen"
> > Identifier "Screen0"
> > Device "Videocard0"
> > Monitor "Monitor0"
> > DefaultDepth 24
> > SubSection "Display"
> > Viewport 0 0
> > Depth 24
> > Modes "1600x1200" "1400x1050" "1280x1024" "1280x960"
> > "1152x864" "1024x768" "800x600" "640x480"
> > EndSubSection
> > EndSection
> >
> > #Section "Screen"
> > # Identifier "Screen1"
> > # Device "Videocard1"
> > # Monitor "Monitor1"
> > # DefaultDepth 24
> > # SubSection "Display"
> > # Viewport 0 0
> > # Depth 24
> > # Modes "640x480"
> > # EndSubSection
> > #EndSection
> >
> > Section "DRI"
> > Group 0
> > Mode 0666
> > EndSection
> > ===============================================
> >
> > See the first section, "ServerLayout"? That was made when I enabled the
> > Dual-head via the GUI.
> >
> > Also note the Monitor1, Monitor0, Screen1, Screen0, Videocard1 and
> > Videocard0 sections.
> > Believe it or not, if you remove the remark statements "#", this will
> > drive your CRT and TV via S-Video.
> > As always, tho, your mileage may vary.
> >
> > Good luck.
> > Matt
> >
> >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
>
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
More information about the mythtv-users
mailing list