public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: linux-kernel@vger.kernel.org
Subject: Aperture pointing to e820 RAM. Ignoring.
Date: Tue, 22 Jul 2008 23:12:34 -0400	[thread overview]
Message-ID: <m3wsjd2t0d.fsf@pullcord.laptop.org> (raw)

Hi,

I have a new 64-bit AMD system, with:

  00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
  CPU0: AMD Phenom(tm) 9550 Quad-Core Processor stepping 03

dmesg contains:

  Checking aperture...
  No AGP bridge found
  Node 0: aperture @ 20000000 size 32 MB
  Aperture pointing to e820 RAM. Ignoring.
  Your BIOS doesn't leave a aperture memory hole
  Please enable the IOMMU option in the BIOS setup
  This costs you 64 MB of RAM

Any suggestions on how to get my 64 MB back?  Full dmesg at:

  http://dev.laptop.org/~cjb/pullcord-dmesg

As a small nitpick, the text quoted above seems misleading:

> Your BIOS doesn't leave a aperture memory hole

I don't think that's true; we just don't like where it mapped it.

> Please enable the IOMMU option in the BIOS setup

.. therefore, I don't think this is relevant.  My BIOS doesn't appear
to have such an option in any case.

> This costs you 64 MB of RAM

A literal interpretation of "Please enable the IOMMU option in the BIOS
setup / This costs you 64 MB of RAM" would be that turning on the
IOMMU option would cost me 64 MB of RAM, whereas I think the opposite
meaning is intended.

Happy to help with the nitpick, and would like to sort out the
underlying problem on this box, which is a Gateway DX4200-UB001A.

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>

                 reply	other threads:[~2008-07-23  3:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3wsjd2t0d.fsf@pullcord.laptop.org \
    --to=cjb@laptop.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox