VNC nor RDP working, help with how to setup on VIM4 Ubuntu 22.04.1

Yes it does seem like there is a lot of complexity and interactions.

All that said, I have a MeLE Quieter3 Intel based SBC side by side with the Khadas VIM4. The MeLE Quieter 3 is running the x64 Ubuntu 22.04.1 LTS off the shelf download from the Ubuntu web site. VNC, RDP, Wayland, pipewire all work without any messing around. And to make it worse for Khadas, the performance of the MeLE SBC is far better. Hardware video drivers are working fine. Trying to do a ARM based Linux machine does seem to be still far behind x64 Intel or AMD. And now we have RISC-V coming up.

user@quieter3-01:~$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 49
Tile Size: 65472
User Name: user
Host Name: quieter3-01
Server Name: pulseaudio
Server Version: 15.99.1
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_00_1f.3.hdmi-stereo-extra1
Default Source: alsa_output.pci-0000_00_1f.3.hdmi-stereo-extra1.monitor
Cookie: 3408:c67e
user@quieter3-01:~$ inxi -Fx
System:
  Host: quieter3-01 Kernel: 5.15.0-48-generic x86_64 bits: 64 compiler: gcc v: 11.2.0
    Console: pty pts/0 Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish)
Machine:
  Type: Mini-pc System: Fanless Mini PC product: Quieter 3 v: N/A serial: <superuser required>
  Mobo: Fanless Mini PC model: Rev JSL1 1.10 serial: <superuser required>
    UEFI: American Megatrends LLC. v: ML_JPL1V1.0 date: 03/15/2022
CPU:
  Info: quad core model: Intel Celeron N5105 bits: 64 type: MCP arch: Tremont rev: 0 cache:
    L1: 256 KiB L2: 1.5 MiB L3: 4 MiB
  Speed (MHz): avg: 778 high: 801 min/max: 800/2900 cores: 1: 801 2: 765 3: 800 4: 747
    bogomips: 15974
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel JasperLake [UHD Graphics] driver: i915 v: kernel bus-ID: 00:02.0
  Display: server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1 driver: gpu: i915
    note:  X driver n/a tty: 152x45 resolution: 1920x1080
  Message: GL data unavailable in console. Try -G --display
Audio:
  Device-1: Intel vendor: Realtek driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Sound Server-1: ALSA v: k5.15.0-48-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX201 160MHz driver: iwlwifi v: kernel bus-ID: 00:14.3
  IF: wlp0s20f3 state: up mac: 80:38:fb:64:82:e6
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel
    port: 3000 bus-ID: 01:00.0
  IF: enp1s0 state: down mac: 00:ce:39:d1:0f:ea
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-8:3
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: 80:38:FB:64:82:EA bt-v: 3.0
    lmp-v: 5.2
Drives:
  Local Storage: total: 230.62 GiB used: 12.12 GiB (5.3%)
  ID-1: /dev/mmcblk1 model: SCA256 size: 230.62 GiB
Partition:
  ID-1: / size: 225.45 GiB used: 12.12 GiB (5.4%) fs: ext4 dev: /dev/mmcblk1p2
  ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat dev: /dev/mmcblk1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 234 Uptime: 3d 18h 42m Memory: 7.52 GiB used: 1.5 GiB (20.0%) Init: systemd
  runlevel: 5 Compilers: gcc: 11.2.0 Packages: 1883 Shell: Bash v: 5.1.16 inxi: 3.3.13

The same over here. I cannot get VNC or RDP working either. I have another Ubuntu 22.04.1 LTS on an Intel Nuc where everything works flawless.

Hello @numbqq ,
Still, neither VNC or RDP work on

khadas@Khadas:~$ cat /etc/fenix-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=VIM4
VENDOR=Amlogic
VERSION=1.2
ARCH=arm64
INITRD_ARCH=arm64
IMAGE_VERSION=1.2-221018
################ GIT VERSION ################
UBOOT_GIT_VERSION=khadas-vims-u-boot-2019.01-v1.2-release
LINUX_GIT_VERSION=khadas-vims-linux-5.4-v1.2-release
FENIX_GIT_VERSION=v1.2
#############################################

Tried with desktop logged on and with desktop logged out. Used standard desktop sharing setup that is shown in ‘Remote Desktop’ section of ‘Sharing’ in ‘Setting’.

Again, not having this working as easily as it does on stock Ubuntu on x86 SBC makes it so difficult for end users to select your product as a useful tool. That’s not good for you, that not good for Linux, that’s not good for ARM.

1 Like

Hello @deepvim

About VNC it works on Ubuntu 20.04, but we do the same steps on Ubuntu 22.04 it doesn’t work, we need to check waht’s the different between Ubuntu 20.04 & Ubuntu 22.04.

Does xrdp works for you?

I did the steps @hojordsh recommended prior to the clean install of the Oct release of the desktop image, it worked then, however I have not tried it since my full wowoo install of the Oct release. Even if that works, it really not the solution that is optimal, IMHO. The control panel vnc and rdp should work out of the box as it does on a stock x64 ubuntu install.

Hello @deepvim I would like to ask you for some details about the use of vnc.

  • The desktop environment you are using is on x86 ubuntu22.04

    • Is it gnome or xfce or something else

    • Is the display frame either X11 or Wayland

  • Can you provide some configuration details

It might make khadas perfect
Thanks!

Hello @ivan.li

I am running the Intel based SBC shown below side by side with the VIM4 ARM. As is shown in the screen capture, it is running the standard download Ubuntu 22.04.1 LTS with GNOME 42.4 using Wayland windowing system. This is all standard ‘out of the box’ nothing added or changed other than via standard ‘apt-get update’ ‘apt-get ful-upgrade’. VNC and RDP work and are able to interact with the GUI session logged into the physical machine. IMHO, this is the way it should work, not a separate session on VNC/RDP from the physical session.

MeLE Fanless Mini PC Quieter3Q Celeron N5105 8GB 256GB Windows 11 Pro Micro Computer Small Desktop Servers with Gigabit Ethernet WiFi 6 PXE Dual HDMI 4K Unlock BIOS

@deepvim Thank you so much for your reply.

Thanks all in trying to get this solved.

@deepvim Sorry to trouble you again. I installed the vnc service on the Intel based SBC today( The details of the desktop environment are shown in the following figure)

  • My Intel based SBC was a disappointment to me.His remote screen can connect successfully, but it doesn’t have any display just black.

  • My judgment is that the desktop environment is not working. I wrote a configuration file for it to run at startup( file path: ~/.vnc/xstartup). My config file just makes it work for the xfce desktop environment.
    Unfortunately GNOME is what I want .:rofl:

  • I would like to know if you have modified or added configuration files for VNC(eg: ~/.vnc/xstartup)

  • Please forgive me for being new to vnc .I’m working on it and I look forward to some help from you. I want the vnc to work properly(Ubuntu 22.04.1 LTS with GNOME 42.4 using Wayland windowing system or x11)

Distant friends, looking forward to your reply

Hi @ivan.li I have wasted many an hour on getting VNC and RDP to work on many various client/server combos. Don’t know if you are old enough, but way back went, I thought these were going to solve the hours that we all wasted getting remote X.11 to work :wink: Not.

Black VNC and RDP screens are an unfortunate fact of the path to getting these things to work.

As I said, I modified NOTHING in the stock Ubuntu 22.04.1 Remote Desktop Control panel or in any config files. That said, setting on the client side can make a difference, I am using RealVNC VNC Viewer 6.21.920 (r45849) x64 (Oct 14 2021 14:43:07) client on Mac OS 12.6. Try setting ‘Picture Quality’ to ‘High’ and ‘Scaling’ to ‘Automatic’, ‘Security’ to ‘Let VNC Server choose’ on your VNC client.

I note you are using X11 Windowing System, where as my Intel SBC Ubuntu 22.04.1 is using Wayland. As well, you and I have a different graphics adapter on the Linux machine. Both may play into the difference.

Apologies I can not be of more help. The whole remote control thing is a PIA.

@deepvim Thank you for your thoughtful answer. Let me on the muddy road is not so lonely.Have a good day/everything/night/morning wherever you are :laughing:

Hello @deepvim

We have some possitive improgress to make VNC work on VIM4.

Here is the steps:

On VIM4:

$ sudo apt-get install tigervnc-standalone-server
$ vncserver -localhost no :1

thanks for your step by step guide I have a Edge2 and couldn’t get rdp going and didnt know what to ask but your info helped a lot

lostpilot

Excellent. I did have to modify the .ini file to use “rdp”, but after that it worked.