Bug 673848

Summary: Radeon 7000 (RV100) doesn't work properly
Product: [Fedora] Fedora Reporter: Jean-François Fortin Tam <nekohayo>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 19CC: mcepl, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-23 18:33:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
requested log files
none
boot.log from the archive
none
dmesg.txt from the archive
none
messages from the archive
none
Xorg.0.log from the archive
none
screencast of the issue
none
screencast of the issue none

Description Jean-François Fortin Tam 2011-01-30 22:01:27 UTC
lspci | grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]

glxinfo | grep "direct rendering"
direct rendering: Yes


Yet, I seem to be able to run compiz, mutter, gnome-shell, or any app requiring 3D. The desktop in general feels sluggish too (at 1024x768). Is this a known problem with the RV100?

Comment 1 Jean-François Fortin Tam 2011-01-30 22:24:44 UTC
Correction to the above paragraph: I seem to be *unable* to run compiz, mutter, gnome-shell, etc.

Comment 2 Matěj Cepl 2011-01-31 13:57:16 UTC
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 add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

Would running demos from mesa-demos (try all of them until they fail, or teapot or fire are the bigger ones) generate some more interesting messages in /var/log/Xorg.0.log or dmesg output?

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

Thanks in advance.

Comment 3 Jean-François Fortin Tam 2011-01-31 16:00:01 UTC
Created attachment 476219 [details]
requested log files

I do not use a xorg.conf
These are the logs as they are on a fresh startup.

I installed the mesa demos package with yum, but I don't know how to run them.
Note that running glxgears only gets 90-100 fps, with 100% CPU usage.

Comment 4 Matěj Cepl 2011-01-31 22:38:46 UTC
Created attachment 476277 [details]
boot.log from the archive

Comment 5 Matěj Cepl 2011-01-31 22:38:53 UTC
Created attachment 476278 [details]
dmesg.txt from the archive

Comment 6 Matěj Cepl 2011-01-31 22:39:06 UTC
Created attachment 476279 [details]
messages from the archive

Comment 7 Matěj Cepl 2011-01-31 22:39:13 UTC
Created attachment 476280 [details]
Xorg.0.log from the archive

Comment 8 Matěj Cepl 2011-01-31 22:52:13 UTC
(In reply to comment #3)
> I installed the mesa demos package with yum, but I don't know how to run them.
> Note that running glxgears only gets 90-100 fps, with 100% CPU usage.

They are not in $PATH, so you have to run them directly with full path, e.g.:

/usr/lib/mesa/teapot

(try other programs in the same directory as well)

Comment 9 Jean-François Fortin Tam 2011-02-01 03:11:21 UTC
I ran teapot, fire, tunnel, tunnel2, glxheads. No crashes, but the apps ran at ~9 to 12 fps. Nothing new shows up in the various logs attached above.

Comment 10 Matěj Cepl 2011-02-01 10:05:54 UTC
What exactly happens when you run desktop-effects from terminal?

Comment 11 Jean-François Fortin Tam 2011-02-01 14:34:32 UTC
Compiz = white screen with only the mouse cursor, and after a few seconds it deactivates because I obviously cannot confirm to desktop-effects that the settings are "correct"

GNOME Shell = corrupt graphics, and after a while it simply crashes and returns me to gdm (possibly because desktop effects tried to kill it).

Video that shows everything: http://jeff.ecchi.ca/public/fedora-673848.ogv

Comment 12 Matěj Cepl 2011-02-01 15:14:53 UTC
Created attachment 476413 [details]
screencast of the issue

Comment 13 Jean-François Fortin Tam 2011-02-01 17:57:41 UTC
Created attachment 476454 [details]
screencast of the issue

Screencast without the cropping of the top part (so you can see the visual corruption in gnome shell)

Comment 14 Fedora End Of Life 2013-04-03 18:16:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 15 Jean-François Fortin Tam 2013-11-23 18:33:05 UTC
Old hardware be damned.