Hi the builtin modelines of XFree40 aren't always good enough I had to add
a modeline to get 1152x864 in 16 bpp on my Matrox Millenium 1 for example,
so I think it would be wise to add modelines to the generated config, then
again the current setup results in a very readable config and the builtin
modelines are probavly very well tested.
This defect is considered MUST-FIX for Winston Beta-5
Does this defect still exist with (on) Winston beta-4?
Well there are still no modelines in the generated XF86Config, so unless the
matrox driver changed significantly I think I still cannot get 1152x864 with
XF40 this way.
I'll check tomorrow when I upgrade the relevant machine to beta4.
Since we generate a working X config for this card, I'm switching
this to an enhancement request.
Assigning to Xconfigurator, as it is being rewritten and will solve many of
Exactly what do your added modeline do? Higher frequency? Lower?
Ehm, I dunno.
All I knew is I couldn't get 1152 x 864 x 16 bpp with my matrox millenium I 2
mb, and a NEC 4 Fge as monitor. Just adding the modelines from my XFree336
XF86Config fixed the problem.
What frequency does that result in?
I currently have another card in but I'm still using the same modeline.
Here's the xvidtune info:
Pixel Clock: 92.00 Mhz
Hsync: 62.41 Khz
Vsync: 69.74 Khz
OK, I can see why X didn't want to use that as it's below 72 Hz and I'm guessing
it won't suggest a modeline for a bad/lowfrequency mode. How does it fail
Depends, if almost always do a custom X setup in anaconda, normally O only check
the mode I want, then testing X just fails, if I check 1024x768 too, I get that
I didn't remember my mode was below the 72 Hz (My card can handle that but not
not allowing modes below 72Hz by defaults sounds sane to me.
So as far as I'm concerned this bug can be closed with notabug.