RSS Bot

Description Allow to disable boot partition by explicit BOOTSIZE=0. This would help when bootloader known to support rootfs FS. Allow image_size < rootfs_size for (potentially compressed) btrfs. 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 compressed btrfs-rootfs image with FIXED_IMAGE_SIZE=$((rootfs_size/2)) and without boot 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 There is an orbiting patch that adds True Random Number Generator (TRNG) completing the rockchip mainline crypto driver. This PR introduces the patch (which is in RFC condition, thus passible of changes) with these benefits: provides better entropy (see below) removes the memory region claim error in dmesg is almost in mainline Some caveats: the existing driver covers rk3288 (32 bit, not applicable in this context), rk3328 and rk3399, but only rk3399 seems to have working hardware. For the other two chips, the TRNG is just disabled. How Has This Been Tested? [x] Current 6.6 kernel packages built and installed on live system (rk3399) [x] Edge 6.7 kernel packages built and installed on live system (rk3399) dmesg can be used to verify if TRNG is enabled: [ 8.091984] rk3288-crypto ff8b0000.crypto: will run requests pump with realtime priority [ 8.092031] rk3288-crypto ff8b0000.crypto: Register ecb(aes) as ecb-aes-rk [ 8.092077] rk3288-crypto ff8b0000.crypto: Register cbc(aes) as cbc-aes-rk [ 8.092087] rk3288-crypto ff8b0000.crypto: Register ecb(des) as ecb-des-rk [ 8.092098] rk3288-crypto ff8b0000.crypto: Register cbc(des) as cbc-des-rk [ 8.092107] rk3288-crypto ff8b0000.crypto: Register ecb(des3_ede) as ecb-des3-ede-rk [ 8.092116] rk3288-crypto ff8b0000.crypto: Register cbc(des3_ede) as cbc-des3-ede-rk [ 8.092126] rk3288-crypto ff8b0000.crypto: Register sha1 as rk-sha1 [ 8.092137] rk3288-crypto ff8b0000.crypto: Register sha256 as rk-sha256 [ 8.092146] rk3288-crypto ff8b0000.crypto: Register md5 as rk-md5 [ 8.092156] rk3288-crypto ff8b0000.crypto: Register TRNG with sample=1200 The mail in the kernel mailing list provides some insight and instruction on how to prove effectiveness of the RNG. Testing existing driver provided by vendor kernel looks quite ineffective in providing decent randomness: root@orangepi4-lts:~# cat /sys/devices/virtual/misc/hw_random/rng_current rockchip root@orangepi4-lts:~# dd if=/dev/hwrng count=100 bs=2048 | rngtest rngtest 2.2 Copyright (c) 2004 by Henrique de Moraes Holschuh This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. rngtest: starting FIPS tests... rngtest: entropy source exhausted! rngtest: bits received from input: 1638400 100+0 records in 100+0 records out rngtest: FIPS 140-2 successes: 0 rngtest: FIPS 140-2 failures: 81 rngtest: FIPS 140-2(2001-10-10) Monobit: 3 rngtest: FIPS 140-2(2001-10-10) Poker: 81 rngtest: FIPS 140-2(2001-10-10) Runs: 81 rngtest: FIPS 140-2(2001-10-10) Long run: 0 rngtest: FIPS 140-2(2001-10-10) Continuous run: 0 rngtest: input channel speed: (min=528.429; avg=1086.773; max=1379.618)Kibits/s rngtest: FIPS tests speed: (min=14.341; avg=47.788; max=59.051)Mibits/s 204800 bytes (205 kB, 200 KiB) copied, 1.52111 s, 135 kB/srngtest: Program run time: 1522960 microseconds While the mainline patch adjusts the number of samples and, albeit being slower and not high quality, seems to be better: root@orangepi4-lts:~# dd if=/dev/hwrng count=100 bs=2048 | rngtest rngtest 2.2 Copyright (c) 2004 by Henrique de Moraes Holschuh This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. rngtest: starting FIPS tests... rngtest: entropy source exhausted! rngtest: bits received from input: 1638400 100+0 records in 100+0 records out rngtest: FIPS 140-2 successes: 28 rngtest: FIPS 140-2 failures: 53 rngtest: FIPS 140-2(2001-10-10) Monobit: 52 rngtest: FIPS 140-2(2001-10-10) Poker: 13 rngtest: FIPS 140-2(2001-10-10) Runs: 3 rngtest: FIPS 140-2(2001-10-10) Long run: 0 rngtest: FIPS 140-2(2001-10-10) Continuous run: 0 204800 bytes (205 kB, 200 KiB) copied, 7.31521 s, 28.0 kB/s rngtest: input channel speed: (min=131.364; avg=222.220; max=278.743)Kibits/s rngtest: FIPS tests speed: (min=17.628; avg=30.777; max=76.600)Mibits/s rngtest: Program run time: 7316184 microseconds Since the original driver from vendor kernel looks like quite useless, I would like to remove this and this soon from the patch archives, and perhaps adapt the mainline driver to provide RNG for rk3308 too, although it is probably useless since the hardware seems to be ineffective on rk3328 (see patch comments) and probably rk3308 is in the same league. @brentr what do you think about? 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

