| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20061107193518.GA26579@thunk.org> Date: Tue, 7 Nov 2006 14:35:18 -0500 From: Theodore Tso <tytso@....edu> To: Auke Kok <auke-jan.h.kok@...el.com> Cc: Pavel Machek <pavel@....cz>, "Robin H. Johnson" <robbat2@...too.org>, linux-kernel@...r.kernel.org Subject: Re: e1000/ICH8LAN weirdness - no ethtool link until initially forced up 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists