bobnx

Forum Replies Created

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • in reply to: Very slow with Xubuntu 20.04 #33338
    Avatarbobnx
    Participant

    Update :

    Xubuntu/Ubuntu pushed some updates to 20.04 this weekend.  One of the updates I noticed involved Lightdm.  So I did a check and there was still a problem.  But I thought let us be thorough, so I uninstalled the Nvidia driver and re-installed the default OpenSource drive.

    It works!

    I just did a reboot to confirm and yes it still works.

    I suppose I should re-check with the Nvidia driver and will do it when I have time.

    It should be noted I did check with replacing the Nvidia driver previously, and it did not work.  So the Ubuntu changes to Lightdm must also be required.

    in reply to: Very slow with Xubuntu 20.04 #33317
    Avatarbobnx
    Participant

    As I have said, I have tried 2 different video drivers – the default open source driver and the Nvidia propriety driver with the same results.

    It was working with Xubuntu 18.04 and to the best of my recollection it was with the latest NX (perhaps a few “point” versions old).  I.e. the same “generic” version of NX on 18.04 and 20.04

     

     

    in reply to: Very slow with Xubuntu 20.04 #33297
    Avatarbobnx
    Participant

    Hi @commandline, sorry about Potex reference.  A bit of a senior moment I am afraid.  I have an issue on the ZK forum and was on there just before I posted here.  ZK is something from Potrex.  My brain got confused as to who owns/develops NX. (:-)

    What I was really trying to say is – I hope NoMachine/NX are still looking at the problem.  It is annoying that stock Xubuntu does not work and I have to kill Lightdm.  Some of the comments seem to imply it is a Xubuntu/Lightdm problem and we have to live with it.

    I don’t think is acceptable to blame xubuntu/lightdm – NX always worked previously and VNC works.

    in reply to: Very slow with Xubuntu 20.04 #33276
    Avatarbobnx
    Participant

    In answer to post of May 5, 2021, as mentioned in post of 26th April, I have tried both the Nvidia and the Open Source drivers with no change in behavior.

    Hopefully, Potex are still investigating this problem?

    FYI using VNC works without problems (except of course the general VNC problems). But would much prefer to use NX.

    in reply to: Very slow with Xubuntu 20.04 #33148
    Avatarbobnx
    Participant

    Yes, using:

    sudo systemctl stop lightdm
    sudo /etc/NX/nxserver --restart

    Then when I connect, the client screen is very responsive.

    I hope that this is helpful to you?

     

    in reply to: Very slow with Xubuntu 20.04 #33131
    Avatarbobnx
    Participant

    Another clue –

    If I run glxgears on the client and then open a terminal, the performance is fine i.e. if I type “a”, it appears straight away.

    in reply to: Very slow with Xubuntu 20.04 #33119
    Avatarbobnx
    Participant

    Another clue!

    There is a KVM Xubuntu 20/04 virtual machine running under the “slow NX” machine.

    So effectively both the main server and the virtual machine are both Xubuntu 20.04 (with latest updates) and NX 7.4.1

    Server is slow.

    Virtual machine is perfect.

    A bit of info – server was an upgrade from 18.04 (also had NX server).  Virtual machine was a fresh install.

     

    in reply to: Very slow with Xubuntu 20.04 #33087
    Avatarbobnx
    Participant

    Perhaps a clue or maybe a red herring –

    Both desktops have 2 network cards.  The second cards in each desktop are connected via a crossover cable.  However (in theory) all network traffic should go via the first network cards.  Only DRBD traffic goes over the crossover.

    I use the term “desktops” liberally.  I really think of them as servers but with a GUI.  That is they use Xubuntu desktop software and have physical displays attached.  Each “server” runs a number of KVM virtual machines.

    Bad server :

    br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 192.168.0.200  netmask 255.255.255.0  broadcast 192.168.0.255
    inet6 fe80::30da:806f:e448:d89b  prefixlen 64  scopeid 0x20<link>
    ether 00:1d:7d:d5:1d:03  txqueuelen 1000  (Ethernet)
    RX packets 103571  bytes 72608255 (72.6 MB)
    RX errors 0  dropped 14268  overruns 0  frame 0
    TX packets 85227  bytes 20241875 (20.2 MB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 10.0.0.200  netmask 255.255.255.254  broadcast 10.0.0.255
    inet6 fe80::1ad6:c7ff:fe06:b0a6  prefixlen 64  scopeid 0x20<link>
    ether 18:d6:c7:06:b0:a6  txqueuelen 1000  (Ethernet)
    RX packets 6692  bytes 547764 (547.7 KB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 6750  bytes 414873 (414.8 KB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    ether 00:1d:7d:d5:1d:03  txqueuelen 1000  (Ethernet)
    RX packets 121528  bytes 77840793 (77.8 MB)
    RX errors 0  dropped 476  overruns 0  frame 0
    TX packets 92360  bytes 20614249 (20.6 MB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
    inet 127.0.0.1  netmask 255.0.0.0
    inet6 ::1  prefixlen 128  scopeid 0x10<host>
    loop  txqueuelen 1000  (Local Loopback)
    RX packets 1930  bytes 143736 (143.7 KB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 1930  bytes 143736 (143.7 KB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
    inet 192.168.100.1  netmask 255.255.255.0  broadcast 192.168.100.255
    ether 52:54:00:5f:52:d0  txqueuelen 1000  (Ethernet)
    RX packets 0  bytes 0 (0.0 B)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 0  bytes 0 (0.0 B)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    Good Server :

    br1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 192.168.0.201  netmask 255.255.255.0  broadcast 192.168.0.255
    inet6 fe80::6ef0:49ff:fe14:81c3  prefixlen 64  scopeid 0x20<link>
    ether 6c:f0:49:14:81:c3  txqueuelen 1000  (Ethernet)
    RX packets 726796  bytes 257686600 (257.6 MB)
    RX errors 0  dropped 193314  overruns 0  frame 0
    TX packets 655460  bytes 139205557 (139.2 MB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 10.0.0.201  netmask 255.255.255.0  broadcast 10.0.0.255
    inet6 fe80::1ad6:c7ff:fe06:b0d6  prefixlen 64  scopeid 0x20<link>
    ether 18:d6:c7:06:b0:d6  txqueuelen 1000  (Ethernet)
    RX packets 4611352  bytes 6260495476 (6.2 GB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 2044631  bytes 187886200 (187.8 MB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    ether 6c:f0:49:14:81:c3  txqueuelen 1000  (Ethernet)
    RX packets 13344889  bytes 17710341246 (17.7 GB)
    RX errors 0  dropped 6409  overruns 0  frame 0
    TX packets 2581827  bytes 341784717 (341.7 MB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
    inet 127.0.0.1  netmask 255.0.0.0
    inet6 ::1  prefixlen 128  scopeid 0x10<host>
    loop  txqueuelen 1000  (Local Loopback)
    RX packets 15789  bytes 1183514 (1.1 MB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 15789  bytes 1183514 (1.1 MB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
    inet 192.168.123.1  netmask 255.255.255.0  broadcast 192.168.123.255
    inet6 fe80::c024:d7ff:fe3e:30b9  prefixlen 64  scopeid 0x20<link>
    ether c2:24:d7:3e:30:b9  txqueuelen 1000  (Ethernet)
    RX packets 0  bytes 0 (0.0 B)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 9  bytes 642 (642.0 B)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    virbr1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
    inet 192.168.100.1  netmask 255.255.255.0  broadcast 192.168.100.255
    ether 52:54:00:c7:7c:fe  txqueuelen 1000  (Ethernet)
    RX packets 0  bytes 0 (0.0 B)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 0  bytes 0 (0.0 B)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet6 fe80::fc54:ff:febf:aa61  prefixlen 64  scopeid 0x20<link>
    ether fe:54:00:bf:aa:61  txqueuelen 1000  (Ethernet)
    RX packets 1751478  bytes 185570661 (185.5 MB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 11585242  bytes 17530475362 (17.5 GB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet6 fe80::fc54:ff:fed3:86ec  prefixlen 64  scopeid 0x20<link>
    ether fe:54:00:d3:86:ec  txqueuelen 1000  (Ethernet)
    RX packets 219007  bytes 340890947 (340.8 MB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 680119  bytes 180866367 (180.8 MB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    in reply to: Very slow with Xubuntu 20.04 #33080
    Avatarbobnx
    Participant

    1gb LAN connection.
    Both Desktops same LAN.
    Both 8gb memory
    Usable desktop Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz
    Unusable desktop Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz

    One difference is slow desktop has:
    VGA compatible controller: NVIDIA Corporation G86 [GeForce 8500 GT] (rev a1

    Fast desktop has:
    Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)

    I have tried with both the NVIDIA driver and native Linux driver with no difference.

    in reply to: Very slow with Xubuntu 20.04 #33073
    Avatarbobnx
    Participant

    Additional info – right click on desktop brings up the desktop menu on the server but menu does not appear on client until mouse is moved.

    in reply to: Xubuntu freezes after couple of connections #33066
    Avatarbobnx
    Participant

    This may not be a NoMachine problem.  I have noticed that after a recent Xubuntu 20.04 update the screen freezes as per your description.

    It seems to be a problem with xfce4_screensaver.

    Removing screensaver (setting to never lock/save seems enough) fixes problem.

    Not had this on Xubuntu prior to 20.04 and in fact first version of 20.04 seemed fine.  Only happened after an update.  Also laptop does not suffer but a couple of different desktops do.  So it is some combination of circumstances on the particular 20.04 machines.

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