Manjaro ARM 20.02 released!

So, I built a c2 and n2 20.03 kde image, it's working well, congratulation, nice job
Enjoy!

c2
sudo buildarmimg -d oc2 -e kde-plasma -v 20.02 -n

[nlc2@c2 ~]$ screenfetch
                             nlc2@c2.20.02
                             OS: Manjaro-ARM 20.03
                             Kernel: aarch64 Linux 5.5.8-1-MANJARO-ARM
         #####               Uptime: 3m
        #######              Packages: Unknown
        ##O#O##              Shell: bash 5.0.16
        #######              Resolution: 1920x1080
      ###########            DE: KDE 5.67.0 / Plasma 5.18.2
     #############           WM: KWin
    ###############          GTK Theme: Breeze [GTK2/3]
    ################         Icon Theme: oxygen
   #################         Disk: 6.7G / 58G (13%)
 #####################       CPU: 4x Unknown
 #####################       GPU: 
   #################         RAM: 601MiB / 1899MiB

n2
sudo buildarmimg -d on2 -e kde-plasma -v 20.02 -n

[nln2@n2 ~]$ screenfetch
                             nln2@n2.20.02
                             OS: Manjaro-ARM 20.03
                             Kernel: aarch64 Linux 5.5.8-1-MANJARO-ARM
         #####               Uptime: 0m
        #######              Packages: Unknown
        ##O#O##              Shell: bash 5.0.16
        #######              Resolution: 1920x1080
      ###########            DE: KDE 5.67.0 / Plasma 5.18.2
     #############           WM: KWin
    ###############          GTK Theme: Breeze [GTK2/3]
    ################         Icon Theme: oxygen
   #################         Disk: 48G / 59G (84%)
 #####################       CPU: Unknown @ 6x 1.896GHz
 #####################       GPU: 
   #################         RAM: 474MiB / 3631MiB

The only problem is the n2 reboot, it doesn't work, the n2 20.03 kde image don't reboot with the GUI and the command line

the n2 20.03 boot ini file look like so

ODROIDN2-UBOOT-CONFIG

# Default Console Device Setting
setenv condev "console=ttyAML0,115200n8"   # on both

# Boot Args
setenv bootargs "root=LABEL=ROOT_MNJRO rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 clk_ignore_unused bootsplash.bootfile=bootsplash-themes/manjaro/bootsplash"

# Set load addresses
setenv dtb_loadaddr "0x20000000"
setenv loadaddr "0x1080000"
setenv initrd_loadaddr "0x3080000"

# Load kernel, dtb and initrd
load mmc ${devno}:1 ${loadaddr} /Image
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson-g12b-odroid-n2.dtb
load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux.uimg
#fdt addr ${dtb_loadaddr}

# boot
booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}

What is the solution to solve this issue?
Sorry but the hardkernel wiki is not helpful

Rebooting failure

  • Tip: If your board doesn't boot (after say 30 seconds). Connect the MicroSD or eMMC on your computer and edit the boot.ini file. There's a option to disable UHS cards. Comment that line.

Thanks for your help.

The n2 19.08 kde image reboot without problem, the boot ini file look like so

ODROIDN2-UBOOT-CONFIG

# Default Console Device Setting
setenv condev "console=ttyS0,115200n8"   # on both

# Auto Detection of Monitor settings based on your Screen information
setenv display_autodetect "true"

