Kernel choice for 10.2

statguy · 05-13-2006, 07:34 PM

I am preparing to upgrade to slack 10.2 and would like some advice on the choice of kernel. Please see below for my specific questions.

I am using a 2.4 series kernel in slack 10.0. Here is a section from my current lilo.conf.

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda2
  label = Linux
  append = "hdc=ide-scsi"
  read-only
# Linux bootable partition config ends

I have to use the append statement with the ide-scsi in order for my cd-writer to function.

Now for the questions.

If I go with a 2.4 kernel, I think I should use the adeptec.s kernel since my PC has built-in adaptec SCSI (although not being used). I don't remember what I used with 10.0.

Will ide-scsi work with that kernel?

If I go with a 2.6 kernel, will ide-scsi work?

Is there a preferable kernel? My hardware is fairly old (PII 455 MHz, 256 Mb RAM, it does have USB but I've never tried to use it).

Thanks for your thoughts.

Old_Fogie · 05-13-2006, 08:42 PM

the 2.6 kernel's I'm pretty sure, (not 100% OKAY) don't use the "ide-scsi" anymore. slack 10.2 comes w/a default 2.4 series kernel that does use that line. slack 10.2 includes an optioanl additional 2.6.13 kernel that is labeled as testing. it's really simple to install. i found it worked on p66, p166, p266, amd300, amd 600 and amd 2500+. I had some issues on pIV's tho.

tw001_tw · 05-13-2006, 09:34 PM

statguy,
Old_fogie is right on. You do not need the 'append ide-scsi' for your
cd burner to work with 2.6.x.

Quote:

If I go with a 2.4 kernel, I think I should use the adeptec.s kerne

I would pick the 2.4.x bareacpi.i to start with. Since you are not
using your scsi, it doesn't matter if the modules for it get loaded
or not. And if you need scsi, as long as you are not booting from the
scsi, all you need to do is "modprobe aic7xxx". Then you can install the 2.6.13 kernel and have an option on boot time of which one you want to use.
Here is a link to the instructions. (also found on install CD #2)
ftp://ftp.slackware.com/pub/slackwar.../README.initrd
Just don't install the kernel-headers package. That may or may not
cause problems, and it works for me without it.

Hope this helps some.
good luck
-tw

statguy · 05-14-2006, 08:28 PM

Thanks for the answers. They make sense.

What compelling reasons, besides the sheer thrill of adventure

are there for moving to 2.6.13?

Old_Fogie · 05-14-2006, 10:00 PM

Quote:

Originally Posted by statguy

Thanks for the answers. They make sense.

What compelling reasons, besides the sheer thrill of adventure

are there for moving to 2.6.13?

For me...These may ? be options that I use that I'm pretty sure (??) were not in 2.4 that I need:

tho they have to be recompiled in...

1. Linux security model - so I can use Dazuko and to enable real-time virus scanning.
2. low latency desktop
3. high memory use..I think 2.4 kernel limits you to 800 meg?
4. pre-empitve kernel
5. 4k stacks
6. security fixes

towsonu2003 · 05-18-2006, 10:01 AM

Quote:

Originally Posted by Old_Fogie

6. security fixes

2.4 has security & bug fix updates I believe.

drkstr · 05-18-2006, 11:37 AM

Quote:

What compelling reasons, besides the sheer thrill of adventure are there for moving to 2.6.13?

If you are going to compile your own kernel, I would suggest just downloading the most recent stable version from kernel.org (possible because Slack does not used modified version of kernel). The biggest improvements I've seen on the 2.6 kernels is hardware support and usability, but there are other benefits as well.

regards,
...drkstr

rje_NC · 05-18-2006, 12:22 PM

One convenient way to get the new kernel for Slackware users is to download the new 2.6.16.16 kernel package from the /testing folder under Slackware current.

You can easily download the Kernel source and kernel header packages and just use installpkg to put them where they belong. I just did this on my new 10.2 install and it worked great. I was quickly ready to make the configuration changes for my system and start the compile.

DO NOT install the binary kernel and module packages from current onto a 10.2 system. But the kernel source and header files will work fine.

Bob

gbonvehi · 05-18-2006, 12:37 PM

You shouldn't install new kernel headers package, you should stay with the one libc was compiled against (currently 2.4 headers).
For more information about why, take a look here: http://www.linuxquestions.org/questi...d.php?t=338385