SBC News

Description This PR configures onboard button as power button on NanoPi Duo2 so that the board can be brought back from suspended state or can be rebooted after shutdown. Also enables ethernet as request on the forum 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] Booted on NanoPi Duo2 and tested button works at sleep and poweroff 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 …

Adds the needed files support the spidev on the NanoPi Neo3 with a different address. Tested on my own NanoPi Neo3 with a LoRaWAN concentrator connected via SPI. I am unsure about the changes in rockchip-fixup.scr-cmd. It needs a user to use a not very convenient device "number" specific to the NanoPi Neo3. But I did not know how to do this differently without possibly breaking other boards. Any suggestions on how this is usually done are welcome. Still it seems I am the only person on this planet to use SPI on the NanoPi Neo3 as no one else seems to have reported anything... Any constructive feedback is very welcome. View the full article

Description FriendlyElec ships their devices with the latest blobs. Trying to run an Armbian image on this board with the old blobs might cause issues. @rpardini run into those issues with the NanoPC T6 and fixed it in https://github.com/armbian/build/pull/6711 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] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Fixed the problem that nanopi r1 cannot boot from emmc. The reason is that uboot uses nanopineo's defconfig and dts when compiling so that it lacks the mmc2 definition. A topic on the forum about this issues: https://forum.armbian.com/topic/28704-nanopi-r1-emmc-install-fails-to-start How Has This Been Tested? Build and update u-boot Checklist: [x] 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 [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merg…

Description update overlay prefix due to SoC family change remove rkbin repo override now that armbian rkbin repo has blobs install headers by default on both boards View the full article

Description now that 6.6.y is -current.. Need to add -current as a build target. tested works.. 6.7.0 -edge is weird-broken. but that's for discussion here. View the full article

Description nanopi-r5c u-boot patch dir has been detached to allow version bump to 2024.07 and add kaslr support patchset this PR includes general 2024.07 patches to board such as: general-btrfs-fix-out-of-bounds-write.patch general-dwc-otg-usb-fix.patch general-dw-hdmi-disable.patch general-fix-inno-phy-macro.patch note to users and maintainers: sorry for forgetting to include those patches in my first PR How Has This Been Tested? [x] Succesfully built and ran u-boot 2024.07 Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no n…

bump u-boot to 2024.07 patch in kaslrseed support enable kaslrseed in nanopi-r5c-rk3568-defconfig set CONFIG_RANDOMIZE_BASE=y(kaslr) (kernel) Reference patchset: 1949474 Credit: Tim Harvey How Has This Been Tested? [x] Built and run edge kernel + u-boot --> KASLR enabled Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

nanopi-r5s: bump blobs & u-boot enhancements for UMS/otg/bootorder nanopi-r5s: bump u-boot from v2024.04-rc3 to v2024.04 "final" nanopi-r5s: add ROCKUSB_BLOB (for Maskrom / rkdevflash extension flashing) nanopi-r5s: bump up blobs 1.18/1.43 -> 1.21/1.44 nanopi-r5s: make u-boot fancy (ums, rockusb, leds, tcp networking stuff) use preboot to flash all leds for 100ms, then leave power LED on nanopi-r5s: u-boot: 2024.04: boot order: usb -> sd -> nvme -> scsi -> emmc nanopi-r5s: u-boot: 2024.04: usb otg in u-boot for working UMS/RockUSB patch/u-boot/v2024.04: rewrite patches, no changes View the full article

nanopi-r5s: u-boot: pci enum in preboot; disable armbian-led-state nanopi-r5s: u-boot: pci enum in preboot; disable armbian-led-state pci enum in preboot; required for working m.2 when booting some older kernels this board has an overlay (DEFAULT_OVERLAYS="nanopi-r5s-leds") to drive the LEDs, disable armbian-led-state service View the full article

Description The same configuration has been working fine for the similar NanoPi R6C for a while. Users have reported issues with the vendor U-Boot not able to boot. Ref: https://forum.armbian.com/topic/42105-report-bug-in-nanopi-r6s/ How Has This Been Tested? [x] ./compile.sh BOARD=nanopi-r6s BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie uboot 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 [ ] My changes generate no new warnings [x] Any dependent changes have been merged and publish…

Description Created udev config for renaming interfaces to WAN, LAN1, LAN2 Created device tree overlay rockchip-nanopi-r5s-leds for enabling front panel status LED's for NICs. enabled by default How Has This Been Tested? Built image. Leds work when cable plugged in. interface names are friendly root@nanopi-r5s:~# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wan: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 link/ether 12:ad:f7:2a:2f:a3 brd ff:ff:ff:ff:ff:ff altname…

Description Resolves #5890 Jira reference number AR-1906 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] Test on RPi5 with mantic image. The iwconfig shows output shows that power management is off as expected 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 down…

networking: main-config: introduce NETWORKING_STACK to control network exts; allow "none"; fix typo networking: exts: introduce sanity checks, debug info protect against enabling networking exts directly debug logging fix typo in ext name networking: main-config: introduce NETWORKING_STACK to control network exts; allow "none"; fix typo NETWORKING_STACK can be set to none (in config phase, pre-extensions) to not-add any networking extensions keep defaulting to systemd-networkd if BUILD_MINIMAL and NetworkManager otherwise fix typo in extension name add NETWORKING_STACK to change-tracking View the full article

Description Correcting hook locations in https://github.com/armbian/build/pull/6756 Jira reference number AR-2384 How Has This Been Tested? [x] Manual image assembly Checklist: [x] My changes generate no new warnings View the full article

No descriptionView the full article

Description There is no official SDK released for rk3576 so we have to use kernel and uboot from rockchip's internal (beta I guess) repo. I wish this rk3576 family can get deleted when rockchip release new SDK for all rk35xx socs in the future. I created kernel config based on rk35xx-vendor and enabled rk3576 soc support on top of it. 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] ./compile.sh BOARD=armsom-sige5 BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=bookworm KERNEL_GIT=shallow [ ] board booting is not yet…

Add possibility of nilfs2 fs based image generation. nilfs2 automatically does snapshots and allow to restore any file to state back in time until it purged. 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. [ ] Test A [ ] Test B 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 [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and publ…

Description I'm running ./conmpile.sh on a CentOS7 host with selinux. I got this error when I have a fat32 boot partition: rsync: [receiver] rsync_xal_set: lsetxattr("/armbian/.tmp/mount-9164f469-ce45-41ce-af3d-07556d8996aa/boot","security.selinux") failed: Operation not supported (95) Since we will rsync boot partition later it should be harmless if we just exclude the whole /boot directory. Related issue from other project: https://github.com/RPi-Distro/pi-gen/pull/261 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 success on my selinux enabled cento…

Description Hello! Here is a patch that will add the device tree and defconfig for the NanoPC T6 in U-Boot, with support for booting from an NVMe SSD. Works excellent with https://github.com/armbian/linux-rockchip/pull/78. How Has This Been Tested? Note: My T6 did not come with a spi nor chip, so I soldered it myself. [x] Flashed the bootloader to the spi nor. [x] Booting from NVMe works as expected with the bootloader in the spi nor. 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 d…

Description Proposed by mboehmer How Has This Been Tested? Not tested yet. 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Renaming network device to eth0 How Has This Been Tested? [x] Generated image Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Maint, moving folder to expected location, add upstream patch. @belegdol Jira reference number AR-2353 How Has This Been Tested? [ ] CI Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Maint. How Has This Been Tested? [x] Patch 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Maint. How Has This Been Tested? Not tested. Removing what was added by Hardkernel. 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] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

odroidhc4: bump to u-boot v2024.04; drop most defconfig patches in favor of hooks odroidhc4: bump to u-boot v2024.04; drop most defconfig patches in favor of hooks add pre_config_uboot_target hook for switching BOOTCONFIG across the two targets adapt UBOOT_TARGET_MAP to not call the defconfig Makefile targets directly, instead, just do a variable assignment (ignored by Make) otherwise, when using the defconfig directly in the UBOOT_TARGET_MAP, the post_config_uboot_target .config changes are overwritten when Make is called only patch left is boot usb-nvme-scsi/sata first (still done in meson64.h) remove FIP handling from family file meson-sm1.conf into board file hoo…

Description Recently, I accidentally erased an SPI flash with an bootloader installed and tried to reinstall the latest bootloader. But it did not recognize the attached disks and proceeded to TFTP Boot. Only by stopping autoboot and hot-swapping the disks or reattaching did the bootloader recognize it, and I was then able to boot with the command. I investigated and found that the problem occured after U-Boot was updated to v2023.01. This issue has been resolved by applying a patch that was previously used in v2022.07. How Has This Been Tested? By compiling U-Boot from trunk (linux-u-boot-odroidhc4-current_24.2.0-trunk) for v2023.01, v2023.04, v2023.07, v2023.10 and t…

odroidm1: bump to u-boot v2024.07; replace defconfig patches with hook odroidm1: bump to u-boot v2024.07; replace defconfig patches with hook bump "armbian" env to reset env in SPI on first run View the full article

odroidm1/orangepi3b: use default (newer) blobs; rewrite patches; bump -rc u-boot to final patch/u-boot/v2024.04: rewrite patches, no changes odroidm1: remove custom blobs, use defaults; bump u-boot 2024.04-rc3 to 2024.04 final orangepi3b: remove custom blobs, use defaults odroidm1: u-boot: rewrite patches, no changes View the full article

odroidn2l: bump to u-boot v2023.10; boot-usb-first patch now only in board folder odroidn2l: bump to u-boot v2023.10; boot-usb-first patch now only in board folder with this, there are no more boards with v2023.07 View the full article

odroidxu4: fix the custom_kernel_config__hack_odroidxu4_firmware() for version hash @belegdol since you're the expert on xu4, is this even needed anymore? It probably works now, but would be nice to get rid of it. Context: that "firmware copy for xu4" was mixed in the middle of kernel compile logic, and was extracted into a kernel config hook; kernel configs are hashed (for caching) and thus need to work even when kernel_work_dir is not set. The hash component has been added. JIRA: AR-1548 View the full article

Description WireGuard support got lost with one of the recent changes to the Odroid XU4 kernel config. This commit re-adds it as module. Jira reference number [AR-9999] 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] Kernel built with lastest Armbian main branch + this change [x] Tested on Odroid XU4Q with an actual WireGuard server test installation root@OdroidXU4:~# dpkg -l linux-image-current-odroidxu4 ii linux-image-current-odroidxu4 23.11.0-trunk armhf Armbian Linux current kernel image 6.1.61-current-odroidxu4 root@OdroidXU4:~# uname -a Linux …

My effort to implement an official armbian support for OLIMEX Teres A64. How to help Testing of the image To capture any bugs i need testers if you want to help then: 1. Install the provided image on a class 10 A1 or higher SDCard and use it to boot the system using command # dd if=/path/to/file/img of=/dev/SDCARD_HERE conv=sync status=progress && sync * Armbian_23.02.0-trunk_Teres-a64_bullseye_current_5.15.89_minimal.img * Armbian_23.02.0-trunk_Teres-a64_bullseye_current_5.15.89_minimal.img.sha * Armbian_23.02.0-trunk_Teres-a64_bullseye_current_5.15.89_minimal.img.txt DO NOT update/upgrade the system! (apt update or apt upgrade or apt dist-upgrade) * We need …

Description This merge request implements an official support for OLIMEX Teres-A64 by Armbian and assigns myself as the maintainer. Solves the following issues: OS breaking after reboot that is currently present on the weekly builds No audio (Solved through including needed packages and updating debian and community olimex wiki) No active maintainer Removes bloatware introduced from armbian-firmware Before Merge Checklist (Reviewer) [ ] Continuous Deployment [ ] Add weekly build for: [ ] minimal stable debian CLI e.g. BOARD=olimex-teres-a64 BRANCH=current RELEASE=bookworm BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no [ ] Debian testing …

Submitted upon request to make user's life easier Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number [AR-9999] How to test $ git clone https://github.com/Kreyren/armbian-build-kreyren.git -b olimex-A20-OLinuXino-MICRO # Clone the source code with the specified branch # Change directory to the cloned repository $ ./compile.sh BOARD=olimex-a20-olinuxino-micro EXPERT=yes 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 conf…

Description Not sure if others are symlinked or they fail silently. Failed to restart sshd.service: Unit sshd.service not found How Has This Been Tested? [x] Tested on Jammy, Mantic, Bookworm Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Remark: This PR is based off v23.11 for now and will be rebased of main/master branch before review Description Running "uefi-x86" board image on qemu-system-x86_64 --display none --serial stdio ... did not: allow GRUB boot without GUI display display early kernel boot messages on the serial console display the console prompt on serial console Jira reference number: None 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. [ ] Test A: Boot uefi-x86 board image on qemu-system-x86_64 --display none --serial stdio ... [ ] Test B: Boot uefi-x86 board image on qemu-s…

