Ilgaz

[Ilgaz]

That setting fixes the crash (coredump) however I get hit by a familiar-looking glitch making the session impossible to interact with. It looks almost exactly the same as the video glitches I saw with Firefox/Wayland. I believe it got fixed with better multithreading on Nouveau, I am actively using video acceleration with Firefox.  https://bugzilla.mozilla.org/show_bug.cgi?id=1658772 . I will inform Nouveau developers about it. Anyway thank you for caring.

Attachments:

1. 

   casaba-Ubuntu-22.04.2-LTS-2023-04-30-16.58.11.png
   

[Ilgaz]

Hello,  thanks again for caring.

When I issue the command with the lib64 path under openSUSE Tumbleweed:

nouveau /dev/dri/card0
nouveau /dev/dri/renderD128
r600 /dev/dri/card0
r600 /dev/dri/renderD128
radeonsi /dev/dri/card0
radeonsi /dev/dri/renderD128
virtio_gpu /dev/dri/card0
virtio_gpu /dev/dri/renderD128

So I added the line (I run nouveau/nvidia)

LIBVA_DRIVER_NAME=nouveau

When I launch the nxplayer.bin and attempt to connect a host it core dumps. I attached the dump file. There are some errors with libva reported in session (log) I am attaching it too.

Attachments:

1. nxplayercoredump.txt
2. session.zip

[Ilgaz]

Hello

Here is the output of the commands

vainfo --display drm
Trying display: drm
libva info: VA-API version 1.18.0
libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_1_18
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.18 (libva 2.18.1)
vainfo: Driver version: Mesa Gallium driver 23.0.2 for NVAC
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple            : VAEntrypointVLD
VAProfileMPEG2Main              : VAEntrypointVLD
VAProfileVC1Simple              : VAEntrypointVLD
VAProfileVC1Main                : VAEntrypointVLD
VAProfileVC1Advanced            : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264Main               : VAEntrypointVLD
VAProfileH264High               : VAEntrypointVLD
VAProfileNone                   : VAEntrypointVideoProc

for DRVNAME in $(find /usr/lib -name “*drv_video.so” -exec basename {} \; | sed ‘s/_drv_video.so//
’); do for DEVICE in /dev/dri/* ; do LIBVA_DRIVER_NAME=$DRVNAME vainfo –display drm –device $DEVICE 1>/dev/null
2>/dev/null ; [ $? -eq 0 ] && echo “$DRVNAME $DEVICE” ; done ; done 2>/dev/null | grep -v dummy

Unfortunately, no output has been shown as a result of that command.

[Ilgaz]

Hello

Thank you for caring. It was indeed a hardware decoding issue, when I disabled it via editing the configuration file it no longer crashes.

[Ilgaz]

Hello. Thanks for caring.

I am currently on Linux Mint 20.3 which is based on Ubuntu 20.04 LTS with 5.4 series kernel. I have nvidia official 340 series driver (not nouveau) installed and ‘vainfo’ command outputs this. Log attached.

ilgaz@ilgaz-MacBook:~$ vainfo
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_1_0
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.6.0)
vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API – 0.7.4
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple            :    VAEntrypointVLD
VAProfileMPEG2Main              :    VAEntrypointVLD
VAProfileH264Main               :    VAEntrypointVLD
VAProfileH264High               :    VAEntrypointVLD
VAProfileVC1Simple              :    VAEntrypointVLD
VAProfileVC1Main                :    VAEntrypointVLD
VAProfileVC1Advanced            :    VAEntrypointVLD
ilgaz@ilgaz-MacBook:~$ inxi -G
Graphics:
Device-1: NVIDIA C79 [GeForce 9400M] driver: nvidia v: 340.108
Display: x11 server: X.Org 1.20.13 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 1280×800~60Hz
OpenGL: renderer: GeForce 9400M/integrated/SSE2 v: 3.3.0 NVIDIA 340.108

Attachments:

1. hp_ip-2023-02-24-07.10.19.tar.gz

[Ilgaz]

I have a way more older/less capable nvidia 9400 here running both openSUSE Tumbleweed (modern, latest kernel, rolling) nouveau driver and Mint (Ubuntu 20.04 based, LTS) with nvidia 340 closed source driver.

Both have vaapi enabled. Following is from openSUSE Tumbleweed. NoMachine refuses to use hardware decoding. This is a particularly big issue on a low spec/old machine like this.

vainfo
Trying display: wayland
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.17 (libva 2.17.1)
vainfo: Driver version: Mesa Gallium driver 22.3.5 for NVAC
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple            : VAEntrypointVLD
VAProfileMPEG2Main              : VAEntrypointVLD
VAProfileVC1Simple              : VAEntrypointVLD
VAProfileVC1Main                : VAEntrypointVLD
VAProfileVC1Advanced            : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264Main               : VAEntrypointVLD
VAProfileH264High               : VAEntrypointVLD
VAProfileNone                   : VAEntrypointVideoProc

inxi -G
Graphics:
Device-1: NVIDIA C79 [GeForce 9400M] driver: nouveau v: kernel
Device-2: Apple Built-in iSight type: USB driver: uvcvideo
Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.8
compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: nouveau gpu: nouveau resolution: 1280x800
API: OpenGL v: 3.3 Mesa 22.3.5 renderer: NVAC

[Ilgaz]

I have sent the logs as instructed to the e-mail address.

[Ilgaz]

Reported the issue to Mozilla/Firefox at https://bugzilla.mozilla.org/show_bug.cgi?id=1802834 and Webcompat at https://webcompat.com/issues/114776

[Ilgaz]

ilgaz@hp:/mnt/c/Users/ilgaz/Downloads> sha256sum nomachine_8.2.3_4_x64.exe
c75b8d8b92e76c20bd28ec038bf371bfc1866c0733aac2e2edb921bfb104f834  nomachine_8.2.3_4_x64.exe
ilgaz@hp:/mnt/c/Users/ilgaz/Downloads> sha256sum “nomachine_8.2.3_4_x64 (1).exe”
c75b8d8b92e76c20bd28ec038bf371bfc1866c0733aac2e2edb921bfb104f834  nomachine_8.2.3_4_x64 (1).exe

Files are exactly the same. Wonder if it is related to how browsers “execute” files? I will report it to Firefox/Mozilla

Attachments:

1. 

   nomachineerror.png
   

2. 

   nomachineerror2.png
   

3. 

   nomachineerror3.png
   

[Author]

Posts