On 17. March 2004 at 12:29AM +0800, csj <[EMAIL PROTECTED]> wrote: > On 15. March 2004 at 5:04PM +0100, > Frank Gevaerts <[EMAIL PROTECTED]> wrote: > > > On Mon, Mar 15, 2004 at 12:02:26PM +0800, csj wrote: > > > For some reason I can't get DRI to work for my Radeon VE (7000) > > > under linux 2.6 using the debs from: > > > > > > http://people.debian.org/~daenzer/dri-trunk-sid/ > > > > > > The same debs work fine under any linux 2.4 version. > > > > > > Can somebody confirm if dri-trunk (especially from the above > > > site) works with linux 2.6? I'm just looking for a success story > > > to inspire me to continue wrestling with the beast. > > > > I don't know if this will help you, but it works for me on > > powerpc with a Radeon Mobility M6 (should be about the same as > > a 7000). The only difference I see is that I have radeonfb > > compiled in. In case it matters, I only use > > xlibmesa-gl1-dri-trunk and xserver-xfree86-dri-trunk, not the > > drm-trunk modules (the kernel driver is up to date in 2.6). My > > PC with a radeon 7000 is still on 2.4 for now. > > Okay, I removed drm-trunk so I can use the "native" 2.6 driver. > But still no DRI. Since my radeonfb is a module, I tried > modprobe'ing radeonfb but I get an error message like "cannot > reserve FB region". Does radeonfb have to be compiled in? Does > it make a difference if I have only generic vesa FB support? > > $ grep VESA /boot/config-2.6.4* > CONFIG_FB_VESA=y > > As much as possible I like all the brand-specific (non-generic) > drivers compiled as modules. I plan to use the exact same kernel > on my other machine which has an nVidia card (which has working > DRI/GLX using the nVidia binary drivers). Thanks!
I just found out something suspicious with the radeon kernel module in 2.6. I could rmmod it even when X is running! Under 2.4, I get a resource busy error. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
