Snapper.
aka @rotopenguin@mastodon.social
Snapper.
The fact that snap has that much telemetry is another reason I stick to Flatpak.
The Steam Deck only does VRR over Displayport. Valve has their own engineers working on every part of the software stack. It’s their own hardware and their dock. With all that, Valve still can’t get VRR over HDMI to work.
Fuck the HDMI forum.
https://askubuntu.com/questions/1351909/lowering-mouse-debounce-time
What you’re looking for is called “debouncing”. I think the answer I’m linking here is wrong, the time is not tuneable in libinput. If you want to go through the ordeal of re-compiling libinput and shoving it in your system (without breaking it all?), it is
debounce_set_timer() and debounce_set_timer_short() in evdev-debounce.c. I think it’s the ms2us(25) call.
Yeah but what they do ain’t worth doing.
I think the screws are supposed to be “captive”, they unscrew from the bosses but still stay with the lid so you don’t lose em.
How many engineers can Canonical yeet now that they can skip on testing and backporting fixes to their own stable kernel?
Are they also going to tell Joe average user to just submit any bugs to LKML?
ExFAT is the LCD filesystem for flash sticks. FAT32 is the filesystem that you have to use for devices designed back when Microsoft was awful about Exfat licensing.
Everywhere else, Btrfs. If Oracle didn’t poison-pill ZFS licensing and it was common on Linux, I would be using that instead. Basically, taking it on faith that a drive didn’t fuck up your data is crazy. The most basic responsibility for a filesystem should be ensuring that “the files come out exactly the same as when they went in”.
By default, windows does “Fast Boot” which doesn’t make booting any faster, but does have the benefit of leaving the volume in a mounted state when you shut it down.
JNot sure if the flash is “gone”, the drive does still believe it has 256GB. I have seen drives die to where they completely forget their identity and are now “Phison controller with 32KB storage”. All they have left is either some absurd concept of falling back to using the controller’s on-die EEPROM, or they’re telling you they have the smallest possible CHS size that isn’t 0 just as a courtesy.
But yeah, the drive does look too mentally broken to continue.
You cut off the enumeration bit, but SMI01 USB DISK01 doesn’t look like any brand I recognize. Flash sticks are cheap and pretty amazing, but one thing they are not is “terribly reliable”. Better luck with the next stick, I mildly recommend making it a Samsung or Sandisk.
Also do “dmesg | grep -i firmware” to see what firmware loads the kernel squirted into the various device controllers.
If the distro just boots into a live session, you can get a pretty good idea there. They’re all working off of roughly the same kernel and driver and firmware sets, give or take some distros being a year out of date. The slower distros have something like “backports” or “enablement kernels” to still give you the option of pulling in newer stuff.
The graphics situation (compositor and mesa and kernel drivers and userland driver libraries) is more complicated. Especially with Nvidia. Your distro choice makes a much bigger impact there.
Ubuntu has its ups and downs when you’re actually living with it, but they have a fantastic installer experience. I have had my fair share of bizarre dead ends with other distro installers, like Bazzite telling me “you need -860GB more space”. Ubuntu puts you in a solid live-iso OS where the installer is just an app that you can drag to one side and run other tools before continuing. It tends to do sensible things if I go off the beaten path with a more advanced install.
Nowadays, I am happy with debootstrapping or btrfs send’ing an existing Debian install to set up a new system for myself. I still think that Ubuntu is reasonably likely to be a good experience for a newcomer.
When you change your nvidia driver version, you also need to do a “flatpak update” so that you have the matching nvidia library version.
Is “the bandwidth of a single nvme drive” actually a bottleneck for your application?
Look at “The Farmer Was Replaced”
Grab the Live Captions flatpak
The latest yt-dlp is in bookworm-backports.
I’ve had some suspend adventures too, but my experience is just on Intel laptops.
About a month ago, Debian Trixie had a regression that made my laptop wake up right after a suspend attempt. Afaict, it was not directly a kernel change, something in userland changed and triggered problems. This pm_async thing fixed it. Frankly, I don’t know why “async” power management is a thing anybody would want. Taking a whole extra millisecond to suspend in a more reliable way seems like a no-brainer.
echo 1 > /sys/power/pm_debug_messages # why would you ever want to not syslog it?? echo 0 > /sys/power/pm_async
Cat /sys/power/pm_wakeup_irq may tell you something about whomst is responsible for sleep failure. Anyways, suspend is the worst thing to diagnose good luck.