Search the Community

Hello. I just tried the latest Armbian jammy for PineBook Pro and the kernel refuses to boot. I tried to replace the 6.6.31 kernel with 6.1.63 from older image and it works without problems.

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.

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)

@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

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.

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.

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

@snakekick Thanks, that seems to confirm my findings back a few months ago. Adding a 5ms delay in the test case did not prevent the crash. Though it could be the system load is at play. Maybe adding a delay at the kernel level would do. pcie is tagged on the big CPUs so the SATA disks seem to matter (as the ethernet port). One could try in emergency mode (passing emergency to the kernel (I do it by "setenv extraboardargs emergency" after halting u-boot with a key press then enter "boot"). You will have just the root partition mounted read-only (so no network connection, a serial console is required). Then run the test. Also note that the design of the GPU regulator has the same issue as the CPU b one ... (for my tests I blacklisted panfrost, ie the GPU driver). After looking at the rockchip64 board schematics the design around the CPU b regulator is not similar but exactly the same as the helios64 one (rockchip64 uses a tcs4545 regulator for cpu b and tcs4546 for GPU). I wonder if the easiest fix would not be to pay someone to desolder the syr837 regulator and solder a tcs4545 instead - same for the GPU regulator a tcs4546 instead of the syr838... except that these chips from Torch Chip seem nowhere to be found. Maybe rip them from a rockpro64 board. @aprayoga can you confirm the Helios64 design for the rk3399 big cpu and gpu regulators are the same as the RockPro64 ones? Would it make sense (and would it fix the unstable cpu_b) to desolder the syr837/syr838 to replace them with tcs4545/tcs4546? Ie the tcs4535 datasheet (I am still unable to find the tcs4545 datasheet) I found tells tcs425 has internal pulldown for VSEL and EN which syr837 does not, the syr837 datasheet requires a 22uF capacitor for VIN but the helios64 has a 10uF one like the rockpro64 for the tcs4545. The SW pin of the helios64 has 470uH inductor with 4 x 22uF capacitors like the rockpro64 for the tcs4545 (like the typical application in the tcs4535 datasheet with 470uH inductor with two 22uF capacitors)? Do you know a replacement for the TCS4545/TCS4546 that has closer specs than the syr837/syr838? I cannot seem to find TCS4545/TCS4546 for sale (maybe I could buy a rockproc64 to desolder them at least for a test... or could you check on your side with a helios64 board that the cpufreq-switching-2-b test above crash with syr837 but not with tcs4545 with vanilla rk3399 opp definitions in dts? Sadly the Helios64 filled a market that is left unfilled. People who do not have the know-how to go full low-wattage DIY NAS and who also cannot afford to pay 1K€ for a NAS (and who might need two NASs to make things worse). In the meantime, I spend a lot of time learning about DIY NAS, but it is still hard to get wattage at full load (they tend to give all idle power usage). I probably will end up gambling and buying one build and pray... but with Helios64 I had the metrics before buying. I found that the Rock960 has the same design for the cpu_b and gpu regulators except for the inductor which is 0.240uH on the rock960 and 0.470uH on the Helios64. But hard to tell if the Rock960 is stable with my cpufreq switching test for the big cpus of the rk3399, might be the use of the board does not stress it as much as a raid10 on the helios64 pcie sata which is tagged to the cpu_b ... (initially it was 4 3TB WD Red - the old CMR model WD30EFRX-68EUZN0), from Helios4 setup as advertised by Kobol wiki for the Helios4... the board crashes on first boot after assembly with this raid setup. Mind I found that the Pinebook Pro also has the same design as the Helios64 this time around the syr837/syr838 ... I begin to wonder if either they are all broken (could be the amount of stress of a NAS ethernet or raid10 pcie is not that common) or if this is not the issue at stake.

Moved post to unsupported/community maintained. This is not a supported board. My mistake, misread the post. This is pine64 not pinebook a64. That board should be supported but the forum structure isn't up to date. I have added the correct tag for the post, but left it in the original locatation.

Also on 1st class hardware it does not go without issues: https://www.google.com/search?q=why+kernel+upgrades+breaks+features On trash ultra cheap and forgotten hardware, where Armbian is trying to make a difference, breakage % is significantly bigger. Every kernel, that is work of thousands of people (some forget to test changes), breaks features even we invest tens of thousands of hours into stabilizing it. There is virtually no support from industry and no support from end users, but we still managed to build automated monitor for upgrades on many boards in automated way: https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results Sadly, we don't test Pinebook, not complex functions as this and not all possible upgrades. Expanding testing to that and patching would cost additional few millions which is simply not possible to secure from this. In past year, nobody applied to serve as test engineer to develop this further. Other Linux distributions are far far away even from this. Install Armbian on a desktop PC.

!!! Warning !!!: Think twice before you upgrade kernel on your PineBook Pro. After years unfortunately I decided to unlock upgrades Armbian Kernels and upgraded kernel to the newest one (current) - 5.15.93. After reboot Armbian couldn't find my encrypted root disk and booting ended every time in (initramfs). I installed again kernel 5.10.60 #21.08.1 and Armbian finds my encrypted disk again. Of course still there is no information that I have to enter the password to unlock disk but only black screen. Happily I know that I have to enter the password when the screen is black. Every upgrade of Armbian is connected with a dose of stress that I'll have to fix my computer. I thought that every following kernel should fix errors not create them.

Description Debian sid desktops have been failing to build for a while due to a dependency issue with ghostscript-x this package has been abandoned... or mostly abandoned.. see Debian Bug #1022718 Removed package from base desktop package lists... Resolves error message below The following packages have unmet dependencies: ghostscript-x : Depends: ghostscript (= 10.01.2~dfsg-1) but 10.02.1~dfsg-1 is to be installed E: Unable to correct problems, you have held broken packages. tested with ./compile.sh build BOARD=pinebook-pro BRANCH=edge BUILD_DESKTOP=yes \ DESKTOP_APPGROUPS_SELECTED='3dsupport browsers internet multimedia' DESKTOP_ENVIRONMENT=cinnamon \ DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base RELEASE=sid View the full article

hi, make sure you have all the kernel modules in your initramfs as listed here: https://github.com/NixOS/nixos-hardware/blob/master/pine64/pinebook-pro/default.nix i had the same issue with my archilnux installation until i included all of them

I found a way to boot after having deleted the U-boot partition, which prevents any useful boot to allow repair. I could then complete the armbian install. This applies to my Pinebook A64, 14" (not the pro pinebook - i cant test that) After removing the U-boot partition, it would only boot to a "busybox" with limited features, not enough to do a repair. I had a copy of armbian jammy on an sd-card, and this had booted OK before my stupid error. But with the SD card inserted, it stilll only booted to the busybox . The trick was to start the boot, and then insert the SD-card mid-boot, and it then booted the working system from the SD-card. During the defective boot, there is a pause with a few lines of text on the screen before it then proceeds with more error messages and into the busybox. I inserted the SD-card during that pause and it completed the boot from the SD-card. (you may need to time this carefully, but it worked on first try for me) Then you have a complete working system and can use armbian-config, > install system to eMMC and it copies the system to the eMMC and fixes the u-boot issue. It will now boot direct from the eMMC. Took me a while to find this trick which I have not seen documented anywhere, but is essential to get a system running to effect a repair.

> Hardware support > Debian 11 comes with Mesa 20.3 which supports the Mali 400 and 450 GPUs via the Lima driver, and various Mali G-series and T-series GPUs via the Panfrost driver. This will cover most modern ARM SoCs, including those found in the Pinebook and Pinebook Pro devices. Panfrost supports the Mali T720 (only up to OpenGL 2.1 and OpenGL ES 2.0), Mali T760, Mali T820, Mali T860, Mali G72, Mali G31, and Mali G52. PanfrostLima - Debian Wiki https://wiki.debian.org/PanfrostLima Can I just switch to Armbian Debian 11 and install Panfrost driver to enable GPU on nano pi r4s?

Description This brings early support for Linux kernel v6.5 for allwinner boards. Following patches are changed Megous patches: disabled patches.megous/video-fbdev-eInk-display-driver-for-A13-based-PocketBooks.patch to prevent build failure. Will work on re-enabling the same Fixes patches: disabled Fix-depends-only-ARM-eInk-display-FB.patch as it changes code introduce by patch disabled above Armbian patches: disabled drv-clk-sunxi-ng-ccu-sun50i-a64-revert-ccu-Pinebook-A64.patch due to patch application failure. Will check if its still needed. Need help from someone who has a PInebook A64 for the same. removed drv-pmic-add-axp313a.patch as it is upstreamed reworked the overlay support patches to reuse the upstream dtbo support. Due to this rework, overlay patches are updated to use dtso as the file extension Config change: Enabled CW1200 wireless driver as this might bring support for xradio xr819 due to patches from megous kernel How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Build succeeds Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Hi, on my Pinebook Pro with Armbian, I would like to use AesCrypt like on all my other Linux and Windows and Android systems, but here on Armbian, I need some support... - AesCrypt seems not to be available as deb package in Armbian and also Debian repos, right? - install AesCrypt directly from AesCrypt website as deb package with gdebi doesn"t work, guess because it is for x86 only - so I would like to make use of pyAesCryt as module in my Python script - the way as I know it from Archlinux and Manjaro, pip install pyAesCrypt does not work, get a message "environment is externally managed, not Debian-packaged software has to be installed via pipx" (I don't know what "externally managed environment" means, seems to special in Debian / Armbian. Is there a good documentation?) - now, pipx install pyAesCryt installs pyAesCryt sucessfully, and I also did the recommended pipx ensurepath - but, pyAesCrypt is not listed as installed module and - with adapted calls in my methods (aescrypt to pyaescrypt) and an module import import pyAesCrypt after starting the script, when it comes to the call, an error message says " no such module" Any help would be much appreciated!

I verify this change on Orangepi-800. Description Upstream don't have this clk source, and each rk3399 SBC with external codec are working. one example is Pinebook Pro, same codec es8316 used. I also verify it on my opi-800. I don't have the board thus not able to test on opi-4 and opi-4-lts. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

The boot loader from Armbian, is it included on the Bookworm image for pinebook pro? So if I reset the SPI flash to all FF's (the device was shipped that way) and dd the Armbian_23.5.1_Pinebook-pro_bookworm_current_6.1.30_xfce_desktop.img to the EMMC (overwriting Manjaro), there is a boot loader that provides the functionality to default-boot the Armbian on the EMMC, and offers a option to boot from SD card during boot process?

# Pinebook Pro testing ## Armbian_23.5.0-trunk.219_Pinebook-pro_jammy_current_6.1.29_gnome_desktop - Boots live disk [x] - Installs to eMMC - ext4 [x] - Fn keys works [] : NOTE F9 and F10 are swapped - Fn1 [x] - Fn2 [x] - Fn3 [] - Fn4 [x] - Fn5 [x] - Fn6 [x] - Fn7 [x] - Fn8 [] - Fn9 [] - Fn10 [] - Fn11 [] - Fn12 [] - Wi-Fi works [x] - Bluetooth works [] - Touchpad works [x] - Ports - USB-C - data [x] - USB-C - power [x] - USB-A - data [x] BUG: Screen locking does not work without GDM. ## Armbian_23.5.0-trunk.219_Pinebook-pro_jammy_current_6.1.29_xfce_desktop - Boots live disk [x] - Installs to eMMC - ext4 [x] - Fn keys works [] : NOTE F9 and F10 are swapped - ESC [] - Fn1 [x] - Fn2 [x] - Fn3 [x] - Fn4 [] - Fn5 [] - Fn6 [] - Fn7 [x] - Fn8 [] - Fn9 [] - Fn10 [] - Fn11 [] - Fn12 [] - Wi-Fi works [x] - Bluetooth works [] - Touchpad works [x] - Ports - USB-C - data [x] - USB-C - power [x] - USB-A - data [x] BUG1: Ubuntu artwork is being used instead of Armbian during live disk boot once in the desktop. Shows the Ubuntu artwork during boot once installed to eMMC, it does show Armbian artwork at login screen/desktop. BUG2: Touchpad is very jumpy. ## Armbian_23.5.0-trunk.219_Pinebook-pro_jammy_current_6.1.29_i3-wm_desktop - Boots live disk [x] - Installs to eMMC - ext4 [x] - Fn keys works [] : NOTE F9 and F10 are swapped - Fn1 [x] - Fn2 [x] - Fn3 [x] - Fn4 [] - Fn5 [] - Fn6 [] - Fn7 [x] - Fn8 [] - Fn9 [] - Fn10 [] - Fn11 [] - Fn12 [] - Wi-Fi works [x] - Bluetooth works [] - Touchpad works [x] - Ports - USB-C - data [x] - USB-C - power [x] - USB-A - data [x] BUG1: Battery indicator says no battery, I have opened a report of it here: https://armbian.atlassian.net/browse/AR-1756 BUG2: Touchpad is very jumpy. # Not tested yet ## Armbian_23.5.0-trunk.219_Pinebook-pro_jammy_current_6.1.29_minimal - Boots live disk [] - Installs to eMMC [] - Fn keys works [] - Fn1 [] - Fn2 [] - Fn3 [] - Fn4 [] - Fn5 [] - Fn6 [] - Fn7 [] - Fn8 [] - Fn9 [] - Fn10 [] - Fn11 [] - Fn12 [] - Wi-Fi works [] - Bluetooth works [] - Touchpad works [] - Ports - USB-C - data [] - USB-C - power [] - USB-A - data []

Not necessarily. It depends on what is on the eMMC. The order you described would work only if there is a boot loader on eMMC that checks for microSD presence and points there if found. If however the boot loader on eMMC is dumb and doesn't care about other bootable devices it just runs through, which can be a big issue if the eMMC module cannot disabled or removed from the board. I faced a similar issue long time ago when I had a pinebook pro in my collection. The fixed boot order of rk3399 is SPI, eMMC, SD. RK3588 might be similar. This default behavior cannot be altered, only worked around by telling the boot loader, that is going to be flashed to SPI or eMMC, to look for microSD first.

Description Yes, we have documented the maintainers in armbian/documentation. But it seem like that some of them don't maintain anymore. Use a separated repos make us forget to update it. So let's document here. What's more, defining this make us easier to update .github/CODEOWNERS The way to find out the BOARD_MAINTAINER has documented in the commit messages. The script to do this #!/bin/bash SRC="$(realpath "${BASH_SOURCE%/*}/../")" readarray -t members < <(curl -L -H "Accept: application/vnd.github+json" -H "Authorization: Bearer ${TOKEN}" "https://api.github.com/orgs/armbian/members?per_page=100" | jq -r .[].login) doc="$(curl -L https://github.com/armbian/documentation/raw/master/docs/Release_Board-Maintainers.md)" function set_maintainer() { local board_config="$1" local maintainers="$2" if ! grep "BOARD_MAINTAINER" "${SRC}/config/boards/${board_config}" >/dev/null 2>&1; then sed -i "s|\(.*\)\(BOARDFAMILY=.*\)|\1\2\n\1BOARD_MAINTAINER=\"${maintainers}\"|" "${SRC}/config/boards/${board_config}" else : # Have set # Replace # sed -i "s|BOARD_MAINTAINER=.*|BOARD_MAINTAINER=\"${maintainers}\"|" "${SRC}/config/boards/${board_config}" fi } while read -r board_config; do type="${board_config##*.}" [[ "conf wip csc eos tvb" == *"${type}"* ]] || continue BOARD="${board_config%.*}" echo -e "\n${board_config}" documented_maintainer=() readarray -t documented_maintainer < <(echo "${doc}" | grep "| ${BOARD} *|" | cut -d'|' -f4 | sed 's/^ *\([^ ]*\) *$/\1/') echo -e "\tDocumented: ${documented_maintainer[*]}" if [[ ! -f ".gh/${board_config}" ]]; then gh_commits="$(curl -H "Accept: application/vnd.github+json" -H "Authorization: Bearer ${TOKEN}" "https://api.github.com/repos/armbian/build/commits?per_page=100&path=config/boards/${board_config}")" echo "${gh_commits}" >".gh/${board_config}" else gh_commits="$(cat ".gh/${board_config}")" fi authors="$(echo "${gh_commits}" | jq -r .[].author.login)" creator="$(echo "${authors}" | tail -1)" echo -e "\tCreator: ${creator}" most_commit="$(echo "${authors}" | uniq -c | sort -nr | awk '($1 >= 3) {print $2}' | head -1)" echo -e "\tMost commit: ${most_commit}" other_commiters=() readarray -t other_commiters < <(echo "${authors}" | grep -v "^${creator}$") if [[ -n "${documented_maintainer}" ]]; then for m in "${documented_maintainer[@]}"; do if [[ "${members[*]}" != *"${m}"* ]]; then echo -e "${board_config}: ${m} is not our member" >&2 fi done set_maintainer "${board_config}" "${documented_maintainer[*]}" continue fi if [[ "${creator}" == "${most_commit}" ]]; then if [[ "${members[*]}" != *"${creator}"* ]]; then echo -e "${board_config}: ${creator} is not our member" >&2 fi set_maintainer "${board_config}" "${creator}" continue fi if [ -z "${other_commiters[*]}" ]; then if [[ "${members[*]}" != *"${creator}"* ]]; then echo -e "${board_config}: ${creator} is not our member" >&2 fi set_maintainer "${board_config}" "${creator}" fi set_maintainer "${board_config}" "" done < <(ls "${SRC}/config/boards/") Raw output aml-s9xx-box.tvb Documented: Creator: SteeManMI Most commit: bananapicm4io.conf Documented: Creator: superna9999 Most commit: bananapi.conf Documented: janprunk Creator: zador-blood-stained Most commit: igorpecovnik bananapim1plus.csc Documented: Creator: zador-blood-stained Most commit: igorpecovnik bananapim2.eos Documented: Creator: igorpecovnik Most commit: igorpecovnik bananapim2plus.conf Documented: igorpecovnik Creator: zador-blood-stained Most commit: igorpecovnik bananapim2pro.conf Documented: igorpecovnik Creator: rpardini Most commit: bananapim2s.wip Documented: Creator: igorpecovnik Most commit: bananapim2ultra.csc Documented: Creator: igorpecovnik Most commit: igorpecovnik bananapim2zero.csc Documented: Creator: igorpecovnik Most commit: igorpecovnik bananapim3.conf Documented: AaronNGray Creator: igorpecovnik Most commit: bananapim5.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: igorpecovnik bananapim64.conf Documented: devdotnetorg Creator: igorpecovnik Most commit: igorpecovnik bananapipro.conf Documented: teknoid Creator: zador-blood-stained Most commit: igorpecovnik bananapir2.csc Documented: Creator: igorpecovnik Most commit: igorpecovnik bananapir2pro.conf Documented: Creator: 150balbes Most commit: beaglev.csc Documented: Creator: Rafal-Hacus Most commit: beelinkx2.tvb Documented: Creator: igorpecovnik Most commit: igorpecovnik clearfogbase.conf Documented: heisath Creator: zador-blood-stained Most commit: igorpecovnik clearfogpro.conf Documented: heisath Creator: zador-blood-stained Most commit: igorpecovnik clockworkpi-a06.csc Documented: littlecxm Creator: Rafal-Hacus Most commit: cubieboard2.csc Documented: Creator: igorpecovnik Most commit: cubieboard4.csc Documented: Creator: igorpecovnik Most commit: igorpecovnik cubieboard.conf Documented: Creator: zador-blood-stained Most commit: igorpecovnik cubietruck.csc Documented: Creator: EvilOlaf Most commit: cubietruckplus.csc Documented: Creator: igorpecovnik Most commit: igorpecovnik cubox-i.csc Documented: Creator: igorpecovnik Most commit: espressobin.conf Documented: ManoftheSea Creator: igorpecovnik Most commit: igorpecovnik fe-som-rk3399.eos Documented: Creator: igorpecovnik Most commit: firefly-rk3399.conf Documented: 150balbes Creator: igorpecovnik Most commit: helios4.conf Documented: heisath Creator: igorpecovnik Most commit: igorpecovnik helios64.csc Documented: Creator: EvilOlaf Most commit: hinlink-h88k.csc Documented: Creator: amazingfate Most commit: imx7sabre.eos Documented: Creator: igorpecovnik Most commit: jethubj100.conf Documented: jethome-ru Creator: adeepn Most commit: jethubj80.conf Documented: jethome-ru Creator: adeepn Most commit: jetson-nano.conf Documented: 150balbes Creator: igorpecovnik Most commit: khadas-edge2.wip Documented: Creator: 150balbes Most commit: khadas-edge.csc Documented: igorpecovnik Creator: Rafal-Hacus Most commit: khadas-vim1.conf Documented: Creator: lanefu Most commit: khadas-vim2.conf Documented: Creator: lanefu Most commit: khadas-vim3.conf Documented: NicoD-SBC Creator: igorpecovnik Most commit: khadas-vim3l.conf Documented: rpardini Creator: lanefu Most commit: lafrite.conf Documented: Tonymac32 Creator: igorpecovnik Most commit: igorpecovnik lamobo-r1.eos Documented: Creator: igorpecovnik Most commit: igorpecovnik lepotato.conf Documented: Tonymac32 Creator: igorpecovnik Most commit: igorpecovnik lime2.csc Documented: igorpecovnik Creator: EvilOlaf Most commit: lime-a10.eos Documented: Creator: igorpecovnik Most commit: igorpecovnik lime-a33.csc Documented: Creator: igorpecovnik Most commit: igorpecovnik lime-a64.csc Documented: igorpecovnik Creator: igorpecovnik Most commit: lime.csc Documented: Creator: igorpecovnik Most commit: igorpecovnik macchiatobin-doubleshot.csc Documented: Creator: jwzawadzki Most commit: igorpecovnik mangopi-mq.wip Documented: Creator: rpardini Most commit: mekotronics-r58-minipc.wip Documented: Creator: rpardini Most commit: mekotronics-r58x-4g.wip Documented: Creator: rpardini Most commit: mekotronics-r58x.wip Documented: Creator: rpardini Most commit: melea1000.csc Documented: Creator: igorpecovnik Most commit: igorpecovnik micro.csc Documented: Creator: igorpecovnik Most commit: igorpecovnik microzed.eos Documented: Creator: igorpecovnik Most commit: miqi.eos Documented: Creator: igorpecovnik Most commit: igorpecovnik mk808c.csc Documented: Creator: zador-blood-stained Most commit: igorpecovnik nanopct3.eos Documented: Creator: igorpecovnik Most commit: nanopct3plus.eos Documented: Creator: igorpecovnik Most commit: nanopct4.conf Documented: 150balbes Creator: igorpecovnik Most commit: igorpecovnik nanopia64.csc Documented: Creator: guidol70 Most commit: nanopiair.csc Documented: Creator: EvilOlaf Most commit: nanopiduo2.csc Documented: Creator: EvilOlaf Most commit: nanopiduo.conf Documented: sgjava Creator: null Most commit: igorpecovnik nanopifire3.eos Documented: Creator: igorpecovnik Most commit: nanopik1plus.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: igorpecovnik nanopik2-s905.csc Documented: Creator: igorpecovnik Most commit: nanopim1.eos Documented: Creator: igorpecovnik Most commit: igorpecovnik nanopim1plus2.eos Documented: Creator: igorpecovnik Most commit: igorpecovnik nanopim1plus.eos Documented: Creator: igorpecovnik Most commit: igorpecovnik nanopim3.eos Documented: Creator: igorpecovnik Most commit: igorpecovnik nanopim4.conf Documented: piter75 Creator: igorpecovnik Most commit: igorpecovnik nanopim4v2.csc Documented: piter75 Creator: Rafal-Hacus Most commit: nanopineo2black.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: nanopineo2.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: igorpecovnik nanopineo3.conf Documented: lpirl Creator: igorpecovnik Most commit: nanopineo4.csc Documented: Creator: igorpecovnik Most commit: nanopineo.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: igorpecovnik nanopineocore2.csc Documented: Creator: EvilOlaf Most commit: nanopineoplus2.conf Documented: teknoid Creator: igorpecovnik Most commit: igorpecovnik nanopi-r1.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: igorpecovnik nanopi-r1s-h5.conf Documented: Creator: aiamadeus Most commit: nanopi-r2c.conf Documented: igorpecovnik Creator: rickliu2000 Most commit: nanopi-r2s.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: nanopi-r4s.conf Documented: littlecxm piter75 Creator: EvilOlaf Most commit: nanopi-r6s.wip Documented: Creator: efectn Most commit: nezha.wip Documented: Creator: rpardini Most commit: odroidc1.eos Documented: Creator: igorpecovnik Most commit: igorpecovnik odroidc2.conf Documented: NicoD-SBC Creator: zador-blood-stained Most commit: igorpecovnik odroidc4.conf Documented: Technicavolous Creator: superna9999 Most commit: igorpecovnik odroidhc4.conf Documented: rpardini Technicavolous Creator: igorpecovnik Most commit: odroidm1.wip Documented: Creator: igorpecovnik Most commit: odroidn2.conf Documented: rpardini Creator: igorpecovnik Most commit: igorpecovnik odroidxu4.conf Documented: igorpecovnik joekhoobyar Creator: zador-blood-stained Most commit: igorpecovnik olimex-som204-a20.eos Documented: Creator: igorpecovnik Most commit: olimex-som-a20.eos Documented: Creator: igorpecovnik Most commit: olimex-teres-a64.conf Documented: Creator: Kreyren Most commit: olinux-som-a13.csc Documented: Creator: igorpecovnik Most commit: igorpecovnik onecloud.csc Documented: Creator: hzyitc Most commit: hzyitc orangepi2.csc Documented: Creator: EvilOlaf Most commit: orangepi3.csc Documented: igorpecovnik Creator: EvilOlaf Most commit: orangepi3-lts.csc Documented: afaulkner420 Creator: Rafal-Hacus Most commit: orangepi4.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: igorpecovnik orangepi4-lts.conf Documented: jock Creator: paolosabatino Most commit: orangepi5.conf Documented: Creator: efectn Most commit: orangepi.eos Documented: Creator: zador-blood-stained Most commit: igorpecovnik orangepilite2.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: orangepilite.csc Documented: igorpecovnik Creator: EvilOlaf Most commit: orangepimini.eos Documented: Creator: zador-blood-stained Most commit: igorpecovnik orangepione.csc Documented: igorpecovnik Creator: EvilOlaf Most commit: orangepioneplus.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: orangepipc2.csc Documented: igorpecovnik Creator: EvilOlaf Most commit: orangepipc.conf Documented: lbmendes Creator: zador-blood-stained Most commit: igorpecovnik orangepipcplus.conf Documented: igorpecovnik Creator: null Most commit: igorpecovnik orangepiplus2e.conf Documented: igorpecovnik Creator: null Most commit: igorpecovnik orangepiplus.csc Documented: Creator: EvilOlaf Most commit: orangepiprime.csc Documented: igorpecovnik Creator: Rafal-Hacus Most commit: orangepi-r1.conf Documented: schwar3kat Creator: null Most commit: igorpecovnik orangepi-r1plus.conf Documented: Creator: aiamadeus Most commit: orangepi-r1plus-lts.conf Documented: schwar3kat Creator: schwar3kat Most commit: orangepi-rk3399.csc Documented: Creator: EvilOlaf Most commit: orangepiwin.csc Documented: Creator: igorpecovnik Most commit: orangepizero2.conf Documented: krachlatte qiurui Creator: igorpecovnik Most commit: orangepizero.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: igorpecovnik orangepizeroplus2-h3.csc Documented: agolubchyk Creator: EvilOlaf Most commit: orangepizeroplus2-h5.csc Documented: Creator: EvilOlaf Most commit: orangepizeroplus.conf Documented: schwar3kat Creator: igorpecovnik Most commit: igorpecovnik pcduino2.eos Documented: Creator: igorpecovnik Most commit: igorpecovnik pcduino3.csc Documented: Creator: null Most commit: igorpecovnik pcduino3nano.eos Documented: Creator: igorpecovnik Most commit: igorpecovnik pine64.conf Documented: janprunk Creator: zador-blood-stained Most commit: igorpecovnik pine64so.conf Documented: Creator: zador-blood-stained Most commit: igorpecovnik pinebook-a64.csc Documented: Creator: igorpecovnik Most commit: pinebook-pro.conf Documented: Creator: igorpecovnik Most commit: pinecube.csc Documented: Creator: Icenowy Most commit: pineh64-b.conf Documented: Creator: igorpecovnik Most commit: igorpecovnik pineh64.csc Documented: Creator: igorpecovnik Most commit: qemu-uboot-arm64.wip Documented: Creator: rpardini Most commit: qemu-uboot-x86.wip Documented: Creator: rpardini Most commit: quartz64a.wip Documented: Creator: 150balbes Most commit: quartz64b.wip Documented: Creator: 150balbes Most commit: radxa-e25.wip Documented: Creator: amazingfate Most commit: radxa-zero2.wip Documented: monkaBlyat Creator: igorpecovnik Most commit: radxa-zero.conf Documented: engineer-80 Creator: engineer-80 Most commit: recore.csc Documented: Creator: null Most commit: renegade.conf Documented: Tonymac32 Creator: igorpecovnik Most commit: igorpecovnik rk322x-box.tvb Documented: Creator: paolosabatino Most commit: rk3318-box.tvb Documented: Creator: paolosabatino Most commit: rock-3a.conf Documented: catalinii ZazaBr vamzii Creator: igorpecovnik Most commit: amazingfate rock-5b.conf Documented: Creator: igorpecovnik Most commit: rock64.conf Documented: clee Creator: igorpecovnik Most commit: igorpecovnik rockpi-4a.conf Documented: clee Creator: igorpecovnik Most commit: igorpecovnik rockpi-4b.conf Documented: Creator: igorpecovnik Most commit: igorpecovnik rockpi-4bplus.csc Documented: Creator: lanefu Most commit: rockpi-4c.conf Documented: clee Creator: igorpecovnik Most commit: rockpi-4cplus.csc Documented: Creator: igorpecovnik Most commit: rockpi-e.conf Documented: Creator: igorpecovnik Most commit: rockpi-n10.csc Documented: Creator: psztoch Most commit: rockpi-s.conf Documented: brentr Creator: igorpecovnik Most commit: igorpecovnik rockpro64.conf Documented: joekhoobyar Creator: igorpecovnik Most commit: igorpecovnik roc-rk3399-pc.csc Documented: Creator: piter75 Most commit: piter75 rpi4b.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: star64.wip Documented: Creator: rpardini Most commit: station-m1.conf Documented: 150balbes Creator: EvilOlaf Most commit: 150balbes station-m2.conf Documented: 150balbes Creator: 150balbes Most commit: station-m3.conf Documented: Creator: 150balbes Most commit: station-p1.conf Documented: 150balbes Creator: EvilOlaf Most commit: station-p2.conf Documented: 150balbes Creator: 150balbes Most commit: sunvell-r69.tvb Documented: Creator: igorpecovnik Most commit: tinkerboard-2.wip Documented: Creator: Tonymac32 Most commit: tinkerboard.conf Documented: Tonymac32 paolosabatino Creator: igorpecovnik Most commit: igorpecovnik tritium-h3.conf Documented: Tonymac32 Creator: igorpecovnik Most commit: igorpecovnik tritium-h5.conf Documented: Tonymac32 Creator: igorpecovnik Most commit: igorpecovnik udoo.csc Documented: Creator: EvilOlaf Most commit: uefi-arm64.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: uefi-riscv64.conf Documented: Creator: igorpecovnik Most commit: uefi-x86.conf Documented: igorpecovnik Creator: igorpecovnik Most commit: unleashed.wip Documented: Creator: rpardini Most commit: unmatched.wip Documented: Creator: rpardini Most commit: virtual-qemu.eos Documented: Creator: rpardini Most commit: visionfive2.wip Documented: Creator: rpardini Most commit: visionfive.wip Documented: Creator: rpardini Most commit: xt-q8l-v10.tvb Documented: Creator: igorpecovnik Most commit: igorpecovnik z28pro.tvb Documented: Creator: igorpecovnik Most commit: igorpecovnik zeropi.csc Documented: igorpecovnik Creator: Rafal-Hacus Most commit: Here is the list who documented in armbian/documentation but aren't our members. So he/she can't add to .github/CODEOWNERS due to he/she don't have the access to write to the repos. bananapim3.conf: AaronNGray is not our member bananapim64.conf: devdotnetorg is not our member clearfogbase.conf: heisath is not our member clearfogpro.conf: heisath is not our member helios4.conf: heisath is not our member jethubj100.conf: jethome-ru is not our member jethubj80.conf: jethome-ru is not our member khadas-vim3.conf: NicoD-SBC is not our member nanopineo3.conf: lpirl is not our member odroidc2.conf: NicoD-SBC is not our member odroidc4.conf: Technicavolous is not our member odroidhc4.conf: Technicavolous is not our member orangepi3-lts.csc: afaulkner420 is not our member orangepi4-lts.conf: jock is not our member orangepipc.conf: lbmendes is not our member orangepizero2.conf: krachlatte is not our member orangepizeroplus2-h3.csc: agolubchyk is not our member radxa-zero2.wip: monkaBlyat is not our member radxa-zero.conf: engineer-80 is not our member rock-3a.conf: ZazaBr is not our member rock-3a.conf: vamzii is not our member rock64.conf: clee is not our member rockpi-4a.conf: clee is not our member rockpi-4c.conf: clee is not our member How Has This Been Tested? Uncessary. Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [X] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Some patches were triggering warning in the armbian build system for kernel 6.1 in rockchip64 family. This PR rework those patches to avoid warnings during kernel patching, does not introduce new features, just cleans some things up. Also the Pinebook Pro patch that was addressing the external control (extcon) for usb3 type-c connector is now split into a patch that adds the device tree bits for pinebook and another patch that implements the feature, since the feature is used in other rk3399 boards. How Has This Been Tested? [x] Debian bullseye minimal image has been built and tested on Orange Pi 4 LTS Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article