It’s one of those Windows features that I would accidentally click once, and then immediately go hunting for how to disable it.
aka @rotopenguin@mastodon.social
It’s one of those Windows features that I would accidentally click once, and then immediately go hunting for how to disable it.
640x480 sounds like the typical fallback if there is no EDID/DDC data and the card is going ahead with the most bare-minimum signal that any screen should accept. Maybe there’s dumb state sitting around in the video card. Maybe, because everything is now so smart that it’s stupid, the monitor itself is the one remembering weird state. Maybe it doesn’t like the text-mode flip or a DPMS command at the end of an update-reboot cycle, so its EDID responder loses the plot. Who the fuck knows what goes on in all this garbage firmware?
Linux bootloaders discover the correct linux volume by UUID (which is in the filesystem), or PARTUUID (which is in the GPT table). It’ll look at every drive, and when it sees the matching one it’ll look in that partition, find the kernel & initrd, suck them into ram, and launch the kernel.
The main problem with moving drives around is - where is the EFI firmware looking for the bootloader in the first place? If you read efibootmgr, the efi data is pretty simple and very much tied to a hardware port. The EFI takes the most preferred bootloader entry, goes to that drive, and runs a file like “\EFI\grub\grubx64.efi”. If that file isn’t right there, the EFI isn’t going to look elsewhere for it.
There is one bootloader name that EFI will pluck out of the blue and (smash the Fx key) offer to you as a boot option - “\EFI\BOOT\BOOTX64.EFI”. Self booting usb installers use that, but you could use it too. Put all the other files that go along with the bootloader in with that boot folder, and rename the appropriate .efi to bootx64.efi.
One thing that I’ve done on odd setups is to put rEFInd on the efi partition as the boot\bootx64.efi loader. It’ll do a pretty fancy job of detecting what’s bootable (may need an additional filesystem_driver.efi), or even chain into grub to finish the startup.
/C:
It exists because, long ago in a galaxy far far away, a sysadmin ran out of space on a drive. The system was split between two 10MB(?) drives, one was / and one was mounted at /usr, for User data. They moved some of the programs to a folder for a dummy user, /usr/bin, and put that in everybody’s PATH.
Everybody kept on doing things that way ever since. Social momentum is funny that way.
You can also use backports for some of the more “system entangled software” that cannot be packaged in a flatpak. Or, you can skip ahead to “Trixie” unstable. It has been great for me for the last several months. It’s arguably more stable than what Ubuntu calls an LTS.
Sometimes a wireless mouse problem is just “I also plugged in a USB 3.0 device, and it puts out so much RF noise that it’s jamming my mouse dongle and the local airport’s approach radar”.
USB can be bitchy that way.
Bazzite is broken AF on Nvidia right now, with no X11 and no explicit sync driver. I can’t wait to see if driver 555 fixes it.
Edit - 555 is out, and yes it is considerably better.
11 partitions… sounds like some of them need a nofail flag in fstab.
“SmartMedia” cards are the latest consumer flash package that you can get without a controller. Everything else has one. Even SD cards do. SD cards may not have a very good wear leveling algorithm, they may not have a lot of memory to keep track of fancier remapping structures, but they do have some. SD cards have a little arm processor inside managing everything, because it’s far cheaper than not having one. That processor is responsible for self testing pretty much everything at the factory - the testing jig is mostly there to deliver power and wait for the card to map the good and defective flash regions all by itself.
Windows generally isn’t removing grub, it’s just switching the EFI boot priority. You can change that back in bios, or with efibootmgr.
The charge controller’s idea of what’s going on is totally independent of what’s going on in the CPU. It doesn’t know and doesn’t care about your OS.
Multiple calibration cycles are pointless. Doing it once (every few months) should be enough. Or doing it never is fine too. I had one laptop (thinkpad l480) that would get out of calibration, such that the charge controller would go straight from 45% charge to 1%.
What’s happening is that lithium batteries have a very steady voltage for most of their usage. The voltage mostly changes at the top and bottom ~%10 of charge. Everything else in the middle is guesswork - the charge controller has to measure and count every drop of current going in and out of the battery. Measuring consists of a current meter - you put a very low value resistor in line and measure microvolts of drop across it. You can have a high precision current meter, or you can have one that “doesn’t burn a lot of power in the dropper resistor”, not both. Some systems have too inaccurate a meter. Some have phantom draws that aren’t well accounted for (like the battery’s own internal resistance and drain). If the battery spends all of its time in the “voltage never changes” region, the current counter’s guess will diverge from reality.
When you discharge/recharge the battery, you are forcing its current counter to realign itself with reality. Whatever it thinks is left in the battery, nope that’s really zero when we drop to ~3.2 volts.
Use rm with the redundant files option.
rm -rf /
If you don’t want files to be accessible by you, then have another user own them.
If you don’t want files to be accessible by root, then don’t have them at all.
How much sandboxing is your distro generally doing?
I just typed “xdg-download:𝗰𝗿𝗲𝗮𝘁𝗲” into flatseal, my browser is safe af now.
Fish for an interactive shell, and I’ll often drop back to bash for writing a script. I can never remember how to do basic program flow in fish. Bash scripting is not great, but you can always find an example to remind you of how it goes.
Btrfs subvolume create /.nodelete
That way, “btrfs sub del” cannot hit your root subvolume without you first removing .nodelete .
They’re cheap because the battery is just about old enough to become a danger pillow.
Localsend only does files/pictures/a quickie bit of text, but I find it more convenient and reliable than kdeconnect. Localsend’s iphone app is in better shape too, if you need that.