LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   X resolution uses highest possible even if lower stated in xorg.conf (https://www.linuxquestions.org/questions/linux-software-2/x-resolution-uses-highest-possible-even-if-lower-stated-in-xorg-conf-596035/)

terfy 10-31-2007 05:24 AM

X resolution uses highest possible even if lower stated in xorg.conf
 
hi.

my X is running highest resolution 2048x1536 in 60hz, even if my xorg.conf is set like this:


Section "Monitor"
Identifier "Flatron F900P"
HorizSync 30-111
VertRefresh 50-200
EndSection

Section "Screen"
Identifier "Screen 1"
Device "GeForce 7600gs"
Monitor "Flatron F900P"
DefaultDepth 24

Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection

Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection

Subsection "Display"
Depth 24
Modes "1600x1200"
ViewPort 0 0
EndSubsection
EndSection
it should result in 24bit 1600x1200 right ??? it does use 2048x1536#60 (it works fine, but I want to use 1600x1200#85, and I know my monitor can do it, Ive done it before in other OS.
and HorizSync 30-111, VertRefresh 50-200 is good, as I always use it from the monitor manual specs

So what to do, can anyone help me ??
thx in advance

jlinkels 10-31-2007 06:16 AM

Check /var/log/Xorg.0.log

It tells you why X takes certain decisions. Check also in that log file WHICH xorg.conf is used. It is one of the most commmon pitfalls that X uses a different xorg.org than you think it uses.

jlinkels

Wim Sturkenboom 10-31-2007 08:06 AM

You can add Option "UseEdid" "False" to the device section.

terfy 11-01-2007 08:58 PM

Option "UseEdid" "False" to the device section does not help..
it helps me not choosing the high res, but if only 1600x1200 is stated in xorg.conf, then X crashes and I have to change my xorg.conf again..

I get used to this high res now.. its just a shame the sync isnt that fast as in 1600x1200 (60vs85)...

But... I like to get it to work with 1600x1200 also..
I have no clue what to do..

in this xorgconfig utility I can choose from some resolutions, I can choose 1600x1200 which I cannot run, and I cannot choose the high 2048x1536 which I CAN run.. even if its not supposed to in my xorg.conf

this sux actually..

can anyone help me getting this fixed ??

jlinkels 11-01-2007 09:14 PM

Well, I asked you to take a look at /var/log/Xorg.0.log. Can you do that and find out where the decision is made to use that resolution?

jlinkels

terfy 11-03-2007 11:14 AM

oki..


Quote:

(II) VESA(0): Total Memory: 4096 64KB banks (262144kB)
(II) VESA(0): Flatron F900P: Using hsync range of 30.00-111.00 kHz
(II) VESA(0): Flatron F900P: Using vrefresh range of 50.00-200.00 Hz
(II) VESA(0): Not using mode "1600x1200" (no mode of this name)
(--) VESA(0): Virtual size is 2048x1536 (pitch 2048)
(**) VESA(0): Built-in mode "2048x1536"
(**) VESA(0): Built-in mode "1280x1024"
(**) VESA(0): Built-in mode "1024x768"
(**) VESA(0): Built-in mode "800x600"
(**) VESA(0): Built-in mode "640x480"
(**) VESA(0): Built-in mode "640x400"
(==) VESA(0): DPI set to (75, 75)
(II) VESA(0): Attempting to use 60Hz refresh for mode "2048x1536" (152)
(II) VESA(0): Attempting to use 85Hz refresh for mode "1280x1024" (11b)
(II) VESA(0): Attempting to use 85Hz refresh for mode "1024x768" (118)
(II) VESA(0): Attempting to use 85Hz refresh for mode "800x600" (115)
(II) VESA(0): Attempting to use 85Hz refresh for mode "640x480" (112)
(II) VESA(0): Attempting to use 85Hz refresh for mode "640x400" (13e)
I see this... "Attempting to use 60Hz refresh for mode "2048x1536"" whyyy !!??!? and no mode ?? wtf

veerain 11-03-2007 11:38 AM

Find out which xorg.conf is using in /var/log/xorg.0.conf
See a line like this at sstart
(==) Using config file: "/etc/X11/xorg.conf"


SFX: http://www.spreadfirefox.com/?q=affi...211983&t=1

terfy 11-03-2007 11:54 AM

Quote:

(==) Log file: "/var/log/Xorg.0.log", Time: Sat Nov 3 15:57:36 2007
(==) Using config file: "/etc/X11/xorg.conf"
so it should be good right ??

its strange

jlinkels 11-03-2007 03:33 PM

Quote:

Originally Posted by terfy (Post 2946894)
(II) VESA(0): Not using mode "1600x1200" (no mode of this name)

Ah, I think I might see a clue...

You ask for 1600x1200, but the driver reports it cannot do that. (It might be that another OS can do it, but that might be driver dependent) X will automatically use the highest resolution reported by the driver.

What if you remove all modes higher than 1280 x 1024 from xorg.conf. Will it then switch to 1280 x 1024? If so, you have found the cause.

Obviously you will not be satisfied with this resolution. Maybe there is a driver update which does support 1600 x 1200. Otherwise, go very thoroughly thru Xorg.0.log and check if there is somewhere a list of supported modes in that file. It is driver dependent what information you get, hopefully there is something like that.

Once you found it, pick a resolution that suits you and enter it in xorg.conf. Provided there is one.

jlinkels

terfy 11-03-2007 04:32 PM

I think that too yes..

it is not on the supported resolutions list..

so.. but how the heck do I find one supporting then ??

wbt for now I really dont care, as I found the highest resolution better for my needs.. just a shame the frequenzies is 60hz than 85 in 1600x1200..

I'll wait for a newer xorg for my distro (Lunar Linux)
or... maybe I should try compile the newest myself.

just shitty lame that 1600x1200 is not supported.. what are ppl thinking man.. its a great res..

anyway I think we can close the thread as It seems to resolve the problem.

thanks

terfy 11-03-2007 05:21 PM

fixed


1: enabled nvidia in kernel
2: compiled nvidia
3: ran nvidia-xconfig
4: restarted X

final: 1600x1200 works great

jlinkels 11-03-2007 06:07 PM

Quote:

Originally Posted by terfy (Post 2946894)
(**) VESA(0): Built-in mode "800x600"
(**) VESA(0): Built-in mode "640x480"
(**) VESA(0): Built-in mode "640x400"

Well, this is a typcial example where the solution is written in SUCH HUGE CAPITALS and one still doesn't see it.

These messages came from the VESA driver, but since you have nvidia, these messages should have been produced by the nividia driver if it had been loaded. like:

(**) NVIDIA(0): ... etc.

Apparently xorg used the wrong driver, and yes it is obvious that it is solved now.

Stupid me! :mad:

jlinkels

terfy 11-04-2007 04:43 AM

yep..

it used VESA drivers before as you see.
bye hey VESA driver sucks if it doesn't even have 1600x1200 mode.

jlinkels 11-04-2007 05:12 PM

Quote:

Originally Posted by terfy (Post 2947628)
yep..
bye hey VESA driver sucks if it doesn't even have 1600x1200 mode.

Yes and know.

The VESA driver is some sort of generic driver which can interface with almost any VGA card, and give a reasonable image. That is because VESA uses a common set of commands to control a graphic card which are implemented in almost all cards. But high optimization, GLX, special resolutions are not handled well or not at all.

Not many VGA cards use VESA as their driver, but as long as you haven't got the real driver for your VGA card running, it is a good general purpose tool. For example, Knoppix reverts to the VESA driver if it hasn't the correct driver for your special card on disk.

The real driver (and certainly for modern high-power cards) is always the preferred one to use. I bet your graphic speed went up an order of magnitude as well.

jlinkels

terfy 11-05-2007 03:37 AM

btw it SHOULD be easier to "install" a gfx driver..


All times are GMT -5. The time now is 01:40 AM.