RSS Bot

Description This PR add some tweaks to get the current (and IMO best possible yet) configuration of the WDK. point to latest development branch which appears to be quite stable add package mtools to support mounting the EFI partition, enable mount add tweak to ensure qrtr-ns.service also runs, like protected-domain-mapper add board file with calibration data that work well with the QCNFA765 Wireless Network Adapter 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 the image with ./compile.sh build BOARD=wdk2023 BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='3dsupport browsers chat desktop_tools editors email internet multimedia office programming remote_desktop' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=mantic [x] written the image to an SSD (with USB-to-SATA adapter) and booted from it, checked for desired operation 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

https://github.com/armbian/build/pull/6053#issuecomment-1869032590 View the full article

Bumps tj-actions/changed-files from 40 to 41. Release notes Sourced from tj-actions/changed-files's releases. v41 Changes in v41.0.1 What's Changed Upgraded to v41 by @​tj-actions-bot in tj-actions/changed-files#1811 chore(deps): update dependency eslint-plugin-prettier to v5.1.2 by @​renovate in tj-actions/changed-files#1813 fix: update characters escaped by safe output by @​jackton1 in tj-actions/changed-files#1815 Full Changelog: https://github.com/tj-actions/changed-files/compare/v41...v41.0.1 Changes in v41.0.0 🔥 🔥 BREAKING CHANGE 🔥 🔥 A new safe_output input is now available to prevent outputting unsafe filename characters (Enabled by default). This would escape characters in the filename that could be used for command injection. [!NOTE] This can be disabled by setting the safe_output to false this comes with a recommendation to store all outputs generated in an environment variable first before using them. Example ... - name: Get changed files id: changed-files uses: tj-actions/changed-files@v40 with: safe_output: false # set to false because we are using an environment variable to store the output and avoid command injection. - name: List all added files env: ADDED_FILES: ${{ steps.changed-files.outputs.added_files }} run: | for file in &quot;$ADDED_FILES&quot;; do echo &quot;$file was added&quot; done ... What's Changed chore(deps): update typescript-eslint monorepo to v6.15.0 by @​renovate in tj-actions/changed-files#1801 Upgraded to v40.2.3 by @​tj-actions-bot in tj-actions/changed-files#1800 chore(deps): update dependency eslint-plugin-prettier to v5.1.0 by @​renovate in tj-actions/changed-files#1802 chore(deps): lock file maintenance by @​renovate in tj-actions/changed-files#1803 chore(deps): update dependency eslint-plugin-prettier to v5.1.1 by @​renovate in tj-actions/changed-files#1804 fix: update safe output regex and the docs by @​tj-actions-bot in tj-actions/changed-files#1805 Revert "chore(deps): update actions/download-artifact action to v4" by @​jackton1 in tj-actions/changed-files#1806 Update README.md by @​jackton1 in tj-actions/changed-files#1808 ... (truncated) Changelog Sourced from tj-actions/changed-files's changelog. Changelog 41.0.1 - (2023-12-24) 🐛 Bug Fixes Update characters escaped by safe output (#1815) (716b1e1) - (Tonye Jack) ⚙️ Miscellaneous Tasks deps: Update dependency eslint-plugin-prettier to v5.1.2 (7aaf10d) - (renovate[bot]) ⬆️ Upgrades Upgraded to v41 (#1811) Co-authored-by: jackton1 jackton1@users.noreply.github.com (cc08e17) - (tj-actions[bot]) 41.0.0 - (2023-12-23) 🐛 Bug Fixes Update safe output regex and the docs (#1805) (ff2f6e6) - (tj-actions[bot]) ⏪ Reverts Revert "chore(deps): update actions/download-artifact action to v4" (#1806) (4f573fe) - (Tonye Jack) 🔄 Update Update README.md (6e79d6e) - (Tonye Jack) Update README.md (d13ac19) - (Tonye Jack) Update README.md (bb89f97) - (Tonye Jack) Updated README.md (#1810) Co-authored-by: renovate[bot] (1864078) - (tj-actions[bot]) Update README.md (#1808) (47371c5) - (Tonye Jack) 📝 Other Merge pull request from GHSA-mcph-m25j-8j63 feat: add safe_output input enabled by default fix: migrate README to safe uses of interpolation ... (truncated) Commits 716b1e1 fix: update characters escaped by safe output (#1815) 7aaf10d chore(deps): update dependency eslint-plugin-prettier to v5.1.2 cc08e17 Upgraded to v41 (#1811) 6e79d6e Update README.md d13ac19 Update README.md bb89f97 Update README.md 1864078 Updated README.md (#1810) f495a03 chore(deps): lock file maintenance 47371c5 Update README.md (#1808) 4f573fe Revert "chore(deps): update actions/download-artifact action to v4" (#1806) Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

bcm2711: don't force SKIP_ARMBIAN_REPO=no; include bootloader fw in bsp-cli if set to yes bcm2711: don't force SKIP_ARMBIAN_REPO=no; include bootloader fw in bsp-cli if set to yes do not force SKIP_ARMBIAN_REPO=no anymore instead, if SKIP_ARMBIAN_REPO=yes: include the bootloader "fw" in bsp package, from Debian's raspi-firmware git source add Debian/Ubuntu-specific packages for Wifi/BT firmware For Ubuntu, include raspi-eeprom and raspi-config too (not available on Debian) tested on rpi4b (bookworm/mantic) - untested on rpi5b (I don't have/want one) View the full article

