Oh thats ugly! I'll be waiting for the stable verson before I upgrade to 8.10
Wow, I had no idea that a driver could actually damage hardware.
SPAM-posters beware! ®
Here's that they think may be going on, "the eeprom is not MMIO mapped, the registers for accessing it are. I'm still not clear if a random write to a memory location could corrupt things, we'll be looking at that today."
Marco ChiappettaManaging Editor @ HotHardware.com
Follow Marco on Twitter
I say, why is this announced all over the internet as if it only affects ubuntu? It affects all Linux distributions using the kernel 2.6.27-rc1 (up until 2.6.27-rc4).
Welcome to HotHardware, Panda!
If you can fix it by rewriting the eeprom (insinuated by the backup procedure), it's not "damaging hardware".
What part of "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn" don't you understand?
Sure it is. What if you don't have a backup of the eeprom? Is corrupted data, not damaged data? And if the corrupted data causes a harware malfunction, isn't that hardware damaged?
>> What if you don't have a backup of the eeprom?
Find someone who does. I don't think Intel's going to sue you for copyright infringement on something that won't work without their hardware. Especially since, owning the hardware, you are already licenced for the eeprom software.
I wouldn't even be surprised if Intel doesn't supply a bootable disk that fixes them, before this is all over - just to avoid the negative impression towards their easily-corruptable NICs.
>> And if the corrupted data causes a harware malfunction, isn't that hardware damaged?
Respectfully speaking: By that logic, If I write a program the overwrites your boot sector - I damaged your computer's hardware.
The NICs might be semi-bricked, but they're not bricked. If you can fix it with a software reload, then obviously the hardware is not damaged.
I remember the old days, when you could really damage hard drives by programming them to beat their heads against physical stops, or set a monitor to a refresh rate that burned it out - those were hardware damage.
I'm surprised there aren't more viruses that take advantage of Intel's eeproms, if they're so easy to re-write. That would make for a hell of a virus - one that hides itself in your NIC eeprom and re-installs after you reformat. Kind of like CIH done right. I have to go now, to start work on a completely unrelated project. :)
NEWS TIPS |
This site is intended for informational and entertainment purposes only. The contents are the views and opinion of the author and/or hisassociates. All products and trademarks are the property of their respective owners. All content and graphical elements areCopyright © 1999 - 2013 David Altavilla and HotHardware.com, LLC. All rights reserved. Privacy and Terms