Great Post!! Question though! Under Supported devices, you list * LibreComputer ROC-RK3328-CC… I checked this board out, it has the Rockchip RK3328, im assuming becuase its named that but, my question is… I have the Android TV BOX A5X Plus Mini (4K Ultra HD), and it has a ROCKCHIP RK3328… Does that mean this will be able to install on this tv box?
Maybe, but as the DTS is not made for your specific device, some stuff might not work. But chances are that it will boot.
Hi,
In May the Odroid C4 install will be 2 years old :-)
[nlc4@c4 ~]$ stat / | awk '/Birth: /{print $2}'
2020-05-14
[nlc4@c4 ~]$ screenfetch
nlc4@c4.test.2020.05.14
OS: Manjaro-ARM 22.01
Kernel: aarch64 Linux 5.15.11-1-MANJARO-ARM
##### Uptime: 2d 22h 55m
####### Packages: Unknown
##O#O## Shell: bash 5.1.12
####### Resolution: 1920x1080
########### DE: KDE 5.88.0 / Plasma 5.23.4
############# WM: KWin
############### GTK Theme: Breeze [GTK2/3]
################ Icon Theme: oxygen
################# Disk:
##################### CPU: Unknown @ 4x 1.908GHz
##################### GPU:
################# RAM: 1064MiB / 3696MiB
[nlc4@c4 ~]$
Congratulations to the dev team.
2 Likes
It might not boot to begin with as not all devices have same dram model so uboot might fail to initialize the memory.
You will have to try it yourself to know how far would it boot and how many IO works out of the box for your device.
Hello, @Strit. Thank you for your amazing work. I tested the rockpro64 from emmc moudle, I think you did some update in the u-boot. Now, it can boot, and the screen can display something. I tested the minimal and sway images. Colud you check the output?
1 Like
Sorry, I can not share images.
:: running hook [udev]
:: Triggering uevents..
:: running hook [plymouth]
:: performing fsck on '/deu/mmcbik2p2'
:: running hook Tudev]
:: Triggering uevents..
:: running hook [plymouth]
:: performing fsck on '/deu/mmcbik2p2':
fsck.ext2: Input/output error while trying to open /deumncb
/dev/mmcb1k2p2:
The superblock could not be read or does not describe a valid
filesystem.
If the device is valid and it really contains an
filesystem (and not swap or ufs or sonething else), then the
is corrupt, and you might try running ezfsck with an alternate
e2fsck -b 8193 (device)
or
e2fsck -b 32768 ‹device>
ERROR: fsck failed on
* /deu/mmcbik2n2°
:: mounting
' /deu/mmcb1k2n2°
on real root
mount: /new root: can't read superblock on deu/mncblk2p2.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#_
Yeah, it’s a general issue we have had with a fair amount of our devices lately. Still not sure why the kernel can’t find the rootfs, since the exact same image works fine on SD card.
Thank you，waiting for your good news. 
Thanks. I’ve created an issue based on your output, so we can track which devices have this issue and possible solutions to the problem.
Hello,
Can you share the content of extlinux.conf in /boot/extlinux ?
I think it is something to do with root=LABEL
ok，Thank you. @spikerguy
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 root=PARTUUID=38cf4fbd-eb59-4078-853d-bcae20d89c6f rw rootwait audit=0 splash plymouth.ignore-serial-consoles
1 Like
Hm. Will have to test this, as we moved away from LABEL because it was too generic. So uboot/extlinux.conf no longer reads PARTUUID properly it seems.
Will have to do some more testing here.
Made a couple of tests. I cannot get it to work with either LABEL or UUID either. Tested on both Rock Pi 4 (rk3399 based) and Quartz64 (rk3566 based).
So my question is now, are you sure you only have 1 Manjaro install in that device and that it’s on the eMMC?
I tested on the minimal image, just change like this
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 root=LABEL=ROOT_MNJRO rw rootwait audit=0 splash plymouth.ignore-serial-consoles
It’s ok, but the sway image seems can’t work.
Yes, just one manjaro. I think you can test the minimal image, it will work.
sway image out put like this
[FAILED] Failed to start Rule-basedâÇir for Device Events and Files
See
'systenctI status systend-udeud.service'
for details,
[
OK
] Stopped Journal Service.
Starting Journal Service.
[
OK
] Stopped Rule-based Manager for Device Events and Files.
Starting Rule-based ManageäÇifor Device Events and Files.
[FAILED] Failed to start Journal Service.
See
"systemctl status systemd-journald.service' for details.
[
OK
1 Stopped Journal Service.
Starting Journal Service.
[FAILED] Failed to start Rule-basedâÇir for Device Events and Files.
See
"systemct1 status systemd-udeud.service' for details.
[
OK 1 Stopped Rule-based Manager for Device Events and Files.
Starting Rule-based ManageâÇifor Device Events and Files
I [FAILED] Failed to start Journal Service.
2 See
"systemct1 status systemd-journald.service' for details.
IlI
OK
] Stopped Journal Service.
Starting Journal Service...
l1 FAILED] Failed to start Rule-basedäÇIr for Device Events and Files.
12 See
"systemctl status systemd-udevd .service' for details.
]I
OK
] Stopped Rule-based Manager for Device Events and Files.
Starting Rule-based ManageäÇlfor Device Events and Files
I [FAILED] Failed to start Journal Service.
12 See
'systemct1 status systemd-journald.service' for details.
OK
] Stopped Journal Service.
Starting Journal Service...
U FAILED] Failed to start Rule-basedâÇir for Device Events and Files.
12 See
"systemct1 status systend-udeud.service' for details.
JI
Ok
1 Stopped Rule-based Manager for Device Euents and Files.
Starting Rule-based ManageäÇifor Device Events and Files.
UI trAILED] Failed to start Journal Service.
2 See
"systemct1 status systemd-journald.service' for details.
IL n
] Stopped Journal Service.
U1 FAILED] Failed to start Journal Service.
2 See
" systemct1 status systemd-journald.service' for details.
I CFAILED] Failed to start Rule-basedâÇir for Device Events and Files.
2 See
'systemct1 status systemd-udeud.service' for details.
IL
OK
1 Stopped Rule-based Manager for Device Events and Files.
1 [FAILED] Failed to start Rule-basedâÇir for Device Events and Files.
12 See
"systemct1 status systemd-udeud.service'
for details.
Starting Show Plymouth Boot Screen..
I FAILED] Failed to start Show Plymouth Boot Screen.
12 See
'systemct1 status plymouth-start.service'
for details.
IL
OK
OK
] Started Forward Password RâÇls to Plymouth Directory Watch.
1 Reached target Local Encrypted Volumes.
OK
] Reached target Path Units.
[ TIME 1 Timed out waiting for device CI0-ef97-4982-82bc-8d0a720cb000.
1 [DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems.
OK
OK
1 Stopped Forward Password RáCluests to Wall Directory Watch.
] Reached target Timer Units.
OK
OK
] Reached target Login Prompts.
OK
1 Reached target Preparation for Network.
OK
1 Reached target Network.
] Reached target Network is Online.
OK
1 Reached target Socket Units.
OK
] Started Emergency Shell,
OK
] Reached target Emergency Mode.
Starting Til Plymouth To Write Out Runtime Data
IL
OK
Starting Create Volatile Files and Directories.
] Finished Tell Plymouth To Write Out Runtime Data.
1 [FAILED] Failed to start Create Volatile Files and Directories
12 See
" systemct1 status systemd-tmpfiles-setup.service'
Starting Record System Boot/Shutdown in UTMP...
for details.
1 [FAILED] Failed to start Record System Boot/Shutdown in UTMP.
2 See '
" systemct1 status systemd-update-utmp.service' for details.
sorry, I have no permission to upload image, so the output word spelling maybe wrong.
I did my tests with minimal image.
Does it work? I only have pine64 rockpro64 board, I do not know if it can work on Rock Pi and Quartz64 board. I will try to build sway from minimal image.
I’m using the Gnome desktop on Khadas VIM3, and after updating Manjaro ARM 21.12, I found out that the Gnome Shell Extension Mailnaq reported not being compatible with this version of Gnome Shell. I had to edit the metadata file:
sudo nano /usr/share/gnome-shell/extensions/mailnag@pulb.github.com/metadata.json
{
"description": "Mailnag GNOME-Shell extension",
"name": "Mailnag",
"shell-version": [ "41" ],
"uuid": "mailnag@pulb.github.com",
"settings-schema": "org.gnome.shell.extensions.mailnag",
"gettext-domain": "gnome-shell-extensions"
}
logout and login
Sounds like it should be reported to the extension maintainer. 
Yes, it would, if you can, do it, I don’t know how, I’m only here for the third day