RSS Bot

Description Resolving 3d and multimedia extensions confusions. Replacement for: https://github.com/armbian/build/blob/main/extensions/mesa-oibaf.sh https://github.com/armbian/build/blob/main/extensions/rk-multimedia-amazingfate.sh https://github.com/armbian/build/blob/main/extensions/rk-panthor.sh and custom one: https://github.com/armbian/os/blob/main/userpatches/extensions/amazingfated-rk3588.sh How Has This Been Tested? [ ] Made all test images with enabled extension Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description It is known that it is built without errors and works on a test platform. freeze the kernel version v6.6.31 sunxi-6.6: rework patches for current v6.6.31 [ ] 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. [x] Build & Test on board Bananapi-m64 View the full article

Description Minor fixes: limit creation of git-sources.json file to following commands - targets, debs-to-repo-json, gha-matrix and gha-workflow Solve slowness when building Ubuntu Noble images. Fixes #6531 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 Ubuntu noble rootfs creation speed improvement using ./compile.sh BOARD=khadas-vim4 BRANCH=legacy KERNEL_CONFIGURE=no BUILD_MINIMAL=yes RELEASE=noble ARTIFACT_IGNORE_CACHE=yes rootfs. It reduced build time from 26 minutes down to only 8 minutes. 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 doas is not compatible with sudo flags. The codebase was checked for sudo-specific uses of this function, but none were found, all cases were in the form of sudo <command>. Replacing it with doas <command> yields the same result. Was extracted from #6576 and can't be merged until it's reverted in #6642 How Has This Been Tested? Used to build images on my machine with extensions that use is_root_or_sudo_prefix 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

Reverts armbian/build#6576 View the full article

Description Upstreaming patch: https://patchwork.kernel.org/project/linux-rockchip/patch/20240430024002.708227-3-liujianfeng1994@gmail.com/ The current fdb50400 won't work. there are errors in dmesg when doing decoding. 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_CONFIGURE=no KERNEL_GIT=shallow 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

Description Update odroidxu4-current kernel to 6.6.31. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 modules View the full article

Description I guess all these BOOTFS_TYPE come from https://github.com/armbian/build/pull/3874. Rock3a and other rk356x boards uses an old version of vendor u-boot: https://github.com/radxa/u-boot/tree/stable-4.19-rock3, which has bad support for ext4 filesystem. While rk3588 uses new version of vendor u-boot which doesn't have ext4 partition issue, so I just drop all this config from rk3588 boards. Command to query boards with this config: grep -rn rockchip-rk3588 config/boards/|awk -F ':' '{print $1}'|xargs grep BOOTFS_TYPE Here are the vendor uboot source of these boards: board vendor uboot source armsom-sige7 armsom-w3 nanopc-cm3588-nas nanopct6 nanopi-r6s rock-5b https://github.com/radxa/u-boot/tree/next-dev-v2024.03 fxblox-rk1 https://github.com/functionland/u-boot/tree/next-dev indiedroid-nova https://github.com/stvhay/u-boot/tree/rockchip-rk3588-unified orangepi5-plus orangepi5pro https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2017.09-rk3588 orangepi5 https://github.com/u-boot/u-boot/tree/2f0282922b2c458eea7f85c500a948a587437b63 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 build BOARD=rock-5b BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DEB_COMPRESS=xz DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base ENABLE_EXTENSIONS='rk-panthor mesa-oibaf rk-multimedia-amazingfate' KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=noble 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

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 merged and published in downstream modules View the full article

lib & config: give shellcheck directions (to /dev/null for dynamic, to repo-relative path for static) for all sourced references lib & config: give shellcheck directions (to /dev/null for dynamic, to repo-relative path for static) for all sourced references in preparation for tightening the shellcheck severity level it needs to be able to follow all sources; dynamic ones are ignored, static ones need root-relative prefix View the full article

t95z: add board file (and u-boot 2024.04) for T95Z Plus Amlogic tvbox t95z: add board file (and u-boot 2024.04) for T95Z Plus Amlogic tvbox we've had kernel patches/DT (from chewitt) for this in meson64 for a long time, but I never sent the board uses blobs for the tartiflette-s912 which is also an DDR3 S912 (VIM2's blobs are DDR4 and won't boot) this adds u-boot 2024.04 support, using chewitt's DT & 000.patching_config.yaml & a specific BOOTPATCHDIR this is a full board as-if it was an SBC, and expects to boot from mainline u-boot; for that to work you've to wipe the eMMC and get rid of the vendor-supplied u-boot if this is not what you want/need, you can use the aml tvbox "board" instead, together with Android u-boot View the full article

