I got a Nanostation M2 on eBay and tried to load 3.20.2.0 and got the "Untested Hardware" banner. I then loaded 3.19.3.0 and it worked fine.
I have attached the support data file for this Nanostation M2 (XM) version. I'd like to get this device on the latest firmware if possible.
Thank you Bill NG1P
I have attached the support data file for this Nanostation M2 (XM) version. I'd like to get this device on the latest firmware if possible.
Thank you Bill NG1P
Support File Attachment:
Hi, Bill:
Did you try the TFTP method?
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#ubiquiti-first-install-process
Now that you have 3.19.3.0 loaded, can you upgrade using 3.20.3.0 sysupgrade?
Chuck
Joe AE6XE
Also what is interesting is after the update the main port and secondary port will not provide a DHCP address. Setting my PC to a 192,168,1,x address I can then get into the Nanostaition on 192.168.1.1 but only using the secondary port the main port doesnt work at all. Also the LAN LED's dont light up.
Attached is the support file for 3.20.3.0
Thank you!
Can you confirm which image you have loaded?
A) http://downloads.arednmesh.org/releases/3/20/3.20.3.0/targets/ath79/gene...
B) http://downloads.arednmesh.org/releases/3/20/3.20.3.0/targets/ar71xx/gen...
For some reason, the ubqiuiti board ID information is not found, hence untested message. I'd expect this to occur regardless of which image is uloaded. can you access with command line and send back the output of these 2 commands?:
1) cat /sys/devices/pci0000:00/0000:00:00.0/subsystem_device
2) dd if=/dev/mtd7 bs=1 skip=12 count=2 2>/dev/null | hexdump -v -n 4 -e '1/1 "%02x"'
On Ubiquiti, option 1 is tried first, if that doesn't exist, then option 2 is supposed to work. It's finding 0xFFFF on your device, just want to make sure which command is returning this value.
for the network ports, the LAN is bridged across these 2 ports. Something odd:
[ 1.567771] ag71xx 1a000000.eth: connected to PHY at fixed-0:00 [uid=00000000, driver=Generic PHY] <- uid shouldn't be 0s
[ 27.954049] eth0: link up (1000Mbps/Full duplex) <- hmmm, I don't believe the main port is a gigabit port...
If you have loaded the ath79 image, try the ar71xx image to see if this issue resolves? I suspect there may be some minor variations in the NS M2 hardware and the new ath79 images only work on one flavor.
Joe AE6XE
I was trying the ath79 image, I tried the ar71 image but got received ERROR <code=2, msg=Firmware check failed>
Error code 2: Firmware check failed. So the ar71 image would not even load.
This is the results from the command line: on ath79 image:
root@NOCALL:~# cat /sys/devices/pci0000:00/0000:00:00.0/subsystem_device
0x0000
root@NOCALL:~# dd if=/dev/mtd7 bs=1 skip=12 count=2 2>/dev/null | hexdump -v -n 4 -e '1/1
"%02x"'
ffffroot@NOCALL:~#
Just for fun I did the same commands from the working 3.19.3.0 image:
root@NOCALL:~# cat /sys/devices/pci0000:00/0000:00:00.0/subsystem_device
0xe012
root@NOCALL:~# dd if=/dev/mtd7 bs=1 skip=12 count=2 2>/dev/null | hexdump -v -n 4 -e '1/1
"%02x"'
ffffroot@NOCALL:~#
Joe AE6XE
Interesting??? Must be a bug in the factory bin? I added the support file just incase that might help.
Thank you
Bill NG1P