From: Theodore Tso <tytso@mit.edu>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: Pavel Machek <pavel@ucw.cz>,
"Robin H. Johnson" <robbat2@gentoo.org>,
linux-kernel@vger.kernel.org
Subject: Re: e1000/ICH8LAN weirdness - no ethtool link until initially forced up
Date: Tue, 7 Nov 2006 14:35:18 -0500 [thread overview]
Message-ID: <20061107193518.GA26579@thunk.org> (raw)
In-Reply-To: <4550AB7A.10508@intel.com>
On Tue, Nov 07, 2006 at 07:51:22AM -0800, Auke Kok wrote:
>
> Your application should really `ifconfig up` the device before checking for
> link.
And for those of us with laptops, application authors should do an
"ifconfig down" the device if it doesn't find a link. Right now
thanks to such applications on my desktop, I boot with e1000
blacklisted so I can run in low-power mode when on a laptop.
BTW, it would be nice if the e1000 driver could be more safely
unloaded when it is built as a module. Yeah, the right answer is that
the gnome desktop is made less power hungry, and there are other
things I can do such as kill -STOP various bits of the gnome desktop
when I am running in battery mode, but it would be nice if I could
forcibly down the e1000 driver, and right not simply keeping the
module unloaded is the most reliably way of doing it in the face of
desktop applets that don't care about how much power they are sucking
down....
- Ted
next prev parent reply other threads:[~2006-11-08 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 1:31 e1000/ICH8LAN weirdness - no ethtool link until initially forced up Robin H. Johnson
2006-11-07 7:14 ` Pavel Machek
2006-11-07 15:51 ` Auke Kok
2006-11-07 19:35 ` Theodore Tso [this message]
2006-11-08 15:59 ` Auke Kok
2006-11-07 21:31 ` Robin H. Johnson
2006-11-07 22:32 ` Auke Kok
2006-11-08 3:56 ` Robin H. Johnson
2006-11-08 12:04 ` Pavel Machek
2006-11-08 19:54 ` General network driver suspend/resume (was e1000 carrier related) Stephen Hemminger
2006-11-08 21:10 ` Auke Kok
2006-11-08 21:33 ` Stephen Hemminger
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=20061107193518.GA26579@thunk.org \
--to=tytso@mit.edu \
--cc=auke-jan.h.kok@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robbat2@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