Do you know *what* is broken?

Date: 2013-02-09 05:38 pm (UTC)
From: (Anonymous)
Matthew, I had a similar issue some time ago regarding notebooks that got "bricked" by a bug in the proprietary nVidia driver. The issue that time was that the driver somehow managed to overwrite the EDID data of the display with garbage. So the driver failed to load and on the next start the BIOS failed to load as well because the video BIOS couldn't identify the display and stopped at that problem. So it would be interesting to know what really gets broken when that bug occurs. Does Samsung know what is dead and how to fix it yet? In my case the bug could be fixed by removing the display and booting with an external monitor. Then reconnect the display and flash the correct data back to the display. Dunno if something like that would help here. Samsung should probably know. The question is if they tell you?
From:
Anonymous
OpenID
Identity URL: 
User
Account name:
Password:
If you don't have an account you can create one now.
Subject:
HTML doesn't work in the subject.

Message:

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org


 
Notice: This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.

Profile

Matthew Garrett

About Matthew

Power management, mobile and firmware developer on Linux. Security developer at Nebula. Member of the Linux Foundation Technical Advisory Board. Ex-biologist. @mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer.

Expand Cut Tags

No cut tags