Search the Community

I've just installed to a Pinebook Pro successfully. Bluetooth is not working, but that's acceptable to me. Details here Thank you so much @MMGenfor the script.

I've just installed armbian to Pinebook Pro's eMCC using the full-disk encryption helper script from https://github.com/mmgen/mmgen-geek-tools The said script was executed inside an armbian installation in an sd card with official Pinebook Pro image. The eMCC installation almost worked - it boots to graphical desktop, however there's no wifi and bluetooth. I don't have any other way to connect the laptop to internet. I guess the way to fix this is to boot the sd card again because it has internet, then open the encrypted disk manually and chroot to its root, then run some command - but I don't know which one! Please help.

I'd be happy to assist with Pinebook Pro maintenance. github.com/seclorum

I have a Pinebook Pro and installed Focal xfce on its eMMC. I would like to swith to i3. So I have installed `i3`, `i3status` and `i3lock` using apt. Then I have altered the `user-session` config of lightdm from `xfce` to `i3` (actually did this at three places). With all this done, I still end up in XFCE. Hints on where to look further are welcome.

Don't have it, but now support should be more or less complete. https://www.armbian.com/pinebook-pro/

It's Focal so XFCE--specifically the current Armbian Focal xfce mainline based kernel 5.10.y for ("no official support") Pinebook Pro. I can probably learn how correct it by studying the differences between the launcher on my Arbian systems vs. my MX-Linux (x86-64) program launcher on another computer. That will probably take more time than it's worth vs. just launching the root aps from the cli though. MX-Linux uses the Whisker menu so maybe a solution lies in trying to install the Whisker menu in Armbian. Thanks

I just upgraded my Pinebook Pro touchpad firmware. Wow! It's especially helpful with Armbian, which lacks the extensive synclient controls of other distros that can partially mitigate the former touchpad lag and hysteresis. Even with synclient, it's a huge improvement! https://forum.pine64.org/showthread.php?tid=14531

I'm running Armbian Focal on my Pinebook Pro. With other distros, I'm accustomed to being able to run utilities requiring root privileges like gparted and Synaptic from the Application menu. With Armbian, however, nothing happens after I click on the application. There is no popup window to authenticate with a root password and the application does not launch. The aps work fine when run from a terminal using sudo, but how can I correct this problem with the Application menu? Thanks!

Is anyone having issues with the Cinnamon desktop version restarting the desktop when using the menu app launcher? Can be repeated by launching with super key and typing anything for search or just launching any application. Happens with all 3 major menu app launchers. menu, cinnamenu and cinnstark Pinebook pro

In uboot there's a folder containing files that end in defconfig Those files are whats used based on what's configured here https://github.com/armbian/build/blob/master/config/boards/pinebook-pro.csc If you run make menuconfig you can load one of those defconfig files and then save accordingly

After lightdm fails on my Pinebook Pro, I simply logon to the terminal and startx but I will try slick-greeter. I could not find the "enable Desktop" from armbian-config -> System-settings, which I assume is an Applications menu hierarchy. Thanks!

Hi al. I've finished my review of the PineBook Pro. I just love this thing. Runs great with Armbian. Here my video. Here all my gathered information:

Hi, i got a Pinebook and install the latest Armbian Image. All is working fine, only the sound output make problems. It isn't matter if i play a mp3 file or a play a YT Video. The sound is just strechted, drawned, like in slow motion. What can i do to solve this issue? Any ideas? Thank you for your help.

4K is hard. I gave up on it. Try this conf but remove the screen section to make sure you're at least using the drm display driver https://raw.githubusercontent.com/armbian/build/master/packages/bsp/pinebook-pro/xorg.conf

Budgie is on my list - as I get kinks worked out with clean, vanilla Armbian. I am doing hybrid arm64 kernels and armhf userspace because of audio-plugins. This worked well for me in Pinebook Pro, etc. I'd do more with pure arm64, if I can solve some gaps with Carla, and when there's a 64-bit Linux Widevine. That's when Google decides they need a 64-bit Chromebook, I guess. — Jeremiah

