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
bpi-r4 doesn't recognize all PCI devices #14767
Comments
full boot log attached |
full boot log from bpi stock |
Reading the lspci output between the bpi and snapshot images, it seems that one of the pci controllers is not being detected under 6.1 kernel. Specifically this one:
|
Using the command
On Snapshot:
Some of the lines that changed seem like they might be the problem. On the sinovoip image:
these change to the following on snapshot:
So the clocks seem different on the latest snapshot. That might explain the kernel log errors and why the card is not being detected. Specifically, snapshot is missing clock values |
Describe the bug
Compared to the Banana pi-provided image which is based on kernel 5.4.246, the most recent snapshot of openwrt fails to detect all the PCI devices on. I'm specifically trying to get a T99W175 b-key modem working. On the sinovoip provided build, the modem is detected, but not on snapshot openwrt.
There are some suggestive errors in the kernel log:
The device I'm expecting to see shows this output in lspci when booting on the 5.4 kernel:
Those errors mentioning "probe failed" with code -110 seem like they might be related.
This is from today's (2024-03-01) nightly downloaded directly from downloads.openwrt.org.
I'm curious if there's any fix for this issue.
OpenWrt version
r25361-a86ff06d2e
OpenWrt release
SNAPSHOT
OpenWrt target/subtarget
mediatek/filogic
Device
Bananapi BPI-R4
Image kind
Official downloaded image
Steps to reproduce
Put a PCIe card in the b key M2 slot, boot up.
Actual behaviour
Card not detected
Expected behaviour
Card is detected (and then drivers load)
Additional info
No response
Diffconfig
No response
Terms
The text was updated successfully, but these errors were encountered: