The_Decryptor

Or Automattic doesn’t have enough employees left to implement it

I mean, the point of the init process is to bring up the filesystem and disks, if the configuration is wrong that’ll be the process to complain about it.

“No, go away.”

That’s a perfectly valid way to deal with toxic contributors. There’s always people with better social skills and equal developer skills out there, you don’t have to accept and include toxic people just because they wrote some code.

I’d double check, if you haven’t picked an option specifically it might just default to the fallback (i.e. BOOTX64) It’ll be under the boot device order section.

(Not my picture, stole it from Reddit)

Here it’s listing all the possible boot options this mobo can find, but there’s a generic “UEFI OS” option which I’d bet is the fallback. And once a choice is made it’s kept unless something resets it, so if it just happened to be set to the fallback once it’ll stick with that until a change is forced.

When installing windows while there is a Linux install, windows will see the EFI partition already there and just decides to share it, and doesn’t create its own.

That’s what it’s supposed to do, it’s a plain FAT32 partition, the bootloaders are just files you put in there.

Part of the issue is that while a well-made motherboard will look for all bootloaders on the partition and present them as options in the firmware UI, bad ones will only look for a specific file (\EFI\BOOT\BOOTX64.EFI) and use that. For an OS to have a chance of booting on those boards it has to overwrite that file, blowing away whatever other bootloader was there before.

It’s annoying, since Windows is mostly well behaved here (It puts the main copy of the bootloader at \EFI\Microsoft\Boot\bootmgfw.efi and Linux bootloaders can see that and offer it, the reverse isn’t true) and can co-exist with Linux well (Well…), but manufacturers cutting corners causes more problems for everybody.

Good news, they’re making it easier to fix stuff like “spurious double clicks”.

https://who-t.blogspot.com/2025/05/libinput-and-lua-plugins.html

I can’t imagine the shame I’d feel if there was a legal finding stating that I was a fan of the minions.

e.g. Mastodon has been around for years, is actually really federated, not owned by a corporation, and a lot more features than BlueSky… but bluesky already has more users and i think largely because: marketing… how are people going to talk about “Mastodon” when they’ve probably never even heard the word before? (also named after a cool band, but not suitable for the masses).

Also fewer syllables, which apparently has a noticeable impact.

From a quick search it seems that the mobo uses a Realtek audio chip, which is probably the actual problem. My current system build uses one and it barely worked under Windows, it’d randomly remap the channels, sometimes it just wouldn’t come up properly (Showed as only a microphone, etc.), had lots of static noise, would constantly think I was unplugging and replugging headphones in, etc. Just a terrible experience compared to the Intel audio system the build before this used.

As much as “just buy another bit of hardware” is an awful bit of advice, I’d recommend getting a USB DAC/soundcard, I bought a cheap soundblaster one and it fixed all my problems. USB audio is a well-defined standardised protocol that’s supported by just about everything, does away with any driver issues or incompatibilities, can be moved between devices, etc. Mine’s a “gaming” model so it’s just a USB port on one side and a headset jack on the other, but you can also get ones with proper inbuilt amplifiers to run full speaker kits, etc.

Yeah, the days of end users installing their own OS is in the past, PCs are appliances for most people now.

They were a bit too public with “Dual_EC_DRBG”, to the point where everybody just assumed it had a backdoor and avoided it, the NSA ended up having to pay people to use it.