I hadn’t restarted my serial logger after I rebooted my laptop, leaving me with no clue about what caused the crash.

Probably way too late now, but if it was a proper kernel panic, it should’ve saved the dmesg in the kernel’s pstore which saves to either ACPI or EFI storage (depending on BIOS or UEFI), which systemd then extracts to /var/lib/systemd/pstore/ on next reboot.

Oh damn, phoronix comments are usually bad, but they really got off the rails this time!

I noticed it the other day too. The flatpak version let me add one SSH key, but another with password protection would only error.

I’ve never tried it, but there’s Waypipe.

Unless you are moving gigabits of data, you won’t notice the difference the smaller header payload of ipv6 offers.

IPv6 headers are usually bigger anyway¹, so the only advantage is more efficient routing (so infinitesimally better latency), but in my experience most routers only support IPv4 hw offload and not IPv6, so it’s only more efficient in theory.

I just like IPv6 because I get a whole /56 prefix to play with, and devices often randomise their host portion through the privacy extensions, meaning they use a new address each day or so.

¹ IPv4 is usually ~20 bytes, but it can be up to 60 bytes if you stack a lot of options, IPv6 is only 40 bytes AFAIK.

You might be able to manually enable IPv6 in Optus’ APN.

My Telstra eSIM didn’t automatically enable IPv6, when my physical SIM did, but enabling it in the telstra.wap APN fixed it.

For the AMD version, if you’re going for an almost all Type A layout or something, it’s handy to note that the Type A expansion card have idle power issues in the back ports.

https://knowledgebase.frame.work/en_us/expansion-card-functionality-on-framework-laptop-13-amd-ryzen-7040-series-SkrVx7gAh

I’ve seen an S3 option in Smokeless_UMAF, so maybe you can enable real suspend, but I haven’t tried on my Framework 13 AMD.

It seems like it’s fixed now, but if possible use one of the mirrors, so everyone’s not hitting that one server all that hard, it’s usually faster too.

Or even better, use the torrent.

Most thermal paste isn’t electrically conductive, so that blob inbetween the capacitors shouldn’t be an issue, but it would be good to know what thermal paste it is to be sure.

This format’s from 2017 I’m pretty sure.

https://hepwori.github.io/execorder/

I initially read it as “No everything is impossible”, which is now my favourite motivational quote.

Could you run dmesg? That will give you logs from the kernel, and you can see what’s slowing it down.

Yes, but it doesn’t look like KPROBES_ON_FTRACE is supported on arm64. I did find this patch though which implements it: https://patchwork.kernel.org/project/linux-arm-kernel/patch/[email protected]/

If you don’t know how to apply a patch, you can either paste the link into b4, or download the mbox and apply it with git am.

Ahh okay, that description kinda sounds like floppy drive power, but it probably is a proprietary thing.

Could also be slimline sata.

Does your BIOS report temperature? Cross reference with that, some boards need custom adjustments. If they’re not in the BIOS it’s possible there isn’t a thermistor connected and they’re just registering noise.

Probably a long shot, but if you live in Australia (or maybe also New Zealand), Jaycar often sells the Ender 3 V3 SE for AU$250, which seemed like a really good price compared to other places I found.

I couldn’t find a hard answer to whether this supports EPYC only, or Ryzen too; so I put together this script to read the CPUID to detect for INVLPGB support according to the AMD64 Programmer’s Manual, and my 7800X3D does not support INVLPGB.

(Let me know if I’ve made an error though!)

#include <stdio.h>
#include <stdint.h>

int main() {
    uint32_t eax, ebx, ecx, edx;

    eax = 0x80000008;

    __asm__ __volatile__ (
        "cpuid"
        : "=a" (eax), "=b" (ebx), "=c" (ecx), "=d" (edx)
        : "a" (eax)
    );

    printf("EBX: 0x%x\n", ebx);

    if (ebx & (1 << 3)) {
        printf("CPU supports INVLPGB\n");
    } else {
        printf("CPU does not support INVLPGB\n");
    }

    return 0;
}

That’s INVLPG which has been there since the 486. The AMD64 Programmer’s Manual has some info on the differences between INVLPG, INVLPGA, and INVLPGB though.