RSS Bot

Description The board has mainline kernel and u-boot support for almost 3 years now but Armbian doesn't build images for it. Add basic build config for this board with Wi-Fi extension enabled. Based on orangepizero2.conf X96 mate is H616-powered TV Box with the same Wi-Fi/BT chip as OPiZ2 (AW859A). Mainline DT is missing Wi-Fi node and some regulators are disabled, but PR is on its way. It doesn't hurt to add Wi-Fi extension to config now. How Has This Been Tested? [x] Compile and verify all defined flavours of image on working hardware [X] Tested Wi-Fi extension with patched DT and proved to be working 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 See title. Reference: https://github.com/armbian/build/pull/6409#issuecomment-2006680880 Feel free to discuss/decide if the removal is appropriate. How Has This Been Tested? [x] Search for boot-rockchip64-vendor in the whole project View the full article

Thanks to sponsors like STMicroelectronics, Netflix, Living Optics, and ChromeOS, Collabora once again came in first place with the most contributors for this release, with 16 developers taking part. View the full article

Description Commit 562d96128ba6 introduces new variable "BOOT_SOC". This var is used at u-boot post install script, so "BOOT_SOC" must be avaiable on system image. Without this u-boot upgrade on tinkerboard will be completely broken. https://forum.armbian.com/topic/35677-tinkerboard-not-booting-after-updates/ How Has This Been Tested? [x] Add BOOT_SOC=rk3288 to /etc/armbian-release and the issue is fixed. 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 When booting U-Boot for rockchip64 or rk3588 devices, the error Failed to load '...-fixup.scr' pops up. This PR fixes this error by checking if the file exists before trying to load it. This PR partially fixes https://github.com/armbian/build/issues/6398 Unfortunately, I was not able to fix the error with missing kaslrseed (even though it may only be cosmetic). Note: U-Boot uses Hush cli language. Not this Hush cli (!) but a different old Hush shell in Busybox which is very badly documented overall unfortunately. I could not find any Hush functionality or a U-Boot command to check if the command kaslrseed exists. Should we include CONFIG_CMD_KASLRSEED for every rockchip64 and rk3588 device? Jira reference number AR-2105 How Has This Been Tested? Just compiling a new uboot image and installing it with dpkg -i (+ armbian-config after that) did not work. [x] Compiled a new image, flashed it and checked U-Boot log ./compile.sh build BOARD=nanopc-cm3588-nas BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm 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 [x] My changes generate no new warnings View the full article

Description Added the necessary parts to create linux-libc-dev packages when creating armbian images. This functionality was not added to the new build system but worked just fine up until v23.02. In my opinion linux-libc-dev should always be created when building an armbian kernel as the kernel versions often differ greatly from the ones natively in the distros (eg. debian bookworm: 6.1.76 vs. armbian current 6.6.21). Also the armbian package source previously included the package but does not anymore, so the latest updates available were 23.02.2. See also https://forum.armbian.com/topic/36140-linux-libc-dev-packages-not-available-after-2302/#comment-184962 How Has This Been Tested? Used the updated scripts to build deb packages and images for bananapi and rpi4b. The created package linux-libc-dev installs the expected headers. 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 View the full article

Description Fix/rewrite-kernel-config two kernel configs (mvebu64-current and sun50iw9-btt-legacy) to adapt them to the latest wireless driver updates in drivers_network.sh. Without doing a rewrite-kernel-config refresh, their kernel builds might potentially fail due to misconfigured wireless driver modules. Checklist: [x] My changes generate no new warnings View the full article

Description We are using out-dated hdmi patches and now mainline has hdmi phy merged. HDMI bridge driver is WIP by collabora but I can get it work on rock5b. Comparing deleted 0032 patch and new 0040 patch for rock5b, we can see devicetree is a llitle different from the old one, for example, we don't need node hdmi-con and hdmi0_out. We have to rewrite all these boards with hdmi support referring to rock5b: [ ] hinlink h88k [ ] rock 5a [x] rock 5b [ ] nanopi r6s/r6c [ ] khadas edge2 [ ] orange pi 5/5b [ ] orange pi 5 plus 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 kernel BOARD=rock-5b BRANCH=edge DEB_COMPRESS=xz KERNEL_GIT=shallow [x] HDMI works on rock5b 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 [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Additions: GPU node UART 1 & 5 nodes GPU is disabled by default as I am not 100% how functional it currently is. 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 [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines View the full article

Description I was checking this Actions workflow https://github.com/armbian/build/actions/runs/8309150018/job/22740183634 and noticed [!] ERROR: failed to detect microarchitecture Reason: RISC-V is not yet supported by kernel-hardening-checker. See https://github.com/a13xp0p0v/kernel-hardening-checker/issues/56 In their README: Supported microarchitectures X86_64 X86_32 ARM64 ARM TODO: RISC-V (issue https://github.com/a13xp0p0v/kernel-hardening-checker/issues/56) How Has This Been Tested? Ran manual in CLI: file=config/kernel/linux-uefi-risc64-edge.config and then if [[ "${file}" = config/kernel/*.config && ! "${file}" =~ riscv ]]; then echo yes; fi Don't know how to run the whole workflow manually quickly, and on a specific file. 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 View the full article

