LinuxQuestions.org
Visit Jeremy's Blog.
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 08-12-2004, 08:23 PM   #1
Repeater
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware 10
Posts: 22

Rep: Reputation: 15
Kernel Panic error after 2.6.7 compile - please help


I've just finished compiling 2.6.7 on Slackware 10 but when I reboot I get the following error.

Kernel panic : VFS: Unable to mount root fs on unknown-block(8,3)

My root file system is mounted on an Ext2 partition on sda3. Do I have to edit any files to include 'root=/dev/sda3' as they may be set to hda1? I'm pretty sure I checked the right options in the menuconfig to enable support for Ext2. My compile went smoothly (I followed a number of excellent guides in the forums here) and it starts to boot fine until it gets to the error. I've searched the forums and have found similar posts but they didn't help me. I decided to post here in case it has anything to do with slackware. Please help.
 
Old 08-12-2004, 08:48 PM   #2
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198
Have you checked the config file for your bootloader?
Have you successfully upgraded a kernel before? (say 2.6.6?)

Simon
 
Old 08-12-2004, 08:52 PM   #3
slackerboy
Member
 
Registered: Jul 2002
Location: USA
Distribution: Slackware, OpenSuse, Debian, Linux Mint, Ubuntu, Red Hat EL
Posts: 70

Rep: Reputation: 15
Did you run /sbin/lilo as the last step in your compilation?

Also, can you get in your system via a floppy? (I hope you made one )
 
Old 08-13-2004, 02:49 AM   #4
Repeater
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware 10
Posts: 22

Original Poster
Rep: Reputation: 15
"Have you checked the config file for your bootloader?"

Do you mean menuconfig? My bootloader is LILO and it seems to be working : ie it dual-boots between windows and Linux properly. Also I've checked the 'lilo.conf' file and it seems to be ok.

"Have you successfully upgraded a kernel before? (say 2.6.6?)"

No. this is my first kernel compile. I was using the 2.4.26 kernel that came with the installation. I did compile the kernel before, but in a seriously reduced capacity. I forgot to check some important fields at the 'make menuconfig' stage.

"Did you run /sbin/lilo as the last step in your compilation?"

No. I ran it now to see if it would work but it didn't. I think I saw the same output it created (Added Windows, added linux etc.) during the main compile though. Would I have to recompile before running /sbin/lilo?

"Also, can you get in your system via a floppy? (I hope you made one )"
Yeah I've made the floppy (I've learned the hard way before) and have since performed a recompile but to no avail.
 
Old 08-13-2004, 03:50 AM   #5
Cedrik
Senior Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140

Rep: Reputation: 244Reputation: 244Reputation: 244
As it seems that you use scsi hard drive, make sure that you compiled scsi support and scsi driver for your controler as built-in.

What is your output for :

perl -ne 'print if /^([^#]).*(scsi)/i' /usr/src/linux/.config

(assuming you did the symlink /usr/src/linux that point to your 2.6.7 source tree)

Last edited by Cedrik; 08-13-2004 at 03:54 AM.
 
Old 08-13-2004, 06:12 AM   #6
Repeater
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware 10
Posts: 22

Original Poster
Rep: Reputation: 15
I use a SATA hard drive which I believe 2.6.7 supports. I think I saw some files containing the word sata being listed during the compile. I don't use a SCSI drive. I still tried entering the above line but got an error message. However without the square brackets I got the following output.

# SCSI device support
# SCSI support type (disk, tape, CD-ROM)
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# SCSI Transport Attributes
# SCSI low-level drivers
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
# CONFIG_SCSI_EATA_TAGGED_QUEUE is not set
# CONFIG_SCSI_EATA_LINKED_COMMANDS is not set
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
# CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
# CONFIG_SCSI_QLOGIC_FC_FIRMWARE is not set
# PCMCIA SCSI adapter support
 
Old 08-13-2004, 07:13 AM   #7
Cedrik
Senior Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140

Rep: Reputation: 244Reputation: 244Reputation: 244
Hey that is precisely what I wanted to avoid : all lines beginning by #

The perl command above works for sure, you surelly did a typo, why not just copy & paste it in a terminal ?

Now that we know that you have a sata disk, what is the output for :

cat /usr/src/linux/.config | grep -i sata
 
Old 08-13-2004, 09:46 PM   #8
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198
Repeater: Cedrik is guiding you down one path - based on some assumptions which may be all to the good. Follw that too, but I have a niggle... this exact thing happened to me during my first kernel ugrade attempt. In my case, the origin was a misidentified root partition as you have suggested in your first post.

Since you are using lilo, it wouldn't hurt to take a sqiz at /boot/lilo.conf to see what it says. You should see an entry for windows, an entry for the 2.6.7 kernel and (hopefully it isn't erased) an entry for the old kernel as well. Compare the old kernel entry to the new one and look what is different - paying especial attention to anything that looks like a root partition ID.

This shouldn't take long.

Cedrik thought you had an scsi hdd because you said the root partition was sda3 and sda would ordinarily denote a scsi hdd, while hda3 would be an ide hdd. (just making sure you two are talking the same language here.)

As a pointer - should you ever recompile, use the option to save the config options to a file and keep it where you can easily find it again (like /root) that way you'll never have to wrack your brains to remember if you've checked that pesky option.

Cheers
Simon
 
Old 08-14-2004, 03:50 AM   #9
Repeater
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware 10
Posts: 22

Original Poster
Rep: Reputation: 15
I never checked the option for NTFS support in the menuconfig and my windows (XP) paritition is visible to linux and mounted on /dev/sda1. Could this have been the problem? Anyway my boot disk got corrupted and I had to do a complete reinstall. Doesn't really matter, though, as I've only recently installled Slackware 10. I'll keep this thread open for a while, in case the same thing happens after I compile 2.6.7 now.
 
Old 08-15-2004, 03:11 AM   #10
suslik
Member
 
Registered: Jul 2004
Distribution: OpenSuse 10.x
Posts: 262

Rep: Reputation: 30
I didn't know that SATA devs show up as /dev/sd*. I would expect /dev/hd*.

Can someone colaborate on that?
 
Old 08-22-2004, 06:23 PM   #11
Repeater
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware 10
Posts: 22

Original Poster
Rep: Reputation: 15
Hi. Back again. I've been having problems compiling the kernel ever since. I'm attempting to compile 2.6.8.1 now and I'm getting the exact same error as I was in the initial post. To answer earlier questions these are my outputs for the following commands.

perl -ne 'print if /^([^#]).*(scsi)/i' /usr/src/linux/.config

CONFIG_BLK_DEV_IDESCSI=m
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_SCSI_AIC79XX=m
CONFIG_SCSI_DPT_I2O=m
CONFIG_SCSI_MEGARAID=m
CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_SVW=y
CONFIG_SCSI_ATA_PIIX=y
CONFIG_SCSI_SATA_NV=y
CONFIG_SCSI_SATA_PROMISE=y
CONFIG_SCSI_SATA_SX4=y
CONFIG_SCSI_SATA_SIL=y
CONFIG_SCSI_SATA_SIS=y
CONFIG_SCSI_SATA_VIA=y
CONFIG_SCSI_SATA_VITESSE=y
CONFIG_SCSI_BUSLOGIC=m
CONFIG_SCSI_DMX3191D=m
CONFIG_SCSI_EATA=m
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_EATA_PIO=m
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
CONFIG_SCSI_IZIP_EPP16=y
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_IPR=m
CONFIG_SCSI_QLOGIC_ISP=m
CONFIG_SCSI_QLOGIC_FC=m
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA2XXX=y
CONFIG_SCSI_QLA21XX=m
CONFIG_SCSI_QLA22XX=m
CONFIG_SCSI_QLA2300=m
CONFIG_SCSI_QLA2322=m
CONFIG_SCSI_QLA6312=m
CONFIG_SCSI_QLA6322=m
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_NSP32=m
CONFIG_SCSI_DEBUG=m
CONFIG_PCMCIA_NINJA_SCSI=m
CONFIG_I2O_SCSI=m


cat /usr/src/linux/.config | grep -i sata

CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_SVW=y
CONFIG_SCSI_SATA_NV=y
CONFIG_SCSI_SATA_PROMISE=y
CONFIG_SCSI_SATA_SX4=y
CONFIG_SCSI_SATA_SIL=y
CONFIG_SCSI_SATA_SIS=y
CONFIG_SCSI_SATA_VIA=y
CONFIG_SCSI_SATA_VITESSE=y

Please help if you can.
 
  


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
Trying to compile 2.6.8 getting Kernel Panic when booting Tristor Red Hat 2 01-13-2005 01:35 AM
Kernel panic after 2.6.1 compile Phaethar Fedora 6 01-14-2004 10:55 PM
kernel panic after compile RIgimp75 Slackware 1 01-09-2004 07:46 PM
Kernel panic: A blown compile? Hangdog42 Slackware 14 03-21-2003 03:50 PM
kernel compile, user PANIC! antken Linux - General 4 01-26-2001 08:06 AM

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

All times are GMT -5. The time now is 09:17 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