SteveTech @ SteveTech @programming.dev

New account: @SteveTech@aussie.zone

---

Read more

Posts

4

Comments

461

Joined

3 yr. ago

Surely this wasn't the same report that failed to find any EV maker that actually uses 'dirty nickel', but concluded they were anyway.

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.

What motherboard do you have?

If it's related to memory context restore, I also had to toggle 'power down enable' on my setup.

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.

I thought Discord gave you the option to send a message as a file now, or maybe that was desktop.

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

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/

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.