• 0 Posts
  • 70 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle


  • The time it took you to write this would have been better spent reading the article:

    Because Android isn’t technically “installed” on the Switch, but rather an external microSD card, you can switch between the default system and Lineage at any time.

    Running Lineage is a big deal for those of us who have a switch laying around that no longer have a use for it.

    • It can be an android tv device replacement
    • Buy a $20 goose neck tablet mount, and now it’s a way to play streamed steam games or use the android tv jellyfin client to watch/play stuff without using the main TV
    • Bedside clock/radio with loads of extra features
    • Dedicated HomeAssistant remote

    Or, the basic use case - Play emulated games on a neat handheld package with a decent screen on a plane or something, without needing to carry or buy another device.






  • S3 is what people actually think of when they think of sleep mode, or modern standby. The running state of the operating system is stored in RAM, in low power mode. All context for the cpu, other hardware like disks and network is lost and those devices are completely shut down - bar the RAM. Basically, you close the lid at the end of the day, and you’re nearly at the same charge level the next morning.

    This saves a lot of power. On my older 8th gen intel cpu laptop, it loses maybe 1-2% charge per day in this mode.

    My new 13th gen laptop still has deep sleep, or standby (s3) as a hardware function, but it’s technically not supported. It actually doesn’t work when enabled, and just falls back to s1 (sleep, everything’s still on, just in low power mode). It loses about 2-3% per hour in this mode

    S4 (Hibernate) does roughly the same as S3, but the OS state is stored to the disk instead of ram, so that can be shut off too. Now the device is completely powered off, losing no charge while ‘asleep’.

    S5 is off

    S4 sleep takes much longer to wake up from than s3, so was less desirable. In the modern computing world (especially end user devices), commonly there’s full disk encryption going on, which adds a layer of complexity to resuming from disk, as you would when waking up from hibernation (s4).

    Making it resume without putting in a decryption password for example (using a TPM), isn’t simple, and breaks a lot when you do system upgades



  • I can honestly say my space grey first-gen magic keyboard has served me well. It sits on my desk at work, I use it every day, and it only needs charging once every few months.

    The only thing I’ve ever done to damage it is pulling the z key off to clean between the keys, I tried to jam it back on wrong and ruined part of the scissor mechanism

    My next keyboard may yet be one of the newer models, but it’s to expensive to pull the trigger yet.

    Having tried it in person, I’m also considering the logitech mx keys mac variant. I didn’t even notice the key shaping while actually typing, and it’s the first keyboard I’d say comes close to being a magic keyboard replacement.

    I like the option(alt)/command(super) switched layout.

    I’ve got a keychron k3 ultra v2 too. I finally gave in on the mechanical keyboard train and splurged a bit - but now:

    • I need a wrist rest, even this ultra low profile version is way higher than I’m used to.
    • I hate the layout (my own fault for buying the most cramped version)
    • On linux at least, bluetooth is not the greatest (sometimes needs a keyboard restart to fix key send delay and repeat keys)
    • I picked the optical (cherry mx red equivelant) switches and they’re mushy af.

    I’ve had the white slim first-gen mini magic keyboard for years too. The battery swelled up, so I removed it and use it wired now. That was probably 8/9 years old.











  • Ubuntu GUI/apt fail

    Back when I used ubuntu, Unity was stuck with old gnome packages. This meant that the version gnome-terminal packaged with ubuntu (up to at least 18.04) didn’t have text reflow on window size changes.

    You could add the upstream sources, upgrade the specific text reflow package only, and then disable the sources.

    I forgot to disable the sources, or typed dist-upgrade (this happened multiple times…). Broke the whole desktop/lightdm setup with half upgraded packages, and half removed packages (for preparation to install new versions). Way easier to reinstall the os than to disentangle. Unity was a mess then anyway.

    Moral: Actually read the package change summaries when doing updates/removes/installs, and [ y/N ] means actually check what the fuck you think you’re agreeing to.

    BtrFS snapshots for idiots

    I’ve also run automated snapshots on my btrfs partition, then run out of space doing multi-hop system upgrade on fedora (dnf has a plugin that creates a snapshot every time it kicks in.

    You can imagine there were many changes happenning per snapshot, and I effectively could have rolled back 4 major fedora versions… Til I ran out of space.

    I couldn’t get a replacement drive in time, and I had an hour to rebuild my laptop before needing to be on a customer site, so sadly I couldn’t preserve my drive for later investigation. My best guess is the high-water-mark was configured incorrectly, and somehow it was able to ‘write’ data past the extents of the filesystem.

    Rollback did work for my home partition, but I had to mount it from another OS to get it to work - so no data loss!

    By that time I’d already reinstalled the os to the root partition/subvolume however, so I couldn’t determine the exact cause of failure :(

    Moral: Snapshots are not backups, and ‘working’ is not ‘tested’