Description Enable Plymouth for onecloud 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 and boot to check 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 [ ] 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 All changes are for onecloud. Rename back to csc Adjust sources config Disable u-boot compilation Support armbianEnv.txt Tweak bootscript Support outbut boot log to HDMI tweak VCC_CORE How Has This Been Tested? [X] Build and burn Checklist: [ ] 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 [ ] 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 Having auto-login isn't always desirable for production images. 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] Booted on a NanoPi R4S Checklist: [X] 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 [ ] 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

Description Instead of requesting to install gcc-or1k-bin package unconditionally, request it only when building images with crust support. Also consolidated crust related configuration into a separate file. Jira reference number AR-1786 How Has This Been Tested? [X] ./compile.sh DOCKER_ARMBIAN_BASE_IMAGE="debian:bullseye" BOARD=nanopineo works as it doesn't need crust support [X] ./compile.sh DOCKER_ARMBIAN_BASE_IMAGE="debian:bullseye" BOARD=nanopiduo2 fails as it bullseye doesn't include gcc-or1k-bin package and hence reported as unsupported system [X] ./compile.sh BOARD=nanopiduo2 works as default release is jammy that has the required package Checklist: [X] My co…

Description Even though git shows a lot of changes, only change is putting the code in if block to make sure that we try to patch the system after we relaunch. Without this I got a password prompt on my MacBook as the system was trying to patch the MacOS. This can be closed if #6076 is ready 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 ar…

Description This exposes the ITC content type provided by hdmi spec to v4l2. This allows user space applications to query the driver using V4L2_CID_DV_RX_IT_CONTENT_TYPE. This way user applications can see not only if a hdmi is plugged in or not, but also what type of video is being transmitted. For my use case specifically, I just want to know if the recieved type is no type (V4L2_DV_IT_CONTENT_TYPE_NO_ITC) or literally anything else. This would let me detect when my main computer's goes to sleep with the hdmi out from the main computer plugged into the OP5+ HDMI in. Without this patch, there's no way to tell that happened, as for my gpu/hdmi plug, it keeps the hot pl…

Description HDMI-rx does not properly report if it is plugged out and says that it is plugged in all the time. The cause is the following. There is an irq that is watching a gpio for 5v high. During the plugout method for the driver, the driver resets the device state. If the irq that is watching for gpio 5 volts is not disabled during this time, it triggers on a transient voltage and sets the driver to run the "High"/plugged in logic. By the time the driver reaches the high logic, the gpio is low again, which resets the cycle by re-calling the plugout method. This is probably why @efectn disabled the log in 0a0eb46 , because it's so noisy and spams the logs. I don't …

Description Open a Jira ticket when GitHub issue is raised, Jira reference number AR-345 How Has This Been Tested? [x] Tested in test repository 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

Description Includes method to compile OpenSBI required for RISCV64 systems The CI failure Lint On Scripts / Shell script analysis (pull_request) is issue not caused by me and it won't be addressed in this merge request Jira reference number [AR-9999] How Has This Been Tested? Used to compile and run: https://github.com/armbian/build/pull/5689 https://github.com/armbian/build/pull/5712 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 warn…

Description 6.1 vendor kernel is not bootable on opi3b. There is a post in forum: https://forum.armbian.com/topic/36332-orangepi3b-kernel-panic-when-trying-to-boot-with-the-new-vendor-kernel6143/#comment-186436 Opi3b is using mainline uboot for all branches which is not compatibale with vendor kernel's npu, ~so I use radxa's rockchip uboot instead and limit mainline uboot to branch edge~. I find that setting vdd_npu with property regulator-always-on will fix the issue. There is also a missing uwe5622 patch on rk35xx family, which will cause kernel panic of sprdbt_tty kernel module. Please describe the tests that you ran to verify your changes. Please also note any relev…

Description This PR adds some patches from Collabora and upstream kernel branch and add initial support for opi5 Jira reference number [AR-9999] 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] OPi5 boots fine [x] SD Card, GMAC, USB, PCIe2, Sata work 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 change…

Description Reapply https://github.com/armbian/build/commit/305886b111ff76a53693a3c171751a8830d106c5 and fix compilation & spi image booting Jira reference number [AR-9999] 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 and boot 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 bee…

Description This PR fixes ES8388 audio on OPi5, add opi5b devicetree and add mainline uboot support. Jira reference number [AR-9999] 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] Boots well with 2024.01-rc4 uboot [x] There are no es8388 errors in dmesg output It would be nice if someone tests SPI flash boot + nvme ssd. I've not tried it because i don't have free M2 ssd rn. rkspi_loader.zip 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 ha…

Description It depends on https://github.com/armbian/linux-rockchip/pull/76 https://github.com/armbian/build/pull/5519#pullrequestreview-1549880906 Jira reference number [AR-9999] 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. [ ] Test A [ ] Test B 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 h…

add support OPI-800 View the full article

Description kASLR is a handy security feature, with no performance downside. (The only downside is some slight inconvenience if you're using KGDB, but if you're the type of person who does kernel step debugging, it seems sane to guess you're already building your own kernel.) If it cannot be enabled due to lack of seed, the kernel will simply print a warning and continue. (See #4306 for more context on what was previously added to get it working on a NanoPi R4S.) I also believe this warning will be useful note for us to add rng support on all devices as time goes on. Example of failure: [ 0.052888] KASLR disabled due to lack of seed Example of success (on a NanoPi …

Description rk-35xx-vendor-6.1 minor touches: - move CONFIG_INPUT_RK805_PWRKEY and CONFIG_PINCTRL_RK805 to modules - move CONFIG_BT to module - add rtw89 8852be/ce wifi support via xunlong/linux-orangepi commit-id 96b2d2827a3f1e4719ebdfcac0b2108e8cbae932 see net: wireless: realtek: Sync rtw89 driver from linux6.2 linux-rockchip-rk3588-edge.config minor touches: - move CONFIG_INPUT_RK805_PWRKEY and CONFIG_PINCTRL_RK805 to modules - move CONFIG_BT to module This enables powerkey functionality for orangepi5-plus OOB Jira reference number AR-2360 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relev…

Description After testing, it was found that Firefly-RK3399 cannot boot using the mainline device tree due to issues with the PMU (Power Management Unit). Even after fixing the PMU problem, Bluetooth still cannot be used. Therefore, the original patch has been optimized by removing unnecessary parts. How Has This Been Tested? [x] Almost all hardware functions(HDMI, WiFi, BT, GbE, USB...). [x] System startup. 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] My changes generate no new warnings [x] Any dependent changes have been…

Description Fixes ethernet broken for some users on 6.x kernels. It was working fine for me on 6.x kernels. For @AGM1968, it was working fine only on cold boot, while for some users from forum it was not working at all. Hence this PR is raised to fix the same by increasing the startup frequency and specifying clock frequency for motorcomm chip 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] Tested by @AGM1968 and also by user on forum that this fixes the broken ethernet [X] In my case, ethernet continues to work fine with this fix as it was working before. C…

Description RTL8153B - does not initialize correctly on boot. Reboot is okay. Start delay work-around in the board file needs tweaking for longer boot time. Jira reference number AR-1910 How Has This Been Tested? [x] Kernel 6.1y tested on Orange Pi R1 Plus LTS [x] Kernel 6.6y tested on Orange Pi R1 Plus 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 [ ] 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 module…

Description Enabled crust for Orange Pi Zero. Also added workaround to make sure board does resume successfully after sleep. The xradio_wlan driver seems to interfere with the same causing board to get stuck on resume after its put to sleep. Hence now we unload the module when entering sleep and reload it on resume. This works with systemctl suspend, but is still broken with rtcwake. Jira reference number AR-1918 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] Tested suspend/resume works using echo +20 > /sys/class/rtc/rtc0/wakealarm && systemctl …

Description Removed rk3399 bluetooth service from Allwinner boards. The service is installed but not enabled. Starting the service messes up uart and other functions in allwinner boards. Hence removing the same as it doesn't belong in any of the Allwinner board images. 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

Description Fix OrangePi One Plus early manufactured board dosen't work with current and edge kernel Discussion about issue: https://forum.armbian.com/topic/21009-orange-pi-one-plus-early-manufactured-board-does-not-work-with-515x-kernel/ https://forum.armbian.com/topic/20227-gave-up-waiting-for-root-file-system-device/ View the full article

Description Fix for Orangepi-r1plus-lts network interface logical names that changed and broke networking. The problem was caused by one of the network interface logical names changing from eth0 to end0. Fixed with a rename in /etc/udev/rules.d/70-rename-lan.rules which is already created from a hook in the board config file (to rename the other network interface). Jira reference number AR-1747 How Has This Been Tested? [x] Built images on: current bookworm, current jammy, edge sid. [x] Tested each image with an iperf3 server session via each network interface individually from an iperf3 client session on a computer with Gb NIC. Performance was as expected. [x] Teste…

Description OrangePi kernel patched to enable TV Output on OrangePi Zero (LTE). Changes made according: https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md 7.3 Add the TV encoder driver to the Linux kernel source sunxi-6.1/0036-wip-h3-h5-cvbs-armbian.patch : makes additions to the "dts", which tells the kernel where are the new devices. Adds kernel code to interact with the tv encoder. With my modifications, now it is applicable to Armbian (this patch came from the LibreElec github). sunxi-6.1/zzzz2-tv.patch : by Armbian user "gleam2003", adds directives to make sure that the dtbo (device tree binary overlay) is compiled sunxi-6.1/zzzz3-tv.pat…

Description As per title. In u-boot v2025.04 the upstream dtb is missing. I assume it will land with v2025.07 later this year. Until then extracted via kernel-dtb from Linux 6.14.2. Had to strip the MAINTAINERS part from Ilya's patch since for unknown reason it failed to apply after converting into Armbian patch format and I didn't want to spent additional time on fixing. Apologies for that. How Has This Been Tested? [x] build [ ] boot: nope, no hw Test image: https://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.05.0-trunk_Orangepi5-max_bookworm_edge_6.14.2_minimal.img.xz Checklist: [x] My code follows the style guidelines of this project [x] I have performed…

Description Add mainline devicetree for opi3b 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] branch edge kernel build okay [x] kernel boots on opi3b Checklist: [x] 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 [ ] 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

orangepi5-plus.wip: initial Orange Pi 5 plus support using Xunlong vendor u-boot kernel dts is waiting for https://github.com/armbian/linux-rockchip/pull/38 to be merge i had tested on my opi5 plus(jammy/cli), it can boot from emmc, both 2 eth ports and nvme is working fine. View the full article

Description patch u-boot 2024.07 to support KASLR enable KASLR Reference patchset: 1949474 Credit: Tim Harvey How Has This Been Tested? [x] built and ran minimal trixie edge orangepi5-plus --> KASLR Enabled Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description Orange Pi 5 requires to relocate FSPI0 pinctrl to identify SPI flash. Otherwise, it breaks NVME boot like now. This PR fixes it How Has This Been Tested? [x] Build and boot Checklist: Please delete options that are not relevant. [ ] 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Use same uboot for current and edge builds, so that we can remove redundant lines. Add sata spi image to current, edge uboot builds. It is a bit hacky, but it works. Also add selection for SPI images like https://github.com/armbian/build/pull/8123 GitHub issue reference: Jira reference number [AR-9999] Documentation summary for feature / change Please delete this section if entry to main documentation is not needed. If documentation entry is predicted, please provide key elements for further implementation into main documentation and set label to "Needs Documentation". You are welcome to open a PR to documentation or you can leave following information for…

Description This should get wifi working on OrangePi Zero2 on current and edge 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] Not tested as I don't have the device. @AGM1968 Could you please test the same? 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 d…

Description bash-completion adds the functionality for autocompleting command when pressing . This is an essential shell functionality and should be enabled even on a minimal image. The package has no dependencies and is slim: https://packages.ubuntu.com/noble/bash-completion How Has This Been Tested? [x] Install minimal image without bash-completion: pain 😵‍💫 [x] Install minimal image without bash-completion: nice and efficient 🌈 Checklist: [x] My code follows the style guidelines of this project [ ] My changes generate no new warnings View the full article

Description ：） How Has This Been Tested? 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

Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number AR-1488 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] JetHub H1/D1/D1+ bullseye image View the full article

Description Allow to disable boot partition by explicit BOOTSIZE=0. This would help when bootloader known to support rootfs FS. Allow image_size < rootfs_size for (potentially compressed) btrfs. 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] Built compressed btrfs-rootfs image with FIXED_IMAGE_SIZE=$((rootfs_size/2)) and without boot partition 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 corresp…

partitioning: back to classic dd /dev/zero to prepare $SDCARD.raw maybe (?) fixes problems with double-sparse when truncate is used on a zfs under Docker reported by @adeepn -- on Docker using zfs draft: no idea if this fixes it at all, just a guess View the full article

partitioning: declare global readonly ROOT_PART_UUID for later hooks partitioning: declare global readonly ROOT_PART_UUID for later hooks re-use local root_part_uuid instead of running blkid multiple times View the full article

partitioning: declare global readonly ROOT_PART_UUID for later hooks partitioning: declare global readonly ROOT_PART_UUID for later hooks View the full article

