Gnome Screen Resolution doesn't match X11/xorg.conf

yitzle · 02-18-2008, 10:07 PM

Distro: Debian Etch.
Select parts of /etc/X11/xorg.conf (I don't think I removed anything pertinent)

Code:

Section "Module"
	Load	"bitmap"
	Load	"ddc"
	Load	"dri"
	Load	"extmod"
	Load	"freetype"
	Load	"glx"
	Load	"int10"
	Load	"vbe"
EndSection

Section "Device"
	Identifier	"Intel Corporation 82945G/GZ Integrated Graphics Controller"
	Driver		"i810"
	BusID		"PCI:0:2:0"
EndSection

Section "Monitor"
	Identifier	"Nokia 446Xt"
	Option		"DPMS"
	HorizSync	30-68
	VertRefresh	50-85
EndSection

Section "Screen"
	Identifier	"Default Screen"
	Device		"Intel Corporation 82945G/GZ Integrated Graphics Controller"
	Monitor		"Nokia 446Xt"
	DefaultDepth	24
	SubSection "Display"
		Depth		24
		Modes		"1600x1200" "1280x960" "1280x1024" "1024x768"
	EndSubSection
EndSection

Section "ServerLayout"
	Identifier	"Default Layout"
	Screen		"Default Screen"
	InputDevice	"Generic Keyboard"
	InputDevice	"Configured Mouse"
EndSection

Section "DRI"
	Mode	0666
EndSection

Gnome's "Screen Resolution Preferences" app offers me 1280x1024 and 1024x768.

gconf-editor: /desktop/gnome/screen/debian/0 has resolution="1280x960"

Why don't they match up? How do I get 1600x1200?

danlee · 02-19-2008, 10:15 AM

Just a thought, but what happens if you remove the other resolutions and only leave the "1600x1200" ?

Make sure you have a backup first.

Code:

cp /etc/X11/xorg.conf /etc/X11/xorg.conf.backup

Run in bash to restore it if it doesn't work.

Code:

rm -f /etc/X11/xorg.conf
cp /etc/X11/xorg.conf.backup /etc/X11/xorg.conf

johnsfine · 02-19-2008, 11:00 AM

With some drivers /var/log/Xorg.0.log gives a fairly clear description of why certain display modes were rejected. It's worth checking.

Quote:

HorizSync 30-68

That maximum horizontal rate of 68 is rather low for a resolution with 1200 scan lines. It isn't impossibly low, but it is low enough that if you convinced the system to do 1600x1200 at 68 or lower HorizSync you wouldn't like the results.

If your monitor can do a decent job displaying 1600x1200 it's correct maximum HorizSync is probably higher than 68.

Quote:

Option "DPMS"

I think that tells the driver to ask the monitor for various information, such as HorizSync. But if you also tell it the HorizSync, I'm not sure which wins. I think I solved some similar problems by temporarily removing the HorizSync line, forcing it to really use DPMS. But once that fixed the problem, I didn't want to leave it that way (because it requires the monitor to be on everytime X starts) so I found the correct HorizSync in /var/log/Xorg.0.log when using DPMS and edited it back into xorg.conf

yitzle · 02-19-2008, 11:19 AM

Quote:

Originally Posted by danlee

Just a thought, but what happens if you remove the other resolutions and only leave the "1600x1200" ?

Make sure you have a backup first.

Code:

cp /etc/X11/xorg.conf /etc/X11/xorg.conf.backup

Run in bash to restore it if it doesn't work.

Code:

rm -f /etc/X11/xorg.conf
cp /etc/X11/xorg.conf.backup /etc/X11/xorg.conf

Code:

Section "Screen"
        Identifier      "Default Screen"
        Device          "Intel Corporation 82945G/GZ Integrated Graphics Controller"
        Monitor         "Nokia 446Xt"
        DefaultDepth    24
        SubSection "Display"
                Depth           24
                Modes           "1600x1200"
        EndSubSection
EndSection

Gnome's "Screen Resolution Preferences" app now offers:
1280x1024, 1024x768, 800x600, 640*480
Where do those come from?

yitzle · 02-19-2008, 11:34 AM

/var/log/Xorg.0.log

Code:

(II) I810(0): VESA VBE DDC supported
(II) I810(0): VESA VBE DDC Level 2
(II) I810(0): VESA VBE DDC transfer in appr. 1 sec.
(II) I810(0): VESA VBE DDC read failed
(II) I810(0): Will use BIOS call 0x5f05 to set refresh rates for CRTs.
(--) I810(0): Maximum space available for video modes: 12288 kByte
Mode: 30 (640x480)
        ModeAttributes: 0x9b
        ...
...Mode...
...
Mode: 3a (1600x1200)
Mode: 4b (1600x1200)

...
Mode: 68 (0x0)
        ModeAttributes: 0x0
        WinAAttributes: 0x0
        ...
(II) I810(0): Nokia 446Xt: Using hsync range of 30.00-68.00 kHz
(II) I810(0): Nokia 446Xt: Using vrefresh range of 50.00-85.00 Hz
(II) I810(0): Not using mode "1600x1200" (no mode of this name)
(II) I810(0): Increasing the scanline pitch to allow tiling mode (1280 -> 2048).(--) I810(0): Virtual size is 1280x1024 (pitch 2048)
(**) I810(0):  Built-in mode "1280x1024"
(**) I810(0):  Built-in mode "1024x768"
(**) I810(0):  Built-in mode "800x600"
(**) I810(0):  Built-in mode "640x480"
(II) I810(0): Attempting to use 60.02Hz refresh for mode "1280x1024" (858)
(II) I810(0): Attempting to use 85.00Hz refresh for mode "1024x768" (854)
(II) I810(0): Attempting to use 85.14Hz refresh for mode "800x600" (852)
(II) I810(0): Attempting to use 85.01Hz refresh for mode "640x480" (850)
(++) I810(0): DPI set to (96, 96)

DPMS is enabled later on.

Well, there is the culprit. The video driver says, 'Not using mode "1600x1200" (no mode of this name)' and procedes to pick its own built-in modes. Except it has 1600x1200 modes. I'll try setting the /etc/X11/xorg.conf mode to "3a", "4b" etc and see if it works...

What is needed to restart X11? If it sufficient to make a new login? Or do I need to restart GDM? Or reboot the entire system?

yitzle · 02-19-2008, 11:41 AM

Code:

(II) I810(0): Not using mode "3a" (no mode of this name)
(II) I810(0): Not using mode "4b" (no mode of this name)
(II) I810(0): Not using mode "1600x1200" (no mode of this name)

What's it want from me?

johnsfine · 02-19-2008, 12:31 PM

Quote:

Originally Posted by yitzle

(II) I810(0): Not using mode "1600x1200" (no mode of this name)

If we really believe that message (as opposed to some other misconfiguration makes it think there is no mode of that name) then you need to provide a modeline in the xorg.conf file. There are lots of other threads discussing how to do that, but I don't have URLs handy. (Adding a modeline in xorg.conf is the most effective and flexible solution even if the message is wrong and some simpler method would work).

There are a few utility programs for constructing modelines. The one whose name I remember is xvidtune. I could never get the TEST button in xvidtune to work and for my intended purpose it was useless without the TEST button. But xvidtune can write modelines out to the terminal session from which it was launched (it is a GUI program, but seems to be intended to be launched from a terminal session in GUI mode, unless I misunderstood something).
One of the other modeline generating programs might be more appropriate, but I forget the names.

However, I think you should fix that maximum horizontal sync value first, or it will interfere with anything else you try.

Regardless of whether you force a modeline in xorg.conf or it finds a modeline, that modeline is still constrained by that low maximum sync.

yitzle · 02-19-2008, 11:00 PM

xvidtuner says (when I hit test) "Sorry: You have requested a mode-line\nThat is not possible, or not supported by your hardware configuration"

Where in the xorg.conf file do I stick a modeline?

HowDoIProgramIt · 02-19-2008, 11:42 PM

Quote:

Originally Posted by yitzle

xvidtuner says (when I hit test) "Sorry: You have requested a mode-line\nThat is not possible, or not supported by your hardware configuration"

Where in the xorg.conf file do I stick a modeline?

In the "Monitor" section of xorg.conf. On my system, "man xorg.conf" is actually pretty thorough. I like Etch but have never found setting up / getting all of the man pages together to be easy; here's the skinny on ModeLine, shamelessly copied from 'man xorg.conf':

"ModeLine "name" mode-description
This entry is a more compact version of the Mode entry, and it also
can be used to specify video modes for the monitor. is a single
line format for specifying video modes. In most cases this isn’t
necessary because the built-in set of VESA standard modes will be
sufficient.

The mode-description is in four sections, the first three of which
are mandatory. The first is the dot (pixel) clock. This is a sin-
gle number specifying the pixel clock rate for the mode in MHz.
The second section is a list of four numbers specifying the hori-
zontal timings. These numbers are the hdisp, hsyncstart, hsyncend,
and htotal values. The third section is a list of four numbers
specifying the vertical timings. These numbers are the vdisp,
vsyncstart, vsyncend, and vtotal values. The final section is a
list of flags specifying other characteristics of the mode. Inter-
lace indicates that the mode is interlaced. DoubleScan indicates a
mode where each scanline is doubled. +HSync and -HSync can be used
to select the polarity of the HSync signal. +VSync and -VSync can
be used to select the polarity of the VSync signal. Composite can
be used to specify composite sync on hardware where this is sup-
ported. Additionally, on some hardware, +CSync and -CSync may be
used to select the composite sync polarity. The HSkew and VScan
options mentioned above in the Modes entry description can also be
used here."

Good luck with it; sounds like it's put you through the mill...

- Larry

fossilet · 03-13-2011, 09:38 PM

Quote:

Originally Posted by yitzle

Gnome's "Screen Resolution Preferences" app now offers:
1280x1024, 1024x768, 800x600, 640*480
Where do those come from?

Hey,

I am just puzzling the same thing. I have to use

Code:

 
# find /etc -type f -print0 |xargs -0 grep -R 1280

and find they are in /etc/gnome-settings-daemon/xrandr/monitors.xml.
I am using 2.30.2. I do not know if this applies to your GNOME version.

fossilet · 03-13-2011, 11:13 PM

Update:

I was not correct. The modes GNOME gives to your actually comes from xrandr. It seems GNOME gets them on the fly not from any configuration files. You may use xrandr to display available modes which are exactly the same with what GNOME gives us:

tux@dell:~$ xrandr
Screen 0: minimum 320 x 200, current 2390 x 768, maximum 8192 x 8192
VGA1 connected 1024x768+1366+0 (normal left inverted right x axis y axis) 306mm x 230mm
1280x1024 60.0
1280x960 60.0
1152x864 75.0
1024x768 85.0* 75.1 70.1 60.0
832x624 74.6
800x600 100.0 85.1 72.2 75.0 60.3
640x480 100.0 85.0 72.8 75.0 60.0
720x400 70.1
640x350 70.1
LVDS1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
1366x768 60.0*+
1360x768 59.8 60.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
DP1 disconnected (normal left inverted right x axis y axis)

EDDY1 · 03-14-2011, 03:03 AM

ou do realize this post is over 3years old?

fossilet · 03-15-2011, 12:20 PM

Yes. But is is really cryptic to find where GNOME get the available resolutions. I was having the same problem as yitzle and Google lead me here. Hope my reply will be of help to future googlers.