Re: [Dri-users] Further DRI problems with a SuperSavage IX/16

[Alex D. <ale...@gm...>]

On Wed, 23 Mar 2005 20:41:41 +0000, yc...@uc... <yc...@uc...> wrote:
> I am trying to get Fedora Core 4 Test 1 installed on my IBM T23, which has a
> 2.6.11 kernel and Xorg X11 6.8.2. My first problems were solved by recompiling
> the kernel without DRM. Now the module compiles fine, giving the following
> errors on loading:
> 
> PCI: Unable to reserve mem region #2:4000000@e8000000 for device 0000:01:00.0
> mtrr: 0xe8000000,0x4000000 overlaps existing 0xe8000000,0x1000000
> mtrr: base(0xe4000000) is not aligned on a size(0x5000000) boundary
> [drm] Initialized savage 2.4.1 20050313 on minor 0:
> [drm] Used old pci detect: framebuffer loaded
> 

Are you using savagefb?  savagefb isn't really compatable with the
savage X server.


> I don't think this is really important. However if I try to run any GL
> applications, such as glxgears my computer will freeze with some strange
> green/blue lines moving from the top to the bottom of the screen on the right
> hand side. I can get control back eventually by switching to another screen and
> back to X or by killing the X server, at which point the terminal will read
> something like:
> 
> 230 frames in 5.0 seconds = 46.000 FPS
> 1 frames in 9.0 seconds =  0.111 FPS
> 89 frames in 12.0 seconds =  7.417 FPS
> 87 frames in 11.0 seconds =  7.909 FPS
> 87 frames in 11.0 seconds =  7.909 FPS
> 88 frames in 11.0 seconds =  8.000 FPS
> wait event returned -16
> 

you might also try disabling command DMA.

> The dmesg output will give:
> 
> agpgart: Found an AGP 2.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:00.0 into 1x mode
> [drm:savage_bci_wait_event_reg] *ERROR* failed!
> [drm]    status=0x00002521, e=0x2522
> 
> Otherwise everything else seems to be working alright and I don't get any error
> messages in my xorg.0.log, or from glxinfo. I have made sure that my xorg.conf
> has the following lines:
> 
>         Option "ShadowStatus" "true"
>         Option "DmaType" "PCI"

try adding:

Option "AGPMode" "4"

and remove the DmaType option.

some savages seem to have problems with lower agp modes

> 
> And that DMA is disabled for vertex transfes. I am booting with a vesafb console
> otherwise it becomes garbled once X loads which is extremely annoying - but
> this might have something to do with my problems.
> Thanks a lot for any help.
> Richard Malone
>