LinuxQuestions.org
Help answer threads with 0 replies.
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 05-20-2010, 10:41 AM   #1
jodef
LQ Newbie
 
Registered: Jan 2004
Posts: 7

Rep: Reputation: 0
Slackware 13 -> Current ,Kernel Panic On Reboot


Hi all

I attempted to upgrade a Slackware 13.0 fresh install to current.

First I updated 13.0 by running:
Code:
slackpkg update
slackpkg upgrade-all
I then amended the mirror to current and ran the following commands
Code:
slackpkg update
slackpkg upgrade-all
Everything ran without errors and slackpkg updated lilo at the end w/out errors on reboot I get the following message:
Code:
Cannot open root device 301 or unknown-block(3,1)
append a correct root= boot option
0800 10485760 sda driver sd
0801 9765472 sda1
0802 720216  sda2
I am running Slack in vbox to learn I created a snapshot just before rebooting so I restored it and tried to amend lilo with sda instead of hda and when I ran lilo -v indicated sda was an invalid parameter.

Not new to linux can find my way around albeit with stumbling but not an expert either.

Can anyone point me in the right direction.

Thanks.
 
Old 05-20-2010, 10:57 AM   #2
smoooth103
Member
 
Registered: Aug 2009
Location: NC, USA
Distribution: Slackware (64 bit)
Posts: 238

Rep: Reputation: 60
There is change in how the newer kernel that deprecates the /dev/hda style harddrive references. You must boot and during the lilo start, "hit tab" and set the boot drive to be "root = /dev/sda1" (or which ever partition) and then after the kernel loads, change your /etc/fstab to reference /dev/sda instead of /dev/hda or /dev/sdb instead of /dev/hdb. Also you will need to change in lilo.conf and then re-run lilo so that it recognizes. There is a changelog entry about how to do this, and also a detailed howto by Robby Workman, just need to look around for it a bit.
 
Old 05-20-2010, 11:15 AM   #3
slackd
Member
 
Registered: Sep 2009
Location: Bhubaneswar, India
Distribution: Slackware, Ubuntu, Windows
Posts: 260
Blog Entries: 1

Rep: Reputation: 60
Thumbs up

Quote:
Originally Posted by smoooth103 View Post
just need to look around for it a bit.
jodef,

There you go..read <this> thoroughly!
 
Old 05-20-2010, 10:33 PM   #4
jodef
LQ Newbie
 
Registered: Jan 2004
Posts: 7

Original Poster
Rep: Reputation: 0
Ok guys thanks for the fast response I have made some progress but still experiencing some difficulties:

Step 1: Edited fstab to change hd* -> sd*

Step 2: Downloaded util-linux-ng installed did updatedb and rebooted (see note)

Note:I experienced a missing libblkid.so.1 preventing filesystem mount this link help me solve that problem : http://eatingsecurity.blogspot.com/2...t-updates.html

Step 3:
Code:
Linux root=/dev/sda1
started the boot process

Now I get stuck at some errors when starting X session lib missing libck-connector.so.0

Question are these problems just part of the process or did something go wrong with the update process. Can they be resolved or should I start again with a fresh install?

Thanks.
 
Old 05-20-2010, 10:56 PM   #5
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,578

Rep: Reputation: 468Reputation: 468Reputation: 468Reputation: 468Reputation: 468
Your slackpkg commands as you have given would not install any of the new packages that are in -current, nor would it remove those packages that are obsolete.

It's really important to read the CHANGES_AND_HINTS.TXT file in the new release prior to upgrading as well as UPGRADE.TXT so that you'll know what additional steps to take.

I would boot into runlevel 1 and follow the steps given in UPGRADE.TXT if I were you.
 
Old 05-20-2010, 11:07 PM   #6
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
When upgrading to current, don't forget
Code:
slackpkg install-new
 
Old 05-20-2010, 11:46 PM   #7
jodef
LQ Newbie
 
Registered: Jan 2004
Posts: 7

Original Poster
Rep: Reputation: 0
Ok no problem I'll read the upgrade and changes and hints completely forgot to do that.

Just one question you mentioned install-new and I did see that step but when I did upgrade-all I saw packages being removed and new packages being installed. The kernel was also upgraded which seems to indicate that install-new wasn't necessary.

Did I miss something?

Thanks.
 
Old 05-20-2010, 11:52 PM   #8
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
Quote:
Originally Posted by jodef View Post
Ok no problem I'll read the upgrade and changes and hints completely forgot to do that.

Just one question you mentioned install-new and I did see that step but when I did upgrade-all I saw packages being removed and new packages being installed. The kernel was also upgraded which seems to indicate that install-new wasn't necessary.

Did I miss something?

Thanks.
Upgrade-all will upgrade packages, such as the kernel. Install-new will install packages that were not part of the previous install, such as the xf86-video-nouveau-blacklist-noarch-1.txz package that blacklists the nouveau driver. The nouveau driver didn't exist in the 2.6.29.6 kernel so there was no xf86-video-nouveau-blacklist-noarch-1.txz package to blacklist it. That package was new and would be added with install-new.
 
1 members found this post helpful.
Old 05-21-2010, 12:19 AM   #9
jodef
LQ Newbie
 
Registered: Jan 2004
Posts: 7

Original Poster
Rep: Reputation: 0
Thanks that clarifies a lot. And after reading the upgrade and changes and hints the stuff I have read really oversimplify the upgrade process. I should have read this before.

Ok so having read the above it refers particularly to upgrading from a CD but if I am doing it via the internet what would I need to do differently aside from selecting the current mirror.

Thanks.
 
Old 05-21-2010, 09:20 AM   #10
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
http://distrowatch.com/weekly.php?issue=20090518 is what I read when I decided to start running current. The clean-system can remove the out-of-tree packages you've installed (I've been told) so be careful with that. Also there is the libata change and Robby's tutorial to fix it to be aware of. The easies way to get current installed is to use Alien Bob's mirror-slackware-current script that will also produce ISO's of current so you can just do a clean install of current.
 
  


Reply

Tags
kernel, slackware


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 after upgrading slackware64-current to 2.6.32.x kernel Lenard Spencer Slackware 4 01-22-2010 11:54 AM
Slackware-current 20080429: Kernel panic psynot Slackware 4 05-02-2008 04:57 AM
kernel panic on reboot of newly compiled kernel lyceum Linux - Newbie 4 09-09-2003 10:40 AM
Kernel panic on reboot runny_yolk Linux - General 0 10-04-2002 11:12 PM
Kernel Panic after reboot Spock Linux - General 8 08-27-2002 10:38 AM


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