u/lukmly013 💾 (lemmy.sdf.org)

I like computers, trains, space, radio-related everything and a bunch of other tech related stuff. User of GNU+Linux.
I am also dumb and worthless.
My laptop is ThinkPad L390y running Arch.
I own RTL-SDRv3 and RSP1 clone.

SDF Unix shell username: user224

  • 10 Posts
  • 71 Comments
Joined 3 years ago
cake
Cake day: June 17th, 2023

help-circle






  • Well, I haven’t yet tried actually using it.

    It seems supertuxkart can reliably freeze Plasma.
    After entering a game, the screen briefly freezes, then Plasma displays “Desktop effects were restarted due to a graphics reset” accompanied by following logs:

    [ 2346.824555] msm_dpu 1a01000.display-controller: [drm:hangcheck_handler [msm]] *ERROR* 5.0.6.0: hangcheck detected gpu lockup rb 2!
    [ 2346.825327] msm_dpu 1a01000.display-controller: [drm:hangcheck_handler [msm]] *ERROR* 5.0.6.0:     completed fence: 59486
    [ 2346.825920] msm_dpu 1a01000.display-controller: [drm:hangcheck_handler [msm]] *ERROR* 5.0.6.0:     submitted fence: 59494
    [ 2346.826698] msm_dpu 1a01000.display-controller: [drm:recover_worker [msm]] *ERROR* 5.0.6.0: hangcheck recover!
    [ 2346.827442] msm_dpu 1a01000.display-controller: [drm:recover_worker [msm]] *ERROR* 5.0.6.0: offending task: supertuxkart (/usr/bin/supertuxkart)
    

    The game will run, but Plasma remains frozen.
    The only fix is to SSH into the phone and restart plasmashell using systemctl restart --user plasma-plasmashell.

    Web browsing mostly works, though in this case, the phone only handles YouTube playback up to 480p.

    Oh, one more interesting observation: Cloudflare CAPTCHA causes Firefox to freeze with 100% CPU usage (single-core). So entering websites like lemmy.world is not possible.







  • Hey.
    So, it would seem I gave you a solution that’s still more complicated than it needs to be.
    You see, I was using Debian at the time I initially played with this, but now I am testing it on Arch. When you check the man pages, you’ll see an interesting option available on Arch.

    So…
    Waypipe on Debian 13 (latest) is version 0.9.2.
    Meanwhile on Arch we have 0.11.0.

    There’s an interesting new option, --xwls.

    Use xwayland-satellite to run X clients under Wayland; for server or ssh modes. This binds X display sockets for the next available display number and sets the DISPLAY environment variable for the program run under waypipe server. This option will only work if xwayland-satellite is installed and in PATH.

    Which means that on Debian you have to:

    1. Compile xwayland-satellite
    2. Add xwayland-satellite to directory in PATH
    3. Compile new version of waypipe from source
    4. Add it to directory in PATH, at least for server

    While on Arch you just pacman -Sy xwayland-satellite waypipe.

    Then it works with waypipe --xwls ssh user@IP program.
    It seems to have been added in 0.10.6.







  • please take a look and tell me what you think

    Sorry if it seems like I do, but I in fact do not have a brain.
    I just found this tool gets the job done, and that’s it.

    I typically just use it in a pretty stupid manual way.

    local$ waypipe -c zstd=6 ssh username@IP
    remote$ export DISPLAY=:90
    remote$ ./xwayland-satellite :90 &
    remote$ xfce4-panel
    

    Even the xfce4-panel discovery was an accident.
    I was using waypipe before knowing about xwayland-satellite. I wanted to run an X program, so in the same shell I typed vncserver to, well, launch a VNC server. That invoked xfce4-session, BUT since the WAYLAND_DISPLAY was set, XFCE DE attached to waypipe rather than XTigerVNC, launching a full remote desktop over my local one.
    And out of that, xfce4-panel proves pretty useful. I can easily launch other programs using GUI, and also see widgets on that panel.

    Here’s what I mean, if that sounds confusing:

    Plasma panel (bottom) is local, XFCE panel (top and middle bottom) are remote.
    Right, and you’re probably wondering why that app launcher at the top looks shattered. Well, both can’t be opened at once. If the application launcher goes out of focus, it closes.
    But also, I use the shatter effect in KDE Plasma, so it doesn’t go away immediately. This is just as close as I could get with screenshot timing.




  • Problem with plain Wireguard is if you can’t open ports on some devices to get a direct connection. It should be just fine with hub and spoke model, but NAT Traversal of Tailscale makes a huge difference. I can get a direct connection between 2 devices connected to mobile data and behind CG-NAT.
    And also the config management if you have too many devices.

    Hub and spoke, you just add new devices to Wireguard on the main device, and the new peer. Full mesh, oof.

    But as far as configuring Wireguard goes, that’s pretty simple. And then there’s the weird stuff with MTU and fragmentation… but that’s not something Wireguard-specific.