Search the Community
Showing results for 'pinebook' in topics.
-
Normally when you have installed a XFCE-Desktop image for the Pinebook A64 you could set the display brigthness with the following pkexec command to a readable higher level - like I did in the past (possible brightness values are 1-10 - on startup this is only set to 2): pkexec /usr/sbin/xfpm-power-backlight-helper --set-brightness 8 read-out command for the current value: pkexec /usr/sbin/xfpm-power-backlight-helper --get-brightness but on standard CLI-install pkexec and xfpm-power-backlight-helper are missing, so to use this command-line (in /etc/rc.local) you have to install these 2 packages: sudo apt install xfce4-power-manager pkexec
-
[Info] Pinebook A64 Display Brightness at bootup with CLI-only-image
Jecht replied to guidol's topic in Allwinner sunxi
Hello I don't know if anyone is currently looking for how to fix these problems. I have a Pinebook 14" (720p) and tried the following: Last published image: Armbian_community_25.2.0-trunk.377_Pinebook-a64_bookworm_current_6.6.72_minimal.img.xz The boot screen is displayed After the message "Starting kernel" the screen turns off completely for about 1 minute Then the backlight turns on but the screen stays black indefinitely The system is unusable Last image available in the archive: Armbian_23.8.1_Pinebook-a64_bookworm_current_6.1.47.img.xz The system boots without showing the boot screen The message "Welcome to ARMBIAN" is displayed and the configuration process begins The system works correctly and allows installation on the eMMC After performing an "update" and "upgrade" the system is unusable as in the last published image. -
I bought a Pinebook Pro two weeks ago. It came with Manjaro KDE preinstalled on EMMC. I wanted to try out Armbian, so I downloaded the Bookworm XFCE image from May 27th. In order to get the SD booted, I first flashed Tow-Boot for Pinebook Pro (pine64-pinebookPro-2021.10-005.tar.xz) from github Tow-Boot to the SPI. Then during boot after pressing ESC the menu lets you select the SD card for boot. The first boot to Armbian worked well. I could set up user, timezone and everything. The XFCE desktop looks very clean with a reasonable selection of software. Well done, team! But after I upgrade the system with apt update & upgrade, the next time the machine is booted and SD card is selected, armbian won't boot anymore 😞 The upgrade seem to have broken something. I tried it twice, the second time freezed the kernel-upgrades in the armbian-config tool prior to upgrading it. Didn't help. Manjaro from EMMC still boots ok. Attached is a screenshot of the failed boot process, after I selected SD card to boot on the Tow Boot menu.
-
I slowly convinced myself that I wanted a PineBook Pro, some time after the first production run. But then COVID, parts shortages, etc. happened and they were not available again until about mid-2022. But when they were, I decided to snap one up. And since then I have not been able to get it to boot Armbian. It came from the factory with Manjaro, which for me being a Debian guy, might as well be useless. So the PBP sat around collecting dust. Since then I have tried a few times to get it to work. I read many forum posts, tried some things. I won't document all that in detail. In this post, I will continue from where I left off here. However to summarize, that was about comparing DTB/DTS files to Kali, which supposedly works. That may become useful later, but I don't think that's the main problem. I think that the main problem is that this new batch came from the factory with no bootloader flashed to the included SPI flash chip. This is a problem on PineBook Pro because the RK3399 has a kind of weird boot order: SPI, eMMC, SD card. Therefore, if you just put in some SD card you flashed, it still boots from the factory Manjaro from the eMMC. Whatever bootloader they are using also apparently will not recognize an otherwise working Armbian image on an SD card. Now, because of the weird boot situation, there is supposed to be a switch to turn off eMMC. However this did not work for me. Which means one of 2 things: The switch does not work. I read at least one other person saying this. Also on the new revision, it's in a slightly different place than the old revision (may be a clue, maybe not). I simply had a bad Armbian image (which I had burned to sd card) that would not boot for whatever reason.[0] But let's put that aside for a moment. As I still think the main problem is the (empty) SPI. And that will be the easiest/best path forward. I confirmed the 'blank SPI' theory 2 different ways. First, as mentioned in a follow-up to the linked post (4 paragraphs above): As Martijn Braam states here: Of course, I like to beat a horse until it's really dead be thorough in my investigations, so today I wasted a lot of time[1] verifying that this indeed was the case. I did so by dd'ing the /dev/mtd0 block device into a file[2]. When I examined the file, it contained all FF, and also it is about 16 MiB in size. To me this confirms that indeed, the SPI on the new batch comes from the factory empty. So what is next? I keep reading that the only people who had success first had to install something like tow-boot to the SPI. That will be my next step. But before I flashed anything to SPI, I wanted to see what really came from the factory (which I did above). I will continue to document my progress whenever time allows for me to work on this. [0] Once I got the bootloader situation sorted, I later used this same image (on the SD card) to boot and install Armbian, so I do not think this was the case. [1] In the end the solution was simple. But first I wasted a lot of time trying to get rkdeveloptool working in Manjaro on the PBP. Only to realize it's intended to be used from a second machine to read the SPI flash via USB in maskrom mode. Anyway, lesson learned. [2] I tried to attach it but maybe it's too big.
-
Hi, I read everything I could possibly find on the DP-Alt mode for the RockPro64 and came to the conclusion that no Distro is offering that right now. However, the Pinebook Pro seems to have support via a Kernel Patch. Can the Pinebook Pro Kernel be installed on the RockPro64? Is there a repository for Armbian Kernels? Thanks very much.
-
Hello, as already mentioned in topic USB C port doesn't work after upgrading to the latest kernel 6.6.2 . The previous problem with not working left usb 3 port persist no more. Everything is fine. As I remember , before update the usb c port has worked with the adapter and the devices like mouse, usb flash etc. Now it doesn't work any more, furthermore it gives no signal of life. There is 0 amps current measured, also dmesg -W gives no output at all after plugging in the device. PS: I was unable to upload the report file, also the service paste.armbian.com doesn't work at the moment.
-
Description Other devices could be added if whatever the regulator needed for UHS is enabled. Read perf def improved on the gnome disk benchmarks. Jira reference number [AR-9999] let's enable salva's UHS overlay for RK3399 tested on PBP with 2ghz with 64 gig samsung evo select i like using the yabs.sh fio benchmark for mixed r/w tests curl -sL yabs.sh | bash -s -- -i -g -n also did gnome disk utility read benchmark before kernel 6.6.10 yabs # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # # Yet-Another-Bench-Script # # v2024-01-01 # # https://github.com/masonr/yet-another-bench-script # # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # Sat Jan 6 05:59:38 PM EST 2024 ARM compatibility is considered *experimental* Basic System Information: --------------------------------- Uptime : 0 days, 0 hours, 2 minutes Processor : Cortex-A53 Cortex-A72 CPU cores : 6 @ 1512.0000 2016.0000 MHz AES-NI : ✔ Enabled VM-x/AMD-V : ❌ Disabled RAM : 3.7 GiB Swap : 1.9 GiB Disk : 57.5 GiB Distro : Armbian 23.08.0-trunk sid Armbian 23.08.0-trunk sid Kernel : 6.6.10-edge-rockchip64 VM Type : NONE IPv4/IPv6 : ✔ Online / ❌ Offline fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/mmcblk1p1): --------------------------------- Block Size | 4k (IOPS) | 64k (IOPS) ------ | --- ---- | ---- ---- Read | 1.82 MB/s (457) | 8.12 MB/s (126) Write | 1.85 MB/s (463) | 8.51 MB/s (133) Total | 3.68 MB/s (920) | 16.63 MB/s (259) | | Block Size | 512k (IOPS) | 1m (IOPS) ------ | --- ---- | ---- ---- Read | 12.39 MB/s (24) | 12.48 MB/s (12) Write | 13.51 MB/s (26) | 13.74 MB/s (13) Total | 25.90 MB/s (50) | 26.23 MB/s (25) gnome disk utility read benchmark (just defaults) Cool got some tiny gains on everything but 4k block after UHS enabled 6.6.10 yabs # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # # Yet-Another-Bench-Script # # v2024-01-01 # # https://github.com/masonr/yet-another-bench-script # # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # Sat Jan 6 06:05:48 PM EST 2024 ARM compatibility is considered *experimental* Basic System Information: --------------------------------- Uptime : 0 days, 0 hours, 0 minutes Processor : Cortex-A53 Cortex-A72 CPU cores : 6 @ 1512.0000 2016.0000 MHz AES-NI : ✔ Enabled VM-x/AMD-V : ❌ Disabled RAM : 3.7 GiB Swap : 1.9 GiB Disk : 57.5 GiB Distro : Armbian 23.08.0-trunk sid Armbian 23.08.0-trunk sid Kernel : 6.6.10-edge-rockchip64 VM Type : NONE IPv4/IPv6 : ✔ Online / ❌ Offline fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/mmcblk1p1): --------------------------------- Block Size | 4k (IOPS) | 64k (IOPS) ------ | --- ---- | ---- ---- Read | 1.85 MB/s (464) | 8.81 MB/s (137) Write | 1.88 MB/s (471) | 9.32 MB/s (145) Total | 3.74 MB/s (935) | 18.14 MB/s (282) | | Block Size | 512k (IOPS) | 1m (IOPS) ------ | --- ---- | ---- ---- Read | 13.06 MB/s (25) | 13.64 MB/s (13) Write | 14.38 MB/s (28) | 15.23 MB/s (14) Total | 27.44 MB/s (53) | 28.87 MB/s (27) gnome disk utility read benchmark (just defaults) View the full article
-
Hello all, I got a problem after new update of armbian firmware through your own module (script). The left USB port on pinebook pro has stoped working at all. Before that was occasionaly after 6 -7 boot ups only one time not working (it is used for mouse). Now after x rebooting it doesnt work at all. The right USB port works without problems. On the left, also USB flash drive doesn't work. No idea, what could it be? Before, as already said, it has worked in 90%. Before firmware upgrade.
-
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.
-
I found a workaround for this problem. Need someone to confirm if this works: 1. Download https://archive.armbian.com/pinebook-pro/archive/Armbian_24.2.1_Pinebook-pro_jammy_current_6.6.16_gnome_desktop.img.xz 2. sudo apt update & sudo apt upgrade 3. reboot 4. install to eMMC or nvme Does it survives?
-
Description This provide an option to set last good kernel for dedicated device. It will prevent upgrading to higher kernels which are known to be broken. For example. At this moment we have Rockchip BSP kernel which was fixed that Radxa ITX has working ports, while this fix will break NVME support on Orangepi. Also this we can use for Pinebook PRO. Configuration: BOARD BRANCH LINUXFAMILY Last good kernel package from repository orangepi5 vendor rk35xx 24.5.3 orangepi5plus vendor rk35xx 24.5.3 orangepi5|vendor|rk35xx|24.5.3 orangepi5plus|vendor|rk35xx|24.5.3 How Has This Been Tested? [x] Test with locally generated repo that contained higer version of kernel. It was hold back. Checklist: [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
-
What about custom hardware, called Pinebook PRO, that needed years before opensource routines were developed by 3rd party (community)? Until then, hardware already become obsolete, maintainace expensive. I am sure Armbian works perfectly on it I am running it on my x86 Lenovo laptop and it works perfectly too. Armbian Ubuntu is exactly the Ubuntu I want & need for everyday work. Do you run Armbian there too and why not? Are you sure? Start volunteering and after a year, you will understand something, after few years you could understand our perspective. I totally agree with you. We do have a mechanism to determine when to adjust status, but it runs every 3 months and with best effort principle. Its not a professional service and runs without any budget. We have no interest to fool you or deliberately waste your time, like everyone wants to waste ours. We try to educate people, but that is usually difficult and expensive as general expectations are shaped by much bigger forces and not with common in mind. This is our try: https://docs.armbian.com/#what-is-supportedmaintained vs. trash proprietary hardware and naivety of people. This is the only way: "Supported/maintained is not a guarantee." As in this world, this is the best you can expect. They sold you demo device without software support and you don't support us to support you! And other big side is telling you something else. We can't compete with that brainwashing. Keeping status synchronized with reality is also expensive, a professional service and also paid from our private pockets. If we would have a volunteer to talk and motivate maintainers, testers round the clock - perhaps you? - we would know faster, before you complaining that something is not o.k. Its a serious logistic operation, while nobody support that so its a complete waste of our time. Why would you waste your time to save everyone's time? While telling me how we should do thing differently to save everyone's time. Step up, make this change so that everyone's time won't be wasted. Also feel free to use any other Linux for Pinebook PRO if ours stop working. Why there are so many alternatives on non-proprietary hardware? And all of them works perfectly. Everyone covers only 0.5% of all maintainers time. Think from that perspective. Armbian is not random Linux me-too distribution. There are no justifications for that and is IMO stupid. It might get fixed upstream, someone might sponsor our work to fix it for you & everyone and you will be happy again. Once support is moved to community, it costs us close to nothing / same as other Linux distributions, which "supports" the hardware. And most people understand that they have nothing to complain about. And are happy when downloaded image works. We needed several years to come out with something that works better then chaos - if you care to understand: https://docs.armbian.com/User-Guide_Board-Support-Rules/
-
No, a MacBook is not the answer. Proprietary software never is. I have an x86_64 laptop running Linux that works perfectly. I understand and appreciate that the Armbian devs are volunteers and do a lot of hard work. But if you can't properly support a platform, don't advertise it as supported. That just wastes everyone's time. I see now that the Pinebook PRO is no longer listed as a supported platform. I wish that had been the case a year ago when I made the decision to purchase mine. (It is still listed as "community maintained" which IMO is misleading. It's not maintained by anyone. Please remove it completely from the list of Armbian hardware.)
-
Getting Armbian working on second batch (Mid 2022) PineBook Pro
Miles Raymond replied to TRS-80's topic in Pinebook Pro
I've installed https://github.com/Tow-Boot/Tow-Boot/releases/tag/release-2023.07-007 Towboot to SPI and https://dl.armbian.com/pinebook-pro/archive/Armbian_24.5.3_Pinebook-pro_bookworm_current_6.6.36_minimal.img.xz to a uSD card but it will not boot. I thought it was a Towboot problem, but it boots to Manjaro on a uSD card (and on eMMC) just fine also. https://github.com/Tow-Boot/Tow-Boot/issues/319 Which Towboot version and which Armbian image did you use? -
You are looking at the master branch. We need an orange-pi-6.9 branch. See: https://megous.com/git/linux/tree/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts?h=orange-pi-6.9#n729 But simply adding this node will not bring results. A set of patches from this rk3399-typec-6.9 branch is needed and there may be something else. Use the instructions to get the necessary README Look at the contents\history (git log -p megi/rk3399-typec-6.9) of the received branches. Special attention is paid to: megi/tcpm-6.9 megi/typec-extcon-6.9 megi/rk3399-typec-6.9 megi/fusb302-6.9
-
I got in contact with the kernels author and got told, that DP-Alt is not yet implemented for the rockpro64. Looking at the schematics, the usb-c controller seems identically to the pinebook pro. I am ready to start digging in the device-tree file for the rkp64 by comparing the pbp to the rkp64. But I don't know how to create and test the Kernel from these files.
-
Generating images, once device is in the system, does not burn our expensive time. It costs a lot less then answering this support question. Updates are generated for all devices (of one family) at once. Adding and removing is expensive and perhaps someone fixed this problem? Then we need to put it back. Those are already maintaining activities, which we don't have resources for ... keeping devices in auto-build costs us close to nothing (until compilation succeeded) and this is the same way all others distros do, while they are marking those random auto-build as "supported by Linux X" ... We at least tell you "we don't know if it works", as checking is expensive. Or even impossible as nobody from the team has this device. It was added by someone like you, user, that wanted to keep this device in the Armbian system, which system provides a lot of common fixes and generally helps maintaining those devices. Our interest is that Armbian runs well on as many devices as possible, but the costs of that is super extreme - as you know, we can't sell you our work, you don't want to pay our bills .... Once we bring support on some device, we have copycats that does absolutely nothing but also "supports" this device. It is really difficult as costs dealing with those devices is close to impossible to cover. If you want that device function perfectly and when there is close to nobody helping, one needs to spent serious time / money to support HW dealers business, copycats and you. Its not sustainable. The same applies to other devices that were thrown to the market ... We are maintaining this system, some devices, while the rest are on you - community. Providing images, keeping this device in the system that is getting common updates all the time, is already great added value. Bugs are shared among similar devices, which means when this bug will be fixed for Pinebook PRO, this device will also have working images ... Its pure economy. They can't afford that. Device is here - and if you want to keep it operational, its your problem. Well, our common problem. We add our share and we can't add more. We don't have this device, we don't have anyone maintaining it. Not anymore. Now, a lot of those devices will still work even nobody maintain them. This indicates it stops before loading user space, probably kernel is crashing. Sometimes you need to solder those pins. HW designers aim is to make a device that they can sell well ... Does this device matches that? Yes, its a nice toy. There is no GRUB on those devices, but yes, problems with boot loader are possible. Every major kernel bump renders some devices into not usable state. That is why we have so much work that nobody notice and very little help. If we could allocate needed resources, all of those "Community (not) supported" will be working. This is certainly not in HW designers interests (as they want to sell you new device), while end users can't understand that buying hardware is just a fists step and means nothing. You need to add a lot more to have this device functional. This is not RPi, who has masses of people that will maintain it for free.
-
[Info] Pinebook A64 Display Brightness at bootup with CLI-only-image
guidol replied to guidol's topic in Allwinner sunxi
Like on the OrangePi's which have problems with the latest Community Edition (kernel 6.6.x and their armbian-firmware) I went back to the most actual stable image before kernel 6.6.x (non-Community Edition?) for the Pinebook A64 which can be found at https://armbian.hosthatch.com/archive/pinebook-a64/archive/Armbian_23.11.1_Pinebook-a64_bookworm_current_6.1.63.img.xz You do get a non-Desktop system with Armbian 23.11.1 Pinebook-a64 bookworm current kernel 6.1.63 then do a Kernel-Freeze in armbian-config -> system apt update/upgrade and you will end with a stable Armbian 24.5.1 Bookworm with Linux 6.1.63-current-sunxi64 This will recognize my 14" Screen, WiFi and Ethernet (USB) -
[Info] Pinebook A64 Display Brightness at bootup with CLI-only-image
guidol replied to guidol's topic in Allwinner sunxi
@Gunjan Gupta Today I did try the following images Armbian_community_24.8.0-trunk.205_Pinebook-a64_noble_current_6.6.31_gnome_desktop.img and Armbian_community_24.8.0-trunk.205_Pinebook-a64_bookworm_current_6.6.31_minimal.img on my 14" (1080p?) Pinebook non-Pro A64, but I do get only a black screen It didnt help to use echo 8 > /sys/devices/platform/backlight/backlight/backlight/actual_brightness or the pkexec-command The screen lights up, but to information on the screen. I had only (sometimes) access via a USB-Ethernet-Adapter. But at some boots the ethernet wasnt recognized and the onboard-Wifi doesnt sho up The last version I could get my screen to work - with a CLI-version of bookworm - is 24.2.0 of armbian (after update?) I dont know how to switch via 720p/1080p for the different screensizes of the Pinebook A64 non-Pro (I have 14" and not 11.6") BTW: after updateing the 24.2.0 of armbian via apt update/upgrade the system is also non-working (Black screen and no ethernet and no Wifi) Its has updated to kernel 6.6.31 and this was also the "death" to some of my OrangePi installations The "Community Editions" are at this time unuseable (because non-tested) - this could end in a bad reputation also for the supported devices - as I think. For me its software-obsoleszenz - rendering working hardware into a paperweight -
Late reply here, but it seems all the Armbian images are broken. While I understand your frustration with Pine64, I think you should remove the Pinebook Pro from your list of images. Being up front and saying that you don't support the hardware is better / less frustrating than claiming to support the hardware but providing broken images. Anyway, I'm selling my Pinebook Pro and reverting it to the factory Manjaro build. It's too annoying to keep fighting with it.
-
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.
-
Hi Referring to https://forum.armbian.com/topic/32667-usb-c-port-doesnt-work-on-pinebook-pro-after-the-latest-update-on-kernel-662/ USB -C is not working. I also tried 6.7.4-edge with no success. Looking for a solution G??gle found this: https://www.linuxquestions.org/questions/slackware-arm-108/pinebook-pro-usb-c-port-not-working-after-kernel-upgrade-4175732886/#google_vignette referring to Megi`s 6.7 kernel. The link was outdated, but the base worked and had versions 6.8 and 6.9. Tried both with a lot of success: USB-C working and the HDMI monitor output as well as Gigabit Ethernet work like a charm again. 😄 The only small issue remaining: Sound is not working (no analog or digital.) armbianmonitor: https://paste.armbian.com/mamocolodo (I had a small issue following Megi`s Readme: The board.dtb should replace rk3399-pinebook-pro.dtb in one of the existing dtb trees. I used dtb-6.7.4-edge-rockchip64.) any ideas about the sound issue are greatly appreciated. Sepp