Description This PR tries to improve the GitHub bug report template for the build framework: Don't have pre-placed text in text boxes which have to be deleted each time (placeholder/light grey background text is still there) Add latest host systems Add optional checkbox if building on WSL2 Small wording improvements/changes How Has This Been Tested? [x] View the result (preview) in my forked repo 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 Bump mainline from 6.8-rc7 to 6.8 stable This currently affects only rk3588-edge Bump UEFI-edge from 6.7 to 6.8 [DOES NOT COMPILE YET!!!] Kernel configs updated via ./compile.sh rewrite-kernel-config Kernel patches updated via ./compile.sh rewrite-kernel-patches The uefi-edge kernel does not compile without errors yet, because of drivers/net/wireless/rtl8192eu and the likes. Some patches need to be added or adapted for 6.8 in patch/misc, but I honestly don't know where to get these patches from. I could not find folders like /drivers/net/wireless/rtl8192eu/os_dep/ in the mainline kernel. Help is appreciated! ❤️ Build log for BOARD=uefi-arm64 BRANCH=edge: https://paste.armbian.com/ejevafisid How Has This Been Tested? [x] 1) Tested with ./compile.sh build BOARD=nanopi-r6s BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no BUILD_ONLY="kernel" KERNEL_CONFIGURE=no RELEASE=bookworm --> build success [ ] 2) Build ./compile.sh build BOARD=uefi-arm64 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no BUILD_ONLY="kernel" KERNEL_CONFIGURE=no RELEASE=bookworm FAILED Checklist: [x] My code follows the style guidelines of this project [ ] My changes generate no new warnings View the full article

desktop: jammy: kde-neon: more basic packages needed desktop: jammy: kde-neon: more basic packages needed add network-manager & pulseaudio settings add discover, otherwise there is a broken icon on the dock add vault/scdaemon for gpg wallet enable debugs in create_desktop_package.sh; disable old postinst pa hack View the full article

rockchip64_common: use ttyFIQ0 as default SERIALCON for both legacy and vendor BRANCHes rockchip64_common: use ttyFIQ0 as default SERIALCON for both legacy and vendor BRANCHes View the full article

