I just tried, seems to work. So I suppose that yes, you can

Yes, it worked but when I tried to boot up to the new kernel, the system just froze.

Obviously I need some more current packages in order to use current's kernel. I guess I will just have to wait for Slackware 14.0

Not sure about that. I would bet on a misconfiguration of the kernel, or maybe you compiled a generic kernel and forgot to make an initrd or to make the root file system (the file system used for /) built in.

Please try again and tell us what are the last error messages you get at boot just before the system freezes.

Typical beginner errors.

1. When using slackpkg to upgrade to a new release of Slackware, use the correct sequence of commands. Just using "slackpkg upgrade-all" gives you a certain 100% failure rate. See http://www.linuxquestions.org/questi...5/#post4676576 where I tried to explain the upgrade process using slackpkg.
2. When upgrading to the next release of Slackware (even if you intend to run -current) you must go all the way. If you try a partial upgrade (hand-picking the packages you think you need) will almost certainly lead to a broken system. Do not mix packages of multiple releases!

Eric

1 members found this post helpful.

For psion10, that means that he should have build himself a newer kernel re using only the config file from current, instead of installing a package taken from current. I must admit I overlooked he did it that way.

Well I used the huge kernel which doesn't need an initrd. As far as I am aware, this is not a system dependent kernel.

I would have expected some of the 13.37 packages to have difficulty running under the new kernel but I didn't expect the system to freeze during boot-up. Neither "dmesg" nor "syslog" showed anything useful (I wish we could capture the boot-up messages).

The kernel by itself, if you mean the kernel source, is not system dependent.

But the kernel once built (the executable) is system dependent.

So the problem is that instead of building it yourself (which is what I recommended) you just installed an already built kernel intended for another Slackware version.

A pointed out by Alien Bob, this can't work.

So, either compile your own kernel, taking as a basis the config file provided in current for it (you could follow this to do that) or wait for Slackware 14 to be released.

How does using a current config file create a kernel that will run in 13.37?

The config file is only a text file which is used as a basis for kernel's configuration. When I wrote "provided in current" I meant one of the files which were used to set the configuration of one of the kernels (version 3.2.26) included in current. But theses files are not specific to a Slackware version, only the kernel built with it is.

So if you put one of these files at the root of your kernel source tree, renamed as ".config", then "make oldconfig" your kernel will get the same configuration as the analog kernel in current. After that you will have to build it it with "make bzImage; make modules; make modules_install" so it be able to run on Slackware 13.37. See aforementioned link for how to proceed.