> > That's strange, most of the lines about dri and drm are OK (begin with > "(II)"). But there is only one failure in XFree86.1.log : > > (==) R128(0): Write-combining range (0xe4000000,0x1000000) > (II) R128(0): [drm] drmSetBusid failed (6, PCI:1:0:0) > > (EE) R128(0): [dri] DRIScreenInit failed. Disabling DRI.
Yes, this means that DRI and DRM are not being initialized. I had the same problem, but I can't remember the exact steps I took to resolve it. I beleive you need to load the module 'agpgart' if it is not already built into the kernel, and then load your agp chipset module 'via-agp' if that is the correct one. > > The chipset driver wasn't loaded (I thought that CONFIG_KMOD=1 > automatically loads needed modules in the kernel). > I'm not sure :) But make sure you did a make modules_install as root, that should set up the module dependencies properly. > So I loaded the module via-agp (I've got a VIA apollo KT266 series > mainboard, so I guess it's the right module) with insmod (modprobe > surprisingly doesn't work with the kernel 2.6.8), restarted the X server. > But the error persists. > > I also tried amd-k7-agp and ati-agp modules. > After you have loaded the module, check the output of dmesg to see if it successfully detected your chipset. I get something like: agpgart: Detected AMD Irongate chipset agpgart: Maximum main memory to use for agp memory: 176M agpgart: AGP aperture is 64M @ 0xe8000000 ... agpgart: Found an AGP 1.0 compliant device at 0000:00:00.0. agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode agpgart: Putting AGP V2 device at 0000:01:05.0 into 1x mode -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
