Qualified success on openSUSE Tumbleweed, Nvidia 1650

[digitaltrails]

I got yserver to build for openSUSE Tumbleweed by using their openSUSE Build Server (OBS).
The build result, and the RPM spec file are at https://build.opensuse.org/package/show/home:mchnz/yserverec.

Note this is an unvetted personal build, so you can only trust it as far as you trust me. The spec file could be used by others to do a more trustworthy build of their own.

The OBS might be useful if you ever need to produce yserver binaries or packages for various distros (I've previously used it to to openSUSE, Arch, and Fedora).

I installed the resulting RPM on the following machine:

Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME B550M-A WIFI II v: Rev X.0x serial: <superuser required>
CPU:
  Info: 6-core model: AMD Ryzen 5 5600 bits: 64 type: MT MCP cache: L2: 3 MiB
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1650 SUPER] driver: nvidia v: 580.159.03
  Display: unspecified server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.12 driver: X:
    loaded: nvidia unloaded: modesetting,vesa gpu: nv_platform,nvidia,nvidia-nvswitch tty: 180x46
    resolution: 1920x1080
  API: EGL v: 1.5 drivers: nvidia,swrast platforms: gbm,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: mesa v: 26.1.4 note: console (EGL sourced)
    renderer: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2, llvmpipe (LLVM 22.1.7 256 bits)
  API: Vulkan v: 1.4.350 drivers: nvidia,llvmpipe surfaces: N/A

I also briefly ran it on another similar machine, but with an RTX 3060 with the nvidia 610.43 driver - which went fine, but I pretty much immediately shifted over to a spare machine.

Having only installed the rpm from my OBS build I didn't have just. Based on what's in the justfile I created a yserver-xterm script containing the following:

#!/bin/bash
RUST_LOG="{{log}}" RUST_BACKTRACE=1 yserver 7 > yserver-hw-xfce.log 2>&1 & 
yserver_pid=$!;
sleep 2;
DISPLAY=:7 xterm
kill -TERM $yserver_pid 2>/dev/null
wait $yserver_pid 2>/dev/null

That ran just fine. I then created a yserver-xfce script:

#!/bin/bash
RUST_LOG="{{log}}" RUST_BACKTRACE=1 yserver 7 > yserver-hw-xfce.log 2>&1 & 
yserver_pid=$!;
sleep 2;
DISPLAY=:7 xfce4-session
kill -TERM $yserver_pid 2>/dev/null
wait $yserver_pid 2>/dev/null

Which also runs fine. I tried a pyqt app, google-chrome, vlc, digikam, and a few other apps. All behaved well.

I noticed google-chrome isn't using the GPU, so no 3d map view.

I installed chromium-bsu native to Linux (very nice arcade style game). It starts, the enemies cascade down the screen and fire correctly, but the player's ship doesn't position or respond to the mouse properly - it's unplayable. Maybe because it's using a bunch of GL libraries along with libSDL2.

Scrolling in xfce-terminal seems a bit jerky - when using the mouse to drag the slider, mousewheel seems OK.

Trying to start kde failed:

#!/bin/bash
RUST_LOG="{{log}}" RUST_BACKTRACE=1 yserver 7 > yserver-hw-xfce.log 2>&1 & 
yserver_pid=$!;
sleep 2;
export DISPLAY=:7
startplasma-x11
kill -TERM $yserver_pid 2>/dev/null
wait $yserver_pid 2>/dev/null

I assume that's because of it using compositing and GPU (and my Nvidia GPU?).

I haven't used yserver for very long. I haven't noticed any other glitches or issues so far. I'm just kicking the tires at the moment, I have no specific plans in mind.

Anyway, I'm very impressed. Thank you for all you time and effort you've put into this.

[digitaltrails]

I found KDE Plasma-6.7 can run if if I disable the compositor:

#!/bin/bash
RUST_LOG="{{log}}" RUST_BACKTRACE=1 yserver 7 > yserver-hw-kde.log 2>&1 & 
yserver_pid=$!;
sleep 2;

export KWIN_COMPOSE=N
DISPLAY=:7 startplasma-x11

kill -TERM $yserver_pid 2>/dev/null
wait $yserver_pid 2>/dev/null

I also see System Settings>Display and Monitror>Compositor>Eable at startup set to off (probably due to export KWIN_COMPOSE=N). Perhaps setting it off in settings is just as good - but that's a chicken and egg situation (if only using yserver).

I've never seen the Plasma desktop start this fast, the little cog was really spinning. The experience is possibly more snappy or as snappy as wayland.

