RSS Bot

Description The default power_allocator governor will not speed up the pwm fan when temp rises up, but step_wise will do according to cooling_level defined in the devicetree. Before this commit I have to set the governor manually by command echo step_wise > /sys/class/thermal/thermal_zone0/policy on rock5b. Since there are many rk3588 boards have pwm-fan node defined in the devicetree, I think it's better to set this governot to default. 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] No need to manualy set the governor after installing the kernel 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

starfive/edge: bump 6.1.23 to 6.1.y; rebase to v6.1.30; hammer dma,pwm patches; update .config no idea if this works, at least it builds View the full article

Description U-boot will go into boot loop when SSD is attached to the USB 3 port. There is a conflict in the patch patch/u-boot/v2022.10/meson64-boot-usb-nvme-scsi-first.patch. The boot loop has been resolved by removing the patch or by placing the priority of USB below MMC. How Has This Been Tested? By compiling u-boot.bin from trunk (linux-u-boot-bananapim5-current_23.05.0-trunk) for u-boot v2022.10 and v2023.4 and testing it on Bpi-M5. Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Test A - Removing patch/u-boot/v2022.10/meson64-boot-usb-nvme-scsi-first.patch [x] Test B - Reordering the Priority of USB to be below MMC. By executing Test A, BPi-M5 can boot successfully. It shows that the current patch to give higher order priority to usb/nvme/scsi create conflict to the booting process. Test B reorder the USB to lower priority. The BPi-M5 can still boot successfully without any errors. 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

😢 still fallout from yesterday's 6.1.30 / 6.3.4 chaos and we're 6.2.16 in the middle EOL View the full article

Description Also update rk35xx to 5.10 rkr4 for rk356x 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] Build legacy image for rock3a [x] Image works on rock3a 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

Released last week, Weston 12.0 brings a number of highlights including two new backends, support for multiple scanout devices, and the addition of new protocol implementations. Here's a look at some of the changes that have landed in this new version. View the full article

Description Just a board status change. View the full article

BPI-CM4 IO: RTW88: Realtek 8822CS SDIO Wireless Support Additional driver support: Realtek 8822BS SDIO wireless network adapter Realtek 8822BU USB wireless network adapter Realtek 8822CS SDIO wireless network adapter Realtek 8822CU USB wireless network adapter Realtek 8821CS SDIO wireless network adapter Realtek 8821CU USB wireless network adapter Jira reference number AR-1724 How Has This Been Tested? Built a new kernel with the latest changes, installed it, added required firmware and rebooted. ____ ____ _ ____ __ __ _ _ ___ ___ | __ )| _ \(_) / ___| \/ | || ||_ _/ _ \ | _ \| |_) | | | | | |\/| | || |_| | | | | | |_) | __/| | | |___| | | |__ _| | |_| | |____/|_| |_| \____|_| |_| |_||___\___/ Welcome to Armbian 23.05.0-trunk Bookworm with Linux 6.1.30-meson64 No end-user support: built from trunk System load: 2% Up time: 31 min Memory usage: 4% of 3.69G IP: 10.0.0.XXX CPU temp: 52°C Usage of /: 6% of 30G RX today: 4.9 MiB [ 0 security updates available, 19 updates total: apt upgrade ] Last check: 2023-05-25 07:50 Last login: Tue May 23 14:27:27 2023 lsmod | grep rtw rtw88_8822cs 16384 0 rtw88_8822c 462848 1 rtw88_8822cs rtw88_sdio 20480 1 rtw88_8822cs rtw88_core 159744 2 rtw88_8822c,rtw88_sdio mac80211 606208 2 rtw88_sdio,rtw88_core cfg80211 430080 2 rtw88_core,mac80211 sudo iwconfig lo no wireless extensions. end0 no wireless extensions. wlan0 IEEE 802.11 ESSID:"XXX" Mode:Managed Frequency:5.785 GHz Access Point: A2:3D:CF:FF:C5:EB Bit Rate=175.5 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=62/70 Signal level=-48 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:28 Missed beacon:0 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 Add cpu-frequency to orangepizero2, allwinner h616 6.x.y kernels Follow up Jira reference number AR-1683 How Has This Been Tested? Armbian 23.05.0-trunk Bullseye ttyS0 orangepizero2 login: alistair Password: ___ ____ _ _____ ____ / _ \| _ \(_) |__ /___ _ __ ___|___ \ | | | | |_) | | / // _ \ '__/ _ \ __) | | |_| | __/| | / /| __/ | | (_) / __/ \___/|_| |_| /____\___|_| \___/_____| Welcome to Armbian 23.05.0-trunk Bullseye with bleeding edge Linux 6.2.16-sunxi64 No end-user support: built from trunk System load: 13% Up time: 0 min Memory usage: 8% of 984M IP: 10.0.0.12 CPU temp: 42°C Usage of /: 5% of 29G [ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ] alistair@orangepizero2:~$ dmesg | grep cpu* [ 0.000000] percpu: Embedded 19 pages/cpu s38760 r8192 d30872 u77824 [ 0.000000] pcpu-alloc: s38760 r8192 d30872 u77824 alloc=19*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] printk: log_buf_len individual max cpu contribution: 4096 bytes [ 0.000000] printk: log_buf_len total cpu_extra contributions: 12288 bytes [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.041807] cpuidle: using governor menu [ 0.062518] cryptd: max_cpu_qlen set to 1000 [ 0.700973] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear) [ 0.875685] ledtrig-cpu: registered to indicate activity on CPUs [ 2.053265] sun50i_cpufreq_nvmem: Using CPU speed bin speed0 [ 8.995945] cpufreq: cpufreq_online: CPU0: Running at unlisted initial frequency: 408000 KHz, changing to: 480000 KHz [x] Test A BUILD compiled and booted 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 Test build from here: https://github.com/amazingfate/armbian-rock5b-images/releases/tag/20230524-0807 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] Image build sucessfully [x] Image running fine on rock5b 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

drivers_network: fix bluetooth stuff landed in 6.1.30/6.3.4 but not in 6.2.y drivers_network: wireless-driver-for-uwe5622-park-link-v6.1-post: fix for 6.1.30 drivers_network: rtl8723cs bt: disable landed patches in 6.1.30/6.3.4; keep for 6.2, which is EOL rockchip64/current 6.1.y: fix broadcom bt serdev hack for 6.1.30 rockchip64/edge 6.3.y: fix broadcom bt serdev hack for 6.3.4 Only after doing this I saw https://github.com/armbian/build/pull/5240 -- sorry View the full article

Description A bunch of patches did not apply anymore to rk322x/rockchip familes due to small upstream changes. This PR fixes the annoyance. How Has This Been Tested? [x] rk322x family patches apply cleanly for current kernel [x] rockchip family patches apply cleanly for current 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 1 out of 1 hunk FAILED --> (43) WARNING: * applying patch/misc/wireless-rtl8723cs/bluetooth-btrtl-quirk-local-ext-features.patch [ failed ] 10 out of 14 hunks FAILED Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored --> (43) WARNING: * applying patch/misc/wireless-rtl8723cs/Bluetooth-btrtl-add-support-for-the-RTL8723CS.patch [ failed ] Ass per title. https://paste.next.armbian.com/girevorico @paolosabatino Also bump Allwinner Jira reference number [AR-9999] How Has This Been Tested? [x] Compiling current meson64 kernel 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

rock-5a: add support for Rock-5A, WiP, using rockchip-rk3588 - by @amazingfate Split-off from https://github.com/armbian/build/pull/5230 Board file straight from https://github.com/amazingfate/armbian-rock5b-images/blob/master/rock-5a.conf View the full article

rockchip64/edge 6.3.y: manually fix Radxa E25/CM3 patches, rebase to v6.3.3, update .config fix E25/CM3 patches from https://github.com/armbian/build/pull/5165#issuecomment-1560666066 rebase all patches to v6.3.3, archeology for missing mboxes update .config, no actual changes Still trying to keep edge clean & patching working... View the full article

kernel: drivers: wireless-rtl8723du-6.3.patch: don't patch the same thing twice Can't really tell how this happened. Am I missing something, @paolosabatino? This removes second identical patch in the same file... 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-1754 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. booted and verified that wlan0's MAC was being derived from the CPU's serial number again 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 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] Tested each build with two iperf3 client sessions bound to both network interfaces simultaneously to iperf3 server sessions on two computers with Gb NICs (to hammer both ports simultaneously). Performance was as expected. 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

New boards & fixes; this de-media-fies the khadas-edge2 khadas-edge2: switch to rockchip-rk3588 legacy kernel add bluetooth-hciattach for working bluetooth most of the work done by @monkaBlyat mekotronics (all boards): use new bluetooth-hciattach extension for out-of-the-box working bluetooth rock-5a: add support for Rock-5A, WiP, using rockchip-rk3588 - by @monkaBlyat bluetooth-hciattach: new generic extension to facilitate adding hciattach systemd service, given the correct params this is not specific to rk3588 and can be reused by others View the full article

image: sanity check: warn if any deb artifacts' actually-installed version does not match artifact-built version this catches problems with outdated/crazy repos, customize doing wrong things, wrong pinning, etc View the full article

rootfs-to-image: find, warn, and remove dangling symlinks in FAT32 /boot otherwise rsync gags. it should not happen, but if it does, we get a nice warning now View the full article

artifacts: introduce calculate_hash_for_variables() which normalizes the input; use in kernel/uboot/etc Does not look like it, but this is a bugfix -- UBOOT_TARGET_MAP might contain $SRC (due to BL31=, etc) and that is hashed into something only ever matches by accident Also fixes artifact-armbian-desktop vs appgroups/config_base differences some hashed variables might contain "${SRC}", so hashes never match, unless built in Docker - this strips away SRC from all vars and adds debugging so we can detect more later. artifact-uboot: include more variables into hash, for ATF & rk stuff artifact-armbian-desktop: - hashed vars actually contain /armbian in different context, skip normalization in this case - include results of relevant aggregation into artifact_input_variables - otherwise: desktops with different appgroups/configs lead to build failures in pipeline - will cause warnings in JSON preparation step, if more than one appgroups/config combo is targeted, since repo can only have one View the full article

artifacts (all): implement DONT_BUILD_ARTIFACTS=any (so we don't need to list them all for CI image builds) View the full article

Description As per description. Jira reference number AR-1751 View the full article

Description Enable INNOLUX_AFJ101_BA2131 panel on rk3588 legacy kernel Jira reference number [AR-9999] How Has This Been Tested? [x] Build kernel 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