Hi @Jose Ramirez I'm updating the aic8800 driver. Not sure if it will fix your issues. But it seems to be more stable. https://github.com/warpme/minimyth2/commit/bcb3cf537d5c6ebbd5144901cc556e0e28fbdca5 I'll also update the kernel headers using your x98h build. You can build the image yourself it's already updated or you'll have to wait. (if the build stops with an error about 'base-files'. Restart the build It will continue where you left off) git clone https://github.com/NickAlilovic/build.git --branch v20250306

Regressions happen all the time and not uncommon at all. Some get fixed upstream, some fix itself, some we have to find a fix. One of thousands of great ideas we'd love it implement but simply can't due to lack of (human) resources. This is why we highly appreciate community involvement.

I am not 100% certain but I think one of these images are installed (and upgraded) on my boards spi/nvme where I confirmed emmc working: http://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_noble_vendor_6.1.84_kde-neon-kisak_desktop.img.xz http://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_noble_vendor_6.1.99_kde-neon_desktop.img.xz

Hi, the manual way of enabling/disabling overlays is checking their availability in /boot/dtb/<family>/overlay and edit /boot/armbianEnv.txt. In your case it seems that a new overlays needs to be written. You can decompile an existing one that is similar using the code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } dtc utility. Once you created a new dts file you can use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-add-overlay <filename>.dts to compile and enable it. What exact values are necessary to achieve your particular case I don't know. I guess for that you have to dig through the datasheets of both your board and the SoC it is built around.

Answering to myself: Seems like the aic8800 driver is looking for the mac address in the eFuses and at least on my device is failing to do so, failing back to randomizing the last 2 bytes of the address. I’ll see if I can patch the driver to use a MAC address from the cmd line or use the .ini file (since that function of the driver was left out). And for the no WiFi after reboot error, seems like the driver is failing to restart the WiFi module.