Ya, I have an idea. You need to load the agpgart module before you load the r128 module. Like Michel Dänzer said, "The agpgart module needs to be loaded before the r128 kernel module or the latter can't use it." Do it like this: Shut down X modprobe -r apgart modprobe -r r128 modprobe agpgart modprobe r128 Then start X Problem solved. Thank you for the help and the gentle slap on the side of the head about loading the agpgart first. I was out taking my son's girl friend home when the enlightenment came. Duh! Load the agpgart first, then the r128. Their both kernel modules IDIOT. Some times I'm just so numb. Mark LaPierre In a message dated Fri, 26 Apr 2002 8:28:30 PM Eastern Daylight Time, MarkLapier@aol.com writes: >One again, thank you for your reply. Unfortunately, the agpgart module was in infact loaded before X was started. Since this is not my problem does any one else have any idea why AGP is failing to initialize? > >Here's the relevent clip from the XFree86.0.log: > >drmOpenDevice: open result is 7, (OK) >drmOpenDevice: minor is 0 >drmOpenDevice: node name is /dev/dri/card0 >drmOpenDevice: open result is 7, (OK) >drmOpenDevice: minor is 0 >drmOpenDevice: node name is /dev/dri/card0 >drmOpenDevice: open result is 7, (OK) >drmGetBusid returned '' >(II) R128(0): [drm] created "r128" driver at busid "PCI:1:0:0" >(II) R128(0): [drm] added 8192 byte SAREA at 0xd88a5000 >(II) R128(0): [drm] mapped SAREA 0xd88a5000 to 0x40018000 >(II) R128(0): [drm] framebuffer handle = 0xd4000000 >(II) R128(0): [drm] added 1 reserved context for kernel >(WW) R128(0): [agp] AGP not available >(WW) R128(0): [agp] AGP failed to initialize -- falling back to PCI mode. >(WW) R128(0): [agp] Make sure you have the agpgart kernel module loaded. >(II) R128(0): [pci] 8192 kB allocated with handle 0xd98bf000 >(II) R128(0): [pci] ring handle = 0xd98bf000 >(II) R128(0): [pci] Ring mapped at 0x4122e000 >(II) R128(0): [pci] Ring contents 0x00000000 >(II) R128(0): [pci] ring read ptr handle = 0xd99c0000 >(II) R128(0): [pci] Ring read ptr mapped at 0x4001a000 >(II) R128(0): [pci] Ring read ptr contents 0x00000000 >(II) R128(0): [pci] vertex/indirect buffers handle = 0xd99c1000 >(II) R128(0): [pci] Vertex/indirect buffers mapped at 0x4132f000 >(II) R128(0): [pci] Vertex/indirect buffers contents 0x00000000 >(II) R128(0): [drm] register handle = 0xd9000000 >(II) R128(0): [dri] Visual configs initialized >(II) R128(0): CCE in BM mode >(II) R128(0): Using 8 MB AGP aperture >(II) R128(0): Using 1 MB for the ring buffer >(II) R128(0): Using 2 MB for vertex/indirect buffers >(II) R128(0): Using 5 MB for AGP textures >(II) R128(0): Memory manager initialized to (0,0) (1024,3840) >(II) R128(0): Reserved area from (0,768) to (1024,770) >(II) R128(0): Largest offscreen area available: 1024 x 3070 >(II) R128(0): Reserved back buffer from (0,770) to (1024,1538) >(II) R128(0): Reserved depth buffer from (0,1538) to (1024,2307) >(II) R128(0): Reserved depth span from (0,2306) offset 0x481000 >(II) R128(0): Reserved 8704 kb for textures at offset 0x780000 >(==) R128(0): Backing store disabled >(==) R128(0): Silken mouse enabled >(II) R128(0): Using XFree86 Acceleration Architecture (XAA) > Screen to screen bit blits > Solid filled rectangles > 8x8 mono pattern filled rectangles > Solid Lines > Dashed Lines > Offscreen Pixmaps > Setting up tile and stipple cache: > 32 128x128 slots > 14 256x256 slots >(II) R128(0): Acceleration enabled >(II) R128(0): Using hardware cursor (scanline 4614) >(II) R128(0): Largest offscreen area available: 1024 x 1531 >(**) Option "dpms" >(**) R128(0): DPMS enabled >(II) R128(0): X context handle = 0x00000001 >(II) R128(0): [drm] installed DRM signal handler >(II) R128(0): [DRI] installation complete >(II) R128(0): [drm] Added 128 16384 byte vertex/indirect buffers >(II) R128(0): [drm] Mapped 128 vertex/indirect buffers >(II) R128(0): Direct rendering enabled > > >In a message dated Fri, 26 Apr 2002 12:48:21 PM Eastern Daylight Time, Michel Dänzer <michel@daenzer.net> writes: > >>On Fri, 2002-04-26 at 17:58, MarkLapier@aol.com wrote: >>> In a message dated Fri, 26 Apr 2002 8:46:29 AM Eastern Daylight Time, Michel Dänzer <michel@daenzer.net> writes: >>> >>> >On Wed, 2002-04-24 at 08:09, MarkLapier@aol.com wrote: >>> >> >>> >> I'm having a problem with AGP initialaizing. I did modprobe -r >>> >> agpgart, depmod -a, and modprobe agpgart to reload the module. That didn't fix the problem. >>> > >>> >The agpgart module needs to be loaded before the r128 kernel module or >>> >the latter can't use it. >>> > >>> >It's a good idea to build agpgart into the kernel in general as loading >>> >the module can fail due to memory fragmentation. >>> >>> Thank you Michel. If the module failed to load wouldn't that be reported by modprobe -v ? >>> >>> [root@tire /root]# modprobe -rv agpgart >>> # delete agpgart >>> [root@tire /root]# depmod -a >>> [root@tire /root]# modprobe -v agpgart >>> /sbin/insmod /lib/modules/2.4.9-31/kernel/drivers/char/agp/agpgart.o >>> Using /lib/modules/2.4.9-31/kernel/drivers/char/agp/agpgart.o >>> Symbol version prefix '' >>> [root@tire /root]# >>> >>> I don't see where there is any problem reported with the module load. >>> That might be because I don't know what to look for. Do you see a >>> problem with what is reported here? >> >>That was just a general hint, I didn't imply it was your problem. >> >>Your problem probably was that agpgart wasn't loaded when r128 got >>loaded. >> >> >>-- >>Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer >>XFree86 and DRI project member / CS student, Free Software enthusiast >>_______________________________________________ >>Xpert mailing list >>Xpert@XFree86.Org >>http://XFree86.Org/mailman/listinfo/xpert >> > > >-- >Mark LaPierre > >_______________________________________________ >Xpert mailing list >Xpert@XFree86.Org >http://XFree86.Org/mailman/listinfo/xpert > -- Mark LaPierre
