NemoMobile made progress on the Weather app, Qt *.prf file compilation issues, and device orientation functionality. NemoMobile was also featured in a Lightning talk at the LinuxAppSummit conference.

https://fosstodon.org/@jmlich/110286687938101438

Hi guys,

I'm using Debian from years and years and I'd like to do install it also on my Pine Phone Pro.

I did it but there's Posh desktop and I'd like to use Plasma Mobile, I followed a lot of guides but I'm not able to replace Posh with Plasma!

Should I recompile the kernel?

GabrieleMax

I have an older Pine64 build (2016 from the original Kickstarter.) I have an image for it of Ubuntu 16.04 that functions with a touchscreen (NOTE: Just Ubuntu with KDE desktop. Not Pinephone, or Pinetablet.) the Ubuntu 16 is struggling to install my wireless USB dongle. I honestly have no idea where I got the image. I don't recall configuring it myself. I think I found it as an existing downloadable IMG file. 

QUESTION: Is there an Ubuntu 18 or 20 image for this Pine64, that also works with the touchscreen out of the box? 

Alternative: Or instructions for installing Ubuntu 18/20 including configuring the touchscreen?

Thanks!
 

hi,

What happend to openbsd/krjdev?


any working builds 2023 or any instructions?

thank you

My old Pinebook Pro wouldn't boot (it tried, but reported boot error messages and hung). It has no eMMC in the laptop at all (removed long ago), but I used to boot Manjaro from the SD card.

I flashed Manjaro ARM Generic to the SD. No boot at all (no power lights, no response).

I flashed Tow-boot to the Pinebook's SPI from the SD card. This booted, and the flash was successful.

I flashed Manjaro ARM Generic back to the SD card, but it does not boot. No power light.

I flashed the old Manjaro image for the PBP to the SD card, but that does not boot.

I re-flashed Towboot to the SD card. That boots!

Edit: I ended up using Towboot to erase the SPI, and then reflashed Towboot to the SPI. That gave me the Towboot boot menu. I think we're onto something here!

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.