Reading over this: http://docs.slackware.com/howtos:sla...:systemupgrade.

I blacklisted:
kernel-generic-smp
kernel-huge
kernel-huge-smp
kernel-modules
kernel-modules-smp
[0-9]+_SBo
[0-9]+alien
[0-9]+compat32

I had a question about this part-
If new kernel(s) have been added to the Slackware release you are upgrading to, then use ”installpkg” to install those new kernel packages first (do not use ”upgradepkg” because that will wipe your existing kernel).
You will have to install at least one kernel (kernel-generic, kernel-generic-smp, kernel-huge, or kernel-huge-smp) and the corresponding kernel modules package (kernel-modules or kernel-modules-smp).
You can not use slackpkg for this step."

Would I just go to kernel.org, download the 3.14 kernel and use installpkg to install it? What about the kernel-headers? What do the huge and generic kernel versions mean?

I'm pretty confused about all this as I'm somewhat new to really messing with Slack. Any help is appreciated.

No, you can't use installpkg to install kernel from kernel.org since it contains source only
Grab the latest kernel packages from a/, d/, and k/ directory and install them using installpkg

kernel headers are located in d/ directory

if you are new to Slackware, then i would advice you to stay in -stable until you are familiar with how Slackware are designed or you will end up brake your own system.

No, you download the files kernel*.txz (from current changelog) and install with installpkg.
(you must edit lilo.conf and run lilo with the new kernel)
a/kernel-generic-3.14.5-i486-1.txz: Upgraded.
a/kernel-generic-smp-3.14.5_smp-i686-1.txz: Upgraded.
a/kernel-huge-3.14.5-i486-1.txz: Upgraded.
a/kernel-huge-smp-3.14.5_smp-i686-1.txz: Upgraded.
a/kernel-modules-3.14.5-i486-1.txz: Upgraded.
a/kernel-modules-smp-3.14.5_smp-i686-1.txz: Upgraded.

d/kernel-headers-3.14.5_smp-x86-1.txz: Upgraded.

k/kernel-source-3.14.5_smp-noarch-1.txz: Upgraded.

Download from any Slackware-current mirror.


Kernel headers is one of the packages above

Huge kernel has all the drivers and modules, it is used to boot the install cd/dvd.
It is recommended that you change from huge to generic, you will find some topics
about using hugeXgeneric, but if you use generic you must use an initrd.gz file.
Search about it, there's info on the forum, and on the /boot dir there's a file
initrd.README.


EDIT- I didn't notice before, you're using compat32, so you must have x86_64.
Use a x86_64 mirror to update and to download.
As willysr said, -stable is safe, but if you want learn how Slackware works then
changing to -current is a good start.
Before change search and read topics on that subject.

Using installpkg would be for a pre-compiled kernel, that is shipped as an update form the slackware devs in the form of a slackware package. Typically named something like kernel-generic-3.10.17-i486-3.txz or kernel-huge-3.10.17-i486-3.txz

You can use slackpkg to easily find out if there is a new slackware kernel available.

You would go to kernel.org if you wanted a newer kernel to compile yourself.

The huge kernel contains almost every driver in the kernel, whereas the generic kernel loads drivers from modules and also requires you create an initrd so you can access the filesystem.

See here on how to do that: http://slackware.osuosl.org/slackwar.../README.initrd

Generally, the huge kernel should be fine in most cases.

Thanks everyone for the help! However, I don't see any SMP kernels listed here: http://slackware.mirrors.tds.net/pub...slackware64/a/

I'm not sure if SMP was integrated into the kernel or not. Again, any help is appreciated.

for 64 bit, all kernel are configured to have SMP

Agreed. If you're new to Slackware it is a good idea to stick with stable. We provide technical support for full installations of stable. If you want to run slackware-current it is expected that you will do some of your own trouble shooting.

I second that. -Current is nice but it has it's issues. If you use OEM drivers, you'll have to be mindful that you'll need to rebuild them prior to the reboot or else you may have incompatibility issues on boot.

-Current is often better ran with the free drivers as it gets less hectic.

Also, updating the glibc-kernel-headers is not recommended unless you rebuild glibc against it. Only use the glibc and kernel-headers packages Patrick updates.

1 members found this post helpful.