Ok, that draft was way more complicated than it should and there's an easier way, also we need to logout and login again for the extension to show. Is it a problem if we restart GNOME shell during install? Here's a better script: 1 #!/bin/bash 2 git clone --depth=1 https://github.com/fthx/no-overview.git 3 NO_OVERVIEW=$(jq -r .uuid no-overview/metadata.json) 4 gnome-extensions pack no-overview 5 gnome-extensions install $NO_OVERVIEW.shell-extension.zip 6 # Restart GNOME shell 7 gnome-extensions enable $NO_OVERVIEW in line 6, I found the following: https://github.com/brunelli/gnome-shell-extension-installer/blob/4357903be8646d940902852bf3e150f625e350e6/gnome-shell-extension-installer#L288

No, nothing happened. When I tell gnome-extensions list it return empty. On my x86 desktop running Noble Gnome.

thanks @prahal - the only image I was able to successfully create and boot from was the initial image mentioned in my original post. At that stage there was: - eMMC with RoobiOS pre-installed - NVMe with nothing on it - micro SD card with the https://dl.armbian.com/rock-5-itx/Bookworm_vendor_minimal image Because it was booting to the error message of not being able to mount mmcblk01p as the root file system, I'm guessing that means the boot sequence is eMMC, NVMe and then micro SD. So I thought I would double-check, given that I now have a working NVMe installation ... so I reburned the https://dl.armbian.com/rock-5-itx/Bookworm_vendor_minimal image to micro SD card to see if the board would boot to that before the existing OS on the NVMe drive. IT DID! Not only that but it booted cleanly (asked me to create the root password and my user account)! I had used the same image file that I had downloaded for the first installation so I really have no idea why it worked this time. Now I guess I have to work out how to transfer that to the NVMe drive ... I suspect there are plenty of Google answers for that so that's my research for next week.

Hi everyone, and thanks a lot for the help. I found the solution: the problem was Windows 11 on my laptop. After writing the Armbian image, if the SD card stays inserted, it becomes corrupted within a few seconds. This happens only with Armbian and only with R3S images. I have no idea why. So, to get a proper SD card, I need quick hands to remove it immediately after the writing finishes (no matter which software is used to write).

This part didn't work for you? It was cool that if I had Extension Manager running I could see the toggle turning on and off as I enable/disable. Also, I had to fully reboot to see it working.