| View previous topic :: View next topic |
| Author |
Message |
joefish
Guru
Joined: 27 Jan 2004
Posts: 316
Location: New Zealand
|
 Posted: Tue Mar 10, 2009 7:12 am Post subject: [solved] Xorg resolution after upgrade to 1.5.3-r3 |
 |
|
I've been setting up a new drive with a new install (so hardware is exactly the same as before), but am having problems with my screen resolution with a switch to xorg-server-1.5.3-r3 (can't remember the exact version I was using before, but whatever was marked as stable on amd64).
X starts without any problems, but my resolution looks like it's about 1024x768. or maybe even 800x600, which is a problem on my 1440x900 screen!
Here is my mostly unchanged xorg.conf:
| Code: |
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" RightOf "Screen1"
Screen 0 "Screen1" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
#Section "Files"
# RgbPath "/usr/lib64/X11/rgb"
#EndSection
Section "Module"
Load "dbe"
Load "extmod"
# Load "type1"
# Load "freetype"
Load "glx"
EndSection
Section "ServerFlags"
Option "Xinerama" "0"
Option "AllowEmptyInput" "off"
EndSection
Section "InputDevice"
# generated from data in "/etc/conf.d/gpm"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Compaq CPQ TFT5015"
HorizSync 31.0 - 61.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor1"
VendorName "Unknown"
ModelName "LCD-MONITOR"
HorizSync 30.0 - 82.0
VertRefresh 56.0 - 76.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7300 SE/7200 GS"
BusID "PCI:4:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Videocard1"
Driver "vesa"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7300 SE/7200 GS"
BusID "PCI:4:0:0"
Screen 0
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "CRT: 1024x768 +0+0; CRT: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Videocard1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "DFP: 1440x900 +0+0"
SubSection "Display"
Modes "1440x900@60"
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
|
At first I thought it might be getting confused between monitors somehow, but I commented out all the stuff for the smaller monitor (which I'm not actually using), however this didn't help.
Do I have to add some kind of config option to specify the resolution? I never had to before... (and I wouldn't know what to add for this setup[/quote][/code], to be honest).
Thanks.
Last edited by joefish on Wed Mar 11, 2009 12:11 am; edited 1 time in total |
|
| Back to top |
|
 |
Malvineous
Apprentice
Joined: 20 Oct 2006
Posts: 281
Location: Brisbane, Australia
|
| Posted: Tue Mar 10, 2009 10:15 am Post subject: Re: Xorg resolution after upgrade to 1.5.3-r3 |
|
|
| joefish wrote: |
| Code: |
Section "ServerLayout"
...
Screen 0 "Screen0" RightOf "Screen1"
Screen 0 "Screen1" 0 0
...
EndSection
Section "Screen"
...
Option "metamodes" "CRT: 1024x768 +0+0; CRT: nvidia-auto-select +0+0"
...
EndSection
Section "Screen"
...
Option "metamodes" "DFP: 1440x900 +0+0"
...
EndSection
|
|
You're telling the driver that screen 0 is the first monitor, then you're telling it "no wait, screen 0 is the other monitor" - why do you have two monitors listed as screen 0? One should be screen 0 and the other should be screen 1.
I'd be willing to bet that it's deciding to use the 1024x768 screen as #0 when presumably you want that as screen #1. |
|
| Back to top |
|
|
joefish
Guru
Joined: 27 Jan 2004
Posts: 316
Location: New Zealand
|
| Posted: Wed Mar 11, 2009 12:10 am Post subject: |
|
|
| Ahh, I was playing around with driver stuff. Changing the driver back to nvidia solved the problem. |
|
| 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
