RSS Bot

Description Reapply https://github.com/armbian/build/commit/305886b111ff76a53693a3c171751a8830d106c5 and fix compilation & spi image booting 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. [x] Build and boot 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 Not sure if this PR makes any sense but welp. I leave that to those who actually know what they are doing ^^ Anyway just for the heck of it I tried what happens if I build Station-P1 against rockchip64 family instead of media Jira reference number [AR-x] How Has This Been Tested? [x] Build Bookworm CLI edge with Linux 6.6.7 [x] Boot Bookworm CLI works [x] Enable 2GHz OC overlay works [x] Install to eMMC works [x] Desktop XFCE works [ ] WiFI does not work but might have been broken before as well. No clue. armbianmonitor: https://paste.armbian.com/oyoyiqoper 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 Add uboot 'button' cmd and add Recovery button to rk3318 uboot dts. In the linux kernel dts button is labeled lowercase "recovery", but I've chosen "Recovery" as it is more frequent in uboot dts'es: $ (cd cache/sources/u-boot-worktree/u-boot/v2022.07/arch/arm/dts; grep -ir 'label.*"recovery"' .) ./rk3399-nanopc-t4.dts: label = "Recovery"; ./rk3399-khadas-edge.dtsi: label = "Recovery"; ./rk3399-roc-pc.dtsi: label = "Recovery"; ./rk3328-rock-pi-e.dts: label = "Recovery"; ./rk3066a-mk808.dts: label = "recovery"; ./rk3399-nanopi-m4b.dts: label = "Recovery"; How Has This Been Tested? [x] boot rk3318 with modified uboot.cmd to test new command: if button Recovery; then echo "Recovery ON" else echo "Recovery OFF" fi 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 patches to support HEVC hardware video decoder provided by rkvdec in rockchip64 socs like rk3328 and rk3399. This leverages the hardware features reducing cpu usage by a wide margin. Also provides some patches and fixes for v4l2 whose patch files seems big, but most is just description text. Can be tested along with the repository published by me on this forum post. Jira reference number AR-1997 How Has This Been Tested? [x] Compile current 6.1 rockchip64 kernel [x] Compile edge 6.6 rockchip64-kernel [x] Test current kernel on existing rk3399 installation on OrangePi4 LTS board [x] Test edge kernel on existing rk3399 installation on OrangePi4 LTS board No harmful side effects have been detected during tests, the system seems stable. Test against 1080p60 h.264 video: Test against 1920x860p30 h.265 video: 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 Related to auto-test system only. View the full article

Description We are storing logs at our pastebin server(s). Switching back to primary as secondary is failing. paste.next.armbian.com -> paste.armbian.com How Has This Been Tested? Made one test build with SHARE_LOG=yes which generated logs on paste bin server. 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 As per subject, plus kernel configs have been updated and enabled rtl8xxx untested wifi chips How Has This Been Tested? [x] Kernel patches apply with current kernel [x] Kernel patches apply with edge 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 As per subject, plus kernel configs have been updated and enabled rtl8xxx untested wifi chips How Has This Been Tested? [x] Kernel patches apply with current kernel [x] Kernel patches apply with edge 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

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 Clean deprecated parts in patches. How Has This Been Tested? [x] Build test 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 to latest lts versions 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 should get wifi working on OrangePi Zero2 on current and edge kernel 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] Not tested as I don't have the device. @AGM1968 Could you please test 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 This PR adds a board config file for RPi 5. While on it, the PR also removes dependency on flash-kernel. Instead some custom scripts are added into the bsp package for installation of updated dtb, kernel and initrd files. Using both rpi4b and rpi5b will produce images compatible with rpi5, but the image created with BOARD=rpi5b will not run on older hardware. The kernel config, patches etc are shared between both boards. To prevent creating new family for RPI5 specific kernel, I have added support for something I call kernel variants. This is basically going to be almost same kernel with extremely small changes that doesn't justify creating new family and yet still needs a different kernel deb file. This is being achieved by adding a suffix to the kernel similar to how we add suffix to bsp files when using flash-kernel among other things. Lastly I have also changed config.txt and cmdline.txt to match official raspberry pi versions as much as possible 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 both RPi4 and RPi5 using mantic as RELEASE 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 Fixes board not properly powering off and rebooting. How Has This Been Tested? [x] Reboots again [x] Powers off 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 [ ] 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 Add rockchip drivers to the uefi-arm64 kernel config to be able to use https://github.com/jaredmcneill/quartz64_uefi on some rk3566/rk3568 boards. How Has This Been Tested? Booted a Pine SOQuartz/CM4IO board with the EDK2 bootloader mentioned above on a sdcard and the patched generic uefi-arm64 image on an nvme drive. Tested with ACPI and Devicetree. 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

