RSS Bot

This will enable the latest Armbian images to boot on aml-s905x3 boxes after the move from uImage to Image. The blob is built on mainline u-boot's tag v2023.10. Changes to be committed: modified: packages/bsp/aml-s9xx-box/boot/build-u-boot/readme.txt new file: packages/bsp/aml-s9xx-box/boot/build-u-boot/u-boot-s905x3.patch new file: packages/bsp/aml-s9xx-box/boot/u-boot-s905x3 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. More information can be found here: #4938 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 and tested on s905x3 box (Tanix TX3) View the full article

This fixes an incompatibility introduced with new Armbian framework's change from uImage to Image Changes to be committed: modified: packages/bsp/aml-s9xx-box/boot/build-u-boot/readme.txt new file: packages/bsp/aml-s9xx-box/boot/build-u-boot/u-boot-s905x2-s922.patch modified: packages/bsp/aml-s9xx-box/boot/u-boot-s905x2-s922 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. 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 and installed aml-s9xx-box (current and edge) on s905x2 based TV Box 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 Update odroidxu4-current kernel to 6.1.75. 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 Driver does not compile on kernel 6.7 due to minor changes in kernel API. The PR just fixes the changes. How Has This Been Tested? [x] Compiled rockchip64 edge 6.7 kernel 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 Attempt to fix build job failure - https://github.com/armbian/os/actions/runs/7675198892/job/20921297126 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 vim4 image 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 Delay fetching khadas common drivers to fix gha matrix failure. Also fixed a cosmetic error when compiling kernel about not able to modify kernel git hooks 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 kernel for vim1s. Made sure common drivers are getting compiled. 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 Restore CONFIG_OF_CONFIGFS=y accidentally(?) lost in https://github.com/armbian/build/commit/fae4f664397656e5a432a24b8adc5c237a53227e How Has This Been Tested? [x] Compile current&edge kernels, check overlays works 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 Jira reference number AR-2038 AR-1870 Closes https://github.com/armbian/build/issues/5729 No more changing global configs. How Has This Been Tested? [x] Few manual runs 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] Any dependent changes have been merged and published in downstream modules View the full article

Description Adds minimalist cloud-init support functionally equivalent to the Ubuntu implementation for the Raspberry PI. addresses issue #6197 Jira reference number AR-2035 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. View the full article

Description Adds LVM support for Armbian. Root partition will be created in an LVM volume group, VG name can be configured. Implements issue #6188. The feature has been tested in all targets I have available. Jira reference number AR-2032 View the full article

Description As per the discovery made by @brentr , the current kernel for rockchip64 become hugely bigger than usual (13M vs. 18M, gzipped). After some checks, it turns out that what happened before with the appearance of useless and unwanted cruft (PATA, ACPI, SCSI :roll_eyes: , whatever... see linked PR) happened again. This PR restores the a sane kernel config for current 6.6 and edge 6.7, rebasing over kernel 6.1. I double checked against latest sane 6.6 I could find, which is 6.6-rc4 and differences are minor. I attach a "patch" file with the differences from sane 6.6-rc4 and 6.6.13 in this PR (use less -R to see with colors) in case someone wants to check it out. A note about rtw88 module: the module has been enable with all the USB/SDIO supported devices, except for rtl8723ds which @brentr recently disabled in another PR because he could not let it work on his hardware. In this case, the rtl8723ds realtek module is enabled as well. How Has This Been Tested? [ ] Test on rk3399 device [ ] Test on rk3328 device [ ] Test on rk356x device [ ] Test on rk3588 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 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 Bumping Khadas vim1s and vim4 kernel to 5.15. This seems to resolve the display issue on cinnamon, but this seems to have the same edid parsing based monitor filtering and hence some monitors are back to not working. I am working on figuring that out and will raise a separate PR for that later. This also solves the issue where disconnecting wifi was raising kernel oops 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 vim1s and vim4 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

By creating a real-time AI chatbot communication system using WhisperLive and WhisperSpeech, we have addressed the unnatural delay in current bot interactions for seamless conversation. View the full article

Description Deleted merged patches in kernel v6.8-rc1 and fix other patch errors. Add a new patch 0033-tools-Makefile-delete-missing-cgroup_clean.patch to fix make clean error in tools. 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 with command ./compile.sh kernel BOARD=rock-5b BRANCH=edge DEB_COMPRESS=xz KERNEL_GIT=shallow [x] Boot on rock5b fine 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 Current branch was bumped to 6.8-rc which does not build. How Has This Been Tested? [ ] Build 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 Add preset variables so that image can do first login automaticly without user interaction. I store variables like username/password in /root/.not_logged_in_yet so that it will get deleted after firstlogin. We can add set these variables by extension post_family_tweaks in board config: function post_family_tweaks__firstlogin_preset_configs() { display_alert "$BOARD" "preset configs for firstlogin" "info" echo "PRESET_USER_SHELL=bash" > "${SDCARD}"/root/.not_logged_in_yet echo "SET_LANG_BASED_ON_LOCATION=y" >> "${SDCARD}"/root/.not_logged_in_yet echo "PRESET_LOCALE=zh_CN.UTF-8" >> "${SDCARD}"/root/.not_logged_in_yet echo "PRESET_TIMEZONE=Asia/Shanghai" >> "${SDCARD}"/root/.not_logged_in_yet echo "PRESET_ROOT_PASSWORD=Armbian" >> "${SDCARD}"/root/.not_logged_in_yet echo "PRESET_USER_NAME=jfliu" >> "${SDCARD}"/root/.not_logged_in_yet echo "PRESET_USER_PASSWORD=Armbian" >> "${SDCARD}"/root/.not_logged_in_yet echo "PRESET_DEFAULT_REALNAME=Jfliu" >> "${SDCARD}"/root/.not_logged_in_yet } 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 command ./compile.sh BOARD=fl700n BRANCH=edge DEB_COMPRESS=xz KERNEL_GIT=shallow BUILD_DESKTOP=yes BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base DESKTOP_APPGROUPS_SELECTED='' [x] Boot image with or without ethernet network, board boots into xfce desktop environment without user interaction [ ] Haven't tested on board with wireless. I haven't implement automatic Connect via wireless? [Y/n]. I will do it later. 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

This is the fourth and final part in a series on persian-rug, a Rust crate for interconnected objects. We've touched on the two big limitations: lack of deletion and lack of enforced matching between proxies and containers. Let's look at other solutions. View the full article

The recently mainlined RTW88 driver for the RTL8723DS does not work at all on the RockPI-S No error messages, but no radio either. The RTW88 driver also blocks the bluetooth radio as well. Reverting back to RTL's own driver, which is still in the patched tree, fixes all this. I'll be working with the RTW88 driver authors get their 8723DS driver working, but, my experience with the RTW88 driver for the USB bus version of this WiFi chip is that it uses significantly more CPU than RTL's driver. To cope with the ever expanding Linux kernel, this patch also includes overriding u-boot's value of fdt_addr_r in the RockPI-s boot.cmd script. 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-2034 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 'current' image and verified it booted and WiFi & Bluetooth functioned [x] Built 'edge' image and verified it booted and WiFi & Bluetooth functioned 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 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 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 have been merged and published in downstream modules View the full article

Description Fix incorrect data read sometimes in last 4kb of compressed files on btrfs. In my case only last 2560 bytes of dtb file was broken, so the only issue was warnings in dmesg on boot. Well, last 2560 of vmlinuz was also broken, but fortunately there was only '\0' bytes, so system was functional and this problem was unnoticed. Patch taken from upstream uboot: https://github.com/u-boot/u-boot/commit/b1d3013d024086c042dbae4ddd99db56bb55b5e7 How Has This Been Tested? [x] Boot from zstd compressed btrfs partition [x] Check uboot loaded kernel sha1sum in uboot console 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 Enables spi flash on Rock-5b Recreated as a patch based on discussion in #6137 will take me some time to setup and do the big-boy pants stuff to submit to mainline but I'll def work on it. View the full article

Description Was having boot issues with RK3568 on edge 6.7.... Per @amazingfate 's advise.. updating montjoie's Rk35xx crypto patch from our Rk3588 patchset resolved the issue. Tested on: RK3568 - nanopi-r5s RK3399 - nanopc-t4 View the full article

Description This change includes kernel patches to provide the following overlays when using armbian-config on the Orange Pi Zero 2 and Orange Pi Zero 3 boards. I2C IR USB OTG SPI UART These boards share very similar SOCs (RH616 / RH618), and the existing configuration that was also shared with the bigtreetech board did not function correctly for the Orange Pi Zero 2/3 boards, so the Zero 2/3 board overlay configuration was split out into its own files, and the board configurations updated to reference the new overlays. Note: The patches for these overlays have been added to the 6.1, 6.6 (current), and 6.7 (edge) patch directories but it appears the 6.1 code may not be used with the current configurations for these boards. Jira reference number [AR-9999] How Has This Been Tested? These updates have been tested with the following configurations [x] Zero 2 Current and Edge kernel with Debian userspace [ ] Zero 3 Current and Edge kernel with Debian userspace (current pending testing) The validation process at a high level Boot clean Armbian image and configure base configuration Launch armbian-config and turn on all Hardware overlays options for the board Reboot when prompted, and confirm that overlays apply correctly in early boot logs (serial connection) Confirm hardware devices are available in the OS 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

In my initial commit I assumed CONFIG_USE_PREBOOT=y was enabled by default. I was wrong. As reported by MicroLinux (Salva) on DISCORD the unit was still having issues booting. I sent him a patch I use which enables preboot and he reported back that "It boots fine now". NOTES: The patch he tested also had boot logo support enabled. In my testing boot logo support is not required. If for some reason in the future there are still eMMC boot issues, than maybe adding a slight delay "sleep 2" to preboot would suffice. https://github.com/armbian/build/pull/5858 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 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