khadas-vim3: bump to u-boot v2024.01; boot-usb-first patch in board folder khadas-vim3: bump to u-boot v2024.01; boot-usb-first patch in board folder patch is slightly different for 2024.01 View the full article

wsl2: vhd/vhdx exts; more wsl2 kernel stuff linux-wsl2-x86-edge.config: enable moar Hyper-V stuff & console as builtin extensions: image-output-vhd renamed to image-output-vhd-azure only Azure wants the static, 1024-aligned original VHD images (and doesnt support VHDX?) new VHDX output format (for generic Hyper-V on Windows 10/11/2019/etc) extensions: image-output-vhdx: add output for dynamic .vhdx (in a zip file, to avoid sparseness errors) new VHDX output format (for generic Hyper-V on Windows 10/11/2019/etc) it is always stored (no compression) in a .zip file, to avoid sparseness errors when building, transfer the .zip file over to Windows, and uncompress it there (not on WSL2 itself/Linux/other machine) wsl2: enable image-output-vhdx for all wsl2 images (this enables wsl2 images to be run directly on Hyper-V) future work: export the rootfs .tar.gz, that can be used on WSL2 as a Custom Distro View the full article

bcm2711: switch to 48-bit virtual address; enable "docker optimizations" bcm2711-edge: switch to 48-bit virtual address; enable eBPF stuff & BTF for tcmalloc (enjoy, cilium, etc) stuff https://github.com/cilium/cilium/issues/23640 see https://github.com/libbpf/libbpf#bpf-co-re-compile-once--run-everywhere bcm2711-current: switch to 48-bit virtual address; enable eBPF stuff & BTF for tcmalloc (enjoy, cilium, etc) stuff https://github.com/cilium/cilium/issues/23640 see https://github.com/libbpf/libbpf#bpf-co-re-compile-once--run-everywhere bcm2711: cmdline.txt: enable "docker optimizations" most u-boot based boards get cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 by default (so work with docker/containerd/k8s/etc) View the full article

meson64: 6.7 edge: real bump to 6.7 meson64: 6.6 current: added -spidev DT's for a few boards & cleanup 0000.patching_config.yaml gives access to SPI Flash in exchange for slower eMMC cleanup 0000.patching_config.yaml for meson64-6.6 meson64: 6.7 edge: copy patches from 6.6 meson64: 6.7 edge: rebase patches to 6.7 general-rc-drivers-should-produce-alternate-pulse-and-space-timing-events.patch: dropped added -spidev DT's for a few boards (gives access to SPI Flash in exchange for slower eMMC) cleanup 0000.patching_config.yaml for meson64-6.7 meson64: 6.7 edge: fix SPI-NOR patch for 6.7.y general-spi-nor-add-support-for-XT25F128B.patch: fixed same as Paolo did for rockchip64-6.7 View the full article

