hi there Chris08,
If you opt for the test26.s kernel during the install, you won't get the Linux 2.6.13 kernel modules. Because they are in a testing directory, they won't even be available to select during the installation. You will have to install the packages using pkgtool immediately after the installation completes, or immediately after you get the system up.
If you don't have a USB keyboard, it should be fine to do so afterwards, because everything really critical is built in that fat assed test26.s kernel image. However, immediately after the install completes, after exiting the Setup menu, before rebooting, you could use pkgtool. At this stage, your slackware partition(s) should still be mounted under /mnt. Type the pkgtool command.
If you've booted again with the Slackware CD and they aren't mounted, typing pkgtool will dump some instructions and examples to console so that you can mount your partitions under /mnt. You would have to mount your cdrom at /cdrom in this case. (not /mnt/cdrom)
If you have elected to put other parts of the slackware system on separate partitions, for example /usr, /var or whatever, you must mount them all under /mnt after mounting the root filesystem there. Your root filesystem will already have the existing mount point directories for your other partitions. This is where the examples come in handy, if you type pkgtool.
For a simple example, assume the root partition is /dev/hda1, and the cdrom drive is /dev/hdc (/dev/cdrom won't work here while booted with the slackware CD). If you are booting from SATA, your hard disk device could be /dev/sda1 (It's treated as a SCSI device).
If you need to mount your filesystem, at the root prompt:
Remove whatever CD is in the drive, and insert Disk 2.
mount /dev/hda1 /mnt
mount /dev/hdc /cdrom
Otherwise, just type pkgtool
Because we did 'cd /cdrom/linux-2.6.13' before typing pkgtool, we can choose to install packages from the current directory. Otherwise, choose Other and you can type the path to where the 2.6.13 kernel module packages are.
Say Yes to the following two packages, and No to the rest (unless you want to install the kernel-source). Say No to kernel-headers.
You may have to do it that way, if you have only a USB keyboard to use. (usb support is modular)
It's just as easy to install the kernel modules packages after the system is up.
If you have the Slackware CD set, they are on Disk 2 in the linux-2.6.13 directory. If you don't have the CD, you will need to make sure you have them available. See further below, they can be downloaded. You need the kernel modules and alsa drivers.
When you boot into your installed Slackware system for the first time, log on as root and with Disk 2 in the drive:
Reboot after installing these packages (or manually load the desired modules)
Otherwise, if you don't need SATA support, play it safe and use one of the 2.4.31 kernels and install Linux 2.6.13 afterwards.
To install the Linux 2.6 kernel afterwards on Slackware 10.2, go to the linux-2.6.13 directory on the second CD in the Slackware 10.2 set, or download it from one of the slackware ftp mirrors at /pub/slackware/slackware-10.2/testing/packages/linux-2.6.13
The packages you need to install, are:
Do not install kernel-headers-2.6.13-i386-1.tgz unless you know what you are doing. They are more for compiling glibc. Read the WARNING file in the directory.
To install these packages, do:
Note! Installing these packages will change the /boot/vmlinuz symbolic link to point to the new kernel image. If you still want to be able to boot the old kernel, you're going to have to fix that, or edit lilo.conf accordingly.
You may want to install the kernel-source-2.6.13 package if, for example, you need to compile third party drivers (kernel modules)
Now, if you are just using ordinary IDE disk controllers, and the ext2 filesystem this generic kernel should be good to go and you just add a stanza to /etc/lilo.conf as usual. However, if you need to support other storage hardware or other filesystems (such as reiserfs) then you will need to create an initrd image (initial ramdrive) and load it in your lilo.conf kernel stanza. This is a way to support critical drivers as modules, that are needed to boot the system. Mainly disk controllers and filesystems.
To create the initrd, you're first going to have to know what modules you are going to need. Separate them in the command, with colons between them.
For example, if you need to build an initrd to support the ext3 filesystem, you're going to need the jbd module, and the ext3 module. The command to create the initrd is as follows:
mkinitrd -c -k 2.6.13 -m jbd:ext3
Or, for reiserfs:
mkinitrd -c -k 2.6.13 -m reiserfs
In your /boot directory, there's a README.initrd file for a bit more info on this. Also, read the man page for mkinitrd on your system. Most every distro does mkinitrd a bit differently, and I like the way this one is implemented.
Once you have your kernel packages installed, and (if necessary) your initrd created, you must add a stanza to /etc/lilo.conf. Put it as the first stanza, below the VGA comments, if you want it to be the default boot choice. (alternatively specify default=2.6.13 or your chosen "label" in the global section of the file)
Note how I've changed the old kernel image to the real filename vmlinuz-ide-2.4.31 because the vmlinuz symbolic link had been changed. I do not believe in using symbolic links for kernel images.
After you make changes to lilo.conf, don't forget to run the lilo command:
That should be it. If you've done everything correctly your system should boot to the generic 2.6.13 kernel you installed. If it doesn't, then simply boot your old kernel. You probably need to correct the module loading parameters in your initrd. You can simply run the command again to make another and re-run the lilo command.
All of this you can get here as well:
Good Luck Chris08!