Got it, Thanks a million! 
Does anyone have the base image available for others to play around with and test? I've done software dev before but haven't done anything with OpenWRT prior to this so I'm still learning the specifics around it. I got compilation working in WSL but now working on building the USB stick image.
How's the performance and range in that case? Does that still use the ath10k-ct driver (not firmware)? FWIW, I'm pretty sure the calibration data will not work correctly with the non-ct driver yet, but I'm working on fixing that (see some of the discussion on my patch).
Anyway, I'll play with it myself eventually. I see some notes elsewhere that suggest the CT drivers (or firmware?) don't support mesh well. I expect many people will want these to support mesh though, so I'd like to get that right in the default build.
OTOH, I see that most (all?) openwrt targets use -ct by default, and I'm not really sure why.
Hi Brian
Below are the error message to bring mesh up
Fri Jan 6 12:51:54 2023 kern.warn kernel: [157441.049523] ath10k_pci 0001:01:00.0: pdev param 0 not supported by firmware
Fri Jan 6 12:51:54 2023 kern.warn kernel: [157441.057095] ath10k_pci 0001:01:00.0: must load driver with rawmode=1 to add mesh interfaces
Fri Jan 6 12:51:54 2023 daemon.notice netifd: radio1 (12639): ip: SIOCSIFFLAGS: Invalid argument
Fri Jan 6 12:51:54 2023 daemon.notice netifd: radio1 (12639): Interface 0 setup failed: IFUP_ERROR
Quick googled some people suggested to use CT firmware 10.4 and others suggested to use the original firmware
I haven't got a chance to test the coverage...
1 Like
Guys, reading this thread brings euphoria. 
Y'all are like heroes.
This is coming from someone who knows nothing about coding/programming. Ha.. I only know how to read guides and install firmware. 
Y'all are amazing! Happy new year.
I've started a toh for the device with what I know. Please help adding sections specifically regarding serial access and anything I've missed: https://openwrt.org/inbox/toh/google/onhub_tp-link_tgr1900
I've also uploaded a compiled image for the TP-LINK variant, if anyone wants to try it out: https://mega.nz/file/KxE0SALb#x1h_6A9Rg7UOaJ0YRcINn8DPk3hRRF_dZhaNR2cBrNE
4 Likes
Thank you for the image. The video earlier says you need to connect a usb keyboard and type ctrl D before putting in the usb flash drive. Is this necessary?
Just followed the summary of steps on the page, used the image, and my spare OnHub is up and running! Thanks for pulling that together into one place and providing an image. Working through migrating all my configuration before I try to swap it in for the one still running the Google firmware, but so far so good.
1 Like
It is not necessary to use a keyboard and press ctrl+d. My understanding is that it just avoids having to wait for the beep, but I think hassle of connecting a keyboard is not worth it. I've tried both methods and they work.
Thank you!. WIll be trying it out today
Does it work on Asus variant?
I used Balena Etcher to flash the pre-compiled experimental firmware to a USB stick, followed the instructions, and so far, so good.
I did run into a weird issue when attempting to expand the storage as outlined here: https://openwrt.org/inbox/toh/google/onhub_tp-link_tgr1900#expanding_storage_optional
Step 6: resize2fs /dev/loop0
resulted in
resize2fs: Bad magic number in super-block while trying to open /dev/loop0
Any thoughts on how to resolve this?
The instructions there would work for ext4, but since this is squashfs partition with hidden f2fs, you can follow this guide to do it: https://openwrt.org/docs/guide-user/installation/installation_methods/sd_card
Essentially, you would need 2 commands:
opkg install f2fs-tools
resize.f2fs /dev/loop0
Got it working. Thanks a ton! Your instructions were spot on
Do you have image for the Asus model? Thanks.
Any love for ASUS SRT-AC1900? Thanks guys.
Here's a link to the asus build. I don't have this variant, so haven't tested it yet: https://mega.nz/file/m4dFEIiJ#4xftsjkyxK2Bj-QKlTXkyWHiznF8U0SotVk0zCqzhBs
Thanks for the image! It works pretty well.
Any way to easily upgrade the kernel? Also, would it be advisable to use some of the packages from generic subsystem?
Thank you again!
could you please point me to the link for the ath10k-firmware-qca988x firmware? I tried updating using the luci interface but it says the pkg I used is not compatible with the architecture. I would like to get the mesh running