The xorg-x11 packaging does not have anything to do with X configuration
or with anaconda's install time autodetection of hardware. Since the bug
report states that this is happening at installation time in anaconda,
then wherever anaconda (or the tools it uses) determines the screen
dimensions from may be incorrect.
Reassigning to anaconda, however it is probably not anaconda which is
directly responsible.

Sorry, not going to test with FC5. Please just wait for someone to report it
again after a few hours of struggling with FC5. Maybe no one is using that
monitor anymore, and you guys don't need to bother fixing it.

Can this be re-opened because this still doesn't work. I was always unable to
install FC4 in graphical mode using my Samsung Syncmaster 913N and now with FC5
I still have the same problem.
It somehow seems to use an unsafe resolution/refresh combination because the
monitor jsut shows colored lines and a warning that the image being displayed is
using a suboptimal resolution. But telling the installer to use specific
resolutions (I tried 640x480, 800x600, 1024x768 and 1280x1024) makes no difference.
If I finally install FC4 or 5 using text mode I can get X to work using either
the vesa or the closed-source nvidia driver. The nv driver installed by default
by the installation just doesn't seem to use the correct settings for the monitor.
I must say that I don't remember correctly anymore, but I think I had to turn
off DDC and modelines manually for the nv driver to work.

Note

You need to
log in
before you can comment on or make changes to this bug.