this post was submitted on 25 Jul 2024
104 points (100.0% liked)
Technology
37699 readers
352 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No bios update, but you most likely received both microcode updates (which is what will fix/mitigate the Intel issue, the bios is only to ensure everybody gets the microcode update) and firmware updates (from
linux-firmware
)Of course non-mainlined (i.e. not in the linux kernel) firmware is a bit more iffy, luckily it's getting slowly better with OEMs using
fwupd
for those scenarios