[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Today's rawhide xorg/radeon

David Woodhouse wrote:

Yes, it's enabled in rawhide, with some checks on the X server to make
sure it's new enough.

OK, using kernel 2121_FC6 looks better, all the DRI errors previously reported are gone, here are snippets from Xorg.0.log

(II) RADEON(0): PCIE card detected
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
(WW) RADEON(0): Enabling DRM support
(II) RADEON(0): [drm] DRM interface version 1.2
(II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0"
(**) RADEON(0): DRI Finishing init !
(II) RADEON(0): [drm] installed DRM signal handler
(II) RADEON(0): [DRI] installation complete
(II) RADEON(0): Direct rendering enabled
(**) RADEON(0): Setting up final surfaces
(**) RADEON(0): Initializing Acceleration
(II) RADEON(0): Render acceleration unsupported on Radeon 9500/9700 and newer.
(II) RADEON(0): Render acceleration disabled

and although GL apps run they are still using CPU horsepower rather than GPU, is there any setting which will "convince" the driver to try to use h/w acceleration?

It'll also be enabled in the 2085 and later kernels if you use the
'allow_r300' module parameter when loading radeon.ko.

is 2085 a candidate for FC5 updates? (via updates-testing)

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]