this post was submitted on 04 Feb 2024
278 points (99.3% liked)

Technology

59589 readers
3394 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] 7heo@lemmy.ml 18 points 9 months ago* (last edited 9 months ago) (8 children)

~~Somehow I doubt that manufacturers of 13 years old motherboards are going to update their UEFIs... I would love to be proven wrong, but it was hard enough to find a UEFI able to POST with a 2080 super already.~~

Edit: I apologize for having missed the point entirely. I would like to thank SteveTech@Programming.dev for bringing this to my attention. This is actually a firmware hacking mod that works by flashing an already modified (using the tools documented in the linked page) firmware to the UEFI EEPROM of a motherboard.

However I will take the opportunity of hijacking my own comment to point out a couple (important) facts:

  1. Ron Minnich, one of the coreboot developers, once gave me the following, (hardware) life saving advice:

Do not flash firmware on a UEFI EEPROM without having a mean to rescue your board. Meaning buy another chip, get a programmer and keep the original firmware onto the original EEPROM.

  1. Some UEFI firmwares are signed. Obviously, modifying them will break the cryptographic signature. This might entirely prevent you from flashing them, but if it does not, it will in any way always prevent the motherboard from checking the integrity of the file. Therefore, only modify a verified firmware, in a way that you understand. And ideally, sign it afterwards with your own key (or at least keep a copy of its hash in a separate location). This will not help wrt the motherboard, but it will absolutely help you making sure the firmware has not been modified any further.
[–] SteveTech@programming.dev 10 points 9 months ago (1 children)

That's exactly why this project exists, to allow users to add ReBAR support to their old motherboards.

[–] 7heo@lemmy.ml 3 points 9 months ago
load more comments (6 replies)