I've tried only a few applications. Konsole of course. Digikam works fine. Google chrome works fine, scrolling is fast with no glitches. I played a video with vlc, looked fine, no tearing.

Window resizing is flickery.

I had to set System Settings > Window Decorations > Normal Window Borders to get window borders.

I don't know whether it's just me, but xwaylandvideobridge keep staring up maximised, so I disabled it:

echo "Hidden=true" >> ~/.config/autostart/org.kde.xwaylandvideobridge.desktop

Had to kill plasmashell to get it restarted on the most recent session. Past sessions seemed fine, so it's not been a common occurrence.

If the screen locks, I cannot unlock it, I had to ssh in and loginctl unlock-session. But after a suspend, it seems the unlock screen works. Nothing interesting logged to the journal. [Edit: may have been because sddm was also running, after stopping it I seem to able to unlock normally.]

Looking forward, I wonder if there might be some synergy with sonic-win.

Here's a screenshot of where I've gotten to today:

[joske]

Thanks for testing! I'll go over all your findings, but first: which commit did you build? Just yesterday I fixed a bunch of XI issues that may impact your chrome game.

[joske]

Indeed, 3D view not available in chrome, but it IS in FF, strange. Will investigate that.

[joske]

Well, I was able to get webGL going in chrome/chromium, but the 3D button doesn't show up, and it doesn't either on Xorg. So not sure what I could do. Please test 139e8a3

[digitaltrails]

Pull from master. No change to maps. Did note:

glx: failed to create dri3 screen
failed to load driver: nvidia-drm
Xlib:  extension "XFree86-VidModeExtension" missing on display ":7".
[13536:13536:0717/082153.928964:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Error) eglGetMscRateANGLE: glXGetMscRateOML failed.  

Also, I'm not sure if it was like this before, but when I open the three-dot menu to access settings, it first appears black and then draws properly when the mouse is moved into the menu. Same for sub menus. If I turn off Settings>SYstem>Use graphics acceleration then the menus draw normally. When the a menu is opened, or the mouse is moved within it, lots of the above error message occur.

Opening the main settings menu:

Opening a sub-menu of the main-menu:

[joske]

the error about the missing extension is normal and harmless, I get that too. The black bits is also present on steam now (also uses chrome engine). I'm investigating that as we speak. This is a regression from now suddenly falling into the GPU path on chrome

[joske]

chromium-bsu fixed in 8b62c93

good catch, ALL apps that want relative raw events would break.

[digitaltrails]

Thanks, works fine now.

[joske]

Can not reproduce the xfce-terminal scroll issue. How big is your scrollback buffer?

Update: tested with unlimited, and still buttery for me.

[digitaltrails]

1000 (the default). Seems smoother now I've running it in Plasma desktop, but dragging the slider seems a bit laggy at times. Back in xfce it seems more laggy. The amount of text to scroll doesn't seem to make a difference. Very smooth in a normal Plasma-X11 login. Maybe its just a symptom of me using nvidia when I shouldn't.

[digitaltrails]

I forced google-chrome to use Vulkan (chrome://flags - search for Vulkan).

• Settings menus OK now.
• Maps still can't do 3D - some errors written out:

I got the same errors about loading dri3 and nvidia-drm, but also these:

[17922:17951:0717/084819.929128:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
[17922:17994:0717/084822.566685:ERROR:content/browser/browser_main_loop.cc:278] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
[17922:17992:0717/084822.566682:ERROR:content/browser/browser_main_loop.cc:278] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
[17922:17993:0717/084822.566682:ERROR:content/browser/browser_main_loop.cc:278] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed

I tried some of the other vulkan related flags, they didn't seem to do anything to help.

I then tried chrome with a different 3D web app - sweethome3d: https://www.sweethome3d.com/SweetHome3DJSOnline.jsp - sweethome3d seems to work just fine.

The Java offline version of Sweethome3d also tries to use the nvidia driver. I had no luck with that. I did try using zink (__GLX_VENDOR_LIBRARY_NAME=mesa MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink "$@"), which stopped the nvidia-drm loading errors, and the app loaded, but the interface was blank. Zink did seem to stop chrome complaining about nvidia-dri, but on luck on maps.

Anyway, all very interesting. I'm impressed that yserver isn't crashing due to all these weird things I've been throwing at it.

[joske]

Xorg can't do 3D on chrome on my system, so this seems a chrome issue, not yserver. webGL/acceleration works now (but bugs remain).

[joske]

The webGL commit was reverted as it regresses steam menu rendering. Hope to be able to re-enable once that is resolved.