Certainly worth a look. It is also probably worth comparing the Armbian commit from when I last had it working until now, but it will need to be when I have a bit more time, and me remembering just when I first started seeing these issues.

I wonder if it'd be worth having a look instead at the Odroid stock kernel image and the vanilla kernel of the base same version; see what quirks are needed. I will have a look and see if that diff is less overwhelming than the massive gap you're seeing.

Hi pcduino2user, glad you are finding it useful. Maybe CMA Buffer size needs to be lowered during the kernel, which actually appears to get ignore anyway once the board has fully booted and replaced with 96mb based on the reserve memory node within the A10 DTSI. This is definitely needed if trying to run a desktop although I wouldn't recommend running a desktop on the Pcduino2. There are still some minor issues that I would like to address in future but I don't have as much time as I used to. For example the pcduino2 is actually booting from the Pcduino1 DTS although this problem is more cosmetic than functional. Both the Pcduino1 and Pcduino2 share the same uboot defconfig file but the Pcduino2 has a USB2 VBUS pin defined within its DTS and physically connected on the PCB. This is normally pulled high by a resistor so does not cause any problems with USB power being enabled. The build framework allows us to configure the kernel but there must be a way to customize uboot more dynamically as well? Now certain Armbian board configuration files appear to contain configuration data for adjusting the dram speed as can be found in the cubieboard.csc so I wonder if a similar setup in the pcduino2 configuration file to override the default device tree property to use sun4i-a10-pcduino2.dts instead of sun4i-pcduino.dts. Given the closeness of hardware it does not seem worth creating a separate defconfig file. Ryzer

Hi @Nick A, the armbian in afiftyp board just see 2GB to, at least it was this way in 2024 when he sent me his boot log. My board is very similar to afiftyp board, except of a number near the QC sticker, that looks like a version number. afiftyp number is 2336 and the mine is 2333. The amout of memory chips is identical to (8 chips), but tha labels is a litle different, but I cant found the label meaning. I use your image since very old one, so I don't think it is about u-boot update, but I could try an older one. About Secure Boot, A patch that you give me solved it and it isn't a problem any more (thanks again for it). @afiftyp, if I'm wrong and you already solve your rom amount in armbian, please let us know and if you could, explain us what you did to solve it, thanks.

Hi Ryzer, hi Igor, I was out of town for a while, but recently I could try out the new Armbian release v25.8.1, which incorporates the changes made by Ryzer. I chose kernel version 6.15 and did get an HDMI output on a Dell 21,5" monitor. So I managed to configure the pcduino2 for its purpose and I am using it again after many years. Excellent! Thank you so much for all your efforts! Great to be back as an Armbian user. Just as a side note: I was first trying with my Dell UltraSharp 34" monitor and there the HDMI output still does not work. I does work with the old Armbian 5.38 version for pcduino2 from the archives and also with Raspberry Pi 3 using a recent version of Raspberry Pi OS. Anyway, this is just for information. I do not think it is worth investigating this issue.