Hi all, I have a working Pinebook Pro Focal build with LUKS encryption enabled. The only issue I have is that when booting no progress or password prompt is displayed. As soon as I enter the password and hit enter I see the boot logo or console output depending on what is set in armbianEnv.txt. I will be continuing my research and learning about the boot process in general but wanted to check in here to see if people had any obvious pointers to share or whether maybe this is a known limitation that is going to be hard to resolve. Thanks, Matt

make sure the Xorg config is using the code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } modesetting driver and not code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } fb Example here: https://github.com/armbian/build/blob/c1ef2aeba9ab782ec543e37425f2da61b2f4c4fb/packages/bsp/pinebook-pro/xorg.conf#L9 Otherwise it's a constraint of the driver for the SoC.. not really an Armbian limitation. Also it's possible the port may be called HDMI-A-1 code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } root@orangepi4:/sys/class/drm/card1-HDMI-A-1# pwd /sys/class/drm/card1-HDMI-A-1 anyway I suspect you need to use the other driver and will be able to use normal means of adjusting resolution FYI I hid your feature request post because it was redundant and I've responded here.

I'm running the Gnome image on my Pinebook Pro and I have to say its pretty good. Ive noticed that the battery life is much more! maybe is due to the GPU work. Everything seems well indeed except that like a previous user said; the changing of the desktop background. I also cannot select any background other than what is specified in /usr/share/backgrounds which dont change anyway. Also, when plugging in a headphone the audio playback wont auto-mute the speakers, ill have to open alsamixer and mute the speakers and bring up the headphone volume; every time i restart the computer. Aside from these everything is much better in terms of fluidity, like its actually more pleasant to use this device now. Great work; Also, I have 0 coding knowledge, i wish i can contribute that's why Im writing this here..

Adding the Pinebook Pro and T-Firefly ROC-RK3399 PC PLUS a.k.a StationGeeker Station P1 to this list

With the help of @megi / @megous , I've now my Pinebook-A64 LCD working. Here is the patch : https://github.com/armbian/build/commit/d49be78b702d7779f78d2655126a56e7f2ea7426

I guess in my mind, the notion of starting to play around with SBC (especially headless)[0] without wanting to learn how to do it "the old fashioned way" in plain vanilla Debian, via terminal, etc... I just find bizarre! But I guess I will just have to take your word for it. In fact, I always considered the fact we try to stick as close as possible to plain Debian (/Ubuntu) as one of the main selling points. For me anyway, the further things get away from those standard tools, the less I like them. Am I alone in this? Well, sorry for the noise. Hopefully if we break this project up into some manageable bits as discussed, I will be able to contribute one or two little pieces at some point. I guess I better get to looking at the existing code, as I never have even used the software, much less dug into the code yet. [0] Which Armbian have been more so historically, although changing recently with more desktop stuff and support things like PineBook Pro, etc.

