Plasma Mobile "stable" currently broken

[acrux]

Today's Plasma Mobile image Manjaro-ARM-plasma-mobile-pinephone-20210610.img does not boot past KDE logo with mouse cursor.
Also - when you update your current working setup to todays latest software, then the result is the same - KDE logo with mouse cursor.
So - be warned
Ironically - Plasma Mobile Dev image boots OK 

[mouffa]

The same thing happens if you apply the updates from previous images.

I connected a keyboard through the dock and I saved the `dmesg`, I should have a look at the Journal too, I will do it later.

I think the suspicious output is the following

Code:

[    9.355294] WARNING: CPU: 1 PID: 3435 at net/wireless/core.c:902 wiphy_register+0x95c/0x980 [cfg80211]
[    9.355373] Modules linked in: 8723cs(C+) ov5640 hci_uart btrtl btbcm bluetooth cfg80211 crct10dif_ce st_magn_spi st_sensors_spi st_magn_i2c st_magn sun50i_codec_analog ecdh_generic st_sensors_i2c inv_mpu6050_i2c sun8i_adda_pr_regmap ecc st_sensors inv_mpu6050 stk3310 rfkill industrialio_triggered_buffer anx7688 kfifo_buf sun4i_lradc_keys panel_sitronix_st7703 sun8i_codec sun4i_i2s snd_soc_ec25 snd_soc_simple_amplifier snd_soc_simple_card snd_soc_bt_sco snd_soc_simple_card_utils snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer snd i2c_gpio display_connector soundcore leds_sgm3140
[    9.355518] CPU: 1 PID: 3435 Comm: systemd-udevd Tainted: G         C        5.12.9-1-MANJARO-ARM #1
[    9.355528] Hardware name: Pine64 PinePhone (1.2) (DT)
[    9.355533] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--)
[    9.355541] pc : wiphy_register+0x95c/0x980 [cfg80211]
[    9.355569] lr : rtw_cfg80211_dev_res_register+0x2c/0x44 [8723cs]
[    9.356020] sp : ffff800012163790
[    9.356024] x29: ffff800012163790 x28: 0000000000000013
[    9.356034] x27: 0000000000000100 x26: ffff8000112afb40
[    9.356043] x25: ffff80001013b890 x24: 0000000000000051
[    9.356053] x23: ffff800011705000 x22: ffff0000028d5800
[    9.356062] x21: ffff000005268dc0 x20: ffff000002978000
[    9.356072] x19: ffff000002978300 x18: 0000000000000020
[    9.356081] x17: ffff800008f4dcf0 x16: ffff800011720013
[    9.356090] x15: ffff0000052691b8 x14: 0000000000000000
[    9.356099] x13: ffff000005268dc0 x12: ffff000003b30b14
[    9.356108] x11: 0000000000000010 x10: 00000000ffffffbd
[    9.356117] x9 : ffff800008db2bc0 x8 : ffff000002978438
[    9.356127] x7 : 000000007fffffff x6 : 0000000000000005
[    9.356136] x5 : 0000000000000004 x4 : ffff800008f4bc18
[    9.356145] x3 : ffff800008ee9f70 x2 : 0000000000000000
[    9.356154] x1 : 0000000000000000 x0 : 0000000000000000
[    9.356164] Call trace:
[    9.356169]  wiphy_register+0x95c/0x980 [cfg80211]
[    9.356204]  rtw_cfg80211_dev_res_register+0x2c/0x44 [8723cs]
[    9.356472]  rtw_os_ndevs_register+0x24/0x120 [8723cs]
[    9.356700]  rtw_os_ndevs_init+0x3c/0x60 [8723cs]
[    9.356926]  rtw_drv_init+0xcc/0x27c [8723cs]
[    9.357152]  sdio_bus_probe+0xe8/0x1cc
[    9.357168]  really_probe+0xe4/0x4c0
[    9.357182]  driver_probe_device+0x58/0xc0
[    9.357191]  device_driver_attach+0xc0/0xcc
[    9.357200]  __driver_attach+0x84/0x124
[    9.357209]  bus_for_each_dev+0x70/0xc0
[    9.357218]  driver_attach+0x24/0x30
[    9.357226]  bus_add_driver+0x104/0x1ec
[    9.357235]  driver_register+0x78/0x130
[    9.357244]  sdio_register_driver+0x2c/0x40
[    9.357251]  rtw_drv_entry+0x4c/0xa0 [8723cs]
[    9.357477]  do_one_initcall+0x54/0x1bc
[    9.357489]  do_init_module+0x54/0x250
[    9.357501]  load_module+0x1f90/0x25ec
[    9.357509]  __do_sys_init_module+0x1ac/0x220
[    9.357518]  __arm64_sys_init_module+0x1c/0x30
[    9.357527]  el0_svc_common.constprop.0+0x60/0x120
[    9.357537]  do_el0_svc+0x24/0x90
[    9.357545]  el0_svc+0x2c/0x54
[    9.357555]  el0_sync_handler+0x1a4/0x1b0
[    9.357562]  el0_sync+0x180/0x1c0
[    9.357570] ---[ end trace accd80c7d9d341d7 ]---

