Hi Team.

I posted to a prior thread about this but nobody is answering, so I guess it can't hurt to do a new thread. It has happened now on identical brand new boards, new EMMCs, also on SD, identical 5a factory PSU, factory heatsink.

OS is Armbian, and it has happened on current desktop and server. This last time I had completed several successful reboots and thought maybe I just hadn't been pushing the plug in all the way. Then it happened again.

The behavior is while the board is running, white light flashing, system munching it just dies. Throws no errors. Just quits. Green light never goes out.

  I was tailing the emby log when it crashed this time.  No errors at all. Prior times it did not successfully reboot, but this one seems to be ok on reboot.

As I have been running Armbian for over 5 years on dozens of boards, this is not an Armbian problem, despite customer service at Pine claiming that this is a software issue. I have followed this exact same process on boards from Rpi2 and Opi PC to other RK3399 boards like NanoM4v2.  Not one has failed.

I am writing a book on NAS options, so this is really relevant to the RP64. I personally bought two boards and NAS boxes and the card and everything.  Something is going on, and it is for sure hardware related.  This last crash was using an EMMC I got from Hardkernel years ago, and was unused.

The pastebin is here:
https://paste.armbian.com/zikixujaho


Here is the syslog:

Apr 28 10:17:45 rockpro64 systemd-resolved[795]: Clock change detected. Flushing caches.
Apr 28 10:17:45 rockpro64 chronyd[1120]: System clock was stepped by 3624.542409 seconds
Apr 28 10:17:45 rockpro64 chronyd[1120]: System clock TAI offset set to 37 seconds
Apr 28 10:17:46 rockpro64 vnstatd[1094]: Info: Latest database update is no longer in the future (db: 2023-04-28 10:05:00 <= now: 2023-04-28 10:17:46), continuing.
Apr 28 10:17:48 rockpro64 systemd[1]: Starting system activity accounting tool...
Apr 28 10:17:48 rockpro64 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Apr 28 10:17:48 rockpro64 systemd[1]: sysstat-collect.service: Deactivated successfully.

hardware log:

Time    CPU_cl0/CPU_cl1  load %cpu %sys %usr %nice %io %irq  Tcpu  C.St.
09:17:07  1416/1800 MHz  1.83  38%  21%  11%  0%  4%  0%  43.3 °C  0/5
09:17:08  1416/1800 MHz  1.83  39%  6%  28%  0%  4%  0%  42.8 °C  0/5
09:17:08  600/1800 MHz  1.83  39%  4%  31%  1%  1%  0%  43.3 °C  0/5
09:17:08  600/1800 MHz  1.83  40%  5%  31%  1%  2%  0%  42.8 °C  0/5
09:17:09  1416/1800 MHz  1.83  42%  9%  25%  0%  6%  0%  43.9 °C  0/5



Apr 28 10:17:48 rockpro64 systemd[1]: Finished system activity accounting tool.
Apr 28 10:18:01 rockpro64 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Apr 28 10:18:51 rockpro64 chronyd[1120]: Selected source 108.61.73.244 (0.ubuntu.pool.ntp.org)

So, the audio pops on the pinebook pro are nothing new.  What I'm wondering is if any sort of improvements the es8316 driver could solve the problem in theory.  My hope is that someone can tell me if this is something that could plausibly be done.  (I'm interested in at least poking it myself but I've never poked the kernel too much before so me investigating it is going to take a while and maybe someone can answer if I'm wasting my time)

Has anyone tried booting a SOQuartz CM installed on a Blade using PXE? I am looking to build a small HA setup using these, but I'd really like to be able to use PXE to make upgrades and management less painful

Anyone else seeing stability problems with their Pinephone running Mobian and the 6.1 kernel? I'm finding that with 6.1 the phone experiences frequent random crashes, spontaneous reboots, and user interface lockups. On the other hand the phone is very stable if reverted back to the 5.15 kernel. I'm not sure if it's a hardware issue with this particular phone or if maybe the 6.1 kernel is not quite fully-baked yet for this platform. (I've been retrying 6.1 each time it's updated but so far it just won't run reliably.)

