RussianNeuroMancer

Put this into /etc/rc.local: rmmod phy_rockchip_pcie && modprobe phy_rockchip_pcie exit 0 Don't forget to make it executable. There was attempt to fix this, but it broke other boards.

I didn't tried this on R2S specifically, but if it works inside systemd-nspawn - then it should work on headless SBC too. 1. Install Mate or XFCE via tasksel 2. Install gdm3 and tigervnc-standalone-server 3. Create these two files (don't forget to enable socket) and configure gdm3. This is of course not only option - you can find other ways to get TigerVNC or xrdp works on headless system. I just told you what works for me, that it.

What do you mean? hs400 is still there.

Thanks for answers! Dynamic Frequency Scaling I never seen anyone with this issue and SSD, which is why I asked. (Assumed that it could be related to board's power supply somehow.) Thank you for sharing your workaround.

So solution for this DFS issue was never found? Also is anyone got this issue with SSD drives? Or it happens only with HDD?

Hi! Thanks for advice, but unfortunately I don't have any Tritium H5 left on hands anymore, so I can't test this. If it works for you - maybe it makes sense to submit this change to upstream or at least ask for tests on mail-list?

Yes, another workaround is in this post. Here is working link to the package for K2. After installing the package you will need to install these old uboot via armbian-config.

Hello! I have three Libre Computer Tritium H5 boards and three eMMC modules on hands. All three eMMC modules is flashed with exactly same Armbian image and exactly same uboot. I also use exactly same PSU and cable for all three boards (however I reproduced this issue with four PSU and three microUSB cables, no difference in behavior was found). All three boards start just fine from microSD (so it's not exactly "Your board doesn't work?" case). One board never boot from eMMC on first power up, but almost always boot on second power up. That reproducible with all three eMMC modules. Two other boards just never boot from any eMMC module. When board can not boot from eMMC it just stuck there: U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot SPL 2021.04-armbian (May 06 2021 - 19:52:02 +0000) DRAM: 2048 MiB Trying to boot from MMC2 That five power up attempt as you can see. I tried to rollback uboot to 2020.04, but it behave in exactly same way.` All three boards was ordered at the same time, in one package. Is anyone can reproduce this? Is there anything else to try, or I should just give up and stick with microSD for now? (Although I probably could left uboot and /boot on microSD and then put rootfs on eMMC, but that another story.)