[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: dri disabled

Okay, I should mention that I recompiled the kernel myself, I suppose
it's possible I mucked that up.

>  Can you run "uname -a" just to confirm that it really is that kernel
> that's being booted?

cnkeller $ uname -r

>  Are you *absolutely* sure that the module you're trying to load is
> the correct one?  The .config file(s) for kernel RPM 2.4.9-13 are all
> correctly set up to build the DRM module for XFree86-4.1, so there is
> something wrong somewhere (I know, you'd noticed :o)


>  Can you try "rpm -V kernel-2.4.9-13" to see if anything's overwritten
> the module (unlikely) and "rpm -V XFree86" too?

Hmmm...I don't claim to be a graphics expert, but the following line
makes me nervous.

cnkeller $ rpm -V kernel-2.4.9-13 | grep radeon
missing    /lib/modules/2.4.9-13/kernel/drivers/char/drm/radeon.o
missing    /lib/modules/2.4.9-13/kernel/drivers/video/radeonfb.o

I'm going to go out on a limb here, you guys just bear with
me....somehow I managed to unconfigure some graphics stuff when I
recompiled my kernel. 

The radeonfb I actually compiled into the kernel, so I don't expect the
module to be there. I wasn't able to get console framebuffers working
without compiling the radeonfb directly into the kernel; I really like
the penguin on bootup. If anyone knows how to get that working as a
module, I'm all ears.

I do have this though

cnkeller $ locate radeon.o

I'm not sure what the difference is between drm and drm-4.0, but it's
pretty obivous that it was there in a previous kernel.

Long story short, me thinks that I need to re-check my .config file for
the kernel.....????

Christopher Keller
Systems Engineer
BeamReach Networks -- Sunnyvale, CA

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]