A way to view or log the splash screen on Pinephone Pro running ArchLinux (Danctnix)

[PHLEMON]

Good day!

I've been using Pinephone Pro as a daily driver for 7 months now. Mainly with Arch Linux Danctnix OS. Recently, I'm having problems with connecting to the wifi. It can scan available SSIDs but could not connect after a 90 second timeout.

I've tried manually connecting the wifi via nmcli, manually installing the firmware for brcmfmac from github repos and rebuilding the initramfs. But it doesn't seem to fix my problem.

I'm thinking whether this is a hardware problem (given that I charge it with a 5v:3000ma charger overnight) or a software problem (since I usually update with yay first then sudo pacman -Syu. The updates could've messed with the firmware.)

SInce I use the phone almost always for online activities, I can't use it and I usually reboot it often following the wifi connectivity error. While doing so, I read something in the splash screen at boot-time stating something along the lines of "Failed to read chip id 258" Hopefully anyone here could point me to a way to log or view the messages at the splash screen, or a more appropriate forum or discussion board to bring up my concern.

Help a bro out, links or advice would be greatly appreciated.

[mikehenson]

Help a bro out, links or advice would be greatly appreciated.

Thank you for providing OS. 

I currently have no issues connecting to WiFi or creating a hot spot for my laptop. 

I do remember a long time ago that I got duplicate connections on nmcli that were stepping on one another.

run command 

Code:

nmcli connection show

Device: PinePhonePro (Daily driver)
OS: DanctNIX Arch with Phosh

[PHLEMON]

I do remember a long time ago that I got duplicate connections on nmcli that were stepping on one another.

run command 

Code:

nmcli connection show

Thanks for this man, was able to see the different UUIDs for each saved networks. However, nothing appeared as duplicates even after 'nmcli con delete UUID' and reconnecting. 

I was able to view the splash screen by crudely taking a video of my PPP at boot-up using my other phone. The error showed up to be "ov8850 1-0036: Failed to read reg 208906: -6" "Probe with driver: driver imx258 failed with error -5. or failed to read chip id 258" both ov8850 and imx258 turns out to be the driver for the camera modules of the PPP which is unrelated to my concern. 

I think these logs would be relevant: 
Upon "sudo dmesg | grep -i sdio" 
Output: 
[ 6.653028] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.pine64,pinephone-pro.bin failed with error -2

Upon "sudo journalctl -u NetworkManager -f"
Output: 
Jul 29 01:54:28 danctnix NetworkManager[3797]: <info> [1722189268.9366] device (wlan0): supplicant interface state: scanning -> associating 
Jul 29 01:54:28 danctnix NetworkManager[3797]: <info> [1722189268.9368] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating 
Jul 29 01:54:29 danctnix NetworkManager[3797]: <info> [1722189269.0558] device (wlan0): supplicant interface state: associating -> disconnected 
Jul 29 01:54:29 danctnix NetworkManager[3797]: <info> [1722189269.0561] device (p2p-dev-wlan0): supplicant management interface state: associating -> disconnected 
Jul 29 01:54:29 danctnix NetworkManager[3797]: <warn> [1722189269.4720] device (wlan0): Activation: (wifi) association took too long 
Jul 29 01:54:29 danctnix NetworkManager[3797]: <info> [1722189269.4723] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') 
Jul 29 01:54:29 danctnix NetworkManager[3797]: <warn> [1722189269.4747] device (wlan0): Activation: (wifi) asking for new secrets

Upon "sudo dmesg | grep -i brcmfmac"
Output: 
[ 7.041425] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 
[ 7.082935] usbcore: registered new interface driver brcmfmac [ 7.236643] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) 
[ 7.238651] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Apr 15 2021 03:03:20 version 7.45.234 (4ca95bb CY) FWID 01-996384e2 
[ 12.117766] brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 
[ 12.126424] brcmfmac: brcmf_set_channel: set chanspec 0x100d fail, reason -52 
[ 12.135012] brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
and so on... repeating the "chanspec fail, reason -52"

Upon "sudo modprobe -r brcmfmac && sudo modprobe brcmfmac"
Output: 
modprobe: FATAL: Module brcmfmac is in use.

I'll try looking for other solutions specifically on chanspec reason -52 (Although I don't see this issue happening on PPP but on Raspberry Pis)

Hopefully you know something about this. But if all fails, I might go reinstalling the OS.

[mikehenson]

Hopefully you know something about this. But if all fails, I might go reinstalling the OS.[/size][/color]

I just did a full update of arch (2024 July 30) and I got the same issue as you.
Downgrading wpa_supplicant to 2.10 and restarting the phone worked for me

From another post, some said to downgrade the wpa_supplicant package. 
wpa_supplicant was just updated on July 20[1] to 2:2.11
you can download wpa_supplicant 2:2.10 here[2]

if you are lazy, here are the commands you will need to run on the phone.

Code:

cd Downloads
wget http://tardis.tiny-vps.com/aarm/repos/2024/06/11/aarch64/core/wpa_supplicant-2%3A2.10-8-aarch64.pkg.tar.xz
wget http://tardis.tiny-vps.com/aarm/repos/2024/06/11/aarch64/core/wpa_supplicant-2%3A2.10-8-aarch64.pkg.tar.xz.sig
sudo pacman -U wpa_supplicant-2\:2.10-8-aarch64.pkg.tar.xz
sudo reboot

[1] https://w1.fi/releases/
[2] http://tardis.tiny-vps.com/aarm/repos/20...ch64/core/

**THIS MAY NOT BE THE CORRECT FIX**

[PHLEMON]

I just did a full update of arch (2024 July 30) and I got the same issue as you.
Downgrading wpa_supplicant to 2.10 and restarting the phone worked for me

Issue solved, thank you for your time, sir! 

This saved me a lot of hassle. I will consider downgrading software packages the next time I encounter a similar issue.