jock

Yes, it is expected that is so: you must run rk322x-config, set led-conf7 and reboot (or setup led-conf7 manually in /boot/armbianEnv.txt)
 
Legacy kernel is discontinued, has some reason only for those who have old boards with NAND. You have no reason to stay with legacy kernel, it's old, insecure and unmaintained!

I already opened a pull request on armbian, when it will be accepted, new kernel will be built with fixes, but I have no control on when the new kernels will be built by the armbian servers.

Tryed the 6.1.55 install by the book and looks also working like 6.1.50 hand patched.
Attaching install and dmesg logs. RK3228B55.zip
 
Shall being good if some more user with desktop installed can testing it so Joke can getting it better verified that is working and putting it in the current release if all is OK.
 
PS: The kernel install is still complaining of missing firmware that it have doing longer time now but my RK3318 box is not doing it on all kernels i have running on it.

@MattWestB I've uploaded convenient deb packages with update dtbs for both kernel 6.1 and 6.5; now they should be finally fixed and work, at least I tested on my board and they work pretty fine.
 
You can download the deb package from here - for your installed system with kernel 6.1 you may want to download and install linux-dtb-current package
Please do a backup as you already did of the /boot/dtb directory on your existing installation!
 

@Benedito Portela Here it is a debian buster minimal image with latest 6.5 kernel. I did not had time to test it though, so try it with an sdcard first!
 
edit: tested the image, it works plenty well!

Here is another dmesg txt from my r29 board.
R29dmesg.txt

Ok, I need to better check what is going on with kernel 6.1 then; perhaps it is a misalignment with the base dtb, but I will try to be more specific tomorrow. Thanks in the meantime!

The Debian version has nothing to do with the underneath hardware. It's just that if you use an older image simply you miss some corrections and compatibility fixes here and there that allowed the eMCP boards work in a stable way.

Ok, I need to better check what is going on with kernel 6.1 then; perhaps it is a misalignment with the base dtb, but I will try to be more specific tomorrow. Thanks in the meantime!

The Debian version has nothing to do with the underneath hardware. It's just that if you use an older image simply you miss some corrections and compatibility fixes here and there that allowed the eMCP boards work in a stable way.

@MattWestB This is the dtb for kernel 6.1, it should work on your existing installation: rk322x-led-conf7.dtbo

@Benedito Portela I checked your firwmare and actually R29_MXQ and R2B_MXQ share the same identical original device tree, so you can go testing the image, just follow the instruction and try with a pristine system on sdcard/usb stick, not juggling with dtbs on existing systems

@Benedito Portela I checked your firwmare and actually R29_MXQ and R2B_MXQ share the same identical original device tree, so you can go testing the image, just follow the instruction and try with a pristine system on sdcard/usb stick, not juggling with dtbs on existing systems

@Benedito Portela I checked your firwmare and actually R29_MXQ and R2B_MXQ share the same identical original device tree, so you can go testing the image, just follow the instruction and try with a pristine system on sdcard/usb stick, not juggling with dtbs on existing systems

@MattWestB Ubuntu or debian does not matter, the dtb depends upon the kernel version.
The image above has kernel 6.5 (edge) and I ask to briefly test it as is, in particular look over hdmi, emmc and ethernet and report dmesg.
 
Jiggling with dtbs over other kernels, or use multitool dtb on armbian (baaad!!! never do this!) is a hazard: it may work or may end up with a broken system and a broken system surely does not help  anyone 😐
 
 
 

@MattWestB Perfect, thanks! I see the eMMC is correctly detected and ethernet working too, so probably my sample is just defective.

dmesg and 
journalctl -a as @jock requested.
 
Looks like Eth and HDMI is working OK WiFi is no go then its having one RTL8723AS and im not using it but if in the future is getting the BT working it shall being great but is not priority .
I have booting it on one USB-Stick and now back to Ubuntu on  the eMMC and HA RCP testing for thread and Zigbee.
RK3228Azip.zip

@MattWestB @Benedito Portela guys I appreciate your feedback, but please use the armbian image I gave from an sdcard and post the dmesg log if you can.
Doing cut&paste over custom setups just makes me really confused. If you already have regular Armbian installed on eMMC/eMCP, just burn the new image on sdcard, plug the sdcard and boot the board.
Your installed system won't be touched because sdcard boot has priority over internal flash. When Armbian is installed, boot priority is always sdcard, then USB stick, then internal flash.

@MattWestB @Benedito Portela guys I appreciate your feedback, but please use the armbian image I gave from an sdcard and post the dmesg log if you can.
Doing cut&paste over custom setups just makes me really confused. If you already have regular Armbian installed on eMMC/eMCP, just burn the new image on sdcard, plug the sdcard and boot the board.
Your installed system won't be touched because sdcard boot has priority over internal flash. When Armbian is installed, boot priority is always sdcard, then USB stick, then internal flash.

@MattWestB @Benedito Portela guys I appreciate your feedback, but please use the armbian image I gave from an sdcard and post the dmesg log if you can.
Doing cut&paste over custom setups just makes me really confused. If you already have regular Armbian installed on eMMC/eMCP, just burn the new image on sdcard, plug the sdcard and boot the board.
Your installed system won't be touched because sdcard boot has priority over internal flash. When Armbian is installed, boot priority is always sdcard, then USB stick, then internal flash.

UPDATE FOR R29-MXQ USERS!
 
