RB951 CPU freq.dropped from 400MHz to 360MHz after upg. 5.22

Recently when updated two of RB951-2n the CPU frequency dropped back to 360MHz. Tried downgrade to ROS 5.21 no effect. Only rollback to v5.20 returned 400MHz. Tested on two RB951-2n with Bootloader 2.41 and 3.0. Under v5.20 same boards shows 400MHz.
Screen Shot 2013-01-12 at 1.38.06 AM.png
Screen Shot 2013-01-11 at 9.56.11 PM.png

http://routerboard.com/RB951-2n

Says CPU speed is 300MHz.

Please read this:

http://forum.mikrotik.com/t/rb951-2n-default-cpu-speed/59763/1

Maybe with 360Mhz is more stable. Software fix in 5.22

Hallo frankie,

if you get a gift on top, that means your router will be able to run with higher speed, what you are crying then?
If they tell 300 MHz and you only will be able to switch it to 240 MHz, ok I have nothing said, but you are able to
switch the entire router to 360 MHz, this is even 60 MHz on top of this cpu speed!!! However where was the real
problem now?
So if they give or plain offer you something on top, please don´t be angry about to get something for free,
you should not be able to demand now 400 MHz, because they where never set this value as an official up
on their website!

Maybe with 360Mhz is more stable. Software fix in 5.22

Really good, I consider.

Perhaps also that the cpu was not so heavy loaded with IPv4 and now with IPv6 it is more
to do or plain handle out and the cpu could be able to overheating? Because there is many more to do for
and they had to narrowed down the MHz.

The AR7242-AH1A is the same chip that is in most of SXT, RB750GL, RB750, 711. They all runs @ 400MHz CPU Clock. Look at the AR7242-AH1A datasheet if you don’t believe me.
I’ve one RB433AH that has 512Mbyte Flash chip on board, all others has 128MB. Nice bonus, but really rare. I also know many routers based on AR9344 (same CPU is on RB2011) with underclocked CPU @560MHz. But my RB2011UAS-2HnD-IN tested @750MHz and working stable at 75-80% constant CPU load. So I don’t think that 400MHz clock is overheat or overload CPU in RB951-2n.
It think it is rather bug than rollback because of stability.

pic.jpg

Hello again,

It think it is rather bug than rollback because of stability.

For sure we well perhaps never know why, this is only and really knowing MikroTik it selfs.

But one think I want to know from you now, that is the following.
You were posting here a screen shot in and on the left side of the Recources monitor, we will be able to see
at the CPU frequency is at 400 MHz right now!!! And now I was thinking that you must at first change the CPU
back to 360 MHz or 240 MHz and then you are able to switch it back to 400 MHz can this be!?
In the other direction it will be not running! Because if the cpu is running at 400 MHz it should not be able to switch
the cpu to 400 MHz, this does not making many sense in my eyes.

Please be so friendly and try it out and switch to 360 MHz and then have a look on the settings section that is shown at the right side, so if you find now the 400 MHz setting you will be able to change the cpu clock back as you was expecting
it. Perhaps you were only in a so called thinking false!

We changed it to improve stability.

Because if you reset or load default config under ROS 5.21 and 5.22 you fallback to default 360Mhz and cannot select 400MHz again. Only Netinstall 5.20 or earlier version would allow to change to 400MHz again.

Maybe a line in changelog would be useful in future.

Why? Clearly no one is noticing it.

(We have had threads here over the ChangeLog for a long time already. As much as the MT is concerned the ChangeLog is incomplete by design and will remain so. Why it is so, it is a matter of opinions and views.)

Hello frankie,

Maybe a line in changelog would be useful in future.

What should they (MikroTik) write there in?

  • We give you 60MHz on top for free.
  • 60MHz for free this week, because you are our little sunshine.
  • You was paying for 300MHz only and 60MHz came on top, because we love you.

What are you talking about? I’m not sure I even understand where this came from.

I agree. A more detailed changelog would be great.