On Wed, Mar 24, 2004 at 08:44:09AM +0800, csj wrote: > 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: > > > > 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!
You can compile in more than one fb driver. If there is no radeon card, the radeonfb driver just won't be used. I wouldn't be surprised if this makes a difference. > 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. Looks like X is not using dri then. Did you look for errors in /var/log/XFree86.log, or in the dmesg output ? Frank -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
