This one is due to the way AGPGART does (or has done for the last 3
years) its module locking. It does a MOD_INC_USE_COUNT as soon as
someone calls the acquire routines. (So you can't unload agpgart
whilst you've a 3d using app (like X) open).
This seems quite sensible, but these days you can't unload agpgart.ko
anyway because the chipset module (via-agp.ko in your case) already
has it 'in use', so I'm tempted to drop those bits.
> but find this in the X startup log.
> (EE) MGA: Failed to load module "mga_hal" (module does not exist, 0)
That's matrox's binary only X blob. Not my fault.
> (EE) MGA(0): [agp] Out of memory (-1014)
This one is. But it may be a knock-on effect from the bug above.
I'll nail that one first.
> (EE) MGA(0): [drm] failed to remove DRM signal handler
> DRIUnlock called when not locked
That one's a problem for the DRI folks.
Dave
-- | Dave Jones. http://www.codemonkey.org.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/