LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-06-2004, 06:48 PM   #1
Kyl3
Member
 
Registered: Apr 2004
Distribution: SUSE 9.3 Pro
Posts: 110

Rep: Reputation: 15
Upgrading stock 2.4.22 kernel to 2.5.x then to 2.6.6 with existing stock .config file


Is there anyway to do that so I can make sure that it boots when I gut it up to 2.6.6?
 
Old 06-06-2004, 07:56 PM   #2
newinlinux
Member
 
Registered: Dec 2003
Location: Next to Equator
Distribution: GNU/Linux 2.6.14
Posts: 382

Rep: Reputation: 30
just keep the 2.4.22 around, you can boot back into 2.4.22 if your 2.6.6 fails.
 
Old 06-06-2004, 09:23 PM   #3
Shade
Senior Member
 
Registered: Mar 2003
Location: Burke, VA
Distribution: RHEL, Slackware, Ubuntu, Fedora
Posts: 1,418
Blog Entries: 1

Rep: Reputation: 46
Ditto.

Why do it such a roundabout way? Since 2.5.x is a development branch anyway, it's possible you'd have more problems with it than the stable 2.6.x series.

Just don't reboot 'til you see lilo accept your settings graciously And keep a boot disk for your old kernel handy, of course.

If you've recompiled your kernel previously, you can still take the old .config and dump it into the new source directory. It'll pick up your old options, while still prompting you for the new ones.

--Shade
 
Old 06-06-2004, 09:47 PM   #4
ringwraith
Senior Member
 
Registered: Sep 2003
Location: Indiana
Distribution: Slackware 15.0
Posts: 1,272

Rep: Reputation: 65
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.
 
Old 06-07-2004, 03:40 PM   #5
Kyl3
Member
 
Registered: Apr 2004
Distribution: SUSE 9.3 Pro
Posts: 110

Original Poster
Rep: Reputation: 15
I did it! I upgraded to 2.4.28! But on that new kernel, it does this:

modprobe: Cant find module tulip (my network card)
modprobe: Cant find snd_emu10k1 (Thats my sound card)

So I thought, run alsaconf and netconfig then dhcpcd. Didn't work. Any ideas?

Last edited by Kyl3; 06-07-2004 at 04:02 PM.
 
Old 06-07-2004, 04:05 PM   #6
Shade
Senior Member
 
Registered: Mar 2003
Location: Burke, VA
Distribution: RHEL, Slackware, Ubuntu, Fedora
Posts: 1,418
Blog Entries: 1

Rep: Reputation: 46
Well, did you configure tulip as a module or in your kernel? Same for sound module?


--Shade
 
Old 06-07-2004, 04:13 PM   #7
Kyl3
Member
 
Registered: Apr 2004
Distribution: SUSE 9.3 Pro
Posts: 110

Original Poster
Rep: Reputation: 15
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)
 
Old 06-08-2004, 05:12 AM   #8
Nichole_knc
Member
 
Registered: Mar 2004
Location: Georgia
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287

Rep: Reputation: 30
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..

That should get what ya need.....
 
Old 06-09-2004, 05:34 PM   #9
Kyl3
Member
 
Registered: Apr 2004
Distribution: SUSE 9.3 Pro
Posts: 110

Original Poster
Rep: Reputation: 15
Strange, I updated the kernel to 2.6.6 just to see if tulip and such will work if I put them as mods. (I still have 2.4.22) And they didn't I'm SURE that tulip and my SB Live! are mods.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
What is stock kernel? kskkumar Linux - General 6 09-13-2008 04:46 AM
Pakcages in stock kernel kskkumar Linux - General 1 11-25-2005 11:38 PM
Fedora with a stock kernel Baltasar Fedora 4 01-26-2004 06:03 PM
Stock bare.i Configuration File DeadPuddle Slackware 4 12-19-2003 08:56 PM
Patching SuSe stock kernel lacerto Linux - Software 0 10-28-2003 10:11 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:45 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration