[Bug 278721] agpgart aperture checking fails with kernel 2.6.22.4-65.fc7 update

bugzilla at redhat.com bugzilla at redhat.com
Thu Nov 27 04:01:06 UTC 2008


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=278721


Antti Huhtala <ahuhtal4 at welho.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|8                           |9




--- Comment #38 from Antti Huhtala <ahuhtal4 at welho.com>  2008-11-26 23:01:02 EDT ---
Well, things have gradually improved since my initial report of a F7 problem.
Since "Linux agpgart interface v0.102" was replaced with "Linux agpgart
interface v0.103" at some recent update, my AGP V3 device is now controlled by
'agpgart-amd64'. This means I now have at least 32M of AGP aperture regardless
of whether the box is cold-booted or warm-booted.

I have updated this bug report first to deal with F8 and now with F9. The
remaining problem seems to be of minor significance: if the box is cold-booted
I get only 32M of AGP aperture though the BIOS setting is 128M. Only if the box
is warm-booted, the full 128M is reserved for AGP aperture.

The problem seems to persist in placing the aperture at an improper address
when the box is cold-booted. From dmesg when cold-booted:

"Aperture beyond 4GB. Ignoring.
.
.
Checking aperture...
Node 0: aperture @ 1ef0000000 size 128 MB
agpgart-amd64 0000:00:00.0: AGP aperture is 32M @ 0xf0000000"

whereas the corresponding lines when warm-booted are:

"Checking aperture...
Node 0: aperture @ f0000000 size 128 MB
agpgart-amd64 0000:00:00.0: AGP aperture is 128M @ 0xf0000000"

Though little harm seems to result from aperture being only 32M after a cold
boot, I'd like to see this problem solved. There are other K8N mobos around.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.




More information about the fedora-triage-list mailing list