Manjaro ARM 20.08 released!

[Darksky]

NetworkManager-wait-online gets enable by NetworkManager just like systemd-networkd-wait-online.service does with systemd-networkd. I have pulled the plug on my network and it booted straight into the desktop with no lag so I am not seeing here a dependency. Strit is right that this issue has become more prevalent lately.

What I am seeing is systemd-networkd being enabled and NetworkManager fighting for control going back and forth. I have never liked systemd-networkd and NetworkManager being enabled at the same time and always disable systemd-networkd. I have had issues in the past with this. The NetworkManager and the systemd-networkd wiki’s both say to not have any other network service running when using one or the other.

Here is some lines showing (of many) systemd-networkd and NetworkManager fighting and taking control from each other. Sometimes on a first boot the wait would be a few seconds and other times it would be a long time. This is when it was a long time:

Sep 06 11:30:59 pi4 systemd-networkd[188]: wlan0: Link DOWN
Sep 06 11:30:59 pi4 NetworkManager[302]: <info>  [1599409859.1435] device (wlan0): set-hw-addr: set MAC address to 26:D2:55:E5:AF:8D (scanning)
Sep 06 11:30:59 pi4 kernel: brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
Sep 06 11:30:59 pi4 systemd-networkd[188]: wlan0: Link UP
Sep 06 11:30:59 pi4 NetworkManager[302]: <info>  [1599409859.1506] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Sep 06 11:30:59 pi4 NetworkManager[302]: <info>  [1599409859.1508] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled
Sep 06 11:30:59 pi4 NetworkManager[302]: <info>  [1599409859.1528] device (wlan0): supplicant interface state: interface_disabled -> inactive
Sep 06 11:30:59 pi4 NetworkManager[302]: <info>  [1599409859.1528] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive
Sep 06 11:33:00 pi4 dbus-daemon[639]: [session uid=1000 pid=639] Activating service name='ca.desrt.dconf' requested by ':1.68' (uid=1000 pid=931 comm="mousepad /home/ray/Desktop/New File ")
Sep 06 11:33:00 pi4 dbus-daemon[639]: [session uid=1000 pid=639] Successfully activated service 'ca.desrt.dconf'
Sep 06 11:37:54 pi4 systemd-networkd[188]: wlan0: Link DOWN
Sep 06 11:37:54 pi4 NetworkManager[302]: <info>  [1599410274.0556] device (wlan0): set-hw-addr: set MAC address to 2A:67:68:2F:C9:3A (scanning)
Sep 06 11:37:54 pi4 systemd-networkd[188]: wlan0: Link UP
Sep 06 11:37:54 pi4 kernel: brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
Sep 06 11:37:54 pi4 NetworkManager[302]: <info>  [1599410274.0615] device (wlan0): supplicant interface state: inactive -> interface_disabled
Sep 06 11:37:54 pi4 NetworkManager[302]: <info>  [1599410274.0616] device (p2p-dev-wlan0): supplicant management interface state: inactive -> interface_disabled
Sep 06 11:37:54 pi4 NetworkManager[302]: <info>  [1599410274.0628] device (wlan0): supplicant interface state: interface_disabled -> inactive
Sep 06 11:37:54 pi4 NetworkManager[302]: <info>  [1599410274.0629] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive

I burned a fresh image and disabled systemd-networkd in /user/lib/system-preset/90-systemd.preset while the sdcard was still in my desktop. systemd-networkd is part of the systemd package and is a strange animal. It does not get enabled until the first boot so I had to disable it in the file that gets read. But after you first boot it can be disabled with systemctl:

disable systemd-networkd.service
disable systemd-resolved.service

I also stopped a stop-dmesg.service that we have to stop spam when the set up menu comes up and saw some more lines after the bluetooth where you do not see any and there were a few more lines being printed out about 1 a second setting thing up but no errors.

[pato]

I have troubles installing Manjaro Sway on my newly shipped PineBook Pro.

What I did:

1. Download Manjaro ARM 20.08 Sway, SHA1 is okay.
2. Flashed the .img.xz to my SD card using Etcher.
   2.b I also copied the .img.xz file into the home folder onto the SD card
3. Put SD card in Pinebook Pro, Power on, system is running from SD card.
4. Installed manjaro-arm-flasher using pamac.
5. Run manjaro-arm-flasher, using the .img.xz file I copied to the SD card earlier, flash it to the internal drive.
6. Poweroff, remove SD card, power on:

Manjaro Logo with Spinning wheel for about 1 minute, then a black screen, occasionally showing the error message for a brief moment:

XDG_RUNTIME_DIR is not set in the environment. Aborting.

I tried to find help searching the web, but only found outdated GitHub issues.
Do you have any advice?

[Strit]

Hm. @appelgriebsch might know what that’s about?

[appelgriebsch]

That’s wired. Could you pls boot from the working SD card and check the partitions on your eMMC… there should be a BOOT_MNJRO and a ROOT_MNJRO.

Haven’t used the manjaro arm flasher to set up my pbpro as I’m already using a nvme as root partition. So I also just did the usual restore to microSD for the 20.08 image without any issues…

