Comment 292 for bug 263555
Revision history for this message
|
|
#292 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(In reply to comment #58 from Jiri Kosina)
> And did this machine expose the problem at least once previously? Apparently
> not all systems having e1000e hardware are being hit by the issue, either only
> specific product IDs are affected, or it might be chipset-dependent, etc.
I am not sure. See comment #32. It might of course also just have been a broken joint on the mainboard.
> Also, please do not forget to back up contents of your EEPROM before you start
> playing with this :)
If it hits me the same as last time, this won't help :) (and yes, i backed it up)
(In reply to comment #59 from Jesse Brandeburg)
> BTW this is the first desktop machine I've heard of that reported the problem.
Regarding the desktop: it also has intel integrated graphics, and it had recurring problems with the graphics driver (lockups) before the ethernet broke. Maybe that's one common factor.