XFree86 4.0.2 Troubles!!!
Robert Hofmann
maybe somebody can help me configuring my Linux system (SuSE 7.1 prof.). I am
not able to get a usable resolution on my two systems. Using XF336, all works.
My monitor supports 30-100kHz, 50-170Hz.
On my Compaq AP200 at work (128MB, ELSA Gloria Synergy 8MB), using XF336, I
have 1280x1024x24bit in ~85kHz. Trying it with XF402, I only get something
around 54Hz. It is not possible to work with this! Any idea how to tune XF402
to have 1280x1024x24bit in a resonable sync (somewere >75Hz)?
On my LapTop (ASUS F7400, 160MB, ATI RAGE PRO LT 8MB), i have the same problem
whan trying it with an external monitor (using Win2k, I have 1280x1024x24bit
in 75Hz.). The horizontal frequency is very very poor. Simply not usable.
Well, I am, lets say, a novice in configuring XF, so maybe it is just to my
poor know-how.
Could anybody please help me? Any hint/help is very welcome!
Kind regards,
Robert
Toby Haynes
> Hi all,
>
> maybe somebody can help me configuring my Linux system (SuSE 7.1 prof.). I am
> not able to get a usable resolution on my two systems. Using XF336, all
> works. My monitor supports 30-100kHz, 50-170Hz.
>
> On my Compaq AP200 at work (128MB, ELSA Gloria Synergy 8MB), using XF336, I
> have 1280x1024x24bit in ~85kHz. Trying it with XF402, I only get something
> around 54Hz. It is not possible to work with this! Any idea how to tune XF402
> to have 1280x1024x24bit in a resonable sync (somewere >75Hz)?
Two possibilities - either there is no suitable mode defined (something which
is highly unlikely with 4.0.x as there are a large collection of default modes)
or you have the wrong monitor refresh rates in the /etc/X11/XF86Config-4
file. XFree86 picks the best mode it can use with the monitor.
Make a backup copy of the /etc/X11/XF86Config-4 file. Dig out your favourite
editor as root and look through for something which starts Section
"Monitor". It should look something like this (based on the numbers you gave
above).
Section "Monitor"
Identifier "Monitor0"
VendorName "COMPAQ"
ModelName "AP2000"
# These two values should be appropriate to your monitor
# Horizontal Sync in units of kHz
HorizSync 30.0-100.0
# Vertical refresh rate in units of Hz
VertRefresh 50.0-170.0
EndSection
The important lines are the HorizSync and VertRefresh ones - the rest is just
window dressing (except the Identifier which is used in the Section
"ServerLayout" part).
> On my LapTop (ASUS F7400, 160MB, ATI RAGE PRO LT 8MB), i have the same
> problem whan trying it with an external monitor (using Win2k, I have
> 1280x1024x24bit in 75Hz.). The horizontal frequency is very very poor. Simply
> not usable.
Should be a similar fix if this is the same problem.
Cheers,
Toby Haynes
--
Toby Haynes
The views and opinions expressed in this message are my own, and do
not necessarily reflect those of IBM Canada.
Robert Hofmann
> > On my Compaq AP200 at work (128MB, ELSA Gloria Synergy 8MB), using XF336, I
> > have 1280x1024x24bit in ~85kHz. Trying it with XF402, I only get something
> > around 54Hz. It is not possible to work with this! Any idea how to tune XF402
> > to have 1280x1024x24bit in a resonable sync (somewere >75Hz)?
>
> Two possibilities - either there is no suitable mode defined (something which
> is highly unlikely with 4.0.x as there are a large collection of default modes)
How can I check this? My monitor is a HP A4576A and it is not listed.
> or you have the wrong monitor refresh rates in the /etc/X11/XF86Config-4
> file. XFree86 picks the best mode it can use with the monitor.
> HorizSync 30.0-100.0
> VertRefresh 50.0-170.0
Well, it is there, but without ".0" at the end. But this shouldn't matter?
Tnx for your help.
Regards,
Robert
Toby Haynes
> Hi Toby!
>
>> > On my Compaq AP200 at work (128MB, ELSA Gloria Synergy 8MB), using XF336,
>> > I have 1280x1024x24bit in ~85kHz. Trying it with XF402, I only get
>> > something around 54Hz. It is not possible to work with this! Any idea how
>> > to tune XF402 to have 1280x1024x24bit in a resonable sync (somewere
>> > >75Hz)?
>>
>> Two possibilities - either there is no suitable mode defined (something
>> which is highly unlikely with 4.0.x as there are a large collection of
>> default modes)
>
> How can I check this? My monitor is a HP A4576A and it is not listed.
Don't worry about the strict monitor definition - the key things are the sync
ranges below. If your monitor supports EDID, then sometimes the monitor will
give misleading information to the driver and things get a little cranky, but
generally it should work ...
>> or you have the wrong monitor refresh rates in the /etc/X11/XF86Config-4
>> file. XFree86 picks the best mode it can use with the monitor.
>
>> HorizSync 30.0-100.0
>> VertRefresh 50.0-170.0
>
> Well, it is there, but without ".0" at the end. But this shouldn't matter?
No - the .0 shouldn't matter.
Okay - lets analyze this a little further. Look at the file
/var/log/XFree86.0.log after you start X in this 1280x1024x24bit@54Hz mode -
save it somewhere safe as I suspect you will quickly go insane looking at a
screen at 54Hz.
Look through it for lines like (the driver may be different):
(II) MGA(0): I2C bus "DDC" initialized.
(II) MGA(0): I2C device "DDC:ddc2" registered.
(II) MGA(0): I2C device "DDC:ddc2" removed.
(II) MGA(0): I2C device "DDC:ddc2" registered.
(II) MGA(0): I2C device "DDC:ddc2" removed.
(II) MGA(0): I2C Monitor info: 0x82872a8
(II) MGA(0): Manufacturer: PHL Model: 4109 Serial#: 2565
(II) MGA(0): Year: 1999 Week: 45
(II) MGA(0): EDID Version: 1.1
(II) MGA(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
(II) MGA(0): Sync: Separate Composite SyncOnGreen
(II) MGA(0): Max H-Image Size [cm]: horiz.: 34 vert.: 25
(II) MGA(0): Gamma: 2.76
and so on.
There should be a list of supported Vesa Modes - I suspect that 1280x1024@75Hz
should be listed. You should also get a pixel clock measurement and an image
size as well, among other details. Then it should tell you what refresh rates
it is going to use, and then it should 'delete' all unsuitable modes. What do
you get for all this, and how does it compare to the specs in the monitor
manual.
Robert Hofmann
> Don't worry about the strict monitor definition - the key things are the sync
> ranges below. If your monitor supports EDID, then sometimes the monitor will
> give misleading information to the driver and things get a little cranky, but
> generally it should work ...
With the old XF336, al works perfect... ;-)
> Okay - lets analyze this a little further. Look at the file
> /var/log/XFree86.0.log after you start X in this 1280x1024x24bit@54Hz mode -
> save it somewhere safe as I suspect you will quickly go insane looking at a
> screen at 54Hz.
I got it. See attachment for details...
> There should be a list of supported Vesa Modes - I suspect that 1280x1024@75Hz
> should be listed. You should also get a pixel clock measurement and an image
> size as well, among other details. Then it should tell you what refresh rates
> it is going to use, and then it should 'delete' all unsuitable modes. What do
> you get for all this, and how does it compare to the specs in the monitor
> manual.
Well, I think, I have found the problem. And it seems to be related to the SuSE
7.1 X-Configuration tool SaX or the gfx-driver itself.
(==) GLINT(0): Min pixel clock is 16 MHz
(--) GLINT(0): Max pixel clock is 110 MHz
(II) GLINT(0): Monitor[0]: Using hsync range of 27.00-100.00 kHz
(II) GLINT(0): Monitor[0]: Using vrefresh range of 50.00-170.00 Hz
(II) GLINT(0): Clock range: 16.25 to 110.00 MHz
(WW) GLINT(0): Mode "1280x1024" deleted (bad mode clock/interlace/doublescan)
(WW) GLINT(0): Mode "1280x1024" deleted (bad mode clock/interlace/doublescan)
(WW) GLINT(0): Mode "1280x1024" deleted (bad mode clock/interlace/doublescan)
(WW) GLINT(0): Mode "1280x1024" deleted (bad mode clock/interlace/doublescan)
(WW) GLINT(0): Default mode "1024x768" deleted (bad mode
clock/interlace/doublescan)
(WW) GLINT(0): Default mode "1280x960" deleted (bad mode
clock/interlace/doublescan)
(WW) GLINT(0): Default mode "1600x1200" deleted (bad mode
clock/interlace/doublescan)
(WW) GLINT(0): Default mode "1600x1200" deleted (bad mode
clock/interlace/doublescan)
(WW) GLINT(0): Default mode "1600x1200" deleted (bad mode
clock/interlace/doublescan)
(WW) GLINT(0): Default mode "1600x1200" deleted (bad mode
clock/interlace/doublescan)
(WW) GLINT(0): Default mode "1600x1200" deleted (bad mode
clock/interlace/doublescan)
(WW) GLINT(0): Default mode "1792x1344" deleted (insufficient memory for mode)
(WW) GLINT(0): Default mode "1792x1344" deleted (insufficient memory for mode)
(WW) GLINT(0): Default mode "1856x1392" deleted (insufficient memory for mode)
(WW) GLINT(0): Default mode "1856x1392" deleted (insufficient memory for mode)
(WW) GLINT(0): Default mode "1920x1440" deleted (insufficient memory for mode)
(WW) GLINT(0): Default mode "1920x1440" deleted (insufficient memory for mode)
(--) GLINT(0): Virtual size is 1280x1024 (pitch 1280)
(**) GLINT(0): Mode "1280x1024": 102.2 MHz, 58.9 kHz, 55.0 Hz
I definitly know, that my max. pixel clock is 150Mhz, NOT 110MHz. With the old
SaX belonging to XF336, I was able to change the clock manually and all was fine
for me. In SaX2 (XF402) I couldn't find where to do so.
I just wonder that the XF402-cfg tells me I have a
BoardName "Winner2000Office"
but I have a "ELSA GLoria Synergy 8MB" (the upper L is no typo! ;-)
Well, I am a novice in configuring XF. Is there another cfg-program to setup the
XF-config? I also tried XF86config, but well, there I have the same problem.
Maybe I just use the wrong tool. Unfortunately I am not that keen on the cfg to
"tune" it myself...
Attached you will find the log, the old XF336 cfg & the new XF402 cfg. Maybe you
can tell me, where I can adjust the clock-speed manually...
You have helped me very much! Tnx in advance!
Robert
Toby Haynes
> Well, I think, I have found the problem. And it seems to be related to
> the SuSE 7.1 X-Configuration tool SaX or the gfx-driver itself.
>
> (==) GLINT(0): Min pixel clock is 16 MHz
> (--) GLINT(0): Max pixel clock is 110 MHz
> (**) GLINT(0): Mode "1280x1024": 102.2 MHz, 58.9 kHz, 55.0 Hz
>
> I definitly know, that my max. pixel clock is 150Mhz, NOT 110MHz. With
> the old SaX belonging to XF336, I was able to change the clock
> manually and all was fine for me. In SaX2 (XF402) I couldn't find
> where to do so.
It's not obvious ...!
> I just wonder that the XF402-cfg tells me I have a
> BoardName "Winner2000Office"
> but I have a "ELSA GLoria Synergy 8MB" (the upper L is no typo! ;-)
I think this is merely a nicety rather than a requirement. But you could
change it to read GLoria Synergy if you like.
> Well, I am a novice in configuring XF. Is there another cfg-program to
> setup the XF-config? I also tried XF86config, but well, there I have
> the same problem. Maybe I just use the wrong tool. Unfortunately I am
> not that keen on the cfg to "tune" it myself...
There are other tools - I personally do the initial configuration with
xf86cfg and then tidy up any errors by hand.
> Attached you will find the log, the old XF336 cfg & the new XF402
> cfg. Maybe you can tell me, where I can adjust the clock-speed
> manually...
Try this - this manually sets the memory clock and might be the right
thing to tweak. There isn't any other obvious Clock tweak... but be
warned - this may hang your machine, so make sure that you can boot to
runlevel 3 if you have to reboot. The other two options below are
safer. (Just in case you don't know, to boot to runlevel 3 you would
type 'linux 3' at the LILO prompt - this is the text-only startup).
Section "Device"
Identifier "Device[0]"
VendorName "Elsa"
Driver "glint"
BoardName "Winner2000Office"
BusID "1:0:0"
Option "SetMClk" "150"
EndSection
One other possibility is to force the chipset detection rather than
letting it probe for it. This would look like
Section "Device"
Identifier "Device[0]"
VendorName "Elsa"
Driver "glint"
BoardName "Winner2000Office"
ChipSet "pm2"
BusID "1:0:0"
EndSection
or possibly the 'pm2v' chipset instead of the 'pm2' if this doesn't do
it.
The order of the Section "Device" doesn't matter, but it's easier to
read in this order :-)