Upgrading stock 2.4.22 kernel to 2.5.x then to 2.6.6 with existing stock .config file
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
2.5 is the development branch of the 2.4 kernel series. There is not yet a development branch of 2.6, that will be 2.7. This is further evidence that 2.6 is still considered not ready for production boxen. My understanding is that Linus doesn't open the development branch until he is satisfied that the current kernel is stable. Also they say you are not supposed to use the .config file from your 2.4 kernel in building the 2.6 kernel, although I think several people have done so. It just needs a lot of tweaking afterwards. Like they said above keep your 2.4 kernel (probably should upgrade it to the newer stock slack kernel as 2.4.22 had security issues IIRC) and then muck around with the 2.6 kernel all you want.
First, I meant 2.4.26. Second, yes soundcard is a module, I dont know where tulip would be but I'm sure its a mod because a used my 2.4.22 .config file and it worked then. (I'm on 2.4.22 now, by the way)
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
The tulip drivers are located in the network device 100mbps card section of the kernel configure menu near the middle. Look for Other pci isa cards which when selected opens cards below it.
Tulip drivers are stated to be 'older' compat drivers but are also used for generic cards.
There is a quick and dirty way to add most anything missed to the kernel as a module.....
Open the .config in your favorite editor and find what you missed (i.e. the tulip driver is around line 690 to 700) ste it to CONFIG_THINGY=m do this for everything as a module you wish. save it...
Goto /usr/src/linux in the console and (command syntax kernel version dependant) make oldconfig then make modules, make modules_install..