It seems RouterOS is unable to utilize the second core of this processor. Am I missing something? Is this a bug in the current version of RouterOS? Same server has no problem running CentOS and detecting both cores.
Yea its turned on in the Bios. If I boot into BARTPE, VistaPE, or CentOS it shows both cores, but RouterOS 3.4 does not. You’d think I wouldn’t have this problem with a 965 Chipset and Intel processor
I did open a ticket wtih a supout.rif, we’ll see if they have any comments.
Thanks Travis, the E6400 is an older Conroe design, the E4600 replaced the E6400 as the new Allendale design. Its also very likely you are running a difference chipset, I’m running the Q965 Express chipset.
Vista clearly sees and uses both cores, so it looks like there is a bug in RouterOS with the Q965 Express chipset or at least this particular Intel DQ965GFEKR motherboard design.
Well after waiting 3 days for a reply from Mikrotik support, they tell me to set multi-cpu = yes, I guess they didn’t bother to read my email or my supout.rif file because I clearly had already set that and rebooted!
The two identical routers I built have the identical problem, yet I can throw a hard drive in each one with CentOS 5.1 or Vista on it and both cores are operating just fine.
More elaborate answer - the new 3.5 includes a new kernel version. If the problem is in the kernel, maybe it’s fixed now. If not - we can’t do anything
Well unfortunately both 3.5 and 3.6 fail to boot into Mikrotik. Uncompresses kernel and just sits there. I booted these servers off NetInstall and did fresh new installs of 3.6 and 3.5, neither work, did a fresh install of 3.4 and it boots again. Since these are fresh installs multi-cpu is off. Changing bios setting for Multi Core makes no difference, still doesn’t allow 3.5 and 3.6 to boot.
This system is unable to boot with multi-cpu=yes, if I wipe it clean and use the default multi-cpu=no, 3.7 will boot. If I then enable multi-cpu=yes and reboot, it will freeze at
