-
Notifications
You must be signed in to change notification settings - Fork 82
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
Unable to flash on RT-AX82U v2 #475
Comments
thanks for reporting this. The problem is not the extension, but I think the problem is something nasty that happens during linking phase of some executables in the last stages of the build. I just need to rebuild the code and check. |
#474 is linked to this issue |
To add, using the file from beta 1 instead of beta 2 worked, it has flashed but has a few quirks (see other issue reports, such as wifi insight giving the 404). |
Here the syslog after uploading a broken image
|
Checked dhd prebuilts and they are fine |
Yes, the build from beta 1 flashed for me, but the one that was previously linked in beta 2 did not. Something is definitely different between the 2. Looks like it happens pretty early on aswell. |
from the build looks these lines look suspicious too
|
Complete build logs from circle ci |
Those definitely will cause problems yeah. |
I checked once again the GPL that I got from ASUS and it's broken CONFIG_BCM_BOOTSTATE_IMPL=1 as it was failing for me before my fix. Moving the archer.o from hnd_extras folder to the SDK folder fixes the problem and the built stock image looks to flash and work correctly. According to Eric the crash seems to come from archer. The prebuil I used is btw correct. |
edit: I succed to revert to stock fw by downloading an much earlier version. Then upgrading to latest again. Phuu.. thought my days was gone at home.. children and wife was all things but happy. Why is this Beta2 available for downloading when it seems to fukk up peoples router? Earlier this day: |
Not clear from reading through here what the status is on Beta 2 for the 82U V2? Is this any closer to resolution or is the stock GPL code from Asus also in trouble? I don't want to F*** my router but I wanted to put it into production, like yesterday....;-) |
@TelecomDoctor the RT-AX82U_V2 is still unstable so it remains in beta. I will push a new beta when i get this fixed. |
Beta 1 works for me on my v2. |
Yes thanks for chiming in. I did/do have the B1 on my V2. There is a BUG report #476 open on it. |
Hi there - any updated status for the Beta 2 for this router? Thanks |
@TelecomDoctor the RT-AX82U_v2 comes with a new SDK and something is not right. I am still investigating.. |
Found anything new on this yet? So far the Beta 1 is still running fine without a hitch for me. |
Fixed a few things, but the main problem is still there and to me it still feel like it's in the building system of the new SDK. I think I will try to release a new image soon. |
To fix this issue for RT-AX82U_V2, just do as below: cd release/src-rt-5.04axhnd.675x/bcmdrivers/broadcom/net/wl
ln -sf impl87 bcm963178 then you can run your build process |
thanks @sadoneli testing... the symlink is actually missing in the git repo.. but I thought it was created by the build system. from the circle ci logs:
In any case I am testing this now. Here is the test build with this fix https://app.circleci.com/pipelines/github/gnuton/asuswrt-merlin.ng/1676/workflows/f26d80e9-7098-4b9c-92d2-bcb1258f37b6/jobs/5612 |
you can find the stable release for the current stable |
Router Model Affected
Models: (eg: DSL-AX82U/RT-AX82U/...)
RT-AX82U v2
Firmware Version Affected
3004.388.4_0-gnuton0_beta2
Is this bug present in upstream Merlin releases too?
No
Describe the bug
I cannot upload the firmware file to my router. All other files have the .w extension but this file does not, and for some reason the Beta 1 file is shown under Beta 2 aswell. I can select the file just fine on the firmware update page, but after the "flash" is done nothing has happened.
To Reproduce
Steps to reproduce the behavior:
Update firmware, nothing happens because probably wrong file extension/file.
Expected behavior
Firmware flashed successfully.
The text was updated successfully, but these errors were encountered: