[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: New ATI fglrx drivers work with AMD64



Manuel,

These MTRR errors are the reason why direct rendering does not work.

I've just faced a similar problem. Hopefully, in my Tyan Tiger K8W S2875 BIOS setup there is an option MTRR Mapping which can be either Continuous or Discrete. The former "explicitly describes the PCI hole as non-cacheable" while the latter "leaves the PCI hole below the 4G boundary undescribed". Continuous is default. All MTRR errors and fglrx direct rendering ability had been fixed when I switched MTRR Mapping to Discrete.

You can see the current MTRR state with 'cat /proc/mtrr'.
This is how my MTRR looked with Continuous mapping:

reg00: base=0x00000000 (   0MB), size=4096MB: write-back, count=1
reg01: base=0x100000000 (4096MB), size=1024MB: write-back, count=1
reg02: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1   <==== this was problematic

And how they look now:

reg00: base=0x100000000 (4096MB), size=1024MB: write-back, count=1
reg01: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg02: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg03: base=0xe0000000 (3584MB), size= 128MB: write-combining, count=1
reg04: base=0xf0000000 (3840MB), size= 128MB: write-combining, count=1

I guess that two 128Mb regions are video card memory and AGP aperture.

Max

Manuel Capinha wrote:
Small add-on:

My problem is somewhere in the kernel module, it seems:
(from dmesg)

[fglrx] module loaded - fglrx 8.8.25 [Jan 14 2005] on minor 0
Fire GL built-in AGP-support
Based on agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 941M
agpgart: Detected AMD 8151 chipset
agpgart: AGP aperture is 32M @ 0x4000000
Power management callback for AGP chipset installed
[fglrx] AGP detected, AgpState   = 0x1f000b7b (hardware caps of chipset)
mtrr: type mismatch for 4000000,2000000 old: write-back new: write-combining
[fglrx:firegl_unlock] *ERROR* Process 25297 using kernel context 0


PID 25297 is my X server.

So, is anyone else seeing this ? I've got no clue about that error message :/

Thanks once again,
Manuel

On Tue, 18 Jan 2005 15:11:32 +0000, Manuel Capinha <mcapinha@gmail.com> wrote:

I got it to install and I can now boot X using ATI's proprietary
drivers, but I got no OpenGL support. Running glxgears gives me around
60 fps, so I know that's being done in software!

Looking in /var/log/XFree86.0.log I found this:

(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0):     Name: fglrx
(II) fglrx(0):     Version: 8.8.25
(II) fglrx(0):     Date: Jan 14 2005
(II) fglrx(0):     Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0):     Build-Kernel UTS_RELEASE:        2.6.9-9-amd64-k8-smp
(II) fglrx(0):     Build-Kernel MODVERSIONS:        no
(II) fglrx(0):     Build-Kernel __SMP__:            no
(II) fglrx(0):     Build-Kernel PAGE_SIZE:          0x1000
(II) fglrx(0): [drm] register handle = 0xff5f0000
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_EINVAL"
(EE) fglrx(0): cannot init AGP
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xffffff000041d000
at 0x2a955da000
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed!                  *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO)             *
(WW) fglrx(0): * no 3D acceleration available                *
(WW) fglrx(0): ********************************************* *

Is anyone else seeing this or does everyone else but my have OpenGL by
hardware ?

TIA,
Manuel


On Tue, 18 Jan 2005 15:10:46 +0100, Filippo Carone
<f.carone@fastwebnet.it> wrote:

* Lorenzo Milesi (lorenzo.milesi@gmail.com) ha scritto:

Hi, I'd just like to give the list a heads up that the new ATI fglrx
drivers actually work with amd64.  They're only available (as usual) in
rpm's but I hacked together Flavio's debian packages and with a bit of
manual copying around it works.

Can you tell me how did you do it?
I tried just alien-ing the rpm but fails because it tries to overwrite
`/usr/X11R6/lib/libGL.so.1.2', owned by xlibmesa-gl package.

use the --force-overwrite switch of dpkg.

cheers,
fc


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org








Reply to: