Manjaro update to Kernel 5.18 breaks install
Hi all,

I downloaded the Manjaro-ARM-minimal-pine-h64-22.04 from Manjaro and flashed it onto an 16GB SD-Card, followed all the on-screen setup instructions/questions, SD-Card got resized and System was up and running.

Next I did the update with pacman and it revoked and signed some keys and had 80something files to update, confirmed with Y and let it run.
After pacman was finished I did a reboot and ended up with a black screen.... Rolleyes 

Got the UART Cable out and recorded the following:
U-Boot SPL 2021.10-2 (Dec 25 2021 - 19:35:48 +0000)
DRAM: 4096 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.5(release):d5992a4
NOTICE:  BL31: Built : 19:35:48, Dec 25 2021
NOTICE:  BL31: Detected Allwinner H6 SoC (1728)
NOTICE:  BL31: Found U-Boot DTB at 0xc08ebd0, model: Pine H64 model A

U-Boot 2021.10-2 (Dec 25 2021 - 19:35:48 +0000) Manjaro Linux ARM

CPU:   Allwinner H6 (SUN50I)
Model: Pine H64 model A
DRAM:  3 GiB
MMC:   mmc@4020000: 0, mmc@4022000: 1
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   phy interface8
eth0: ethernet@5020000
starting USB...
Bus usb@5101000: USB EHCI 1.00
Bus usb@5101400: USB OHCI 1.0
Bus usb@5311000: USB EHCI 1.00
Bus usb@5311400: USB OHCI 1.0
scanning bus usb@5101000 for devices... 3 USB Device(s) found
scanning bus usb@5101400 for devices... 1 USB Device(s) found
scanning bus usb@5311000 for devices... 1 USB Device(s) found
scanning bus usb@5311400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  2  1  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
249 bytes read in 3 ms (81.1 KiB/s)
1:    Manjaro ARM
Retrieving file: /initramfs-linux.img
8553821 bytes read in 425 ms (19.2 MiB/s)
Retrieving file: /Image
24656384 bytes read in 1222 ms (19.2 MiB/s)
append: initrd=/initramfs-linux.img console=ttyS0,115200 root=PARTUUID=24bd05f5-5339-4ae2-8590-23c1846a16bc rw rootwait audit=0 splash plymouth.ignore-serial-consoles
Retrieving file: /dtbs/allwinner/sun50i-h6-pine-h64-model-b.dtb
32213 bytes read in 7 ms (4.4 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41a20000
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 497d7000, end 49fff55d ... OK
   Loading Device Tree to 00000000497cc000, end 00000000497d6dd4 ... OK

Starting kernel ...

It appears that the Manjaro 5.18 Kernel is broken. Undecided

Has anybody else this issue and how did you solved it?
I ended up adding the packages "linux" and "linux-headers" to "IgnorePkg" section of /etc/pacman.conf to prevent pacman from upgrading to Kernel 5.18, not a solution but a workaround. Undecided
I do not own an 'H64', but have confirmed the problem with both 'Rock64 / Rockpro64'. (probably all rockchip soc's).
Symptoms are not as bad as in your H64 case.
But, I have confirmed that the most basic and most important interface = serial console (ttySx) is broken.
(I can't log in from ttySx, but FBCon is fine and I can log in from there.)

As you know, the serial console is a basic tool when troubleshooting.
It is unfortunate that a commit that breaks such an important interface has been left unattended for more than two weeks.
(Looking at GitLab, it certainly seems that no one has reported it ...)


In my case, I don't use the kernel they provide as-is, but use my own kernel, so it's not a problem.
However, I think there are a lot of people who are affected.
(If anyone update the system carelessly, the kernel will be updated as well, and if unlucky, it will become unbootable ...)

I see that you have a GitLab account.
Please report the problem to them.
Thanks for your suggestion, I just searched GitLab and they don't have a project listed under "manjaro".
DDG has listed the url "" but one has to register with them as ones gitlab login credentials are not accepted on that page (seems they host their own git).
I assumed so because url = "".
So you can read it, but you can't write it.

As for "kernel update", it is necessary to do it by monitoring the contents of the commit.
This is the workaround for the time being.

For standard users, this situation is likely to continue for a while.
Especially for H64 users, who will be unable to boot, the damage will be enormous.

Possibly Related Threads…
Thread Author Replies Views Last Post
  Manjaro Arm on the pineH64 roel 38 18,978 02-16-2022, 03:01 PM
Last Post: acwest

Forum Jump:

Users browsing this thread: 2 Guest(s)