# HDMI Mode
# Resolution Configuration
#    Symbol             | Resolution
# ----------------------+-------------
#    "480x272p60hz"     | 480x272 Progressive 60Hz
#    "480x320p60hz"     | 480x320 Progressive 60Hz
#    "480p60hz"         | 720x480 Progressive 60Hz
#    "576p50hz"         | 720x576 Progressive 50Hz
#    "720p60hz"         | 1280x720 Progressive 60Hz
#    "720p50hz"         | 1280x720 Progressive 50Hz
#    "1080p60hz"        | 1920x1080 Progressive 60Hz
#    "1080p50hz"        | 1920x1080 Progressive 50Hz
#    "1080p30hz"        | 1920x1080 Progressive 30Hz
#    "1080p24hz"        | 1920x1080 Progressive 24Hz
#    "1080i60hz"        | 1920x1080 Interlaced 60Hz
#    "1080i50hz"        | 1920x1080 Interlaced 50Hz
#    "2160p60hz"        | 3840x2160 Progressive 60Hz
#    "2160p50hz"        | 3840x2160 Progressive 50Hz
#    "2160p30hz"        | 3840x2160 Progressive 30Hz
#    "2160p25hz"        | 3840x2160 Progressive 25Hz
#    "2160p24hz"        | 3840x2160 Progressive 24Hz
#    "smpte24hz"        | 3840x2160 Progressive 24Hz SMPTE
#    "2160p60hz420"     | 3840x2160 Progressive 60Hz YCbCr 4:2:0
#    "2160p50hz420"     | 3840x2160 Progressive 50Hz YCbCr 4:2:0
#    "640x480p60hz"     | 640x480 Progressive 60Hz
#    "800x480p60hz"     | 800x480 Progressive 60Hz
#    "800x600p60hz"     | 800x600 Progressive 60Hz
#    "1024x600p60hz"    | 1024x600 Progressive 60Hz
#    "1024x768p60hz"    | 1024x768 Progressive 60Hz
#    "1280x800p60hz"    | 1280x800 Progressive 60Hz
#    "1280x1024p60hz"   | 1280x1024 Progressive 60Hz
#    "1360x768p60hz"    | 1360x768 Progressive 60Hz
#    "1440x900p60hz"    | 1440x900 Progressive 60Hz
#    "1600x900p60hz"    | 1600x900 Progressive 60Hz
#    "1600x1200p60hz"   | 1600x1200 Progressive 60Hz
#    "1680x1050p60hz"   | 1680x1050 Progressive 60Hz
#    "1920x1200p60hz"   | 1920x1200 Progressive 60Hz
#    "2560x1080p60hz"   | 2560x1080 Progressive 60Hz
#    "2560x1440p60hz"   | 2560x1440 Progressive 60Hz
#    "2560x1600p60hz"   | 2560x1600 Progressive 60Hz
#    "3440x1440p60hz"   | 3440x1440 Progressive 60Hz
setenv hdmimode "1080p60hz"

# Monitor output
# Controls if HDMI PHY should output anything to the monitor
setenv monitor_onoff "false" # true or false

# Overscan percentage
# This value scales down the actual screen size by the percentage below
# valid range is 80 to 100
setenv overscan "100"

### voutmode : hdmi or dvi
setenv voutmode "hdmi"
# setenv voutmode "dvi"

# HPD enable/disable option
setenv disablehpd "false"

# Enable/Disable CEC
setenv cec "true"

# Hardkernel ODROID-VU7 support
# By default VU7 support is disabled
setenv disable_vu7 "true"
# setenv disable_vu7 "false"

# max cpu frequency for big core, A73 in MHz unit
# setenv max_freq_a73 "2004"  # 2.004 GHz
# setenv max_freq_a73 "1992"  # 1.992 GHz
# setenv max_freq_a73 "1908"  # 1.908 GHz
setenv max_freq_a73 "1800"  # 1.8 GHz, default value
# setenv max_freq_a73 "1704"  # 1.704 GHz
 
# max cpu frequency for little core, A53 in MHz unit
# setenv max_freq_a53 "1992"  # 1.992 GHz
setenv max_freq_a53 "1896"  # 1.896 GHz, default value
# setenv max_freq_a53 "1704"  # 1.704 GHz


# max cpu-cores
# Note:
# CPU's 0 and 1 are the A53 (small cores)
# CPU's 2 to 5 are the A73 (big cores)
# Lowering this value disables only the bigger cores (the last cores).
# setenv maxcpus "4"
# setenv maxcpus "5"
setenv maxcpus "6"

### Normal HDMI Monitors
if test "${display_autodetect}" = "true"; then hdmitx edid; fi
if test "${hdmimode}" = "custombuilt"; then setenv cmode "modeline=${modeline}"; fi
if test "${cec}" = "true"; then setenv cec_enable "hdmitx=cec3f"; fi

# VU7 Settings
if test "${disable_vu7}" = "false"; then setenv hid_quirks "usbhid.quirks=0x0eef:0x0005:0x0004"; fi

# Boot Args
setenv bootargs "root=/dev/mmcblk${devno}p2 rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=${hdmimode} cvbsmode=576cvbs max_freq_a53=${max_freq_a53} max_freq_a73=${max_freq_a73} maxcpus=${maxcpus} voutmode=${voutmode} ${cmode} disablehpd=${disablehpd} cvbscable=${cvbscable} overscan=${overscan} ${hid_quirks} monitor_onoff=${monitor_onoff} logo=osd0,loaded ${cec_enable}"

