From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nate Lawson Subject: Re: Network failures with ACPI enabled (kernel 2.4, 2.6) PROBLEM FOUND!!!!!! Date: Wed, 31 Dec 2003 15:02:13 -0800 (PST) Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20031231150153.R2857@root.org> References: <20031231001716.76cb2e8d.mike@it-loops.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: <20031231001716.76cb2e8d.mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Michael Guntsche Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org On Wed, 31 Dec 2003, Michael Guntsche wrote: > On Tue, 30 Dec 2003 17:36:14 -0500 > "Brown, Len" wrote: > > The BIOS' AML may not be well coordinated with the CMOS setting > > for enabling/disabling the device. > > > > It is interesting that Windows XP works either way. > > Could be that Linux has an ACPI bug that XP does not have, > > or that the BIOS happens to work with XP's implementation > > and not Linux's implementation. > > > > Is there a way to see what the change in the CMOS does to ACPI? > What puzzles me is that with the parport disabled outgoing traffic > still works. It would make more sense if the network didn't work at all. Only incoming packets generate an interrupt. -Nate ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click