Gunjan Gupta

uInitrd file is built automatically on the board when a installing a new kernel. Installing a new kernel triggers generation of initramfs using update-initramfs command. After initramfs is created, the update-initramfs triggers /etc/initramfs/post-update.d/99-uboot script to generate uInitrd file. I believe you only choose to change kernel and haven't updated anything. Latest available edge kernel would have been something like 6.4.12 or something. What was the output of "apt update" and "apt upgrade" Hard to understand what was going on without seeing the output Upgrades are generally not tested because of resource crunch. But theoretically that is what is supposed to be done for performing an upgrade. I guess this is because of your armbian config has gone missing. Again you haven't shared any of the outputs from the operations you have performed. So can't really say why that file went missing in the first place

Wifi for current and edge kernel is fixed and updated kernel is available from beta repository and in nightly builds. It will be pushed to stable later may be in few days or once 23.11 is released

Thanks for reporting this. Made me realize why I was not able to boot any 5.15 kernel on my custom build images. I have added few fixes for 6.1 and 6.5 kernel. Feel free to upgrade to them from beta repository i.e. beta.armbian.com. Stable repository is lacking fixes for wifi though which are currently included only in kernel from beta repository

Its hard to help with just it wouldn't boot statement. What was the output from serial console. Or was there any output on the serial console?

There are two ways you can go. Either add a patch and build a new image. Or use official image with a device tree overlay to change that line. If you want to go the first route, run the following command ./compile.sh BOARD=orangepizero BRANCH=current uboot-patch It will start the patch mode and then wait for you to make changes. if you are building with docker, you have to open a shell using "docker exec -it <instance_id> /bin/bash". Go to cache/sources/u-boot-sunxi/<version>/ directory and make your changes. Go back to window where you ran ./compile.sh and press enter. It will ask you for few things once you provide those a patch file will be created in output directory. Then you can copy that patch file to patch/u-boot/u-boot-sunxi directory so that the patch applies to the image you have to do the same thing for kernel as well. Most of the workflow will remain the same just command will be kernel-patch instead of uboot-patch and source directory will also be something like cache/sources/linux-something. The patch has to be placed in patch/kernel/archive/sunxi-<kernel_version>/ directory or its corresponding userpatches directory. If you go to device tree overlay route, create a file called sun8i-h3-reg_vcc_wifi.dts with the following content /dts-v1/; /plugin/; &reg_vcc_wifi { gpio = <&pio 0 2 GPIO_ACTIVE_HIGH>; }; compile it with "dtc -@ -I dts -O dtb -o sun8i-h3-reg_vcc_wifi.dtb sun8i-h3-reg_vcc_wifi.dts". copy dtb file to /boot/dtb/overlays directory and enable it using armbian-config. It will take affect after reboot

Could you please share the logs? Pull your ethernet out while wifi is working. Once the wifi stops working, plug the ethernet back in and run armbianmonitor -u to upload the logs. Then share the URL here. I have already created a PR to fix the wifi, it should get pulled in a few days. Then probably you can get the kernel from beta.armbian.com repository. But still I will try this out tomorrow on the newer kernel to see to make sure it doesn't have similar issue.

Yeah, I think that should work fine. Why, are you facing any issues when doing the same?

Hi, I am working on enabling crust support in Armbian. A draft version of pull request is here. I have made the changes for the same. With my changes, crust compiles as part of building the image and gets bundled in u-boot. I can also see the following message from U-boot U-Boot 2022.10-armbian (Jun 14 2023 - 13:49:59 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi NEO DRAM: 512 MiB Core: 61 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Starting SCP... Net: SCP/INF: Crust v0.5.10000 eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop and the following message is present in dmesg output [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: MIGRATE_INFO_TYPE not supported. [ 0.000000] psci: SMC Calling Convention v1.0 So I know that crust is getting loaded. I am not sure how I can test if its working as its supposed to be. I can use some guidance for the same. Thanks in advanced