• 1 Post
  • 12 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle
  • lemmyvore@feddit.nlOPtoLinux@lemmy.mlCPU errors?
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 days ago

    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.




  • lemmyvore@feddit.nlOPtoLinux@lemmy.mlCPU errors?
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    2 days ago

    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?



  • lemmyvore@feddit.nlOPtoLinux@lemmy.mlCPU errors?
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    3 days ago

    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.




  • lemmyvore@feddit.nlOPtoLinux@lemmy.mlCPU errors?
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 days ago

    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. :/



  • Is there a reason to expose your services to the whole internet? That’s what CF tunnels and Tailscale Funnel do.

    I can’t really recommend either of them, Funnel forces you to use a .ts.net subdomain you can’t use your own domain. CF allows it but forces you to use their DNS service. Both CF and Tailscale play MITM with your HTTPS connection, meaning they decrypt and reencrypt it on the fly, meaning they are able to look at your unencrypted traffic.

    If you really must expose your services publicly then get a cheap VPS, point your domain A and AAAA records at its public IPs, make a tunnel from your server to the VPS, and forward connections to port 443 on the VPS public interface through the tunnel to the reverse HTTP proxy running on your server (with mandatory TLS encryption and Let’s Encrypt certificates for your domain).

    This way you get an unbroken TLS connection all the way through, with nobody in the middle.

    The tunnel that you use between your server and the VPS can work behind CGNAT because it’s outgoing.

    Technically the tunnel doesn’t necessarily need to be encrypted because it will only carry TLS connections anyway, but then you have to deal with authorization. It’s probably simplest to do an SSH tunnel.