screen resolution configuration inquiry

zero79 · 10-05-2004, 08:04 PM

Hey everybody,

I've got this strange video issue going on. I'm using Sarge with the proprietary NVIDIA driver (if that's relevant).

Basically, I want to change my screen resolution to 640x480 for a game (doom 3!). First of all, i tried the slick "xrandr" tool. I actually have 2 resolutions available via xrandr (if i do "xrandr -q" i get 1024x768 or 512x384 as possible screen options). So, i can do "xrandr -s 512x384" and get a lower res screen; however, i want to go to 640x480, so i did "xrandr -s 640x480" and nothing happened.

If i look in "/etc/X11/XF86Config-4", i have 1024x768, 800x600, and 640x480 as modes for each display depth. So i tried to remove 1024x768 and 800x600 from all depths so that X would be forced to go into 640x480. Upon doing an X restart i'm still at 1024x768 (same result with a reboot).

I even went so far as to do "dpkg-reconfigure xserver-xfree86" and pick 640x480@60Hz as the maximum resolution of my monitor, but on restarting X, i'm still at 1024x768.

So at this point, i am just at a loss. what else can i do to try to get my system to display X at 640x480? thanks so much for your thoughts.

Bruce Hill · 10-05-2004, 08:26 PM

Have you tried Ctrl+Alt+- (minus on the numeric keypad)?

btw - there never has been, or will be, a "flawless" victory ;}

zero79 · 10-05-2004, 08:43 PM

yeah ctrl-alt-plus/minus doesn't do anything. i think that was deprecated with xfree86 4.3 in favor of xrandr.

i've had quite a few flawless victories in mk.

Bruce Hill · 10-05-2004, 09:29 PM

Quote:

Originally posted by zero79
yeah ctrl-alt-plus/minus doesn't do anything. i think that was deprecated with xfree86 4.3 in favor of xrandr.

Deprecated "in favor of xrandr" sounds like a step backwards
for a gui app. So just "apt-get xorg" and be done with it.

Quote:

i've had quite a few flawless victories in mk.

By definition, there cannot possibly be a "flawless victory,"
because victory is "success in a struggle against difficulties or
an obstacle"; and flaw is "an imperfection." Therefore, if there
is no imperfection, you wouldn't have a struggle. And if mk
stands for Mandreck, well, there are quite a number of flaws
in that distro, so you'll have to post somewhere other than LQ
to find a buyer for that one... ;}

zero79 · 10-05-2004, 10:00 PM

it may have just been that the old technique of screen res modification (not xrandr) was deprecated going into xfree86 4.3 and later (including xorg). and thus, if i had more than one working screen res setting, ctrl-alt-plus/minus may work.

mk stands for mortal kombat where it's fairly easy to have a flawless victory; flawless refers to the fact that your opponent caused no damage. it all depends on what context you define flawless in.

anyway, this argument has nothing to do with the thread. i'm running sarge, which doesn't have an xorg package yet. even if it did, i would probably run into the same problem on xorg also. i'm obviously just missing some non-standard config setting on sarge (or possibly the proprietary nvidia driver has hijacked control of screen res settings).

Bruce Hill · 10-05-2004, 10:10 PM

Quote:

Originally posted by zero79
mk stands for mortal kombat where it's fairly easy to have a flawless victory; flawless refers to the fact that your opponent caused no damage. it all depends on what context you define flawless in.

anyway, this argument has nothing to do with the thread. i'm running sarge, which doesn't have an xorg package yet. even if it did, i would probably run into the same problem on xorg also. i'm obviously just missing some non-standard config setting on sarge.

Sorry about the mk comment - I'm not a gamer and missed it,
but what I said wasn't necessary anyway.

Ctrl+Alt+(-/+) works in xorg, and I thought I ran 4.3 of xfree86
before upgrading my system, but that's all gone so I can't check.
It doesn't seem like this would be deprecated for a gui, does it?
Even though Sarge doesn't have xorg, you can get the source.
I think because of the licensing issue, Debian will eventually go
with X.org anyway. But yes, this sounds more something that
isn't configured correctly. I've been reading a lot of posts lately
because my LCD displays fonts badly compared to a CRT, and I
think I've read about this same issue.

If you care to post your /etc/X11/XF86Config-4 file, I believe
that someone could give you a hand...

zero79 · 10-05-2004, 10:13 PM

my XF86Config-4 file is fairly standard, but i will post it here for completeness.

Code:

Section "Files"
	FontPath	"unix/:7100"			# local font server
	# if the local font server has problems, we can fall back on these
	FontPath	"/usr/lib/X11/fonts/misc"
	FontPath	"/usr/lib/X11/fonts/cyrillic"
	FontPath	"/usr/lib/X11/fonts/100dpi/:unscaled"
	FontPath	"/usr/lib/X11/fonts/75dpi/:unscaled"
	FontPath	"/usr/lib/X11/fonts/Type1"
	FontPath	"/usr/lib/X11/fonts/CID"
	FontPath	"/usr/lib/X11/fonts/Speedo"
	FontPath	"/usr/lib/X11/fonts/100dpi"
	FontPath	"/usr/lib/X11/fonts/75dpi"
EndSection
Section "Module"
	Load	"bitmap"
	Load	"dbe"
	Load	"ddc"
	Load	"extmod"
	Load	"freetype"
	Load	"glx"
	Load	"int10"
	Load	"record"
	Load	"speedo"
	Load	"type1"
	Load	"vbe"
