Hacker News Reader

More often than not, the changelog just states "performance improvement" or "bug fix", without any detail on what they've done.

For example, I've been bitten before by Dell due to plundervolt updates that removed the undervolting capability under the umbrella of "security fixes".

View on HN

> I've been bitten before by Dell due to plundervolt updates that removed the undervolting capability

That's enterprise computing for you.

Been bitten by that kind of shenanigan more often than I can remember.

Happened to a colleague. Not sure if he ever found out how to rollback to the older version.

Usually there isn't, unless there is a sufficiently serious issue with the update.

Why wouldn't there be a rollback option, especially on enterprise hardware? If it breaks something you need to revert, and quickly

Usually BIOSes can be flashed with the machine off, using a "chip-clip" programmer.

They can but the data on the chip is a combination of machine specific identifiers, config data, and BIOS code. If you chip flash it you have to get an image from some sketchy place and it will nuke your serial number etc. You can also have problems if your RAM is made by a different manufacturer. Chip flashing is a last resort.

Reply on news.ycombinator.com