/C:
rotopenguin
joined 2 years ago
The "AI boom" means that Intel is going to take die space from the GPU and give it to an NPU. That's how you get Windows 11®️ CoPilot™️ cetified.
Lol I guess they could mount the deck to show as a scoreboard.
Frick, I'm going to have to check out Farmer Was Replaced.
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.
I have a monitor with awful speakers (thanks Acer), and SteamOS will dutifully switch to them instead of using its own much better speakers. I made a non-steam shortcut with this abomination to kick it back to the internal speakers (manually run it whenever you plug into the dock/external screen).
pactl set-default-sink 'alsa_output.pci-0000_04_00.5-platform-acp5x_mach.0.HiFi__hw_acp5x_1__sink'
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.
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.