After upgrading to F-10 from F-9, I lost DRI support: [petro@Sulaco ~]$ grep \(EE\) /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) RADEON(0): Static buffer allocation failed. Disabling DRI. (EE) RADEON(0): At least 46080 kB of video memory needed at this resolution and depth. http://peter.fedorapeople.org/F-10/Xorg.0.log I've got also garbled colors in glxgears (with perfomance drop from 700 fps to 100): http://peter.fedorapeople.org/glxgears.png Snippet from lspci -vvv: 0000:00:10.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ATI Technologies Inc RV280 [Radeon 9200] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 255 (2000ns min), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 48 Region 0: Memory at 98000000 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at 0400 [size=256] Region 2: Memory at 90000000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at f1000000 [disabled] [size=128K] Capabilities: [58] AGP version 2.0 Status: RQ=80 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none> Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: radeonfb Kernel modules: radeon http://peter.fedorapeople.org/F-10/lspci.txt
Created attachment 325010 [details] lspci.txt from http://peter.fedorapeople.org/F-10
Created attachment 325011 [details] Xorg.0.log from http://peter.fedorapeople.org/F-10
Created attachment 325012 [details] glxgears.png from http://peter.fedorapeople.org/F-10
Changing defauld bit depth to 16 resolved it, however I don't think this is a proper fix for this issue in 2008/2009 :)
Just for curiosity - here is a log from F-9's X.org - there is no issue with memory allocation for DRI: http://peter.fedorapeople.org/Xorg.0.log
Created attachment 326277 [details] Xorg log from F-9 (w/o error with memory allocation)
Today's git ( d5cb24075928690377fd2dfaa32abfebff9990df ) solved this issue. I've got glxgears with 700+ fps and correctly drawn, even in 24-bit color!
I have reported other Radeon performance problems in #485651 but decided to try glxgears results as well. I still get very poor performance with the latest official drivers: xorg-x11-drv-ati-6.10.0-2.fc10.i386 xorg-x11-server-Xorg-1.5.3-15.fc10.i386 FPS CPU ------- --- --------------------- 140.3 62% f10-radeon 1513.8 59% f10-radeon-16bpp 143.2 61% f10-radeon-exa 1513.6 59% f10-radeon-exa-16bpp 95.8 42% f10-vesa 886.1 20% f9-radeon 1510.2 29% f9-radeon-16bpp 842.4 21% f9-radeon-exa 1511.8 30% f9-radeon-exa-16bpp 133.4 44% f9-vesa For some reason, glxgears consumes also much more CPU in F10. I didn't measure the server CPU consumption. The tests were done in runlevel 2 starting just the server and glxgears. Dropping down to 16bpp seems to fix the performance problem (because DRI gets enabled), but as Peter remarks, this shouldn't be necessary nor is it obvious for the majority of users.
Created attachment 336181 [details] Bar graph of glxgears FPS and CPU usage in F9 and F10
I just noticed that after switching to 16bpp I couldn't watch videos any more, the overlay area was blank. So 16bpp isn't a viable workaround for the DRI bug.
*** Bug 508467 has been marked as a duplicate of this bug. ***
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
This issue still exists in F-12: [petro@Sulaco Desktop]$ grep \(EE\) /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) RADEON(0): Static buffer allocation failed. Disabling DRI. (EE) RADEON(0): At least 72000 kB of video memory needed at this resolution and depth. [petro@Sulaco Desktop]$ rpm -q mesa-dri-drivers mesa-dri-drivers-7.6-0.13.fc12.ppc [petro@Sulaco Desktop]$ rpm -q xorg-x11-drv-ati xorg-x11-drv-ati-6.13.0-0.10.20091006git457646d73.fc12.ppc
Created attachment 372874 [details] Xorg.0.log from F-12
Created attachment 372875 [details] lspci -vvv output from F-12
Created attachment 372876 [details] glxgears on F-12
Created attachment 372877 [details] lspci -vvv output from F-12
Hi Peter. I had the same problem on FC12 PPC (G4 Mac Mini). * glxgears only got around 80 fps * glxgears with yellow/green appearance * really blocky video ouput in vlc/totem * same output of "grep \(EE\) /var/log/Xorg.0.log" (although my video memory required was lower) This was my work around... to add the virtual line: Section "Screen" ... Subsection "Display" Depth 24 Modes "1280x1024" Virtual 1280 1024 EndSubsection EndSection Now DRI is enabled, glxgears gets above 1200 fps and video looks great. Hope this helps.
Thanks for the tip, Mike! This config solves almost all issues: ==================== Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 EndSection Section "Screen" Identifier "Screen0" SubSection "Display" Virtual 1920 1200 EndSubSection EndSection ==================== Now I'm sure, that there is something wrong then "Virtual" directive is missing.
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.