LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
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 07-23-2005, 12:02 PM   #1
sund00bie
LQ Newbie
 
Registered: Jul 2005
Posts: 3

Rep: Reputation: 0
kernel Panic slackware 10.1 (sata) after upgrading to 2.6.10 pkg in /testing


Hi

Im currently having a problem booting into slackware after upgrading
to the 2.6.10 kernel pkg in /testing/

I had no problem booting into default 2.4 kernel but only encountered this
problem after upgrading.

This what i did from to my freshly installed 10.1 (2.4)
- mount /mnt/cdrom
- cd /testing/packages/linux-2.6.10/
- installpkg *.tgz
- cd /boot
- mkinitrd -c -k 2.6.10 -m reiserfs


This is the error i get from both slackware and slackware2610 (see my
lilo.conf below)

- /boot/initrd.gz: loading kernel modules form initrd image
- using /lib/modules/2.6.10/reserfs.ko
- VFS: Cannot open root device "85" or unkown-block (8,21)
- Please append a correct "root=" boot option
- Kernel panic - Not syncing VFS: Unable to mount root fd on unkown-block
- (8,21)

I can still load my 2.4 Slackware by booting from the cd with the folloing
command
- sata.i root=/dev/sdb5 noinitrd ro

Could some one please have a look at info provided and help me out

Thanking you very much


my du would look something like this
/music /dev/hda1
/dump /dev/sda1
/winblows /dev/sdb1
/ /dev/sdb5
/swap /dev/sdb6


Then i edited this to suit my needs then added it to lilo.conf

# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.10
initrd = /boot/initrd.gz
root = /dev/hda6
label = Linux2610
read-only
# Linux bootable partition config ends


Here is my lilo.conf

# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Windows bootable partition config begins
other = /dev/sdb1
label = Winblows
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sdb5
label = Slackware
read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.10
initrd = /boot/initrd.gz
root = /dev/sdb5
label = Slackware2610
read-only
# Linux bootable partition config
 
Old 07-23-2005, 12:23 PM   #2
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
Welcome to LQ!

Does your /etc/lilo.conf look like the lower one in your post?
Your / filesystem must be /dev/sdb5

I suspect that the new kernel you installed has no support
for your SATA drive. Did you check?

You must have these options in the kernel. I am only listing
the section headers and not all the entries.
Code:
# ATA/ATAPI/MFM/RLL support
#
# CONFIG_BLK_DEV_IDE_SATA is not set

# SCSI device support
#
CONFIG_SCSI=y

# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y  <-- if this is a module (m) and not built in (y), your kernel will panic and not boot 

# SCSI low-level drivers
#
CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_VIA=y  <-- this is my chipset, yours may be different 
I do not think those generic kernels include SATA support.
 
Old 07-23-2005, 09:17 PM   #3
sund00bie
LQ Newbie
 
Registered: Jul 2005
Posts: 3

Original Poster
Rep: Reputation: 0
Yes the posted lilo.conf is my lilo.conf and yes my file system is /dev/sdb5 as i stated in my df -h

Thanks for the info, i think your right and that the included kernel in /testing does not include sata support. So i understand y i cannot boot to my Slackware 2.6.10 kernel but y cannot i boot in2 my defult 2.4 kernel via lilo ??

I didnt make any changes to that kernel ?

so if i boot back into my 2.4 kernel by booting from cd and "#make menuconfig" this will edit my defult 2.4 rather then the 2.6.10 kernel right ?

If so, how can i boot into the 2.6.10 kernel (even via cd) so that i can customize the kernel and add SATA support ?


Thanking you

- Sund00bie
 
Old 07-23-2005, 10:45 PM   #4
lowpro2k3
Member
 
Registered: Oct 2003
Location: Canada
Distribution: Slackware
Posts: 340

Rep: Reputation: 30
Chinaman!

Thanks so much for that! I've been having huge trouble recompiling my default slack kernel from the CD (2.4.29), and that must be a reason. I don't mean to thread-hijack, but I've been through the 2.4.29 menu a jillion times and I can't find what you've mentioned.

