RSS Bot

Description Lets ship currently latest with and install it when we build distros that needs it. Installs latest deboostrap scripts to the host if we choose to build something that is not supported by default. Jira reference number AR-2090 How Has This Been Tested? [x] Manually running it 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

Description The idea is to generate output/git_sources.json file that will contain url, branch and commit hash combo. The easiest way to generate file for all devices is to run ./compile.sh targets. Then at the time of release we will copy the output/info/git_sources.json file to config/sources/git_sources.json. Once the file is copied, the hash information from the file will be used to fetch resources for git repositories where branches are specified instead of tags or commits. There can be other ways to do this as well. I am just too tired to experiment more on the same. Raising it to be a communication starter. Jira reference number AR-2087 Based on: https://github.com/armbian/build/pull/6272 How Has This Been Tested? [ ] Tested output/git_sources.json file generation using ./compile.sh targets command [ ] Copied generated file to config/sources and modified it to use a different commit hash for 6.6 kernel. Then tested that kernel is being built from that hash instead of the latest available 6.6 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

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. [x] Test A [x] Test B 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

Picks up from where we left off; https://github.com/armbian/build/pull/6296 Stable wireless depends on the following PR; https://github.com/armbian/build/pull/6314 Notables: Updated U-Boot to v2024.01 U-Boot SPL 2024.01-armbian (Feb 29 2024 - 04:57:24 -0500) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.10.2(debug):armbian NOTICE: BL31: Built : 04:56:45, Feb 29 2024 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a09ca98, model: BananaPi M4 Zero INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2024.01-armbian (Feb 29 2024 - 04:57:24 -0500) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: BananaPi M4 Zero DRAM: 2 GiB Core: 52 devices, 21 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. starting USB... Bus usb@5311400: USB OHCI 1.0 scanning bus usb@5311400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3259 bytes read in 3 ms (1 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 205 bytes read in 2 ms (99.6 KiB/s) 31833 bytes read in 11 ms (2.8 MiB/s) Working FDT set to 4fa00000 4203 bytes read in 7 ms (585.9 KiB/s) Applying kernel provided DT fixup script (sun50i-h616-fixup.scr) ## Executing script at 45000000 18347702 bytes read in 2961 ms (5.9 MiB/s) 23365640 bytes read in 3770 ms (5.9 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=418d0000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 18347638 Bytes = 17.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 48e80000, end 49fff676 ... OK Loading Device Tree to 0000000048e0f000, end 0000000048e7ffff ... OK Working FDT set to 48e0f000 Starting 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 [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Backported 6.7.y to 6.1.y. Included fixups for 6.1, 6.6, 6.7 and added 6.8. 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

The merge request has landed, the non-conformant implementation warnings are gone, and NVK's Meson configuration now reads "nouveau" instead of "nouveau-experimental". It's now time to start shipping NVK to users! View the full article

Description Some network related dependency were missing as DNS within docker container was not working. While dealing with config, several other options were enabled, which should be harmless. Jira reference number AR-2086 How Has This Been Tested? [x] Generated Debian Bookworm with HA extension which loads automatically 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

armbian-resize-filesystem wants to align partitions on 16 MB boundaries, however due to an off-by-one error it would make the last sector of the partition start at a 16 MB boundary instead of ending at a 16 MB boundary. View the full article

Description This PR makes Khadas Edge 2 usable on mainline and update USB patches on rk3588 edge. What is not working: MCU fan control. The driver is exists on upstream kernel but VIM3 has different fan control register and logic, needs new implementation. Type-C port Wlan and Bluetooth Jira reference number AR-2082 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

With adversity comes the need to rise to the challenge. As the tech climate continues to shift, our talented new joiners have readily jumped in to advance the open source mission. View the full article

Description JetHome: fix u-boot patches for rescue button. Applies only to JetHub devices Jira reference number AR-2081 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] Fixed JetHub D1/D1+ [ ] Test B Checklist: [X] 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 support for "i.MX8M Plus" boards from TQ-System. Use atf and uboot from https://github.com/tq-systems Add BSP packages for the tqma8mpxl family Add kernel patches (6.1 and 6.6) for the tqma8mpxl family Supported mainline kernels: current = 6.1.71 and edge=6.6.10 Supported boards: mba8mp-ras314 mba8mpxl How Has This Been Tested? [x] Build images for mba8mp-ras314 and mba8mpxl with current and edge kernel [x] Boot test "bookworm_current" and "bookworm_edge" mba8mp-ras314 [x] Boot test "jammy_current" and "bookworm_edge" mba8mpxl [x] HDMI, WLAN, USB test's mba8mp-ras314" bookworm_edge" with xfce image [x] HDMI, WLAN, USB test's mba8mpxl" bookworm_edge" with xfce 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 [ ] 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 AmLogic soc patches for read chip_id and soc information from Secure Monitor call to soc-driver. Enabled by default only for JetHub devices (other needs to be enabled via general-socinfo-sm-4-arm64-dts-meson-add-dts-links-to-secure-monitor-for-.patch.disabled patch) https://lore.kernel.org/linux-arm-kernel/202402221557.ELxBYVKH-lkp@intel.com/T/ Jira reference number AR-2073 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. [ ] JetHub works [ ] some other closed-source devices based on axg/gxl/a1 soc works too. Checklist: [X] 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

