RSS Bot

Adding in support for new desktop being added . i3 lxde lxqt and others to be added as made View the full article

Fix path for img in the lightdm login background View the full article

Description Instead of requesting to install gcc-or1k-bin package unconditionally, request it only when building images with crust support. Also consolidated crust related configuration into a separate file. Jira reference number AR-1786 How Has This Been Tested? [X] ./compile.sh DOCKER_ARMBIAN_BASE_IMAGE="debian:bullseye" BOARD=nanopineo works as it doesn't need crust support [X] ./compile.sh DOCKER_ARMBIAN_BASE_IMAGE="debian:bullseye" BOARD=nanopiduo2 fails as it bullseye doesn't include gcc-or1k-bin package and hence reported as unsupported system [X] ./compile.sh BOARD=nanopiduo2 works as default release is jammy that has the required package 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description I just move config/kernel/linux-rockchip-rk3588-legacy.config to config/kernel/linux-rk35xx-legacy.config, and make them share the same family rk35xx. Now rk356x will use the same kernel rk3588 legacy is using. I tested the new kernel on my rock3a, working well. 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 kernel of rock3a and rock5b, same result. [x] New kernel 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

Description This PR ports over recent changes for the Orange Pi Zero 2 board brought by AGM1968 for 6.2.y kernel, back to 6.1.y kernel (current LTS). Changes being ported (minor modifications required to the patching metadata, overall code & structure intact): https://github.com/armbian/build/pull/5247 (CPU scaling) https://github.com/armbian/build/pull/5270 (on-board LED states changes) How Has This Been Tested? CPU scaling tests [x] Test A: Build & boot-up the board, making sure it still works [x] Test B: Run ThomasKaiser/sbc-bench See: https://github.com/mdziekon/armbian-build/pull/2 LED changes tests [x] Test A: Build & boot-up the board, making sure it still works, and the LED changes have been applied 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

Powered by Rust, the video codec stack on ARCVM is now bringing faster and more reliable video decoding on ChromeOS. Here's how Collabora has been helping shape video virtualization for Chromebooks, and what it means for end users. View the full article

Update maintainers synched from the database View the full article

All patches apply and resolves issue: https://github.com/armbian/build/issues/5357 Jira reference number AR-1785 [ ] 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 Bump 32-bit kernel to 6.3.8. I didn't bumped it for 64-bit sunxi devices as drv-rgb-add-ws2812.patch introduced in #5267 makes use of of_get_named_gpio_flags function which is removed in 6.3. As I don't have a Bigtreetech cb1, I am not comfortable modifying code to fix this patch. The kernel module added by drv-rgb-add-ws2812.patch is not enabled for 32-bit devices and hence it doesn't cause compilation issues on 32-bit sunxi kernel. Excluding drv-rgb-add-ws2812.patch, I have updated any patch that was broken, and have disabled patches where changes were present upstream. Also disabled same rockchip related patches that I disabled in #5326 How Has This Been Tested? [X] Created an image and booted on Nanopi duo2 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 script to generate CODEOWNERS How Has This Been Tested? [X] Run and check CODEOWNERS 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 [X] Any dependent changes have been merged and published in downstream modules View the full article

Update maintainers synched from the database View the full article

Description Fixed PR from wrong DB Jira reference number AR-1712 View the full article

Description This PR adds support for Recore A5, A6, and A7 hardware. Recore is a 3D printer control board based on Allwinner A64. Since the board uses the AR100 for real time stepping, the SCP is disabled and instead a version of Klipper is loaded instead. How Has This Been Tested? The patches have been tested by building the current and legacy kernels with the minimal images. [ ] Minimal image with current kernel [ ] Minimal image with legacy 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

removed linked dir for bookworm under desktops put new bookworm desktops into place put new skel files into place for themeing of desktops pre how Igor wants desktops themed added new desktops to the armbian.firstlogin script so new desktops are supported. I took out any duplicate files and shrunk it down to 1 cairo-doc dir in the skel.all dir users can add their file managers to the cairo if they want to. Cinnamon/gnome/icemw/lxde/lxqt/mate/xfce desktops. I fallowed the task-(desktop)-desktop install debian now uses installing all proper files the desktops require . I have run test builds on current desktop and they all build correctly. View the full article

Description Added support for midstream kernels to the interactive config kernel branch selection. 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] Interactive configure rock 5B 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

I moved the new skel dir's to a sud dir of debian-skel. I removed gnome-builder, freecad and the launch-bars from the app groups. leaving it to the user to add these part . this shold bring images back downin size. Printing and filesharing moveed to app-groups like the debian community said it shouldbe. To make it cleaner smaller base desktop install. as filesharing and printing are optional addons if you want web-dev removed I will but I know alot who want the tools to dev and test web pages. View the full article

