Welp no change. I’m guessing the motherboard firmware already contained the latest microcode. Oh well, was worth a try, thank you.
Welp no change. I’m guessing the motherboard firmware already contained the latest microcode. Oh well, was worth a try, thank you.
It’s a pain in the butt to swap CPUs one more time but that may pale in comparison to trying to convince the shop that a core is bad and having intermittent faults. 🤪
This sounds like my best shot, thank you.
I’ve installed the amd-ucode
package. It already adds microcode
to the HOOKS
array in /etc/mkinitcpio.conf
and runs mkinitcpio -P
but I’ve moved microcode
before autodetect
so it bundles code for all CPUs not just for the current one (to have it ready when I swap) and re-ran mkinitcpio -P
. Also had to re-run grub-mkconfig -o /boot/grub/grub.cfg
.
I’ve seen the message “Early uncompressed CPIO image generation successful” pass by, and lsinitcpio --early /boot/initramfs-6.12-x86_64.img|grep micro
shows kernel/x86/microcode/AuthenticAMD.bin
, there’s a /boot/amd-ucode.img
, and an initrd
parameter for it in grub.cfg
. I’ve also confirmed that /usr/lib/firmware/amd-ucode/README
lists an update for that new CPU (and for the current one, speaking of which).
Now from what I understand all I have to do is reboot and the early stage will apply the update?
Any idea what it looks like when it applies the microcode? Will it appear in dmesg
after boot or is it something that happens too early in the boot process?
BIOS is up to date, CPU model explicitly listed as supported, memtest ran fine, not using XMP profiles.
All hardware is the same, I’m trying to upgrade from a Ryzen 3100 so everything should be compatible. Both old and new CPU have a 65W TDP.
I’m on Manjaro, everything is up to date, kernel is 6.12.17.
Memory runs at 2133 MHz, same as for the other CPU. I usually don’t tweak BIOS much if at all from the default settings, just change the boot drive and stuff like “don’t show full logo at startup”.
I’ve add some voltage readings in the post and answered some other posts here.
Everything is up to date as far as I can tell, I did Windows too.
memtest ran fine for a couple of hours, CPU stress test hang up partway through though, while CPU temp was around 75C.
Yep, it’s explicitly listed in the supported list and BIOS is up to date.
RAM is indeed at 2133 MHz and the cooling is great, got a tower cooler (Scythe Kotetsu mark II), idle temps are in the low 30’s C, stress temp was 76C.
Motherboard is a Gigabyte B450 Aorus M. It’s fully updated and support for this particular CPU is explicitly listed in a past revision of the mobo firmware.
Manual doesn’t list any specific CPU settings but their website says stepping A0
, and that’s what the defaults were setting. Also I got “core speed: 400 MHz”, “multiplier: x 4.0 (14-36)”.
even some normal batch cpus might sometimes require a bit more (or less) juice or a system tweak
What does that involve? I wouldn’t know where to begin changing voltages or other parameters. I suspect I shouldn’t just faff about in the BIOS and hope for the best. :/
The problem is that the main container can (and usually does) rely on other layers, and you may need to pull updates for those too. Updating one app can take 5-10 individual pulls.
The Hoffman recipe is 12g of coffee, 250ml of water, 2 minutes steep time, give a small swirl to the recipient, steep another 30 seconds, then press down slowly over at least another 30 seconds. You can find the video on youtube.
There are many other factors involved such as the size of the grind, the uniformity of the grind, the temperature of the water, the steeping time, and the quantities of coffee and water – so really the recipe is just meant as a starting point. You will need to dial it in for each different batch of coffee.
Most of these factors have to do with caffeine extraction aka “yield”. More time steeping, hotter water, more water & coffee and finer grind all increase extraction but in different ways, and over-extraction usually ends up tasting bitter. The opposites decrease extraction and under-extraction ends up tasting sour. The Hoffman recipe is a balanced start.
With the Aeropress you have easy access to all these factors and can customize the brew extensively but you have to do some trial and error.
Well that’s the nice part about the Aeropress, the process is so customizable that you can find a good recipe for just about any coffee.
The Hoffman recipe is not meant to be perfect, just a safe starting point. It can’t possibly fit every single coffee batch out there.
Ironically, if Graphene would succeed, it would lead to a system that’s every bit as locked down as a manufacturer’s Android. GrapheneOS would also not allow you to have root etc.
IMO Graphene wants a place at the big player table. They’re not in it for user freedoms.
Trump’s appointments tipped the balance. They didn’t “decide” as much as been taken over. It’s a part of the judicial system gone rogue and Congress is supposed to reign it back in.
I would uninstall the screensaver so fast if I saw a nag screen. Wtf it’s a screensaver, what does it matter? I’ll use a version that’s 50 years old if I want to.
Alright, have fun with that. 🙂
If you mean to do that in the public DNS records please note that public records that point at private IPs are often filtered by ISP’s DNS servers because they can be used in web attacks.
If you don’t use your ISP’s DNS as upstream, and the servers you use don’t do this filtering, and you don’t care about the attacks, carry on. But if you use multiple devices or have multiple users (with multiple devices each) eventually that domain will be blocked for some of them.
Generally speaking, a subdomain like jellyfin.myhome.com
will work out much better than a subpath like myhome.com/jellyfin
.
Very few web apps can deal well (or at all) with being used under a subpath.
optical media doesn’t last that long (5-10 years) and is easily damaged
I beg to differ. I’ve been backing things up to optical for 25 years now with minimal issues. CDs could be easily scratched but it hasn’t been the case for DVD and BR.
M-DISK uses in-organic substances that make the discs mostly immune to exposure but it’s a more recent invention. Proper storage and handling still goes a long way towards protecting discs even if they’re not in-organic.
Honestly I’ll just send it back at this point. I have kernel panics that point to at least two of the cores being bad. Which would explain the sporadic nature of the errors. Also why memcheck ran fine because it only uses the first core by default. Too bad I haven’t thought about it when running memtest because it lets you select cores explicitly.