SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Just installed Slackware-current but had one minor problem, while booting into the system (I choose the huge kernel) I was missing /lib/modules/2.6.17.x. Only thing I had was the 2.4.x modules under /lib. I ended up compiling my own kernel to fix the problem, I'm wondering if this is a bug, or if its an error on my part.
modprobe would complain it couldn't find lib/.../188.8.131.52-smp/modules.dep and if I renamed it to 184.108.40.206 it would complain lib/.../220.127.116.11/modules.dep wasn't there. I'm guessing its the wrong build I tryed uncompressing.
How come selecting the huge kernel doesn't install the modules with it?
From the Slackware-HOWTO in the slackware-current root:
huge26.s This is a 18.104.22.168 kernel with support for nearly all
IDE (ATA), SATA, and SCSI controllers, as well as
most of the filesystems supported in the standard
kernel. The 2.6 kernel series is not the default
kernel on Slackware but does have some advantages for
certain users and hardware, though perhaps the
additional complexity causes it to sacrifice a bit of
stability and security. If you install with this
kernel you might want to go to ftp.kernel.org later
and build a new kernel from the latest sources.
IMPORTANT! If you install with the huge.s kernel
you will need to find the /extra/linux-22.214.171.124
directory later and install at least the
kernel-modules package in it to have full hardware
Oddly I'm getting a kernel panic with this on one of my boxes. I'm still checking to see what's missing (ie modularised instead of compiled in) - but that's part of the fun.
EDIT: Kernel panic now gone - and don't I feel like a fool. I have /boot on its own partition (I like it read only and ext2) and didn't notice that the lilo installer put that partition as the root. In other words, huge26.s works fine on a Dell GX620...
This is a set of essential kernel packages with support for SMP (up to 16
processors), support for SMT (Hyperthreading), and optimizations for
As with the other 2.6.x kernels in this Slackware release, an alsa-driver
package is not provided. You may leave the alsa-driver package that was built
for 2.4.x in place in order to have /usr/include/sound headers, OR you may
install the kernel-headers-smp package here which includes ALSA
/usr/include/alsa headers from the kernel. The kernel-modules-smp provides the
ALSA modules that for 2.4 are provided by the alsa driver package.
There, that should cut down on the "where are is the alsa-driver" inquires.
I'll admit it's a bit confusing when a package disappears, but it's because
this functionality was merged into the standard kernel. :-)
The performance offered by these kernels and modules should be close to
optimal for any i686+ multiprocessor/core system. Further tweaking should not
be helpful for most uses, but (as always) feel free to play with the options.
Source packages are not provided. Instead, use the uniprocessor kernel-source
package, and apply the SMP Makefile patch:
cat linux.makefile.smp.diff | patch -p1
And copy the config-generic-smp-* over the /usr/src/linux-*/.config.
This will provide the source tree used to build the kernel-generic-smp kernel.