Search the Community
Showing results for tags 'pinebookpro'.
Found 6 results
-
Hi, I put the image on an SD card, but the machine fails to boot. Looking at the serial console, it just sits in a loop with the CPU constantly resetting after an exception. Serial console log is attached. Regards, Dianne. bootloop.txt -
In fact all versions since kernel 5.10.?? are broken and stop at u-boot. Better the Uboot shall dive down and never ever come up to bother us. Finally I managed to install bullseye by using a buster image, deactivtion kernel upgrade and removed the armbian.list from /etc/apt/ Then I changed source list from buster to bullseye apt update apt upgrade -y apt full-upgrade -y thats it. And i is really a shame to fool the community by uploading untested software.
-
Hello, I flashed the Armbian_22.11.1_Pinebook-pro_jammy_edge_6.0.10_gnome_desktop.img file on the 64GB eMMC card of my Pinebook Pro (PBP) laptop but although the eMMC recognizes the image (the ARM logo appears on the screen for a few seconds), booting stalls at (initramfs). I proceeded as follows: 1) First copied the image file from my PC on a 64GB SD card which I inserted into PBP, booted it from the SD card and installed Armbian-Ubuntu without any problem. 2) Downloaded the Armbian*.xz file a second time - this time from the SD card installation -, uncompressed it and flashed it to the eMMC with a USB-to-eMMC adapter after having formatted and partitioned the eMMC. 3) Removed the SD card and rebooted. Installation of Armbian-Ubuntu began but stalled after a few seconds at the (initramfs) prompt. Couldn't type any command (such as exit) after it. PBP only boots from the SD card, but not from eMMC. Nor does it find the SSD card which I inserted with an eNVME adapter on the laptop. Any hint or advice helping me to solve this issue would be very much appreciated.
-
Thank you all for this series of notes. I have been operating Armbian 22.08 successfully using the sd card on my PBP and like it BUT I would like to boot from emm. I have tried dozens of ways to install it to no avail. Seems to be associated with the rootdev=UUID=... If I use the UUID provided in the Armbian-install then I can boot from emm but it ends up mounting and running from the SD partition. Is there any code that can be inserted into the /boot/armbianEnv.txt file that would provide better diagnostics? To me it appears as if the emm partitions UUID is not available at boot time. Thanks, Carl
-
hello guys bluetooth stopped working uname -a Linux pinebook 5.15.76-rockchip64 #22.08.8 SMP PREEMPT Sun Oct 30 10:57:32 CET 2022 aarch64 GNU/Linux dmesg | grep Bluetooth [ 9.863147] Bluetooth: Core ver 2.22 [ 9.863249] Bluetooth: HCI device and connection manager initialized [ 9.863261] Bluetooth: HCI socket layer initialized [ 9.863266] Bluetooth: L2CAP socket layer initialized [ 9.863276] Bluetooth: SCO socket layer initialized [ 9.972130] Bluetooth: HCI UART driver ver 2.3 [ 9.972144] Bluetooth: HCI UART protocol H4 registered [ 9.972147] Bluetooth: HCI UART protocol BCSP registered [ 9.972218] Bluetooth: HCI UART protocol LL registered [ 9.972222] Bluetooth: HCI UART protocol ATH3K registered [ 9.972261] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 9.972460] Bluetooth: HCI UART protocol Intel registered [ 9.972609] Bluetooth: HCI UART protocol Broadcom registered [ 9.972646] Bluetooth: HCI UART protocol QCA registered [ 9.972649] Bluetooth: HCI UART protocol AG6XX registered [ 9.972688] Bluetooth: HCI UART protocol Marvell registered [ 12.322372] Bluetooth: hci0: command 0xfc18 tx timeout [ 20.450331] Bluetooth: hci0: BCM: failed to write update baudrate (-110) [ 20.450363] Bluetooth: hci0: Failed to set baudrate [ 20.799400] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 20.799435] Bluetooth: BNEP filters: protocol multicast [ 20.799461] Bluetooth: BNEP socket layer initialized blueman-manager blueman-manager 14.32.28 ERROR Manager:147 on_dbus_name_appeared: Default adapter not found, blueman-manager 14.32.28 ERROR Manager:151 on_dbus_name_appeared: No adapter(s) found, exitin stopped working after last system update
-
Hello! I don't really have a question, but just wanted to report I tried out the generic UEFI arm64 image on a Pinebook Pro, and it installed emmc and booted just fine! This was possible because I had installed Tow-Boot to the SPI flash, which supports UEFI booting. I had tried using the Pinebook Pro build of armbian, which worked fine when booting off the sdcard, but installing it to the emmc wasn't working. I'm using Tow-Boot 2021.10 then arbmian image Armbian_22.08.7_Uefi-arm64_jammy_current_5.15.74 . There's a few rough edges in the grub menu, but it boots the OS off the emmc just fine. Should the be mentioned on the Pinebook Pro page? Personally, having Tow-Boot installed to SPI is all around a much more "normal" laptop experience, so it seems like a good idea in general.
