[ARM Stable Update] 2020-03-26 - KDE Plasma 5.18.3 + applications + frameworks, Thunderbird 68.6.0 and Kernels

Hello ARM community.

Another Stable update is upon us!

This is a big stable update, where almost everything got updated.


This update features:

  • Most of our kernels got updated
  • Thunderbird updated to 68.6.0
  • KDE Plasma got updated to 5.18.3
  • Plasma Frameworks updated to 5.68
  • KDE Applications updated to 19.03.3
  • Plasma Mobile packages got updated

Upstream Notifications:
The packages hplip and firewalld requires manual intervention:
https://www.archlinux.org/news/hplip-3203-2-update-requires-manual-intervention/
https://www.archlinux.org/news/firewalld081-2-update-requires-manual-intervention/


  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

4 Likes

Known Issues:

Hi,

I updated c2 and n2, 20.02 kde and 20.03 kde version

c2 20.02 kde reboot after update
c2 20.03 kde don't reboot after update

same issue with the n2

n2 19.08 kde reboot after update
n2 20.02 kde reboot after update
n2 20.03 kde don't reboot after update

please find below more details

extlinux.conf c2 20.02 kde reboot without problem with console or GUI

LABEL Manjaro ARM
KERNEL ../Image
FDT ../dtbs/amlogic/meson-gxbb-odroidc2.dtb
APPEND initrd=../initramfs-linux.img console=tty1 root=LABEL=ROOT rw rootwait bootsplash.bootfile=bootsplash-themes/manjaro/bootsplash

extlinux.conf c2 20.03 kde don't reboot after update

LABEL Manjaro ARM
KERNEL ../Image
FDT ../dtbs/amlogic/meson-gxbb-odroidc2.dtb
APPEND initrd=../initramfs-linux.img console=tty1 root=LABEL=ROOT_MNJRO rw rootwait bootsplash.bootfile=bootsplash-themes/manjaro/bootsplash

boot.ini n2 20.02 kde reboot after update

ODROIDN2-UBOOT-CONFIG

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

# Boot Args
setenv bootargs "root=LABEL=ROOT 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}

boot.ini n2 20.03 kde reboot after update

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}

I stay tune for more details

Absolute no problem with the 19.08 kde, reboot without problem with console or GUI
boot.ini n2 19.08 kde reboot after update

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}

This is a general problem with Amlogic boards on newer mainline kernels.
No idea why though.

The 19.08 release is still the best for Odroid N2. The 4.9 kernel there is still much better than the mainline kernels. It is a bit of an effort to update to current, but still, 19.08 is best for ON2. Is there a (normal/good) way to install an up-to-date 4.9 odroid n2 kernel on 20.02? Update went smooth on 19.08. :slight_smile:

1 Like

Nope. Since we switched to mainline, we haven't updated the BSP kernel in the repo.

Hi,

I agree with you for the 19.08, but the 20.02 and 20.03 are working well, unfortunately the reboot is not ok...

I'm late but I give you an answer, it was an old question from you

The c2 is not equiped with audio adaptater and wifi module, but hardkernel (the odroid designer)
sell WiFi Module 3 and USB Audio Adapter, those accessories are both working well with manjaro arm for odroid c2 and n2. (tested with success on linux and win desktop)

For PBP, beside the compositor settings, the update did NOT do
editing /etc/environment and commenting the
QT_QUICK_RENDERER=software line
Made it really quite unpleasant, double mouse, black 'comet',,
false flip to login screen every 2 minutes
OK now

Hi,

Are you talking about the odroid n2? Is it a solution for the reboot?

The /etc/environment file look like so for the manjaro arm kde 19.08, 20.02 and 20.03

#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
QT_QUICK_BACKEND=software

Is the file correct now with those line?

#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
QT_QUICK_BACKEND=software line

Sorry, I don't understand the next step, thanks for your reply.

It actually is surprising at how well the 4.9 kernel does compared to mainline. It's not just the missing audio or the missing reboot/shutdown that is missing. It's just more speedy, more smooth, plays better video in firefox, it's just better. I have no doubt that at some point mainline kernels will improve above and beyond the 4.9, but at this point, 4.9 is the better option for Odroid N2. (And no glitching video output with 4.9, I have that on mainline as well, tested with a lot of hardware. )

And on a brand new install of 19.08 for ON2, just manually update python (from extra) and then pacman-mirrors manually and you are good to go on Odroid N2. No pretty bootsplash, but lots of benefits.

We are a mainline distro though, so we want to go mainline as much as possible.

The Amlogic boards are a pain to support on mainline and their BSP kernels are ancient (4.9 is years old at this point). So no matter what we do, we won't win.
I feel like we should push mainline on these boards, even though some things are not working yet.

The things that are not working on mainline are mainly: Audio, Video acceleration and 3d acceleration.
The rest is pretty much there. Those 3 requires the correct drivers. Audio is really weird on Amlogic, right now it conflict with pulseaudio (which is a userland tool). Video acceleration is being worked on, by LibreELEC and 3d acceleration will get there, when Panfrost makes support for the G12X series MALI GPU's.

2 Likes

Some things are not working yet, we are here to improve this state, with no problem.

Indeed, going forwards mainline is the way to go! That said, for end users... 19.08. (And I'm thinking something is not quite right somewhere, because overall performance on mainline is down compared to 4.9. But perhaps that's just on my use cases, surfing the web and using the desktop.) All will come in due time to mainline.

That is probably because of video driver support.

That could well be. I noticed playing video files on an un-updated 19.08 was a lot smoother than on a fully updated update 19.08. So the video processing has actually declined with recent driver updates, and that is even without the mainline kernel route. And with the additional issues with mainline... When graphics / video acceleration actually arrives on mainline, and the power management is fixed, and the audio... the Odroid N2 will be awesome. :smile: For now, 19.08 for the Odroid really kicks ***. So: Many thanks for having supplied it :slight_smile:

2 Likes

Somehow the single quotes disappear,,
Put # at beginning of line QT_QUICK........

1 Like

Thanks for your answer,

is it correct so ?

#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
# QT_QUICK_BACKEND=software line

Essentialy, yes. I don't think you understand, though.
To make a LINE commented, add a "#" at the beginning,
the line becomes a comment, so the "extra", "unneeded" word "line"
does not matter, the line is now a comment
Read the post again
Did you have the double mouse pointer or other problems?

Thanks for the explications

You're right, I'm lucky I Have no double mouse pointer or other problems like that

For the comment the c && c++ language use // :slight_smile: or /* :slight_smile: */

Have a good day.

tl;dr: Skipped previous update, needed to adjust bootloader config.


My Manjaro ARM install on a Rock Pi 4 stopped booting after this update.

I did not update u-boot when the package was updated, so I did it manually. But it didnt work.

Checking Serial console, it was stuck:

U-Boot 2020.01-4 (Mar 04 2020 - 09:29:33 +0000) Manjaro ARM

Model: Radxa ROCK Pi 4
DRAM:  3.9 GiB
PMIC:  RK808 
MMC:   dwmmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: Radxa ROCK Pi 4
rockchip_dnl_key_pressed: adc_channel_single_shot fail!
Net:   eth0: ethernet@fe300000
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0(part 0) is current device
** Unrecognized filesystem type **
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
382 bytes read in 7 ms (52.7 KiB/s)
1:      Manjaro ARM
Retrieving file: /boot/extlinux/../initramfs-linux.img
7838780 bytes read in 338 ms (22.1 MiB/s)
Retrieving file: /boot/extlinux/../Image
21225984 bytes read in 899 ms (22.5 MiB/s)
append: initrd=../initramfs-linux.img console=tty1 root=PARTUUID=d1637089-a0e3-4261-9d90-ad9cf334c764 rw rootwait bootsplash.bootfile=bootsplash-themes/manjaro/booh
Retrieving file: /boot/extlinux/../dtbs/rockchip/rk3399-rock-pi-4.dtb
72638 bytes read in 13 ms (5.3 MiB/s)
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f57a8000, end f5f21c3c ... OK
   Loading Device Tree to 00000000f5793000, end 00000000f57a7bbd ... OK

Starting kernel ...

Searching in /boot, boot.txt was renamed to boot.txt.pacsave and there was a new extlinux folder.

I remembered @Strit posting something about extlinux, and came across the previous update which I had skipped:

After updating extlinux.conf to point to my root partition (I run root off a external HDD), things started working again.

Thanks.

Edit-
Serial console is not reaching login prompt, stuck at loading kernel line. Otherwise its working.

Edit 2-
Changing console=tty1 to console=ttyS2,1500000 in extlinux.conf as done in boot.txt.pacsave fixes the serial console issue.

1 Like

Forum kindly sponsored by