On Thu, 7 Oct 2004 11:22:01 -0500, Jacob S <[EMAIL PROTECTED]> wrote: > On Thu, 07 Oct 2004 09:52:14 +0200 > Dominique Dumont <[EMAIL PROTECTED]> wrote: > > > Jacob S <[EMAIL PROTECTED]> writes: > > > > > I'm running the latest updates in Sarge, with a 2.6.7-1-k7 kernel. > > > I've modprobed agpgart and nvidia_agp, which according to the logs > > > recognize the agp bridge on the motherboard. > > > > You also have to load a radeon module *after* the agpgart > > module. Here's What I use in my modutils: > > > > # load agpgart before radeon so DRI can work > > # when X11 is launched > > add below radeon agpgart > > Thanks, but X11 is already doing this for me. I am loading agpgart and > nvidia_agp via modprobe, and then have a driver line in > /etc/X11/XF86Config-4 to tell X to use the radeon driver. After I load > X, I can do a lsmod and see that the radeon module is loaded. This is > also the same method I use on the computer that's successfully using a > Radeon 9200SE right now. > > Investigating the problem a little more, it seems the lack of dri > support is due to the following errors in dmesg. But google doesn't seem > to be helping much there either; all the hits it returns seem to be > unrelated to my problem. I've also tried upgrading to 2.6.8-1-k7, > instead of 2.6.7, but it returns the same errors in dmesg. > > mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x200000 > mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x200000 > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held > [drm:radeon_unlock] *ERROR* Process 2157 using kernel context 0 > > Does anyone have any more suggestions? >
Yes, use "ati" instead of "radeon" on your XF86Config-4... Andrea -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
