Prev: What will Slack 13 give me that Slack 11 doesn't have?
Next: Slackware 13
From: Douglas Mayne on 14 Oct 2009 10:01
On Wed, 14 Oct 2009 04:58:04 -0700, vtcodger wrote:

> On Oct 13, 10:09�am, Ed Wilson <ewil...(a)jackmaxton.com> wrote:
>> vtcodger wrote:
>> > I have seen assertions that there is a README.txt file that
>> > explains how to modify the source for non-SMP but I can't find the
>> > file. Is it a myth?
>>
>> slackware/slackware-12.1/source/k/README.TXT
>>
>> --
>> Ed
>
> Thanks Ed, but that seems to be the README for upgrading Slackware
> 12.1 to 12.2 which I'd prefer not to do because stuff always breaks on
> upgrades, and I have more than enough problems in my todo list at the
> moment.
>
> What I'm looking for is a different README that I think probably
> exists somewhere. Let me frame my question differently.
>
> 1. It is definitely true that Slackware 12.1 has several different
> precompiled kernel options, e.g. huge, SMP, non-SMP. Is it also true
> that there is only one set of kernel source code in the repositories
> -- /shr/pkg/kqemu/kernel-source-2.6.24.5_smp-noarch-2.tgz ?
>
> I think that the answer to that is "yes"
>
<snip>
>
To reiterate, this file:
<mirror>://slackware/slackware-12.1/source/k/README.TXT

has the instructions. Paraphrasing the instructions there:

If you are compiling kernel modules outside of the linux source (vmware,
qemu, virtualbox, etc.) for a non-smp kernel, then you will need to
recompile the kernel (bzImage) at least once. The kernel source has the
appropriate config:

<mirror>://slackware/slackware-12.1/source/k/config-generic-2.6.24.5

Refer to the file for the complete instructions. I posted this mainly to
add this information:

1. AFAIK, the VIA C7 will work with an SMP kernel. The above instructions
are not really needed for that CPU.

2. The VIA C7 is specifically supported by the Linux kernel. If you are
going to all of the trouble of recompiling your kernel, then this a chance
to optimize it for VIA C7.

3. IMO, the Linux kernel versions 2.6.2x has some performance issues
(AIUI, this relates to its block IO elevator code, SLAB/SLUB, etc.).
Under certain conditions, I noticed very poor performance when running
virtualization apps. YMMV. This appears to be much improved under kernel
2.6.3x. YMMV.

Finally, I am not sure that a single VIA C7 has the horsepower for running
virtualization. YMMV.

--
Douglas Mayne
From: Henrik Carlqvist on 14 Oct 2009 13:30
vtcodger <donald.kenney(a)gmail.com> wrote:
> 4. Where is the information on how to compile 12.1 modules for a non-
> SMP kernel? I need it because I am far too old and stupid to work it
> out for myself.

Assuming that you have installed a non-SMP or any other custom kernel
which affects module compability you should do something like the
following:

cp /boot/config /usr/src/linux/.config
cd /usr/src/linux
make modules
make modules_install

The above also assumes that /boot/config contains the configurations for
your custom kernel.

Please note however that this only rebuilds the modules that are part of
the linux kernel source tree. If you have other modules installed like
drivers for audio or video or kqemu which didn't come from the kernel
sources you will also have to recompile those modules. Depending on your
version of Slackware some of those sources might be part of X.org or alsa.
Some of those modules like kqemu or a binary nVidia driver might not be
part of Slackware at all.

Instead of working in /usr/src/linux you can make a copy of that directory
tree to somewhere else and build your modules there. By doing that you
don't need to be root when doing "make modules", only when doing "make
modules_install". However, having the right /usr/src/linux/.config might
be a good idea when compiling other modules like kqemu.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

From: vtcodger on 15 Oct 2009 03:55
Thank you very much gentlemen. With all that information, I'll either
solve the problem or I'm not going to solve the problem. Due to some
family plans that have gone seriously awry, I probably won't get to
work on this for three or four days. It appears that I will be
spending the next few days admiring autumn foilage while I shuttle
people and dogs from the Champlain Valley to and from Southern New
England.
From: Eef Hartman on 15 Oct 2009 04:31
Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote:
> vtcodger <donald.kenney(a)gmail.com> wrote:
> cp /boot/config /usr/src/linux/.config
> cd /usr/src/linux

You should do "make oldconfig" after that, to create all the right
dependencies for the changed config.

> make modules
> make modules_install

And according to Pat's README, you should also build a complete
kernel, with
make bzImage
make clean
rm .version

before you can build modules for that kernel.
--
*******************************************************************
** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-278 82525 **
*******************************************************************
From: Eef Hartman on 15 Oct 2009 04:33
Martin Schmitz <news(a)rmz.ath.cx> wrote:
> -rwxr-xr-x 1 root root 1816 2009-08-18 23:58 patch-to-non-smp.sh*

That one isn't there yet in 12.1, so you'll have to do it by hand.
--
*******************************************************************
** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-278 82525 **
*******************************************************************
First  |  Prev  | 
Pages: 1 2
Prev: What will Slack 13 give me that Slack 11 doesn't have?
Next: Slackware 13