DAP-X1860 A1 - pci=realloc solution without local build?

[mnj]

Device: D-Link DAP-X1860 A1
OpenWrt: 25.12.0-rc3
Issue: PCI BAR allocation failures but device has no serial port

Problem:

• Getting: "pci 0000:00:00.0: BAR 0: failed to assign"
• u-boot-tools not available in APK repos
• No fw_printenv command
• Device has no external serial port

Question: Any workarounds or solutions for this device?

My U-Boot doesn't store bootargs in environment (uses device tree).
fw_setenv approach doesn't work.

Anyone have a pre-built firmware with pci=realloc, or alternative solution?

[brada4]

Any actual problems?
a- embedded pcie slots with nothing connected can fail en masse
b- whats the use of them
c- you will not be able to mod oem bootloader to any good end. You can specify extra parameters for linux cmdline rebuilding image.
d- buy a rackmount server instead

[mnj]

Thanks for the feedback! This clarifies things significantly.

Addressing Your Points

a) "Embedded PCIe slots with nothing connected can fail en masse"
Understood - I have two MediaTek MT7915E WiFi cards (2.4 GHz and 5 GHz) actively
using the PCIe slots. Good to know this behavior is expected for embedded devices.

b) "What's the use of them"
The two PCIe slots host WiFi radio modules:

• PCIe 0: MT7915E (5 GHz, 802.11ax)
• PCIe 1: MT7915E (2.4 GHz, 802.11ax)
  Both functioning normally.

c) "You will not be able to mod OEM bootloader... rebuild image instead"**
This confirms what we discovered: my device doesn't store bootargs in U-Boot
environment - they come from the kernel device tree. So fw_setenv couldn't modify
them. The solution would be rebuilding OpenWrt with `pci=realloc` embedded in the
kernel cmdline, correct?

d) "Buy a rackmount server instead"
Ha! Fair point - reality check appreciated. This is consumer-grade hardware.

Conclusion:
Based on your guidance:

1. Device functions correctly as-is
2. PCI BAR warnings are expected on embedded devices
3. If I rebuild firmware, I can suppress warnings with `pci=realloc`
4. But it's optional since device works perfectly

Thanks for the clarification and helpful context!