Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 01-20-2010, 11:48 AM   #1
Lenard Spencer
Registered: Sep 2004
Location: Florida
Distribution: Slackware, Linux from Scratch
Posts: 293

Rep: Reputation: 117Reputation: 117
Kernel panic after upgrading slackware64-current to 2.6.32.x kernel

I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:

# Linux bootable partition config begins
image = /other/spare4/boot/vmlinuz
  root = /dev/hdc4
  label = Slackware64
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
I have already tried changing to "root = /dev/sdc4" but lilo errors out trying to install. I cannot upgrade this machine to SATA because it is an older mobo with SATA 1 ports, and will not recognize SATA 2.

What do I need to add to be able to boot this partition? Thanks.

Last edited by Lenard Spencer; 01-20-2010 at 11:53 AM. Reason: additional information
Old 01-20-2010, 12:37 PM   #2
Registered: Aug 2009
Posts: 112

Rep: Reputation: 18
Were you using the default included kernel before? The upgrade kernels given most often need an initrd if you don't want to compile (for me it was ext3 support... had a heck of a time figuring that one out.) it yourself (which I recommend, by the way. just look it up in the slackbook is what I did. It's not as hard as you think. Just remember the framebuffer driver <grin>).

I don't know why the upgrades kernels differ from the prepackaged ones, but they do. They're much more generic.

Although... I hope someone else chimes in because I don't have any experience with -current. This was all on 12.2
Old 01-20-2010, 12:44 PM   #3
Alien Bob
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,527

Rep: Reputation: 7942Reputation: 7942Reputation: 7942Reputation: 7942Reputation: 7942Reputation: 7942Reputation: 7942Reputation: 7942Reputation: 7942Reputation: 7942Reputation: 7942
If you need to fix up your Slackware after the kernel update where hda became sda then may be a useful piece of reading for you.
Old 01-22-2010, 09:56 AM   #4
LQ Newbie
Registered: Nov 2008
Location: Elbląg, Poland
Distribution: Slackware64-current
Posts: 22

Rep: Reputation: 16
The same issue one guy posted on Polish slackware forum. He resolved it by:
On slack 12.2:
# mknod /dev/sda b 8 0 
# mknod /dev/sda1 b 8 1
and then:
image = /dev/sda1
Or on slackware-current:
# mknod /dev/hda b 3 0 
# mknod /dev/hda2 b 3 2
an then
image = /dev/hda2
And refresh lilo.
Old 01-22-2010, 10:54 AM   #5
LQ Veteran
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,511

Rep: Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077
edit /etc/fstab change hda entries to sda


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
[SOLVED] Slackware64-current Kernel No sound on CLI and in Browsers gargamel Slackware 10 01-13-2010 01:33 AM
Slackware64-current missing kernel headers? UpAndUp Slackware 2 08-26-2009 07:08 PM
[SOLVED] Latest slackware64-current xorg and kernel update woes veeall Slackware 10 07-19-2009 12:31 AM
[SOLVED] Problem with kqemu in slackware64-current since kernel niels.horn Slackware 3 06-20-2009 04:27 PM
upgrading Fedora Core 3 kernel 2.6.9-1.667 to manually+kernel panic error LinuxLovinNoob Linux - Newbie 7 12-17-2008 08:45 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:35 AM.

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