09:05 <DC-IRC> [Discord] <.thenakedtruth> Does anyone know how this `rk_crypto2` module can be exactly used? Or is someone using it?

09:05 <DC-IRC> [Discord] <.thenakedtruth> I had to remove the module when I use cryptsetup with disks. Otherwise this module is killing performance. The modul consumes very high cpu and disk speed is 30MB/s.

09:20 <DC-IRC> [Discord] <rpardini> Unsure. We're carrying montjoie's (Corentin Labbe's) crypto patchset from late 2023 -- seems the series has stalled though.

09:24 <DC-IRC> [Discord] <tr9x> Hello, community. I’m writing with a problem I’ve been struggling with for some time, and I can't seem to solve it. Specifically, I have an Orange Pi 5B with a built-in 256GB eMMC disk. I want to install Armbian on it, so I download the image dedicated to the Orange Pi 5B and write it to an SD card. After booting from the card, I edit the file boot/armbianEnv.txt and change f <clipped message>

09:24 <DC-IRC> [Discord] <tr9x> dtfile=rockchip/rk3588s-orangepi-5.dtb to fdtfile=rockchip/rk3588s-orangepi-5b.dtb. I reboot the system and run armbian-install. After installing it on the eMMC and rebooting the Orange Pi 5B, nothing happens. It doesn't boot. What could be the problem? Is eMMC not fully supported yet?

09:26 <DC-IRC> [Discord] <.thenakedtruth> Ok. I will blacklist the module for now, that it does not even try to load. Seems to of no use for me for now. In the logs I see this when I mounted a cryptsetup disk. But then this fe37... process went nuts on the cpu.

09:26 <DC-IRC> [Discord] <.thenakedtruth> ```

09:26 <DC-IRC> [Discord] <.thenakedtruth> Aug 10 23:37:23 dumpster kernel: rk2-crypto fe370000.crypto: Fallback for cbc-aes-rk2 is cbc-aes-ce

09:26 <DC-IRC> [Discord] <.thenakedtruth> ```

10:04 <DC-IRC> [Discord] <efectn> Do you have USB ttl to get boot logs?

10:14 <DC-IRC> [Discord] <tr9x> Unfortunately, I don't have one.

10:14 <DC-IRC> [Discord] <tr9x> Unfortunately, I don't have one.

10:15 <DC-IRC> [Discord] <Werner> Why do you edit armbianEnv.txt? If 5b dtb wasn't there in first place you used the wrong image.

10:17 <DC-IRC> [Discord] <tr9x> There is only one image for both 5 and 5B

10:18 <DC-IRC> [Discord] <Werner> Ah, indeed there is. Didn't know they have been combined at some point. Never mind

10:26 <DC-IRC> [Discord] <pjack1212> Install with armbian-config the uboot to emmc or If aviable spi flash

10:32 <DC-IRC> [Discord] <Werner> Best chance debugging this is picking up an USB UART adapter. Absolutely mandatory for debugging SBCs. Check #❓first-aid These things are dirt-cheap and very useful.

10:34 <DC-IRC> [Discord] <tr9x> Thx

17:53 <DC-IRC> [Discord] <tr9x> I encountered a similar issue on (https://forum.armbian.com/topic/29441-orange-pi-5b-doesnt-boot-from-emmc-when-even-an-empty-sd-card-is-inserted/). Orange Pi 5B and other boards based on Rockchip CPUs have a booting issue. When the eMMC is flashed with Ubuntu (or another OS like Armbian, as I believe), the board will not boot if a blank SD card is inserted.

17:53 <DC-IRC> [Discord] <tr9x> Investigation through a serial debug cable shows that the bootloader selects the SD card as the first boot device and tries to boot from it. Since there is no valid image, the system panics and halts. On x86 systems, the bootloader would typically fallback to the next boot device.

17:53 <DC-IRC> [Discord] <tr9x> The issue is related to the module "config_distro_bootcmd.h" in the u-boot section, which defines the boot steps. The system tries to boot from the SD card without checking if it contains a valid image. Can this issue be reported to someone?

18:19 <acari> sometimes i have trouble making it boor from sd when a valid image is on emmc