Bug 485275

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf (if you have one) whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Created attachment 331792 [details]
/var/log/Xorg.0.log with no xorg.conf

Add the Xorg log, with no xorg.conf used.

Well, we told you so ;-)
> (WW) RADEON(0): R600 support is mostly incomplete and very experimental

Passing to developers.

Any update on this issue ?

Looking carefully at the log, I noticed DRI and AIGLX were enabled (with a software rasterizer which does not even work properly - trying to enable compiz results in a white screen that is very difficult to get out of), but disabling them did not help performance.

Created attachment 333600 [details]
Xorg.0.log with no xorg.conf file

I have a somewhat related issue with the ATI RADEON HD 4650 1GB PciE.
I have just installed a new FC10 x86_64 from the installation DVD.
The first screen was displayed with X.
I have requested in it the first option to upgrade or install a new system.
The next screen was a tty screen regarding media verification which I skipped.
the next step was that anaconda has been run.
At the end of the anaconda run a message "X failed to start" has been displayed.
From this point and on the installation continued in text mode.
The final login mode was text mode (init level 3).
After installation completion a full system update has been done using yum.

Next step was to test X. For this I have issued the startx command.
The startx command started to execute, w white screen has been displayed all over my physical display and it just hang in this stage.

I have exited the startx using alt+ctrl+bs.

This has been done with no xorg.conf file.
Looking in the Xorg.0.log file, it seems that bothe the adapter and the display have been properly detected. However there are errors regarding all possible display resolutions in the log file.

At this stage I am not able to switch the graphical mode.

I am attaching my Xorg.0.log file.

Any help will be appreciated.

Thanks,
Itzik

Have you tried the radeonhd driver? It should have better support for these cards.

For #6, the initial F10 does not support RV730. Add vga=795 to the boot line to use vesa, update, and it should work (only slightly faster than vesa ...).

I am using rawhide on my RV770, and with the very latest xorg-x11-drv-ati-6.11.0-7, both EXA and xv finally work, and everything is really really fast. Good job Dave. Of course, I can't test with the RV730 right now.

I know I will never get any answer after one month politely ignoring this BZ, but I'll ask anyway: is there any chance the R600+ support gets ported to F10 ?

I wasn't ignoring it, I just wasn't able to do anything about it.

Now AMD have released the code, I've put in into rawhide thus fixing bugs.

However the code isn't ready for an F10 backport, maybe it will be by the time F11 ships, but not yet. It doesn't even suspend/resume properly yet.

I just tested rawhide with the RV730, and both EXA and XV are functional (no surprise). Speed is good. For whatever reason, there seems to be more tearing moving windows around than on the RV770.

Although it may not suspend/resume (I really don't see the point of suspend/resume personally ...), the current F10 driver looks really bad to me for R700.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

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.