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 03-26-2004, 03:04 PM   #1
Glock Shooter
Member
 
Registered: Jan 2002
Location: Riverside, CA
Distribution: Slackware Convert!!
Posts: 210

Rep: Reputation: 30
Slack 9.1 won't boot after Swaret upgrade


I updated my system after not having done so if a very long time. According to swaret it updated the kernel. Now after selecting linux from lilo, it just stays on loading kernel and hangs. Did I forget to do something?
 
Old 03-26-2004, 03:09 PM   #2
hp_tux
Member
 
Registered: Mar 2004
Location: Germany
Distribution: Slackware 14
Posts: 87

Rep: Reputation: 15
Hello,

Quote:
it just stays on loading kernel and hangs
mmh, could you describe that a bit more precisely?

cu

hp_tux
 
Old 03-26-2004, 03:19 PM   #3
320mb
Senior Member
 
Registered: Nov 2002
Location: pikes peak
Distribution: Slackware, LFS
Posts: 2,577

Rep: Reputation: 47
We need more info....like what if any errors messages are you getting??
 
Old 03-26-2004, 03:28 PM   #4
mrcheeks
Senior Member
 
Registered: Mar 2004
Location: far enough
Distribution: OS X 10.6.7
Posts: 1,690

Rep: Reputation: 50
don't let a tool update your kernel...it could forget to load for exemple module for jfs filesystem or not include it if you have jfs = hangs on boot.
It could forget or add modules you don't even need.
compile the kernel if you want to update it.

rescue your disk and after compile a new kernel or get the old one back or load the old one by default if you don't want to compile it
 
Old 03-26-2004, 05:04 PM   #5
Glock Shooter
Member
 
Registered: Jan 2002
Location: Riverside, CA
Distribution: Slackware Convert!!
Posts: 210

Original Poster
Rep: Reputation: 30
There is no error message, it says loading kernel and just sits there. No kernel panic as I can ctr alt delt to reboot.
 
Old 03-26-2004, 05:41 PM   #6
hp_tux
Member
 
Registered: Mar 2004
Location: Germany
Distribution: Slackware 14
Posts: 87

Rep: Reputation: 15
Hello,

and now you can only start a rescue system and repair your installation!

Good Luck!

cu

hp_tux
 
Old 03-26-2004, 09:23 PM   #7
Azmeen
Senior Member
 
Registered: May 2003
Location: Malaysia
Distribution: Slackware, LFS, CentOS
Posts: 1,307

Rep: Reputation: 46
OK, maybe I can help here a bit.

First of all, I pray that you have some form of Linux rescue CD or floppy (eww) available. I think the first Slack CD would suffice as well.

Once you've booted the CD, there should be a /tmp directory available. This dir is usually mapped into your RAM and is used as a temporary working space for files used in installation, for example.

One good thing about this dir is that it is the only writable dir on your temporary filesystem, therefore, you can use it to mount your "real" filesystems on your hard discs.

Assuming that you have a single / (root partition) using some part of your hard disc (in this case i'll assume it's /dev/hda1), you'd merely need to mount it.

So do these steps:

Code:
cd /tmp
mkdir slack
mount /dev/hda1 slack/
At this point you should check to see if the partition is mounted properly. Just take a look at the /tmp/slack directory, and traverse through some familiar dirs, such as your homedir for example.

If it is correct, then you should chroot to this dir:

Code:
chroot /tmp/slack
Now, you should already be in your slack partition as if you actually booted into it.

I'd suggest you check your lilo.conf file and make sure the entries are correct. After that, just run /sbin/lilo and try rebooting.

If it's a problem due to a kernel upgrade, you should now (at least) be able to boot up.

Hopefully this solves your problem.
 
Old 03-26-2004, 10:00 PM   #8
chopp
Member
 
Registered: Sep 2003
Location: AB. Canada
Distribution: Slackware
Posts: 126

Rep: Reputation: 16
Azmeen

Sorry to butt in here, but you seem to have good advise.

Code:
chroot /tmp/slack
what is the chroot command used for?

cheer's
chopp
 
Old 03-26-2004, 10:56 PM   #9
Azmeen
Senior Member
 
Registered: May 2003
Location: Malaysia
Distribution: Slackware, LFS, CentOS
Posts: 1,307

Rep: Reputation: 46
chroot is short for change root directory.

eg. If you have a dir called /test, and you run chroot /test, you will then be put in /test, as if it was your root directory.

ie. the contents of / will be the contents of /test

chroot is useful if you can't boot your OS, but still have the necessary system files in place... for example, lilo problems.

It can also be used to "jail" users into a sandbox or safe area of your hard disk. So, let's say they do some serious damage to the system, it will only limit it to their particular "jail"... But this should be a discussion on an altogether different thread
 
Old 03-26-2004, 11:33 PM   #10
ringwraith
Senior Member
 
Registered: Sep 2003
Location: Indiana
Distribution: Slackware-current
Posts: 1,244

Rep: Reputation: 47
Why couldn't he just boot from the CD. At the first prompt type in per the instruction to boot from your root partition. Then type lilo.
 
Old 03-26-2004, 11:53 PM   #11
Glock Shooter
Member
 
Registered: Jan 2002
Location: Riverside, CA
Distribution: Slackware Convert!!
Posts: 210

Original Poster
Rep: Reputation: 30
Running /sbin/lilo fixed it after booting from the slack cd. I've done that before but I haven't booted inot linux in over 3 months....it's all slowly coming back to me now. Thanks for the help.
 
Old 03-27-2004, 07:20 AM   #12
moonloader
Member
 
Registered: Nov 2003
Location: linuxquestions.org
Distribution: Linux and BSD
Posts: 229

Rep: Reputation: 30
I think your lilo.conf can't find boot image after you upgraded.go to KDE control center and lilo.conf in administrator mode probe the the image then accpet.it will work then
 
Old 03-27-2004, 09:44 AM   #13
r_jensen11
Senior Member
 
Registered: Apr 2003
Location: Minnesota, USA
Distribution: Slack 10.0 w/2.4.26
Posts: 1,032

Rep: Reputation: 45
This is one of many reasons why I have about 6 different kernel options for my system. If the newest one doesn't work, I can just fall back to an older one and try again.
 
  


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
upgrade to 10.0 or use swaret? Axion Slackware 5 06-17-2004 10:32 AM
Strange error messages on boot after swaret --upgrade swinchen Slackware 4 04-24-2004 12:49 PM
Upgrade of Slack Gnome to current via swaret justaguynsrq Slackware 8 04-07-2004 06:38 AM
can,t boot slack after kernel upgrade. little_ball Slackware 3 03-30-2004 06:40 PM
Slack 9.0- upgrade to 9.1 or just Swaret to Current? Frank_Drebin Slackware 1 03-11-2004 11:53 PM


All times are GMT -5. The time now is 11:07 PM.

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