pakos96

Yes they are "normal" errors: the brcmfmac driver probes for such firmware files, does not find them and proceeds with other filenames. It just reports what is an information as an error, and also does not report that it finally found a valid firmware file.
brcm4334 chip has no clm_blob binary; AFAIK only newer/bigger broadcom chips have it, but older chips like 4330/4334 don't have and don't need it.
 

No problem! I was intentionally being ironic  thanks again

No problem! I was intentionally being ironic  thanks again

@pakos96 attached to this message there is a script that does the trick to change the ddrbin frequency.
Can be used on the boot block device directly on the board, or on a file to modify a ddrbin binary or an armbian image before sdcard burn.
 
Usage and examples are in-built with the script, so launching it without arguments provides all the help that could be needed.
 
Some notes:
THIS IS AN EXPERT THING. If you're not an expert, do not do this; do not come here later sobbing you made a mistake, or you will receive more insults that will make you cry even more 🫣 always always always test the ddrbin frequency change on a system booting from sdcard if there is a bootloader installed in eMMC, it has priority: changing the ddrbin on sdcard won't have any effect until you clean the eMMC (or the bootloader) some boards (notably X88 Pro) do not like ddr frequencies above 330MHz: they won't boot changing the ddrbin frequency of the bootloader in the eMMC is very dangerous! You may brick the board (only way out: maskrom via eMMC clock pin gating)  
ddrbin-switch-freq.sh

Thank you!
Yes, I have this comportamento:
echo 0 > /sys/class/leds/working/brightness -------- BLUE LED
echo 255 > /sys/class/leds/working/brightness ----------- RED LED
 
and I set:
echo "disk-activity" > /sys/class/leds/working/trigger
 
but I didn't have the blue led when there are I/O operations.
I see two led (red and blue when read/write) only in the first steps of armbian startup
 
Board: RK3328_8D4_V1.1

@pakos96 That's right, the flashing leds are made on purpose to have a visual feedback that the kernel is alive.
 
Once you setup the led-config suitable for your board, you can change the led behaviour writing to /sys/class/leds/working/trigger. You can even read that file to know which are the available triggers.

@pakos96 Ookay, got it! Glad to hear everything is fine
Thanks for the photos, they are always useful to inspect the board!

Hi,
thanks for your reply. Sorry but I can only reply to the topic once a day. I've installed the minimal version and it's ok. No problem so far. I sent the links in the previous message in the hope that you can find something useful. I hope so
I don't want to get the idea that I complained that it was "lagging" but it was just to be able to provide more information about my tv box and help in some way with the development.
These are the double-sided photos of the card (if it can help):


I am currently using the limited 1.1GHz version (although in reality the max speed is 1.01GHz), I have installed pi-hole and unbound and have not noticed any problems at the moment.
Thanks again!

Hi,
thanks for your reply. Sorry but I can only reply to the topic once a day. I've installed the minimal version and it's ok. No problem so far. I sent the links in the previous message in the hope that you can find something useful. I hope so
I don't want to get the idea that I complained that it was "lagging" but it was just to be able to provide more information about my tv box and help in some way with the development.
These are the double-sided photos of the card (if it can help):


I am currently using the limited 1.1GHz version (although in reality the max speed is 1.01GHz), I have installed pi-hole and unbound and have not noticed any problems at the moment.
Thanks again!

Hi,
thank you for your work! I've tried the latest image with mainline kernel Ubuntu Hirsute on my android box bought on Amazon Italy called "Bqeel TV Box R2 PLUS 4GB +64GB CPU RK3318" (https://www.amazon.it/gp/product/B07VXMTD78).
I installed the image on the eMMC and tried a bit to see how the performance was. It starts up correctly but it lags enough. I have created with "armbianmonitor -u" a log that maybe can help you.
This is the specification: RK3318, 4GB RAM, 64GB ROM, WIFI AP6330.
This is the link of the log: ix.io/3zSk (verbosity 7)
This is the link for download the original Android ROM: https://mega.nz/file/AYlDhA7L#y7vW7S3arW995X_m5c8URa3UGVTzxm0KDrC1-aNplGw.
 
Unfortunately I don't know how to use the soldering iron and I don't have the skills to connect a serial cable.
Hope it can help you somehow. 
Cheers