Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PCIe Link width degraded to x1 for RockPro64 (probably all RK3399) #6655

Closed
1 of 2 tasks
chnce opened this issue May 23, 2024 · 2 comments
Closed
1 of 2 tasks

PCIe Link width degraded to x1 for RockPro64 (probably all RK3399) #6655

chnce opened this issue May 23, 2024 · 2 comments

Comments

@chnce
Copy link

chnce commented May 23, 2024

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?

  1. Use current image 24.2.1 (or daily build) on a RockPro64 (other RK3399 will probably have the same issue)
  2. Install PCIe card with more than x1 capability.
  3. Check PCIe lane width with lspci -vv. It will only be a x1 link.
  4. Build Armbian image with patch/kernel/archive/rockchip64-6.6/rk3399-fix-pci-phy.patch disabled and flash to the RockPro64
  5. Check PCIe lane width with lspci -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?

  • Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Copy link

Jira ticket: AR-2337

@igorpecovnik
Copy link
Member

Answered in forums.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants