Ultra 60 Dual Processor Question

[echurchm]

I have an Ultra 60 Dual 300 mhz machine. When I look in /proc/cpuinfo, it only shows 1 cpu as active. Does this mean that only 1 cpu is being used. If so how can I change this.

I followed the directions given on the site to perform the installation. The only part that was unclear was the compiler flags so I commented them all out.. Not sure if this was correct and causing my problem.

Any info would be greatly appreciated.

Ed

[Ferris]

1. What kernel are you using? I have an Untra2 dual processor, and if
I do 'uname -a', I get

Linux lacewing.inforead.com 2.4.20-sparc-r0 #3 SMP Fri Jan 3 15:56:09 UTC 2003 sparc64 sun4u TI UltraSparc II (BlackBird) GNU/Linux

So I am using a multiprocessor version (SMP) of 2.4.20. Make sure that
you are using an SMP kernel. Then, when you boot the system, you should
see fairly early on that the kernel is using both CPUs.

2. For CFLAGS in make.conf, I use
CFLAGS=-mcpu=v9 -mtune=v9 -O2 -pipe
Or look at the coments in 'make.conf'

[echurchm]

When I execute uname -a I get,

Linux linux.home.net 2.4.18 #1 Sun May 12 22:07:11 CEST 2002 sparc64 sun4u TI UltraSparc II (BlackBird) GNU/Linux.

I thought I compiled the kernel with SMP enabled. I have CONFIG_SMP=y.

I noticed your ouput had 2.4.20-sparc-r0. I'm assuming the -sparc-r0 means something. Did you download the linux kernel from some particular?

Now given I compiled my system with the wrong make.conf file, how do I recompile the entire system. Do I need to start from scratch with Fdisk.

Thanks Ed.

[Ferris]

1. As to the last question, no. All you need to do is make sure to boot an
SMP kernel. If you have one built with SMP=yes, you should be able
to test it by 'gzip -c vmlinux > /boot/vmliniz-4.2.20-SMP
(and I put 'cp System.map /boot/System.map-4.2.20-SMP)

Now, edit (if necessary) your 'silo.conf' file (mine is /boot/silo.conf;
it also might be /etc/silo.conf (?)) to contain lines that look like

# If /boot is a separate partition, remove /boot from the image path
# ((( which for me it is )))
image=/vmlinuz-2.4.20-SMP
label=gentoo
root=/dev/sdb4

(or root=/... for wherever you mount /)
reboot, and when you get the SILO: prompt, enter 'gentoo' in this
example. For me, this is the first entry in silo.conf, so just booting
the system does everything.)

If you started with a good 2.4.20 kernel from someplace and you like
the .configuration, all the rest should be optional.

If you have already done this, it might be as simple as specifying your
kernel of choice at 'SILO:' prompt.


2. I got the sources from GenToo: Go to /usr/portage/sys-kernel/sparc-sources
and
ebuild sparc-sources-2.4.20-r2.ebuild fetch unpack

3. Now, the kernel sources are correctly patched into
/var/tmp/portage/sparc-sources-2.4.20-r2/work/linux.....
(or something very like it in /var/tmp/portage)

3a. For consistency, I went to this directory (.../work) and did something
like 'find linux... -depth -print | cpio -pdvm /usr/src' because we want
the kernel source to live in /usr/src (with, say, 'ln -s linux... linux')

4. For, me, at that point I took my older '.config' file for ker 2.4.18,
the default arch/sparc64 configure file, and edited the old .config
to get a target for kernel-2.4.20

5. make ARCH=sparc64 oldconfig dep clean vmlinux modules
as in installation guide. The make process will possibly ask you some
questions.

6. If everything is OK, proceed as in item '1.' (and in install guide)
to put the compressed kernel into /boot/, fix up silo.conf,
do 'make modules_install'
7. Reboot, of course, to try the kernel.

At least, that worked for me. If you are lucky, maybe someone who
understands this better than I do will respond as well. I am just passing on something that I got to work.

Regards,
Ferris

[Ferris]

(And as you say, it's
CONFIG.SMP=y as well. My 'SMP=yes' should have said that.)