EndSection
Section "InputDevice"
	Identifier	"Generic Keyboard"
	Driver		"keyboard"
	Option		"CoreKeyboard"
	Option		"XkbRules"	"xfree86"
	Option		"XkbModel"	"pc104"
	Option		"XkbLayout"	"us"
EndSection
Section "InputDevice"
	Identifier	"Configured Mouse"
	Driver		"mouse"
	Option		"CorePointer"
	Option		"Device"		"/dev/input/mice"
	Option		"Protocol"		"ImPS/2"
	Option		"Emulate3Buttons"	"true"
	Option		"ZAxisMapping"		"4 5"
EndSection
Section "Device"
	Identifier	"NVIDIA Corporation NV34 [GeForce FX 5200]"
	Driver		"nvidia"
EndSection
Section "Monitor"
	Identifier	"Generic Monitor"
	HorizSync	30-57
	VertRefresh	43-72
	Option		"DPMS"
EndSection
Section "Screen"
	Identifier	"Default Screen"
	Device		"NVIDIA Corporation NV34 [GeForce FX 5200]"
	Monitor		"Generic Monitor"
	DefaultDepth	24
	SubSection "Display"
		Depth		1
		Modes		"640x480"
	EndSubSection
	SubSection "Display"
		Depth		4
		Modes		"640x480"
	EndSubSection
	SubSection "Display"
		Depth		8
		Modes		"640x480"
	EndSubSection
	SubSection "Display"
		Depth		15
		Modes		"640x480"
	EndSubSection
	SubSection "Display"
		Depth		16
		Modes		"640x480"
	EndSubSection
	SubSection "Display"
		Depth		24
		Modes		 "640x480"
	EndSubSection
EndSection
Section "ServerLayout"
	Identifier	"Default Layout"
	Screen		"Default Screen"
	InputDevice	"Generic Keyboard"
	InputDevice	"Configured Mouse"
EndSection

omry_y · 10-06-2004, 02:09 AM

you ommited the first few comments from your XF86Config-4 file:

# This file is automatically updated on xserver-xfree86 package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
# cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
# md5sum /etc/X11/XF86Config-4 > /var/lib/xfree86/XF86Config-4.md5sum
# dpkg-reconfigure xserver-xfree86

I am guessing that thats why your "dpkg-reconfigure xserver-xfree86" did nothing.

zero79 · 10-06-2004, 06:20 PM

i followed omry_y's suggestion, and executed the command set suggested in the beginning of the x config file, but i still am only able to run at 1024x768.

however, reading the comment, i take it that it means that by executing those commands the package manager will automatically use the new config with the changes upon an upgrade to xfree86. so i don't think that following those steps will make any difference (except saving me a step (maybe) when xorg rolls into debian).

zero79 · 10-06-2004, 06:37 PM

ok, i've got some more info. it looks like i'm getting a lot of "hsync out of range" messages in "/var/log/XFree86.0.log"

does anyone know how i can find the proper hsync setting for my monitor.

here is the section of the log file with the errors.

Code:

(WW) NVIDIA(0): The user specified HorizSync "28.000-33.000" has been adjusted
(WW) NVIDIA(0):      to "" (the intersection with EDID-specified HorizSync
(WW) NVIDIA(0):      "48.000")
(EE) NVIDIA(0): no HorizSync values remaining
(WW) NVIDIA(0): The user specified VertRefresh "43.000-72.000" has been
(WW) NVIDIA(0):      adjusted to "60.000" (the intersection with
(WW) NVIDIA(0):      EDID-specified VertRefresh "60.000"
(WW) NVIDIA(0): Generic Monitor: Using default hsync range of 48.00-48.00kHz
(II) NVIDIA(0): Generic Monitor: Using vrefresh value of 60.00 Hz
(II) NVIDIA(0): Clock range:  12.00 to 400.00 MHz
(II) NVIDIA(0): Not using default mode "640x350" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x175" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x400" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "720x400" (hsync out of range)
(II) NVIDIA(0): Not using default mode "360x200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "320x240" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "400x300" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1152x864" (hsync out of range)
(II) NVIDIA(0): Not using default mode "576x432" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "832x624" (hsync out of range)
(II) NVIDIA(0): Not using default mode "416x312" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1152x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "576x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using mode "640x480" (no mode of this name)
(**) NVIDIA(0): Validated modes for display device DFP-0:
(**) NVIDIA(0):      Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(**) NVIDIA(0):      Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D)
(II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
(--) NVIDIA(0): Display dimensions: (310, 230) mm
(--) NVIDIA(0): DPI set to (83, 84)

zero79 · 10-06-2004, 07:36 PM

ok, i figured out the problem. X was probing my monitor (asking what resolutions it is capable of displaying), but this display is old and stupid and doesn't conform to the EDID (Extended Display Identification Data) protocol, and basically just wasn't communicating the correct information to X.

so all i needed to do was to get X to ignore the data returned from EDID (it will assume that most resolutions are available by default if it doesn't get the EDID info).

in case anyone else runs into this problem, i'm posting the updated monitor section in "/etc/X11/XF86Config-4"

Code:

Section "Monitor"
	Identifier	"Gateway FPD 1500"
	HorizSync	30-61
	VertRefresh	56-75
	Option		"DPMS"
	Option		"IgnoreEDID" "true"
EndSection