Description Forgot to shift kernel configs for rockchip family when switching current to 6.6 and edge 6.7; done right now. Curiously I noticed this after hitting "buggy" behaviour on rk322x board with several rcu_scheduler debug messages while board was under high load, vnstatd process was often at 100% cpu usage and reading /proc/net/dev file (which is a simple text file with some network interface stats) stalls vnstatd. Turning off eth0 interface solved the problem but of course it was not solution. I shifted the kernel config, recompiled kernel 6.6 and this apparently solved the problem (maybe thanks to CONFIG_NEED_SRCU_NMI_SAFE=y ?) If it is so, the consideration I make here is that using that using a kernel config that does not match the kernel version may, in some corner cases, be harmful for stability How Has This Been Tested? [x] Kernel deb packages compiled and tested on live rk322x system 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

See the discussion in https://forum.armbian.com/topic/30074-helios64-armbian-2308-bookworm-issues-solved/page/3/#comment-179040 Description The Helios64-specific changes get moved to rockchip64, as https://github.com/armbian/build/blob/main/config/boards/helios64.csc#L3 says that it's not rk3399 anymore. How Has This Been Tested? See discussion in https://forum.armbian.com/topic/30074-helios64-armbian-2308-bookworm-issues-solved 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 Ubuntu variants were somehow forgotten when adding systemd-resolved in https://github.com/armbian/build/pull/6142 Jira reference number AR-1657 How Has This Been Tested? [x] Generating Ubuntu Jammy 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 As per subject: bump rockchip64 current kernel to 6.6 and edge kernel to 6.7 Jira reference number AR-2017 How Has This Been Tested? [ ] Compile kernel deb packages for 6.6 [ ] Compile kernel deb packages for 6.7 [ ] Build image and test with kernel 6.7 for rk3328 board [ ] Build image and test with kernel 6.7 for rk3399 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 [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 Add new borad of ASUS Tinker-Edge-R. ASUS Tinker Edge R is an Single Board Computer (SBC) specially designed for AI applications. I've written the device tree file for it, added the u-boot config file, and I've done the current version adaptation. Jira reference number [AR-9999] How Has This Been Tested? [x] UART test. The serial port output is printed through UART, and there are almost no errors in the armbian boot log. [x] Stability testing. Let the CPU run the specified task all the time, and the test will be conducted for 48 hours without any error. 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description rtl8723cs driver need some little changes to compile on kernel 6.7; it was breaking rockchip and allwinner families This pull request contains those changes. Jira reference number AR-2025 How Has This Been Tested? [x] Patch applies correclty on kernel 6.7 [x] Kernel deb packages correctly built 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

Collabora's kernel team made a number of key contributions including a new kselftest for verifying driver probe of Devicetree-based platforms, multiple improvements to further improve support for MediaTek SoCs found in Chromebooks, and more. View the full article

Description Bump all mainline based kernels. How Has This Been Tested? [ ] Build test within CI Checklist: [x] My code follows the style guidelines of this project [ ] My changes generate no new warnings View the full article

Create a overlay_prefix to h616 for orangepizero3. Description There are no overlays nor fixup scripts for h618. Since the orangepizero3 is i/o hardware identical to the orangepizero2, it makes sense to just point the zero3 to the zero2 overlays. Jira reference number [AR-9999] How Has This Been Tested? An image for orangepizero3 with this change was generated. It ran the fixup script on boot. Armbian-config -> System-> Hardware was used to enable an spidev. On reboot the overlay was loaded. 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

This does not change the current boot order and requires additional hardware. Hardware used in my testing: BananaPi BPI-CM4IO Baseboard with BPI-CM4 Module Mini PCI-E PCI Express to SATA 3.0 Dual Ports Adapter Converter Hard Drive Extension Card https://a.co/d/0G679qW Kingston 120GB A400 SATA 3 2.5" Internal SSD https://a.co/d/fB2qf3r External power supply for Hard Drive 2.5" 3.5" https://www.ebay.com/itm/114620135743 bananapi: ~ $ lspci 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01) 01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) bananapi: ~ $ sudo blkid /dev/mmcblk1p1: LABEL="EMMC" UUID="67ea5c62-c9cb-498e-91ff-3e60d71bd1ab" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="0a8751c2-01" /dev/sda2: LABEL="ROOTFS" UUID="39d23eae-ba3a-4b28-acba-8f45ff8eed1c" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="e6053ca6-02" /dev/sda1: LABEL="BOOT" UUID="d540a625-98a8-4c73-a5a3-7a905d5bbb98" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e6053ca6-01" /dev/zram0: UUID="ee6d34f4-fda2-4207-8dc9-b8a4b83cd759" TYPE="swap" bananapi: ~ $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 111.8G 0 disk ├─sda1 8:1 0 508M 0 part /boot └─sda2 8:2 0 111.3G 0 part / mmcblk1 179:0 0 14.6G 0 disk └─mmcblk1p1 179:1 0 14.6G 0 part mmcblk1boot0 179:32 0 4M 1 disk mmcblk1boot1 179:64 0 4M 1 disk zram0 253:0 0 1G 0 disk [SWAP] 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 Migrate the Banana Pi R2 Pro from the media family to the rockchip64 family. Also migrate to upstream u-boot which added support for this board in its latest release. How Has This Been Tested? Compiled a desktop image, wrote it on an sdcard, booted and tested everything is functional on the bpi-r2-pro. ./compile.sh BOARD=bananapir2pro BRANCH=edge RELEASE=trixie BUILD_MINIMAL=no BUILD_DESKTOP=yes DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base DESKTOP_APPGROUPS_SELECTED=none KERNEL_CONFIGURE=no 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 @lujianhua has just pushed two commits enabling 120Hz panel: https://gitlab.com/sm8250-mainline/linux/-/tree/sm8250/v6.7?ref_type=heads This pr also rebased the xiaomi keyboard related patches to his branch, although keyboard is still not working. Enable CONFIG_HIDRAW because I find it is necessary for yuzu emulator to detect nintendo switch pro controller. 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.sh kernel BOARD=xiaomi-elish BRANCH=sm8250 DEB_COMPRESS=xz [x] Xiaomi elish boots with 120Hz. 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 Update symlink for bluetooth firmware on JetHub D1 Jira reference number AR-2022 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] JetHub D1 build and run ok 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 As per subject, move rockchip current to 6.6 and edge to 6.7. Some rework has to be done, in particular a LE patch has been fully merged (linux-0020) and can be remove and rockchip DFI driver has been heavily modified, so requires some patient work to be reinstated. Jira reference number AR-2016 How Has This Been Tested? [x] Compile rockchip 6.6 kernel [ ] Compile rockchip 6.7 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 In several situations we need to have systemd-resolved installed and configured or we loose DNS. This happens in case of HA and most likely OMV too. As per documentation: systemd-resolved will work out of the box with a network manager using /etc/resolv.conf. No particular configuration is required since systemd-resolved will be detected by following the /etc/resolv.conf symlink. This is going to be the case with systemd-networkd, NetworkManager, and iwd. move DNS server set from Ubuntu specifics change switch to if and check for DISTRIBUTION instead of RELEASE detach bullseye so we can keep it operational without systemd-resolved change bullseye to EOS Install systemd-resolved by default to all variants Jira reference number AR-1657 How Has This Been Tested? [x] Made few images 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 Rewrite patches since we have stable git hash length KERNELPATCHDIR is no longer $LINUXFAMILY-$BRANCH, so declare it in board config file Bump kernel to 6.7.y Add support for nintendo pro/joycon controller since this device can run yuzu emulator 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] ./compile.sh kernel BOARD=xiaomi-elish BRANCH=sm8250 DEB_COMPRESS=xz KERNEL_GIT=shallow [x] Xiaomi elish boots 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 duplicated existing SATA2 overlay for SATA1 used on Rock5b and probably others. I know in the legacy kernel the equivalent patch is board specific, but will stay generic for now.. plus I didn't see where to disable wifi or BT interrupts in current device tree. working with port multiplier root@rock-5b:~# uname -a Linux rock-5b 6.7.0-rc8-edge-rockchip-rk3588 #4 SMP PREEMPT Sun Dec 31 20:51:25 UTC 2023 aarch64 GNU/Linux root@rock-5b:~# dmesg|fgrep -i sata [ 0.890642] ahci-dwc fe220000.sata: supply ahci not found, using dummy regulator [ 0.891363] ahci-dwc fe220000.sata: supply phy not found, using dummy regulator [ 0.892281] platform fe220000.sata:sata-port@0: supply target not found, using dummy regulator [ 0.893198] ahci-dwc fe220000.sata: PMPn is limited up to 5 ports [ 0.893787] ahci-dwc fe220000.sata: forcing port_map 0x0 -> 0x1 [ 0.894308] ahci-dwc fe220000.sata: masking port_map 0x1 -> 0x1 [ 0.894848] ahci-dwc fe220000.sata: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode [ 0.895641] ahci-dwc fe220000.sata: flags: ncq sntf pm led clo only pmp fbs pio slum part ccc apst [ 0.897897] ata1: SATA max UDMA/133 mmio [mem 0xfe220000-0xfe220fff] port 0x100 irq 44 lpm-pol 0 [ 1.368703] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.376249] ahci-dwc fe220000.sata: FBS is enabled [ 1.693186] ahci-dwc fe220000.sata: FBS is disabled [ 1.851976] ahci-dwc fe220000.sata: FBS is enabled [ 1.853741] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 330) [ 2.167231] ahci-dwc fe220000.sata: FBS is disabled [ 2.325286] ahci-dwc fe220000.sata: FBS is enabled [ 2.326584] ata1.01: SATA link up 3.0 Gbps (SStatus 123 SControl 330) [ 2.643041] ahci-dwc fe220000.sata: FBS is disabled [ 2.801950] ahci-dwc fe220000.sata: FBS is enabled [ 2.803625] ata1.02: SATA link up 3.0 Gbps (SStatus 123 SControl 330) [ 3.119206] ahci-dwc fe220000.sata: FBS is disabled [ 3.275283] ahci-dwc fe220000.sata: FBS is enabled [ 3.276958] ata1.03: SATA link up 6.0 Gbps (SStatus 133 SControl 330) [ 3.593076] ahci-dwc fe220000.sata: FBS is disabled [ 3.751950] ahci-dwc fe220000.sata: FBS is enabled [ 3.753535] ata1.04: SATA link up 3.0 Gbps (SStatus 123 SControl 330) View the full article

