From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: [Debian-eeepc-devel] Debian on the ASUS EeePC 1005PE Date: Fri, 19 Feb 2010 14:14:44 -0800 Message-ID: <201002191414.45156.dmitry.torokhov@gmail.com> References: <87y6iqy58p.fsf@marvin.43-1.org> <9b2b86521002190810if166725ob21c005f250bf152@mail.gmail.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-vw0-f46.google.com ([209.85.212.46]:56242 "EHLO mail-vw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754350Ab0BSWO4 (ORCPT ); Fri, 19 Feb 2010 17:14:56 -0500 Received: by vws11 with SMTP id 11so203591vws.19 for ; Fri, 19 Feb 2010 14:14:55 -0800 (PST) In-Reply-To: <9b2b86521002190810if166725ob21c005f250bf152@mail.gmail.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Alan Jenkins Cc: Ansgar Burchardt , Corentin Chary , debian-eeepc-devel@lists.alioth.debian.org, debian-users@lists.debian.org, ACPI Devel Maling List On Friday 19 February 2010 08:10:39 am Alan Jenkins wrote: > On 2/18/10, Ansgar Burchardt wrote: > > Hi, > > > > I got an ASUS EeePC 1005PE a few days ago and am trying to install > > Debian testing on it. > > > > There have been several problems so far: > > > > > 2. The Ethernet card disappeared completely. It did no longer show up > > in the output from lspci, nor was it accessible in Windows. This > > problem persisted over shutdowns as well. Removing the battery and > > disconnecting the power supply luckily made the card show up again. > > > > A patch was available for this issue on a different EeePC model [3]. > > This one was not so easy to backport, so I just changed it to disable > > hot-plug always (patch attached). This solved this issue for me: the > > Ethernet card does no longer disappear. > > > > [3] http://bugzilla.kernel.org/show_bug.cgi?id=14570 > > My suggestion for this problem would be to contact the eeepc-laptop > maintainer :-). > > I guess we're too late to add a blacklist entry for 2.6.33, but we > should be able to get a fix into 2.6.33.1. I think blacklist addition should be fine even for .33. Thanks. -- Dmitry