BTHomeHub - Openwrt no wireless

[#1]

Hi,

After a long and dreadful day, I've managed to get OpenWrt installed on a new BT HH, everything is working fine apart from Wifi, I am unable to see it in Network menu and can't really tell if its actually working. I've pasted the relevant info that I could think of. Could a kind soul out there help me to understand what I've done wrong.

root@OpenWrt:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='23.05.5'
DISTRIB_REVISION='r24106-10cc5fcd00'
DISTRIB_TARGET='lantiq/xrx200'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt 23.05.5 r24106-10cc5fcd00'
DISTRIB_TAINTS=''

root@OpenWrt:~# ubus call system board
{
"kernel": "5.15.167",
"hostname": "OpenWrt",
"system": "xRX200 rev 1.2",
"model": "BT Home Hub 5A",
"board_name": "bt,homehub-v5a",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05.5",
"revision": "r24106-10cc5fcd00",
"target": "lantiq/xrx200",
"description": "OpenWrt 23.05.5 r24106-10cc5fcd00"
}
}

root@OpenWrt:~# wifi up
root@OpenWrt:~# wifi status
{

}
root@OpenWrt:~# wifi config
root@OpenWrt:~# wifi status
{

}

root@OpenWrt:/lib/firmware/ath10k/QCA988X/hw2.0# lspci
00:0e.0 Ethernet controller: Qualcomm Atheros AR922x Wireless Network Adapter (rev 01)
01:00.0 PCI bridge: Lantiq MIPS SoC PCI Express Port (rev 01)
02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter

root@OpenWrt:/lib/firmware/ath10k/QCA988X/hw2.0# dmesg | grep 00:0e.0
[ 0.361284] pci 0000:00:0e.0: [168c:ff1d] type 00 class 0x020000
[ 0.367173] pci 0000:00:0e.0: reg 0x10: [mem 0x00000000-0x0000ffff]
[ 0.381878] pci 0000:00:0e.0: BAR 0: assigned [mem 0x18000000-0x1800ffff]
[ 13.490181] ath9k_pci_owl_loader 0000:00:0e.0: enabling device (0000 -> 0002)
[ 13.498835] ath9k_pci_owl_loader 0000:00:0e.0: Direct firmware load for ath9k-eeprom-pci-0000:00:0e.0.bin failed with error -2
[ 13.509031] ath9k_pci_owl_loader 0000:00:0e.0: Falling back to sysfs fallback for: ath9k-eeprom-pci-0000:00:0e.0.bin
[ 14.571795] ath9k_pci_owl_loader 0000:00:0e.0: no eeprom data received.

root@OpenWrt:/lib/firmware/ath10k/QCA988X/hw2.0# dmesg | grep 02:00.0
[ 2.643233] pci 0000:02:00.0: [168c:003c] type 00 class 0x028000
[ 2.648924] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[ 2.655751] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[ 2.662530] pci 0000:02:00.0: supports D1 D2
[ 2.695801] pci 0000:02:00.0: BAR 0: assigned [mem 0x1c000000-0x1c1fffff 64bit]
[ 2.703144] pci 0000:02:00.0: BAR 6: assigned [mem 0x1c200000-0x1c20ffff pref]
[ 14.159670] ifx_pcie_bios_map_irq port 0 dev 0000:02:00.0 slot 0 pin 1
[ 14.164970] ifx_pcie_bios_map_irq dev 0000:02:00.0 irq 144 assigned
[ 14.291103] ath10k_pci 0000:02:00.0: enabling device (0000 -> 0002)
[ 14.296281] ath10k_pci 0000:02:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[ 19.831078] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[ 19.838947] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[ 19.856790] ath10k_pci 0000:02:00.0: firmware ver 10.2.4-1.0-00047 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 35bd9258
[ 19.900262] ath10k_pci 0000:02:00.0: Loading BDF type 0
[ 20.828393] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 20.922366] ath10k_pci 0000:02:00.0: otp calibration failed: 2
[ 20.926817] ath10k_pci 0000:02:00.0: failed to run otp: -22 (download-cal-data)
[ 20.934158] ath10k_pci 0000:02:00.0: could not init core (-22)
[ 20.940149] ath10k_pci 0000:02:00.0: could not probe fw (-22)

When I try to restore the stock firmware it tells me that it is successful but the messages above it complains about /dev/ubi9_1 to 3 do not exist?

Any help would be appreciated @MisterW 

Moderator's note by Mike (Mav): Post released from Spam Filter.

