From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Vlasov Subject: Re: ACPI stops working after memory upgrade vpr Matrix 175b4 Date: Wed, 4 Feb 2004 19:18:08 +0300 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20040204191808.2e23df00.vsu@altlinux.ru> References: <20040204073941.05d71e0b.rddunlap@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org On Wed, 4 Feb 2004 07:39:41 -0800 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. Many BIOSes patch the DSDT according to the system configuration (e.g. rename \_S3 to something other if Suspend to RAM is disabled in the setup). Probably some BIOSes put the memory size into DSDT this way... ------------------------------------------------------- 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