Description of problem:
R200 misrenders the teapot and reflect mesa demos.
Possibly others, haven't tried them.
Version-Release number of selected component (if applicable):
February 2011 test day live CD
TI Technologies Inc RV280 [Radeon 9200] (Secondary) (rev 01)
Smolt profile: http://www.smolts.org/client/show/pub_a5d07af1-0e5e-4bb1-b6cb-5d02feaf0891
Steps to Reproduce:
1. Run teapot or reflect
2. Run them again with LIBGL_ALWAYS_SOFTWARE=1
3. Compare the output images
Reflect doesn't seem to be lit
Texturing of the floor in teapot is wrong
Images are fairly close to identical
Created attachment 480283 [details]
reflect, as rendered by a rv280
Created attachment 480284 [details]
reflect, software rendering
Created attachment 480285 [details]
teapot, as rendered by a rv280
Created attachment 480286 [details]
teapot, software rendering
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.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 482777 [details]
Created attachment 482779 [details]
Created attachment 482780 [details]
/var/log/Xorg.0.log is the attachment 480896 [details]
dmesg output is the attachment 480897 [details]
/var/log/messages is the attachment 480898 [details]
It's the exact same disc image on the exact same hardware, what more do you want?
(In reply to comment #10)
> It's the exact same disc image on the exact same hardware, what more do you
Nothing, I just made better links to the bug. As you can see I declared this bug complete in terms of logs and passed it to the developers.
Oh, I'm sorry. I completely misinterpreted what you were doing. My apologies.
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
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: