You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some time ago I noticed that that the SATA card on my RockPro64 only uses a x1 PCIe link, even though it supports x2.
In order to narrow the issue down, I tested different combinations of hardware (x2 SATA card, x4 NVMe) and software (latest Armbian, Armbian 23.8, manjaro ARM).
On older Armbian builds as well as on Manjaro, both cards run at their designated link width (x2 and x4).
Comparing the patches between Armbian 23.8 and current showed the introduction of the following patch: #6057
Building an image for current Armbian with said patch disabled (for which I by the way had to delete the patch, creating an empty file in user_patches did not work), restores the full PCIe with.
What happened?
Some time ago I noticed that that the SATA card on my RockPro64 only uses a x1 PCIe link, even though it supports x2.
In order to narrow the issue down, I tested different combinations of hardware (x2 SATA card, x4 NVMe) and software (latest Armbian, Armbian 23.8, manjaro ARM).
On older Armbian builds as well as on Manjaro, both cards run at their designated link width (x2 and x4).
Comparing the patches between Armbian 23.8 and current showed the introduction of the following patch: #6057
Building an image for current Armbian with said patch disabled (for which I by the way had to delete the patch, creating an empty file in user_patches did not work), restores the full PCIe with.
This is my related forum post: https://forum.armbian.com/topic/39370-pcie-width-only-x1-for-a-x4-card/#comment-191184
How to reproduce?
lspci -vv
. It will only be a x1 link.patch/kernel/archive/rockchip64-6.6/rk3399-fix-pci-phy.patch
disabled and flash to the RockPro64lspci -vv
. The link width should correspond to the full capability.Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
Ubuntu 22.04 Jammy
Are you building on Windows WSL2?
Relevant log URL
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: