Serious, potentially hardware-damaging e1000e driver issue on Intrepid - Ubuntu
This is a discussion on Serious, potentially hardware-damaging e1000e driver issue on Intrepid - Ubuntu ; Be aware:
Serious, potentially hardware-damaging e1000e driver issue on Intrepid
Dear developers,
Reports have been coming in that the e1000e Ethernet driver for Intel GigE
chipsets, as included upstream in Linux 2.6.27, may under certain conditions
irreparably damage your Ethernet ...
-
Serious, potentially hardware-damaging e1000e driver issue on Intrepid
Be aware:
Serious, potentially hardware-damaging e1000e driver issue on Intrepid
Dear developers,
Reports have been coming in that the e1000e Ethernet driver for Intel GigE
chipsets, as included upstream in Linux 2.6.27, may under certain conditions
irreparably damage your Ethernet hardware by corrupting the on-board
firmware.
While we expect alphas to include a fair number of bugs, and rely on your
continued support and testing to help resolve these bugs for Ubuntu
releases, bugs that damage hardware are quite another matter. As a result
of this bug we must recommend that users do *not* use Intrepid alphas,
including the LiveCDs, on machines with Intel GigE Ethernet.
Efforts to safeguard the hardware of affected users are ongoing, though
initially this will consist of a workaround in the form of disabling the
e1000e driver. Alpha 6 CD images will not be re-issued for this fix, so
affected users are advised to either use daily CD images once a resolution
is in place, or to wait for the release of the 8.10 beta, due to be released
on October 2.
Full announcement here:
https://lists.ubuntu.com/archives/ub...er/000488.html
--
John
No Microsoft, Apple, AT&T, Intel, Novell, Trend Micro, nor Ford products were used in the preparation or transmission of this message.
The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.
-
Re: Serious, potentially hardware-damaging e1000e driver issue onIntrepid
John F. Morse wrote:
> Serious, potentially hardware-damaging e1000e driver issue on Intrepid
It's not just Intrepid. The latest Mandriva and SUSE, too:
http://www.heise.de/english/newsticker/news/116431
--
As we enjoy great advantages from inventions of others, we should be
glad of an opportunity to serve others by any invention of ours;
and this we should do freely and generously.
--Benjamin Franklin
-
Re: Serious, potentially hardware-damaging e1000e driver issue onIntrepid
johnny bobby bee wrote:
> It's not just Intrepid. The latest Mandriva and SUSE, too:
> http://www.heise.de/english/newsticker/news/116431
--
As we enjoy great advantages from inventions of others, we should be
glad of an opportunity to serve others by any invention of ours;
and this we should do freely and generously.
--Benjamin Franklin
-
Re: Serious, potentially hardware-damaging e1000e driver issue onIntrepid
On Mon, 29 Sep 2008 23:06:46 -0500, John F. Morse wrote:
> Serious, potentially hardware-damaging e1000e driver issue on Intrepid
>
> Reports have been coming in that the e1000e Ethernet driver for Intel
> GigE chipsets, as included upstream in Linux 2.6.27, may under certain
> conditions irreparably damage your Ethernet hardware by corrupting the
> on-board firmware.
Blame where it's due: Intel ethernet boards have their own opcodes. This
time Intel decided to "borrow" an opcode and "re-use" it for firmware
update instead of ethernet functions. It really is Intel's fault this
time.
-
Re: Serious, potentially hardware-damaging e1000e driver issue on Intrepid
Roland Latour wrote:
> On Mon, 29 Sep 2008 23:06:46 -0500, John F. Morse wrote:
>
>> Serious, potentially hardware-damaging e1000e driver issue on Intrepid
>>
>> Reports have been coming in that the e1000e Ethernet driver for Intel
>> GigE chipsets, as included upstream in Linux 2.6.27, may under certain
>> conditions irreparably damage your Ethernet hardware by corrupting the
>> on-board firmware.
>
> Blame where it's due: Intel ethernet boards have their own opcodes. This
> time Intel decided to "borrow" an opcode and "re-use" it for firmware
> update instead of ethernet functions. It really is Intel's fault this
> time.
Reminds me of the LG burner issue where some "borrowed" code could lead to
flashing the burner firmware with junk.
