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.

Back when I replaced my cracked screen I managed to damage the vibration motor on the USB-C side board by prying it up in the wrong place and breaking it apart.

I recently bought a replacement USB board with vibrator and installed it but still am not getting the confirming vibration when turning the phone on. Is there a command that can be used to manually test the vibration motor to see if it's doing anything? (Charging is working through the USB port so I know the board is connected.)

Does anyone have an idea of when the PinePhone mainboard will be in stock again? 

Thanks in advance

I previously tried to install "calindori" on mobian, but did not get very far, -it's a bit out of my league.

I just thought I would pose the question of whether this is a terribly difficult thing to package for mobian, as it seems to be designed to work pretty well on small screens?

Regards everyone.

Hi, does anyone know a fix for this?

I tried plugging in my pinephone dock (with nothing in it) to my pmos ce pinephone, running mobian, and the screen goes blank. If I unplug it, the screen comes back on again.

I have never used the dock for anything previously, or changed any settings in regard to it.

I was just going to plug a usb memory stick into the dock to transfer files to and from the phone, using a file manager.

The same thing happens if I plug a memory stick into a usb-a to usb-c adaptor, then plug it into the pinephone. (the activity light on the pendrive flashes for a second or two, however)

Regards everyone!

I am interested in purchasing a pinephone but the one thing holding me back is the dip switch location.

My idea at first was to cut out the back place to have easier access but the switches are tiny, so I cam up with a newer idea.

Why not make a back plate or case that not only allows access to the kill switches, but also enlarges them so it is more practical and convenient? Yes of course the back would stick out more but it is something we could get used to by necessity? 

Maybe this is easier said then done but I would love to have this option. Thoughts?

edit: what is the status of HDCP (High-bandwidth Digital Content Protection) on the Pinephone and its relation on how it connects to the external monitor via HDMI on the dock? If it's there, can it be toggled off? Hadn't thought of this recently with all my old gear, doing some more reading I guess it may be a big part of the equation with getting a signal to an old DVI monitor. I am seeing "HDCP" compliant dvi/hdmi adapters, where my old monitors stand with that I'll have to look into more.

beginning of original post:
Hello, read a bunch of threads/searches etc about various problems with hdmi monitors via the dock and also success stories. Going deeper I found a couple of things reporting problems with hdmi to dvi monitor, but the threads were 4 years old. Anyone having success running the convergence dock (or other) from the pinephone to hdmi cable to a dvi monitor via an adaptor?

I will be looking into the various small hdmi monitors for portable use, but right now I have a 23" Apple Cinema display native 1920 x 1200, and a 24" Dell 2405fpw, also 1920 x 1200 native. These are run singly, not dual monitors, just different workstations. Working beautifully with my old Dell m6500/m6300 1920x1200 precision laptops.

Note: I don't have a working PP at the moment, waiting on microSD card as the OS needs to be flashed. Just looking ahead and researching hdmi to dvi adaptors. Looks like I can get set up to experiment with both my current monitors pretty cheaply <$20 for just the adapters. I already had a couple of nice hdmi cables on hand I had picked up real cheap at a yard sale years back, looking ahead to this day
thanks

edit: good info here but not PP specific, and 4 years old: use of sunxidrm, and RGB vs YPbPr settings if available in monitor. I do happen to have a powered dvi active 'repeater', mentioned in the thread.
https://forum.pine64.org/showthread.php?tid=1374

and this one, also 4 years old, again not PP specific:
https://www.reddit.com/r/pine64/comments...t_screwed/
which points to this 'caveat' suggesting do not use dvi/adapters
https://elinux.org/Pine64#Caveats

Hi folks,

I just assembled my NAS case for the RP64 which I had lying around for a few months. When doing this, I followed the wiki, yet I encountered a few obstacles:

(1) The wiki shows the RP64 screwed in with black screws. This does not seem right to me. Imho, the black screws with the cone heads go only on the outside of the case. For inside the case, the four silver screws with the flat heads seem right to me.

(2) The edges of the cage for the HDDs are pretty sharp and might damage the SATA/Power cables while routing. I have put some tape  around the sharp parts to make it more safe. Would you consider this a worthwhile recommendation for the wiki?

(3) The larger silver screws included for installation of the hard drives seem too long to me. When I used them, I damaged the threads in one of my disks although I paid attention not to tighten them too hard. Luckily I tried this with two near-worthless and very dated disks (250 GB WD RAID Edition, the "original" and legendary predecessors of the WD Red series...). I then switched the screws for some others I had here that are about half way shorter and seem to fit better.

Has anyone else had similar issues? If I'm not the only one I will consider updating the wiki and adding some notes about these issues.