I have a PBP (2021 batch) and screwed up the original Manjaro KDE eMMC image with some combination of cups and display resolution mischief. I have been using Armbian successfully from a microSD card but want to fix my eMMC boot. The only image of Majaro that targets eMMC specifically is this one, but it's way out of date. I have since tried to update packages etc but am running into pretty difficult challenges getting things updated to a point where I could update the OS to a current version (namely I can't access the current mirror list). This is preventing me from using the manjaro-arm-installer package that would help update OS. Has anyone else run into this issue and solved it? Or is there another OS with a current eMMC version?

Thanks for any advice!

Audio  volume and its indicator on the screen  goes the opposite direction of  the up or down buttons when they are  pressed.   Repeating the button press eventually fixes the problem temporarily until the desired volume is reached.  Do you have this problem?

Hello i got a problem with root password, any defult passwords doesnt works, can anyone give me working password?

i have the software application running that states there are updates. but it just does not install any of them. when i click on "install" or "upgrade" or what that button shows, it shortly says "cancel" and thats it, nothing else happens.
i thought i could do that manually with a terminal like apk update, but i dont have any root password

so how can i install updates without all the time reinstalling the complete OS?

For 2 years I’ve been running Debian 10 Buster on my PBP, installed, with encryption, on the eMMC with Daniel Thompson’s awesome installer (thank you Daniel!!). The PBP is my daily driver.

Last week I tried upgrading to Debian 11 Bullseye following the instructions on the Debian website (https://www.debian.org/releases/bullseye...de-process). All seemed to go smoothly until it came to rebooting, which unfortunately only produced a green power LED and a black screen.

I tried installing Tow-Boot, hoping I could salvage something with that or otherwise do a clean install of Debian 11. Unfortunately booting from the Tow-Boot installer SD card fails in the same way: Only the power LED lights, otherwise nothing happens. I tried 2 different SD cards (both Kingston 32 GB Class 10 U1 though) and wrote the spi.installer.img to the cards using both dd and the disks utility.

I can boot Bullseye from a similar SD (previously created with Daniel Thompsons installer) though.

I recorded the upgrade with “script” as per 4.4.1 in the Debian upgrade instructions but don’t really know what to look for.

I’ve been a linux user for around 15 years, happy to use the command line for simple things and to fix problems with instructions found online but otherwise very much a GUI person. I can’t really find any information relating to my 2 problems so I’m more than a bit out of my depth here.

Is there anyone with an idea what I’m doing wrong?

My Pinephone (convergence) has horizontal pinstripe lines throughout the screen. I suspect it has to do with the resolution being set at 360x720. I can't find an xrandr mode that will let it be set at 720x1440.

I'm running Manjaro Phosh.

In case this has anything to do with the problem, I do not have a ~/.monitors.xml or ~/.config/monitors.xml file. If it's supposed to be there, it's gone.

Thanks.

Was trying to use Spot to listen to my music, and for the longest time I thought there was some sort of driver issue... Wasn't really sure, but the audio would get really choppy and laggy whenever I tried to play on the speaker, so I just assumed that something (library, pipewire, IDK...) was broke, but the choppiness seemed to by a CPU thing, so I got the serendipitous idea to check it at low volume, and what do ya know, it works great! So I am not sure if there are still fixes for this coming down the pipe, but to anyone who might be in my position and think it is broke, it isn't! Just the speaker seemingly draws too much current from the CPU.

In trying to use Geary on manjaro or arch -- last week it worked fine on both -- it demands a keyring password.  I type in my root password or my gmail password but neither works and my inbox won't update. I have renamed .local/share/keyring/Default_keyring.keyring but it didnt help. I also used sudo pacman-key --init and --populate but that didn't help either. I deleted and reinstalled Geary but the reinstalled version immediately knew to use my Gmail account and didn't update. I have recently installed towboot but haven't done anything else significant. 

Advice?

Hello!
I'm from Kiev (Ukraine).
I want to buy Pine64 Pro.
The shipping options doesn't have "Ukraine" at the countries list at the store. Is that an mistake? Or you do not deliver goods to Ukraine?

Thanks

I've followed the instructions at the wiki on setting up mobile data, and it works fine, except that it really kills the battery. Every time the phone boots it auto-enables any connections it can, which means to prevent the phone from automatically overheating and dying after a few hours in my pocket I need to remember to manually turn data off.

Is there a way to configure the modem connection with nmcli to keep it from turning on automatically, or should I just have a script run a few minutes after boot to turn it off?
The second option seems kinda hacky to me so I'd rather avoid it, but I'm using sxmo so I might as well embrace the way of the bash scripts...