Hi everyone. Bought a PBP a couple of months ago that because useless out of the box. First it arrived with a broken screen. Was sent a replacement and got it booted. Performed updates and had the black screen issue. Failed at fixing that for some time. Recently tried to get Kali on it which would be extremely useful for me. I have it booting from the SD. But it looks like I deleted a partition from my eMMC and I can't figure anything out. I'm fairly tech savy but I just can't wrap my head around getting the eMMC built back up. Is there a guide available for zeroing out the eMMC and starting from scratch? I'd appreciate any help. I have scoured the forums and tried various things but haven't been successful and/or haven't found what I needed. It'll probably just go in a drawer until I decide to get rid of it unless I can find this help.

Thanks so much for any guidance you can provide.

Hi!

I just purchased a Pinecil and an additional tip. Since the original package of the pinecil is really fine, I was wondering if I could put the additional tip also into the package for safe storage. Since the package has plenty of free space, I cut out the place for the additional tip.

My suggestion: Why not providing the original package with 3 cutouts for the tips, also if only one tip is included? This would be really useful for safely storing all together.

See image included:

Hi all - hoping someone may be able to shed some light into a solution.  I have a Pinephone Pro connected to an Anker 6-in-1 usb hub.  Intermittent power is being provided through the anker hub.  It will be set up in a remote location to collect some weather data and powered by solar.  My goal is to have the pinephone shut itself down when the battery gets under 50%, then boot back up when power is applied.


The problem: A script can successfully tell the phone to shut down at the specified battery percentage, but the phone will instantaneously reboots as soon as the shutdown process is complete.  This happens when no power is present, but the hub is still plugged in.  I expect this when power is available, but it is a problem that it happens when power is absent as I need the device to shut down to conserve power for bootup.  This seems to happens when any device is plugged into the phone (flash drive, FTDI chip, pinehub, etc).


My theory is that the RK818 PMIC chip is misconfigured and is recognizing the phone's own OTG power as if it were power being passed in.  This then initiates the boot cycle.  Does this make sense?  Can anybody explain what is happening here, and any resolution?  I've seen some threads about a similar issue noted with the keyboard, but none with a resolution to this issue.


I've tried:

  - Mobian, Manjaro, and PostmarketOS and the behavior is consistent across all three.
  - Shutting down OTG power in mobian manually.  Peripherals shut down, but the phone still reboots after shutdown
  - Every type of cable known to humanity between the phone and the hub

I'm not certain of the name or directory for Phosh's custom keystrokes. Can anyone help to track down its location?

Thanks.

Hello everyone,

I posted this also on the Fedora forum, see here

I own a Pinephone 64 formerly with PostmarketOS and SXMO installed. I was happy when I read about Fedora Phosh 38 being available so I wanted to install it on my Pinephone. I downloaded the Fedora-Phosh-38-1.6.aarch64.raw.xz file from Fedora Phosh | The Fedora Project. Checksums did match, hence the file didn’t seem to be corrupted or anything. I connected and rebooted my Pinephone (which has TowBoot installed) and tried to write the downloaded file with Balena Etcher onto the eMMC. This left me with the message “Attention Something went wrong. If it is a compressed image, please check that the archive is not corrupted. The elevated process died unexpectedly”.

I then remembered that openSUSE also comes with a raw.xz image, so I checked out their install process, see HCLinePhone - openSUSE Wiki , and it seemed straight forward. I used

Hi,

I recently turned my Pinephone back on with a SIM inserted - it had been last used in 4G mode only for VoLTE test purposes with mobile data off.
This time mobile data was on - I had to disable the still incorrect aeroplane mode - this turned on bluetooth - and I could then access the mobile data setting to turn it off.

I ran updates and rebooted and the same thing happened, the phone restarted with 4G data back on whereas data had been turned off before restarting it.

How come this has changed? How do I disable data at startup? Why are the settings prior to restart / reboot not preserved?

Can't believe the aeroplane mode bug is still present too....

I could find nothing on https://salsa.debian.org/groups/Mobian-team/-/issues
or https://source.puri.sm/Librem5/phosh/-/issues

Curious as to whether or not anyone else has noticed this.

Thanks for your help / feedback.