jock

@SuperMaximus probably you can disable the vop nodes in the device tree and there will be no video output. Another way could be to disable the video output in the u-boot configuration/header files (ie: remove vidconsole)

@stroma Hello, thanks for the photos, they will be useful at least to have an idea of the issue. Anyway did you try the experimental image with kernel 5.19.15 and libreelec patches? They have several HDMI/DRM fixes, perhaps they fix your case. Since the LE patches are not mainlined into armbian, you should then not upgrade the kernel. I quickly looked back and @Seth described similar issues you have had with his two boards.

Hmmm that's odd, I applied the same "fix" @ilmich applied on libreelec but it didn't work. The serial log output could have been very handy here; we will think about what could be wrong and maybe some other idea may pop up.

@rafaeldavid I actually don't remember what exactly we discussed about the last time, but surely R29 boards have this long-time HDMI issue I could not inspect because have no such board and noone provided one to study. For the clock issue, I don't remember if I suggested you to use the cpu-stability (both with 1.2 or 1.4 ghz max frequency) overlay and see if it makes any difference. What I could guess about is that there are some board whose power regulation design in "slow" to bring up voltage in time for the frequency change, so random crashes happens. The overlay will raise the lowest voltage from 0.900v to 1.100v, so the gap with max voltage (1.35v) is shorter. I have a board with such kind of issue right here, and that overlay made it work flawlessy.

Perhaps @Seth can give some advice.

To debug the problem, it is better to paste the link coming from armbianmonitor -u ; also photos of the board are very useful to identify which board you have. Also this is the reference thread for rk3318 boxes

@ochentay4 I set up a multitool image with the same fix proposed by @ilmich on his libreelec image. This fresh build is totally untested, but you can download a copy from here and test by yourself. Perhaps this solves @n3o problem too.

@arcube101 Hi, this kind of problems usually is in the wifi firmware/nvram ballpark, except for on kind of software issue I experienced: check if wpasupplicant debian package is correctly installed in your system: that package was removed as a dependency from network manager in upstream packages, thus was not included anymore in the base armbian images. Installing it manually may solve the problem. Other than that, I have seen such kind of refusal when the crystal reference clock was set to a wrong frequency, but AFAIK on realtek chips you really can't se the reference frequency via driver option or nvram. Try the first suggestion and see if it works.

@moussa854 Hello, from the logs you posted it looks to me that the eth0 interface seems to be DOWN: ### ip addr: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet XXX.XXX.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 56:9e:45:d9:4d:b8 brd ff:ff:ff:ff:ff:ff

🥳🥳🥳

No, I mean the serial output logs. If you don't know what I'm talking about, read the rest of the thread or search with google.

Inference in which sense? An opencl load of some sort?

Paste the serial output logs here; without them, we're blind

Best hope is that it will go around 400mbit/s, more reasonably around 300/350mbit/s; surely you won't get anything near the full gigabit.

Nope. But you can put the compressed image and multitool will decompress on the fly

Hello, what do you mean exactly with: Also post the link given by armbianmonitor -u

NAND are not exactly easy beasts, if the multitool does not detect it anymore it is because the kernel rockchip driver does not detect it. It is difficult to say what happened exactly, we have spent hours and hours to figure out what was the behaviour of the nand driver and all the other proprietary software pieces of the puzzle. Also they are quite "fragile" pieces of hardware, and abusing of them can quickly destroy the cells capacity to work. In the past, people has restored the NAND functionality restoring original android images with AndroidTool for windows, or uploading particular bootloaders; you should look for such resources in this thread (or with google) because some procedures were described to do so I forgot to bookmark. For what me and @fabiobassa have seen, what seems to be an apparently random behaviour of the NANDs, in reality it is deterministic and can be understood. What we've found to be totally confusing was the fact that keeping anything attached to the board (HDMI, ethernet, keyboard, serial adapter, ... whatever!) can prevent the NAND from being detected after a reboot. Also remember to use the armbian image with the legacy kernel, those with mainline kernel miss the proprietary driver. Also you could post a dmesg log after booting such legacy kernel image to see what the driver has to say about NAND.

I think all the greetings go to @SteeMan that spotted the missing bits in some armbian configuration files

Well, maskrom mode is ALWAYS possible, there is no way except doing hardware damage to the board to break maskrom mode.

They ARE developed, and are pretty advanced too. The problem is that video acceleration in browsers is far from being a simple task. Consider that it is not so easy to have hardware accelerated videos even with regular x86

Hmmm, this is interesting, because I experience this also on rockchip 32 bit with kernel 6.1.11 revision. Perhaps we're hitting a kernel bug at this point

@gerotmf You could keep a ssh session with dmesg -w command running while you do the operations that freeze your board. This way you will immediately see kernel issues on dmesg log as soon as they appear, if there is any. After inspecting the dtb, I don't see anything really relevant that may causes crashes. You can run some benchmark/testing tools like openssl (using the "speed" benchmarking mode) or memtester to chek the ram. Also you may follow the instructions in this post to install an alternative bootloader with memories at 333 MHz (in place of the stock 666 MHz) and see if you get better stability.

Yes I made some precompiled images in the past, but they are not updated anymore because there are the "nightly" ones. I suggest you to go with nightlies, which are updated very often, even though they are not declared "stable" because they come with the "edge" kernel flavour. You can always switch to a "current" (ie: older kernel, considered "stable") kernel using armbian-config if you prefer. The only drawback with nightlies is that the userland comes with debian sid or latest ubuntu, which is not always an optimal choice (debian sid is way too edgy, for my tastes). Yes I am

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

@Slash402 actually, I don't even know if there is real fault in the hardware or 4 chips are fake or whatever... looking at the PCB there are 8 chips of 2 gigabits each, so they should account for a total of 16 gigabits = 2 gigabytes. Now 1 gigabyte is missing, but who knows why... the tricks and gimmicks of chinese cheap tv boxes are infinite. The original idbloader runs the memories at 666 mhz, it is a very nice bump in general performance against the 333 mhz of these other idbloaders, so I suggest to use the original one if it works ok for you.