Description made overlay to enable spi flash on rock5b based on https://github.com/Googulator/linux-rk3588-midstream/blob/adbadbf32e87b308688136aa55c03b1bed6f7e03/arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts#L704C1-L724C4 root@rock-5b:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk1 179:0 0 59.7G 0 disk ├─mmcblk1p1 179:1 0 256M 0 part /boot └─mmcblk1p2 179:2 0 58.8G 0 part /var/log.hdd / zram0 251:0 0 3.8G 0 disk [SWAP] zram1 251:1 0 50M 0 disk /var/log zram2 251:2 0 0B 0 disk nvme0n1 259:0 0 238.5G 0 disk └─nvme0n1p1 259:1 0 238.5G 0 part root@rock-5b:~# dmesg|fgrep -i spi [ 0.000000] GICv3: 480 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.891760] spi spi0.0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/regulators/dcdc-reg7 [ 0.892578] spi spi0.0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/dvs3-null-pins [ 0.893311] spi spi0.0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/dvs2-null-pins [ 0.894043] spi spi0.0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/dvs1-null-pins [ 0.896499] spi-nor spi1.0: mx25u12835f (16384 Kbytes) [ 1.761968] 1 fixed-partitions partitions found on MTD device spi1.0 [ 1.762534] Creating 1 MTD partitions on "spi1.0": View the full article

Description Digging and reworking this https://github.com/armbian/build/pull/6100 while (de)attaching to new LTS kernel. Jira reference number AR-2005 How Has This Been Tested? 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