[#2]

@haval I'm afraid I'm not likely to be much help.

I did once try to install Openwrt on a Plusnet Hub one (aka BT Home hub A) but gave up as I could never get the serial interface to be reliable!

My current use of Openwrt is on a TPlink ER605 and a Ubiquiti ER-X , neither of which have wifi functionality. I use a separate wireless AP to provide wifi.

From the Openwrt site https://openwrt.org/toh/bt/homehub_v5a , it does seem like no wifi is a distinctly possible scenario but all it says is

If OpenWrt/LEDE installation fails, or you discover there is no wireless interfaces, you should restore the original stock firmware from the earlier 128 MiB Nanddump file you created, and try again to install OpenWRT. See section 5 of the OpenWrt/LEDE Installation Guide for BT Home Hub 5A which describes how to use the restore script in detail. Restoring stock firmware can be completed in as little as 3 minutes, otherwise, it normally takes just over an hour. Once Nanddump restoration is complete, the script offers the option to install OpenWrt/LEDE again. Otherwise, the hub will reboot and launch stock BT/Plusnet firmware. 

which is what I assume you've tried ?

[#3]

Thanks amigo. Yes I tried doing the stock firmware restore but I don't believe it restored it because it complains about /dev/ubi9_1 to 3 do not exist which tells me that the dd command has probably failed. Why would the restore be pointing to a device that does not exist

[#4]

which tells me that the dd command has probably failed

Sounds feasible!.

I must admit I was a bit wary of installing Openwrt on my ER605 , since the install reconfigured the ubi structure, but at least I didn't have to do it via a serial connection.

As I said, I gave up on the Hub one, and also it wasn't going to cope with the throughput of my FTTP connection anyway.

If you're looking for an Openwrt router , I assume you seen this thread  ?

[#5]

My BT Internet requires an ADSL router which is the homehub, I have a spare which is what I am working on to get it working so I can replace my current one and avoid having 2 routers.

I see so many people having got it to work just don't understand why I am having the issue when I've followed all the steps unless there's always the possibility that I may have done something hence why I am trying to restore the stock firmware but failing.

Writing data to block 1011 at offset 0x7e60000

ATTACHING backup ubi partition to ubi dev number 9
UBI device number 9, total 1016 LEBs (131088384 bytes, 125.0 MiB), available 991 LEBs (127862784 bytes, 121.9 MiB), LEB size 129024 bytes (126.0 KiB)

DETACHING nand ubi partition...

RESTORING u-boot partition from backup
Erasing 128 Kibyte @ 80000 -- 100 % complete
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000

RESTORING u-boot env partition from backup
Erasing 128 Kibyte @ 0 -- 100 % complete
Writing data to block 0 at offset 0x0

RESTORING unused partition from backup
Erasing 128 Kibyte @ 20000 -- 100 % complete
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000

FORMATING nand ubi partition
ubiformat: mtd3 (nand), size 132644864 bytes (126.5 MiB), 1012 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 1011 -- 100 % complete
ubiformat: 1012 eraseblocks have valid erase counter, mean value is 80
ubiformat: formatting eraseblock 1011 -- 100 % complete

ATTACHING nand ubi partition to ubi dev number 0 using
19 reserved blocks for bad block handling
UBI device number 0, total 1012 LEBs (130572288 bytes, 124.5 MiB), available 989 LEBs (127604736 bytes, 121.7 MiB), LEB size 129024 bytes (126.0 KiB)

RESTORING OpenRG ubi volume from backup
Volume ID 1, size 326 LEBs (42061824 bytes, 40.1 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "OpenRG", alignment 1
dd: can't open '/dev/ubi9_1': No such file or directory
ubiupdatevol: erro[  171.181815] ubi0 warning: vol_cdev_release: update of volume 1 not finished, volume is damaged
r!: cannot read 129024 bytes from "-"
              error 0 (No error information)

RESTORING [-Censored-] ubi volume from backup
Volume ID 2, size 662 LEBs (85413888 bytes, 81.5 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "[-Censored-]", alignment 1
dd: can't open '/dev/ubi9_2': No such file or directory
ubiupdatevol: erro[  171.245991] ubi0 warning: vol_cdev_release: update of volume 2 not finished, volume is damaged
r!: cannot read 129024 bytes from "-"
              error 0 (No error information)

RESTORING caldata ubi volume from backup
Volume ID 3, size 1 LEBs (129024 bytes, 126.0 KiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "caldata", alignment 1
63+0 records in
63+0 records out