Moderators: peebee, Forum moderators
Runnung voidpup-64 22.02 on an intel N97 computer.
There is a microcode update for RFDS, and the correct file (No extension) was installed in /lib'firmware
I then discovered that grub4dos in GPT stick install looks in the fdrv copy of the install location.
SFS editted, and the intel_ucode directory with the ucode file moved there. Then reboot...
dmesg | grep microcode reports 'no microcode'.
Edit sfs again, adding a .ucode extension... still fails.
Need help with this
Regards
N97
I miss nooby, we both joined within days of each other in 2008. Its a long road here for me, but I grow and change, as we all do, know it or not, like it or not.
@N97 New pups (like Bookwormpup64) have a microcode loading mechanism in their fdrv. Most other puppies require other steps for activation. I use an older method, as follows:
I make microcode files (latest 2024-11-12), & it plus steps to use it are here: https://forum.puppylinux.com/viewtopic.php?p=9658#p9658
Hope that's useful.
no loading mechanism found in fdrv... see 1st post again for system properties... voidpup-64 22.02.
I miss nooby, we both joined within days of each other in 2008. Its a long road here for me, but I grow and change, as we all do, know it or not, like it or not.
The only kind of microcode updates you can get using fdrv is "late loading", which probably won't work. You want "early loading", which requires ucode.cpio and configuring the boot loader to load it.
However, the best kind of microcode updates is through firmware update. If your device has available BIOS or UEFI updates from the vendor, apply all of them because they can update microcode to the latest version for your CPU. If the vendor no longer provides them, ucode.cpio is your best option.
If the Puppy you use comes without ucode.cpio, ask the developer to include it because using old microcode (maybe even the factory microcode, which can be ancient) can affect performance, security, stability and even your device's longevity.