On 24. March 2004 at 10:51AM +0100, Frank Gevaerts <[EMAIL PROTECTED]> wrote:
> 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? [...] > 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. Well I compiled it in and it didn't make a difference. On hindsight I think it would be suprising if it did make a difference. I had "radeonfb" compiled as a module for both 2.4 and 2.6. And for both kernels I don't have "radeonfb: loaded. Or I could unload it while X is running > > 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 ? This is the best I can come up with: $ grep -A 10 'Option "dri" is not used' kernel-2.6-XFree86.0.log (WW) RADEON(0): Option "dri" is not used (II) RADEON(0): Direct rendering disabled (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA $ grep -A 10 'Option "dri" is not used' kernel-2.4-XFree86.0.log (WW) RADEON(0): Option "dri" is not used (II) RADEON(0): X context handle = 0x00000001 (II) RADEON(0): [drm] installed DRM signal handler (II) RADEON(0): [DRI] installation complete (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers (II) RADEON(0): [drm] dma control initialized, using IRQ 11 (II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808 (II) RADEON(0): Direct rendering enabled (==) RandR enabled (II) Initializing built-in extension MIT-SHM Apparently with kernel 2.6 DRI is disabled after the driver detects that DRI is not being used. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
