Looks like the 128gb eMMC does not list compatibility with the RockPro64. Any reason that it can't be used, or are there known issues with it?

I've recently had the displeasure of trying to find a USB-PD charger, having to wade through numerous "fast charging" USB chargers with no indication of whether it meant USB-PD, Qualcomm QC (never mind which revision), Samsung's Adaptive Fast Charging, or any other one from the myriad of other fast charging protocols. After finally finding one, it (unsurprisingly) still didn't work with the PinePhone, probably due to the incomplete anx7688 driver.

The recent release of the PinePower and improvements of the aforementioned driver renewed my interest, however. Has anybody tried charging their PinePhone with the PinePower? Does PD work (reliably) or does it too charge at 1.5A? Which distro and kernel version were you on?

The Rock64 has a pin for I2S1 MCLK, can this pin be used to provide an external MCLK when the I2S interface is in master mode ?
If so, I could not find any register in the documentation how to enable this (Only MUX setting). Is there any info related to the external MCLK for I2S ?

Thanks,

I can't get POE to work. I tried 3 different passive POE power injectors. No sign of life

Hello,

I have this problem - I started using my Pinephone UBPorts edition with pmOS on sdcard, and it worked well enough, but I wanted it to be a bit faster so I decied to transfer to the internal eMMC storage. I wiped the UBPorts that was present here (wipefs --all) and install pmOS via pmbootstrap running on the pinephone from the sdcard. But now, text messages wont send, does not matter whether I boot from sdcard or internal memory. Modem manager cli behaves in a weird way - 

So I've had my postmarketOS device for several months now.

About two days ago, after I shut it down, it loops to a black screen after I enter my password and the postmarketOS image appears and the kernel info shows. All that is visible is the terminal cursor blinking at the top left corner. It loops until I hard reset or runs out of battery power.

I've tried attached a microSD card to the phone per other people's advice before booting but that does not address the problem.

I don't have any images to demonstrate but I would appreciate any advice to further diagnosing the issue. It will take some time and resources, however, to obtain another Linux device that could connect to the board. Perhaps the flash memory is full?

Would it be recommended to trigger the Reset button on the back?

All -
  Ordered a new pinephone the other day, and while I wait for it to be delivered, I have been looking around to determine what toolchain I need to get cross-compilation of apps going.

Could someone point me towards some documentation or helpful info on the topic?  Not looking for a handout, just a hand.  It's been a good long while since I've done any serious dev work via crosscompiling (I think the last time I touched a crosscompiler was when I was building stuff for a Compaq iPaq running Linux), and I just want to make sure I've got the right tools in place.

Hey guys.

I setup my pinebook pro with ayufan lastest gnome focal images
I installed bsp u-boot to emmc and now can be able boot os on my NVME( ayufan focal gnome).
But I can't make deep sleep or suspend working.

I checked log, it seems pinebook pro can enter deep sleep mode but there is no way to wake it up, I have to push power button for 6 sec and boot it again.

I tried some fixes and none of theme works with nvme rootfs ( it works for emmc maybe)

So anyone can get this working?

Greetings. The title says it all, sort of. I cannot get FreeBSD to boot after reboot. Gives me this error:

[*]
mountroot: waitingMounting from ufs:/dev/ufs/rootfs failed with error 19.


My system specs:

