[FC4] Problem mit der Nvidia-Treiber installation --> xorg.conf

[Green Mamba]

Hi,

ich habe den aktuellen Treiber für mein 64 Bit Fedora-Core installiert, und muss jetzt die xorg.conf anpassen. Ich habs so gemacht wie in der Anleitung von NVidia beschrieben. Allerdings bekomm ich damit ein Bild auf dem TV, sogar ein sehr sauberes Bild (das wollte ich immer schon einmal ), allerdings bleibt mein TFT schwarz. Hier mal die aktuelle xorg.conf:

# Xorg configuration created by system-config-display

Section "ServerLayout"
	Identifier     "single head configuration"
	Screen      0  "Screen0" 0 0
	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
# the X server to render fonts.
	RgbPath      "/usr/X11R6/lib/X11/rgb"
	FontPath     "unix/:7100"
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" "de"
	Option	    "XkbVariant" "nodeadkeys"
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   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "LCD Panel 1280x1024"
	HorizSync    31.5 - 67.0
	VertRefresh  50.0 - 75.0
	Option	    "dpms"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "nvidia"
	VendorName  "Videocard vendor"
	BoardName   "NVIDIA GeForce 6800 GT"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "Monitor0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     16
		Modes    "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1280x1024" "1152x864" "1152x768" "1024x768" "800x600" "640x480"
	EndSubSection
EndSection

Section "DRI"
	Group        0
	Mode         0666
EndSection

Kann mir jemand sagen was ich falsch mache?

Viele Grüße,
Mamba

//Edit
Ach ja, noch ne Frage am Rande. Ich hab ja bislang meist mit SuSE garbeitet, dort gabs eine schöne Suit für die Software-Installation. Hier habe ich nichts dergleichen finden können, außer "Hinzufügen und entfernen von Applikationen". Damit kann ich aber nur die Sachen von der DVD installieren. Wenn ich z.B. xmms haben will, komm ich dann nicht drum herum mit ein rpm zu besorgen? Das muss doch bequem über die GUI zu machen sein!?

 

[Bacchisio]

was hast du denn genau verändert?
nv sollte nvidia heißen,load dri sollte auch auskommentiert werden

hast du auch die zusätzlichen Quellen eingetragen? ich glaube das liegt an der Linzenzfrage die in der news angesprochen wurde

 

[Green Mamba]

Args, sorry, hatte glatt die originale hier reingepastet. Jetzt ist die mit den von dir angesprochenen Änderungen drin. Im Prinzip habe ich genau das gemacht was du gesagt hast, deckt sich ja auch mit der Anleitung.
Hardware steht in meiner Sig unter Silicon Valley. Asus A8N SLI Deluxe, und GeForce 6800GT PCIe.

 

[marcelcedric]

Hi,

1.)

Section "Device"
Identifier "Videocard0"
Driver "nv"
VendorName "Videocard vendor"
BoardName "NVIDIA GeForce 6800 GT"
EndSection

Muss das nicht nvidia heißen? Zweitens kannst du mal die Log von Xorg posten, welche in /var/log liegt.

2.) Es wurde ein zweites Repository Namens "Livna" aufgemacht, wo die ganzen extras von FC liegen, da sie nicht mehr auf die CDs pasten und keine extra CD erstellt worden wollte. Einige Pakete auch wegen den Lizenzen.

rpm --ihv http://rpm.livna.org/fedora/4/x86_64/RPMS.lvn/livna-release-4-0.lvn.2.4.noarch.rpm

Und als GUI:

rpm --ihv http://switch.dl.sourceforge.net/sourceforge/yumex/yumex-0.40-1.tla.1.FC4.noarch.rpm

MfG

 

[Bacchisio]

sehe ich das richtig dass du twinview benutzen willst?

in der conf hast du ja nichts diesbezüglich geändert, appendix G in der readme müsste alles erklären

 

[marcelcedric]

X CONFIG TWINVIEW OPTIONS

To enable TwinView, you must specify the following options in the Device
section of your X Config file:

Option "TwinView"
Option "MetaModes" "<list of metamodes>"

You must also specify either:

Option "SecondMonitorHorizSync" "<hsync range(s)>"
Option "SecondMonitorVertRefresh" "<vrefresh range(s)>"

or:

Option "HorizSync" "<hsync range(s)>"
Option "VertRefresh" "<vrefresh range(s)>"

You may also use any of the following options, though they are not required:

Option "TwinViewOrientation" "<relationship of head 1 to head 0>"
Option "ConnectedMonitor" "<list of connected display devices>"

Please see detailed descriptions of each option below.



Detailed Description of Options

TwinView

This option is required to enable TwinView; without it, all other
TwinView related options are ignored.

SecondMonitorHorizSync
SecondMonitorVertRefresh

You specify the constraints of the second monitor through these
options. The values given should follow the same convention as the
"HorizSync" and "VertRefresh" entries in the Monitor section. As the
XF86Config man page explains it: the ranges may be a comma separated
list of distinct values and/or ranges of values, where a range is
given by two distinct values separated by a dash. The HorizSync is
given in kHz, and the VertRefresh is given in Hz. You may, if you
trust your display devices' EDIDs, use the "UseEdidFreqs" option
instead of these options (see Appendix D for a description of the
"UseEdidFreqs" option).

