All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Moles <jeremy-9vekgGPT+OA7YuNMryXyOw@public.gmane.org>
To: acpi-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org
Subject: RAM > 1GB
Date: Wed, 02 Feb 2005 11:34:03 -0500	[thread overview]
Message-ID: <1107362043.4512.11.camel@localhost> (raw)

Hello ACPI gurus. :)

I have a Dell X300 here using a custom DSDT table appropriate with the
BIOS version. The trouble is, the system has an "unusual" amount of
RAM--so much so that it breaks ACPI and prevents a few things from
working. 128Mb of RAM is built into the motherboard and an additional
1Gb has been added.

When the system is booted WITH the additional RAM, I get a number of
errors. The dmesg file is here:

http://downloads.emperorlinux.com/research/ACPI/dmesg-bad

When the system is booted WITHOUT the additional RAM, everything works
as intended.

http://downloads.emperorlinux.com/research/ACPI/dmesg-good

I've also provided the DSDT table that I'm using, which can be found in
the same directory as the dmesg files.

I would appreciate any help on fixing this issue if anyone is available.
At any rate, keep up the good work! You guys make a lot of what we do
here possible!

>>cheers<<

-- 
Jeremy L. Moles
EmperorLinux
1-888-651-66
www.EmperorLinux.com
jeremy-LdSqz1EEwCk7YuNMryXyOw@public.gmane.org



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

             reply	other threads:[~2005-02-02 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 16:34 Jeremy Moles [this message]
2005-02-02 17:07 ` RAM > 1GB liste-9nAOAgdJVo4b1SvskN2V4Q
2005-02-02 17:11 ` Matthew Garrett

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=1107362043.4512.11.camel@localhost \
    --to=jeremy-9vekggpt+oa7yunmryxyow@public.gmane.org \
    --cc=acpi-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.