You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Software versions of OpenWrt/LEDE: 19.07.0-rc1, 18.06.4
Steps to reproduce: Flash and run
I see that the list of supported hardware does not include Ubiquiti Rockets, though they are mentioned in the source tree, and of course they appear in the published ubnt images.
There was a patch submitted in 2015 for a bug where the eth0 interface could not be found. The dmesg error line was something like: ag71xx ag71xx.0: no PHY found with phy_mask=00000023
I just looked at the setup in ar71xx and found that there the rocket-m-xw has exactly the same setup as the bullet-m-xw.
So, you could try the ath79 ubnt_bullet-m-xw image from master or 19.07.3 and report whether the same issue exists there (you would need to force-flash, and not keep settings). Based on the result, we could add support for the rocket-m-xw in ath79 as a clone of the bullet-m-xw ...
valentis:
Greetings,
I see that the list of supported hardware does not include Ubiquiti Rockets, though they are mentioned in the source tree, and of course they appear in the published ubnt images.
There was a patch submitted in 2015 for a bug where the eth0 interface could not be found. The dmesg error line was something like: ag71xx ag71xx.0: no PHY found with phy_mask=00000023
It is talked about here: https://forum.archive.openwrt.org/viewtopic.php?id=56830
The patch is here: https://patchwork.ozlabs.org/patch/461730/
Though, when I load a few of the latest rocket M2 XW images I still get that error. However, if I load a nano M XW image it seems to work fine.
Is this a regression? What is the best way to handle it? Should the Rocket support be rolled into the nano, or should it's build target be fixed? :-)
The text was updated successfully, but these errors were encountered: