[Dri-users] Re: Some problems with Savage4 in x11-6.9.0

[<ki...@ba...>]

On Tue, 25 Apr 2006, Felix K=FChling wrote:

> Am Dienstag, den 25.04.2006, 19:21 -0500 schrieb
> ki...@ba...:
(...)
>
> On an opteron system I believe you should use amd64-agp.
>
> Regards,
>  Felix
This may have cured the problem:

We have now directly after reboot the following:

root@khayyam:~# lsmod|grep agp
amd64_agp              10372  1
agpgart                28976  1 amd64_agp
root@khayyam:~# dmesg|grep agp
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected AGP bridge 0
agpgart: AGP aperture is 32M @ 0xd0000000
root@khayyam:~#

so things are looking better. And after starting X we get

  root@khayyam:~# dmesg|grep agp
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected AGP bridge 0
agpgart: AGP aperture is 32M @ 0xd0000000
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
root@khayyam:~#

and

root@khayyam:~# lsmod|grep savage
savage                 32704  1
drm                    64340  2 savage
root@khayyam:~#

and in the Xorg.0.log we now have

=2E..

(II) SAVAGE(0): [drm] framebuffer handle =3D 0xf0000000
(II) SAVAGE(0): [drm] added 1 reserved context for kernel
(II) SAVAGE(0): [agp] Mode 0x1f000207 [AGP 0x1106/0x0204; Card=20
0x5333/0x8a22]
(II) SAVAGE(0): [agp] 16384 kB allocated with handle 0x00000001
(II) SAVAGE(0): [agp] command DMA handle =3D 0xd0000000
(II) SAVAGE(0): [agp] agpTextures handle =3D 0xd0100000
(II) SAVAGE(0): [drm] aperture handle =3D 0xf2000000
=2E..

which looks much better.

Thanks. Now, do you have a USB digital still camera with proprietary=20
interface that you want to make to=20
work? Perhaps I could help you with that. Unless of course it is using one=
=20
of those cursed proprietary compression algorithms ...

Theodore Kilgore