[pato]

$ lsblk -o +FSTYPE,LABEL

NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT FSTYPE LABEL
mmcblk2      179:0    0  58,2G  0 disk                   
├─mmcblk2p1  179:1    0 213,6M  0 part            vfat   BOOT_MNJRO
└─mmcblk2p2  179:2    0    58G  0 part            ext4   ROOT_MNJRO
mmcblk2boot0 179:32   0     4M  1 disk                   
mmcblk2boot1 179:64   0     4M  1 disk                   
mmcblk1      179:96   0   116G  0 disk                   
├─mmcblk1p1  179:97   0 213,6M  0 part /boot      vfat   BOOT_MNJRO
└─mmcblk1p2  179:98   0 115,8G  0 part /          ext4   ROOT_MNJRO
zram0        252:0    0   5,6G  0 disk [SWAP]

It seems to be fine…

[appelgriebsch]

Japp looks good. Just to make sure the flashing was a ok could you please try it in another way…

1. boot from microSD
2. open up a terminal
3. go to the folder holding your downloaded image file
4. get root via sudo su -
5. run xzcat Manjaro-ARM-sway-pbpro-20.08.img.xz | dd of=/dev/mmcblk2 bs=1M status=progress conv=fsync to flash it to eMMC
6. after it’s done reboot the pbpro and follow the initial setup wizard steps

[pato]

Awesome, this way it worked. Thank you

[appelgriebsch]

My pleasure!

[pato]

I have another issue with the terminal:

ht tps://ibb.co/mGY74j1
(sorry I am not allowed to post media or links. it is a link to a GIF showing my messed up terminal input)
It was like this from the beginning.
Do you know anything about this problem?

[pato]

It seems they fixed the according bug in silver, I hope the update will make it to the arch repositories soon

Line wrapping issue with silver in termite (using bash)

[regivanx]

Hello, has video acceleration been turned off? Videos on chromium are now extremely choppy. On chrome://gpu/

Problems Detected

• Accelerated video decode is unavailable on Linux: 137247, 1032907
  Disabled Features: accelerated_video_decode
• Protected video decoding with swap chain is for certain Intel and AMD GPUs on Windows: 1093625
  Disabled Features: protected_video_decode
• Clear uniforms before first program use on all platforms: 124764, 349137
  Applied Workarounds: clear_uniforms_before_first_program_use
• Always rewrite vec/mat constructors to be consistent: 398694
  Applied Workarounds: scalarize_vec_and_mat_constructor_args
• Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
  Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
• Some drivers can’t recover after OUT_OF_MEM and context lost: 893177
  Applied Workarounds: exit_on_context_lost

I’m on Pinbook Pro.

[bsu4phd]

Fresh installed Manjaro-ARM-xfce-rpi4-20.08.img.xz on a Pi 4 w/ the Element14 touch screen display. Boot hangs at “Reached target Bluetooth.”

Past fresh installs of Raspbian, Ubuntu have gone OK.

Any ideas?

[djaywhite]

@bsu4phd If you search for “Reach Target Bluetooth” using the forum search.
You will find :-

Manjaro ARM 20 on Raspberry Pi 3

We have reports of the boot process taking a lot of time, where it seemingly hangs at “Reached target Bluetooth”. Waiting for a few minutes should make it continue. We are not sure why this happens yet, but it seems related to Network Manager as that fails to enable and then re-enables fine when it continues.

Please read the link below as well, it will tell you how to get the most out of the forum and helps us to help you. Welcome

https://forum.manjaro.org/t/welcome-to-the-new-manjaro-forum/151/4

[djaywhite]

The first line of “Problems Detected” that you posted says :-

Accelerated video decode is unavailable on Linux: 137247, 1032907

If you click on the 137247 link you will see that this is a chromium issue.
You can ask them when it may become available.

[bsu4phd]

Thanks for the quick reply!

I did see that and waited for 10 min’s. plus. Apologies for failing to note that in my original post.

Could my issue be related to the Element14 touch screen display?

[djaywhite]

@bsu4phd
Try this as well.

@j0b314

Do I need some more libs?

[bsu4phd]

20.06 boots OK.

[Yuvia]

@Janne

La nueva instalación de xfce 20.08 en pinebook pro es muy lenta. Al igual que en, puedo ver ventanas emergentes dibujadas en 1-1.5 segundos; cambiar el tamaño de una ventana de terminal con el mouse se retrasará y se congelará horriblemente y así sucesivamente.

Hi. I am having the same experience with the latest Xfce image for rockpi4b. It works more smoothly with the previous images. Is installing xf86-video-fbturbo-git enough? how would be the procedure to do that? Thank you.

[Shjim]

Congrats on Maintainer/Dev for ARM i3 edition … it very nicely setup and run smooth on Pinebook Pro.
shame no Gnome edition…

[Janne]

Yes. Just install that package, then reboot. That’s all.

I would like a (non-KDE) desktop without this issue. Does anyone know if Wayland and Sway works smoothly with the Panfrost driver?