From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Dave Bauer <dave-eQMij45H2SHXYFsarriMmxagbA6BzR3y@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI stops working after memory upgrade vpr Matrix 175b4
Date: Tue, 3 Feb 2004 09:31:44 +0100 [thread overview]
Message-ID: <20040203083143.GA29079@hell.org.pl> (raw)
In-Reply-To: <401F0395.1090407-eQMij45H2SHXYFsarriMmxagbA6BzR3y@public.gmane.org>
Thus wrote Dave Bauer:
> My ACPI stopped working when I added an additional 256mb RAM to my vpr
> Matricx 174b4 laptop. It has 256mb already, I added 256mb to make it
> 512mb and I got a bunch of AE_NO_MEMORY errors in the ACPI code.
>
> I took the extra RAM out, and the ACPI support works.
>
> I am using kernel 2.6.1 with acpi patches. I had the same problem on
> 2.6.0. On 2.4.20 with acpi patches the machine would not even boot with
> the extra memory.
>
> I have a custom DSDT file that I fixed errors in. When it was working on
> 2.4.20 It looked like all the ACPI features were active and functional.
Recompile your DSDT. Since the amount of RAM changed and you're probably
using old DSDT containing wrong addresses, no wonder you're hitting errors.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-03 8:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 2:12 ACPI stops working after memory upgrade vpr Matrix 175b4 Dave Bauer
[not found] ` <401F0395.1090407-eQMij45H2SHXYFsarriMmxagbA6BzR3y@public.gmane.org>
2004-02-03 8:31 ` Karol Kozimor [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 7:07 Yu, Luming
2004-02-04 15:39 Randy.Dunlap
2004-02-04 16:18 ` Sergey Vlasov
[not found] ` <20040204073941.05d71e0b.rddunlap-3NddpPZAyC0@public.gmane.org>
2004-02-04 17:28 ` Bruno Ducrot
[not found] ` <20040204172852.GL882-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-09 20:21 ` Nate Lawson
2004-02-05 11:21 ` Bas Mevissen
2004-02-05 12:30 ` Karol Kozimor
[not found] ` <20040205123049.GC22034-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-02-05 16:27 ` Randy.Dunlap
[not found] ` <20040205082758.1917e71a.rddunlap-3NddpPZAyC0@public.gmane.org>
2004-02-06 0:51 ` Karol Kozimor
2004-02-07 12:23 ` Bruno Ducrot
2004-02-05 20:45 Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8ABD-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-02-05 20:41 ` Dave Bauer
2004-02-11 8:19 Yu, Luming
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=20040203083143.GA29079@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=dave-eQMij45H2SHXYFsarriMmxagbA6BzR3y@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox