There is a thread for official Debian support, but it's not PBP-specific, so I thought it would be appropriate to create one here.

Since linux-image-5.10.0-7-arm64, the linux-image-arm64 meta-package in Debian Sid/Unstable now supports PBP. That corresponds to the kernel version 5.10.38. Latest version is actually 5.10.40. By now linux-image-5.10.0-7-arm64 should've made its way into Debian Bullseye/Testing, which should become the next stable some time this year. I've been running it for the past almost two weeks, and below are my findings so far, primarily compared to the 5.8.5 kernel build using xmixahx's pbp-tools. Since U-boot have an effect on some of the functionality, full disclosure - I'm using BSP u-boot release 2.0 by mrfixit (https://github.com/mrfixit2001/updates_r...filesystem). I have not yet tried other versions of u-boot, neither any of the custom builds nor u-boot-rockchip package from Debian repos that since some time ago claims to support PBP.

Did not test:
* Bluetooth

What works:
* WiFi
* Built-in display at native resolution
* 3D acceleration
* Webcam
* Built-in microphone
* Sound (built-in speakers and headphones, I'm still using custom acpid event to switch output)

What doesn't work:
* Deep sleep (regression compared to xmixahx's 5.8.5)

What works differently:
* Debian's kernel defaults to schedutil scaling governor.
* big cores are now limited to 1.8GHz instead of 2.0GHz, little cores still run at up to 1.416GHz. This could potentially explain why with Debian kernel I have not yet been running into any freezes outside of my attempts at deep sleep, unlike with xmixahx's 5.8.5 kernel.

Source based Linux distribution CRUX-ARM  adhering to ideology keep it simple, has its own package system, also supports the port system.

installation README.TXT
crux-arm-3.6-aarch64-core-rockpro64-5.12.9-build-20210605.img.zst
crux-arm-3.6-aarch64-core-rockpro64-5.12.9-build-20210605.img.zst.sha256

Is the entire board dedicated to bug reporting or is there a specific area?

After updating yesterday my phones audio is super scratchy, this was not the case before the update

Hoping for a fix on that 

Hi,

(in short: USB 2.0 devices don't work on the USB-A 3.0 port and I'm asking if this is normal behavior)

I've tried to see if this question has been asked before but typing usb into the search function will tell you that the word is too short, oops.
Didn't find it in the Wiki either, so here we go:

I've been testing my new Pinebook Pro and I've noticed that USB 2.0 devices won't be properly recognized on the left USB-A 3.0 port.

I've tested two thumbdrives so far, both of which will work well on the right side USB-A 2.0 port.
So I can rule out the devices are faulty.

But connecting them on the left side will produce errors about the device not accepting he setup address and eventual unability to enumerate the device (sorry, different notebook here so I can't paste, but it's quite generic. I will provide logs later, if needed).

I've tried a USB-A 3.0 hard drive that works well (with Pinebook wall plug connected), so the USB-A 3.0 port seems to be fine for those.

My question: Is this normal behavior? Are others seeing this?

I must ask if there a version of debian for the pinebook pro that can support the gpu without having to get too deep into recompiling things?(somewhat pain free install)

So I followed along the guide to install CentOS 7 referenced on the Wiki (and noted on the thread here: https://forum.pine64.org/showthread.php?...&pid=95685 and the guide on the developer's site here: https://project31.github.io/pine64/), and decided to give upgrading to CentOS 8 and then switching to Stream a try.

I followed a few guides online (specifically here https://www.tecmint.com/upgrade-centos-7-to-centos-8/ and here https://linux.web.cern.ch/centos8/docs/migration/), and with a tad extra fiddling to handle the kernel version, I was able to get fully updated and now am booting into CentOS stream!

My question is that upgrading 7 - 8 isn't technically supported, so I would like to try making an updated image for Stream 8.

The Project31 site has some info linking to it's inspiring project, which mentions taking the AArch64 image and a booting Armbian image and swapping out the rootfs bits while preserving the the /boot, /lib/modules, and /lib/firmware (here: https://github.com/umiddelb/aarch64/wiki...ch64-board)

When I try to follow up on this, I cannot seem to figure out how to take the images available on the CentOS site and extract the rootfs.... Can anyone point me in the right direction?

Thank you for your help, and your patience!

Just setting up a new Pinephone with the stock Manjaro OS and getting a 'wrong PIN' error, despite checking a few times when setting up the phone the PIN I would use.

How can I re-run the setup/installation process again? There doesn't appear to be a factory setting or recovery mode option.

Can get usable sound on speakers by setting card to rk... (not default) and increasing volume of "headphones" ? to max and by increasing audio scale to 150% in system settings: audio. But the settings are not persistent. They disappear on rebooting and at other times during use.
Someone mentioned a fix but I can't find it. Thanks for any tips.
Edit: the alsamixer is set back to the "default" card choice when the sound goes back to very low volume. If I re-choose the rk... card, the volume goes back up. I think this is happening when listening to a series of you tubes. Maybe the default setting could be set to the rk... card in some config file. Have each choice be the same?

Hi, all...

...I bought a stock 64G laptop (Pro) from Pine. I have had it about a month.



I tried out a few OS's and played around with it a little. It's interesting, but I think someone on this forum would appreciate it more than I do.


Asking $200, and that includes shipping for (most) U.S. buyers. If you are outside the continental U.S., message me and we'll see what we can figure out.




Cheers,

-Robert



P.S. I am often outside of internet range. If you try to contact me and I don't get right back to you, just give me few hours to respond.                

I've had my Pinephone for some weeks now, and I'm trying to solve one important nagging issue. 

The Broadband modem will just die and not come back up. I'm suspecting that it may be a weak or absent carrier signal but, I have very little to go on.

I'm not finding any  mmcli commands that would allow me to reboot the modem. 

When this happens, it's as if the device is gone, or has been completely unmounted and mmcli fails as there is no device and my only recourse is to reboot the system.

What would be the best approach to:

• Discover and remount the device if necessary
  
• Cycle the modem on if not active