How do I install Slackware 11 with the 2.6.17.13 kernel?
olddru...@gmail.com
more support for my mobo hardware, but I'm not sure how to do it. Is
there something I type in at boot, or an option in the install I may
have missed?
Two Ravens
As far as I can remember one installs with the kernel one chooses from the
boot options, or uses the kernel provided and then makes a choice later in
the installation process, its been awhile since I made an install. To the
best of my recollection one has both options open.
--
Two Ravens
"...hit the squirrel..."
Roel Kluin
> I want to setup Slackware 11 with the 2.6.17.13 kernel, since it has
> more support for my mobo hardware, but I'm not sure how to do it.
2.6.17.13 is in the .../extra/linux-2.6.17.13/ directory. That is on
your dvd or if you use cds, either 2 or 3. You can install the packages
using kpackage, or from the commandline using 'installpkg <packagename>'.
you need to be root for that.
Install the following packages from that
directory: kernel-generic-2.6.17.13-i486-1.tgz
kernel-modules-2.6.17.13-i486-1.tgz
kernel-source-2.6.17.13-noarch-1.tgz
don't install the headers (see the kernel-headers.WARNING). You may have
to adapt your /etc/lilo.conf file and run lilo afterwards if you use the
lilo bootmanager, (adapt /boot/grub/menu.lst if you use grub). Maybe the
slackbuild script already does that; I'm not sure.
Or to compile from source, see:
http://www.slackbook.org/html/system-configuration-kernel.html
Two Ravens
> On Sat, 03 Feb 2007 09:07:17 -0800, olddrunkninja wrote:
>
>> I want to setup Slackware 11 with the 2.6.17.13 kernel, since it has
>> more support for my mobo hardware, but I'm not sure how to do it.
>
> 2.6.17.13 is in the .../extra/linux-2.6.17.13/ directory.
<snip>
I'm glad that someone was there to catch my incompetence.
Eef Hartman
> On Sat, 03 Feb 2007 09:07:17 -0800, olddrunkninja wrote:
> 2.6.17.13 is in the .../extra/linux-2.6.17.13/ directory. That is on
> your dvd or if you use cds, either 2 or 3. You can install the packages
Actually: CD 4 (source disk 1), it didn't fit on CD 3 anymore.
> don't install the headers (see the kernel-headers.WARNING).
And see also this text in the ChangeLog:
extra/linux-smp-2.6.17.13/kernel-headers-smp-2.6.17.13-i386-1.tgz
Optional kernel headers. There will only be needed to compile a few things,
such as apps and libraries that use ALSA (it contains the /usr/include/sound
directory that for 2.4.x kernels is supplied in the alsa-driver package)
Note that the "alsa-driver" package does NOT work with this kernel,
you have to recompile the "alsa in the kernel" itself if you want
changes, OR install a newer alsa driver package from source:
Please note that if you install with this you still need kernel-modules
from /extra, and that there's no alsa-driver for this kernel because it's
all built into kernel-modules and kernel-headers (well, and the kernel :-).
ALSA 1.0.11/12 specifically DO NOT support these newer kernels.
--
********************************************************************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M....@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
********************************************************************
Olive
> Roel Kluin <rjc_Remove_kluin@ho_nospam_tmail.com> wrote:
>> On Sat, 03 Feb 2007 09:07:17 -0800, olddrunkninja wrote:
>> 2.6.17.13 is in the .../extra/linux-2.6.17.13/ directory. That is on
>> your dvd or if you use cds, either 2 or 3. You can install the packages
>
> Actually: CD 4 (source disk 1), it didn't fit on CD 3 anymore.
>
>> don't install the headers (see the kernel-headers.WARNING).
>
> And see also this text in the ChangeLog:
> extra/linux-smp-2.6.17.13/kernel-headers-smp-2.6.17.13-i386-1.tgz
> Optional kernel headers. There will only be needed to compile a few things,
> such as apps and libraries that use ALSA (it contains the /usr/include/sound
> directory that for 2.4.x kernels is supplied in the alsa-driver package)
>
> Note that the "alsa-driver" package does NOT work with this kernel,
> you have to recompile the "alsa in the kernel" itself if you want
> changes, OR install a newer alsa driver package from source:
> Please note that if you install with this you still need kernel-modules
> from /extra, and that there's no alsa-driver for this kernel because it's
> all built into kernel-modules and kernel-headers (well, and the kernel :-).
> ALSA 1.0.11/12 specifically DO NOT support these newer kernels.
You do not need to install the kernel-header of the 2.6 kernel but keep
the kernel header of the 2.4 series; you need to have the kernel header
corresponding with the kernel that have been used to compile glibc (see
the warning in the Slackware tree). Kernel modules that really want to
have the current kernel header look in /lib/modules/`uname -r`/build
(which is a symlink to /usr/src/`uname -r`.
As for the alsa driver they are included in the kernel modules packages
of the 2.6 kernel (but they are in a separated package fot the 2.4 one).
Olive
Thomas Ronayne
better or worse, just different.
I install using the test26.s kernel (and I do a "full" install; i.e.,
everything). When that completes and the system boots for the first time
there will be missing modules and all kinds of stuff, but not to worry.
The next thing I do is mount disk 4 and
upgradepkg /mnt/cdrom/testing-2.6.18/linux-2.6.18/*.tgz
That upgrades all the 2.4.x kernel-related stuff that got installed by
default (no matter what kernel you use to install) to 2.6.x.
For some reason /etc/rc.d/rc.modules remains linked to
/etc/rc.d/rc.modules-2.4.33.3 instead of /etc/rc.d/rc.modules-2.6.18, so
before you reboot
cd /etc/rc.d
rm rc.modules
ln -s rc.modules-2.6.18 rc.modules
and that takes care of that.
The last thing I do is mount disk 1 and
cp /mnt/cdrom/kernels/test26.s/config /usr/src/linux-2.6.18/.config
That puts the configuration the test26.s kernel was built with into the
kernel source directory so I have a known starting point if I want to
fiddle with the kernel (actually, I do -- I install Cisco VPN -- but
otherwise I do not mess with it).
Again, not better, just different (and I'm running half a dozen servers
built exactly this way; no runs, no drips, no errors -- YMMV).
Hope this helps.
--
Everything works -- if you let it.
Thomas Ronayne
> olddru...@gmail.com wrote:
>> I want to setup Slackware 11 with the 2.6.17.13 kernel, since it has
>> more support for my mobo hardware, but I'm not sure how to do it. Is
>> there something I type in at boot, or an option in the install I may
>> have missed?
>>
>
pretty bad). Ignore all that claptrap, please.
Eef Hartman
> That upgrades all the 2.4.x kernel-related stuff that got installed by
> default (no matter what kernel you use to install) to 2.6.x.
No, it doesn't, as kernel-ide-2.4.<whatever> does NOT have the same package
name as kernel-generic-2.6.18 (the words BEFORE the version are different),
so you'll wind up with BOTh the 2.4 as well as the 2.6 kernel.
But the modules OF the 2.4 kernel DO get overwritten by the 2.6 ones
(the package name is kernel-modules-<version> in both cases) so this 2.4
kernel isn't functional, you must explicitly removepkg it.
> For some reason /etc/rc.d/rc.modules remains linked to
> /etc/rc.d/rc.modules-2.4.33.3 instead of /etc/rc.d/rc.modules-2.6.18, so
> before you reboot
That may have to do with the above, as the 2.4 kernel hasn't been totally
removed yet.
> That puts the configuration the test26.s kernel was built with into the
> kernel source directory so I have a known starting point if I want to
> fiddle with the kernel (actually, I do -- I install Cisco VPN -- but
> otherwise I do not mess with it).
That config has already been saved, in /boot/config-<version>.