installed vim4-ubuntu-22.04-gnome-linux-5.4-fenix-1.1-220721.img.xz via oowow
sudo apt update
sudo apt full-upgrade
sudo do-fenix-full-upgrade
this last command showed:
E: Unable to locate package fenix-updater-package-jammy-vim4-mainline
sync
sudo reboot
In control panel:
enabled Remote Desktop in Sharing
Remote Desktop is ON
Remote Control is ON
Enable Legacy VNC Protocol is checked ON
under this option, set selection to 'Require a password'
In Authentication section set a user name to :
user
copied the generated Password to remote machine
using 'VNC Viewer 6.21.920 (r45849) x64 (Oct 14 2021 14:43:07)' client on Mac OS Monterey Version 12.6
Shows an authentication dialog box, I enter the password I copied from the VIM4 machines Remote Desktop Authentication section (VNC does not use the username, just password)
On the client, the VNC client program just hangs showing 'Connecting to 192.168.86.10...'
Never goes past this window. On VIM4 desktop, in upper right corner, the yellow 'Sharing' icon has appeared next to the WiFi icon. If you click on the 'Sharing' icon, the drop down says 'Screen is Being Shared'. But nothing on client side.
If you press the 'Stop' button on the client VNC window, the client stops trying to connect, HOWEVER, on the VIM4, the yellow 'Sharing' icon is still there. You can go in and 'Turn Off' sharing under the dropdown described above.
using 'Microsoft Remote Desktop Version 10.7.9 (2011)
Remote Desktop just shows a black window on client machine, on VIM4 while RDP session is open, shows the 'sharing icon' on upper right corner of VIM4 desktop. When you exit the black screen on the client, the sharing icon goes away on the VIM4
If I logout of the VIM4 machine and try to attach, neither work, VNC shows an immediate message of 'The connection was refused by the computer'
Above steps work fine on a:
MeLE Fanless Mini PC Quieter3Q Celeron N5105 8GB 256GB with Gigabit Ethernet WiFi 6 PXE Dual HDMI 4K Unlock BIOS
Tried removing the password on the login keyring, this had no effect:
sudo apt install seahorse
removed pw from login keyring
I’m not sure if its an option for you, but I am using xrdp for remote desktop to my vim4 with no issue. Of note, I can’t have the session logged in locally on the vim, and the remote session simultaneously.
On your ubuntu, there is no way to select the NOT wayland option. I tried all the login options and the edit of sudo vi /etc/gdm3/custom.conf to disable wayland.
If you try to login to VIM4 with wayland off, you canNOT.
On the MeLe Intel SBC with stock x64 Ubuntu 22.04.1 LTS both VNC and RDP work under Wayland AND you can login with Wayland OFF and again both VNC and RDP work.
I realize x64 and ARM images are different animals, but the fact is the stock Ubuntu 22.04 on x64 works and your ARM image does not.
Gotta love technology… I suffered through Ubuntu not being able to use the NVIDA display drivers, the symptoms were exactly this, you tried to use the hardware accelerated drivers and Ubuntu would barf at the login and just return to login prompt.
Now it is the exact opposite, you try to use a non-accelerated driver and you cannot login …
Hi @hojordsh Thank you for the steps, I will give it a try. I use the Microsoft provided Remote Desktop app for Mac OS. It is a bit old, shows a 2011 date for it last update (version 10.7.9) , however a 2022 copyright. All that said, it still runs on a Intel MacOS 12.6 Monterey machine fine.
I tried using VNC and RDP and couldn’t get them working either. All I got was a black screen so I tried disabling Wayland and it borked the system until I backed out the change.
I gave up with the built in desktop sharing feature and installed xrdp but can only log in occasionally and never if a local user is already logged in. Strange that @hojordsh seems able to do so.
I also tried installing different versions of VNC following various tutorials but couldn’t get any of them to work reliably.
Just to be clear,
I can’t rdp if the session is open by another user (or myself locally). I can see in the logs that the session is used and cant be forwarded.
Im pretty sure its /var/log/xrdp it you tail -f that file, and try to rdp you should see what is failing
So it seems to me that the problem with built-in Wayland desktop sharing could be linked to the problems some people are experiencing with pipewire as both Wayland and pipewire definitely seem to be involved as this: https://wiki.archlinux.org/title/PipeWire#WebRTC_screen_sharing shows.
I realise that both of these are taking about systems other than the khadas but I would have though that some of what they are discussing might apply here.
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.
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.
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.
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.
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
