LWN.net Logo

No evidence of bricking

No evidence of bricking

Posted Apr 22, 2009 16:34 UTC (Wed) by proski (subscriber, #104)
Parent article: Danger with NVIDIA drivers 180.29

The announcement says:

Using earlier NVIDIA Linux drivers on the Celsius H270 notebook will result in a corrupt EDID, which will persist across reboots
If a system reboots, it's not bricked. Bricked systems don't reboot.


(Log in to post comments)

No evidence of bricking

Posted Apr 22, 2009 16:42 UTC (Wed) by corbet (editor, #1) [Link]

If you don't like my term, then fine. You still have to send it back to the vendor to get a system that works. It's a brick that stays warm.

No evidence of bricking

Posted Apr 23, 2009 11:21 UTC (Thu) by Duncan (guest, #6647) [Link]

"It's a brick that stays warm."

Great example of that famous Corbet humor! Sure you aren't related to any
of that Python troop? (Still laughing.)

"I'm not a brick!"

"You are a brick. You're a brick that stays warm!" [conk]

...

(See what all those first-week readers missed! =:^)

No evidence of bricking

Posted Apr 23, 2009 15:37 UTC (Thu) by GreyWizard (guest, #1026) [Link]

This comment just made my day. Well said.

No evidence of bricking

Posted Apr 22, 2009 17:41 UTC (Wed) by rakoenig (subscriber, #29855) [Link]

If the error occurs the system boots exactly to the point where BIOS/Video-BIOS want to identify the display. Since the EDID data is corrupt the system locks up, so you don't even have a chance booting with an external monitor attached. So you have an expensive brick that keeps your desk at moderate temperature (to quote Jonathan).

The only way to "repair" this requires opening the housing and will make the customers warranty void. So the process is contacting the vendor and letting someone from them repair it with the proper tools.

BTW: This issue seems to be happening on drivers of the 180.xx series only. Debian 5.0 with packaged 173.xx drivers are not affected.

Rainer (that "bricked" and repaired his H270 several times)

No evidence of bricking

Posted Apr 22, 2009 18:34 UTC (Wed) by proski (subscriber, #104) [Link]

Thanks for the details! That's bad indeed.

No evidence of bricking

Posted Apr 22, 2009 21:22 UTC (Wed) by gnb (subscriber, #5132) [Link]

Although the fact that the system is bricked at that point seems as much a
BIOS deficiency as anything. The BIOS could do something sensible like look
for an external display, or try falling back to some lowest common
denominator display spec. and hope the hardware can manage this, or just boot
with no video and hope the OS supports a serial console. Simply dying because
the EDID is garbage is feeble.

No evidence of bricking

Posted Apr 22, 2009 23:19 UTC (Wed) by nix (subscriber, #2304) [Link]

You're surprised that a BIOS is crappy?

I've had systems whose BIOSes went into an infinite loop because a hard
drive was larger than they expected, or because two hard drives were
attached, or because the keyboard was not attached, or because the wrong
model of keyboard was attached, or because the machine was plugged into a
docking station with an attached display which was not made by the right
vendor.

These days I'm rather surprised if I attach *anything* I didn't buy with a
PC to the machine and the BIOS doesn't toss its cookies over the side.

I think I may be getting cynical in my old age.

No evidence of bricking

Posted Apr 23, 2009 8:29 UTC (Thu) by gnb (subscriber, #5132) [Link]

>You're surprised that a BIOS is crappy?
No, I realize that's the standard. Disappointed maybe.

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds