Re: how does X find modelines?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Warren Paul wrote:
> The reason I have those lines commented is for testing. So instead of re
> writing everything out again I just comment and uncomment the lines I need.


Hmm, I didn't get that part from the email you sent with the configuration and
log files. The logfile that worked, which lines were uncommented?


Modes "1600x1200"
# Modes "1680x1050" "1400x1050" "1280x1024" "1280x960" "1024x768" "800x600" 640x480"
# Modes "1680x1050"


the mode 1600x1200 works fine.
The 1680x1050 1400x1050 etc line is for when everything finally works and to test that everything works fine. Thats why I have it commented out to save me writing out al those modes again.
the the 1680x1050 line is just for testing purposes. So when yourself or I or anyone comes up with an idea I can just uncomment it and comment the rest. I know it probably aint the best idea and may be confusing, but I've done this so many times, I just wanted a quicker way :-)



Hi, I hope you don't mind me following along. From an earlier email:

   Subsection "Display"
       Depth       24
    Modes        "1600x1200"
#    Modes       "1680x1050" "1400x1050" (etc.)...

and you included

Modeline "1680x1050" 147.10 1680 1784 1968 2256 1050 1051 1054 1087

and got this response...

(II) fglrx(0): Not using mode "1600x1200" (no mode of this name)
(--) fglrx(0): Virtual size is 1680x1050 (pitch 1728)
(**) fglrx(0): Mode "1680x1050": 147.1 MHz, 65.2 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1680x1050" 147.10 1680 1784 1968 2256 1050 1051 1054 1087


what I'm not exactly clear about is whether X is really using the modeline values on this last line or not, but it seems to me that you didn't give it a chance to realyl use 1600x1200 correctly since you didn't include a modeline inpt for that setting. (And I understand that you probably didn't want to...)

I've heard of other people that have had problems with modeline settings causing strange sorts of problems. I'm sure you're sick of all of this, but have you gone through a number of other (slower) refresh rates?

50Hz:

Horizontal Resolution: 	1680
Vertical Resolution: 	1050

Vertical Refresh Rate: 	50.00 Hz
Horizontal Refresh Rate: 	54.12 KHz
Dot Clock Frequence: 	116.05 MHz


# V-freq: 50.00 Hz // h-freq: 54.12 KHz Modeline "1680x1050" 116.05 1680 1744 1888 2144 1050 1050 1052 1082


55Hz:

Horizontal Resolution: 	1680
Vertical Resolution: 	1050

Vertical Refresh Rate: 	55.00 Hz
Horizontal Refresh Rate: 	59.72 KHz
Dot Clock Frequence: 	131.86 MHz


# V-freq: 55.00 Hz // h-freq: 59.72 KHz Modeline "1680x1050" 131.86 1680 1752 1912 2208 1050 1050 1052 1085


60Hz: Horizontal Resolution: 1680 Vertical Resolution: 1050

Vertical Refresh Rate: 	60.00 Hz
Horizontal Refresh Rate: 	65.35 KHz
Dot Clock Frequence: 	149.01 MHz


# V-freq: 60.00 Hz // h-freq: 65.35 KHz Modeline "1680x1050" 149.01 1680 1760 1944 2280 1050 1050 1052 1089

Please note that for 60Hz I got slightly different values than you did. This is interesting.

Wish I had real answers.

Good luck,
Mark
_______________________________________________
XFree86 mailing list
XFree86@xxxxxxxxxxx
http://XFree86.Org/mailman/listinfo/xfree86

[Index of Archives]     [X Forum]     [Xorg]     [XFree86 Newbie]     [IETF Announce]     [Security]     [Font Config]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux Kernel]

  Powered by Linux