Forum Replies Created
-
AuthorPosts
-
gerard
ParticipantMake sure you don’t have a software firewall enabled.
That will 100% block connections to the server!
gerard
ParticipantI have similar setup but I do manage to login with Wayland but its just a blank/black screen, then NoMachine crashes.
Works fine in X11. Not sure if related to this or not.
gerard
ParticipantUsing NoMachine v8.11.3-1 which is on the AUR and works. I have also tried the git version but there is no difference in the behavior in these cases.
.+=========================. ——————————-
:++===++==================- :++- OS: CachyOS Linux x86_64
:*++====+++++=============- .==: Host: AB350N-Gaming WIFI
-*+++=====+***++==========: Kernel: 6.8.1-4-cachyos
:++++=====-==: -*****+ Display (DELL S2330MX): 1920×1080 @ 60Hz
:++========-=. .=+**+. DE: KDE Plasma 6.0.2
.+==========-. . WM: KWin (X11)
:=====+++==========++++++++++++++*- CPU: AMD Ryzen 5 3600 (12) @ 4.21 GHz
.====++==============++++++++++*- GPU: Intel Arc A380
Locale: en_GB.UTF-8gerard
ParticipantStarting to believe that NoMachine has not realized that the OneVPL is now the replacement to MediaSDK.
This is only reason I can think of why NoMachine can’t use hw encoding at present.
But for sake of argument I did install the old mediasdk files according to guides provided and it did not resolve them problem for me. No HW encoding for Intel Arc380 under ARCH.
I wonder if it works under other Linux distributions that aren’t running a OLD kernel setup.
gerard
ParticipantI noticed in this session log file it has some audio errors. (yes my quicksync is also busted for some reason)
Attachments:
gerard
ParticipantMAN files excluded.
Pipewire-pulse package files:
/usr/bin/pipewire-pulse /usr/lib/pipewire-0.3/libpipewire-module-protocol-pulse.so /usr/lib/pipewire-0.3/libpipewire-module-pulse-tunnel.so /usr/lib/systemd/user/pipewire-pulse.service /usr/lib/systemd/user/pipewire-pulse.socket /usr/share/pipewire/media-session.d/with-pulseaudio /usr/share/pipewire/pipewire-pulse.conf
Pipewire package files:/usr/bin/pipewire /usr/bin/pw-cli /usr/bin/pw-config /usr/bin/pw-dot /usr/bin/pw-dump /usr/bin/pw-link /usr/bin/pw-metadata /usr/bin/pw-mon /usr/bin/pw-profiler /usr/bin/pw-reserve /usr/bin/pw-top /usr/bin/spa-inspect /usr/bin/spa-json-dump /usr/bin/spa-monitor /usr/lib/pipewire-0.3/libpipewire-module-access.so /usr/lib/pipewire-0.3/libpipewire-module-adapter.so /usr/lib/pipewire-0.3/libpipewire-module-client-device.so /usr/lib/pipewire-0.3/libpipewire-module-client-node.so /usr/lib/pipewire-0.3/libpipewire-module-combine-stream.so /usr/lib/pipewire-0.3/libpipewire-module-link-factory.so /usr/lib/pipewire-0.3/libpipewire-module-metadata.so /usr/lib/pipewire-0.3/libpipewire-module-portal.so /usr/lib/pipewire-0.3/libpipewire-module-profiler.so /usr/lib/pipewire-0.3/libpipewire-module-protocol-native.so /usr/lib/pipewire-0.3/libpipewire-module-rt.so /usr/lib/pipewire-0.3/libpipewire-module-rtkit.so /usr/lib/pipewire-0.3/libpipewire-module-session-manager.so /usr/lib/pipewire-0.3/libpipewire-module-spa-device-factory.so /usr/lib/pipewire-0.3/libpipewire-module-spa-device.so /usr/lib/pipewire-0.3/libpipewire-module-spa-node-factory.so /usr/lib/pipewire-0.3/libpipewire-module-spa-node.so /usr/lib/spa-0.2/control/libspa-control.so /usr/lib/spa-0.2/libcamera/libspa-libcamera.so /usr/lib/spa-0.2/support/libspa-dbus.so /usr/lib/spa-0.2/support/libspa-journal.so /usr/lib/spa-0.2/support/libspa-support.so /usr/lib/spa-0.2/v4l2/libspa-v4l2.so /usr/lib/spa-0.2/videoconvert/libspa-videoconvert.so /usr/lib/spa-0.2/videotestsrc/libspa-videotestsrc.so /usr/lib/systemd/user/pipewire.service /usr/lib/systemd/user/pipewire.socket /usr/share/pipewire/client-rt.conf /usr/share/pipewire/client-rt.conf.avail/20-upmix.conf /usr/share/pipewire/client.conf /usr/share/pipewire/client.conf.avail/20-upmix.conf /usr/share/pipewire/minimal.conf /usr/share/pipewire/pipewire-pulse.conf.avail/20-upmix.conf /usr/share/pipewire/pipewire.conf /usr/share/pipewire/pipewire.conf.avail/10-rates.conf /usr/share/pipewire/pipewire.conf.avail/20-upmix.conf
There are a number of other pipewire related packages as you can see in the arch repo website search system. But I think these two are the ones of most importance.
gerard
ParticipantIn saying all that there is some funky stuff going on with pulse on this server for some reason.
Odd however how all other desktop sharing apps have no problem with all this.
Attachments:
gerard
Participant#47352
neither of these locations exist under Arch for pulse native or pipewire-0
gerard
Participant#47351
Yes processes owned by user.
printenv shows XDG_RUNTIME_DIR=/run/user/1000
WHILE
cat /proc/1559/environ (there are 3 pids) shows this
PWD=/usr/NX/etcNX_FEATURES=underverse-server,GigabyteTechnologyCo.Ltd.AB350N-GamingWIFI,Linux,CachyOS,6.7.9,x86_64,AMD Ryzen 5 3600 6-Core Processor ,12,33574191104,316PERL5LIB=/usr/NX/lib:/usr/NX/lib/perl:/usr/NX/lib/perl/include:/usr/NX/lib/perl/nxnode:/usr/NX/lib/perl/libperlNX_SYSTEM=/usr/NXPERL5INCLUDE=/usr/NX/lib/perl/nxnodeNX_VERSION=8.11.3SHLVL=0LD_LIBRARY_PATH=/usr/NX/lib:/usr/NX/lib/perl:/usr/NX/lib/perl/include:/usr/NX/lib/perl/nxnode:/usr/NX/lib/perl/libperlPATH=/usr/NX/lib:/usr/NX/lib/perl:/usr/NX/lib/perl/include:/usr/NX/lib/perl/nxnode:/usr/local/sbin:/usr/local/bin:/usr/binDBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/busUSER_PAM_ENV_KEYS=
gerard
ParticipantI will check and do these things you suggest.
gerard
ParticipantDone
gerard
ParticipantOk here is a log dumb. Followed instructions, no audio still. Tried to change audio device to a few other things, nothing.
March 10, 2024 at 21:20 in reply to: No sound forwarding (option to change settings is greyed out) #47315gerard
ParticipantThis might be what my problem is also. No sound on CachyOS with 8.11.3
-
AuthorPosts