Description Find and take loop device in one shot to prevent race condition How Has This Been Tested? [x] Build image Checklist: [x] I have performed a self-review of my own code View the full article

The default will align the data structures with the cluster size, which causes the size to not be set to the full partition size. This causes issues with some board ROMs. Use the -a flag to ignore the alignment and fill the available space. How Has This Been Tested? [x] Tested on SK-TDA4VM, SK-AM62B, and SK-AM64B boards Checklist: [x] 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 [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downst…

partitioning: move hook call image_specific_armbian_env_ready() after the end of related manipulations partitioning: move hook call image_specific_armbian_env_ready() after the end of related manipulations depending on rootpart/extlinux/boot.ini it might not have run or had any effect View the full article

Description Mount option commit=600 (=10 minutes) seems pretty high. Reduce it to 120 for ext4 (default for ext4 is commit=5) and 120 for btrfs (default for btrfs is commit=30) to reduce risk of losing data on power loss. Only verly low settings (maybe 1-10) will have impact on performance according to documentation. From ext4: commit=nrsec (*) This setting limits the maximum age of the running transaction to ‘nrsec’ seconds. The default value is 5 seconds. This means that if you lose your power, you will lose as much as the latest 5 seconds of metadata changes (your filesystem will not be damaged though, thanks to the journaling). This default value (or any low valu…

Description When booting on H3 boards with regulator-gpio, we get the following error. [ 8.518147] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.518188] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 8.518373] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.518391] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 8.518565] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 8.518585] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 8.518752…

linux 6.7.y support 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

Reduce failed to get tx report from firmware dmesg spam. https://lore.kernel.org/linux-wireless/20210713104524.47101-1-pkshih@realtek.com/ https://cgit.freebsd.org/src/commit/?id=e140d551b78670fbf99c83a59438cb13de50420f 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

RTW88: updates and fixes 6.1: wireless-next 2023-10-06 The new regulation of China has been released, so update to the latest TX power table that also includes some changes of QATAR and UK. Why didn't add the wireless next updates to 6.5 and 6.6? The updates are small, with one of which only fixing a typo that has no effect on functionality. Plus these changes will more than likely make it in on their own. https://lore.kernel.org/linux-wireless/20231004085051.205683-1-pkshih@realtek.com/T/#t 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-…

Patch set includes a complete backport of RTW88 as it currently stands, along with extras. Extra: Patch: RTL8723DS (SDIO) Patch: _rtw_download_firmware() warn: missing unwind goto? Patch: Hack: SDIO RX Aggregation Limiting I only have two units available to me with an 8822CS module and in my testing this is only required on the BPI-CM4IO. With out LIMITING the unit will either kernel panic or not be able to send or receive. This is currently being looked into: https://lore.kernel.org/linux-wireless/CAFBinCBaXtebixKbjkWKW_WXc5k=NdGNaGUjVE8NCPNxOhsb2g@mail.gmail.com/T/#u It may be possible to just set LIMITING across all builds, but that to me seems like a poor choice.…

Backport updates from Linux 6.3. In my testing this has no ill effects on SDIO 8822CS and fixes USB 8821CU dmesg | grep rtw [ 8.684999] rtw_8821cu 4-1:1.0: Firmware version 24.11.0, H2C version 12 [ 9.426555] usbcore: registered new interface driver rtw_8821cu lsmod | grep rtw88 rtw88_8821cu 16384 0 rtw88_8821c 81920 1 rtw88_8821cu rtw88_usb 20480 1 rtw88_8821cu rtw88_core 131072 2 rtw88_usb,rtw88_8821c mac80211 458752 2 rtw88_core,rtw88_usb cfg80211 331776 2 rtw88_core,mac80211 Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my o…

Adjusted patching in drivers/net/wireless/realtek/rtw88/usb.c to reflect update in Linux 6.3.13 (EOL) https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/net/wireless/realtek/rtw88/usb.c?id=v6.3.13&id2=v6.3.12 [ ] 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

Adjusted patching in drivers/net/wireless/realtek/rtw88/mac80211.c and drivers/net/wireless/realtek/rtw88/usb.c to reflect update in Linux 6.4.4 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/net/wireless/realtek/rtw88/mac80211.c?id=v6.4.4&id2=v6.4.3 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/net/wireless/realtek/rtw88/usb.c?id=v6.4.4&id2=v6.4.3 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 …