Hallo Igor, thanks for taking the time. I tried to debug the issue my self but good stuck on booting an vanilla kernel (creating the uinitrd for it). Wondering if there is some documentation on how to boot the a64 without it (i dont see why we need one here). Meanwhile i have some bootlog with from the armbian kernel (which you probably already have but which may help other to help here debugging) [ *** ] A start job is running for Armbian …ware optimization (28s / 2min 14s) [ 44.008360] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CRTC:41:crtc-0] flip_done timed out [ 54.237793] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CONNECTOR:43:eDP-1] flip_done timed out [*** ] A start job is running for Armbian …ware optimization (29s / 2min 14s) [ 74.744614] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CRTC:41:crtc-0] flip_done timed out [ 84.957794] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CONNECTOR:43:eDP-1] flip_done timed out [ OK ] Finished Armbian hardware optimization. [ 105.469267] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CRTC:41:crtc-0] flip_done timed out [ 115.695951] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CONNECTOR:43:eDP-1] flip_done timed out [ 125.928118] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [PLANE:35:plane-1] flip_done timed out [ OK ] Reached target Basic System. [ 136.174199] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CRTC:41:crtc-0] flip_done timed out [ 146.438337] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CONNECTOR:43:eDP-1] flip_done timed out [ 156.637767] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [PLANE:35:plane-1] flip_done timed out Starting Accounts Service... [ 166.899900] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CRTC:41:crtc-0] flip_done timed out [ 177.148191] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CONNECTOR:43:eDP-1] flip_done timed out [ 187.357792] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [PLANE:35:plane-1] flip_done timed out Starting Save/Restore Sound Card State. [ 197.597808] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CRTC:41:crtc-0] flip_done timed out [ 207.837779] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CONNECTOR:43:eDP-1] flip_done timed out [ 218.102088] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [PLANE:35:plane-1] flip_done timed out [ OK ] Started Armbian first run tasks. [ 228.356302] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CRTC:41:crtc-0] flip_done timed out [ 238.557787] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CONNECTOR:43:eDP-1] flip_done timed out [ 248.797769] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [PLANE:35:plane-1] flip_done timed out Starting Bluetooth service... [ 259.089793] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CRTC:41:crtc-0] flip_done timed out [ 269.315817] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CONNECTOR:43:eDP-1] flip_done timed out [ 278.242162] Unable to handle kernel paging request at virtual address 0000000040030027 and later on the trace to it [ 279.621805] ------------[ cut here ]------------ [ 279.621822] [CRTC:41:crtc-0] vblank wait timed out [ 279.621904] WARNING: CPU: 1 PID: 193 at drivers/gpu/drm/drm_atomic_helper.c:1513 drm_atomic_helper_wait_for_vblanks.part.28+0x274/0x290 [ 279.621907] Modules linked in: hci_uart btqca btrtl btbcm 8723cs_old btintel bluetooth uvcvideo cfg80211 ecdh_generic axp20x_adc analogix_anx6345 axp20x_battery axp20x_ac_power videobuf2_vmalloc analogix_dp sunxi_cedrus(C) rfkill lima ecc sun4i_gpadc_iio gpu_sched industrialio l [ 279.622012] CPU: 1 PID: 193 Comm: kworker/1:2 Tainted: G D WC 5.10.18-sunxi64 #trunk.1 [ 279.622014] Hardware name: Pinebook (DT) [ 279.622030] Workqueue: events splash_callback_animation [ 279.622039] pstate: 40000005 (nZcv daif -PAN -UAO -TCO BTYPE=--) [ 279.622044] pc : drm_atomic_helper_wait_for_vblanks.part.28+0x274/0x290 [ 279.622050] lr : drm_atomic_helper_wait_for_vblanks.part.28+0x274/0x290 [ 279.622052] sp : ffff800012a03910 [ 279.622056] x29: ffff800012a03910 x28: 0000000000000000 [ 279.622062] x27: 000000000000042c x26: ffff000044646000 [ 279.622068] x25: 0000000000000000 x24: 0000000000000001 [ 279.622074] x23: 0000000000000038 x22: 0000000000000001 [ 279.622080] x21: ffff000042396700 x20: ffff0000421f8080 [ 279.622085] x19: 0000000000000000 x18: ffff8000114d17d0 [ 279.622091] x17: 0000000000000014 x16: 0000000000000002 [ 279.622097] x15: ffff8000114d1810 x14: 0000000000002548 [ 279.622102] x13: 0000000000002580 x12: ffff000075b71a20 [ 279.622107] x11: 0000000000000002 x10: ffff000075b66320 [ 279.622113] x9 : ffff000075b6dac0 x8 : 206b6e616c627620 [ 279.622119] x7 : 5d302d637472633a x6 : 0000000000000001 [ 279.622125] x5 : ffff000075b93810 x4 : 0000000000000000 [ 279.622130] x3 : 0000000000000027 x2 : 0000000000000023 [ 279.622136] x1 : 5280998379074000 x0 : 0000000000000000 [ 279.622143] Call trace: [ 279.622150] drm_atomic_helper_wait_for_vblanks.part.28+0x274/0x290 [ 279.622156] drm_atomic_helper_commit_tail_rpm+0x64/0x80 [ 279.622160] commit_tail+0xa4/0x1a0 [ 279.622165] drm_atomic_helper_commit+0x160/0x408 [ 279.622172] drm_atomic_commit+0x4c/0x60 [ 279.622181] drm_client_modeset_commit_atomic.isra.17+0x1d8/0x270 [ 279.622187] drm_client_modeset_commit_locked+0x60/0x1a0 [ 279.622195] drm_fb_helper_pan_display+0xb8/0x1d8 [ 279.622202] fb_pan_display+0x8c/0x100 [ 279.622207] dummy_update_start+0x20/0x48 [ 279.622213] fbcon_switch+0x368/0x568 [ 279.622219] redraw_screen+0x144/0x270 [ 279.622225] splash_callback_redraw_vc.part.4+0x34/0x48 [ 279.622230] splash_callback_animation+0x4c/0x60 [ 279.622237] process_one_work+0x1f0/0x3c0 [ 279.622241] worker_thread+0x270/0x520 [ 279.622247] kthread+0x120/0x128 [ 279.622253] ret_from_fork+0x10/0x30 [ 279.622258] ---[ end trace d29e482d74631eef ]--- So while i`m not familiar with the the details of the display init i assume this is not the display but the gpu / drm driver crashing. Any advice where to go from here to help with fixing the issue would be very appreciated.

