[OpenWrt-Devel] newer mikrotik boards not booting?

Joe Ayers joe at ayerscasa.com
Sun Jun 14 15:11:04 EDT 2020


> > Anyone else seeing this on recently purchased  Mikrotik models?
> > Installing openwrt 19.07.03 on a Mikrotik LHG 5 boots, initfs and
> > appears to succeed with sysupgrade.  Then the device is in an infinite
> > boot loop.   It appears there's no console configured in routerboot to
> > see what it is doing.  Any pointers to turn on?
> Is it the same with 19.07.2 or 19.07.1? Just to make sure it's not a
> regression in OpenWrt.

19.07.3 and 19.07.2 have the same behavior -- after flashing, infinite
boot loop.

> > Note, I'm working with another individual seeing this on a new LHG 5
> > model device.  I have reproduced and tested on a newly purchased SXTsq
> > 5HPnD, which has a motherboard labeled "LHG 5HPnD".   Prior SXTsq
> > 5HPnD  and LHG 5HPnD models  have been working fine.
>
> When you boot via TFTP, can you check whether the dmesg lines "Kernel
> command line" are the same on older and newer devices?
>

not working -- new device,  openwrt image, 19.07.2, from initramfs boot:

[    0.000000] Kernel command line: no-uart no-nand parts=1
boot_part_size=16777216 gpio=228923 HZ=300000000 mem=64M
kmac=74:4D:28:6A:28:F4 board=lhg hw_opt=00284001 boot=0 mlc=11
console=ttyS0,115200 rootfstype=squashfs noinitrd

not working -- new device, openwrt image, 19.07.3, from initramfs boot:

[    0.000000] Kernel command line: no-uart no-nand parts=1
boot_part_size=16777216 gpio=228923 HZ=300000000 mem=64M
kmac=74:4D:28:6A:28:F4 board=lhg hw_opt=00284001 boot=0 mlc=11
console=ttyS0,115200 rootfstype=squashfs noinitrd

Yes, working -- older LHG 5HPnD device, AREDN image based on 19.07.2,
flashed image boot (I don't have this device in hand to flash openwrt
image directly):

[    0.000000] Kernel command line: no-uart no-buzzer no-nand parts=1
boot_part_size=16777216 gpio=261675 HZ=300000000 mem=64M
kmac=64:D1:54:93:9E:A2 board=lhg ver=3.41 hw_opt=00284001 boot=1
mlc=11 console=ttyS0,115200 rootfstype=squashfs noinitrd

> > sysupgrade log:
> >
> > Commencing upgrade. Closing all shell sessions.
> > Watchdog handover: fd=3
> > - watchdog -
> > Sending TERM to remaining processes ... crond uhttpd xinetd sh dnsmasq
> > sh ntpd netifd hostapd [  146.589174] device wlan0 left promiscuouse
> > [  146.593957] br-lan: port 2(wlan0) entered disabled state
> > sleep sleep ubusd urngd logd rpcd
> > Sending KILL to remaining processes ...
> > /lib/upgrade/stage2: line 126: [-x: not found
>
> This last line does not look good, but I can't locate it in the source
> code :(
>

I can't reproduce, not sure what this error was all about.   Suggest
we ignore, unless further occurrences.

19.07.2 sysupgrade on new device.   From cpuinfo, "MikroTik
RouterBOARD SXTsq 5HPnD", with motherboard label "LHG 5HPnD":

root at OpenWrt:/tmp# sysupgrade -n -F
openwrt-19.07.2-ar71xx-mikrotik-rb-nor-flash-16M-squashfs-sysupgrade.bin
Device unknown not supported by this image
Supported devices: rb-750-r2 rb-750up-r2 rb-750p-pbr2 rb-911-2hn
rb-911-5hn rb-931-2nd rb-941-2nd rb-951ui-2nd rb-952ui-5ac2nd
rb-962uigs-5hact2hnt rb-lhg-5nd rb-map-2nd rb-mapl-2nd rb-wap-2nd
rb-wapr-2nd rb-sxt-2nd-r3
Sysupgrade is not yet supported on unknown.
Image check failed but --force given - will update anyway!
Commencing upgrade. Closing all shell sessions.
Watchdog handover: fd=3
- watchdog -
killall: telnetd: no process killed
Sending TERM to remaining processes ... netifd odhcpd uhttpd ntpd
dnsmasq ubusd urngd logd rpcd
Sending KILL to remaining processes ...
Performing system upgrade...
Unlocking firmware ...

Writing from <stdin> to firmware ...
Upgrade completed
Rebooting system...
umount: can't unmount /dev: Resource busy
umount: can't unmount /tmp: Resource busy
umount: can't unmount /: Invalid argument
[ 1082.724168] reboot: Restarting system

19.07.3 sysupgrade on new device.   From cpuinfo, "MikroTik
RouterBOARD SXTsq 5HPnD", with motherboard label "LHG 5HPnD":

root at OpenWrt:/tmp# sysupgrade -n -F
openwrt-19.07.3-ar71xx-mikrotik-rb-nor-flash-16M-squashfs-sysupgrade.bin
Device unknown not supported by this image
Supported devices: rb-750-r2 rb-750up-r2 rb-750p-pbr2 rb-911-2hn
rb-911-5hn rb-931-2nd rb-941-2nd rb-951ui-2nd rb-952ui-5ac2nd
rb-962uigs-5hact2hnt rb-lhg-5nd rb-map-2nd rb-mapl-2nd rb-wap-2nd
rb-wapr-2nd rb-sxt-2nd-r3
Sysupgrade is not yet supported on unknown.
Image check failed but --force given - will update anyway!
Commencing upgrade. Closing all shell sessions.
Watchdog handover: fd=3
- watchdog -
killall: telnetd: no process killed
Sending TERM to remaining processes ... netifd odhcpd uhttpd ntpd
dnsmasq ubusd urngd logd rpcd
Sending KILL to remaining processes ...
Performing system upgrade...
Unlocking firmware ...

Writing from <stdin> to firmware ...
Upgrade completed
Rebooting system...
umount: can't unmount /dev: Resource busy
umount: can't unmount /tmp: Resource busy
umount: can't unmount /: Invalid argument
[  304.564494] Removing MTD device #1 (hard_config) with use count 1
[  304.571849] reboot: Restarting system

Same result with 19.07.2 and 19.07.3,  device in infinite boot loop.

Joe AE6XE

_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel



More information about the openwrt-devel mailing list