It can, but it requires creating your own signing key, registering it with secure boot, and signing your nvidia driver.
There’s a guide here: https://askubuntu.com/a/1049479
But if you’re running any out of tree drivers (e.g. the nvidia driver), I’d recommend just leaving secure boot off.
Before other people start commenting ‘yeah obviously’, it’s their April Fools video, it’s pretty funny.
I never mentioned vulnerabilities, I just wanted to point out that, RDP doesn’t really work without a graphical session, Windows Server Core gets around this by being a graphical session (although very basic).
Also I’m not sure, but I don’t think Windows handles RDP on the kernel level, it’s just nicely tied in with DWM and doesn’t have to deal with the multitude of window managers on Linux.
Handling RDP on the kernel level does sound like a bad idea security wise, but there should be a better way.
Windows Server Core still has a window manager, just all it does show a command prompt very similar to the one in the usual Windows recovery environment.
I wonder if this made it into the android kernel: https://www.androidpolice.com/pixel-stutter-bug-addressed-by-third-party-dev/
Or if it is just general updates.
You have to be on the March update, then go to Developer options -> Linux environment, and enable it. Then ‘Terminal’ will appear in your apps drawer.
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’ve never tried it, but there’s Waypipe.
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.
This format’s from 2017 I’m pretty sure.
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/20191218140622.57bbaca5@xhacker.debian/
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.
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.
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.
The symbol they defined out is not the equals symbol but rather U+2550, so the for loop is fine.