LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel
User Name
Password
Linux - Kernel This forum is for all discussion relating to the Linux kernel.

Notices



Reply
 
Search this Thread
Old 06-24-2006, 09:58 PM   #1
banjzooie
LQ Newbie
 
Registered: Feb 2006
Distribution: Slackware 10.2
Posts: 19

Rep: Reputation: 0
Why does Kernel 2.6.17.1 + Slackware 10.2 = Kernel Panic?


Hello. I recently had to reinstall my entire Slackware Linux OS because I did something stupid that screwed it up. After reinstalling I went to kernel.org to get the latest kernel and got 2.6.17.1. I went through and configured it with "make xconfig" and selected what I thought to be all the appropriate stuff--I'd had no trouble doing that with previous kernels, 2.6.16.18 being the most recent I've used before 2.6.17.1.

I did all the usual stuff such as "make bzImage", copying that bzimage to my boot directory as vmlinuz-2.6.17.1, "make modules", "make modules_install", copying the system.map and .config into /boot as system.map-2.6.17.1 and config-2.6.17.1 respectively, and all the symlink stuff. I didn't see any need to modify lilo.conf based on the circumstances--It was pointing to vmlinuz, which was a symlink to vmlinuz-ide-2.4.31, and I replaced that symlink with one pointing to the 2.6 version of vmlinuz. Seemed like I did everything right.

So I restart after I do all that, select Slackware from the NTLDR boot menu, and Lilo starts as usual. Not long after that the kernel says to please properly specify "root=" or something like that, says something along the lines of no VFS linking, and then kernel panic happens and everything freezes. I'm forced to do a hard shutdown. I figured I'd just checked a wrong option in Xconfig, but I didn't have anyway to fix that now, so I was forced to reinstall Slackware again.

This time, before compiling kernel 2.6.17.1, I used "dd" to dump my current mbr using the 2.4.31 kernel to a file, "slack.old" and stored that file on a FAT32 partition. After compiling and going into /sbin/lilo to have it register the new settings, I dumped the new mbr onto that same FAT32 partition as "slack.mbr," the file which NTLDR was told to boot if I selected Slackware. I rebooted and selected Slackware, and the same thing happened--Kernel panic. After another hard shutdown I booted into another OS and copied the "slack.mbr" file into "slack.bad", deleted slack.mbr and copied "slack.old" into slack.mbr. That allowed me to boot Slack again under the 2.4 kernel, but I'd really like to use the 2.6 kernel.

What exactly should I do to stop kernel panic from happening? Does it have to do with what I select in the kernel compilation? This is really strange because it hasn't happened to me when using 2.6 kernels older than 2.6.17.1.
 
Old 06-25-2006, 12:56 AM   #2
prozac
Member
 
Registered: Oct 2005
Location: Australia
Distribution: slackware 12.1
Posts: 753

Rep: Reputation: 32
why would you do everything and then not re-run lilo? the 'make bzimage' AFAIK is not necessary, you can just copy the bzimage after you have done the make. one more thing, it's always a good practice to leave you old kernel config as it is for sometime. you could have very well copied the bzimage,.config and System.map into /boot and added relevant entries in lilo.conf. this way even if your new kernel fails to boot for some reason, you old kernel still remains useful and bootable. just my 2 cents.
 
Old 06-25-2006, 01:00 AM   #3
banjzooie
LQ Newbie
 
Registered: Feb 2006
Distribution: Slackware 10.2
Posts: 19

Original Poster
Rep: Reputation: 0
Thanks, I'll keep that in mind.

Problem solved--I was a moron and forgot to enable IDE chipset compatibility when I was configuring the 2.6.17.1 kernel. I kinda needed that if I wanted Linux to be able to see its own hard drive.

From all around Banjzooie are shouts of "DUH!!!"

I'll be more careful next time I'm configuring a kernel. Everything works great now.

Edit: I never removed the original kernel or its system.map and config. I only removed the symlinks to them. They still operated without modification to lilo.conf when I booted the old kernel with the old MBR (which contains the old lilo settings).

Last edited by banjzooie; 06-25-2006 at 01:03 AM.
 
Old 06-25-2006, 01:28 AM   #4
cereal83
Member
 
Registered: Feb 2004
Location: Canada
Distribution: Slackware
Posts: 478

Rep: Reputation: 30
if you do

make bzlilo; make modules; make modules_install

it will auto move vmlinuz and System.map into /boot for you and run lilo for you also and move the old kernel image to vmlinuz.old
 
Old 06-25-2006, 10:59 AM   #5
sundialsvcs
Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 5,455

Rep: Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172
Quote:
Originally Posted by banjzooie
Problem solved--I was a moron and forgot to enable IDE chipset compatibility when I was configuring the 2.6.17.1 kernel. I kinda needed that if I wanted Linux to be able to see its own hard drive.

From all around Banjzooie are shouts of "DUH!!!"
From all around Southeast Tennessee are mumbles of "uh huh, been there, done that..."

Q: Why do programmers have flat heads?
A: (Slap!) Doh!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
compiled kernel 2.6.10 with slackware 10.0, kernel panic salviadud Linux - Newbie 1 02-09-2005 05:05 PM
Kernel Panic with new kernel in slackware Omniscientist Linux - General 4 11-12-2004 02:21 PM
Slackware Kernel Panic! Heretic1 Linux - Newbie 0 10-27-2003 10:35 PM
Slackware 8.1 -- Kernel panic appler Slackware 4 03-19-2003 03:59 PM


All times are GMT -5. The time now is 09:28 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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration