Hi,

I just installed Slackware as I did with 12.0. Means: I disabled all
huge kernels and their kernel modules and also disabled all smp kernels
as I only have one CPU and I know that my board causes a crash if I try
to boot with SMP kernel.

Now I rebooted and... *CRASH*

Nothing worked. No slackware boot.

Some hours later I saw that someone seems to have already copied an
huge-smp kernel to my /boot and symlinked this to /boot/vmlinuz.

I did *not* install any SMP and any HUGE kernel, so why the hell are
those silly files there?

I moved the links to where they should be, *DELETED* the silly huge
kernel, and now the system boots.

Why has Slackware 12.1 such silly kernel handling?

Thanks in advance

CU

Manuel

On 2008-05-15, Manuel Reimer <mreimer@expires-31-05-2008.news-group.org> wrote:
> Hi,
>
> I just installed Slackware as I did with 12.0. Means: I disabled all
> huge kernels and their kernel modules and also disabled all smp kernels
> as I only have one CPU and I know that my board causes a crash if I try
> to boot with SMP kernel.
>
> Now I rebooted and... *CRASH*
>
> Nothing worked. No slackware boot.
>
> Some hours later I saw that someone seems to have already copied an
> huge-smp kernel to my /boot and symlinked this to /boot/vmlinuz.
>
> I did *not* install any SMP and any HUGE kernel, so why the hell are
> those silly files there?
>
> I moved the links to where they should be, *DELETED* the silly huge
> kernel, and now the system boots.
>
> Why has Slackware 12.1 such silly kernel handling?
>
> Thanks in advance
>
> CU
>
> Manuel
>

You say "someone" installed the kernel? What kernel did you use during
installation?

Which kernel did you choose to install during the installation?
Did you use a different kernel other than the one for installation?

Sounds like the same question three times, but they really are three different
questions

-Matt

On 2008-05-15, Manuel Reimer <mreimer@expires-31-05-2008.news-group.org> wrote:

> I just installed Slackware as I did with 12.0. Means: I disabled all
> huge kernels and their kernel modules and also disabled all smp kernels
> as I only have one CPU and I know that my board causes a crash if I try
> to boot with SMP kernel.
>
> Now I rebooted and... *CRASH*
>
> Nothing worked. No slackware boot.
>
> Some hours later I saw that someone seems to have already copied an
> huge-smp kernel to my /boot and symlinked this to /boot/vmlinuz.
>
> I did *not* install any SMP and any HUGE kernel, so why the hell are
> those silly files there?
>
> I moved the links to where they should be, *DELETED* the silly huge
> kernel, and now the system boots.
>
> Why has Slackware 12.1 such silly kernel handling?


Here are the relevant post-install scripts:

kernel-generic-2.6.24.5-i486-2
( cd boot ; rm -rf vmlinuz )
( cd boot ; ln -sf vmlinuz-generic-2.6.24.5 vmlinuz )
( cd boot ; rm -rf System.map )
( cd boot ; ln -sf System.map-generic-2.6.24.5 System.map )
( cd boot ; rm -rf config )
( cd boot ; ln -sf config-generic-2.6.24.5 config )

kernel-generic-smp-2.6.24.5_smp-i686-2
( cd boot ; rm -rf vmlinuz )
( cd boot ; ln -sf vmlinuz-generic-smp-2.6.24.5-smp vmlinuz )
( cd boot ; rm -rf System.map )
( cd boot ; ln -sf System.map-generic-smp-2.6.24.5-smp System.map )
( cd boot ; rm -rf config )
( cd boot ; ln -sf config-generic-smp-2.6.24.5-smp config )

kernel-huge-2.6.24.5-i486-2
( cd boot ; rm -rf vmlinuz )
( cd boot ; ln -sf vmlinuz-huge-2.6.24.5 vmlinuz )
( cd boot ; rm -rf System.map )
( cd boot ; ln -sf System.map-huge-2.6.24.5 System.map )
( cd boot ; rm -rf config )
( cd boot ; ln -sf config-huge-2.6.24.5 config )

kernel-huge-smp-2.6.24.5_smp-i686-2
( cd boot ; rm -rf vmlinuz )
( cd boot ; ln -sf vmlinuz-huge-smp-2.6.24.5-smp vmlinuz )
( cd boot ; rm -rf System.map )
( cd boot ; ln -sf System.map-huge-smp-2.6.24.5-smp System.map )
( cd boot ; rm -rf config )
( cd boot ; ln -sf config-huge-smp-2.6.24.5-smp config )

In case you don't follow, the *only* way the vmlinuz symlink
would be pointing at one of the smp kernels is if you installed
one of the smp kernels. If you had only installed *one* kernel
package, then the symlink would be pointing at that kernel.

In a default full installation, the last kernel to be installed
is hugesmp.s, so the vmlinuz symlink will point to it. That is
a very sane default, because it will "just work" for the vast
majority of people. If/since you know you need something different,
and since you feel qualified to judge Slackware's kernel handling
as "silly" I would expect you to know that deviating from the
default configuration requires some changes to lilo.conf and/or
to the vmlinuz symlink.

-RW

On Thu, 15 May 2008 13:58:36 +0200, Manuel Reimer
<mreimer@expires-31-05-2008.news-group.org> wrote:

>Hi,
>
>I just installed Slackware as I did with 12.0. Means: I disabled all
>huge kernels and their kernel modules and also disabled all smp kernels
>as I only have one CPU and I know that my board causes a crash if I try
>to boot with SMP kernel.
>
>Now I rebooted and... *CRASH*
>
>Nothing worked. No slackware boot.
>
>Some hours later I saw that someone seems to have already copied an
>huge-smp kernel to my /boot and symlinked this to /boot/vmlinuz.
>
>I did *not* install any SMP and any HUGE kernel, so why the hell are
>those silly files there?
I asked the same question
ol0m24p7pk5uj2j34fkpkapu721a0o4670@4ax.com
The solution by Mike worked like a charm. You need it to
compile non-crashing modules. Apparently smp is built into various
environment values. The script removes these references.
FWIW
[]'s