I had been hitting this error in both cases. The install log suggests a conflict between the base package and the desktop package. I am able to create a server image without issues so for now that gives me what I needed! Selecting previously unselected package armbian-focal-desktop-gnome. (Reading database ... 89075 files and directories currently installed.) Preparing to unpack .../armbian-focal-desktop-gnome_21.05.0-trunk_all.deb ... Unpacking armbian-focal-desktop-gnome (21.05.0-trunk) ... dpkg: error processing archive /root/armbian-focal-desktop-gnome_21.05.0-trunk_all.deb (--unpack): trying to overwrite '/etc/udev/hwdb.d/10-usb-kbd.hwdb', which is also in package linux-focal-root-current-pinebook-pro 21.05.0-trunk dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /root/armbian-focal-desktop-gnome_21.05.0-trunk_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

Hello all, I want to build armbian for Pinebook Pro with LUKS enabled but I'm hitting this error. This is happening regardless of build environment (I've tried virtualbox, docker, vagrant) or board selection (most recently I tried building orangepipcplus). .... ] Installing [ armbian-focal-desktop-gnome_21.05.0-trunk_all.deb ] [ error ] ERROR in function install_deb_chroot [ image-helpers.sh:148 ] [ error ] Installation of /root/armbian-focal-desktop-gnome_21.05.0-trunk_all.deb failed [ pinebook-pro focal yes rockchip64 ] [ o.k. ] Process terminated [ o.k. ] Unmounting [ /root/build/.tmp/rootfs-712d9aa2-7aa7-4e20-ae2e-21136ed09662/ ] [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:65 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated Any suggestions on what is causing this failure? Thanks, Matt

@lukasz are you running on X11 For me , using self built hirsute/gnome (as opposed to just downloading) , using gnome on Wayland shows proper " mali T860 (Panfrost)" where gnome on Xorg shows " unknown, but in in either case glxinfo extended renderer section shows panfrost is used. Perhaps there is a bug in the settings program? Desktop sort of works for me on my 4k monitor (usbc dock-hdmi connection--same as on other distributions--the geometry is wrong and that also effects the display on the pinebook itself, but it has worked that way on any distribution I have tried) Natural scrolling setting seems to work on Wayland...