Topic: Dual CPU Support in SME Server

[gtoseski]

Have an old PII Proliant Server running SME Server 6.0.1-01, just wondering does it support (SMB) dual CPU, is there something i need to do? I really want to take advantage of the hardware i am using.
Thankyou

[dmac]

I have installed SEM 6.0.1 Custom on a Dell PowerEdge with Dual PII 350's and it has been working as a gateway for the last two years without a hitch.  SME should recognize the dual processors and load the appropriate modules.  You will have a prompt at startup if you watch the screen.

[flaviove]

If you need info about cpu´s you can try that
"[user@machine]#cat /proc/cpuinfo".

[gtoseski]

where do i type that command,
i have looked at my logs and it only shows "initializing CPU#0"
does not mention the 2nd CPU anywhere

[flaviove]

Just login on your SMEserver box as a root and type it on the command line prompt(cat /proc/cpuinfo)
You can do that too.
type: cd /proc <enter>
type: cat cpuinfo <enter>

[Smitro]

Don't forget when you start up the server, when you see the splash screen select SME SMP and not SME UP. This will enable SMP (Symmetric Multi-Processing). You only have to do it once and it will remember it next time.

[gtoseski]

The SMP at the startup did the trick and also the cpuinfo!!!, thank you so much for all the help,
This SME Server is really growing on me!!

[gtoseski]

Unfortunately when i reboot, it does not remember the 2nd CPU,
i have to select the SMP part to boot or it will only boot into 1 CPU
any suggestions?

[gtoseski]

Unfortunately when i reboot, it does not remember the 2nd CPU,
i have to select the SMP part to boot or it will only boot into 1 CPU
any suggestions?

[Smitro]

are you sure? did you shut the machine down properly and then bring it back up?

[gtoseski]

I use the shutdown that is in the admin concole, also i have tried in the web admin.
i have tried in the promt

the command, shutdown -g0

i hope that is the right command, i use the shutdwon command in SCO UNIX

[brewstate]

I checked out the cpuinfo file and it says siblings 1 that is the only thing that I could see that may show more than one cpu. Also tops doesn't really show 2 processors, is that normal? (you may properly assume that I booted in smp mode and have read the previos posts to this thread).  Thank you.

[kruhm]

-edit /etc/lilo.conf
-change "default = SMEServer-up" to "default = SMEServer-smp"
-/sbin/e-smith/expand-template /etc/lilo.conf
-lilo
-/sbin/e-smith/signal-event reboot

[Denbert]

Hi,

I’m trying to setup a new server with SMP.

My mobo is an ASUS A7M266-D and two Athlon 2400 MP processors.

Installing SME 6.0.1 runs fine and I choose SME SMP at bootup, but message log says:

“kernel: SMP motherboard not detected.”

Then I tried upgrading the installation to SME 7.beta5 and got this great message in my log:

“kernel: Total of 2 processors activated (7929.85 BogoMIPS).”

Anyone got a suggestion – I can use it now, but hey, there are two processors in the server, why not use them both

[mrjhb3]

Unfortunately when i reboot, it does not remember the 2nd CPU,
i have to select the SMP part to boot or it will only boot into 1 CPU
any suggestions?

Please try this fix

cd /etc/e-smith/templates/etc/lilo.conf

cp 30labels /root - just in case you need to revert back to it.

pico -w 30labels

add this line:

s/default=SMEServer.*/default=$kernel/;

above this line:

$_ } @preamble;


then do

/sbin/e-smith/config show lilo

If your DefaultKernel is set to SMEServer-up then do:

/sbin/e-smith/config setprop lilo DefaultKernel SMEServer-smp

/sbin/e-smith/expand-template /etc/lilo.conf

/sbin/lilo

You should see an * by the SMP version.

reboot - shutdown -r now

Watch the splash screen on reboot and you should see the SMP version selected.  If you can't be at the server console, then after the server is back up do a cat /proc/cmdline while logged in as root and you should be able to determine what kernel version was booted.  

I have tried to thoroughly test this fix on 6.0.1, but am not in a position to update the bug report yet.  The only thing that needs changing to fix this is the update to 30labels.  There are other events that run to change lilo.conf and update lilo if a new kernel is chosen.

Let me know if this does indeed fix this for you.

JB