Werner

just tested with a clean image, featuring 6.18.y and works just fine. This may be an issue if your setup is quite old, because at some point upstream changes caused Armbian kernel to break IIRC and this was worked around. The warning is persistent but doesn't actually matter. Please verify that a clean system boots normally.

hard to tell without any logs whatsoever

[ 5.092655] CPU1: failed to come online [ 5.092666] CPU1: failed in unknown state : 0x0 [ 10.217311] CPU2: failed to come online [ 10.217324] CPU2: failed in unknown state : 0x0 [ 15.341948] CPU3: failed to come online [ 15.341961] CPU3: failed in unknown state : 0x0 Yes we're aware of this, since it affects all H5 and H6 devices. We have a few ideas about what could be the cause like added logging (yes, sounds odd but..oh well) or certain ATF version. https://github.com/armbian/build/issues/9555

moved to off-topic since not directly related to armbian.

seems like openwrt already figured this and the fix is actually upstream: https://github.com/torvalds/linux/commit/c3fe7071e196e25789ecf90dbc9e8491a98884d7 (also see https://github.com/immortalwrt/immortalwrt/commit/7ef19bb9cd59f5018fc96b01a5465ed84038cfe8) This may tell that one or more Armbian patches make things worse , no clue though which one if any.

moved

Another attempt, again check https://testing.armbian.de/r4s/?C=M&O=D for most recent debs. This time adding an artificial bus scan delay into the r4s dts. Another poke in the dark but perhaps...

See inline comments. Dirty SPI may cause this but without logs from serial console this is just a guess

Hm. Well. Im out of ideas. Perhaps openwrt will find something when they're going to work on 6.18. Unmarked the old solution for now since it no longer applies.

https://testing.armbian.de/r4s/?C=M&O=D Check for the more recent files. This has a different attempt to fix it by reverting some stuff to be more like 6.12

While waiting for new info, first poke in the dark. rk3399-fix-pci-phy.patch disabled https://testing.armbian.de/r4s/ feel free to test

Perhaps a hardware defect? At least that would be my guess from what it sounds.

Please provide logs. armbianmonitor -u Otherwise its just poking around in the dark

elaborate. If there is only garbage output your usb uart adapter may not be able to handle this speed. Example would be CP2102 which outputs garbage instead of gracefully failing when "overclocked".

My n2 works fine btw. https://paste.armbian.com/cocivagayi

FT232R, CH340 or CP2104 are known to work nicely. Search for any usb uart adapter built around one of these. Don't get CP2102 because if you ever get a rockchip board it would be useless.

UART logs via serial console

logs?

No. edge will give you 7.0-rc3 since it was bumped recently. You can try to revert this commit to get 6.19. No guarantee it works, nor any support will be given. https://github.com/armbian/build/pull/9445

Yes, they seem to be missing in repo. As a quick fix I'd suggest to use the build framework to create yourself a set of deb files containing all necessary packages code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh BOARD=orangepi5 BRANCH=current kernel code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } copy the packages from output/debs to your board and use dpkg to install them.

Depends on the image you are using. The image for 3 LTS should work for the 3 LTS. The image for the 3 (without lts) will not.

Without uart hard to tell.

Well since you asked in this sub-forum, feel free to start:

Well the only thing armbian-config does, is calling "armbian-install" which has been there for ages

correct