Still no dice. So, this is a Archer c6 v2, and from the stock install, I performed the opkg install procedure from the first post, then did @DjiPi's method to change board-2.bin and firmware-5/bin. Thank you so much for finding the exact URLs for me as well @DjiPi.
dmesg now reports:
[ 12.006667] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[ 12.239461] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA9888/hw2.0/firmware-6.bin failed with error -2
[ 12.250558] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 12.520337] firmware ath10k!QCA9888!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed
[ 13.909285] ath10k_pci 0000:00:00.0: qca9888 hw2.0 target 0x01000000 chip_id 0x00000000 sub 0000:0000
[ 13.918860] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[ 13.939931] ath10k_pci 0000:00:00.0: firmware ver 10.4-126.96.36.199-00086 api 5 features no-p2p,mfp,peer-flow-ctrl,allows-mesh-bcast,no-ps crc32 5e94c44d
[ 14.300492] ath10k_pci 0000:00:00.0: failed to fetch board data for bus=pci,bmi-chip-id=0,bmi-board-id=20 from ath10k/QCA9888/hw2.0/board-2.bin
[ 14.314174] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA9888/hw2.0/board.bin failed with error -2
[ 14.324822] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 14.422965] firmware ath10k!QCA9888!hw2.0!board.bin: firmware_loading_store: map pages failed
[ 14.431979] ath10k_pci 0000:00:00.0: failed to fetch board-2.bin or board.bin from ath10k/QCA9888/hw2.0
[ 14.441709] ath10k_pci 0000:00:00.0: failed to fetch board file: -11
[ 14.448487] ath10k_pci 0000:00:00.0: could not probe fw (-11
After making these changes, To answer @darksky's question, lib/firmware now looks like:
Someone CMIIW, these are the fallback error messages that are completely normal; it tries to load a bunch of different firmware files and those that are not found produce these messages. When you replace your files, just ensure you give the same names that the ones that were already there originally and it will sweep them in it's "load scan".
I would keep the names that OpenWrt came with originally.