RockchModel: Pine64 RockPro64 v2.1
U-Boot TPL 2020.10 (Jan 07 2021 - 05:00:17)
FreeBSD-13.0-CURRENT-arm64-aarch64-ROCKPRO64-20210107-f2b794e1e90-255641.img.xz (Listed on this page:https://download.freebsd.org/ftp/snapsho...AGES/13.0/ )
Image uncompressed and written to eMMC module using dd

The full boot to kernel panic is posted at https://pastebin.com/BkxGCjsJ

Line 364 is where the error is printed.

The install was fresh and booted fine. The image gives you root with "root" as the password, and "generic" as the hostname. I added 2 users, changed the host name, and rebooted. Got this error several times before trying a fresh install on an SD card, then experiencing the same error on reboot. Reflashed both the SD card and eMMC module a couple of times each, did the above setup, then rebooted with the same result. According to another forum for TrueNAS other's were experiencing this and the issue was their BIOS or the newest version of BSD. You can read more about it there:

https://www.truenas.com/community/thread...-19.13620/

I am entirely new to BSD in any version but would like to start with running a headless FreeBSD on my home lab. I will take a step back and try previous versions but any help in diagnosing this, or manually booting, via the prompts would be appreciated. BSD is way over my head but this just seems like an exciting place to start. Thank you for your attention!


#############################################################################################################

UPDATE

#############################################################################################################


I switched images and found the one posted on December 24th, 2020 works even after reboot. (The image I was using was posted on January 7, 2020. I was confused and thought there was only one RockPro64 image. They have the same beginning and similar ends in the long link.

The working image: FreeBSD-13.0-CURRENT-arm64-aarch64-ROCKPRO64-20201224-3cc0c0d66a0-255241.img.xz

Hey folks, noob here. I've done as much as I can to solve this on my own because I don't want to be the user whose question is answered with "uh, there's already a comprehensive guide for that, search the forum next time", but I'm really at a loss now. I have the US layout Pinebook Pro running Manjaro with Plasma KDE pretty much exactly how it came to me. Since I'm new to Linux (currently posting from a Windows 10 desktop) and I don't have a good idea of what's causing my problem, I'm going to describe everything here as thoroughly as possible, so this post will be long.

The current problem: when I try to turn on my PBP the power LED lights up red, then turns green, and then, if I'm trying to boot normally from the eMMC, the boot logo comes up with its little progress wheel, but after about two revolutions it hangs there indefinitely. Once it freezes, everything but the power button is unresponsive. If I try to boot from my bootable SD card, I get a red LED, then a green LED, but a black screen that just stays that way.

If I boot from eMMC and I hit the keyboard shortcut before the boot logo freezes, I can switch to a virtual console, and tty2-6 work as expected - I can even switch back to tty1, where my GUI should be, but the screen stays black, sometimes with a cursor (which can move, somehow, but there's nothing to click) and sometimes without. Once or twice the frozen logo has appeared on tty1 with a movable cursor - which still can't interact with anything - but I can't figure out why it only does that sometimes, or even whether that's important.

I had my PBP for a few months as my first Linux machine, and everything was great. Then I went without using it for several weeks (just coincidentally, nothing was wrong with it), during which I mostly left it plugged in, but I had the thought that that might be bad for the battery, so I unplugged it for a while. This cycle recurred several times, so over that period, I probably left it in both states for too long, overcharging and then dying entirely. Yes, I am an idiot, thank you for asking. When I finally opened it up to use again, it froze at the boot logo like I described above.

I went through as many wiki articles, forum posts, and Reddit threads as I could stomach and found some things to try, none of which fixed the problem. Unfortunately this happened a couple weeks ago so I don't remember all the details, but they included:

-fixing my locale (which had been wrong due to my own error)
-installing updates (someone had a similar issue caused by the battery dying mid-update) including refreshing mirrors
-rolling back drivers (apparently there were issues with a recent Nvidia driver causing black screen)
-opening up the case to check eMMC switch position (it was fine) and ribbon cables (they were also fine)
-troubleshooting X11, because $xinit and $startx had returned errors, but all I could parse was something about font folders - I think I ended up reinstalling X
-updating Plasma KDE packages specifically (I had this written down but I don't recall which packages or why)

I finally decided to just do a clean install of Manjaro. This was tricky since my PBP is the only device I have with an SD card reader, but I backed up my user data (so, for the record, there's nothing on it now that I need to save, so all solutions are viable) and then made a bootable SD card via virtual console (which, for me, was an achievement).

Everything seemed fine after a successful clean Manjaro installation - it powered on normally, the GUI functioned as expected, I got my settings dialed back in without issue.

I tried to run a system update but got an error about files that already existed. Unfortunately I can't remember what program was causing the issue, but the recommendation I found was to force an update as superuser, which I did, and things seemed resolved. But I had the bright idea to restart after the update, so I did, but instead of coming back on normally, it froze at the boot logo again. I tried more internet searching and fiddled with some things, trying to remember exactly what I'd done before. However, I was by then righteously pissed, so I decided, fuck it, I'll just re-re-install, but now it won't even boot from the SD card, which I haven't touched since the first reinstall.

The virtual consoles still work, but I still haven't been able to boot either from the SD or normally into the GUI and I can't find any advice I haven't already tried to follow. I tried $xinit and $startx again, which yields the same errors as before, and I tried powering on with the eMMC switched off and then switching it back on when the LED comes on, which also did not resolve anything.

To summarize, the timeline was, to the best of my recollection:

-Normal use
-Probably plugged in too long followed by allowing battery to die several times
-Freeze on boot
-Attempt software troubleshooting
  -Locale
  -Updates
  -Driver check
  -Try to address X11 issues in particular after $xinit and $startx fail
-Attempt hardware troubleshooting
  -All switches and cables in place
-Reinstall OS, boots normally
-Run software updates
  -One error, resolved by installing via CLI as superuser
-Restart after updates out of habit
-Freeze on boot again
-Try $xinit and $startx, same errors as before
-Try to clean install again but won't boot from SD at all, just green LED and black screen
-Try booting with SD and hotswitching eMMC (this struck me as odd but I found it at https://forum.pine64.org/showthread.php?...6#pid62426)
-Despair, weep openly, rage at unjust god, walk the dog for emotional cooldown
-Post on pine64 forum

So, do I need to resign myself to a virtual console-only PBP experience? Am I just taking something for granted that I shouldn't? Did I do this to myself? Is there any good in this world at all? I need to pare down some of my hobbies anyway, so let me know if it's a lost cause and I'll delete my account and go back to doing resin castings. Anyway, I tend to be a quick learner and I like digging into new things, but my Linux experience - and CLI knowledge - is limited to my time with my PBP and Manjaro, so responses on the level of "Baby's First Linux" would be entirely warranted. Thanks, everyone.