From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-user+bounces-111798-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1OP3dR-0007DN-51
for garchives@archives.gentoo.org; Thu, 17 Jun 2010 01:11:13 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id AD436E0BF7
for <garchives@archives.gentoo.org>; Thu, 17 Jun 2010 01:11:12 +0000 (UTC)
Received: from mail-yw0-f203.google.com (mail-yw0-f203.google.com [209.85.211.203])
by pigeon.gentoo.org (Postfix) with ESMTP id 323DAE0D5F
for <gentoo-user@lists.gentoo.org>; Thu, 17 Jun 2010 01:04:26 +0000 (UTC)
Received: by ywh41 with SMTP id 41so6079826ywh.9
for <gentoo-user@lists.gentoo.org>; Wed, 16 Jun 2010 18:04:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from
:user-agent:mime-version:to:subject:references:in-reply-to
:content-type:content-transfer-encoding;
bh=TuW8ffQFDl5IAJiEtCtxmKzmySm4lLQ1Abkefk+DD3I=;
b=E58gZ3G3th2kHAryo/JKSFMgHQU5oaZPEFngdevA1DMcgDRlS5vxBY8veporuDwSVa
EgfOycgKbWi1XnitOt5g7XsZR7PlREOr+tLMqI/TMcpAvn9klUFMMvIWGv/h7LexXm+w
NuZN4a1JwUYc7XFA/NOstWjzljuETRtd8tEz8=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=message-id:date:from:user-agent:mime-version:to:subject:references
:in-reply-to:content-type:content-transfer-encoding;
b=JcoDbeYZ3KEKnyy9f0O0YEKghoBZwVmMdl0FEoG1LCsl2a+lnhxaosnsudbq/PflWP
bvZbO++AOtryqlm364dEOZpElxEAj7RMkA8DV0r+SLLwfA83PNPUtSR3/A5zzQpUR03b
PZ+WnkRBnUd/stswUrVMnLvvf/3NMXZ/oKrxg=
Received: by 10.91.210.19 with SMTP id m19mr2841113agq.3.1276736665446;
Wed, 16 Jun 2010 18:04:25 -0700 (PDT)
Received: from [192.168.1.2] (adsl-0-93-68.jan.bellsouth.net [65.0.93.68])
by mx.google.com with ESMTPS id 21sm3953186ywh.2.2010.06.16.18.04.24
(version=SSLv3 cipher=RC4-MD5);
Wed, 16 Jun 2010 18:04:24 -0700 (PDT)
Message-ID: <4C197497.40108@gmail.com>
Date: Wed, 16 Jun 2010 20:04:23 -0500
From: Dale <rdalek1967@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100616 Gentoo/2.0.4-r2 SeaMonkey/2.0.4
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] (dual) booting windows kills the ethernet device
for linux
References: <yu9k4pyqyzw.fsf@nyu.edu>
In-Reply-To: <yu9k4pyqyzw.fsf@nyu.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Archives-Salt: e990207a-6543-4eef-ab6e-c6f5983ada8c
X-Archives-Hash: b4cefa549ef7f7db714b6f3c32203dd3
Allan Gottlieb wrote:
> I feel strange writing this since I can hardly believe it.
> However, it seems to be quite repeatable.
>
> I have a new dell latitude E6500 that I set up for dual booting:
> windows 7 and gentoo linux.
>
> The machine seems to have two "hardware" states determined by whether
> windows has been run since power on.
>
> If you power the machine on it goes into what I call State A.
> Now if I either select linux from grub or just use the default we get
>
> linux boots and eth0 works
> reboot
> linux boots and eth0 works
> ...
> reboot
> linux boots and eth0 works
>
> but now reboot into windows and we get State B
> windows boots and eth0 works
> reboot to linux
> linux boots but eth0 fails
> reboot
> linux boots but eth0 fails
> ...
> reboot
> linux boots but eth0 fails.
>
> If I then power the machine off instead of simply rebooting
> we get back to State A
>
> power on
> linux boots and eth0 works
> reboot
> linux boots and eth0 works
>
> etc.
>
> This is quite repeatable. I would greatly appreciate an explanation.
>
> thanks,
> allan
>
>
I read about this ages ago. I *think* it was windoze doing some sort of
a shutdown on the card, disabling it or putting it into sleep mode if
you want to call it that. It appears that Linux isn't "waking" the card
up but a power cycle does. It also appears that windoze "wakes" the
card up when it boots.
I'm pretty sure they found a fix but I can't recall what they did. It
seems they changed some sort of setting in windoze but not real sure.
May want to google the mailing list archives and see if you can find
it. I know it is older than the archives I have here. I keep them for
a year then it dumps them. So it's been a good while. May have to dig
back a while.
Biggest point of reply, you're not nuts. Someone else had the same
problem. lol Hard to believe I remember as much as I did tho. o_O
Dale
:-) :-)