Ahh okay, that description kinda sounds like floppy drive power, but it probably is a proprietary thing.
SteveTech
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!)
Code
#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.
If you're already getting an IPv6 prefix allocated, then you can randomise the second half of the address, most devices do this automatically with EUI-64.
Otherwise you pretty much just have to use some sort of IPv6 tunnel.
It's part of GNU Gzip, and zcat is basically just a shell script that runs exec gzip -cd "$@"
meaning you can actually just do cat /usr/bin/zcat
to get the source.
The options that start with HAVE_
usually depend on the arch or compiler. I don't believe it's possible to enable manually without modifying the source itself.
firmware drivers
This sounds like you're talking about firmware blobs that the kernel drivers load, which are usually in a package called linux-firmware
. It should be updated automatically, but I'll check in the morning with Fedora Silverblue.
Otherwise if you're talking about device firmware, than that's all fwupd
, rpm-ostree
has nothing to do with that.
Idk about the UK, but in Australia if you're only sending a small amount of data, some carriers offer IoT plans starting at ~$1/month. So maybe some carriers do the same in the UK?
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 withgit am
.