HorizSync
VertRefresh

Which display device is "first" and which is "second" is often
unclear. For this reason, you may use these options instead of the
SecondMonitor versions. With these options, you can specify a
semicolon-separated list of frequency ranges, each optionally
prepended with a display device name. For example:

Option "HorizSync" "CRT-0: 50-110; DFP-0: 40-70"
Option "VertRefresh" "CRT-0: 60-120; DFP-0: 60"

Please see Appendix R on Display Device Names for more information.

MetaModes

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 X config 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 X config 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 (i.e. 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"

Because it is often unclear which mode within a MetaMode will be used
on each display device, mode descriptions within a MetaMode can be
prepended with a display device name. For example:

"CRT-0: 1600x1200, DFP-0: 1024x768"

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.

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.

Because it is often unclear which display device is "first" and which
is "second", TwinViewOrientation can be confusing. You can further
clarify the TwinViewOrientation with display device names to indicate
which display device is positioned relative to which display device.
For example:

"CRT-0 LeftOf DFP-0"



ConnectedMonitor

With this option you can 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 are a
comma-separated list of display device names; for example:

"CRT-0, CRT-1"
"CRT"
"CRT-1, DFP-0"

WARNING: this option overrides what display devices are detected by
the NVIDIA kernel module, and is very seldom needed. You really only
need this if a display device is not detected, either because it does
not provide DDC information, or because it is on the other side of a
KVM (Keyboard-Video-Mouse) switch. In most other cases, it is best not
to specify this option.

Just as in all X config entries, spaces are ignored and all entries are case
insensitive.

Yep, die Optionen fehlen.

MfG

 

[Green Mamba]

Nein, twinview möchte ich nicht unbedingt benutzen. Sollte es aber funktionieren hätte ich natürlich nichts dagegen. Ich möchte einfach nur ein Bild auf meinem Monitor.

@marcel
Ist dein Tip noch aktuell, jetzt wo die neue conf-Datei drin ist? Was genau installiere ich mir denn da von Livna?

 

[marcelcedric]

Nein, twinview möchte ich nicht unbedingt benutzen. Sollte es aber funktionieren hätte ich natürlich nichts dagegen. Ich möchte einfach nur ein Bild auf meinem Monitor.

Poste doch mal die Xorg-Log aus /var/log.

@marcel
Ist dein Tip noch aktuell, jetzt wo die neue conf-Datei drin ist? Was genau installiere ich mir denn da von Livna?

Was meinst du mit "aktuell" und "neue conf-datei"? Du installierst die livna-rpm, um Zugriff auf das Repository zu erlangen. Oder was meinst du?

MfG

 

[Bacchisio]

das hier könnte interessant sein

Why does X crash when starting on Fedora Core 4?

A. There are interaction problems with SELinux (enabled by default on Fedora
Core 4) and the NVIDIA graphics driver. NVIDIA is investigating this, but
it is recommended that you append the kernel boot option "selinux=0" to the
kernel boot line in your grub.conf file. You must reinstall the NVIDIA
driver after adding this option.

 

[Green Mamba]

Ok, eins nach dem anderen. Es ist ja nicht so dass X crashed, aber es bedient halt das falsche Display, nämlich das TV, statt dem normalen Monitor. Ich werde das aber trotzdem mal eintragen.
Hier erstmal die versprochene Xorg.log im Anhang.

 

[Green Mamba]

Soo, ich bin jetzt zu dem allseits verschrieenen SuSE 9.3 zurückgekehrt, und habe dort das gleiche Problem. Im Anhang nochmal die akutelle xorg.conf. Vielleicht kann mir ja jemand helfen. Es funktioniert alles tadellos, nur wenn ich den Rechner mit eingestecktem TV hochfahre, bekomm ich nur ein Bild auf dem TV. Man muss doch irgendwie einstellen können dass er immer den gleichen Ausgang nehmen soll!?

 

[Bacchisio]

den Vorschlag von Tim aus dem irc channel schon getestet ?
http://forums.gentoo.org/viewtopic-...out.html?sid=e7bc69bbca6cf4536edd2a968c00868e

 

[Green Mamba]

Jap, hatte ich wohl vergessen.
Allerdings ist dort von der XF86Config die Rede. Hier gehts um die xorg.conf. Haben beide die gleiche Syntax?

 

[Bacchisio]

da xorg eine weiterentwicklung von xfree ist sollte es gehen
ich würde ein backup machen und ausprobieren, schlechter als jetzt kann es ja nicht funktionieren

 

[Mavado]

Ja, beide haben den gleichen syntax

 

[karuso]

falls das nicht klappt kannste auch mal als root xorgcfg starten, das erstellt dir grafisch den aufbau deiner config und lässt dich diese auch verändern. damit hab ich es damals hinbekommen.

 

[Mavado]

Naj aber FC4 is auch nicht das besze is sehr buggy leider.
FC3 war immer noch besser bzw is immer noch besser

 

[marcelcedric]

Laeuft bei mir eigentlich ganz gut. Merke in letzter Zeit nur, dass es sich oefters verabschiedet, zum Beispiel bei VMWare oder Java, kann aber auch an mir liegen.

MfG