On 27.01.20 17:14, Joe Ayers wrote:
You should report this bug under "openwrt-19.07":
https://bugs.openwrt.org/
You are apparently using ar71xx, did you try an ath79 19.07 image?
the first mikrotik device in ath79 was merged to master last week, so ath79 is
not an option here ATM.
Best
Adrian
Regards,
Baptiste
The devices with this issue aren't supported with Openwrt images yet
:) . Thus, submitting a defect may be problematic. I've added a
few definitions on top of the openwrt "Mikrotik LHG 5" to add support
(and hopefully I can find the time to submit an openwrt PR). There
are 3 devices with exact same motherboard "LHG 2nD" and same behavior
going from 18.06.2 to 19.07.0:
LDF 2nD
LHG 2nD
LHG 2nD-XL
I have narrowed down the problem. By removing "40_run_failsafe_hook",
procd completes as expected. Something seems to be triggering
failsafe mode and blocking procd. If anyone knows what might have
changed or where to fix the root cause, would appreciate any
information to save time. I'll dig a little more...
Joe AE6XE
I'm also a bit worried when seeing this:
[ 0.133043] ar71xx: invalid MDIO id 1
Koen
On 25-01-20, Joe Ayers wrote:
At http:\\arednmesh.org, we've had several mikrotik devices working,
all with "LHG" motherboards. One of the devices, RB LHG 2nD-XL no
longer boots with upgrade from 18.06.2 to 19.07.0. Other devices with
same "LHG" mother board continue to work fine, e.g. RB LHG 5nD-XL, LHG
5nDHP.
I'm stuck on getting this working, if you have any pointers, please
let me know. Here's dmesg where it hangs:
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
