05-20-2021, 05:22 PM
(This post was last modified: 05-20-2021, 06:03 PM by t4_4t.
Edit Reason: type miss
)
You can use "dmesg" to determine if "kernel param" is working properly.
The kernel I'm using is different from "Armbian", but see below for a comparison.
# kernel param: libata.force=6.0Gbps # or "kernel param": none
# kernel param: libata.force=3.0Gbps
If your settings are working as expected and you still can't see any improvements ...
There is also "force to PCIE-GEN1", but I don't think it's likely to improve.
If all you can think of doesn't work, unfortunately you have to give up.
In my opinion, "PINE's SATA-Card" is a card of that degree after all.
A similar problem occurred when I installed this "SATA-Card" on a standard "x86-Base PC".
Therefore, it is not a problem limited to Arm-based SBC.
I think the quality of this card itself is poor.
--- Addition ---
ASM1061 vs ASM1062
# lspci
It's just a matter of recognition.
The above "SATA-Card" was purchased from "PINE-Store" and the Chip stamp is "ASM1061".
But, "lspci" reports "ASM1062" as mentioned above.
The kernel I'm using is different from "Armbian", but see below for a comparison.
# kernel param: libata.force=6.0Gbps # or "kernel param": none
Code:
[ 2.853814] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.880750] ata1.00: ATA-8: TOSHIBA MQ01ABD100, AX1P2A, max UDMA/100
[ 2.880754] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 2.882527] ata1.00: configured for UDMA/100
[ 2.883274] scsi 0:0:0:0: Direct-Access ATA TOSHIBA MQ01ABD1 2A PQ: 0 ANSI: 5
[ 2.894956] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 2.894960] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 2.895075] sd 0:0:0:0: [sda] Write Protect is off
[ 2.895081] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.895130] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.109635] sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15 sda16 >
[ 3.136205] sd 0:0:0:0: [sda] Attached SCSI disk
# kernel param: libata.force=3.0Gbps
Code:
[ 2.365367] ata1: FORCE: PHY spd limit set to 3.0Gbps
[ 2.365838] ata1: SATA max UDMA/133 abar m512@0xfa010000 port 0xfa010100 irq 243
[ 2.366498] ata2: FORCE: PHY spd limit set to 3.0Gbps
[ 2.366953] ata2: SATA max UDMA/133 abar m512@0xfa010000 port 0xfa010180 irq 243
...
[ 2.830294] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 2.862941] ata1.00: ATA-8: TOSHIBA MQ01ABD100, AX1P2A, max UDMA/100
[ 2.862945] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 2.864633] ata1.00: configured for UDMA/100
[ 2.865399] scsi 0:0:0:0: Direct-Access ATA TOSHIBA MQ01ABD1 2A PQ: 0 ANSI: 5
[ 2.876828] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 2.876832] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 2.876960] sd 0:0:0:0: [sda] Write Protect is off
[ 2.876966] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.877022] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.091710] sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15 sda16 >
[ 3.101514] sd 0:0:0:0: [sda] Attached SCSI disk
If your settings are working as expected and you still can't see any improvements ...
There is also "force to PCIE-GEN1", but I don't think it's likely to improve.
If all you can think of doesn't work, unfortunately you have to give up.
In my opinion, "PINE's SATA-Card" is a card of that degree after all.
A similar problem occurred when I installed this "SATA-Card" on a standard "x86-Base PC".
Therefore, it is not a problem limited to Arm-based SBC.
I think the quality of this card itself is poor.
--- Addition ---
ASM1061 vs ASM1062
# lspci
Code:
00:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 0024
01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
It's just a matter of recognition.
The above "SATA-Card" was purchased from "PINE-Store" and the Chip stamp is "ASM1061".
But, "lspci" reports "ASM1062" as mentioned above.