|
| ▲ | __patchbit__ 4 hours ago | parent | next [-] |
| At boot time, the following package provides the latest Intel CPU microcode data files on NetBSD. sysutils/intel-microcode-netbsd
dmesg shows cpu 0: ucode 0xf0->0xf6
cpu 1: ucode 0xf0->0xf6
|
|
| ▲ | altairprime 5 hours ago | parent | prev | next [-] |
| https://github.com/intel/intel-linux-processor-microcode-dat... $ echo 1 > /sys/devices/system/cpu/microcode/reload
Hot-swappable, even. TIL! |
|
| ▲ | throwaway2037 an hour ago | parent | prev | next [-] |
| Why is this downvoted? (At the time of writing, the text is grey, so it has at least a few downvotes.) This is a good question. As others have noted below, yes, and sometimes you can see kernel logging on start-up when the microcode is loaded. |
| |
| ▲ | varispeed an hour ago | parent [-] | | Classic HN elitism. Oh this peasant doesn't know the basics and dares to ask question that I deem stupid? DOWNVOTE |
|
|
| ▲ | bri3d 6 hours ago | parent | prev [-] |
| Yes? It is regularly; both the firmware or the OS can deliver updates depending on configuration. The Raptor Lake CPUs in question have gone through an enormous number of microcode revisions already due to quite famous voltage scaling issues; it's unclear if this errata is fallout from or related to a similar root cause or just another issue with the processor. |
