ypopovych Posted February 20 Posted February 20 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. 0 Quote
Igor Posted February 20 Posted February 20 22 minutes ago, ypopovych said: could be backported even to 6.1 You mean this problem is present also on Rockchip vendor kernel? Well, then this is also helpful, while for mainline based kernels, 6.6 and 6.12.y are only target. Besides EDGE, where this will emerge automatically. Thanks. 0 Quote
sdyspb Posted February 20 Posted February 20 (edited) 10 hours ago, ypopovych said: When we remove a resistor it simply avoids this bug and SATA controller works in a different mode (which could be slower) It sounds wrong. There is no degradation in speed. Also, your assumption about SSC of the clock generator is wrong as well. According to datasheet of AU5426, it does not support SSC Edited February 20 by sdyspb 0 Quote
ypopovych Posted February 20 Posted February 20 (edited) 8 hours ago, Igor said: You mean this problem is present also on Rockchip vendor kernel? 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. Edited February 20 by ypopovych 1 Quote
sdyspb Posted February 20 Posted February 20 (edited) Just look at this from datasheet and schematic perspective - ASM1164 needs SSC if SRIS is enabled, but according to datasheet of clock generator there is no SSC, so the original schem is not correct. There are three solutions: 1) place somehow clock with SSC or the best one is adding the independent clock for ASM1164 2) unsolder R29 to disable SRIS 3) disable SRIS by software At this moment I choose number two, but if you find the third one I will stand on your side Actually, SRIS means that RC and EP are clocked by different sources (I think it is like SSC where some jitter always exists), but in Radxa 5 ITX all the clocks are produced by one oscillator, so, SRIS is not right mode for this board. According to PCIe architecture the board uses Common REFCLK, not SRIS. Due to Common Clock the PLL of ASM1164 can't sync in SRIS mode because it needs a little deviation to be locked Edited February 20 by sdyspb 0 Quote
ypopovych Posted February 20 Posted February 20 @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 0 Quote
sdyspb Posted February 20 Posted February 20 (edited) I've already sent them my fix in WeChat (Tom Cubie and his team). They promised to take a look at my point. Of course, asking them on forum is a great idea Edited February 20 by sdyspb 0 Quote
prahal Posted February 21 Posted February 21 I will try this 6.13 patchset but it looks like SATA drives are already stable with 6.12 (iè without this patchset) or at least more stable than vendor 6.1.Could be another fix between 6.1 and 6.12 helps.Envoyé de mon CPH2089 en utilisant Tapatalk 0 Quote
prahal Posted February 21 Posted February 21 Still building 6.1 vendor with the gated clock patch set. Though I noticed the mainline kernel has default pinctrl settings for pcie but not the vendor one. If one want to try testing these dts pinctrl pcie definition from mainline to vendor. 0 Quote
prahal Posted February 23 Posted February 23 So the vendor 6.1 kernel set both the pcie3x2 ASMedia SATA and pcie3x4 M.2 M.Key vpcie3v3-supply with the same `vcc3v3_pcie30` supply which is the supply for the pcie ref clock so they worked around the issue by describing incorrectly the supply for these pcie controllers. This pcie ref clock power supply patch set is likely still of interest for the mainline 6.12 branch. I confirm that I was at least once able to reproduce the ASMedia SATA not seen with the gated ref clock patch set applied to the vendor branch (even though as I found later on there was already a workaround in the vendor kernel in that they set the oscillator supply as the supply for both pcie controllers even though that does not describe the hardware correctly). 0 Quote
alrouen Posted March 1 Posted March 1 I own a radxa itx 5 (rev2). I can confirm that a custom armbian build on edge branch (kernel v6.14) works perfectly (SATA drives are always detected). But all my previous test with armbian 6.1 / rock-ubuntu or even with the latest radxa OS version had the same issue with the SATA drive (sometime found sometime not) 0 Quote
Bobbox Posted March 16 Posted March 16 I'm a beginner and I'm new to armbian and linux in general. I have a NVME + SATA HDD plugged on my Rock 5 ITX with the problem of the HDD not detected. I tried different sever images listed here  , but the HDD was not detected. The debian 12/kernel 6.1 based image from Radxa works, the HDD is detected, but it doesn't match my needs of a minimal server image. As a tentative, I built the following custom image based on Ubuntu Jammy and the SATA HDD is detected at every boot (sda 1TB). v25.5 rolling for Rock 5 ITX running Armbian Linux 6.12.19-current-rockchip64 Packages: Ubuntu stable (jammy), possible distro upgrade (noble) Last login: Sun Mar 16 18:46:48 2025 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 931,5G 0 disk └─sda1 8:1 0 931,5G 0 part mtdblock0 31:0 0 16M 0 disk zram0 253:0 0 3,9G 0 disk [SWAP] zram1 253:1 0 50M 0 disk /var/log zram2 253:2 0 0B 0 disk nvme0n1 259:0 0 238,5G 0 disk └─nvme0n1p1 259:1 0 236,1G 0 part /var/log.hdd / I cannot say if this image has other issues, but till now it's doing its job. 0 Quote
Igor Posted March 16 Posted March 16 24 minutes ago, Bobbox said: I tried different sever images listed here  , but the HDD was not detected. This should be fixed in 1h - i forgot to move latest images to the download area. 0 Quote
Popolon Posted Sunday at 10:46 PM Posted Sunday at 10:46 PM Hi, same problem here, however kwankiu archlinux that use the same release of the kernel has working SATA. Maybe it's patchs or options could be used as references? Didn't looked at the reboot issue. On the other side Arch for ARM is far more limited than other Arch Linux flavor I use (x86_64 and RISC-V), strangely there is not even GL acceleration (only vulkan-panfrost is compiled). Armbian as far more complete package set. I would like to have a Trixie version to cross compile some RISC-V things, as GCC12 included in Bookworm What, uname sees as kernel: Armbian (no SATA but GL acceleration): Linux rock-5-itx 6.1.99-vendor-rk35xx #1 SMP Wed Mar 19 11:16:36 UTC 2025 aarch64 GNU/Linux Archlinux (SATA, but no GL acceleration) Linux armitx 6.1.99-rockchip #1 SMP Fri Feb 28 19:07:25 HKT 2025 aarch64 GNU/Linux zgrep SATA give the same options set: <pre> $ zgrep SATA config.gz CONFIG_SATA_HOST=y CONFIG_SATA_PMP=y CONFIG_SATA_AHCI=y CONFIG_SATA_MOBILE_LPM_POLICY=0 CONFIG_SATA_AHCI_PLATFORM=y # CONFIG_SATA_INIC162X is not set # CONFIG_SATA_ACARD_AHCI is not set # CONFIG_SATA_SIL24 is not set $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 1,8T 0 disk ├─sda1 8:1 0 47,7G 0 part ├─sda2 8:2 0 47,7G 0 part ├─sda3 8:3 0 1,7T 0 part └─sda4 8:4 0 6G 0 part sdb 8:16 0 2,7T 0 disk ├─sdb1 8:17 0 50G 0 part ├─sdb2 8:18 0 2,7T 0 part └─sdb3 8:19 0 2G 0 part mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 7,3G 0 disk ├─mmcblk0p1 179:1 0 16M 0 part ├─mmcblk0p2 179:2 0 300M 0 part └─mmcblk0p3 179:3 0 7G 0 part mmcblk0boot0 179:32 0 4M 1 disk mmcblk0boot1 179:64 0 4M 1 disk mmcblk1 179:96 0 28,9G 0 disk ├─mmcblk1p1 179:97 0 16M 0 part └─mmcblk1p2 179:98 0 28,8G 0 part / nvme0n1 259:0 0 238,5G 0 disk └─nvme0n1p1 259:1 0 236,1G 0 part </pre> 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.