No or broken 3d-acceleration with Jaunty on ibook/powerpc

Bug #354677 reported by David Hedberg
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-ati (Ubuntu)
New
Undecided
Unassigned

Bug Description

Powerpc port of Jaunty, installed with the beta-iso and updated today 2009-04-03, seemingly fails to initialize proper 3D-acceleration. glxgears runs with low fps (around 60), and also with a blue tint.
Compiz-manager aborts with:
Software rasterizer detected, abortingaborting and using fallback: /usr/bin/metacity

2D and xv seems to work fine. I have also attempted setting UseFBDev to false in Xorg.conf with no difference.

Possibly relevant section from Xorg.0.log:
(II) RADEON(0): [DRI] installation complete
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xf2ce2000 at 0x48021000
(II) RADEON(0): [drm] Closed DRM master.
(WW) RADEON(0): Direct rendering disabled
(II) RADEON(0): Render acceleration enabled for R200 type cards.

glxinfo, however, claims that direct rendering is enabled.

And from /var/log/syslog:
Apr 3 20:08:47 ibook kernel: [ 1608.954840] radeonfb 0000:00:10.0: Invalid ROM contents
Apr 3 20:08:47 ibook kernel: [ 1608.955042] radeonfb 0000:00:10.0: Invalid ROM contents
..
Apr 3 20:08:47 ibook kernel: [ 1609.206954] agpgart-uninorth 0000:00:0b.0: putting AGP V2 device into 4x mode
Apr 3 20:08:47 ibook kernel: [ 1609.206972] radeonfb 0000:00:10.0: putting AGP V2 device into 4x mode
Apr 3 20:08:48 ibook kernel: [ 1609.418221] __ioremap(): phys addr 0x0 is RAM lr f2ae9d10
Apr 3 20:08:48 ibook kernel: [ 1609.418234] __ioremap(): phys addr 0x101000 is RAM lr f2ae9d10
Apr 3 20:08:48 ibook kernel: [ 1609.418239] __ioremap(): phys addr 0x102000 is RAM lr f2ae9d10
Apr 3 20:08:48 ibook kernel: [ 1609.418247] [drm:radeon_do_init_cp] *ERROR* could not find ioremap agp regions!

lspci -vvnn gives:
0000:00:10.0 VGA compatible controller [0300]: ATI Technologies Inc M9+ 5C63 [Radeon Mobility 9200 (AGP)] [1002:5c63] (rev 01)
 Subsystem: ATI Technologies Inc M9+ 5C63 [Radeon Mobility 9200 (AGP)] [1002:5c63]
 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 [size=128K]
 Capabilities: <access denied>
 Kernel driver in use: radeonfb

uname -a:
Linux ibook 2.6.28-6-powerpc #16-Ubuntu Wed Apr 1 07:52:37 UTC 2009 ppc GNU/Linux

lsb_release -rd:
Description: Ubuntu jaunty (development branch)
Release: 9.04

Revision history for this message
David Hedberg (david-hedberg) wrote :
Revision history for this message
David Hedberg (david-hedberg) wrote :

I should have done this before reporting the bug of course, but as I had vague memories of acceleration working when trying out an earlier live-cd version of ubuntu "long ago", I downloaded the 5.04 Live CD and tried it out. And it did indeed have working 3D-acceleration.

Comparing the logs seemed to point at the difference lying in 5.04 falling back on pci for the dri, so I added:
 Option "BusType" "PCI"
to my xorg.conf.

With this option added, 3D-acceleration (including compiz which I'm using at the moment) seems to work just fine, and glxgears (the beloved benchmarking tool ;) ) reports fps about 10 times higher than before.

So. Bug closed?

(is there even any use in reporting possibly ppc-specific bugs?)

Revision history for this message
Simon Butcher (sbutcher) wrote :

I experience the same problem with ibook 1.42ghz 14 inch model.
Intrepid was working (with wobbly windows) but upgrade to jaunty beta does not allow compiz to run (same error as above).

However my /etc/X11/xorg.conf is 0 bytes.

 Hardware is
0000:00:10.0 VGA compatible controller [0300]: ATI Technologies Inc M11 NV [FireGL Mobility T2e] [1002:4e56] (rev 80)
 Subsystem: ATI Technologies Inc M11 NV [FireGL Mobility T2e] [1002:4e56]
 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 [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=8 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
 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-

Revision history for this message
Jonathan Hudson (jh+lpd) wrote :

This is a duplicate of Bug 345542 <email address hidden>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.