a few issues popped up after last nights updates.
1. sxmo_setpinebacklight segfults unless it is run with sudo, therefore adjustong brightness with the config menu or in xinitrc fails and just displays the default brightness of 750.
2. suspend and lock (screen off) both turn off the screen for a second or so and then turn it back on. it appears that suspend is completely broken

this is all ive noticed so far but its been a busy work week

Was running nextCloudPi on Armbian 21.02.1 stable, headless. Board: v3 w/ 4G
No issue for over a couple of months, 5A power, htop would indicate temps in the 36-45 range.

Today (2021-02-09) Installed the Armbian configuration utility and conducted an update on the board firmware.
Currently unable to complete a boot of the OS.
It appears to be having issues sometime after starting the Network manager.

A failure is flagged when attempting to start the network interfaces.

After either the starting of the Network Manager or the Setup of the zram based device zram2 messages similar to the following are generated:
BUG: spinlock suspected on CPU#0, armbian-hardwar/667
BUG: spinlock suspected on CPU#2, ln/670
    lock: 0xffffffc0fec1c0, .magic: dead4ead, .owner: <none/-1, . .owner_cpu: -1
BUG: spinlock suspected on CPU#3, ln/679
    lock: 0xffffffc0fec1c0, .magic: dead4ead, .owner: <none/-1, . .owner_cpu: -1
    lock: 0xffffffc0fec1c0, .magic: dead4ead, .owner: <none/-1, . .owner_cpu: -1
BUG: spinlock suspected on CPU#1, migration/1/12
    lock: 0xffffffc0fec1c0, .magic: dead4ead, .owner: <none/-1, . .owner_cpu: -1

Then it locks up...

Any suggestion or guidance would be appreciated.

Hey all,

I've got a pretty rough python3 script that I'm working on right now. It takes SMS and MMS messages from the PinePhone (Tested on PMos and Mobian) and bridges them to a Matrix server.

for SMSes I talk directly to Modem Manager via the dbus and MMSes require mmsd from kop316 https://forum.pine64.org/showthread.php?tid=12491


I've uninstalled chatty on my testing device as it also interacts directly with the modem.I did this because i think it'll cause problems if its running at the same time. I'm still pretty new to programming and definitely not a developer. Just a Linux admin who hates using his cellphone when I'm already at a keyboard. So far no one else has written anything so I have to.

If you're interested in helping me please let me know! I'd love to get someone who has experience to make this better.

Cheers!

Ohai.

Have you ever had a broken display manager and were annoyed by the fact that the cable to the external keyboard interferes with standing up your Pinephone upright or even lay perpendicular to the keyboard so you can read without holding your head in an uncomfortable position?

Not anymore! Just do this as root:

Hello everyone.

As in the pjsf thread (below), my Pinetab has a misfortune, he has a WiFi and Bluetooth radio. Is there or will there be a possibility of purchasing spare parts? It can be the radio module itself or the entire motherboard. I can replace it, but without the parts, I can't do anything.

Hi all,

            after running well for 25 days more or less, my rockpro64 is unusable. All USB ports and ethernet port are not working. I tried with many images, Manjaro, armbian... to top it all sometimes the startup finish with a kernel panic message.

I'm pretty sure that this is a hardware failure. Has anyone a similar experience? I'm very disgusted, the rockpro64 only ran for 25 days more or less. I have had others SBC, like raspberry pi, in the same place for years without problems. 

I have my new PinePhone Plasma for a short time. I was trying out multi-distro demo image.
I liked the feel of Mobian and I have some experience with Debian.
I did an apt-get dist-upgrade. It worked but after that I get a message, No WWAN Adapter Found.
I do not know how get back the WWAN Adapter and I have not anyone else with this.
Thank you for any help.
Silas

Hello All,

I have a Pinebook Pro running factory Manjaro. Every single time I reboot the system, the brightness is reset to 40%. I have to use the Fn+F2 key to manually adjust the brightness to 70%.

Does anyone have a solution so that the display brightness will be set at 70% every single time the system is started?

I searched online for hours. I didn't find a solution that works.

Thanks

Hi all,

When I got my pinecil, I powered it up to verify it works - it was on for less than a minute.  When I tried to use it tonight, it's completely dead.  It doesn't do anything when power is applied via barrel plug nor USB C.  Went to look into reporting to support, and the link from the page Warranty Policy - PINE STORE (pine64.com) goes to https://support.pine64.org/  - which gives a security cert warning.  Unsure how else to get ahold of Pine support.

I think I may know what the issue is - my power supply is set to 24 volts, which is what I've used with my TS100, and RC charging rig forever.  I've seen several places that say that the barrel plug can take 24v, but others that say 20v or 21v.    The wiki - Pinecil - PINE64 even says "Recommend operating voltage 12-21V, maximum rating at 24V"  right below "12V- 24V DC5525 Barrel Jack"

Anyway - did I overvolt and burn it up?  What specifically would i have burned (didn't open it up yet to look). Repairable?

I know that coherent_pool is a Linux kernel command line parameter, and it "sets the size of memory pool for coherent, atomic DMA allocations". I know it is specific to ARM ISA. I know it is set to 1M (1MiB) in bootloader config in Danielt's unofficial Debian installer script, and likely in most other Linux images/installers for PBP. I know in-kernel it defaults to 256KiB. I know (both from own experience and from some experienced Linux systems engineers) that various "performance tweaks" often times at best give marginal improvements or have a placebo effect, at worst can compromise system performance or stability or both. But at least for tweaks like vm.swappiness or the likes there are pretty clear consequences of changing their value either way. Even CMA (Contiguous Memory Allocator) has reasonably clear consequences of tweaking the value - too little and your device drivers for e.g. webcam may be unable to allocate enough RAM to work properly, too much is just pointless though shouldn't hurt your system (in practice it appears to be "eating" into memory usable by normal applications - e.g. when I experimented with very high CMA numbers my applications at some point started OOMing).

What I'm still puzzled by though through and through is coherent_pool - so far I have been unable to figure out what exact effect changing this value would have. It appears there is some interplay with CMA - e.g. if I set coherent_pool to 1M-8M and CMA at their default 64M things seem to work fine, if I drop CMA to 0 I easily get OOMs if coherent_pool is still set to 1M-8M, but system seems to work fine if I set coherent_pool or both to 0 (admittedly, haven't tried using webcam or any USB devices in that setup). So from that I conclude that coherent_pool actually needs CMA to work correctly, even if from https://lwn.net/Articles/479297/ it seems that CMA is a more recent development than coherent_pool. Some googling around shows that people run into some issues with certain drivers if coherent_pool is not set large enough (and especially if CMA is not enabled/large enough - one source had system complain about insufficiently big coherent_pool, and the issue was fixed by increasing CMA size instead), and some other sources claim issues if coherent_pool is set too large.

AFAIK there are some people working on kernel code around here, I am hoping that maybe some of them would know enough about kernel (as large of a knowledge area it is though) to provide some clarity on coherent_pool - what exactly is this setting for, how does it interact with CMA, why is it set by default to 256KiB if it (supposedly) frequently needs (does it?) to be tweaked to larger amounts, what is the effect of increasing or lowering its value too much?