Red Hat Bugzilla – Bug 471399
Resolution changing with x1950 pro, with modesetting fails.
Last modified: 2018-04-11 06:55:19 EDT
Created attachment 323453 [details]
xorg.log from an X run without modesetting.
First of all, this is not a duplicate of the "fails to start without nomodeset" bug, my system starts and works fine.
However when I start a game which changes the resolution, my display becomes garbled.
To be specific when I start machineball ("yum install machineball") my display becomes garbled, I haven't tried other games yet, but I'm pretty sure this is caused by the resolution change this fullscreen game requests during startup.
I'll attach an xorg.log from a run without modesetting.
log file ends with a zillion copies of the lines
RADEONCheckTexturePOT: NPOT repeating source unsupported (38x91), transform=1
and then another zillion of
R300CheckCompositeTexture: Unsupported picture format 0x1011000
(In reply to comment #1)
> log file ends with a zillion copies of the lines
> RADEONCheckTexturePOT: NPOT repeating source unsupported (38x91), transform=1
> and then another zillion of
> R300CheckCompositeTexture: Unsupported picture format 0x1011000
Note this log file is from a successfull! run (without modesetting) of machineball. Those messages are because I'm using a special compiled version of xorg-x11-drv-ati which has sofftware fallback debugging enabled. I'm running this version at the request of airlied (who also build it for me).
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
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.