As of 2024 Feb, Github still no allow a source branch to be renamed. Previous PR https://github.com/armbian/build/pull/6291 was auto closed by Github upon source branch renaming. This new PR supersedes it. Description Running "uefi-x86" board image on qemu-system-x86_64 --display none --serial stdio ... did not: allow GRUB boot without GUI display display early kernel boot messages on the serial console display the console prompt on serial console Jira reference number: None 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: Boot uefi-x86 board image on qemu-system-x86_64 --display none --serial stdio ... [x] Test A: Boot uefi-arm64 board image on qemu-system-aarch64 --display none --serial stdio ... [ ] Test B: Boot uefi-x86 board image on qemu-system-x86_64 --display vga ... 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 Bump BigTreeTech CB1 kernel to 6.1.79 from 6.1.43 as discussed in AR-2075. 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 that patches apply and kernel builds fine. I don't have device to actually test the working for 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 Add aya odin2 config,Most functions can be used now, but the amplifier driver is missing, so the speaker cannot be used. The headphone jack can barely be used, but there are quality issues with the sound. Currently, only Bluetooth is used to connect the speaker or headphones to play music During installation, the latest Mesa will be compiled to ensure that the GPU driver can be used properly, as Mesa lacks Open GL support and can only use Zink to provide hardware acceleration for the desktop. However, this can lead to some issues 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] WiFi & BT [x] GPU [x] PD Charger [x] Touch Screen [x] Joystick [x] Power/Vol UP/Vol Down Button 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 Any mounted directory should not be copied but also mounted on the new boot device when booting. Jira reference number AR-2043 Closing https://github.com/armbian/build/issues/6242 How Has This Been Tested? Need testing ! [ ] Fresh install to eMMC media [ ] Install to eMMC with configured zfs device 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 [ ] 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-2079 How Has This Been Tested? [x] Generated KDE desktop image for Odroid M1. Firstrun goes without password and after reboot (system must be up 1m) login is not automatic anymore. 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

Description Update odroidxu4-current kernel to 6.1.76. How Has This Been Tested? not yet, just committing current work. 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 Add config and device-trees for rock3c Only for AP6256 versions,not for AIC8800 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. [ ] Can boot [ ] most of the devices on board works well including pcie usb3 Gbit Eth 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 New blobs has been pushed to rk bin repository. https://github.com/armbian/rkbin/pull/25 Probably support for new memory chips. Jira reference number AR-2077 How Has This Been Tested? [x] Boot on Orange Pi 5 v1.2 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 We probably don't want to bother people with upstream release upgrades as they are outside our power. How Has This Been Tested? Not tested yet. Configuration change. 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description bump le potato to u-boot 2024.01 How Has This Been Tested? builds and boots 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

DMESG; https://paste.debian.net/1308388/ Wifi / Bluetooth patrick@bananapim4zero:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 3: wlx9803cf623b3f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 98:03:cf:62:3b:3f brd ff:ff:ff:ff:ff:ff inet 10.0.0.172/24 brd 10.0.0.255 scope global dynamic noprefixroute wlx9803cf623b3f valid_lft 172331sec preferred_lft 172331sec inet6 2601:586:4d00:3580::9b29/128 scope global dynamic noprefixroute valid_lft 345134sec preferred_lft 345134sec inet6 2601:586:4d00:3580:26d0:ba9c:10af:4de9/64 scope global dynamic noprefixroute valid_lft 345601sec preferred_lft 345601sec inet6 fe80::2cd1:8a57:ec6f:1336/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether f6:b7:9a:22:59:54 brd ff:ff:ff:ff:ff:ff patrick@bananapim4zero:~$ bluetoothctl Agent registered [CHG] Controller 98:03:CF:62:3B:40 Pairable: yes [bluetooth]# show Controller 98:03:CF:62:3B:40 (public) Name: bananapim4zero Alias: bananapim4zero Class: 0x00000000 Powered: yes Discoverable: no DiscoverableTimeout: 0x000000b4 Pairable: yes UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0542 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x05 (5) SupportedIncludes: appearance SupportedIncludes: local-name Connected to PC with g_ether enabled; [2788714.157345] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [2788714.157348] usb 6-1: Product: RNDIS/Ethernet Gadget [2788714.157351] usb 6-1: Manufacturer: Armbian Linux 6.6.18-current-sunxi64 with musb-hdrc [2788714.158370] cdc_subset 6-1:1.0 usb0: register 'cdc_subset' at usb-0000:00:1d.7-1, Linux Device, 32:5f:82:14:13:48 [2788714.186937] usbcore: registered new interface driver cdc_eem lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 29.7G 0 disk └─mmcblk0p1 179:1 0 29.4G 0 part /var/log.hdd / mmcblk1 179:32 0 7.3G 0 disk ├─mmcblk1p1 179:33 0 508M 0 part └─mmcblk1p2 179:34 0 6.8G 0 part mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk zram0 251:0 0 961.7M 0 disk [SWAP] zram1 251:1 0 50M 0 disk /var/log zram2 251:2 0 0B 0 disk I haven't tested to make sure eMMC boot works yet with Armbian, but it does on my personal builds, with the same patches in place. NOTE: WIFI and BT can sometimes be sketchy. Currently the Armbian img is using RTW88. There is the morrownr option, which runs stable, but I also find to not be 100%. 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 Fixing compilation due to broken patch. @paolosabatino This reverts commit 7c062f7daeca83e19b050b8e7ac6bf6aa6635693. How Has This Been Tested? Need testing. Assume upstream is tacking the same things? 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