From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bas Mevissen Subject: Re: ACPI stops working after memory upgrade vpr Matrix 175b4 Date: Thu, 05 Feb 2004 12:21:02 +0100 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <4022271E.3000307@basmevissen.nl> References: <20040204073941.05d71e0b.rddunlap@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20040204073941.05d71e0b.rddunlap-3NddpPZAyC0@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: "Randy.Dunlap" Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org Randy.Dunlap wrote: >> > > < 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. > > Is this correct? If a user adds or removes memory, then the > DSDT must be rebuilt? Sheesh!! That's bad if this is correct. > Patch the DSDT on runtime. Or add a checksum on the original DSDT. Regards, Bas. ------------------------------------------------------- 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