[acrux]

Good news is that now updating the PlaMo June 10th image to latest available software results a booting system.
So probably the image was built when the plasma 5.22 update was not complete resulting a non-booting image.
Good chance is that the tomorrow image will be OK again

[mouffa]

Thanks, I repaired it in the following way,

1) Connect a keyboard with the Dock.
2) When the "K" logo stops running hit [CTRL+ALT+F3] to switch to terminal 3.
3) Log in.
4) Give the `nmtui` command to setup an internet connection.
5) `sudo pacman -Syu` to update.
6) `reboot` to reboot.

[ryo]

Thanks, I repaired it in the following way,

1) Connect a keyboard with the Dock.
2) When the "K" logo stops running hit [CTRL+ALT+F3] to switch to terminal 3.
3) Log in.
4) Give the `nmtui` command to setup an internet connection.
5) `sudo pacman -Syu` to update.
6) `reboot` to reboot.

The only thing I did differently is, instead of step 4, I connected an ethernet cable into the dock so I could skip step 4 here.
But it worked, you saved us!

Edit: one thing to keep in mind: apparently the swipe to open the app drawer changed to tap the ^ button to open the app drawer.
I just got so used to it on both PlaMo and GraphineOS, it really confused me here.
They could have used the Plasma logo for this instead, like how they're doing it on desktop for decades now.

[mouffa]

I tried the ethernet cable but for some reason on Manjaro Plasma the connection is not working though the eth0 interface is present and I have to configure it with further commands, nmtui does the job well for the wifi, on Manjaro Phosh the ethernet works automatically.

[ryo]

I tried the ethernet cable but for some reason on Manjaro Plasma the connection is not working though the eth0 interface is present and I have to configure it with further commands, nmtui does the job well for the wifi, on Manjaro Phosh the ethernet works automatically.

Really?
On Manjaro PlaMo the ethernet connection was automatic for me.

Did you by any chance plug it in after booting up?
Because I remember my keyboard didn't work when I plugged in the dock after booting, it only worked when inserting before booting.

[scott_VYuCAbn3k1NFK]

I hit the same problem on the unstable channel - seems to also be reported here (https://forum.manjaro.org/t/manjaro-arm-...ne/69318/7), but seems to be fixed now if you can upgrade.

I repaired my system differently to the two solutions given above, so thought I would share.

You need to have qemu setup to automatically run aarch64 executables (see here https://ownyourbits.com/2018/06/13/trans...nfmt_misc/). Then do the following:

1. Boot the phone into jumpdrive by flashing jumpdrive to an sd card and booting that.
2. Connect the phone to a linux laptop using the USB cable.
3. Install arch-chroot (sudo apt install arch-install-scripts on Ubuntu 20.10)
4. Mount the phone root drive (I just clicked the folder MNJRO_ROOT in nautilus / nemo)
5. cp /etc/resolve.conf /media/<username>/MNJRO_ROOT/etc/resolve.conf
6. sudo arch-chroot /media/<username>/MNJRO_ROOT
7. sudo pacman -Syyu

[mouffa]

This is useful if you don't have a dock to connect the keyboard.

[mouffa]

I checked the ethernet cable again, it is unstable, it achieves to make an internet connection for some minutes and then it is "deactivated", I won't spend any more time on this for now, I want to continue with the modem and start the development of a FrameBuffer GUI.