khadas-vim3: fix stray closing brace in board file khadas-vim3: fix stray closing brace in board file a stray closing brace, meant for the function, that ends up doing the wrong config change View the full article

Description Issue reported from radxa's forum: https://forum.radxa.com/t/the-changable-wifi-interface-name-of-rock-5c-lite/20921 Rock5c has an onboard aic8800 usb wifi/bt module, which has random wifi interface name by default, which will cause non-static connection name created by networkmanager. 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] PREFER_DOCKER=no ./compile.sh kernel BOARD=rock-5c BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=jammy KERNEL_GIT=shallow DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base 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

-Clean, remove params for old kernel -Add option to disable usb autosuspend -Add display console replace rootdev with "LABEL=armbi_root" to boot from sd card an emmc with same boot.ini View the full article

Description Add support for RK3588 based board Cool PI CM5 EVB Jira reference number [AR-9999] How Has This Been Tested? ./compile.sh build BOARD=coolpi-cm5 BRANCH=edge 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 DOWNLOAD_MIRROR=bfsu EXPERT=yes EXTRAWIFI=no KERNEL_CONFIGURE=no PREFER_DOCKER=no RELEASE=noble Download the compiled img to sdcard, and can 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 Enabling KDE Neon at Noble How Has This Been Tested? [ ] Build test [ ] Running desktop inspection 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 Tested only for assembly at this point. It needs further optimisations. How Has This Been Tested? [x] Build test [ ] Booted image with i3wm Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description I'm sorry, the error on the 6.8 kernel occurred because I didn't synchronize my code in time, resulting in patch errors that affected the compilation. Based on the hints here, I am optimizing the device tree for the firefly-rk3399 kernel: https://github.com/armbian/build/pull/6611 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 merged and published in downstream modules View the full article

patching: rewrite: fully stabilize patch index stanzas as well as From lines patching: rewrite: fully stabilize patch index stanzas as well as From lines git format-patch --zero-commit doesn't affect index xxx...yyy lines, only From: so use the classy "use a regex with a callback" solution as git format-patch doesn't offer one this will make all patches change when rewritten, but hopefully for the last time ! we need to preserve index 000000000000..xxx as zeros, which indicate new file creation, thus: new file creations are rewritten as index 000000000000..111111111111 non-creations are rewritten as index 111111111111..222222222222 this is the final version of #6455 View the full article

extensions: rk-panthor: mesa-oibaf + DEFAULT_OVERLAYS="panthor-gpu" extensions: rk-panthor: mesa-oibaf + DEFAULT_OVERLAYS="panthor-gpu" I had worked this before AF sent his oneliner, but I forgot to PR Should be the same, except avoids sadness when trying with the wrong kernel/branch 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 Add new user to render group, otherwise the non-root user do not have access /dev/dri/renderD128 on RK3399. When login using non-root user to the desktop environment, the GPU acceleration does not work. 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 A Login to the desktop environment using non-root user, glxinfo -B shows the right render device. name of display: :10.0 display: :10 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Panfrost (0xffffffff) Device: Mali-T860 (Panfrost) (0xffffffff) Version: 22.3.6 Accelerated: yes Video memory: 3860MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 3.1 Max compat profile version: 3.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: Panfrost OpenGL renderer string: Mali-T860 (Panfrost) OpenGL core profile version string: 3.1 Mesa 22.3.6 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL version string: 3.1 Mesa 22.3.6 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.1 Mesa 22.3.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 Checklist: Please delete options that are not relevant. [ ] 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

No descriptionView the full article

Description pbp dp port alt mode patch breaking on 6.6.31 https://paste.armbian.com/udedocucek View the full article

Description Due to changes in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/usb/typec/tcpm/tcpm.c?h=v6.6.31&id=789326cafbd1f67f424436b6bc8bdb887a364637 we need to adjust patch How Has This Been Tested? [x] Patch applies well [ ] Build test 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 Add some patches to fix the ethernet PHY on orangepi zero2w, includes: drv-pwm-sun50i-h616-enhance-pwm.patch sunxi pwm enhance driver from this commit: linux-orangepi#c68ef342eba3673c7f1f5aa1ab819b06da1f60c6 drv-pwm-sun50i-h616-enhance-pwm.patch sunxi gmac and ac200 phy driver, from this commit: linux-orangepi#97b476246bc79756423cf6c1d4907606c9633d4b Had to change a bit around the exported function and dependency config to make it possible to load as module 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