Hey! I have problem with this switch. CPU Temp is about 68C. Fan fail. POE output 0 W. There is about 10 AP connected to it. All Works. Is this software bug? I run at 7.24.2 and fw is 6.41.3. Mybe I need to upgrade to 7.24.5 and upgrade fw to 7.24.2? My health print is this -
0 poe-out-consumption 0 W
1 cpu-temperature 66 C
2 fan-state fail
3 fan1-speed 0 RPM
4 fan2-speed 0 RPM
5 fan3-speed 0 RPM
6 fan4-speed 0 RPM
7 board-temperature1 56 C
8 board-temperature2 40 C
9 psu1-voltage 26.4 V
10 psu2-voltage 52.8 V
11 psu1-current 0 A
12 psu2-current 0 A
For one its called current firmware - meaning its firmware not a bootloader, so why call it RouterBOOT instead of current-bootloader?
Then its not even my fault at that point, and youre still wrong because what i said is still right whatever u say, its literally by the documentation definition of what to do with the versions and you just being a goblin correcting uhmmm akschually its akschually a bootloader akschually and still the same goes for the bootloader if the versions arent matched bootloader version can matter in specific compatibility scenarios
Bunch of rats on the forums grouping together even tho the original comment is more than correct
Why are you arguing with me about how MikroTik decided to call it?
Just don't spread shit information in this forum if you have no idea what you're talking about.
You literally come here and call people out on "technically correct" when the original statement is more than correct for the problem at hand, you're literally the nerd kid who says "UHM AKSCHUALLYY ITS NOT THIS ITS THAT" just because theres some little nuance corner case when it literally doesnt matter for the discussion at hand, actual 3rd grade ragebait.
Grow up.
And its not your first case, most of your reponses are half assed passive agressive garbage instead of trying to be helpful with all your knowledge that you have, its wild these days. Mic drop.
The only reason it h as nothing to do with the RouterOS is because its a whole separate thing its in RouterBOARD, when the package itself is under packages and its an os, the firmware in general is the translation layer between the hardware and software, so my whole argument is calling the RouterBOOT or the "bootloader" versions firmware is literally wrong.
And by what they address it as in the winbox "minimum or current -firmware" means its firmware and im calling it firmware and you can literally nothing do about it and its correct.
The problem is that no one knows how crucial the firmware for the rest of ROS is.
You can check old threads where Normis states that firmware could be out of sync of ROS.
On the other hand why they push out everytime a new firmware with each ROS revision. You never know if it includes code for new devices, corrections to the old ones. Just pure "magic".
The used name however suggest that firmware called RouterBOOT - as used during boot process - may manage software-hardware layer as it was just explained.
If not, then would be no need for such a layer, except the ability to run serial based terminal for recovery but then changing it each time would not have the sense also as it would be only a simple terminal/programmer set of funcionalities.
In PC world it used to be called BIOS, EFI, OpenBOOT, OpenFirmware
No matter what I would keep both modules in sync. Especially when something goes wrong.
, if people actually did read documentation, you would have half of the fun ...
its akschually 
) tells us to keep it in sync, and not so casually it gives no real reason for doing that.