jock

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.

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!

@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!

@occams razor I produced a bunch of deb packages with update dtbs, you can find them here, in particular you can test this deb package for edge kernel 6.5. You should get a new led-conf8 overlay, so you can remove led-conf7 and add led-conf8 in /boot/armbianEnv.txt, reboot and see if the board boots and works.

@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!

I resume this thread because there have been some advancements in the HDMI problem on the R29 boards and, discussing with @ilmich and @fabiobassa, we noticed that there are some similarities with the H20 boards. @occams razor here also posted his experience with a H20 board and the photos are very informative because his board has the marking H20_221_V1.71, while the board in this thread is H20_221_V1.5. The difference is important, because @occams razor's V1.71 boots but has no HDMI, while V1.5 board does not boot at all. Despite the different form factor of the two boards, the V1.71 looks like having three high power switching regulators, while the V1.5 has just two of them. Looking at the DTB, probably both of them require to switch a GPIO to enable HDMI exactly as like as R29/R2B boards, but the H20_221_V1.5 probably is not capable to run the CPU above 1Ghz, while the V1.71 can. Multitool has been fixed for R29/R2B boards, but now it should run and show HDMI also on all H20 boards. I posted here an experimental image that H20 users can test too, enabling led-conf7 overlay as well. I may also provide a special overlay for @occams razor for his H20 V1.71, which should perhaps be able to run cpu up to 1.4 ghz

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!

@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 This is the dtb for kernel 6.1, it should work on your existing installation: rk322x-led-conf7.dtbo

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

@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 @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!

@Aapo Tahkola I guess you have some other kind of problem (ie: stability problem), because such error should never happen on both slow or fast boards, as long as it does not happen on any board I have around.

Have a box with rk3528 here and did some work some weeks ago, mainly to get a kernel and multitool running on it. It works, but I didn't publish an image for it yet (only available in source code), plus my board does not want to boot from sdcard and had no time and no will to further study it better.

@Alex ThreeD Well I think that's a little of a mess there... the patch says rk356x fix, but actually it is doing something different and I saw that those hunks were also mentioned in the libreelec kernel patches for all rockchip socs (LE patches are my reference "Bible" about video and DRM). I made some test with other LE patches and they were fixing some other rk3399 configurations, but still there are plenty of them to be included (~40 patches) that is not a good idea to submit them yet to armbian rockchip64 branch. However, I think that if the patch was lost in transition, feel free to fix the thing, send a PR and I will approve and merge the fix 👍

@Alex ThreeDthanks for investigating this! I suspected some kind or problem like that, there are some bits that have changed in a function to validate the modelines. I don't know when I will be able to fix the thing, but perhaps it could ben enough to revert the function to previous behaviour

I can't repair the server, as like as the community images are not getting produced regularly. They are not under my control.

Mmmh, I think wireguard module backport has been removed from armbian from non-mainline kernels some time ago. Upgrading the legacy kernel is quite useless though, since it is frozen at the version supplied by rockchip and not anymore upgraded. Kernel headers should be already there as a separate package, so if you need wireguard you can still compile the backport yourself.

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

@Felipe Muniz I don't think it was a good idea to change the NAND. AFAIK, eMMC can be switched with no real software issues, but NAND chips in my opinion are way thougher because they require a software layer (the FTL) to work correctly. The proprietary NAND driver contains the FTL routines for a bunch of vendors and specific parts, so IMHO you can't put any bigger/better part and expect to work out of the box. You may boot in maskrom mode, upload a recent loader and see if rfdeveloptool/rkflashtool detect the nand parameters correctly (size, vendor, page size, ecc bits, etc...),otherwise I would not expect it to work in any way.

Hello, sure it won't harm other boards, but your specific problem may be due to slow voltage regulation from low to high frequency state. 0.025v increase is very minimal that may not solve your stability issues in all cases, but just enough for a limited stress testing. I'm not minimizing your finding, but perhaps the matter may be investigated a bit if you're curious you can: 1) raise the voltage only of the one or two lower frequency bins (600mhz and 800mhz) and then run the stress test and see if you gets issues 2) run the tests with "stock" voltages blocking the cpu to the highest frequency (cpufreq-set will do the job) What I have seen on different boards is that some of them have a "lazy" power regulation that takes too long to raise the voltage to reach the right level, so when there is the frequency shift, it just gets unstable.

I will never stress out that THESE issues reported by you are the exact reasons to chose a properly supported Single Board Computer from the officially supported list and not buy crap like supercheap tvboxes. If you don't have the time, will and skills to solve troubles, tvboxes may end up being a large source of frustration. The very same problems are the main reason tvboxes are NOT OFFICIALLY SUPPORTED and NOT ENDORSED by Armbian project; tvboxes are just a community effort to have fun with them and avoid some waste, but the mileage can vary greatly. Here are the FAQs

Not sure what this sentence means: did you try to install the multitool on the internal flash? Why?!? If I understand correctly, you have been able to run once the multitool regularly, do the backup, and then something wrong happened so the board does not boot anymore?