Re: which kernel for dual opteron ???
Hi Adam:
I extrapolate your indications to my case (hope to the benefit of others too)
of installed debian 64 testing from etch beta 2 release, choosing
linux-image-2.6.15-1-amd64-generic.
Hardware: TWO 264 amd64-opteron on Tyan K8WE 2895 plus video card and scsi
card for external scsi chain composed of hd, CD, and scanner ; plus TWO hd
in raid1 from debian. All that functioning.
Aim: to have a worksation for crunching numbers, i.e. no gui, no sound, but
equipper for X with a flexible window manager like mwm. At present it is twm
and nothing else is offered. When all ok, i have to compile some special
applications in OpenGL as pre-computation. Finally, computations with mpqc,
already available for debian unstable 64.
Question: should I compile kernel from the present situation or it should be
better replace before that actual kernel with a smp kernel (or it is
immaterial)?
Additional question: should hardware change, like additional ram, etc, I guess
that the kernel has to be recompiled. True?
Thanks a lot. I am no expert in computer science, just user who is looking for
the highes floating point he can afford.
francesco pietra
On Wednesday 31 May 2006 16:17, Adam Stiles wrote:
> On Wednesday 31 May 2006 14:06, helices wrote:
> > > >WHICH kernel will make best use of my system?
> > >
> > > Of those listed, kernel-image-2.6.8-12-amd64-k8-smp. But you probably
> > > don't want any of those listed.
> >
> > <snip />
> >
> > OK, I'll bite. WHICH kernel do you recommend? WHY?
>
> The best kernel for your system is always one you have compiled yourself.
>
> Get yourself some kernel sources from kernel.org, the .config file for the
> kernel you are currently using, and the output of lsmod. Do `make
> oldconfig` {which will ask you a series of questions about any new features
> that were not in the kernel version to which your existing .config applies;
> you may as well just accept the defaults} and then `make menuconfig`.
> Enable SMP, hard-compile in any modules you want to be hard-compiled in,
> and disable drivers for any hardware you know you haven't got and aren't
> going to get in future.
>
> After that you can compile your kernel with make-kpkg and install it.
> Don't forget to run /sbin/lilo if you are using that, or whatever the
> alternative is if you are using grub.
>
> The worst you can do if you mess up is cause your system to need booting
> from a CD. Then you'll have to mount your system, chroot in and sort out
> the bootloader configuration. It sounds a lot more painful than it really
> is.
>
> Final piece of advice: if you're running apache2 and PHP on a box with
> multiple processors, make even surer than usual to use the "prefork"
> version!
>
> --
> AJS
Reply to: