Gentoo Archives: gentoo-user

From: Mark Knecht <markknecht@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: No HW acceleraton on radeon Mobility X300 with linux-2.6.36-r5, mesa-7.9, xorg-server-1.9.2 and video-ati-6.13.2
Date: Tue, 18 Jan 2011 01:14:47
Message-Id: AANLkTi=8qibHvprCO8hSpjd7aaZ63G=7UBu9JuuBawHn@mail.gmail.com
In Reply to: Re: [gentoo-user] Re: No HW acceleraton on radeon Mobility X300 with linux-2.6.36-r5, mesa-7.9, xorg-server-1.9.2 and video-ati-6.13.2 by Daniel Tihelka
1 On Mon, Jan 17, 2011 at 2:31 PM, Daniel Tihelka <dtihelka@×××××.com> wrote:
2 > Hallo  Mick.
3 > Thank you very much - it helped. Removing 'video=vesafb:ywrap,mtrr:3
4 > vga=792'
5 > from kernel boot options, and framebuffer-related stuff in kernel config,
6 > especially:
7 >
8 > # CONFIG_FB_DDC is not set
9 > # CONFIG_FB_BOOT_VESA_SUPPORT is not set
10 > # CONFIG_FB_BACKLIGHT is not set
11 > # CONFIG_FB_MODE_HELPERS is not set
12 > # CONFIG_FB_TILEBLITTING is not set
13 > # CONFIG_FB_VESA is not set
14 > # CONFIG_FB_RADEON is not set
15 > # CONFIG_DISPLAY_SUPPORT is not set
16 > # CONFIG_VGACON_SOFT_SCROLLBACK is not set
17 > # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
18 >
19 > (not all the options were removed by hand, it is just diff of the configs,
20 > and
21 > maybe, some of them could be enabled without causing problems).
22 >
23 > Now, there are much more 'drm'-related messages in 'dmesg', and also X.org
24 > uses the drm correctly. The 'glxinfo' returns:
25 > ...
26 > OpenGL vendor string: X.Org R300 Project
27 > OpenGL renderer string: Gallium 0.4 on RV370
28 > OpenGL version string: 2.1 Mesa 7.9
29 > OpenGL shading language version string: 1.20
30 > ...
31 >
32 > It looks good now. Thank you very much for your advice again.
33 > Dan
34 >
35 > On Sunday 16 January 2011 16:52:30 Mick wrote:
36 >> On Sunday 16 January 2011 15:18:50 Daniel Tihelka wrote:
37 >> > And the kernel seems to use them (when started with boot options
38 >>
39 >> > 'video=vesafb:ywrap,mtrr:3 vga=792'):
40 >> Dan, try removing uvesa/vesa/radeon/etc. framebuffer modules from your
41 >> kernel and the above line too from grub when you boot and see if your KMS
42 >> radeon driver can now work on its own.
43 >
44
45 Daniel,
46 I'm seeing the same problem here and trying to follow my way
47 through your kernel config changes. I don't think I have it yet on
48 this box as I'm seeing a message about rendering being disabled in
49 Xorg.log.0
50
51 c2stable ~ # cat /var/log/Xorg.0.log | grep render
52 [ 29.017] (WW) RADEON(0): Direct rendering disabled
53 c2stable ~ #
54
55
56 even though glxinfo says it's enabled:
57
58 c2stable ~ # glxinfo | grep render
59 direct rendering: Yes
60 OpenGL renderer string: Gallium 0.4 on softpipe
61 GL_NV_blend_square, GL_NV_conditional_render, GL_NV_light_max_exponent,
62 c2stable ~ #
63
64 Anyway, I'm sure I'll figure it out but I'm curious how you measure
65 that it's working up to it's potential. I'm getting less than 200FPS
66 in glxgears. I get >2500 on a cheaper nvidia card so I'm certain this
67 Radeon 300 can do better.
68
69 What do you see in glxgears?
70
71 Thanks,
72 Mark

Replies