rob

Test version 20230421-EDK2-EFI with support for system startup control on a monitor screen with a keyboard Nice! currently SD centric.. so one needs to watch what's on other devices, and do normal tricks to return to booting from nvme otherwise the expected: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, KASLR will be disabled EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... PartitionDriverBindingStop: FlushBlocksEx returned with Success PartitionDriverBindingStop: FlushBlocksEx returned with Success EFI stub: ERROR: Exit boot services failed. EFI stub: ERROR: Failed to update FDT and exit boot services ConvertPages: Incompatible memory types, the pages to free have been freed Application failed, r = 1

I was confused until realizing U-Boot 2017.09-armbian (Mar 17 2023 - 15:51:29 +0300) only recognized BOT flash drives as all mine support UASP starting USB... Bus usb@fc800000: USB EHCI 1.00 Bus usb@fc840000: USB OHCI 1.0 Bus usb@fc880000: USB EHCI 1.00 Bus usb@fc8c0000: USB OHCI 1.0 Bus usb@fcd00000: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fc800000 for devices... 4 USB Device(s) found scanning bus usb@fc840000 for devices... 1 USB Device(s) found scanning bus usb@fc880000 for devices... 1 USB Device(s) found scanning bus usb@fc8c0000 for devices... 1 USB Device(s) found scanning bus usb@fcd00000 for devices... 1 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Device 0: Vendor: SanDisk Rev: 0001 Prod: Extreme Type: Hard Disk Capacity: 14966.6 MB = 14.6 GB (30651688 x 512) ... is now current device Scanning usb 0:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf =================begin=================== 313 bytes read in 188 ms (1000 Bytes/s) 1: Armbian Retrieving file: /boot/uInitrd =================begin=================== 20929541 bytes read in 1709 ms (11.7 MiB/s) Retrieving file: /boot/Image =================begin=================== 33747456 bytes read in 2420 ms (13.3 MiB/s) Perhaps plug drives into the black ports, not the blue ones.

Спасибо за помощь. glmark2 2021.02 ======================================================= OpenGL Information GL_VENDOR: Mesa GL_RENDERER: Mali-G610 (Panfrost) GL_VERSION: OpenGL ES 3.1 Mesa 23.0.0-devel (git-cbe80448cc) ======================================================= glmark2 Score: 760

uBoot on USB? I can petitboot a mini root from usb, but don't know how to load Armbian without a µSD or eMMC stub.

Thanks for the detailed walkthrough. Solved issues with QEMU and editing meson-g12b.conf so far no stack traces dumped with 5.8.7.1_35809.20191129_COEX20191120-7777 88x2bu which is the root goal. normally had them every hr so that's a good sign.

First thanks for the excellent build environment. I'm building BRANCH=current RELEASE=focal BOARD=odroidn2 which makes dpkg-deb: building package 'linux-source-5.10.45-current-meson64' in '/tmp/tmp.8RgxL6czti/linux-source-current-meson64_21.08.0-trunk_all.deb'. but I'm trying to share .ko with the nightly CI image https://armbian.tnahosting.net/dl/odroidn2/archive/Armbian_21.05.4_Odroidn2_focal_current_5.10.43.img.xz because I'm still working out binfmt_misc issues in my hirsute LXC env. update-binfmts: warning: unable to open /proc/sys/fs/binfmt_misc/status for writing: Permission denied update-binfmts: warning: qemu-arm not in database of installed binary formats. [ o.k. ] Adding Armbian repository and authentication key [ /etc/apt/sources.list.d/armbian.list ] chroot: failed to run command ‘/bin/bash’: Exec format error mount: /root/build/.tmp/rootfs-30acf184-73cd-46c1-864e-6b43fbd38071/proc: WARNING: source write-protected, mounted read-only. mount: /root/build/.tmp/rootfs-30acf184-73cd-46c1-864e-6b43fbd38071/sys: WARNING: source write-protected, mounted read-only. mount: /root/build/.tmp/rootfs-30acf184-73cd-46c1-864e-6b43fbd38071/dev: WARNING: source write-protected, mounted read-only. mount: /root/build/.tmp/rootfs-30acf184-73cd-46c1-864e-6b43fbd38071/dev/pts: WARNING: source write-protected, mounted read-only. [ o.k. ] Applying distribution specific tweaks for [ focal ] chroot: failed to run command ‘/bin/bash’: Exec format error chroot: failed to run command ‘/bin/bash’: Exec format error chroot: failed to run command ‘/bin/bash’: Exec format error [ o.k. ] Applying common tweaks chroot: failed to run command ‘/bin/bash’: Exec format error chroot: failed to run command ‘/bin/bash’: Exec format error chroot: failed to run command ‘/bin/bash’: Exec format error [ .... ] Updating [ package lists ] [ .... ] Temporarily disabling [ initramfs-tools hook for kernel ] [ .... ] Installing [ linux-u-boot-odroidn2-current_21.08.0-trunk_arm64.deb ] [ error ] ERROR in function install_deb_chroot [ image-helpers.sh:150 ] [ error ] Installation of /root/linux-u-boot-odroidn2-current_21.08.0-trunk_arm64.deb failed [ odroidn2 focal no meson64 ] I don't understand how to build v5.10.43 rather than v5.10.45 so I slide in my newly built 88x2bu.ko

Armbian CI is building v5.10.43 while my local build is making v5.10.45. How can I switch? I've tried all sorts of iterations of KERNELRELEASE= BRANCH= and LIB_TAG= in userpatches/config-example.conf but can't find the right combination to build a v5.10.43 kernel with RELEASE=focal What's the correct build env var and value needed to match Armbian's CI?

Bump. Did you find an overlay for ttyAML1 for your Odroid C2? I need to write one for the N2.

eth0 get link on the N2 with 5.6.18-meson64 (root@builder) but after switching to nightly 5.7.9-meson64 (root@stable) link errors with [ 76.174115] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet] (irq=25) [ 76.278174] meson8b-dwmac ff3f0000.ethernet: Failed to reset the dma [ 76.278892] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed [ 76.287895] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Hw setup failed I've tracked this to a needed delay in the overlay, a patch is available here: https://forum.khadas.com/t/vim2-ethernet-problem-with-mainline-kernel/5817/7 https://patchwork.kernel.org/patch/10997079/ Thanks for an outstanding build! If there is a bug tracker someplace this should be logged, please point me in that direction.