Hi everyone

I installed slackware 10.2 with the default 2.4.31 kernel, but now a
driver forces me to upgrade to 2.6. I would like to know whether the
system I installed (at the time choosing a 2.4 kernel) is ready for use
with a 2.6 kernel. Or do some utilities/system scripts need to be
updated for everything to bo smoothly?

Thanks for any help,

Mack

MackS wrote:

> I installed slackware 10.2 with the default 2.4.31 kernel, but now a
> driver forces me to upgrade to 2.6. I would like to know whether the
> system I installed (at the time choosing a 2.4 kernel) is ready for use
> with a 2.6 kernel.

I run 10.2 with a stock 2.6.12 kernel from kernel.org, tuned to my hardware.
Runs nice)

Niki Kovacs
--
I'm not as think as you stoned I am.

MackS wrote:

> I would like to know whether the system I installed (at the time
> choosing a 2.4 kernel) is ready for use with a 2.6 kernel.

Slackware is not only ready for the 2.6 kernel theres a prebuild kernel
2.6.13 ready to download from the /testing tree.

Warning: If you are using another kernel than the default kernel bare.i
then installing kernel-2.6.13 will overwrite kernel-2.4.31

Find your nearest mirror here:
<URL: http://www.slackware.com/getslack/>

Remember to read this file README.initrd, you'll find it in the same
directory as the kernelpackages.
--
Thomas O.

This area is designed to become quite warm during normal operation.

In article <1130524309.279080.223470@o13g2000cwo.googlegroups .com>, MackS wrote:
>
> I installed slackware 10.2 with the default 2.4.31 kernel, but now a
> driver forces me to upgrade to 2.6. I would like to know whether the
> system I installed (at the time choosing a 2.4 kernel) is ready for use
> with a 2.6 kernel. Or do some utilities/system scripts need to be
> updated for everything to bo smoothly?

It should work fine. The only hitch I had was that the 2.6 kernel
was probing udev, which I hadn't configured under 2.4. Uninstalling
the udev package in this case should fix the problem.

I used both the stock Slackware kernel and a custom-built kernel
on 10.0, and they work great. So you should really have no
problems with 10.2 and 2.6.

--keith

--
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom
see X- headers for PGP signature information

On 28 Oct 2005 11:31:49 -0700, "MackS" <mackstevenson@hotmail.com> wrote:

>I installed slackware 10.2 with the default 2.4.31 kernel, but now a
>driver forces me to upgrade to 2.6. I would like to know whether the
>system I installed (at the time choosing a 2.4 kernel) is ready for use
>with a 2.6 kernel. Or do some utilities/system scripts need to be
>updated for everything to bo smoothly?

It depends, on desktop hardware disabling udev does the trick, on
laptops new tools are required for 2.6.13+ --> pcmciautils and friends.

Slack-10.2 doesn't yet have these updated tools... CardBus is fine,
older stuff? YMMV... I don't use slack's 2.6 kernels, since the
system is up and running try compiling your own kernel...

I'm biased though, always found it easier to compile a new kernel
than to figure out how to use initramfs )

/boot/README.initrd points at something worth reading, perhaps.

Grant.

Hi guys


> It depends, on desktop hardware disabling udev does the trick,

Thank you for your help on this. But you are telling me that I
*disable* udev? I thought that I actually had to install that for use
with 2.6.

Thanks for clarifying this

Mack

MackS wrote:
> Hi guys
>
>
>
>>It depends, on desktop hardware disabling udev does the trick,
>
>
> Thank you for your help on this. But you are telling me that I
> *disable* udev? I thought that I actually had to install that for use
> with 2.6.
>
> Thanks for clarifying this
>
> Mack
>
Devfs support was removed from the 2.6.13 kernel. So i think you have to
use udev for 2.6.13.* or 2.6.14. Everything has worked smoothly for me
so far. Just make sure the package is installed and the
/etc/rc.d/rc.udev file is executable.

Vasilis

Vasilis Papavasileiou wrote:
> Devfs support was removed from the 2.6.13 kernel. So i think you have to
> use udev for 2.6.13.* or 2.6.14.

either that, or use a static /dev directory, as in the old days.

personally, i think udev is a great idea, and the only trouble i had
getting it to work was because i forgot to compile support for it in into
the kernel...

> Everything has worked smoothly for me
> so far. Just make sure the package is installed and the
> /etc/rc.d/rc.udev file is executable.

yup, that should do it. then go and read
<http://www.reactivated.net/writing_udev_rules.html> to learn how to set up
persistent device naming for removable devices.

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9