Description armbian.list generated two times on every build: when==image-early and when==image-late If when==image-early armbian.list renamed to armbian.list.disabled and this file goes to image. https://github.com/armbian/build/issues/6086 Jira reference number AR-2007 How Has This Been Tested? [X] Rebuild image, armbian.list.disabled disappears 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 [X] Any dependent changes have been merged and published in downstream modules View the full article

Description Legacy - 5.15.x -> 6.1.x Current - 6.1.x -> 6.6.x Edge - 6.6.x -> 6.7-rc6 move kernel branch and minor definitions to config/sources/common.conf (this location was predicted to contain this) bump UEFI kernels fix Phytium patch compilation failure for 6.7.y removed old leftover kernel patch directories Jira reference number AR-2005 How Has This Been Tested? [x] Patching test 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 I noticed that I was not seeing many locales that were supposed to be shown during first login like en_IN for English India. I was only getting the following 3 options when choosing to get locales based on my location At your location, more locales are possible: 1) bhb_IN.UTF-8 2) tcy_IN.UTF-8 3) Skip generating locales Please enter your choice: This is because we were looking for .UTF-8 suffix in the locale names. But not all UTF-8 locales have that suffix. All UTF-8 locales do end with UTF-8 at the end. So now we are using the same. With the fix, I am now getting much better result. Here is the list after the fix for comparison At your location, more locales are possible: 1) anp_IN 8) brx_IN 15) kok_IN 22) ml_IN 29) sat_IN 36) ur_IN 2) ar_IN 9) doi_IN 16) ks_IN 23) mni_IN 30) sd_IN 37) Skip generating locales 3) as_IN 10) en_IN 17) ks_IN@devanagari 24) mr_IN 31) sd_IN@devanagari 4) bhb_IN.UTF-8 11) gu_IN 18) ks_IN@devanagari 25) or_IN 32) sd_IN@devanagari 5) bho_IN 12) hi_IN 19) mag_IN 26) pa_IN 33) ta_IN 6) bn_IN 13) hne_IN 20) mai_IN 27) raj_IN 34) tcy_IN.UTF-8 7) bo_IN 14) kn_IN 21) mjw_IN 28) sa_IN 35) te_IN Please enter your choice: Note: we now have ~320 locales offered to be selected when not filtering by location. Before we were only showing 153. 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] Created image with the fix and went through the first run process on Orange Pi 3 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 [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Bumping U-boot to 2024.01-rc5 for Allwinner boards. There were some defconfig patches that were failing, I have migrated them to board config file using post_uboot_config_target hook function. This has resulted into removal of several patches. There are still some defconfig patches left, I will move them as and when needed. Apart from that, updated crust support patches for Allwinner H3 as few of them had patch application failure. As U-boot now has AXP313 support, I have removed the patch for the same and have migrated Bigtreetech to use the upstream driver. 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 booting on Orange Pi Zero, Orange Pi Prime, Orange Pi 3 and Orange Pi 3 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 [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 Swapped one tiny bit (really) to set ddrbin command rate to 2T instead of 1T for rk322x family. How Has This Been Tested? Untested 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 Bump Allwinner kernels Legacy - 5.15.x -> 6.1.x Current - 6.1.x -> 6.6.x Edge - 6.6.x -> 6.7-rc6 Removed old leftover kernel patch directories. 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. [ ] Edge kernel builds with EXTRAWIFI=no. Some driver harness drivers including xradio, rtl8189es, rtl8189fs, rtl8812au, rtl8192eu and possibly others needs some fixes as compilation fails for 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 downstream modules View the full article

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 article

Weston 13.0 brings multiple fixes and important changes, notably the ability to load multiple backends simultaneously. This can be used to load VNC, RDP, or PipeWire backends for remote access alongside the native DRM backend. View the full article

Description Integrating deboostrap hack directly into build framework instead of having it as extension. better compatibility with host system support for Debian variants too doesn't break on making docker images future proof and auto-obsolete when host systems deboostrap version passes 1.0.128 Jira reference number AR-2004 How Has This Been Tested? [x] Generating Docker images [x] Generating Ubuntu noble 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 Add support for armsom-sige7 board Dependencies required for this change：https://github.com/armbian/linux-rockchip/pull/131 armsom-sige7 related document links: How Has This Been Tested? Compile command: ./compile.sh 2.5Gb Network *2 ok Headphone ok usb 3.0 * 2 ok typec ok hdmi tx ok 40pin-Header ok LED ok debug ok Fan ok M2 E key ok 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 Ubuntu Noble is not yet in Jammy deboostrap. Lets patch the system with an extensions, so we con't mess up with a framework itself. This will eventually become deprecated anyway. Jira reference number AR-2004 How Has This Been Tested? [x] Manual run ./compile.sh ENABLE_EXTENSIONS="ubuntu-noble" 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 Minor kernel bumps Legacy - 5.15.143 -> 5.15.144 Current - 6.1.68 -> 6.1.69 Edge - 6.6.7 -> 6.6.8 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 booting on Orange Pi Zero (sun8i H3) 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 Necessary changes only to make repository work. There is probably lots of work to do laser... Jira reference number [AR-9999] How Has This Been Tested? Builds until the point where it tries to grab release file form apt repo which obviously fails. 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

Description Converted configuration for uwe5622 support to extension making it easier to add wifi and bluetooth support to boards with uwe5622 wireless module. Added the uwe5622 extension to Orange Pi Zero2. This should add bluetooth support to the same. Moved Orange Pi 3 LTS specific code out of the family config file Also for H6 based devices, switched to lightdm-gtk-greeter as slick-greeter shows weird artifacts Also added myself as maintainer for Orange Pi 3 and Orange Pi 3 LTS. 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 wifi, bluetooth and login screen on Orange Pi 3 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

Description The lm75 sensor was defined in the dts as "onnn,lm75". Set it to "national,lm75" as is set in the upstream dts. (there is no such thing as "onnn,lm75"). Later on (or maybe I should include it there) we should remove the lm75 module from MODULES and MODULES8lEGACY in config/boards/helios64.csc, as the DTS already loads it. (which makes me think "onnn,lm75" as a DTS node never was recognized by a kernel, thus the need to explicitly load lm75). How Has This Been Tested? [x] remove lm57 from the config (I believe it was /etc/modules but is long gone) and reboot with new dts 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 Fix compilation warnings [🐳|🔨] CC arch/arm/mach-rockchip/boot_mode.o (...) [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c: In function ‘rockchip_dnl_mode_check’: [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:174:24: warning: ‘return’ with a value, in function returning void [-Wreturn-type] [🐳|🔨] 174 | return 0; [🐳|🔨] | ^ [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:166:6: note: declared here [🐳|🔨] 166 | void rockchip_dnl_mode_check(void) [🐳|🔨] | ^~~~~~~~~~~~~~~~~~~~~~~ [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:183:24: warning: ‘return’ with a value, in function returning void [-Wreturn-type] [🐳|🔨] 183 | return 0; [🐳|🔨] | ^ [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:166:6: note: declared here [🐳|🔨] 166 | void rockchip_dnl_mode_check(void) [🐳|🔨] | ^~~~~~~~~~~~~~~~~~~~~~~ [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:196:17: warning: implicit declaration of function ‘cli_simple_run_command’ [-Wimplicit-function-declaration] [🐳|🔨] 196 | cli_simple_run_command(cmd, 0); [🐳|🔨] | ^~~~~~~~~~~~~~~~~~~~~~ [🐳|🔨] arch/arm/mach-rockchip/boot_mode.c:170:13: warning: unused variable ‘ret’ [-Wunused-variable] [🐳|🔨] 170 | int ret = 0; [🐳|🔨] | ^~~ it could be that adding the missing cli include fix functionality. So this patch might be more than cosmetic. 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 u-boot for helios64 board (v2022.07) and boot with this u-boot. -./compile.sh uboot BOARD=helios64 BRANCH=edge RELEASE=bookworm BUILD_KSRC=no ARTIFACT_IGNORE_CACHE="yes" The CONFIG_SYS_SCSI_MAX_DEVICE definition removal from u-boot v2022.04 (as since this version this is a macro) I have only build tested with: ./compile.sh uboot BOARD=helios64 BRANCH=edge RELEASE=bookworm BUILD_KSRC=no ARTIFACT_IGNORE_CACHE="yes" BOOTBRANCH="tag:v2022.04" BOOTPATCHDIR="u-boot-rockchip64-v2022.04" 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

As 2023 draws to a close, I wanted to give a quick update on NVK, what's happened this year, and where we'll be headed in 2024. While previous posts have focused primarily on the technical details, this post will be more geared towards users. View the full article

Description Switch back to Rockchip DDR binary for DDR initialization in u-boot for Helios64. I believe there is nothing board-specific about this memory initialization issue, but it might be no other Armbian board has this combination of rk3399 and LPDDR4. Else there is something specific about the memory set up on the Helios64 hardware. On the Helios64 random memory errors happens when using the U-Boot DDR intialization code for rk3399. Switching to the rkbin rk33 933MHz v1.25 allows this testcase to run more than once without a memory error: for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done Could be LPDDR4 specific. Workaround https://github.com/armbian/build/issues/4761 "free() invalid pointer". A proper fix would be to fix u-boot own lpddr4 initialization code for Rockchip but I miss the Rockchip DDR binary settings to compare with. 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 ] run for i in $(seq 1 100);do python3 -c "import pkg_resources" || break;done multiple times 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

Google Open Source have chosen their second group of winners for the 2023 Google Open Source Peer Bonus Program, and Arnaud Ferraris, Senior Software Engineer at Collabora and Mobian project lead, is among the recipients! View the full article

Description It breaks EDGE compilation as define was done only for legacy. How Has This Been Tested? Manual build. View the full article