Hello, this is an update for those people who has R29 board and have suffered issues regarding stability problems and no HDMI output.
I had the chance to have a board in my lab thanks to @Hudson FAS and something is moving!
 
What's wrong with this board:
Differently from any other known board, it has a specific GPIO pin to turn the HDMI on and off: discovering such GPIO required extensive trial and error, it was disguised in the original dtb as "power-hold" 😅
But the main problem with this board is that it has no power regulation for CPU, so it cannot run faster than 1Ghz.
The default dtb shipped with Armbian and Multitool are set to run the CPU up to 1.2Ghz. For this reason, some (most?) unlucky R29 samples were totally unable to boot with the default configuration.
 
I still need some help from community though: my sampl is able to boot and works stable but:
emmc does not work ethernet does not work unless I downgrade the link to 10 Mbit/s I suspect my sample is damaged, but I need a feedback from other users to understand if there's something more in the dtb to discover or it is just my sample.
 
Multitool
you can download a fixed version from here. It should work flawlessy and HDMI should turn on with no problems.  
Armbian
you still need to do some manual passages:
Burn the multitool on a sdcard, run it on the board, make a backup of the original firmware then erase the internal flash to force sdcard boot. Store the backup on a safe place; if you wish, it would be appreciated if a copy can be shared here for further studies! Burn this Debian Bookworm minimal Armbian image on the sdcard, the try to boot the board. If you're able to boot, access via ssh, run rk322x-config, select your configuration options and select led-conf7 as GPIO configuration in the last passage, then reboot; you're done! if your board does not boot, mount the sdcard partition and manually add  overlays=led-conf7 in /boot/armbianEnv.txt, then you should be able to boot  
Thanks!

UPDATE FOR R29-MXQ USERS!
 
Hello, this is an update for those people who has R29 board and have suffered issues regarding stability problems and no HDMI output.
I had the chance to have a board in my lab thanks to @Hudson FAS and something is moving!
 
What's wrong with this board:
Differently from any other known board, it has a specific GPIO pin to turn the HDMI on and off: discovering such GPIO required extensive trial and error, it was disguised in the original dtb as "power-hold" 😅
But the main problem with this board is that it has no power regulation for CPU, so it cannot run faster than 1Ghz.
The default dtb shipped with Armbian and Multitool are set to run the CPU up to 1.2Ghz. For this reason, some (most?) unlucky R29 samples were totally unable to boot with the default configuration.
 
I still need some help from community though: my sampl is able to boot and works stable but:
emmc does not work ethernet does not work unless I downgrade the link to 10 Mbit/s I suspect my sample is damaged, but I need a feedback from other users to understand if there's something more in the dtb to discover or it is just my sample.
 
Multitool
you can download a fixed version from here. It should work flawlessy and HDMI should turn on with no problems.  
Armbian
you still need to do some manual passages:
Burn the multitool on a sdcard, run it on the board, make a backup of the original firmware then erase the internal flash to force sdcard boot. Store the backup on a safe place; if you wish, it would be appreciated if a copy can be shared here for further studies! Burn this Debian Bookworm minimal Armbian image on the sdcard, the try to boot the board. If you're able to boot, access via ssh, run rk322x-config, select your configuration options and select led-conf7 as GPIO configuration in the last passage, then reboot; you're done! if your board does not boot, mount the sdcard partition and manually add  overlays=led-conf7 in /boot/armbianEnv.txt, then you should be able to boot  
Thanks!

UPDATE FOR R29-MXQ USERS!
 
Hello, this is an update for those people who has R29 board and have suffered issues regarding stability problems and no HDMI output.
I had the chance to have a board in my lab thanks to @Hudson FAS and something is moving!
 
What's wrong with this board:
Differently from any other known board, it has a specific GPIO pin to turn the HDMI on and off: discovering such GPIO required extensive trial and error, it was disguised in the original dtb as "power-hold" 😅
But the main problem with this board is that it has no power regulation for CPU, so it cannot run faster than 1Ghz.
The default dtb shipped with Armbian and Multitool are set to run the CPU up to 1.2Ghz. For this reason, some (most?) unlucky R29 samples were totally unable to boot with the default configuration.
 
I still need some help from community though: my sampl is able to boot and works stable but:
emmc does not work ethernet does not work unless I downgrade the link to 10 Mbit/s I suspect my sample is damaged, but I need a feedback from other users to understand if there's something more in the dtb to discover or it is just my sample.
 
Multitool
you can download a fixed version from here. It should work flawlessy and HDMI should turn on with no problems.  
Armbian
you still need to do some manual passages:
Burn the multitool on a sdcard, run it on the board, make a backup of the original firmware then erase the internal flash to force sdcard boot. Store the backup on a safe place; if you wish, it would be appreciated if a copy can be shared here for further studies! Burn this Debian Bookworm minimal Armbian image on the sdcard, the try to boot the board. If you're able to boot, access via ssh, run rk322x-config, select your configuration options and select led-conf7 as GPIO configuration in the last passage, then reboot; you're done! if your board does not boot, mount the sdcard partition and manually add  overlays=led-conf7 in /boot/armbianEnv.txt, then you should be able to boot  
Thanks!

@Stoven @jock
 
We were moving servers around and forgot about https://users.armbian.com
 
Fixed.

I got it, I don't remember if it is v2.0, but perhaps it is a v1.4; anyway it works flawlessy on my case, it has a specific led-conf because it carries the rk805 pmic that is required to make operational before trying to raise cpu frequency