Updated: 6.1 / 6.4 Added: 6.5 For doc sake, this update makes 6.1 slightly different than 6.4 and 6.5 in one particular area of main.c. As shown here: https://github.com/lwfinger/rtw88/commit/7746e2fa87a6687c068c9c746f6efbeee2616496 6.1 requires we use del_timer_sync, where the above releases use timer_delete_sync. Tested-on: ODROID-C4 X96-AIR BPI-CM4 (linux 6.x.y) There is no meson64-6.5 patch dir as of yet, so I didn't run an official test using Armbian. In my own personal builds, these patches all apply clean and the resulting kernel behaves as expected. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my …

Description Enable power led in u-boot on H5 based boards. 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] Booted on Orange Pi Prime 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

Description Removed Allwinner spi patch for u-boot. It was upstreamed in 2018 and is currently available as SPI_SUNXI config option in u-boot. Also it looks like driver added by the removed patch was never enabled for any of the boards. Hence removing it also doesn't makes any difference for that reason either. 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 module…

HACK: BOOT ORDER: NVMe SDCARD eMMC. NOTES: In my testing there has been no false starts or hangs up. Meaning the boot process has been stable. The downside to this in my opinion is that if there is an OS on the NVMe it will always take boot priority. The drive would need to be pulled or DD'd in order for SD eMMC boot to kick in. This has been tested by pulling the NVMe and booting from the drive and killing it; dd if=/dev/zero of=/dev/nvme0n1 bs=32768 count=32768 Tested-on: Waveshare CM4-IO-BASE-B 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…

This does not change the current boot order and requires additional hardware. Hardware used in my testing: BananaPi BPI-CM4IO Baseboard with BPI-CM4 Module Mini PCI-E PCI Express to SATA 3.0 Dual Ports Adapter Converter Hard Drive Extension Card https://a.co/d/0G679qW Kingston 120GB A400 SATA 3 2.5" Internal SSD https://a.co/d/fB2qf3r External power supply for Hard Drive 2.5" 3.5" https://www.ebay.com/itm/114620135743 bananapi: ~ $ lspci 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01) 01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) bananapi: ~ $ sudo blkid /dev/mmcblk1p1: LABEL="EMMC" UUID="67ea5c62-c9cb-4…

This brings the patch set up to 2023-06-22 wireless-next Drivers tested; 8822CS. 8821CU and 8723DS Notables; Not seeing random dmesg spam rtw_8822cs failed to get tx report from firmware which I would see on both the CS and CU from time to time. [ ] 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

Description Adding u-boot patches to recognize the espressobin ultra, and compile a device tree for firmware use. How Has This Been Tested? Compiled and booted on ebin ultra View the full article

Description BigTreeTech CB1 current(6.1) & edge(6.2) patches. AXP313A PMIC ok Onboard RTL8189FS WIFI ok The Ethernet AC200/AC300 PHY drivers built-in H616 and HDMI have not yet been adapted. In fact, the HDMI of sun50i-h616-orangepi-zero2.dts and the ethernet of sun50i-h616-x96-mate.dts also have the same effect(cannot work) Jira reference number [AR-9999] How Has This Been Tested? Both BRANCH=current and BRANCH=edge have been compiled successfully without any errors and can be started normally when written to the device. 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 m…

U-Boot: Update DRAM parameters and enable USB. Backport sunxi reorganize mctl_mem_matches_* functions Backport restore modified memory Add delay to steady dram detection Alphabetize dts Linux: Add spi1_cs1_pin to h616 dtsi Add node to m4-zero dts Alphabetize dts [ ] 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

patching: 6.5+ armhf Makefile autopatcher; better summary patching: enhance the DT Makefile Autopatcher to work with armhf's new 6.5 subdir Makefiles as well as arm64 arm64: one-rule-per-dtb arm32: single-rule, multi-dtb patching: show the patch number for multi-patch mbox files in summary table patching: show auto-patch'ed in summary table (in blue); remove spurious warnings View the full article

patching: accept a sha1 in BASE_GIT_TAG (as well as branch or tag) patching: accept a sha1 in BASE_GIT_TAG (as well as branch or tag) just for convenience View the full article

patching: emit warnings when files in dt folder overwrite pre-existing files (DTs that landed upstream) patching: emit warnings when files in dt folder overwrite pre-existing files (DTs that landed upstream) it's more and more common that the (bare) DT files in our dt folders have landed upstream this adds warnings and marks the patching table red when some bare-dt file overwrites what's already in git without this it's very easy to forget them there during bumps View the full article