this post was submitted on 20 Aug 2024
53 points (98.2% liked)

Hardware

473 readers
32 users here now

All things related to technology hardware, with a focus on computing hardware.


Rules (Click to Expand):

  1. Follow the Lemmy.world Rules - https://mastodon.world/about

  2. Be kind. No bullying, harassment, racism, sexism etc. against other users.

  3. No Spam, illegal content, or NSFW content.

  4. Please stay on topic, adjacent topics (e.g. software) are fine if they are strongly relevant to technology hardware. Another example would be business news for hardware-focused companies.

  5. Please try and post original sources when possible (as opposed to summaries).

  6. If posting an archived version of the article, please include a URL link to the original article in the body of the post.


Some other hardware communities across Lemmy:

Icon by "icon lauk" under CC BY 3.0

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Schmuppes@lemmy.world 12 points 4 weeks ago* (last edited 4 weeks ago) (2 children)

Yeah, I couldn't believe it when I read that my 5 yo 3700X was not gonna get patched. I would have had a hard time buying another Ryzen when my platform upgrade is due in 2-3 years' time.

Edit: How will the fix be rolled out? Do I have to wait for a BIOS update?

[–] Fecundpossum@lemmy.world 8 points 4 weeks ago

This is my assumption, so I’ve been watching my motherboard’s OEM’s support site for an update to drop. I find it absolutely maddening that of the 20 or so articles I’ve read on this matter, not a single fucking one has mentioned how less educated users might go about patching this vulnerability. The tech journalists care about the clicks and literally nothing else.

Microcode is usually bundled with bios updates.