Description Converted to markdown and bash simulating nasting array.Proof of consept 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 technical writer: [x] A simple converter complexly [x] Will Turn your Json to a Bash simulated array and provide a table of features. [x] ./build/doc/doc.sh How Has This Been Tested? [x] (https://github.com/armbian/build/pull/5734 [x] (https://github.com/armbian/build/pull/5894 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] I have commented my code, particularly in hard-to-understand areas View the full article

In continuation with our series about Kernel Integration we'll go into more detail about how regression detection, processing, and tracking can be improved to provide a better service to developers and maintainers. View the full article

Description As discussed here on the forums this overlay adds support for the RTL8211f chip found on Rockpi E Hardware revision 1.21 Documentation summary for feature / change Documentation updated, hope that's enough and appropriate. How Has This Been Tested? Running that overlay currently on four Rockpi S instances connected to the 1 Gbit/s port Checklist: [X] I have performed a self-review of my own code [X] My changes generate no new warnings View the full article

Description This is a follow-up on this PR https://github.com/armbian/build/pull/6376 and this comment https://github.com/armbian/build/pull/6376#issuecomment-1987147291 It's more of an idea, since I tried rewrite-uboot-patches and noticed the following: Board NanoPi-R6S has 5 U-Boot patches in total (legacy/u-boot-raxda-rk3588). Using ./compile.sh BOARD=nanopi-r6s BRANCH=edge rewrite-uboot-patches has the following patch summary: Summary: u-boot patching: 5 total patches; 5 applied; 2 with problems; 2 needs_rebase However, instead of only rewriting/rebasing the 2 patches, it modifies all 5 patches slightly (see example below). This means your git working tree quickly gets cluttered with these modified-without-any-real-changes patch files. And you'll have to either figure out which patches were changed/rebased if you only want to commit those, or commit all and make it harder to see the actual changes (I think?). Example of a patch file getting modified even if the patch stays the same: (Notice the lines/hunks did not get changed, only the metadata) git diff patch/u-boot/legacy/u-boot-radxa-rk3588/0001-Add-defconfig-and-dtb-of-nanopi6.patch | cat diff --git a/patch/u-boot/legacy/u-boot-radxa-rk3588/0001-Add-defconfig-and-dtb-of-nanopi6.patch b/patch/u-boot/legacy/u-boot-radxa-rk3588/0001-Add-defconfig-and-dtb-of-nanopi6.patch index 38f1a5a..b8e16cd 100644 --- a/patch/u-boot/legacy/u-boot-radxa-rk3588/0001-Add-defconfig-and-dtb-of-nanopi6.patch +++ b/patch/u-boot/legacy/u-boot-radxa-rk3588/0001-Add-defconfig-and-dtb-of-nanopi6.patch @@ -1,18 +1,16 @@ -From 70d65e65db965295ddd23d5db752aad1c035c205 Mon Sep 17 00:00:00 2001 +From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Muhammed=20Efe=20=C3=87etin?= <efectn@protonmail.com> Date: Sat, 15 Apr 2023 23:12:17 +0300 -Subject: [PATCH] Add defconfig and dtb of nanopi6 +Subject: Add defconfig and dtb of nanopi6 --- - arch/arm/dts/rk3588s-nanopi-r6s.dts | 126 ++++++++++++++++ - configs/nanopi-r6s-rk3588s_defconfig | 217 +++++++++++++++++++++++++++ + arch/arm/dts/rk3588s-nanopi-r6s.dts | 126 ++++++ + configs/nanopi-r6s-rk3588s_defconfig | 217 ++++++++++ 2 files changed, 343 insertions(+) - create mode 100644 arch/arm/dts/rk3588s-nanopi-r6s.dts - create mode 100644 configs/nanopi-r6s-rk3588s_defconfig diff --git a/arch/arm/dts/rk3588s-nanopi-r6s.dts b/arch/arm/dts/rk3588s-nanopi-r6s.dts new file mode 100644 -index 0000000000..4899e23fa3 +index 000000000000..4899e23fa3aa --- /dev/null +++ b/arch/arm/dts/rk3588s-nanopi-r6s.dts @@ -0,0 +1,126 @@ @@ -144,7 +142,7 @@ index 0000000000..4899e23fa3 +}; diff --git a/configs/nanopi-r6s-rk3588s_defconfig b/configs/nanopi-r6s-rk3588s_defconfig new file mode 100644 -index 0000000000..19bae55629 +index 000000000000..19bae5562928 --- /dev/null +++ b/configs/nanopi-r6s-rk3588s_defconfig @@ -0,0 +1,217 @@ @@ -366,5 +364,5 @@ index 0000000000..19bae55629 +CONFIG_OPTEE_V2=y +CONFIG_OPTEE_ALWAYS_USE_SECURITY_PARTITION=y -- -2.39.2 +Armbian How I tried to solve this The information if a patch needs rebasing is already there, so I tried to solve this by introducing a new option REWRITE_PATCHES_NEEDING_REBASE in addition to the existing REWRITE_PATCHES. Why an additional option? I didn't want to break anything (took me some hours already to figure out where the actual patch rewriting happes and to understand their logic, so I'm not confident to change what REWRITE_PATCHES does on its own 😅) Maybe there will be some reason when you want to actually rewrite all patches even if they don't need rebasing? If it's not an issue, I could also just remove the additional option REWRITE_PATCHES_NEEDING_REBASE and instead make this the default behaviour for REWRITE_PATCHES. How Has This Been Tested? [x] Run the same command as earlier: ./compile.sh BOARD=nanopi-r6s BRANCH=edge rewrite-uboot-patches and only the 2 patches that needed rebasing were modified [x] Compiled a board image to check if nothing got broken: ./compile.sh build BOARD=nanopi-r5c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm 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 View the full article

The latest Linux Kernel 6.8 release brings thousands of new lines of code, improving the core kernel, architecture support, networking, file systems, and more. 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-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 technical writer: [ ] short description (copy / paste of PR title) [ ] summary (description relevant for end users) [ ] example of usage (how to see this in function) 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: 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 As per title. Jira reference number AR-2103 How Has This Been Tested? [x] Manual build 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 This is a sample JSON file that can be used to track features and well as their documentation. This will help bridge information between the developers and the technical writers and help maintain up-to-date documentation. View the full article

Description In order to fullfil the Jira task AR-1988 (Resolve Rockchip patch maintenance nightmare), remove rockpis family in favor of rockchip64 and merge the configuration bits from the family .conf file into the board rockpi-s.conf file. Also removes the legacy patches from the archive Jira reference number AR-1988 How Has This Been Tested? [x] A current kernel image has been produced [x] idbloader has been verified to be matching against the pre-cleanup image [x] /boot/armbianEnv.txt contains the overlay_prefix=rk3308 [x] /boot/boot.cmd matches config/bootscripts/boot-rockpis.cmd [ ] /boot/armbianEnv.txt contains /config/bootenv/rockpi-s.txt Please @brentr check that produced images also boots; I tried to check that all the bits are in the right place, but can't do the ultimate test, thanks! 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

Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines View the full article