Fernando Meira schreef:
> On 10/10/05, Jason Cooper <[EMAIL PROTECTED]> wrote:
>
>> Fernando Meira ([EMAIL PROTECTED] ) scribbled:
>>
>>> I think I have radeon driver built-in the kernel.. does that mean
>>> that
>>
>> it is
>>
>>> loaded before agpgart? agpgart and intel_agp are both modules...
>>>
>>> should I them recompile my kernel and leave radeon as module?
>>
>> yes.
>
>
>
> Ok, with this modules being loaded at boot: agpgart intel_agp radeon
>
> I still don't have rendering! So, should I try to compile all
> built-in the kernel? Or should I go for x11-drm?
>
> Cheers, Fernando
>
I'm not sure I understand what you're doing here.
As far as I know (and I must stress that I'm not that familiar with
either the radeon driver or how it works with the Mobility chips,
because I have a 9800SE that must use the fglrx drivers to get OpenGL/3D
hardware acceleration/direct rendering), the radeon driver is a 2D
driver that is used in combination with the kernel's DRM and the Mesa
libraries to get direct rendering/3D hardware acceleration enabled.
So my first question would be:
What is the status of DRM in your kernel?
Device Drivers=>Character Devices=>Direct Rendering Manager (XFree86
4.1.0 and higher DRI support)
It was DRM [=m].
All (agpgart, inter_agp, DRM, radeon) were [M].
Now, I know that for the fglrx drivers to run, this kernel option must
be *unset*, but it's clear that you can't even have the 'radeon' module
if DRM is not set. However, in looking at these settings in my own
kernel (and assuming that the Mobility chipset in your lappy can use
these drivers to provide 3D hardware acceleration), I noticed that:
- when I had /dev/agpgart set as a module, I could only build DRM as a
module (the kernel gave me a message to this effect);
- setting /dev/agpgart to statically compiled (Y) allowed me to build
DRM statically compiled (but I could still build Radeon as a module, and
intel_agp as a module under agpgart).
Again, I'm no big expert on the radeon kernel drivers, but I find it
hard to believe that in this situation it can be a good thing for
/dev/agpgart and /DRM themselves to be compiled as loadable modules
rather than statically (although the sub-functions, intel_agp and
radeon, most likely *should* be compiled as modules).
So I would suggest that your kernel config "should" look like this:
<*> /dev/agpgart (AGP Support)
< > ALI chipset support
< > ATI chipset support
< > AMD Irongate, 761, and 762 chipset support
< > AMD Opteron/Athlon64 on-CPU GART support
<M> Intel 440LX/BX/GX, I8xx and E7x05 chipset support
< > NVIDIA nForce/nForce2 chipset support
< > SiS chipset support
< > Serverworks LE/HE chipset support
< > VIA chipset support
< > Transmeta Efficeon support
<*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
< > 3dfx Banshee/Voodoo3+ (NEW)
< > ATI Rage 128 (NEW)
<M> ATI Radeon
< > Intel I810 (NEW)
< > Intel 830M, 845G, 852GM, 855GM, 865G
< > Matrox g200/g400 (NEW)
< > SiS video cards (NEW)
Ok, so I do as you say, change agpgart and DRM to be statically and leave inter_agp and radeon as modules.
Exactly as you mention.
For what it's worth. You could then take agpgart out of
/etc/modules.autoload.d/kernel- 2.6 (since it's no longer a loadable
module, you can't load it that way anyway. but then intel_agp should
hopefully load correctly).
Yes... done!
You would perhaps also want to check your build of xorg:
emerge -pv xorg-x11
Yes, I have opengl USE flag active and xorg-x1 compiled with it.
Hope this helps,
Holly
Well, I really appreciate it, but it's still not working. All the same, no errors and no rendering.
Xorg.0.log does not report any error, dmesg reports:
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
and lsmod:
radeon 60800 1
intel_agp 15260 1
So.. don't know what can be wrong...
To add: now I lost the booting report!! After disabling DRM, FM support (vesa-fb + ati + ddc/I2C) for trying fglrx driver.. I can't get back the booting screen.. just a black screen from Grub to login manager.. The funny part is that I re-set all these kernel option.. well, all less one, support for FB splash (inside /Device Drivers/Graphics Support/Support for framebuffer devices/), which I can't find anymore.. weird.. very weird...
any clue? to any of the problems?
Thanks,
Fernando
