To answer my own question, it turns out that (for my system, at least) the
agp.ko module *must not be preloaded* with loader.conf.  Commenting
agp_load="YES" out of /boot/loader.conf fixed all three problems listed

On Sun, 11 Jan 2004, David Fleck wrote:
> 4.9-RELEASE-p1.
> At boot, the agp module appears to load OK:
> # dmesg | grep agp
> Preloaded elf module "agp.ko" at 0xc03d336c.
> agp0: <VIA Generic host to PCI bridge> mem 0xe0000000-0xe7ffffff at device
> 0.0 on pci0
> agp0: allocating GATT for aperture of size 256M
> However, when starting X, the kernel spits out this message:
> /kernel: error: [drm:radeon_unlock] *ERROR* Process 265 using kernel
> context 0
> There is no such process when I look, of course...  the relevant section
> of the XFree86 log is:
> (II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:0:0"
> (II) RADEON(0): [drm] added 8192 byte SAREA at 0xc22ce000
> (II) RADEON(0): [drm] mapped SAREA 0xc22ce000 to 0x28279000
> (II) RADEON(0): [drm] framebuffer handle = 0xd8000000
> (II) RADEON(0): [drm] added 1 reserved context for kernel
> (WW) RADEON(0): [agp] AGP not available
> (II) RADEON(0): [drm] removed 1 reserved context for kernel
> (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xc22ce000 at
> 0x28279000
> (II) RADEON(0): Memory manager initialized to (0,0) (1024,8191)
> I'm assuming there's some relationship between (a) the kernel warning
> message, (b) the 'AGP not available' message, and (c) the fact that DRI
> doesn't work anymore (it did before I upgraded from 4.6.2 to 4.9).  Can
> anyone think of where to look to figure this out?

David Fleck

[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to