Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
  • in reply to: Verify GPU encoding used? #32238

    It is:

    apt search libva-drm2
    Sorting… Done
    Full Text Search… Done
    libva-drm2/groovy,now 2.8.0-1 amd64 [installed,automatic]
    Video Acceleration (VA) API for Linux — DRM runtime

    in reply to: Verify GPU encoding used? #32222


    The server host is an Intel gen5 (Broadwell) processor, using the integrated graphics.

    00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics [8086:1606] (rev 09) (prog-if 00 [VGA controller])
    DeviceName: VGA compatible controller
    Subsystem: Intel Corporation HD Graphics [8086:1606]
    libva info: VA-API version 1.8.0
    libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/
    libva info: Found init function __vaDriverInit_1_8
    libva info: va_openDriver() returns 0
    vainfo: VA-API version: 1.8 (libva 2.8.0)
    vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics – 20.2.0 ()

    Session attached.

    in reply to: Verify GPU encoding used? #32201

    About /usr/NX/var/log/node folder please check on the server side.

    I finally found the session logs, per

    As of version 7.0.208: The display agent log files should be stored in the correspondent session directory created under the home directory of the session owner, e.g. the user’s home/.nx/node/C-display-sessionid directory. Which is where my session logs are.

    The session log is verifying (in addition to the client information) that I am getting only the software encoder, though I still have no indication why.

    Thank you

    in reply to: Verify GPU encoding used? #32126

    “/usr/NX/var/log/node folder please check on the server side.”
    The server doesn’t have it.

    jason@CB5:/usr/NX/var/log$ du -a .
    4 ./logrotate
    4 ./archives
    40 ./nxupdate.log
    12 ./nxd.log
    44 ./nxinstall.log
    28 ./nxerror.log
    16 ./nxserver.log
    152 .

    I did upgrade my client and I can see the string now, and it is indicating that I’m not getting h.264 acceleration, so I’ll have to figure out why that is.

    in reply to: Verify GPU encoding used? #32108

    That’s actually what I was referring to when I found old posts mentioning a way to check. Maybe I don’t have the logging enabled for that, but I don’t have a node subdirectory in /usr/NX/var/log. Since the posts were a few years old, I started thinking that the log information was moved elsewhere, but none of the files in the log directory has anything like that. On my install, the only subdirs off that are “archives” and “logrotate”.

    I did find that post you linked as well. So, one thing about that particular item, it doesn’t say where in the UI that information is located. My server version is 7.1.3 but I’ve just noticed that I think my client is rather outdated (it was kind of tricky to find something that showed the client version, at least on Windows). If my older client (I think it’s 6.4.6) is able to display the string properly, than I am on all software, which I’ll have to figure out. I’ll update my client and see if that changes what I’m seeing in the connection information. I’m assuming I’m looking in the right place (Display Settings on the client; it’s the only place that has a string that looks like the information mentioned in the KB article).


    in reply to: Disable hardware acceleration on the client side? #23812

    Ah, thanks! I was looking for settings prior to establishing the connection.


    in reply to: Client – set to snap to size vs resize desktop #21951


    I didn’t realize the button was a function toggle, I thought it was going to cause my remote to resize to my desktop.’

    I’m not sure what triggers it, I didn’t mean to imply I think the unlock triggers it.  I just notice that it only seems to happen after my screen has locked (although, I don’t think it happens every time).


Viewing 7 posts - 1 through 7 (of 7 total)