littleking

[Log in to get rid of this advertisement]

i am having one heck of a time enabling SMP in the kernel on slackware 10, anyone able to give me a hand?

i have following the SMP how-to along with the kernel compiling newbie guide. every time i reboot after compiling i get a kernel panic, anyone able to help?

trey85stang

you should only have to make one change in the kernel config.. then recompile following the guides...

what is the message you get with the kernel panic? is it a mounting issue.. etc??

EDIT.. is this 2.6.7 or 2.4.26?

guzzi

just as trey85stang said, the kernel would be nice to know.

I have been through the same problem, the kernel panic I got was due to me not placing the bzImage in /boot and using the same name in /etc/lilo.conf.

Also, when you boot, do you see more than one Tux at the top of your screen? If so, the number of Tux images you see is the number of CPU's that are running. These will appear before most things can cause a kernel panic. What I mean to say, you will know at initial boot if you did good on your SMP setup, even if you do get a kernel panic later in the boot process.

Glad it isn't just me that has these problems.

littleking

2.4.26 as for the error i'll have to recompile to get the error again. i believe it was something to the effect of "unable to mout root" ro something or other. basically what im doing is trying to enable SMP using the raid.s kernel on an ibm x345...

are there any step by step instructions on how to do this? the smp-howto seems kind of outdated and hard to follow. also it seems that when i reboot after compiling that all my drivers are no longer detected.


sorry for sounding like a noob, just never been able to get a successful kernel recompile and i dont want to have to use redhat just because it has a "built-in" smp kernel.

guzzi

littleking I have had the exact same problems.

To get SMP going I used guides from the world famous Linux Questions then adjusted to what is in this post.

I have not used the raid.s kernel, only speakup.s and adaptec.s. You may want to compare the .config files associated with these to see what the differances are.

With adaptec.s this is how I do it with 2.4.26

This is all done in /usr/src/linux

with an original .config from the CDROM or the installation if it is unmodified, I run
make menuconfig
in Processor Type and Features
Pentium4 (I have dual Xeons)
HIGHMEM = 4 gig (have 1 gig, but less is used if this option is not selected)
math emulation (I do it because ?)
MTTR = y
SMP = y
General Setup
No Power Management Support
ACPI = y (without this you get 2 CPU's)
ACPI Support (from memory, I get kernel panic without this)
Config ACPI =y
CONFIG ACPI HT Only = y
Character Devices
Enhanced Real Time Clock
SCSI Support (also I get kernel panic without this)
make anything to do with aic7xxx built into the kernel (have dual SCSI ctrls)

now edit Makefile so that the line EXTRAVERSION is unique
whatever you place in this line will be the name of the modules created in the install_makemodules operation. If this isn't done, the new modules will have the same name as the old, and may/will cause kernel panic.

On a stock 2.4.26 Makefile Makefile will look like this
VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 26
EXTRAVERSION =

may I suggest that EXTRAVERSION = SMP.

make dep
make bzImage
make modules
make modules_install

cp /usr/src/linux/arch/i386/boot/bzImage /boot/whatever_name (this needs to be unique in /boot)

fix /etc/lilo.conf so that the name given to the kernel (whatever_name) is set like the following
image = /boot/whatever_name
root = /dev/sdb3 (this is where my / is at.)
label = make_up_a_name_that_will_show_up_in_the_lilo_boot_screen
read-only


run the command /sbin/lilo which will set the modifications to lilo.conf

reboot and there you are.

littleking

thanks! ill give it a shot!

MS-outLINUX-in!

Tried this manual, and also http://www.linuxquestions.org/questi...threadid=49035 , but had no luck...
The newcompiled kernel does not recognize scsi! During installation selecting adaptec.s kernel makes the scsi work, but have only one processor operational. Have tried to install a pure ide system, but the ide disk is too small - i use it only to boot the kernel.
How do I make the kernel to get the scsi driver to run?
Have a server machine to experiment here, can try out lots of ways...

guzzi

I to have had that problem. It was fixed in my case by compiling into the kernel anything that had to do with the SCSI controllers. If my SCSI controllers were put in as modules, it would kernel panic.

There are ways around putting the SCSI stuff into the kernel, but it is a little more work, which I dislike.

ADS

Are you copying the correct .config file to the kernel directory? If you don't do that, you're compiling the stock .config, which doesn't have a lot of drivers/modules that are included in the slackware .config.