Is the monitor being correctly probed by ddcprobe?

yes, I think that was okay (Vision Master Pro 21" Iiyama)
'cause that's the first think I though might have failed.

Daniel

Hmm...can you post the results of the ddcprobe?

The reason I ask is because we fall back to some safe defaults for
monitors that can't be probed (640x480 and 800x600).  If you go to the
hardware tab and manually select the right monitor, the list of
resolutions will change to reflect the capabilities of that selection.
 If that's not the case here, then I don't know what could be wrong. 
Almost none of that code has changed since FC1.

As root I get 

[root@localhost root]# ddcprobe
                                                                     
          
Videocard DDC probe results
Description:  Matrox MISTRAL
Memory (MB):  2
                                                                     
          
Monitor DDC probe results
ID: IVM2130
Name: Iiyama MT-9021E/T, VisionMasterPro
Horizontal Sync (kHZ): 24-94
Vertical Sync (HZ)  : 50-160
Width (mm): 400
Height(mm): 300
[root@localhost root]#

 The values returned seems accurate.
 As an user it fails, that's probably normal though:

localhost:~ -> ddcprobe
                                                                     
          
Monitor DDC probe results
Monitor DDC Probe failed.
localhost:~ ->

  Running the gui configuration tool, the hardware (card Matrox
Millenium II, VisionMasterPro 21) is correctly detected. Now it
offers 4 resolutions (1152, 1024, 800, 640) though the monitor/card
combo has been running 1600x1200 happily, even on FC2 beta1 ...

  I hope this helps ...

Daniel

I can't believe that a 2MB video card can do 1600x1200 in anything
other than 8 bit color.  I've put a 2MB Matrox Mystique in my test
machine and when I try to do anything over 800x600 with 16 bit color
or more, xorg-x11 gives an error that it needs at least 4608 kB of
video memory to do that resolution and bit depth.

The list of available resolutions comes from rhpl in the xhwstate.py
file in the available_resolutions() function.  It tries to create a
list of resolutions that makes sense for video cards of various memory
sizes.  It's impossible to correctly guess all available modes for all
video card/monitor combination and get it completely right.  

I'm going to change the component of this bug to rhpl and assign it to
katzj.  I would recommend closing this as 'notabug' since I think the
code in availabe_resolutions() gets it right about as often as can be
expected.

well dccprobe is just wrong, I think that card has 4MB
From the /var/log/XFree86.0.log (where it's running 1600x1200x16bpp)
(--) PCI:*(0:9:0) Matrox Graphics, Inc. MGA 2164W [Millennium II] rev
0, Mem @ 0xcd000000/24, 0xcfffc000/14, 0xcf000000/23, BIOS @ 0xcffe0000/16
[...]
(--) MGA(0): VideoRAM: 4096 kByte

Daniel

I had the same problem with my Matrox Millenium II in FC1 and I
continue to have this problem in FC2 after doing a fresh installation.
 I'm absolutely sure that My Millenium II has 4MB of memory but
dccprobe is reporting that it only has 2MB.

I have the same problem, running FC2, after a clean install i can't
get any higher resolutions than 800x600. 

Im sure, that I can run in 1024x768 using millions of colors, but
setup does not provide that resolution. Im using an LCD screen,
DDCPROBE did get the specs right - but to avoid problems I did try a
1024x768 generic LCD - it didn't do any good.

Is there a way to force a resolution in FC2 (im a n00b when it comes
to linux).

Closing bugs on older, no longer supported releases. Apologies for any lack of
response.

Please attempt to reproduce this bug on a currently supported release, such as
Fedora Core 4. If it persists, please open a new bug in bugzilla.