# Set load addresses
setenv dtb_loadaddr "0x1000000"
setenv loadaddr "0x1B00000"
setenv initrd_loadaddr "0x3700000"

# Load kernel, dtb and initrd
load mmc ${devno}:1 ${loadaddr} /Image
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson64_odroidn2.dtb
load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux.uimg
fdt addr ${dtb_loadaddr}

# boot
booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}

No idea. I don't see any options to disable UHS cards in the config, both old and new.

Hello, I use a Minimal install of Manjaro on headless RPi4.
I installed this in Oct 2019, and am having much difficulty with all the mirror changes.

I tried running the suggested

wget http://manjaro-arm.moson.eu/stable/core/aarch64/pacman-mirrorlist-20200225-1-any.pkg.tar.xz && sudo pacman -U pacman-mirrorlist-*

then sudo pacman-mirrors -g gives me:

Traceback (most recent call last):
  File "/usr/bin/pacman-mirrors", line 23, in <module>
    from pacman_mirrors import pacman_mirrors

I also tried to just do a clean install, but

  1. There's no minimal 20.02 image
  2. The manjaro-arm-installer appears to be incompatible with my PC desktop distro (Linux Mint 19.3)
$ sudo bash manjaro-arm-installer
systemd-nspawn command is missing! Please install the relevant package.

I have systemd installed, but I don't see any package containing "nspawn" in the name.

Is there any way to get my install to function again after all these mirror changes?

I think I can get you an img for minimal tomorrow. As a clean installation is the only option.

@spikerguy Thanks for the offer, but I've realized 19.12 minimal image is provided, and was able to install and update mirrors from there. It seems to be working ok now.
Still it could be useful for others if the latest minimal image was officially provided.

edit: And just out of curiosity, is there a specific systemd (bleeding edge?) version requirement for manjaro-arm-installer, or any other idea why it would not work on my Mint desktop?

Minimal images was provided up to 19.12.
The reason we discontinued them, was the very low download numbers, compared to the work of making, testing and uploading them.

It needs systemd, with support for the --resolv-conf=copy-host option. This seems to be an issue with debian/ubuntu based systems.

Last night, I put my PBP in sleep, and I lost almost 40% of my battery. Is this due to the s2 sleep? I read in the thread that s3 sleep was working for someone, should this already have landed in the unstable branch or not?
I'm running the Gnome DE on Wayland. How can I check if HW acceleration is being used and enable it?

I noticed that the MVME's speed decreases after the pbp was in suspend mode

How did you fit that drive in your PBP? I bought the same drive and ended up using it as a second drive in my NUC, because I couldn't fit it to the PBP.

Dear Manjaro Pi developers, thank you for the great pi version. It runs great on my Pi4, the only thing I would love to have is a built in is RealVNC server just like in Raspbian. I think most of us run the pi as a secondary pc, to have a built in RealVNC server would allow easy VNC connection without additional configuration

Can that be please a feature request?
Thank you

Hi,

for the vnc give a look here ( 2 link), I hope it will be helpful, on my side I use krdc and krfb

https://forum.manjaro.org/t/tigervnc-on-manjaro-arm-rpi4-running-gnome/123415

https://forum.manjaro.org/t/realvnc-server-on-raspberry-pi-4/110581

As I have one of the wrong adapters that were shipped with the first “bad batch” I followed the instructions from danielt, but I didn’t use a cable tie to fix the SSD in its position. I used a small piece of double side tape.

Does its job so far...

Hmm... I was waiting for Pine64 to release a new adaptor. Does the SSD make much difference to anything? Boot times, application launching times?

Didn’t compare boot times but to me apps start quicker and the system feels smother. Thats why I noticed the speed difference after suspend mode.

Could they not be added back to the repositories in case people want to use them? I previously had them set as my system theme. I prefer matcha to breath2. Only noticed it had gone after I re-flashed Manjaro onto my PBP.

It can be installed from the themes gitlab.
Not much point from a package maintainer, to maintain something that's not used in the editions. Especially when the theme had flaws.

The Matcha GTK style is still in the repository. The papirus icons are also still in the repository. You can download the Matcha KDE package manually. The Matcha KDE package currently is this one. Wrote about it in post 72, following an earlier tip from Strit. Just 'sudo pacman -U' the downloaded package and then set it up with System Settings.

My PBP takes quite q long time before the power LED changes from red to green. Is this a uboot or kernel issue? How can I check if I have the latest uboot installed?

for me as well on emmc or any sd on any distro after a couple installation swaps

Forum kindly sponsored by