ziomario

Forum Replies Created

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • in reply to: Private: Nxplayer.bin crash on Ubuntu? #49263
    ziomario
    Participant

    The NoMachine app for mobile is not a server. You can use the Android app to start connections to a host where you have installed one of the server products, such as the free edition. It will not be possible to reach your Android device from your Ubuntu machine.

    What I want to do is to display / control Android from my Ubuntu machine. How can I do this ?

    You mean that on your Android device you then searched for NoMachine hosts and found 192.168.1.6 which is your Ubuntu computer being broadcast on the LAN? If you connect and the port is unavailable, you should see an error dialog telling you. Do you see any error dialogs when you try to connect?

    I mean that on the Ubuntu machine I searched for a NoMachine hosts and it found 192.168.1.6,which is the IP of my Android system

    Please make a test. Change the port back to the default 4000 port on your Ubuntu host (please leave all settings as default ones, if necessary reinstall) Go to your Android device and connect to it using the local IP address of the NoMachine Ubuntu PC. Can you connect?

    Android does not let us to use low ports. Port 4000 on Android host cannot be reached by any client,because it is too low.

     

    ziomario
    Participant

    Update 2 : I see the same behavior if I virtualize the same debian VM on linux with qemu + kvm. So,it does not depend about freebsd + bhyve.

    ziomario
    Participant

    UPDATE : There is a workaround to fix it,to stop and start the nx server,like this :

    sudo /etc/NX/nxserver --shutdown

    sudo /etc/NX/nxserver --startmode manual

    sudo /etc/NX/nxserver --restart

    but it is uncomfortable. I don’t understand why it works like this and how to fix it.

    in reply to: Can’t change GW port on the server settings #31618
    ziomario
    Participant

    7.0.211 on arm64 (jetson nano) ; I try to change the GW port directly from the GUI on the section server port,gateway port. You can see on the image that I have attached that the port is set to : 23960. I tried to change the value from there,but the change does not stick. When I go back and I come back to the same section or after having rebooted the nano, I always see the same port : 23960.

     

    ziomario
    Participant

    My mobile provider does not supports the nat. So, do u know a workaround for this ?

    ziomario
    Participant

    The Ip which starts with 10 is not the external IP of my mobile connection. Im not sure which kind of IP is this. it seems an internal ip,such as 172 or 192. As I said, the external IP of my mobile connection starts with 5. I can see it going on the website ‘www.showip.net’

    ziomario
    Participant

    I don’t know which kind of IP is the one that starts with 10. Usually, my external IP starts with 5.

    ziomario
    Participant

    Which IP number should I use? The external one? The IP number that I get going on the website: ‘https://showip.net/’? On port 4000? I did it. It does not work because the error “a connection timeout while trying to connect to “external ip” on port 4000.

    ziomario
    Participant

    Hello.

    I disabled the x server with the command : sudo systemctl set-default multi-user.target

    following this guide :

    https://www.nomachine.com/AR02R01074

    because I had a lot of flickering inside the NoMachine window. What you suggest to me to do now ? I should re enable it ? but why if now it works fine ? I tried all these pipelines and no one worked right now :

    gst-launch-1.0 -e videotestsrc ! nvivafilter cuda-process=true customer-lib-name=”libnvsample_cudaprocess.so” ! ‘video/x-raw(memory:NVMM), format=(string)NV12’ ! nvoverlaysink
    nvbuf_utils: Could not get EGL display connection
    WARNING: erroneous pipeline: could not link videotestsrc0 to nvivafilter0

    gst-launch-1.0 -e videotestsrc ! nvivafilter cuda-process=true customer-lib-name=”libnvsample_cudaprocess.so” ! ‘video/x-raw(memory:NVMM), format=(string)NV12’ ! nvoverlaysink
    nvbuf_utils: Could not get EGL display connection
    WARNING: erroneous pipeline: could not link videotestsrc0 to nvivafilter0

    gst-launch-1.0 videotestsrc is-live=true ! nvvidconv ! ‘video/x-raw(memory:NVMM), format=I420’ ! nvivafilter customer-lib-name=”./libnvsample_cudaprocess.so” cuda-process=true ! ‘video/x-raw(memory:NVMM), format=RGBA’ ! nvegltransform ! nveglglessink
    nvbuf_utils: Could not get EGL display connection
    Setting pipeline to PAUSED …
    Using winsys: x11
    ERROR: Pipeline doesn’t want to pause.
    Setting pipeline to NULL …
    Freeing pipeline …

    this seems to be the better one…

    gst-launch-1.0 nvarguscamerasrc ! ‘video/x-raw(memory:NVMM),width=3820, height=2464, framerate=21/1, format=NV12’ ! nvvidconv flip-method=0 ! ‘video/x-raw,width=960, height=616’ ! nvvidconv ! xvimagesink -e

    since it produces something like this :

    https://forums.developer.nvidia.com/t/resolution-problems-with-the-camera-imx219-77ir-mounted-on-the-jetson-nano/165140/5

    but anyway there is something wrong.

    in reply to: Various problems that I’m not able to fix #31126
    ziomario
    Participant

    Now I have. Yes, I have fixed the flickering problem. I have one further thing to understand : how to switch automatically the mouse cursor from the ubuntu / jetson nano / os to the Windows 10 / NoMachine client OS and viceversa, automatically without to press a shortkey combinations of keys. Thanks.

    in reply to: Various problems that I’m not able to fix #31096
    ziomario
    Participant

    Hello. I’ve just bought the dummy plug model EZDIY-FAB HDMI and I’ve attached to the jetson nano HDMI port. And under Ubuntu I went under monitor setting and I have chosen : “HDMI-0, resolution 1920 x 1080,refresh rate 60. In addition, I went under the display configuration panel of NoMachine and I’ve chosen “adapt to the window” ; I have also clicked on “modify display settings” and I have chosen “use a custom resolution to 1920 x 1080” ; quality = better. But the flickering problem is still there.

    in reply to: Flickering problem #31078
    ziomario
    Participant

    ok. but the point here is if I can fix it,because I don’t have an additional monitor to attach to the jetson nano.

    in reply to: Flickering problem #31050
    ziomario
    Participant

    When I use nomachine I detach the monitor from the board and I see the flickering. If I use the board with the monitor attached,without NoMachine,I don’t see the flickering. I’ve attached a video to show you what I mean for flickering.

     

     

    in reply to: Flickering problem #31043
    ziomario
    Participant

    – NoMachine product (7.0.211) and version on local : Windows 10

    – NoMachine product (7.0.211) and version on remote : ubuntu 18.04 for arm 64 (on jetson nano)

    – Whether the problem arises connecting to a physical or a virtual display : it happens when I connect the NoMachine client on Windows 10 to a NoMachine server running on ubuntu / jetson nano

    – Remote and local Windows/Mac/Linux version (Windows XP/7/8, OS X 10.x, Ubuntu xyz, Mint x.y, etc.) : client = Windows 10 ; remote server = cinnamon on ubuntu 18.04 for arm 64 (nvidia version)

    – If on Linux, desktop version (GNOME. KDE, whatever) on client and on server : cinnamon

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