r300 falling back on swrast
Jeremy Huddleston
jeremyhu at freedesktop.org
Sun May 3 13:33:47 PDT 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
For the record, it seems to be a bug in Ubuntu's kernel. I cannot
reproduce the problem using 2.6.28.9, 2.6.29.2, or the latest 2.6 git.
Thanks for the pointers.
Jeremy Huddleston wrote:
> So I've got a PowerBook that I like to use to determine if issues I
> come across are XQuartz specific or not... I've been using Fedora on
> it for a while, but jumped ship to Ubuntu because of some annoyances.
>
> With Ububntu, however, the r300 DRI driver is not being selected.
> It's falling back on swrast for some reason. I've bumped to trunk for
> libdrm, mesa, ati drivers.
>
> The Xorg.0.log is here:
> http://cloud.cs.berkeley.edu/~jeremy/ati-powerbook/Xorg.0.log
>
> And a successful log from under Fedora is here:
> https://bugzilla.redhat.com/attachment.cgi?id=341960
>
> Interesting log points:
> ...
> (==) RADEON(0): Backing store disabled
> (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 0xf3162000 at
> 0x48026000
> (II) RADEON(0): [drm] Closed DRM master.
> (WW) RADEON(0): Direct rendering disabled
> (II) RADEON(0): XAA Render acceleration unsupported on Radeon
> 9500/9700 and newer. Please use EXA instead.
> (II) RADEON(0): Render acceleration disabled
> (II) RADEON(0): num quad-pipes is 1
> (II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
> ...
> (II) AIGLX: Screen 0 is not DRI2 capable
> (II) AIGLX: Screen 0 is not DRI capable
> (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
> (II) GLX: Initialized DRISWRAST GL provider for screen 0
>
> Here is the start log with no xorg.conf (and the fbdev driver moved
> aside to prevent it complaining about needing busIDs):
> http://cloud.cs.berkeley.edu/~jeremy/ati-powerbook/Xorg.0.no_xorg.conf.no_fbdev.log
>
> It's not much different than the other log, but I figured I'd provide
> it anyways, since it should "just work"...
>
>
>
> 0000:00:10.0 VGA compatible controller [0300]: ATI Technologies Inc
> RV350 [Mobility Radeon 9600 M10] [1002:4e50]
> Subsystem: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
> [1002:4e50]
> 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 b8000000 (32-bit, prefetchable) [size=128M]
> Region 1: I/O ports at 0400 [size=256]
> Region 2: Memory at b0000000 (32-bit, non-prefetchable) [size=64K]
> Expansion ROM at f1000000 [size=128K]
> Capabilities: <access denied>
> Kernel driver in use: radeonfb
>
>
> _______________________________________________
> xorg-devel mailing list
> xorg-devel at lists.x.org
> http://lists.x.org/mailman/listinfo/xorg-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJ/f+mjC1Anjf1NmMRAgeFAJ9N9KALwd3cMyrgF1jtAiBjoA9UNgCeOTYD
DYgGfr258sv9UnzCWpTeU8c=
=A2+6
-----END PGP SIGNATURE-----
More information about the xorg-devel
mailing list