Created attachment 325526 [details]
log with no xorg.conf, ended up on 800x600
F10 did not use proper resolution on ATI cards with radeon driver. Even I have LCD 1280x1024 and X server detect it properly, I ended up on 800x600.
I tryed xorg-x11-drv-ati-6.9.0-61.fc10.i386 from koji with no luck.
I have to use xorg.conf with HorizSync and VertRefresh to use native resolution.
Created attachment 325527 [details]
xorg with HorizSync and VertRefresh to get native 1280x1024
Created attachment 325529 [details]
log with xorg.conf, native 1280x1024 has been auto-used
Created attachment 325530 [details]
log with no xorg.conf, ended up on 800x600
I have onboard "ATI Technologies Inc RV370 [Sapphire X550 Silent]" (0300: 1002:5b63) and:
The KMS correcly set 1280x1024 for text console.
The other machine has onboard ATI RS690 [Radeon X1200 Series] and has the same problem. With no xorg.conf both 54 and 59 drivers end up on 800x600 even text console has 1280x1024. xorg.conf needs 1280x1024 mode in screen section.
Created attachment 325587 [details]
Other machine, no xorg.conf, ends with 800x600
Created attachment 325588 [details]
Other machine, xorg.conf to get 1280x1024
Created attachment 325589 [details]
Other machine, xorg.conf has been used, correct 1280x1024
Last 3 attachments are from "other machine" with xorg-x11-drv-ati-6.9.0-61.fc10.i386.
The 61 driver is better than the older from F10 because does not hang. 61 is only much slower nad X server eats 50 to 70% of CPU when there are fast movements (Firefox scrolling, 3D desktop effects). But mouse is still movable when the troubles come.
1) login as root (open terminal, type command "su -" and root's password)
2) init 3
3) login as root at text console
4) X -configure
5) copy new config file to /etc/X11/xorg.conf
6) edit file above an add (if needed) to Display subsection under Screen section
your native resolution:
It is possible to create new config file in GUI, then logout/login only.
ASUS M2A-VM with onboard "ATI Technologies Inc RS690 [Radeon X1200 Series]" has the same problem. But without hangs even older driver (PCI ID: 0300: 1002:791e).
My friend has laptop with a ATI Mobility Radeon X300, I had to install F10 for him, X completely failed to startup during the installation already, so I had to force the VESA driver to be able to run anything graphical, either during installation of F10 or normal use of F10 (after installation of course)... If I currently try to use any other driver (including fglrx) then X fails to startup. So he's stuck using F10 in VESA mode....
Try using nomodeset on the kernel boot line in grub.
This is very similar to bug #493243. From the attached log, I see that it's detecting a monitor attached to VGA-0 when there isn't one. Definitely try using "nomodeset" as a workaround for now.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.