Bug 25707 - Problems with DRI on ATI Radeon HD3850
Summary: Problems with DRI on ATI Radeon HD3850
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2009-12-18 05:34 UTC by Maxim
Modified: 2009-12-18 12:25 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

xorg.conf (3.39 KB, text/plain)
2009-12-18 05:34 UTC, Maxim
no flags Details
Xorg.0.log (52.12 KB, text/plain)
2009-12-18 05:35 UTC, Maxim
no flags Details
glxinfo (18.69 KB, text/plain)
2009-12-18 05:37 UTC, Maxim
no flags Details
lspci (1.78 KB, text/plain)
2009-12-18 05:37 UTC, Maxim
no flags Details
dmesg (65.10 KB, text/plain)
2009-12-18 11:51 UTC, Maxim
no flags Details

Description Maxim 2009-12-18 05:34:39 UTC
Created attachment 32173 [details]

I`m using Gentoo and i have problems starting hardware acceleration on my video card. I use -9999 version of xorg-server, mesa, libdrm, xf86-video-ati and some more libraries and protocols. And I have kernel 2.6.32-gentoo. glxinfo says that it is Software Rasterizer, but i want to get hardware acceleration. More info in attachments (xorg.conf, Xorg.0.log, lspci, glxinfo)
P.S I used advices in this article: http://en.gentoo-wiki.com/wiki/Radeon, but it didn`t helped. Some discussion of this is here: http://www.gentoo.ru/node/17754, but it`s in Russian and it`ll probably be useless for you.
Comment 1 Maxim 2009-12-18 05:35:30 UTC
Created attachment 32174 [details]
Comment 2 Maxim 2009-12-18 05:37:19 UTC
Created attachment 32175 [details]
Comment 3 Maxim 2009-12-18 05:37:49 UTC
Created attachment 32176 [details]
Comment 4 Rafał Miłecki 2009-12-18 06:38:47 UTC
Important part:

(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) RADEON(0): [drm] Using the DRM lock SAREA also for drawables.
(II) RADEON(0): [drm] framebuffer handle = 0xe8000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(II) RADEON(0): X context handle = 0x1
(II) RADEON(0): [drm] installed DRM signal handler
(WW) RADEON(0): [agp] AGP not available
(EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI.
(II) RADEON(0): [agp] You may want to make sure the agpgart kernel module
is loaded before the radeon kernel module.
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xf8025000 at 0xb714e000
(II) RADEON(0): [drm] Closed DRM master.
(II) RADEON(0): RADEONRestoreMemMapRegisters() : 
(II) RADEON(0):   MC_FB_LOCATION   : 0x010700e8 0x00ff00e0
(II) RADEON(0):   MC_AGP_LOCATION  : 0x003f0000
(==) RADEON(0): Backing store disabled
(WW) RADEON(0): Direct rendering disabled
(EE) RADEON(0): Acceleration initialization failed
(II) RADEON(0): Acceleration disabled
Comment 5 Maxim 2009-12-18 06:51:15 UTC
You mean this line:
"(II) RADEON(0): [agp] You may want to make sure the agpgart kernel module
is loaded before the radeon kernel module." I`m sure that agpgart is loaded before radeon. Here`s my /etc/modules.autoload.d/kernel-2.6:
# /etc/modules.autoload.d/kernel-2.6: kernel modules to load when system boots.
# Note that this file is for 2.6 kernels.
# Add the names of modules that you'd like to load when the system
# starts into this file, one per line. Comments begin with # and
# are ignored. Read man modules.autoload for additional details.

# For example:
# aic7xxx


Comment 6 Alex Deucher 2009-12-18 07:54:09 UTC
Please attach your dmesg.
Comment 7 Maxim 2009-12-18 11:51:03 UTC
Created attachment 32180 [details]
Comment 8 Maxim 2009-12-18 11:55:05 UTC
I think problem is here:
    0.234229] uvesafb: failed to execute /sbin/v86d
[    0.234238] uvesafb: make sure that the v86d helper is installed and executable
[    0.234246] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2)
[    0.234252] uvesafb: vbe_init() failed with -22
[    0.234261] uvesafb: probe of uvesafb.0 failed with error -22
[    0.234556] vesafb: framebuffer at 0xe8000000, mapped to 0xf8080000, using 10240k, total 16384k
[    0.234564] vesafb: mode is 1280x1024x32, linelength=5120, pages=2
[    0.234569] vesafb: protected mode interface info at c000:a176
[    0.234575] vesafb: pmi: set display start = c00ca218, set palette = c00ca2d6
[    0.234580] vesafb: scrolling: redraw
[    0.234585] vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0

Vesa says that framebuffer is mapped to 0xf8080000, but xorg still wants to acces it from 0xe8000000 or i don`t understand this thing.
Comment 9 Alex Deucher 2009-12-18 11:58:29 UTC
The agp kernel module for your chipset doesn't seem to be loaded.  You system has an Intel AGP bridge so it should be using the intel agp module.
Comment 10 Maxim 2009-12-18 12:12:22 UTC
OK. I have found  it too. I had enabled ati chipset in the kernel. And now i enabled intel chipset anb all works fine. glxgears show ~1100 fps and ut2004-demo goes with little count of lags. Excuse me for disturbing you.
P.S. Sorry for my bad English -- i`m 15 years old student from Russia.
Comment 11 Rafał Miłecki 2009-12-18 12:25:31 UTC
No problem, great you've this working now :)

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.