Easyinstaller VNC connection refused

mvandenabeele · February 11, 2022, 10:06am

Hi

I’m trying to connect to a freshly installed Torizon Easy Installer using VNC because no display is connected at the moment. Both 192.168.11.1 (USB RNDIS) and the local IP in my network result in “connection refused”. I can ping both IPs successfully. Must I do something extra to enable the VNC server? Using Torizon Easy Installer v2.0b7 on a Verdin 1.1 development board with a Verdin V1.1A

Thanks in advance!

Merijn

mvandenabeele · February 11, 2022, 10:35am

Did some further testing…

First time reinstalling Easy Installer seemed to work according to ubuntu terminal. No VNC was available and a portscan showed the open ports from our project. Reinstalled Easy Installer again, and now the port scanner is showing

Connecting to port 5900 using Remmina gives me following error:

Trying to connect using TightVNC on Windows did nothing the first few times, but suddenly I got a working connection.

So I guess VNC server is working, but not as reliable as I would expect. For production, this will be unacceptable I’m afraid.

mvandenabeele · February 11, 2022, 10:56am

Third time, same procedure, now I get

henrique.tx · February 21, 2022, 1:53pm

Hi @mvandenabeele !

Sorry for taking so long to answer.

We just tried to reproduce your issue using Easy Installer 2.0b7, but it is working from our side.

About the “Too big desktop name length…”, could you try to modify the settings regarding the scaling of the image? Maybe something like “no auto” or “fix setting” could help you.

On Remmina, maybe go to Preferences > Appearance > Default view and try different settings.

Best regargs,

MariusM · February 22, 2022, 10:03am

Other solution:

enter recovery
load last (newer) Torizon Easy Installer from desktop

I had a similar problem on imx8x , on the old version Torizon Easy Installer did not work from my desktop over VNC , after update everything works

henrique.tx · March 8, 2022, 2:26pm

Hi @mvandenabeele !

Were you able to overcome the issue?

Best regards,

apanelli · March 8, 2022, 4:56pm

Hello, I 'm facing the same behaviour.
I enter into recovery mode, then I load latest version Verdin-iMX8MM_ToradexEasyInstaller_5.5.0+build.6 from the host, and after it boots (I see TEZI log output console) I cannot connect using VNC. After a while it throws timeout.

Doing the same but loading a previous version (Verdin-iMX8MM_ToradexEasyInstaller_5.4.0+build.4) works correctly and allows me to connect using the same VNC connection.

Best regards,
Alejandro

Verdin iMX8MM V1.1A
Verdin Development Board V1.1A

MariusM · March 10, 2022, 10:36am

test host by “PING” ping <IP_ADRESS>
is alive?
test VNC by “TELNET” telnet <IP_ADRESS> 5900

what are your results ?

apanelli · March 10, 2022, 3:29pm

Hi MariusM,

Both TEZI versions answer the ping test correctly, but only v5.4.0b4 establishes connection when I try the telnet command to 5900 port.

When I check the IP address in both version from the serial console, I get different results, like usb0 adapter is missed:

TEZI v5.4.0b4:

/ # ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
    link/ether 00:14:2d:68:2f:26 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.20/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::214:2dff:fe68:2f26/64 scope link
       valid_lft forever preferred_lft forever
3: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:14:2d:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.1/24 scope global usb0
       valid_lft forever preferred_lft forever
    inet6 fe80::214:2dff:feff:ffff/64 scope link
       valid_lft forever preferred_lft forever
4: mlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether d8:c0:a6:cf:72:17 brd ff:ff:ff:ff:ff:ff
/ #

TEZI v5.5.0b6:

/ # ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
    link/ether 00:14:2d:68:2f:26 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.20/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::214:2dff:fe68:2f26/64 scope link
       valid_lft forever preferred_lft forever
3: mlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether d8:c0:a6:cf:72:17 brd ff:ff:ff:ff:ff:ff
/ #

Could it be the reason that v5.5.0b6 is not working?

Best regards,
Alejandro

MariusM · March 10, 2022, 5:32pm

you did not provide the most important information

what IP you are trying to connect to

on TEZI v5.4.0b4 I see

192.168.0.20/24     192.168.11.1/24

on TEZI v5.5.0b6 I see

192.168.0.20/24

Why does the TEZI version matter to you?

apanelli · March 10, 2022, 5:44pm

Hi MariusM,

I used in both cases 192.168.0.20
It doesn’t matter at all to me by now, I’ve just had that problem and I solved it by using a previous version. I’m giving the information because maybe there is something wrong in the newer version, so it will be present in newer ones. Altough I’m not sure if it is a problem or a misconfiguration.

Best regards,
Alejandro

edwaugh · March 14, 2022, 1:21pm

Hi,
Just for information we see this issue pretty commonly as well. Some versions of EasyInstaller work and some don’t. 5.4 build 4 is the last working for us.
Ed

apanelli · April 1, 2022, 12:22am

Hello,

I have just tested latest version: TEZI v5.6.0b9 and usb0 adapter is available again, and I was also able to connect through VNC properly (using 192.168.0.20:5900 in my case).

/ # ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
    link/ether 00:14:2d:68:2f:26 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.20/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::214:2dff:fe68:2f26/64 scope link
       valid_lft forever preferred_lft forever
3: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:14:2d:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.1/24 scope global usb0
       valid_lft forever preferred_lft forever
    inet6 fe80::214:2dff:feff:ffff/64 scope link
       valid_lft forever preferred_lft forever
4: mlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether d8:c0:a6:cf:72:17 brd ff:ff:ff:ff:ff:ff
/ #

I’m not sure if it is the usb0 or other thing, but now it is working with this new version.

Best regards,
Alejandro