| View previous topic :: View next topic |
| Author |
Message |
tehnick
n00b
Joined: 11 Apr 2005
Posts: 22
|
 Posted: Mon May 30, 2005 4:50 am Post subject: using tv through s-video xorg.conf |
 |
|
I'm trying to get my TV working in X. It's connected through S-Video on the same card as my monitor is on. I get this error:
| Quote: | | (WW)NVIDIA: More than one matching Device section found: Device1 |
This is my xorg.conf:
http://tehnick.ath.cx:50/xorg.conf |
|
| Back to top |
|
 |
chuliomartinez
n00b
Joined: 25 Dec 2004
Posts: 30
Location: Event horizont
|
| Posted: Mon May 30, 2005 1:51 pm Post subject: Leave only one device section! |
|
|
The problem is that you have more than 1 device section. Delete all but the one saying driver:nvidia.
Now if you r primary monitor is on dvi (like some LCD monitors)
then you have TV and DFP (digital flat panel) devices connected. (The order is VERY important). Otherwise
you have CRT, TV.
You only needed one monitor section that describes the FIRST device (eg TV if you have dvi LCD!)
For the SECOND device use
| Code: |
Option "SecondMonitorHorizSync" "30-81" #use your own values!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Option "SecondMonitorVertRefresh" "60"
|
options in the device section.
Then you should configure twinview. You will probably want "clone", eg both devices displaying the same.
For other twinview modes consult the nvidia docs ( eg RTFM:) which you should anyway.
TwinViewOrientation
This option controls the positioning of the second display
device relative to the first within the virtual X screen, when
offsets are not explicitly given in the MetaModes. The possible
values are:
"RightOf" (the default)
"LeftOf"
"Above"
"Below"
"Clone"
When "Clone" is specified, both display devices will be assigned
an offset of 0,0.
| Code: |
Option "TwinView" "on"
Option "TwinViewOrientation" "Clone"
|
Then provide Metamodes.
(Quote from nvidia manual)
A single MetaMode describes what mode should be used on each
display device at a given time. Multiple MetaModes list the
combinations of modes and the sequence in which they should be
used. When the NVIDIA driver tells X what modes are available,
it is really the minimal bounding box of the MetaMode that is
communicated to X, while the "per display device" mode is kept
internal to the NVIDIA driver. In MetaMode syntax, modes within
a MetaMode are comma separated, and multiple MetaModes are
separated by semicolons. For example:
"<mode name 0>, <mode name 1>; <mode name 2>, <mode name 3>"
Where <mode name 0> is the name of the mode to be used on display
device 0 concurrently with <mode name 1> used on display device 1.
A mode switch will then cause <mode name 2> to be used on display
device 0 and <mode name 3> to be used on display device 1. Here
is a real MetaMode entry from the XF86Config sample config file:
Option "MetaModes" "1280x1024,1280x1024; 1024x768,1024x768"
If you want a display device to not be active for a certain
MetaMode, you can use the mode name "NULL", or simply omit the
mode name entirely:
"1600x1200, NULL; NULL, 1024x768"
or
"1600x1200; , 1024x768"
Optionally, mode names can be followed by offset information
to control the positioning of the display devices within the
virtual screen space; e.g.:
"1600x1200 +0+0, 1024x768 +1600+0; ..."
Offset descriptions follow the conventions used in the X
"-geometry" command line option; i.e. both positive and negative
offsets are valid, though negative offsets are only allowed when
a virtual screen size is explicitly given in the XF86Config file.
When no offsets are given for a MetaMode, the offsets will be
computed following the value of the TwinViewOrientation option
(see below). Note that if offsets are given for any one of the
modes in a single MetaMode, then offsets will be expected for
all modes within that single MetaMode; in such a case offsets
will be assumed to be +0+0 when not given.
When not explicitly given, the virtual screen size will be
computed as the the bounding box of all MetaMode bounding boxes.
MetaModes with a bounding box larger than an explicitly given
virtual screen size will be discarded.
A MetaMode string can be further modified with a "Panning Domain"
specification; eg:
"1024x768 @1600x1200, 800x600 @1600x1200"
A panning domain is the area in which a display device's viewport
will be panned to follow the mouse. Panning actually happens on
two levels with TwinView: first, an individual display device's
viewport will be panned within its panning domain, as long as
the viewport is contained by the bounding box of the MetaMode.
Once the mouse leaves the bounding box of the MetaMode, the entire
MetaMode (ie all display devices) will be panned to follow the
mouse within the virtual screen. Note that individual display
devices' panning domains default to being clamped to the position
of the display devices' viewports, thus the default behavior is
just that viewports remain "locked" together and only perform
the second type of panning.
The most beneficial use of panning domains is probably to
eliminate dead areas -- regions of the virtual screen that are
inaccessible due to display devices with different resolutions.
For example:
"1600x1200, 1024x768"
produces an inaccessible region below the 1024x768
display. Specifying a panning domain for the second display
device:
"1600x1200, 1024x768 @1024x1200"
provides access to that dead area by allowing you to pan the
1024x768 viewport up and down in the 1024x1200 panning domain.
Offsets can be used in conjunction with panning domains to
position the panning domains in the virtual screen space (note
that the offset describes the panning domain, and only affects
the viewport in that the viewport must be contained within the
panning domain). For example, the following describes two modes,
each with a panning domain width of 1900 pixels, and the second
display is positioned below the first:
"1600x1200 @1900x1200 +0+0, 1024x768 @1900x768 +0+1200"
If no MetaMode string is specified, then the X driver uses the
modes listed in the relevant "Display" subsection, attempting
to place matching modes on each display device.
ConnectedMonitor
This option allows you to override what the NVIDIA kernel
module detects is connected to your video card. This may be
useful, for example, if any of your display devices do not
support detection using Display Data Channel (DDC) protocols.
Valid values for this option are "CRT" (cathode ray tube), "DFP"
(digital flat panel), or "TV" (television); when using TwinView,
this option may be a comma-separated list of display devices;
e.g.: "CRT, CRT" or "CRT, DFP".
My config:
(I'm using xfs and LCD monitor on dvi, anyway the relevant part is the device section)
| Code: |
# XFree86 4 configuration created by pyxf86config
#Section "DRI"
# Group 0
# Mode 0666
#EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "DevInputMice" "AlwaysCore"
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/lib/X11/rgb"
FontPath "unix/:-1"
EndSection
Section "Module"
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/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "InputDevice"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Identifier "DevInputMice"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "Monitor"
Identifier "Monitor0"
HorizSync 30-50
VertRefresh 60
Option "DPMS"
EndSection
#Section "Monitor"
# VendorName "Monitor Vendor"
# ModelName "Monitor 1024x768"
# HorizSync 30.0 - 81.0
# VertRefresh 56.0 - 75.0
# Option "dpms"
# # 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
# #ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
# # 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
# #ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
#EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "Videocard vendor"
BoardName "NVIDIA GeForce FX (generic)"
# Option "Flatpanel" "true"
# Option "NODDC" "1"
# Option "NoEDID" "1"
Option "NoLogo" "True"
Option "CursorShadow" "True"
Option "RenderAccel" "True"
Option "NvAGP" "1"
Option "TwinView" "on"
Option "SecondMonitorHorizSync" "30-81"
Option "SecondMonitorVertRefresh" "60"
# Option "MetaModes" "1024x768,1024x768", "800x600,800x600", "640x480,640x480"
Option "MetaModes" "1024x768, 1280x1024; 1024x768, 1024x768; 800x600, 800x600; 640x480, 640x480;"
# Option "MetaModes" "1024x768,1024x768"
Option "TwinViewOrientation" "Clone"
Option "TVOutFormat" "COMPOSITE"
Option "TVStandard" "PAL-N"
# Option "SyncToVBlank" "1"
# Option "XVideoTextureSyncToVBlank" "1"
# Option "XVideoBlitterSyncToVBlank" "1"
Option "ConnectedMonitor" "DFP, TV"
# can hurt opnegl apps, but I like shadows
# http://forums.gentoo.org/viewtopic.php?p=1731084
Option "AllowGLXWithComposite" "1"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
#######################################
#Going for shadows:)
######################################
Section "Extensions"
Option "Composite" "Enable"
EndSection
|
_________________
naked&dead |
|
| Back to top |
|
|
tehnick
n00b
Joined: 11 Apr 2005
Posts: 22
|
| Posted: Mon May 30, 2005 6:30 pm Post subject: |
|
|
I followed what you said and I am getting this error now:
| Quote: |
(EE) NVIDIA(0): No modes remaining for display device TV-0
(EE) NVIDIA(0): *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration. |
This is my updated xorg.conf that results in this error:
http://tehnick.ath.cx:50/xorg.conf |
|
| Back to top |
|
|
chuliomartinez
n00b
Joined: 25 Dec 2004
Posts: 30
Location: Event horizont
|
| Posted: Mon May 30, 2005 8:02 pm Post subject: Typo:) |
|
|
It is the other way. In your config:
| Code: |
Option "SecondMonitorHorizSync" "60"
Option "SecondMonitorVertRefresh" "30-60"
|
Should be:
| Code: |
Option "SecondMonitorHorizSync" "30-60
Option "SecondMonitorVertRefresh" "60
|
Does the one monitor setup work, I mean does X start? (eg. TwinView = "0")
If it doesn't help please post the the full xorg log. (it should be /var/log/Xorg.0.log)
PS:
Please try to be more careful. These days it would be very uncommon to damage your hardware with invalid xconfig, but...
_________________
naked&dead |
|
| Back to top |
|
|
tehnick
n00b
Joined: 11 Apr 2005
Posts: 22
|
| Posted: Tue May 31, 2005 12:44 am Post subject: |
|
|
Ah.. I didn't catch that. I fixed it and I am still getting the same results. X does not start but gives the error that I quoted in my last post.
Here is my xorg log:
http://tehnick.ath.cx:50/Xorg.0.log |
|
| Back to top |
|
|
chuliomartinez
n00b
Joined: 25 Dec 2004
Posts: 30
Location: Event horizont
|
| Posted: Tue May 31, 2005 7:42 am Post subject: Bois problem |
|
|
Seems that there is a bios problem from the log. It is however only reported as warning and there are valid modes for the CRT so it might be not important.
The cause of the failure is that there are no modes for the TV found. There is no way (I know of) to force nvidia to use a specific mode for the tv.
Maybe you could try to change the TVStandart and or setting TVOutFormat to COMPOSITE. For my Sony TV it doesn't matter what mode I use it still works ok:). Did you try twinview in Windoze?
o The "TVStandard" option should be added to your screen section; valid
values are:
"PAL-B" : used in Belgium, Denmark, Finland, Germany, Guinea,
Hong Kong, India, Indonesia, Italy, Malaysia, The
Netherlands, Norway, Portugal, Singapore, Spain,
Sweden, and Switzerland
"PAL-D" : used in China and North Korea
"PAL-G" : used in Denmark, Finland, Germany, Italy, Malaysia,
The Netherlands, Norway, Portugal, Spain, Sweden,
and Switzerland
"PAL-H" : used in Belgium
"PAL-I" : used in Hong Kong and The United Kingdom
"PAL-K1" : used in Guinea
"PAL-M" : used in Brazil
"PAL-N" : used in France, Paraguay, and Uruguay
"PAL-NC" : used in Argentina
"NTSC-J" : used in Japan
"NTSC-M" : used in Canada, Chile, Colombia, Costa Rica, Ecuador,
Haiti, Honduras, Mexico, Panama, Puerto Rico, South
Korea, Taiwan, United States of America, and Venezuela
"HD480i" : 480 line interlaced
"HD480p" : 480 line progressive
"HD720p" : 720 line progressive
"HD1080i": 1080 line interlaced
"HD1080p": 1080 line progressive
"HD576i" : 576 line interlace
"HD576p" : 576 line progressive
The line in your X config file should be something like:
Option "TVStandard" "NTSC-M"
If you do not specify a TVStandard, or you specify an invalid value,
the default "NTSC-M" will be used. Note: if your country is not in
the above list, select the country closest to your location.
_________________
naked&dead |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
