• 61 Posts
Joined 1 year ago
Cake day: July 1st, 2023


  • I actually have an old laptop with a GTX 780M and a Core i3 3rd Gen running Arch.

    When I tried GNOME on it with Fedora, it defaulted to X11 on login when it detected the Nvidia card. However, mine was also an Optimus laptop, and I could mostly always get Wayland working with the iGPU on the Intel. This is how I mostly ran for a year or two without ever using the dGPU.

    I need to chuck in a new SSD on that, but I could check it out let you know if anything’s changed in recent years. I don’t think wayland support for older nvidia cards have even been worked on in the last couple of years. There’s work for wayland on newer nvidia cards, but it’s mostly still spotty.

  • Yep I second this. I’ve been using GNOME, hyprland and sway interchangeably since 2021 Oct on my system as my main DEs. I recently wanted to give Plasma Wayland a try. Was met with multiple crashes, and freezes that required me to long press the power button to reboot to get it working again.

    While the new rootless wayland on SDDM worked fine for me, there are several things in Plasma that still don’t yet have support for Wayland. I could never get screen sharing to be reliable on Plasma Wayland, despite having the right portals installed.

    GNOME, Sway, and Hyprland are miles ahead in having a stable system on Wayland.

    • What is the Wi-Fi card you’re using? Some cards using a Realtek chipset have bad performance.
    • Check and see if the antenna is being obstructed by the case on S920, or if there’s anything metal nearby that could be causing interference.

    As to how you can go about debugging it, that part is hard. I’ve suffered from frequent disconnections on my OpenWRT install on a router, and I had to trawl through the system logs (it’s there on LuCI) to see what was triggering the disconnection when using the AP. After you find the line you think could be it, Google for it to see if anyone else has had similar issues. Ask on the OpenWRT forums since people on there might have come across it and have a solution.

    You should also check to see if a reconfig of a very basic AP triggers the issue.