I ran this command:
Code:
$ cd ~/linux-2.4.29
$ grep "SCSI_SATA" .config
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_SATA_AHCI is not set
# CONFIG_SCSI_SATA_SVW is not set
# CONFIG_SCSI_SATA_NV is not set
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_SX4 is not set
# CONFIG_SCSI_SATA_SIL is not set
# CONFIG_SCSI_SATA_SIS is not set
# CONFIG_SCSI_SATA_ULI is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
It seems like it should be under SCSI Support ---> SCSI Low Level Drivers, but I can't find Promise support anywhere, it just looks like a bunch of actual SCSI hardware. I'll keep looking, but if you have any hints it would be much appreciated. For now I'll move my current .config to a backup and make that change in the .config file, but I would hate to make a change like that and not know where it is in menuconfig.

Thanks alot.
 
Old 07-23-2005, 10:50 PM   #5
lowpro2k3
Member
 
Registered: Oct 2003
Location: Canada
Distribution: Slackware
Posts: 340

Rep: Reputation: 30
Quote:
Originally posted by sund00bie
If so, how can i boot into the 2.6.10 kernel (even via cd) so that i can customize the kernel and add SATA support ?
I could be wrong, but by the sounds of it since theres no SATA support in the default kernel, you'd need to download your own and compile it from source. I just set up my Slack system with SATA RAID 0 on 2 disks with a Promise SATA controller, and I know I need SATA support just to be able to see my disks. Personally I would save myself the headache, and use your 2.4 system to download the 2.6 kernel and required updates (I heard you should update udev and a few other things, see the kernel recompile sticky) and basically use your working 2.4 kernel as your environment.

I could be wrong and maybe theres a way to customize the kernel on the CD, I dont know much at all about the Slackware package management stuff. But if you cant somehow customize the kernel to add SATA support you'll probably need to do what I listed above, which really shouldnt be too bad anyways.

Good luck!
 
Old 07-24-2005, 12:10 AM   #6
sund00bie
LQ Newbie
 
Registered: Jul 2005
Posts: 3

Original Poster
Rep: Reputation: 0
Thanks for all the prompt responses.

As stated i think ill go back to to the 2.4 kernel (reinstall) then do a fresh install of the latest kernel with Promise Sata inlcuded.

Thanks again

Pce
 
Old 07-24-2005, 10:43 PM   #7
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
Quote:
Originally posted by sund00bie
Thanks for all the prompt responses.

As stated i think ill go back to to the 2.4 kernel (reinstall) then do a fresh install of the latest kernel with Promise Sata inlcuded.

Thanks again

Pce
If you haven't reinstalled yet, post back and tell us. We'll tell you how to do it easier.

I don't know what you're referring to reinstalling. If it's the kernel, okay ... maybe. If it's the OS, post back afterwards and we'll teach you the *nix way (shucks, it's broken, let's find out what broke and fix it), rather than the Windoze way (shucks, it's broken, let's reinstall the OS).

No matter what, we'll get you going with Slackware.
 
Old 07-25-2005, 04:59 AM   #8
isis
LQ Newbie
 
Registered: Oct 2003
Location: Saarland, Germany
Distribution: Slackware
Posts: 22

Rep: Reputation: 15
Had a similar issue:

You just have to recompile the kernel with modules for your sata-controller integrated ( scsi low level driver ) and to be sure the support for the filesystem.

finally make
make modules_install
make install

lilo

And it should work.
 
  


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
Kernel panic upgrading from 2.4.31 to 2.6.13 Sushy Slackware 8 12-03-2006 05:50 PM
kernel panic on SATA paranoyakX Debian 5 07-07-2006 01:45 PM
Kernel panic - SATA support in 2.6 and slackware vmt1 Slackware 7 12-01-2005 01:55 PM
2.4.27 kernel panic after testing upgrades farpoint Debian 2 06-22-2005 08:09 AM
SATA kernel panic N3K0KUN Slackware 1 02-25-2004 12:22 PM


All times are GMT -5. The time now is 09:26 AM.

Main Menu
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