From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: (dual) booting windows kills the ethernet device for linux
Date: Thu, 17 Jun 2010 04:00:25 +0300 [thread overview]
Message-ID: <hvbs2t$15g$1@dough.gmane.org> (raw)
In-Reply-To: <yu9k4pyqyzw.fsf@nyu.edu>
On 06/17/2010 03:33 AM, 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.
The explanation is that the Windows driver leaves the hardware in a
state that the Linux driver doesn't expect. A warm reboot doesn't reset
it correctly. Only a cold one does. This is usually a bug in the Linux
driver. Might be worth reporting upstream.
next prev parent reply other threads:[~2010-06-17 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 0:33 [gentoo-user] (dual) booting windows kills the ethernet device for linux Allan Gottlieb
2010-06-17 1:00 ` Nikos Chantziaras [this message]
2010-06-17 1:04 ` Dale
2010-06-17 2:43 ` Allan Gottlieb
2010-06-17 9:27 ` Alex Schuster
2010-06-17 18:48 ` Allan Gottlieb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hvbs2t$15g$1@dough.gmane.org' \
--to=realnc@arcor.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox