#microcode — Public Fediverse posts

z386: An Open-Source 80386 Built Around Original Microcode

https://nand2mario.github.io/posts/2026/z386/

#HackerNews #z386 #open-source #80386 #microcode #retrocomputing #technews

80386 Microcode Disassembled

https://www.reenigne.org/blog/80386-microcode-disassembled/

#HackerNews #80386 #Microcode #Disassembly #ComputerArchitecture #RetroComputing #TechHistory

Conditions in the Intel 8087 floating-point chip's microcode

https://www.righto.com/2025/12/8087-microcode-conditions.html

#HackerNews #Intel8087 #FloatingPoint #Microcode #Technology #History #ComputerArchitecture

Conditions in the Intel 8087 floating-point chip's microcode

https://www.righto.com/2025/12/8087-microcode-conditions.html

#HackerNews #Intel8087 #FloatingPoint #Microcode #Technology #History #ComputerArchitecture

Conditions in the Intel 8087 floating-point chip's microcode

https://www.righto.com/2025/12/8087-microcode-conditions.html

#HackerNews #Intel8087 #FloatingPoint #Microcode #Technology #History #ComputerArchitecture

Conditions in the Intel 8087 floating-point chip's microcode

https://www.righto.com/2025/12/8087-microcode-conditions.html

#HackerNews #Intel8087 #FloatingPoint #Microcode #Technology #History #ComputerArchitecture

Conditions in the Intel 8087 floating-point chip's microcode

https://www.righto.com/2025/12/8087-microcode-conditions.html

#HackerNews #Intel8087 #FloatingPoint #Microcode #Technology #History #ComputerArchitecture

Waiting for #AMD to release the RDSEED #microcode fix for the "embedded" #EPYC 4005 series. I think it will be the first time I ever needed or wanted to update my CPU firmware. I know a bit more about it now that I attended the talk about AMD Zen microcode tools at the #39C3.

https://media.ccc.de/v/39c3-the-angry-path-to-zen-amd-zen-microcode-tools-and-insights

https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7055.html

Waiting for #AMD to release the RDSEED #microcode fix for the "embedded" #EPYC 4005 series. I think it will be the first time I ever needed or wanted to update my CPU firmware. I know a bit more about it now that I attended the talk about AMD Zen microcode tools at the #39C3.

https://media.ccc.de/v/39c3-the-angry-path-to-zen-amd-zen-microcode-tools-and-insights

https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7055.html

Waiting for #AMD to release the RDSEED #microcode fix for the "embedded" #EPYC 4005 series. I think it will be the first time I ever needed or wanted to update my CPU firmware. I know a bit more about it now that I attended the talk about AMD Zen microcode tools at the #39C3.

https://media.ccc.de/v/39c3-the-angry-path-to-zen-amd-zen-microcode-tools-and-insights

https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7055.html

Waiting for #AMD to release the RDSEED #microcode fix for the "embedded" #EPYC 4005 series. I think it will be the first time I ever needed or wanted to update my CPU firmware. I know a bit more about it now that I attended the talk about AMD Zen microcode tools at the #39C3.

https://media.ccc.de/v/39c3-the-angry-path-to-zen-amd-zen-microcode-tools-and-insights

https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7055.html

Z8086: Rebuilding the 8086 from Original Microcode

https://nand2mario.github.io/posts/2025/z8086/

#HackerNews #Z8086 #Rebuilding #8086 #Microcode #RetroComputing #Technology #Innovation

Z8086: Rebuilding the 8086 from Original Microcode

https://nand2mario.github.io/posts/2025/z8086/

#HackerNews #Z8086 #Rebuilding #8086 #Microcode #RetroComputing #Technology #Innovation

Z8086: Rebuilding the 8086 from Original Microcode

https://nand2mario.github.io/posts/2025/z8086/

#HackerNews #Z8086 #Rebuilding #8086 #Microcode #RetroComputing #Technology #Innovation

Z8086: Rebuilding the 8086 from Original Microcode

https://nand2mario.github.io/posts/2025/z8086/

#HackerNews #Z8086 #Rebuilding #8086 #Microcode #RetroComputing #Technology #Innovation

Z8086: Rebuilding the 8086 from Original Microcode

https://nand2mario.github.io/posts/2025/z8086/

#HackerNews #Z8086 #Rebuilding #8086 #Microcode #RetroComputing #Technology #Innovation

If you use #btrfs on kernels ranging from 6.12 to 6.19 and get the error:

VFS: Unable to mount root fs on unknown_block(0,0)

Add the 'btrfs' and 'microcode' hooks to /etc/mkinitcpio.conf via chroot and rerun initramfs generation.

If that doesn't help install `intel-ucode.img` and add it to your grub boot parameters in the initrd list.

If that still doesn't help (happens on Intel 3770k and older) disable #zstd initramfs compression, use gzip instead.

You are welcome

#initramfs #microcode

If you use #btrfs on kernels ranging from 6.12 to 6.19 and get the error:

VFS: Unable to mount root fs on unknown_block(0,0)

Add the 'btrfs' and 'microcode' hooks to /etc/mkinitcpio.conf via chroot and rerun initramfs generation.

If that doesn't help install `intel-ucode.img` and add it to your grub boot parameters in the initrd list.

If that still doesn't help (happens on Intel 3770k and older) disable #zstd initramfs compression, use gzip instead.

You are welcome

#initramfs #microcode

If you use #btrfs on kernels ranging from 6.12 to 6.19 and get the error:

VFS: Unable to mount root fs on unknown_block(0,0)

Add the 'btrfs' and 'microcode' hooks to /etc/mkinitcpio.conf via chroot and rerun initramfs generation.

If that doesn't help install `intel-ucode.img` and add it to your grub boot parameters in the initrd list.

If that still doesn't help (happens on Intel 3770k and older) disable #zstd initramfs compression, use gzip instead.

You are welcome

#initramfs #microcode

If you use #btrfs on kernels ranging from 6.12 to 6.19 and get the error:

VFS: Unable to mount root fs on unknown_block(0,0)

Add the 'btrfs' and 'microcode' hooks to /etc/mkinitcpio.conf via chroot and rerun initramfs generation.

If that doesn't help install `intel-ucode.img` and add it to your grub boot parameters in the initrd list.

If that still doesn't help (happens on Intel 3770k and older) disable #zstd initramfs compression, use gzip instead.

You are welcome

#initramfs #microcode

Courtesy of Eric Rechlin of hpcalc.org, now you can watch a fat ugly guy who says "um" far too often, at HHC 2025 talking about and demonstrating the forthcoming Nonpareil II microcode-level simulation of various HP RPN calculators (currently HP-15C and HP-16C):

https://www.youtube.com/watch?v=eraikEonaJQ

The audience really liked that the graphics is fully scalable, rather than only having integer multiple scaling of a bitmap, in the original Nonpareil.

#hhc2025 #Nonpareil2 #rpn #calculator #microcode

Courtesy of Eric Rechlin of hpcalc.org, now you can watch a fat ugly guy who says "um" far too often, at HHC 2025 talking about and demonstrating the forthcoming Nonpareil II microcode-level simulation of various HP RPN calculators (currently HP-15C and HP-16C):

https://www.youtube.com/watch?v=eraikEonaJQ

The audience really liked that the graphics is fully scalable, rather than only having integer multiple scaling of a bitmap, in the original Nonpareil.

#hhc2025 #Nonpareil2 #rpn #calculator #microcode

Courtesy of Eric Rechlin of hpcalc.org, now you can watch a fat ugly guy who says "um" far too often, at HHC 2025 talking about and demonstrating the forthcoming Nonpareil II microcode-level simulation of various HP RPN calculators (currently HP-15C and HP-16C):

https://www.youtube.com/watch?v=eraikEonaJQ

The audience really liked that the graphics is fully scalable, rather than only having integer multiple scaling of a bitmap, in the original Nonpareil.

#hhc2025 #Nonpareil2 #rpn #calculator #microcode

Courtesy of Eric Rechlin of hpcalc.org, now you can watch a fat ugly guy who says "um" far too often, at HHC 2025 talking about and demonstrating the forthcoming Nonpareil II microcode-level simulation of various HP RPN calculators (currently HP-15C and HP-16C):

https://www.youtube.com/watch?v=eraikEonaJQ

The audience really liked that the graphics is fully scalable, rather than only having integer multiple scaling of a bitmap, in the original Nonpareil.

#hhc2025 #Nonpareil2 #rpn #calculator #microcode

Courtesy of Eric Rechlin of hpcalc.org, now you can watch a fat ugly guy who says "um" far too often, at HHC 2025 talking about and demonstrating the forthcoming Nonpareil II microcode-level simulation of various HP RPN calculators (currently HP-15C and HP-16C):

https://www.youtube.com/watch?v=eraikEonaJQ

The audience really liked that the graphics is fully scalable, rather than only having integer multiple scaling of a bitmap, in the original Nonpareil.

#hhc2025 #Nonpareil2 #rpn #calculator #microcode

At HHC 2025, I learned of the existence of another HP-95C in private hands, which makes four that I know of.

The HP-95C was a desktop scientific programmable printing calculator, with continuous (CMOS) memory but no card reader. It would have been introduced in 1976, positioned between the HP-91 desktop non-programmable printing scientific, and the HP-97 desktop programmable printing scientific with magnetic card reader.
1/
#hhc2025 #rpn #calculator #microcode #simulator

At HHC 2025, I learned of the existence of another HP-95C in private hands, which makes four that I know of.

The HP-95C was a desktop scientific programmable printing calculator, with continuous (CMOS) memory but no card reader. It would have been introduced in 1976, positioned between the HP-91 desktop non-programmable printing scientific, and the HP-97 desktop programmable printing scientific with magnetic card reader.
1/
#hhc2025 #rpn #calculator #microcode #simulator

At HHC 2025, I learned of the existence of another HP-95C in private hands, which makes four that I know of.

The HP-95C was a desktop scientific programmable printing calculator, with continuous (CMOS) memory but no card reader. It would have been introduced in 1976, positioned between the HP-91 desktop non-programmable printing scientific, and the HP-97 desktop programmable printing scientific with magnetic card reader.
1/
#hhc2025 #rpn #calculator #microcode #simulator

At HHC 2025, I learned of the existence of another HP-95C in private hands, which makes four that I know of.

The HP-95C was a desktop scientific programmable printing calculator, with continuous (CMOS) memory but no card reader. It would have been introduced in 1976, positioned between the HP-91 desktop non-programmable printing scientific, and the HP-97 desktop programmable printing scientific with magnetic card reader.
1/
#hhc2025 #rpn #calculator #microcode #simulator

At HHC 2025, I learned of the existence of another HP-95C in private hands, which makes four that I know of.

The HP-95C was a desktop scientific programmable printing calculator, with continuous (CMOS) memory but no card reader. It would have been introduced in 1976, positioned between the HP-91 desktop non-programmable printing scientific, and the HP-97 desktop programmable printing scientific with magnetic card reader.
1/
#hhc2025 #rpn #calculator #microcode #simulator

I just gave an HHC 2025 presentation and demonstration of Nonpareil II, my work--in-progress microcode-level HP calculator simulator, now written in C++20 using the Qt6 toolkit. Compared to the original, it uses vector graphics for smooth scaling over a wide range of window sizes.
#hhc2025 #rpn #calculator #microcode #simulator

I just gave an HHC 2025 presentation and demonstration of Nonpareil II, my work--in-progress microcode-level HP calculator simulator, now written in C++20 using the Qt6 toolkit. Compared to the original, it uses vector graphics for smooth scaling over a wide range of window sizes.
#hhc2025 #rpn #calculator #microcode #simulator

I just gave an HHC 2025 presentation and demonstration of Nonpareil II, my work--in-progress microcode-level HP calculator simulator, now written in C++20 using the Qt6 toolkit. Compared to the original, it uses vector graphics for smooth scaling over a wide range of window sizes.
#hhc2025 #rpn #calculator #microcode #simulator

I just gave an HHC 2025 presentation and demonstration of Nonpareil II, my work--in-progress microcode-level HP calculator simulator, now written in C++20 using the Qt6 toolkit. Compared to the original, it uses vector graphics for smooth scaling over a wide range of window sizes.
#hhc2025 #rpn #calculator #microcode #simulator

I just gave an HHC 2025 presentation and demonstration of Nonpareil II, my work--in-progress microcode-level HP calculator simulator, now written in C++20 using the Qt6 toolkit. Compared to the original, it uses vector graphics for smooth scaling over a wide range of window sizes.
#hhc2025 #rpn #calculator #microcode #simulator

World's first #CPU-level #ransomware can "bypass every freaking traditional technology we have out there" — new #firmware-based attacks could usher in new era of unavoidable ransomware
Beek, #Rapid7's senior director of threat analytics, revealed AMD Zen chip bug gave him idea that highly skilled attacker could in theory "allow those intruders to load unapproved #microcode into the processors, breaking encryption at the hardware level and modifying CPU behavior at will."
https://www.tomshardware.com/pc-components/cpus/worlds-first-cpu-level-ransomware-can-bypass-every-freaking-traditional-technology-we-have-out-there-new-firmware-based-attacks-could-usher-in-new-era-of-unavoidable-ransomware

World's first #CPU-level #ransomware can "bypass every freaking traditional technology we have out there" — new #firmware-based attacks could usher in new era of unavoidable ransomware
Beek, #Rapid7's senior director of threat analytics, revealed AMD Zen chip bug gave him idea that highly skilled attacker could in theory "allow those intruders to load unapproved #microcode into the processors, breaking encryption at the hardware level and modifying CPU behavior at will."
https://www.tomshardware.com/pc-components/cpus/worlds-first-cpu-level-ransomware-can-bypass-every-freaking-traditional-technology-we-have-out-there-new-firmware-based-attacks-could-usher-in-new-era-of-unavoidable-ransomware

World's first #CPU-level #ransomware can "bypass every freaking traditional technology we have out there" — new #firmware-based attacks could usher in new era of unavoidable ransomware
Beek, #Rapid7's senior director of threat analytics, revealed AMD Zen chip bug gave him idea that highly skilled attacker could in theory "allow those intruders to load unapproved #microcode into the processors, breaking encryption at the hardware level and modifying CPU behavior at will."
https://www.tomshardware.com/pc-components/cpus/worlds-first-cpu-level-ransomware-can-bypass-every-freaking-traditional-technology-we-have-out-there-new-firmware-based-attacks-could-usher-in-new-era-of-unavoidable-ransomware

World's first #CPU-level #ransomware can "bypass every freaking traditional technology we have out there" — new #firmware-based attacks could usher in new era of unavoidable ransomware
Beek, #Rapid7's senior director of threat analytics, revealed AMD Zen chip bug gave him idea that highly skilled attacker could in theory "allow those intruders to load unapproved #microcode into the processors, breaking encryption at the hardware level and modifying CPU behavior at will."
https://www.tomshardware.com/pc-components/cpus/worlds-first-cpu-level-ransomware-can-bypass-every-freaking-traditional-technology-we-have-out-there-new-firmware-based-attacks-could-usher-in-new-era-of-unavoidable-ransomware

World's first #CPU-level #ransomware can "bypass every freaking traditional technology we have out there" — new #firmware-based attacks could usher in new era of unavoidable ransomware
Beek, #Rapid7's senior director of threat analytics, revealed AMD Zen chip bug gave him idea that highly skilled attacker could in theory "allow those intruders to load unapproved #microcode into the processors, breaking encryption at the hardware level and modifying CPU behavior at will."
https://www.tomshardware.com/pc-components/cpus/worlds-first-cpu-level-ransomware-can-bypass-every-freaking-traditional-technology-we-have-out-there-new-firmware-based-attacks-could-usher-in-new-era-of-unavoidable-ransomware

https://www.theregister.com/2025/05/11/cpu_ransomware_rapid7/

Spoiler alert: Beek followed through and wrote proof-of-concept code for #ransomware that hides in the computer's #processor. "Of course, we won't release that, but it's fascinating, right?"

This, according to Beek, is the worst-case scenario. "Ransomware at the #CPU level, #microcode alteration, and if you are in the CPU or the #firmware, you will bypass every freaking traditional [anti-malware] technology we have out there."

https://www.theregister.com/2025/05/11/cpu_ransomware_rapid7/

Spoiler alert: Beek followed through and wrote proof-of-concept code for #ransomware that hides in the computer's #processor. "Of course, we won't release that, but it's fascinating, right?"

This, according to Beek, is the worst-case scenario. "Ransomware at the #CPU level, #microcode alteration, and if you are in the CPU or the #firmware, you will bypass every freaking traditional [anti-malware] technology we have out there."

https://www.theregister.com/2025/05/11/cpu_ransomware_rapid7/

Spoiler alert: Beek followed through and wrote proof-of-concept code for #ransomware that hides in the computer's #processor. "Of course, we won't release that, but it's fascinating, right?"

This, according to Beek, is the worst-case scenario. "Ransomware at the #CPU level, #microcode alteration, and if you are in the CPU or the #firmware, you will bypass every freaking traditional [anti-malware] technology we have out there."

https://www.theregister.com/2025/05/11/cpu_ransomware_rapid7/

Spoiler alert: Beek followed through and wrote proof-of-concept code for #ransomware that hides in the computer's #processor. "Of course, we won't release that, but it's fascinating, right?"

This, according to Beek, is the worst-case scenario. "Ransomware at the #CPU level, #microcode alteration, and if you are in the CPU or the #firmware, you will bypass every freaking traditional [anti-malware] technology we have out there."

https://www.theregister.com/2025/05/11/cpu_ransomware_rapid7/

Spoiler alert: Beek followed through and wrote proof-of-concept code for #ransomware that hides in the computer's #processor. "Of course, we won't release that, but it's fascinating, right?"

This, according to Beek, is the worst-case scenario. "Ransomware at the #CPU level, #microcode alteration, and if you are in the CPU or the #firmware, you will bypass every freaking traditional [anti-malware] technology we have out there."

Von #AMD-Lücke inspiriert:

#Forscher warnt vor #Ransomware im #CPU-Microcode

Eine Lücke in #AMD-CPUs ermöglicht manipulative Eingriffe in den #Microcode. Darin eingeschleuste #Ransomware wäre äußerst schwer zu bezwingen.

Eine #Ransomware-Infektion kann für Unternehmen weitreichende Folgen haben, die nicht selten auch in einer Insolvenz münden. Durch geeignete Maßnahmen lassen sich die Risiken für solche #Sicherheitsvorfälle eindämmen.

https://www.golem.de/news/von-amd-luecke-inspiriert-forscher-warnt-vor-ransomware-im-cpu-microcode-2505-196112.html

Von #AMD-Lücke inspiriert:

#Forscher warnt vor #Ransomware im #CPU-Microcode

Eine Lücke in #AMD-CPUs ermöglicht manipulative Eingriffe in den #Microcode. Darin eingeschleuste #Ransomware wäre äußerst schwer zu bezwingen.

Eine #Ransomware-Infektion kann für Unternehmen weitreichende Folgen haben, die nicht selten auch in einer Insolvenz münden. Durch geeignete Maßnahmen lassen sich die Risiken für solche #Sicherheitsvorfälle eindämmen.

https://www.golem.de/news/von-amd-luecke-inspiriert-forscher-warnt-vor-ransomware-im-cpu-microcode-2505-196112.html

Von #AMD-Lücke inspiriert:

#Forscher warnt vor #Ransomware im #CPU-Microcode

Eine Lücke in #AMD-CPUs ermöglicht manipulative Eingriffe in den #Microcode. Darin eingeschleuste #Ransomware wäre äußerst schwer zu bezwingen.

Eine #Ransomware-Infektion kann für Unternehmen weitreichende Folgen haben, die nicht selten auch in einer Insolvenz münden. Durch geeignete Maßnahmen lassen sich die Risiken für solche #Sicherheitsvorfälle eindämmen.

https://www.golem.de/news/von-amd-luecke-inspiriert-forscher-warnt-vor-ransomware-im-cpu-microcode-2505-196112.html

Von #AMD-Lücke inspiriert:

#Forscher warnt vor #Ransomware im #CPU-Microcode

Eine Lücke in #AMD-CPUs ermöglicht manipulative Eingriffe in den #Microcode. Darin eingeschleuste #Ransomware wäre äußerst schwer zu bezwingen.

Eine #Ransomware-Infektion kann für Unternehmen weitreichende Folgen haben, die nicht selten auch in einer Insolvenz münden. Durch geeignete Maßnahmen lassen sich die Risiken für solche #Sicherheitsvorfälle eindämmen.

https://www.golem.de/news/von-amd-luecke-inspiriert-forscher-warnt-vor-ransomware-im-cpu-microcode-2505-196112.html

Linux 6.16 will warn users about outdated Intel microcode

Intel is routinely releasing new microcode for their processors to improve the processor’s performance and to fix critical issues, especially when dealing with security vulnerabilities that may be found in old microcode versions. This is to ensure that your system becomes more secure than before by eliminating security vulnerabilities.

A patch has been queued to the Linux kernel tip repository that will make its way to the Linux 6.16 kernel. It warns the user on boot that the microcode version for the processor is old and that it needs to be updated to ensure security. Userspace applications can determine whether your computer is using the old microcode via the /sys/devices/system/cpu/vulnerabilities/old_microcode file.

The kernel, if running in the old microcode, will be tainted with the TAINT_CPU_OUT_OF_SPEC flag, making it more difficult for kernel bugs that have to do with the old microcode to be reported directly to the bug tracker. The implementation relies on a manually-maintained list of processors found in the intel-ucode-defs.h file. It contains a list of structures that contain the following variables:

• flags: List of flags (always X86_CPU_ID_FLAG_ENTRY_VALID)
• vendor: Processor vendor (always X86_VENDOR_INTEL)
• family: Processor family (usually 0x6 or 0xf)
• model: Processor model
• steppings: Processor stepping
• driver_data: Processor microcode ID as an integer

Not only that, but all processors that are running on a debug microcode (that is, microcode ID with the 31st bit set to 1) are considered to be old.

We advise you to update your processor’s microcode to the latest version to ensure that there are no security vulnerabilities present.

#intel #Kernel #Linux #LinuxKernel #Microcode #news #processor #processors #Tech #Technology #update