When the install asks which kernel I want to use, can I choose the 2.6.7?

Yes, the 2.6.7 runs very well here.

HTH,

Samsara

Sorry, I believe the answer is no.

Hmmm, 2 conflicting answers. What to do, what to do... What would happen if I chose the 2.6.7 kernel, Shilo?

Choose it and see. I never saw an option allowing me to choose it. If you did a full install, you didn't install anything from testing. So you would have the wrong source, kernel headers, modules, etc. For all of the trouble you will go through, it would probably be easier to install the stock kernel and:

A) Use the inluded directions in /boot for upgrading to the 2.6.7 kernel using mkinitrd.

or

B) Download the source yourself and compile your own.

I don't see two conflicting answers to your question. Your question is if it is possible to install the 2.6.7 kernel during the install. Samsara hasn't answered that. He has simply said that he has 2.6.7 running. I might note that I have 2.4.26, 2.6.7, and 2.6.8.1 all running very well. Doesn't mean I can install the 2.6.7 kernel during the install.

A better question, if you feel that the two answers are conflicting, is:

Samsara- So how did you get the 2.6.7 kernel loaded during the install?

I believe that you will not get an answer to that question, because evry time I have heard this question, everyone has stated that it cannot be done.

Read somewhere on these forums that 2.6.7 kernel should be included on the 2nd Slackware 10 cd, to install it one could use pkgtool, reboot and voila!

But have not yet tried it myself, although I will get the change it a day or two.

I think there is a little more to it than that. Check out /var/slackware-current/testing/packages/linux-2.6.8.1/README.initrd (maybe something else on yours, but definately README.initrd). Regardless, this is not a method to install a 2.6 kernel during the initial install.

You're right Shilo, I couldn't choose it. For one, I could not unmount the cd while in the process of installing and insert the other cd. For 2, the kernel on the cd needs to have something done with it: it isn't in the same "format" as the other kernels that can be used. I am allowed to choose a kernel from a floppy disk, but I couldn't just copy it from the cd onto a floppy: it isn't "right". You probably know why, but that's ok I don't need to know yet. I now know it can't be done that way (during the install).

The answers seemed conflicting to me, because of the actual question I asked: "When the install asks which kernel I want to use, can I choose the 2.6.7?"

Samsara said "yes..." so I assumed that meant yes in answer to my question, and the added comment was just an extra illumination.

I don't really need the new kernel, but I figured since I was reinstalling I might as well try.
Thanks!

Linda-

I know that some people like to install the "Official" Slackware 2.6.7 (or now the 2.6.8.1 in /testing), but I have found that the easiest way to go is just downloading the source from kernel.org (or one of it's mirrors) and compiling it yourself. The sweet thing is that it leaves your 2.4 stuff alone. If you can't boot the new 2.6 kernel, just keep trying when ever you feel like it. Eventually, it will work. You just have to figure out the choices that work best for you. In the meantime, you'll always be able to use your 2.4 kernel, so there is no risk of losing your system.

I think this is a good way to learn about kernel compiling. If you try to learn with your 2.4 kernel, there's always a chance that you'll mess something up and your old 2.4 kernel won't work. That's just not the case with the 2.6 kernel. Anyone please feel free to correct me if they think that I am wrong.

Some key points to remember with the 2.6 kernel. (Note: I am assuming that everything is already working peachy-keen with your stock install.)

1) You should be using hotplug and udev with it. They can be enabled with the following.
Now if you weren't using these before, your 2.4 kernel installation MAY act up on you. I recommend doing an:
Before you try out anything. Then, without getting into recompiling or anything, run the two previous commands and reboot.

Now:
If you get no output, then you are looking good. If they are different, we are going to have to look at why. It may be that you need to add something to your /etc/hotplug/blacklist file. You may aslo have some problems with your /dev directory. It is now generated automatically at boot time. Any custom symlinks are toast. If you have problems with this, search the forums a bit. I think I've already posted on some ways to get all the devices created properly with udev. If not, I'll post up a quick guide. This is usually a problem for people with more than one optical (CD/DVD) drive.

2) SCSI emulation is no longer needed with the 2.6.7 kernel. I think that it is all the 2.6.x kernels where "x" is 5 or greater. The exceptions to this are 2.6.8 (It's broken in other ways and should not be used) and 2.6.8.1. Some of the CD burning functionality was broken with these kernel releases. If burning is a concern for you, I would recommend 2.6.7.

What this all means is that you can remove the "append: hdc=ide-scsi" or whatever from /etc/lilo.conf. Make sure to run /sbin/lilo afterwards if you make any changes. Also, if you were previosly using SCSI emulation solely for the CD burning, you can also comment out the relevant line in /etc.rc.d/rc.modules. Note that you may still need it for other things, like USB mass storage. Everyone differs here.

Of course if you do make these changes, you will lose your burning ability under the 2.4 kernel. Something to keep in mind, if that is important to you. I would recommend this being one of the last things to change, if you are jumping over to 2.6.x.

3) make oldconfig has given a lot of people hassles. Make sure that if you have Frame buffers configured (you probably see a little penguin when you boot), that you have the appropriate choices made when you configure your kernel. I recommend using "make xconfig". It's very user-friendly. Note the output fro mthe terminal after you start that up. You probably already loaded the cjoices from your working kernel. Just go through all the choices. This allows you to answer to the new options and double check your old options. Take your time on this step. It's the most important of any of the steps when compiling a new kernel. Some people don't take their time. This is what I think: does it take longer to pour over every single selection and make the right choices, or to quickly glance at all of the options, have a broken kernel, post on the forum for help, wait for a response, try out the suggestions, etc.? No one can possibly know all of the hardware you are running and all of the different protocals that you may need. Everyones suggestions on how to compile your kernel are nothing more than best guesses developed from their own kernel compiling experience.

Hope this is useful.