XM-v5.5.build12536 - NO
XM-v5.3.5.build11245 - NO
XM-v5.3.3.build9634 - NO
XM-v5.3.2.build8909 - NO
XM-v5.3.build7782 - NO
XM-v5.2.build5132 - I couldn't even install this
XM-v5.1.build3635 - I couldn't even install this
i am having the same problem after updating to air os 5.5 maybe somenthing changed. Now i can not flash any ddwrt into my loco m2, even if i flash 5.3.5 still cant flash ddwrt into it.
i am having the same problem after updating to air os 5.5 maybe somenthing changed. Now i can not flash any ddwrt into my loco m2, even if i flash 5.3.5 still cant flash ddwrt into it.
You could flash this specific loco m2 with dd-wrt before you updated to AirOS 5.5 ? _________________ Kernel panic: Aiee, killing interrupt handler!
I'd test that for you if I had another device here.
LOM, my reason for switching to DD-WRT for this particular device/customer is the fact that I need to make this Bullet a WiFi repeater.
The customer has a DLink DSL Modem/Router and he wants me to take that router's WiFi signal and repeat it outside the house using the Bullet M2.
Do you think I can accomplish that with DD-WRT?
I thought I'd ask just to make sure I'm going in the right direction.
i am having the same problem after updating to air os 5.5 maybe somenthing changed. Now i can not flash any ddwrt into my loco m2, even if i flash 5.3.5 still cant flash ddwrt into it.
You could flash this specific loco m2 with dd-wrt before you updated to AirOS 5.5 ?
yes, several ,last was 17201, but repeater mode was not working with wep encription and sash told me i needed to uppdate , thats why i udated to airos 5.5....
I'd test that for you if I had another device here.
LOM, my reason for switching to DD-WRT for this particular device/customer is the fact that I need to make this Bullet a WiFi repeater.
The customer has a DLink DSL Modem/Router and he wants me to take that router's WiFi signal and repeat it outside the house using the Bullet M2.
Do you think I can accomplish that with DD-WRT?
I thought I'd ask just to make sure I'm going in the right direction.
i use to do that with my loco m2. not sure about your bullet, but should be the same thing.
It looks like 5.5 changes the bootloader permanently.
Yes, I strongly suspect that once one has upgraded to 5.5 build 12536 then one is stuck with a boot loader that can only flash firmware part of an upgrade and not the boot loader part.
Downgrading to an earlier AirOS build doesn't help - the boot loader remains the same and I'd say that Ubiquiti has painted themselves into a corner with this.
I have disassembled the boot loader from 12536 as I have done with many other u-boot from other mfgrs, and I have nerver seen so much bugs at the the same time not even in the very early u-boot for Atheros.
I'm surprised that a compiler/linker has been able to generate this pure crap code without throwing a lot of errors.
It is soo bad that I couldn't believe it, I had to download the 12536 build once again because I thought there must had been something wrong with my first download of it.
There wasn't anything wrong with the download.. _________________ Kernel panic: Aiee, killing interrupt handler!
I don't know the differences between OpenWRT and dd-wrt so I can't say, I would need a serial log showing what goes wrong.
I'll see if I can narrow it down based on the number of LED's that are turned on, Ubiquiti uses them to show boot progress. _________________ Kernel panic: Aiee, killing interrupt handler!