Description Add pwm fan support to NanoPi R4S. Document from FriendlyElec: https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R4S#How_to_Control_Fan_Speed_for_Cooling And reference code: https://github.com/friendlyarm/kernel-rockchip/commit/f74ac319f02e2d22cdd33227e7f167e4232809f9 How Has This Been Tested? build and run on R4SE hardware. [x] fan works [x] /sys/devices/virtual/thermal/thermal_zone0/trip_point_[3/4]_temp controls two speed of the fan 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 This PR enabled USB port present on the expansion board for the OrangePi Zero 2 sbc. This change applies to the current current variant of the OS for this board (Kernel 6.1.y). (Similar PR for 6.2.y kernel here: #5344) How Has This Been Tested? Requirements: Any USB stick with basic file system present (eg. exFAT) and some files / folders on it Logged in as root or as a user with sudo priviledges [x] Test A: make sure the change does not break the board when used WITHOUT the expansion board Boot up the board Check whether the base USB port still works correctly lsusb shows the USB stick when plugged into the port mount /dev/sda1 /media/<mountpoint> is able to mount the USB stick plugged into the port [x] Test B: check whether the ports work when expansion board is plugged in Plug a USB stick into one of the additional ports Check whether the tested port works correctly lsusb shows the USB stick when plugged into the port mount /dev/sda1 /media/<mountpoint> is able to mount the USB stick plugged into the port ls /media/<mountpoint> properly enumerates files / folders on the stick umount /media/<mountpoint> is able to unmount the USB stick Repeat for the other port on the expansion board 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 This PR enabled USB port present on the expansion board for the OrangePi Zero 2 sbc. This change applies to the current edge variant of the OS for this board (Kernel 6.2.y). How Has This Been Tested? Requirements: Any USB stick with basic file system present (eg. exFAT) and some files / folders on it Logged in as root or as a user with sudo priviledges [x] Test A: make sure the change does not break the board when used WITHOUT the expansion board Boot up the board Check whether the base USB port still works correctly lsusb shows the USB stick when plugged into the port mount /dev/sda1 /media/<mountpoint> is able to mount the USB stick plugged into the port [x] Test B: check whether the ports work when expansion board is plugged in Plug a USB stick into one of the additional ports Check whether the tested port works correctly lsusb shows the USB stick when plugged into the port mount /dev/sda1 /media/<mountpoint> is able to mount the USB stick plugged into the port ls /media/<mountpoint> properly enumerates files / folders on the stick umount /media/<mountpoint> is able to unmount the USB stick Repeat for the other port on the expansion board 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

@adeepn @rpardini As discussed here: https://github.com/armbian/build/pull/5315 In order to update to the latest rtl8822cs BT firmware for the G12/SM1 family of boards and still provide the downstream firmware for the AXG/GXL family, I created an apt hook to ensure the proper firmware stays in place. I unfortunately can’t test this beyond creating an IMG as I don’t own the unit and the firmware isn’t currently committed. In order to test, someone would need to boot an IMG built from this commit, add the latest firmware to the booted unit and install a package to see if the apt hook works. Firmware commit: https://github.com/pyavitz/armbian-firmware/commit/a7bf7c7cc8a85dbbc28c1c409e09b11917ebc2b6 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

Looks like this got missed when removing KERNEL_ONLY. Having it here in the first example causes that example to fail, Remove it. [x] Test build with KERNEL_ONLY fails [x] Test build without KERNEL_ONLY passes 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 made corresponding changes to the documentation [x] My changes generate no new warnings View the full article

Description Since of historical reasons script armbian-install is still creating a log file with name /var/log/nand-sata-install.log as well as using other artifacts from folder /usr/lib/nand-sata-install. I would like to align those names to comply with the original script name having been run: If run as nand-sata-install => create /var/log/nand-sata-install.log, lookup artifacts in /usr/lib/nand-sata-install If run as armbian-install => create /var/log/armbian-install.log, lookup artifacts in /usr/lib/armbian-install To achieve 2. I did: rename folder packages/bsp/common/usr/lib/nand-sata-install -> packages/bsp/common/usr/lib/armbian-install - since this is now the most likely current one. create a symbolic link packages/bsp/common/usr/lib/nand-sata-install linking to packages/bsp/common/usr/lib/armbian-install for backward compatibility. How Has This Been Tested? Tested on a board (Cubietruck) installed. 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

Description Hello all, This PR adds support for the Texas Instruments SK-AM64B. Features, schematics, and purchase links can be found on the board page[0]. We work to ensure our silicon/boards have "Upstream First" Linux support, so this board makes use of stock upstream U-Boot and Linux, no patching needed to utilize the full set of feature. The only odd part here is our first-stage bootloader, which is built from fetched sources separately (see compile_k3_bootgen() in k3.conf). If a pre-built binary for this is preferred just let me know. Thanks! [0] https://www.ti.com/tool/SK-AM64B How Has This Been Tested? [x] Build/Boot tested Bookworm CLI/Minimal on Current(v6.1) and Edge(v6.3) kernels [x] Build/Boot tested Jammy CLI/Minimal on Current(v6.1) and Edge(v6.3) kernels [x] Dual Gbit Ethernet works [x] Dual-band Wi-Fi works [x] USB 3.1 Gen 1 works [x] OSPI and SD card works 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 As per tittle. 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] My changes generate no new warnings View the full article

Event Dispatcher, part of the upcoming WirePlumber 0.5 configuration system refactoring, is a custom PipeWire event scheduling mechanism designed to address many of the fundamental issues in WirePlumber. View the full article