ypopovych

Hello. I want to try UEFI boot on this board. And I have one question. Can I use Rockchip vendor kernel with Armbian UEFI?

@sdyspb Should we also bother guys on Radxa forum? I think their forum is a better place to ask about hardware. Meantime software fix from latest kernel could be backported to enable oscillator without depending on the initialization order

yes. We have this problem on Armbian with 6.1 vendor kernel. And also ubuntu builds from Joshua Riek have the same problem (they use vendor 6.1 too) ===== @sdyspb but if it's a hardware bug it shouldn't work properly on old 5.10 kernel too. But it works. And also shouldn't work randomly on 6.1 kernel. It's interesting why SRIS disabling fixes it. And why it works on old kernel with SRIS. And we have a kernel patch accepted in the 6.13 mainline kernel with fix for our problem.

From what I see it could be backported even to 6.1. It's pretty small change. One new driver into clk-gpio.c, which should work on 6.1 too and couple of changes in the DT file.

i checked latest mainline kernel sources and they have this patch merged and accepted. I think it was merged in version 6.13.

I can be wrong, but seems as hardware mod can be avoided if armbian adds this fixes to the DTS and clk-gpio.c for our board: https://lore.kernel.org/all/20240906082511.2963890-6-heiko@sntech.de/ Seems as board has proper clock for SRIS mode to work, but it should be enabled on boot. And because PCIe3.0 is split between two devices kernel starts it only for M2 slot, so if M2 slot is initialized before SATA controller it will work, if SATA controller is initialized before M2 it will not get clock signal and will hang. I checked current DTS in armbian and it doesn't have this clock logic. When we remove a resistor it simply avoids this bug and SATA controller works in a different mode (which could be slower).

@sdyspb Wow! I will try to do it in the couple of days and will tell result

I tried to install OS to the SATA SSD and connect it to the ASM1164 port to test. U-Boot detects SATA SSD, loads initrd, and then initrd fails to detect SSD and boot fails. It boots after 3-7 restarts and then works fine. Seems as U-Boot can initialize SATA controller properly and read data on every boot and kernel only one boot from five.

I have the same problem on the latest rolling release kernel. Could be that this is not a PCI problem? I have a second controller in the m.2 e-key port with JMB582 and it works fine. Also I can see ASM1164 in the lspci output but without "ahci" driver loaded for it. I can enable disks if I do: echo "1" > /sys/bus/pci/devices/0001\:11\:00.0/remove sleep 1 echo "1" > /sys/bus/pci/rescan What can I do to help debug the problem?