RouterOS 3.5, 3.6 and 3.7 on Intel Pentium M boot error

RouterOS General
1

Hello,

RouterOS 3.5, 3.6 and 3.7 on Intel Pentium M 1.6GHz boot error message below:

Loading system with initrd
This kernel requires the following features not present on the CPU:
0:6
Unable to boot - please use a kernel appropriate for your CPU.

RouterOS 3.4 is OK on this CPU.

2

This error message on VMware.

3

Same problem here! Any solution? :open_mouth:

4

I heard from MT support yesterday that a Pentium-M fix for their kernel is already finished and will be included in 3.8. :slight_smile: w00t. :slight_smile:

– Nathan

5

so all the problems are in VMWare?

6

No, I don’t think so…I tried to boot mine on a genuine 1.5GHz Pentium-M system, not VMware, and got the error described in the first post on this thread. I did some Googling around on it and it sounded like the problem was that compiling the Linux kernel with certain Pentium 4 optimizations would seemingly prevent the same kernel from working on Pentium-M, or at least that was the consensus reached in the discussions I found on the issue. MikroTik support didn’t actually tell me what the problem really was or what solution they came up with, only that it is now fixed. :slight_smile:

My guess would be (?) that the VMware issue experienced by others is probably similar, and hopefully their issues will also be solved by the new kernel build in 3.8 as well. Interestingly, I have booted 3.7 within VMware Server 1.0 and didn’t have any problems doing so (but then again the host machine for the VMware session wasn’t a Pentium-M either).

– Nathan

7

we have never before seen a problem with pentium m. if this is something that can be reproduced on any M system, contact support please

8

Normis,

I’m not sure how, but you somehow completely misunderstood me. Go back and read my posts more closely. :slight_smile:

I already contacted support BEFORE I posted here, and they told me that they HAVE seen the problem with Pentium M, and they had already fixed it for 3.8. I guess that they forgot to tell you this. :slight_smile: You can look up the ticket yourself: 2008042366000133

I wasn’t reporting the problem here on the forums. Instead, I was letting everyone else who was having the same problem know that a fix is already on the way! I figured that the people who started this thread might be happy to hear this. So chill. :slight_smile:

Thanks,

– Nathan

9

I’ll thank this person for sharing this with everyone else :confused: