1 |
Fernando Meira schreef: |
2 |
> On 10/10/05, Jason Cooper <gentoo@××××××××××.net> wrote: |
3 |
> |
4 |
>> Fernando Meira (fmeira@×××××.com) scribbled: |
5 |
>> |
6 |
>>> I think I have radeon driver built-in the kernel.. does that mean |
7 |
>>> that |
8 |
>> |
9 |
>> it is |
10 |
>> |
11 |
>>> loaded before agpgart? agpgart and intel_agp are both modules... |
12 |
>>> |
13 |
>>> should I them recompile my kernel and leave radeon as module? |
14 |
>> |
15 |
>> yes. |
16 |
> |
17 |
> |
18 |
> |
19 |
> Ok, with this modules being loaded at boot: agpgart intel_agp radeon |
20 |
> |
21 |
> I still don't have rendering! So, should I try to compile all |
22 |
> built-in the kernel? Or should I go for x11-drm? |
23 |
> |
24 |
> Cheers, Fernando |
25 |
> |
26 |
|
27 |
I'm not sure I understand what you're doing here. |
28 |
|
29 |
As far as I know (and I must stress that I'm not that familiar with |
30 |
either the radeon driver or how it works with the Mobility chips, |
31 |
because I have a 9800SE that must use the fglrx drivers to get OpenGL/3D |
32 |
hardware acceleration/direct rendering), the radeon driver is a 2D |
33 |
driver that is used in combination with the kernel's DRM and the Mesa |
34 |
libraries to get direct rendering/3D hardware acceleration enabled. |
35 |
|
36 |
So my first question would be: |
37 |
|
38 |
What is the status of DRM in your kernel? |
39 |
|
40 |
Device Drivers=>Character Devices=>Direct Rendering Manager (XFree86 |
41 |
4.1.0 and higher DRI support) |
42 |
|
43 |
Direct Rendering Manager (XFree86 4.1.0 and higher DRI support |
44 |
x CONFIG_DRM: |
45 |
|
46 |
x |
47 |
|
48 |
x Kernel-level support for the Direct Rendering Infrastructure (DRI) |
49 |
x introduced in XFree86 4.0. If you say Y here, you need to select |
50 |
x the module that's right for your graphics card from the list below. |
51 |
x These modules provide support for synchronization, security, and |
52 |
x DMA transfers. Please see <http://dri.sourceforge.net/> for more |
53 |
x details. You should also select and configure AGP |
54 |
|
55 |
x (/dev/agpgart) support. |
56 |
|
57 |
x |
58 |
|
59 |
x Symbol: DRM [=m] |
60 |
x Prompt: Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) |
61 |
x Defined at drivers/char/drm/Kconfig:7 |
62 |
x Depends on: AGP || AGP=n |
63 |
x Location: |
64 |
x -> Device Drivers |
65 |
x -> Character devices |
66 |
x |
67 |
|
68 |
|
69 |
Now, I know that for the fglrx drivers to run, this kernel option must |
70 |
be *unset*, but it's clear that you can't even have the 'radeon' module |
71 |
if DRM is not set. However, in looking at these settings in my own |
72 |
kernel (and assuming that the Mobility chipset in your lappy can use |
73 |
these drivers to provide 3D hardware acceleration), I noticed that: |
74 |
|
75 |
- when I had /dev/agpgart set as a module, I could only build DRM as a |
76 |
module (the kernel gave me a message to this effect); |
77 |
|
78 |
- setting /dev/agpgart to statically compiled (Y) allowed me to build |
79 |
DRM statically compiled (but I could still build Radeon as a module, and |
80 |
intel_agp as a module under agpgart). |
81 |
|
82 |
Again, I'm no big expert on the radeon kernel drivers, but I find it |
83 |
hard to believe that in this situation it can be a good thing for |
84 |
/dev/agpgart and /DRM themselves to be compiled as loadable modules |
85 |
rather than statically (although the sub-functions, intel_agp and |
86 |
radeon, most likely *should* be compiled as modules). |
87 |
|
88 |
So I would suggest that your kernel config "should" look like this: |
89 |
|
90 |
<*> /dev/agpgart (AGP Support) |
91 |
< > ALI chipset support |
92 |
< > ATI chipset support |
93 |
< > AMD Irongate, 761, and 762 chipset support |
94 |
< > AMD Opteron/Athlon64 on-CPU GART support |
95 |
<M> Intel 440LX/BX/GX, I8xx and E7x05 chipset support |
96 |
< > NVIDIA nForce/nForce2 chipset support |
97 |
< > SiS chipset support |
98 |
< > Serverworks LE/HE chipset support |
99 |
< > VIA chipset support |
100 |
< > Transmeta Efficeon support |
101 |
<*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) |
102 |
< > 3dfx Banshee/Voodoo3+ (NEW) |
103 |
< > ATI Rage 128 (NEW) |
104 |
<M> ATI Radeon |
105 |
< > Intel I810 (NEW) |
106 |
< > Intel 830M, 845G, 852GM, 855GM, 865G |
107 |
< > Matrox g200/g400 (NEW) |
108 |
< > SiS video cards (NEW) |
109 |
|
110 |
For what it's worth. You could then take agpgart out of |
111 |
/etc/modules.autoload.d/kernel-2.6 (since it's no longer a loadable |
112 |
module, you can't load it that way anyway. but then intel_agp should |
113 |
hopefully load correctly). |
114 |
|
115 |
You would perhaps also want to check your build of xorg: |
116 |
|
117 |
emerge -pv xorg-x11 |
118 |
|
119 |
These are the packages that I would merge, in order: |
120 |
|
121 |
Calculating dependencies ...done! |
122 |
[ebuild R ] x11-base/xorg-x11-6.8.2-r4 -3dfx +3dnow +bitmap-fonts |
123 |
-cjk -debug -dlloader -dmx -doc +font-server -insecure-drivers -ipv6 |
124 |
-minimal +mmx +nls -nocxx +opengl -pam -sdk +sse -static +truetype-fonts |
125 |
+type1-fonts (-uclibc) +xprint +xv 0 kB |
126 |
|
127 |
As you see, opengl support is *optional*, and if not compiled, |
128 |
presumably the Mesa libraries that allow X to render 3D for those |
129 |
drivers that don't do so natively would also not be available. |
130 |
|
131 |
|
132 |
Hope this helps, |
133 |
Holly |
134 |
-- |
135 |
gentoo-user@g.o mailing list |