Manjaro ARM 19.12 Official Release - PineBook Pro

[pjsf]

For someone else who got stuck and can't update with the DE being broken (can't login, connect to wifi, etc):

Ah okay, so it's not only me. I also got the mismatched libraries (mix of already upgraded KDE 5.64 and not yet available packages stuck at 5.63 with outdated libraries and missing C++ symbols) with unable to re-log into KDE.
As I'm new to ArchLinux, I tough I did something wrong with pacman.

If not, copy /etc/udev/hwdb.d/10-usb-kbd.hwdb from the default debian system to the same location of your Manjaro SD.

Haven't even noticed the missing brightness key. The hwdb.d entry indeed helped.

@chzbacon not a bug but a feature more seriously tho, WiFi is using the SDIO interface - it itsn't plug-and-play like USB 2.0 - so once you cut power to it, you'll need to reboot so the kernel 'sees' it on boot.

Any chance to finding a way to manually force restarting the Wifi?
e.g: manually rmmod + modprobe again ?

After-all some SDIO interfaces are supposed to support some plug-and-play capabilities: I certainly remember hot-pluggin a SDIO Wifi card into the SD slot of my older PalmOS PDAs.

---

{...} more seriously tho, WiFi is using the SDIO interface - it itsn't plug-and-play like USB 2.0

Any chance to finding a way to manually force restarting the Wifi?
e.g: manually rmmod + modprobe again ?

After-all some SDIO interfaces are supposed to support some plug-and-play capabilities{...}

Okay, I got it.

First, trying to to just rmmod doesn't work:

Code:

$ sudo rmmod brcmfmac brcmutil cfg80211
$ modprobe brcmfmac
$ dmesg
[ 1299.511038] usbcore: deregistering interface driver brcmfmac
[ 1313.114017] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 1313.114781] cfg80211: failed to load regulatory.db
[ 1313.132537] brcmfmac: probe of mmc0:0001:1 failed with error -110
[ 1313.133192] brcmfmac: probe of mmc0:0001:2 failed with error -110
[ 1313.133865] usbcore: registered new interface driver brcmfmac

But, after finding other people with similar problems of MMC module soldered on the motherboard that need manual restart but can't be physically unplugged, the following thing forced a restart of the Wifi (without reboot):

Code:

$ ls -d /sys/devices/platform/*.dwmmc/mmc_host/mmc0
/sys/devices/platform/fe310000.dwmmc/mmc_host/mmc0
$ echo 'fe310000.dwmmc' | sudo tee /sys/bus/platform/drivers/dwmmc_rockchip/unbind
$ echo 'fe310000.dwmmc' | sudo tee /sys/bus/platform/drivers/dwmmc_rockchip/bind
$ dmesg
[ 1845.593897] mmc0: card 0001 removed
[ 1849.712047] dwmmc_rockchip fe310000.dwmmc: IDMAC supports 32-bit address mode.
[ 1849.712707] dwmmc_rockchip fe310000.dwmmc: Using internal DMA controller.
[ 1849.713307] dwmmc_rockchip fe310000.dwmmc: Version ID is 270a
[ 1849.713840] dwmmc_rockchip fe310000.dwmmc: DW MMC controller at irq 27,32 bit host data width,256 deep fifo
[ 1849.714799] dwmmc_rockchip fe310000.dwmmc: allocated mmc-pwrseq
[ 1849.715321] mmc_host mmc0: card is non-removable.
[ 1849.728861] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[ 1849.777673] mmc_host mmc0: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0)
[ 1850.622467] dwmmc_rockchip fe310000.dwmmc: Successfully tuned phase to 47
[ 1850.627007] mmc0: new ultra high speed SDR104 SDIO card at address 0001
[ 1850.636215] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 1852.731997] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 1852.732808] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 1852.734049] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Sep  7 2018 14:33:37 version 7.45.96.27 (42b546f@shgit) (r) FWID 01-c958c084 es7.c5.n4.a3
[ 1860.053215] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Tada! Reboot-less restart of Wifi achieved!

Ideally, it would be great if the embed-controller firmware could be modified, so that not only does it shut-down the power to the Wifi chip, but it also sends an even to Linux (simulate soft "Wifi switch" key presses ?)
so that Linux could in turn unbind or rebind the SDIO accordingly on its side of things.

The bonus point:
- this would also make a quite quick hack for the people having troubles with Wifi. If the broadcom starts to behave and crash, just hit "Pine64 logo"+"F11" twice in a row to restart the damn thing thanks to the privacy switches !

---

The bonus point:
- this would also make a quite quick hack for the people having troubles with Wifi. If the broadcom starts to behave and crash, just hit "Pine64 logo"+"F11" twice in a row to restart the damn thing thanks to the privacy switches !

Irony - level : over 9000!

Exactly when I was posting this, my Broadcom crashed and lost wifi.
And I did exactly perform the unbind/bind sequence to recover network and to get Firefox to successfully finish the "FORM POST" of the above post.

So now we definitely need somebody fluent in the EC to upgrade the firmware, and somebody fluent in the event handling to do map the bind/unbind to the simulated "Soft Wifi switch" keypresses.

---

And with that I have a good presentation machine for work. Yay!

Thanks for that , it got it going again. One thing I did notice is that after reloading like this the adapter can't see my 5ghz network, only the 2.4ghz. I also had a problem on initial boot of both Manjaro and the factory installed Debian that although it could see the 5ghz network the first connection attempt would hang, then work on subsequent attempts, so maybe some firmware issue with the 5ghz support?

Update: ... and after a few minutes the 5ghz networks become visible again!