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

[bugzilla at redhat.com]

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

Summary: agpgart aperture checking fails with kernel 2.6.22.4-65.fc7 update


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





------- Additional Comments From ahuhtal4 at welho.com  2008-05-16 16:05 EST -------
(In reply to comment #35)
> My present kernel is 2.6.24.7-92.fc8 and the problem persists. As requested,
> I've changed Fedora version number to 8 which I've been using since December 2007.
> I've tried Fedora-9-x86_64-Live and didn't see apgart error messages but that
> probably doesn't mean the problem is fixed in Fedora 9.

...and indeed, when I COLD-BOOT the F9-x86_64-Live CD and execute the following
commands in Gnome terminal window:

[fedora at localhost ~]$ uname -r
2.6.25-14.fc9.x86_64

[fedora at localhost ~]$ dmesg | grep aperture
Checking aperture...
Node 0: aperture @ 7ef0000000 size 128 MB
Your BIOS doesn't leave a aperture memory hole
Mapping aperture over 65536 KB of RAM @ 4000000
agpgart: No usable aperture found.
agpgart: Consider rebooting with iommu=memaper=2 to get a good aperture.

[fedora at localhost ~]$ dmesg | grep agpgart
agpgart: Detected AGP bridge 0
agpgart: Aperture pointing to RAM
agpgart: Aperture from AGP @ f0000000 size 4096 MB
agpgart: Aperture too small (0 MB)
agpgart: No usable aperture found.
agpgart: Consider rebooting with iommu=memaper=2 to get a good aperture.
Linux agpgart interface v0.103
[fedora at localhost ~]$ 

..nothing has changed since agpgart aperture detection first broke in F7 last
August - except for the fact that now the kernel does not crash like it did
then. Kernel crash was however caused by improper memory allocation for my 512M
of RAM, not as a result of failed aperture detection.


-- 
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, or are watching someone who is.