[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Installing SMP kernel



Hi,

I just installed Debian on the xserve I've been battling with for the last few days, foregoing raid support and such. I used "install-power4" which installs the package kernel-image-2.6.8-power4. I want to enable smp in the kernel so I installed kernel-image-2.6.8-power4-smp, ran yabootconfig which didn't ask me what kernel I wanted to use (and I'm assuming it is not its job to do that) which nets me this in /etc/yaboot.conf:

## yaboot.conf generated by yabootconfig 1.0.8
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ

boot=/dev/sda2
device=/ht@0,f2000000/pci@7/k2-sata-root@c/k2-sata@0/disk@0:
partition=3
root=/dev/sda3
timeout=30
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot

image=/boot/vmlinux
        label=Linux
        read-only
        initrd=/boot/initrd.img
        initrd-size=8192
--

Am I correct in assuming that I can edit this file so it looks like this:

## yaboot.conf generated by yabootconfig 1.0.8
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ

boot=/dev/sda2
device=/ht@0,f2000000/pci@7/k2-sata-root@c/k2-sata@0/disk@0:
partition=3
root=/dev/sda3
timeout=30
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot

image=/boot/vmlinux-2.6.8-power4-smp
        label=Linux
        read-only
        initrd=/boot/initrd.img-2.6.8-power4-smp
        initrd-size=8192
--

And restart?

The boot directory looks like this:
box:/boot# ls -l
-rw-r--r--   1 root root   39522 2005-01-08 17:21 config-2.6.8-power4
-rw-r--r-- 1 root root 39251 2005-01-08 17:21 config-2.6.8-power4-smp
-rw-r--r--   1 root root    1024 2005-01-05 12:06 first.b
lrwxr-xr-x 1 root root 27 2005-02-23 15:57 initrd.img -> initrd.img-2.6.8-power4-smp -rw-r--r-- 1 root root 4820992 2005-02-23 11:13 initrd.img-2.6.8-power4 -rw-r--r-- 1 root root 5046272 2005-02-23 15:57 initrd.img-2.6.8-power4-smp lrwxr-xr-x 1 root root 23 2005-02-23 11:13 initrd.img.old -> initrd.img-2.6.8-power4
-rw-r--r--   1 root root   45328 2005-01-05 12:06 second.b
-rw-r--r-- 1 root root 935380 2005-01-08 23:47 System.map-2.6.8-power4 -rw-r--r-- 1 root root 963240 2005-01-08 23:50 System.map-2.6.8-power4-smp lrwxr-xr-x 1 root root 24 2005-02-23 15:57 vmlinux -> vmlinux-2.6.8-power4-smp
-rw-r--r--   1 root root 3941828 2005-01-08 23:47 vmlinux-2.6.8-power4
-rw-r--r-- 1 root root 4227776 2005-01-08 23:50 vmlinux-2.6.8-power4-smp lrwxr-xr-x 1 root root 20 2005-02-23 11:13 vmlinux.old -> vmlinux-2.6.8-power4

The reason I ask is that after running the yabootconfig initrd.img is now a symlink to initrd.img-2.6.8-power4-smp; yabootconfig seems to have updated the files for me but last time I tried this (a couple of days ago) I was left with an unusable machine after reboot.

Which way should I go with; yabootconfig or my custom editing? Are both wrong?

A.



Reply to: