While perusing the recent -current changelog, I noticed this entry:

Does this mean there will be an option to install a 2.6.13 kernel during the setup installation (as opposed to installing one from /testing after installation)? If so, that's cool. I always end up compiling my own kernel after installation, but for some folks, having the option to install a 2.6 kernel during the actual setup/installation routine will be nice.

it looks that way to me, i thought maybe the 2.6 series would just be in 11 but hes put one on the install right at the last minute.

No, Slackware-10.2 will have 2.4.31 by default. Look closer
and you'll see that kernel is in the testing directory.

You can build your own CD, or put that kernel on a floppy,
and use it when you install. But IMO you'd be better off to
install with the default 2.4.31 and then build your own 2.6.13
or whatever afterwards. The 2.6.x.x kernels in testing so
far have not had the same support as the 2.4.x kernels.

Yes, I just checked this out on ftp.slackware.com. If you navigate into current and then into kernels (where the install kernels are kept) you'll see the new test26.s directory. It won't be the default kernel but at least there will be an option to for a 2.6 kernel at install time.

I also noticed that this 2.6 kernel contains reiserfs support, which the previous 2.6 test kernel did not. So, if you use reiser you shouldn't need the initrd anymore.

Yes, it looks like there is preliminary 2.6 support for the installation. I haven't looked at it yet, but I suppose that you'd still have to install the 2.6 kernel modules from testing.

I did not say that 2.6 was going to be the default. I know 2.4.31 is the default and I also realize that 2.6.x is in /testing (as I indicated in my post). But, it seems to me that in addition to all of that, he has also added a testing 2.6 kernel to the list of kernels to that one can choose from during the installation. The installation will still default to 2.4.31, and one can still go into /testing and install a 2.6 later, but it looks like you will also now be able to install a 2.6 during the initial installation.

That is good to hear. I never understood why the default kernels were set up that way. It always seemed like a lot of effort just for the filesystem. I always compile in ext2, ext3, and reiserfs into my kernels so I never used initrd, but it always seemed to me that also be how the default kernel was set up.

You are right indeed...sorry old chap. I missed it because of those
entries which aren't bold face.

Yes, it's quite large too, at 3.1M ... seems to have everything but
the kitchen sink ... unless I missed that, too. ;)

When I started my rsync there was nothing but the ChangeLog browser
to look at, and no mirrors had it yet. My rsync has now been running
for about 12 hours. Had to get it from the Slackware ftp server, and
that after waiting in line a bit. Seems that server only allows for 30
connections, and it's not very fast.

Yup to install the 2.6 kernel @ boot use

test26.s

haven't tried it yet look for some Cd's as we speak to get them burnt to try it out....


taken from slackware how to due to that I wasn't able to install slackware 10.1 cause my sata drive wasn't being dected
There is also a 2.6.13 install kernel that might be useful if your machine
has new hardware such as a Serial-ATA controller that isn't working with
the 2.4 kernel:


test26.s This is a 2.6.13 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 still has a few rough
edges, so it's not the default kernel on Slackware
yet, but some users may need it to install on their
hardware. Because the 2.6 kernel series is rapidly
evolving, 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. The 2.6 kernel is
not yet considered officially supported by Slackware.

Well I tried it and I get locks up on IRQ 11 and same thing for bare.i locks up on IRQ 11.... Never gonna buy a ati chipset motherboard again

It looks like PK is getting fed up waiting for Reiser4 to become part of the kernel and has made the unusual step (for him) of modifying the kernel.
Many Slackware users just install into a simple root partition + swap and therefore have /boot on reiser3fs, so reiserfs has to be compiled into the kernel to work.

I just loaded it on my ibm T42 notebook but yet the touchpad will not work at all. I tried all kinds of configurations and even external optical mice won't work. Any suggestions would be cool. Other than that it runs fine with the 2.6 kernel. I am a newbie so hopefully i'll figure it out.

I selected the test26.s kernel and failed to find any modules, not really a shock as /lib/modules only contains 2.4.31

So did I. At first I was indeed shocked when I got the message of missing modules, until I found out there are none. What the heck is that? I would say that's not comfortable.
I'm confused by an unexpected error in the slackware installation, which is seldomly seen. Please tell me how this is fixed in the most comfortable way, if you fixed it.

..really unexpectet, I am disappointet a little bit..

You really should read text related to the new release.
From http://mirror.switch.ch/ftp/mirror/s.../RELEASE_NOTES: