Re: [Dri-users] Lost direct renderig after upgradigng CVS

[<ign...@no...>]

ign...@no... dijo:   
   
>     
> After upgrading CVS, no direct rendering any more. This is from   
Xorg.0.log:    
>     
> (II) ATI(0): X context handle = 0x1    
> (II) ATI(0): [drm] installed DRM signal handler    
> (II) ATI(0): [DRI] installation complete    
> (II) ATI(0): [drm] Added 128 16384 byte DMA buffers    
> (EE) ATI(0): [drm] Failed to map DMA buffers list    
> (II) ATI(0): [drm] removed 1 reserved context for kernel    
> (II) ATI(0): [drm] unmapping 8192 bytes of SAREA 0xd4be8000 at 0x40d44000    
> (II) ATI(0): Direct rendering disabled    
>     
> After setting  LIBGL_DEBUG=verbose, glxinfo reports  this:    
>     
> name of display: :0.0    
> libGL error: XF86DRIQueryDirectRenderingCapable returned false    
> display: :0  screen: 0    
> direct rendering: No    
> server glx vendor string: SGI    
> server glx version string: 1.2    
>     
> (...)    
>     
> And dmesg | grep drm:    
>     
> [drm] Initialized drm 1.0.0 20040925    
> [drm] Initialized mach64 1.0.0 20020904 on minor 0:    
> [drm] Used old pci detect: framebuffer loaded    
> [drm] descriptor ring: cpu addr d4c24000, bus addr: 0xf4000000    
> [drm] DMA test succeeded, using asynchronous DMA mode    
>     
> As you can see, no mention to AGP, but lines about AGP look normal in    
> Xorg.0.log.    
>     
> Any idea?    
>     
> Should I report it as a bug in bugzilla?    
>     
> Thank you in advance.    
>     
>    
   
   
After upgrading CVS, the problem is still the same. I forgot to mention that 
startx output ended with "[drm] Failed to map DMA buffers list".   
   
In the former report, xorg.conf had the option "AgpSize" "64". Then, I have 
tried to set "AgpSize" "128" and the result is quite different:   
   
1) The end of startx output is "[agp] Could not bind"  
   
2) With the new option, glxinfo reports this:   
name of display: :0.0   
libGL: XF86DRIGetClientDriverName: 6.5.6 mach64 (screen 0)   
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/mach64_dri.so   
drmOpenByBusid: Searching for BusID pci:0000:01:00.0   
drmOpenDevice: node name is /dev/dri/card0   
drmOpenDevice: open result is 4, (OK)   
drmOpenByBusid: drmOpenMinor returns 4   
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0   
display: :0  screen: 0   
direct rendering: Yes   
   
3) Xorg.0.log:   
   
(II) ATI(0): [drm] Will request asynchronous DMA mode   
(**) ATI(0): [agp] Using AGP 2x Mode   
(**) ATI(0): [agp] Using 128 MB AGP aperture   
(II) ATI(0): [agp] Mode 0x1f000203 [AGP 0x8086/0x7190; Card 0x1002/0x4c4d]   
(II) ATI(0): [agp] 131072 kB allocated with handle 0x00000001   
(EE) ATI(0): [agp] Could not bind   
(WW) ATI(0): [agp] AGP failed to initialize -- falling back to PCI mode.   
(WW) ATI(0): [agp] Make sure you have the agpgart kernel module loaded.   
(II) ATI(0): [drm] register handle = 0xfcfff000   
   
(...)   
   
(II) ATI(0): X context handle = 0x1   
(II) ATI(0): [drm] installed DRM signal handler   
(II) ATI(0): [DRI] installation complete   
(II) ATI(0): [drm] Added 128 16384 byte DMA buffers   
(II) ATI(0): [drm] Mapped 128 DMA buffers at 0x40d46000   
(II) ATI(0): [drm] Installed interrupt handler, using IRQ 11   
(II) ATI(0): Direct rendering enabled   
   
Although it complains about agpgart, it is loaded before I run startx and it 
remains loaded later. intel-agp, drm and mach64 modules are also loaded.  
   
In few words:   
   
A) If AgpSize is set to 64, glxinfo reports libGL error and no direct 
rendering, Xorg.0.log reports "[drm] Failed to map DMA buffers list" and I 
can't see any problem with AGP.   
   
B) If AgpSize is set to 128, glxifo looks fine, Xorg.0.log reports no error 
about drm but it reports problems with AGP (see above).  
   
Why to complain if I have direct rendering anyway? Well, trying to use 
direct rendering is catastrophic: glxgears makes my X system completly 
unusable, and resetting X is not enough to  solve: I have to reset the whole 
computer. The same if I try to play the game gl-117. If I run the program 
gears, it is not that bad: its window remains black (no gears) but the 
pattern of the CPU monitor and the reported speed of gears program suggest 
me that I have direct rendering "working". If I moove any window while 
running gears, the screen is again unusable, but I can recover stopping 
gears, and no need to reset.  
This is from /var/log/kernel/errors when running gears:   
   
Aug 26 20:08:16 localhost kernel: [drm:mach64_ring_tick] *ERROR* bad ring   
head address: 0x00000000   
Aug 26 20:08:47 localhost last message repeated 217 times   
   
I send as an attached file a piece of /var/log/kernel/info when running 
gears for few seconds with AgpSize is set to 128.  
  
I have an ATI Rage Mobility-M AGP 2X (mach64 chip) with 8 MB memory in a 
Dell Inspiron 3700. Mandrake 10.1, kernel 2.6.8.1-25