-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsupported Device ubnt_nanobeam-ac-xc #611
Comments
Did you see the new install instructions for Ubiquiti AC devices in the docs? |
Yes, please use the new method which is documented on the website. You cannot install firmware this way with AC devices as the firmware is not signed. |
what is the initramfs file for? its not used in the instructions |
flash unsuccessful |
That means that your command to kill the signature validation of fwupdate failed. Try it again. Orv W6BI |
I did this and I am still getting the same thing.
how do I get the XC firmware virsion? my prompt says |
I'm guessing this isnt the Gen2 model (which I've checked)? We've not validate the non Gen2 model so I'm not sure what to expect here without access to the hardware. |
This procedure outlines how to retrieve and install the correct AirOS software: |
yes this is a gen1 how far are you from santa cruz?
I am following that guide when I do this. |
how important is it that the username and password are whats stated in the guide? |
I tried again with the same password as the docs and got the same result
|
Not sure what's going on here except to think that we need a different "patch" for fwupdate.real on this device. Can you log into the device and send the output of this:
|
|
Looking through some documentation this evening I noticed there is a different build - ubnt_nanobeam-ac-xc - which might be what we need for this device. We've not currently building it as a nightly but I can build a custom one for you to test? If it works we can then add it. |
Sure. I'd love to test it. That must be why the firmware it's trying to install is wa but my model is an xc |
I sent a build to the email registered with your sfarc slack account. Let me know if you need it sent elsewhere. |
the first time setup page is different than i'm used to sysinfo page says:
here is the support data supportdata-NOCALL-202301030028.gz when I try to change the host name and password for the first time setup I get a bad gateway error
|
Thanks. I'll add it to the nightly. |
Can you follow the instruction in the PR written by @ae6xe to extract the missing power data? Sorry. |
|
Fantastic! Thanks. |
should I try last night's nighty on my radios or wait till tomorrow when the power offset is implemented? |
The power offset is a relatively minor thing. If you'd try today's nightly it should fix everything else (hopefully) |
looks like its working here is the support data for good measure |
when I do the first time setup save it doesnt come back up properly. I have to wait till its back to "on" lights then unplug it and plug it back in |
Sorry - I'll need more detail as I dont understand what you mean by this. |
By first time setup I mean going to 192.168.1.1 and setting the hostname and password and clicking save It didn't come back up after that. I had to unplug it and plug I back in. After hitting save the dhcp server for 192.168.1.x wasn't there anymore but the 10.x.x.x never came up. My laptop kept giving itself zeroconf addresses |
A couple of things:
|
I have two nanobeam ac 5 devices that I flashed and they both did it I will test again and open a new issue if its persistent Thank you for building support for the xc variant |
I forgot to answer your question
I changed the time zone and hit the save button then the reboot button and it came back up without removing power So I think that is a yes I have not tried just using the reboot button without having saved settings changes first |
I have nanobeam AC
NBE-5AC-19
I held the reset button till I get the 1-3 2-4 blink lights
I tried
aredn-2065-599819c-ath79-generic-ubnt_nanobeam-ac-squashfs-factory
but that said error 2 frmware check failedso then I tried all of these
all of them said firmware check failed.
The text was updated successfully, but these errors were encountered: