Bug 542275

I just realized that I am passing nomodeset from grub. I will try to reproduce the issue without nomodeset and update the ticket.

I can start X if I don't pass the nomodeset option during boot, but glxgears only gives 1-2 gears/second.

$ glxinfo | grep rend
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 (RV410 5E4B) 20090101  TCL DRI2


$ glxgears 
11 frames in 6.1 seconds =  1.810 FPS

Xorg.0.log
http://pastebin.com/f56bc92f7

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), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

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

Thanks in advance.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Created attachment 377293 [details]
dmesg output

Created attachment 377294 [details]
Xorg.0.log

I'm not using an xorg.conf, but I did try using one with the options on the common bugs page. It didn't help.

All logs aboard, setting keyword=Triaged, setting status=ASSIGNED (Fedora 12) per new policy.

This bug has been triaged

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

*** Bug 545559 has been marked as a duplicate of this bug. ***

can you try latest kernel ?

by the way, i invite you to join bug https://bugzilla.redhat.com/show_bug.cgi?id=541562 to solve X700 suspend/resume issue

i am gathering people who have this chipset to have a better testing ground

i am using airlied git tree and it is performing better

here are glxgears results :

5798 frames in 5.0 seconds

that with KMS enabled

Please do not mix issue in one bug report - this is about X not starting, nothing to do with suspend nor glxgears performance.

I still see this on 2.6.31.9-174.fc12.i686, logs are identical as was reported earlier:

https://bugzilla.redhat.com/attachment.cgi?id=377008
https://bugzilla.redhat.com/attachment.cgi?id=377009

Hi Daniel,

Again, this issue is the same, and Fedora is trying to focus on KMS issues. So non KMS issue are likely non welcome.

Please read more before trying to give judgements like that. I am having this issue, and all X700 owners do, and it is RELATED to suspend resume issue.

Best Regards

I have an x7-- card and did some testing on this just before Christmas. 2.6.31.9-74.fc12.x86_64 failed with PLL divider issue. The partition has been upgraded to Rawhide. 2.6.32.2-15 (and earlier) and 2.6.33-rc2 seem to work fine in this regard. All tests were done acpi=off, radeon.modeset=1.

My regrets for not having checked this thread since then.

Further confirmation should be done. THe machine is my main workstation (CentOS, fwiw). I'll try to schedule some time for fc testing. Perhaps others can help out with the newer kernels.

Best,
Ed Leaver

I have an x7-- card and did some testing on this just before Christmas. 2.6.31.9-74.fc12.x86_64 failed with PLL divider issue. The partition has been upgraded to Rawhide. 2.6.32.2-15 (and earlier) and 2.6.33-rc2 seem to work fine in this regard. All tests were done acpi=off, radeon.modeset=1.

My regrets for not having checked this thread since then.

Further confirmation should be done. THe machine is my main workstation (CentOS, fwiw). I'll try to schedule some time for fc testing. Perhaps others can help out with the newer kernels.

Best,
Ed Leaver

I've confirmed this bug appears to be fixed on my fc12 and rawhide installs with the 2.6.31.12-174.2.3.fc12.x86_64 and 2.3.33-0.20.git0.fc13.x86_64 kernels. Both boot and startx fine, and run dual monitors pretty snappy with my x700 r410 card, but I won't do any extensive use on them until I find time to track down a snd-hda-intel bug. Please some one else confirm the fc12 fix. Thx.
Ed Leaver

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.