As we continue improving the kernel integration landscape on multiple fronts, this also means making better tests available for all. Working closely with the community, we have now landed a new, ready-to-use, kselftest upstream in mainline Linux. View the full article

Description TOC is generated by GitHub, so we don't need to expose it. Checklist: [x] My code follows the style guidelines of this project View the full article

Description Update odroidxu4-current kernel to 6.1.67. 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 Recently, I accidentally erased an SPI flash with an bootloader installed and tried to reinstall the latest bootloader. But it did not recognize the attached disks and proceeded to TFTP Boot. Only by stopping autoboot and hot-swapping the disks or reattaching did the bootloader recognize it, and I was then able to boot with the command. I investigated and found that the problem occured after U-Boot was updated to v2023.01. This issue has been resolved by applying a patch that was previously used in v2022.07. How Has This Been Tested? By compiling U-Boot from trunk (linux-u-boot-odroidhc4-current_24.2.0-trunk) for v2023.01, v2023.04, v2023.07, v2023.10 and testing those on ODROID-HC4. [X] Test A - Compiling U-Boot without patch and trying to boot in v2023.01 and later versions U-Boot 2023.01 (Dec 10 2023 - 18:25:52 +0900) odroid-hc4 Model: Hardkernel ODROID-HC4 SoC: Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2) DRAM: 1 GiB (effective 3.8 GiB) Core: 392 devices, 32 uclasses, devicetree: separate MMC: sd@ffe05000: 0 Loading Environment from nowhere... OK In: serial Out: serial Err: serial Board variant: hc4 Net: eth0: ethernet@ff3f0000 PCIE-0: Link up (Gen2-x1, Bus0) starting USB... Bus usb@ff500000: Register 3000140 NbrPorts 3 Starting the controller USB XHCI 1.10 scanning bus usb@ff500000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 2 1 0 Device 0: unknown device scanning bus for devices... SATA link 0 timeout. SATA link 1 timeout. AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq stag led clo pmp pio slum part ccc sxs Device 0: unknown device Card did not respond to voltage select! : -110 MMC Device 1 not found no mmc device at slot 1 MMC Device 2 not found no mmc device at slot 2 Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.0.4 (7 ms) *** Warning: no boot file name; using 'C0A80004.img' Using ethernet@ff3f0000 device TFTP from server 192.168.0.1; our IP address is 192.168.0.4 Filename 'C0A80004.img'. Load address: 0x1000000 [x] Test B - Compiling U-Boot with applying patch and trying to boot in v2023.01 and later versions U-Boot 2023.01 (Dec 10 2023 - 22:20:23 +0900) odroid-hc4 Model: Hardkernel ODROID-HC4 SoC: Amlogic Meson SM1 (S905X3) Revision 2b:c (10:2) DRAM: 1 GiB (effective 3.8 GiB) Core: 389 devices, 30 uclasses, devicetree: separate MMC: sd@ffe05000: 0 Loading Environment from nowhere... OK In: serial Out: serial Err: serial Board variant: hc4 Net: eth0: ethernet@ff3f0000 PCIE-0: Link up (Gen2-x1, Bus0) starting USB... Bus usb@ff500000: Register 3000140 NbrPorts 3 Starting the controller USB XHCI 1.10 scanning bus usb@ff500000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 2 1 0 Device 0: unknown device scanning bus for devices... Target spinup took 0 ms. Target spinup took 0 ms. AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq stag led clo pmp pio slum part ccc sxs Device 0: (0:0) Vendor: ATA Prod.: Samsung SSD 860 Rev: RVT0 Type: Hard Disk Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) Device 1: (1:0) Vendor: ATA Prod.: Samsung SSD 860 Rev: RVT0 Type: Hard Disk Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) Device 0: (0:0) Vendor: ATA Prod.: Samsung SSD 860 Rev: RVT0 Type: Hard Disk Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) ... is now current device Scanning scsi 0:1... Found U-Boot script /boot/boot.scr 8147 bytes read in 2 ms (3.9 MiB/s) ## Executing script at 08000000 U-boot default fdtfile: amlogic/meson-sm1-odroid-hc4.dtb Current variant: hc4 226 bytes read in 1 ms (220.7 KiB/s) Current fdtfile after armbianEnv: amlogic/meson-sm1-odroid-hc4.dtb Mainline bootargs: root=UUID=masked rootwait rootfstype=ext4 splash=verbose console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=7 ubootpart= libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u net.ifnames=0 cgroup_enable=memory swapaccount=1 19016823 bytes read in 298 ms (60.9 MiB/s) 27433472 bytes read in 426 ms (61.4 MiB/s) 76314 bytes read in 13 ms (5.6 MiB/s) Working FDT set to 4080000 232 bytes read in 4 ms (56.6 KiB/s) Applying kernel provided DT fixup script (meson-fixup.scr) ## Executing script at 32000000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 19016759 Bytes = 18.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Working FDT set to 4080000 Loading Ramdisk to 3eddd000, end 3ffffc37 ... OK Loading Device Tree to 000000003ed62000, end 000000003eddcfff ... OK Working FDT set to 3ed62000 Starting 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

Description This PR fixes ES8388 audio on OPi5, add opi5b devicetree and add mainline uboot support. 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. [x] Boots well with 2024.01-rc4 uboot [x] There are no es8388 errors in dmesg output It would be nice if someone tests SPI flash boot + nvme ssd. I've not tried it because i don't have free M2 ssd rn. rkspi_loader.zip 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 Small followup fix https://github.com/armbian/build/pull/6006 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 and boot rk3318-box from second partition 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 "optional/boards" directory seems to have been deprecated and actually never used so much. Remove the last board support package there (rk3318-box) and move into extension as suggested by @rpardini. Ancillary BSP files have been removed too. The extension may have global interest because it was a workaround for X.Org and Lima driver: the former was not able to autodetect the latter with some revision combinations. That configuration fixes the autodetection. At the moment, it has been enabled in rk3318-box board and rk322x family. How Has This Been Tested? [x] Compile debian bookworm image for rk3318-box and verify 40-serverflags.conf presence [x] Compile debian bookworm image for rk322x-box and verify 40-serverflags.conf presence 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 As per title. How Has This Been Tested? [ ] Build test at CI Checklist: [ ] My changes generate no new warnings View the full article

Original version destroyed journal on command postrotate as files in /var/log.hdd/journal are overwritten by cat. With the patch journal is not damaged anymore. Description In original version in postrotate files in /var/log.hdd/journal are deleted by the command dest="/var/log/$file" cat $file > $dest as /var/log/journal is a symling to /var/log.hdd/journal files are cated on themselves which ends up with an empty file. How Has This Been Tested? check journal by journactl. There is no data earlier than today 0:00. Also "journalctl --verify" shows that journal is damaged. 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 As specified in PR https://github.com/armbian/build/pull/5967, there was a nasty mistake in rockchip and rk322x source files that were attempting to create two groups (gpio and i2c) on the building host instead of the built image. This caused the build system to crash when the groups were already present on the building host, which is totally not desiderable, and the intended feature was also broken. After some inspection, the groups were leveraged by a couple of udev rules to allow non-root users have access to gpio and i2c resources out of the box. This PR fixes the group creation on the target built image. Note: gpio and i2c gids starts from 900 because gids nearby 1000 are already taken by some existing services. Note 2: this supersedes https://github.com/armbian/build/pull/5967 which can be closed as well. Jira reference number AR-1935 How Has This Been Tested? [ ] Compile debian bookworm for rockchip family, verify the presence of groups in target image [x] Compile debian bookworm for rk322x family, verify the present of groups in target image 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