Is there any way to get S3 suspend working on the latest Manjaro? That's really the only thing holding it back from being perfect at the moment (other than needing to downgrade the wifi firmware package).
(06-16-2020, 08:31 PM)PRStoetzer Wrote: Is there any way to get S3 suspend working on the latest Manjaro? That's really the only thing holding it back from being perfect at the moment (other than needing to downgrade the wifi firmware package).
Yes you will have to flash bsp uboot and then the S3 suspend will work fine.
Install the package using this command and then follow the instruction.
Code:
sudo pacman -S uboot-pinebookpro-bsp
Do not do this if you don't have experience with uboot or basic dd linux commands.
Manjaro ARM Team.
Devices: Pinebook Pro & PinePhone.
Is there a way to set the default screen brightness for with the machine powers on?
I'm running stock Manjaro Arm 20.04 with all current updates. I love the PBP, but my only real papercut issue is that the screen is really low brightness every time I turn it on. Obviously I can just change it with the keyboard, but it'd be nice if the brightness just defaulted brighter. Is there a way I can change this default value?
Thanks
(06-19-2020, 09:05 AM)theplaidtieninja Wrote: Is there a way to set the default screen brightness for with the machine powers on?
I'm running stock Manjaro Arm 20.04 with all current updates. I love the PBP, but my only real papercut issue is that the screen is really low brightness every time I turn it on. Obviously I can just change it with the keyboard, but it'd be nice if the brightness just defaulted brighter. Is there a way I can change this default value?
Thanks
Yes you can.
Open Energy Saver application from start menu.
There you will see Brightness Level increase as per your convenient and press apply. from next boot it will follow this setting.
Good Luck
Manjaro ARM Team.
Devices: Pinebook Pro & PinePhone.
So I'm having an issue with the WiFi that I'm fairly sure is NOT related to the kill switch. Or at least not in the way others have experienced it. To clarify - I have made sure that the killswitch is in the off position (2 blinks) and rebooted, and also tested with the reverse (3 blinks) to make sure there was no issue here.
Issue: It randomly disconnects while working, and cannot reconnect even with reboots + cycling the kill switch.
The odd thing is that it shows WiFi networks in the area, and attempts to connect them, but cannot do so successfully.
It is resolved by reinstalling the OS, so seems like its software related. Has happened to me so far on the factory Manjaro KDE that it shipped with, and with Manjaro i3 ARM 20.04
One time it happened without any input from myself (saw it disconnect sitting on my desk while working on my primary), another it happened while doing something unrelated in vim.
When I run inxi -Fxz, I get the same "No ARM data found for this feature" that happens with the kill switch issue.
Looking at journalctl -u NetworkManager, I see:
dhcp4 (wlan): request timed out
device (wlan0): state change: ip-config -> failed (reason ip-config-unavailable, sys-iface-state: 'managed')
manager: NetworkManager state is now DISCONNECTED
platform-linux: do-change-link[2]: failure changing link: failure 52 (invalid exchange)
device (wlan0) set-hw-addr: failed to set MAC address to [MAC here] (scanning) (NME_UNSPEC)
device (wlan0) Activation failed for connection "Homelab"
Restarting the service with systemctl restart NetworkManager.service doesn't work either.
Any idea what could be causing this?
Wanted to chime back in that the issue seems to come and go for me, so it might be hardware related! It came back this morning before cutting out again this afternoon. This time, however, restarting NetworkManager worked.
Will monitor the issue over the coming week(s).