On Tue, Nov 08, 2011 at 10:38:17PM -0500, Josh Luthman wrote:
> On Nov 8, 2011 8:40 PM, "Scott Lambert" <[email protected]> wrote:
> >
> > I have an RB493G which I upgraded to RouterOS 5.8 tonight. The first
> > one went good, this one had to be power cycled.
> >
> > It came up and looked good. So I upgraded the firmware to 2.37.
> > That went worse than the OS upgrade.
> >
> > It will no longer output anything on the serial console when trying
> > to boot.
> >
> > If I hit the secondary bootloader button, it will boot on power up.
> > Then the OS works fine.
>
> Sounds like a broken board to me, but I haven't seen that specific
> situation.
I found the issue:
lambert@MikroTik > /system routerboard settings print
baud-rate: 115200
boot-delay: 5s
boot-device: nand-if-fail-then-ethernet
enter-setup-on: any-key
cpu-frequency: (unknown)
boot-protocol: bootp
enable-jumper-reset: yes
force-backup-booter: no
silent-boot: yes
I set the cpu-frequency to 680MHz and tried the "/system routerboard
upgrade" again. It booted!!!
BTW, the other RB493G, brand new, which I upgraded last night was
running 4.14. I didn't pay enough attention to the firmware version
prior to upgrade. At some point I noticed it had the cpu-frequency
set to 100MHz. Someone mentioned that issue in the 5.8 release
thread on the MikroTik forum. Perhaps checking the routerboard
settings before a firmware upgrade is in order?
--
Scott Lambert KC5MLE Unix SysAdmin
[email protected]
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
