• 50 Posts
  • 237 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

help-circle



  • Gadget bridge doesn’t really work for any “new” (i might be wrong here) devices.

    Most newer Garmin devices should work since 0.82 (and earlier with nightly). It’s not feature complete compared to using Gadget Connect but should be enough for most use cases, unless you really care about the social/awards aspect and some of the deeper metrics (although if you’re handy with SQL you can handle that yourself).

    Not being able to set an event date and have “daily suggested workouts” follow that is my only annoyance, although I’ve been happy just using the defaults for now.








  • Linux currently doesn’t have a concept of “exclusive fullscreen” in the way that Windows does. A new wayland protocol can probably resolve this, although I’m not sure if any work has been done for that yet.

    You could do it manually though most likely by having a script check if the current window is fullscreen (which you can do with sway/wlroots easily at least) and then apply the change. But there would be some false positives where you might not want the behaviour (like a video player), although if you’re watching high resolution/high framerate content it would be useful.


  • It depends on the GPU I suspect. The 6XXX series doesn’t appear to have that issue, at least not in a significant way. But yeah, the 7XXX series having power consumption issues isn’t too surprising.

    As for the quote, the “more aggressive ramping” is about its behaviour under load, which you probably do want if you’re playing games.

    You can revert the change in the same way as you can make the change now, with a udev rule. And you can change it on the fly with a script if needed.

    Udev rule:

    KERNEL=="card0", SUBSYSTEM=="drm", DRIVERS=="amdgpu", ATTR{device/power_dpm_force_performance_level}="manual", ATTR{device/pp_power_profile_mode}="0"
    

    (you might be able to leave the power_dpm_force_performance_level part unset)

    You can also try the compute (5) or VR (4) modes which have slightly different behaviour (I use the compute mode on my systems even though they are mostly for gaming).

    I believe some of the third party GPU control utilities can also do this, but I don’t personally use them.








  • however the issue I run into is if I lose internet access at home, none of my services are able to function as they can no longer reach the management interface.

    Do the services stop working immediately, or only after restarting the netbird client(s)? I’ve found headscale/tailscale nodes will continue to communicate with each other with the internet down, but restarting the tailscale client will break things (which makes sense of course).

    If netbird has an equivalent to MagicDNS that could cause issues after a while of losing connectivity (since the DNS will be hosted on the VPS).