LinuxQuestions.org
Review your favorite Linux distribution.
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
 
LinkBack Search this Thread
Old 02-13-2013, 07:54 PM   #16
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 836

Rep: Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620

Quote:
Originally Posted by Yaakov Ben-Avraham View Post
# uname -a

Linux eyes 2.6.37.6 #2 Sun Apr 10 01:09:12 CDT 2011 i686 Intel(R) Pentium(R) III CPU-S 1400 MHz GenunineIntel GNU/Linux

I am running the non-SMP kernel because Slackware 14.0 HUGESMP.S image hangs
when booting from DVD (Slackware 13.37 HUGESMP.S works from DVD)

This was a fresh installation on a virgin disk.
Impossible. You're not running the kernel that came with Slackware 14.0.
 
Old 02-14-2013, 12:12 AM   #17
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware-14.0 on a Lenovo T61 6457-4XG
Posts: 3,654

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
I can hardly imagine how you got there. Maybe you had Slackware 13.37 previously installed, you didn't wipe it out before installing Slackware 14 (that is to say, you told the installer not to format your root partition) and you didn't run lilo during the configuration post-installation. I may be fully wrong, but please send output of following command, to check:
Code:
ls -l /boot
PS Not sure if it is important but tell us what is your hard disk's lay-out as well (outputs of cat /etc/fstab or cat /proc/partitions and df -h). Just wondering: if you have a separate /boot partition, maybe you didn't reformat that one.

PS2 Maye be you kept the old kernel (this we know for sure as that's what output of "uname -a" shows) and during installation you chose the "expert" mode of liloconfig and reused your old lilo.conf?

In any case I'd try running the commands Mr. Volkerding gave you in post #12. Do not forget to run lilo after that, with an entry for a 3.2.29 kernel.

Or if your system is even more messed up, reinstall everything -- then, after having saved what you want to keep, do accept to reformat the relevant partitions this time when asked by the 'setup' program.

Last edited by Didier Spaier; 02-14-2013 at 06:41 AM. Reason: PS added
 
Old 02-14-2013, 07:16 AM   #18
Yaakov Ben-Avraham
LQ Newbie
 
Registered: Jan 2013
Location: Vancouver, Canada
Distribution: Slackware 14.0
Posts: 25

Original Poster
Rep: Reputation: Disabled
Smile

Quote:
Originally Posted by Didier Spaier View Post
PS2 Maye be you kept the old kernel (this we know for sure as that's what output of "uname -a" shows) and during installation you chose the "expert" mode of liloconfig and reused your old lilo.conf?
THANK YOU !!!

I did exactly that. My Lilo.conf had an entry that read

image = /boot/vmlinuz

which pointed to the wrong image. Changing this entry to

image = /i/boot/vmlinuz

solved the problem, since the correct image was in directory /i/
 
Old 02-14-2013, 07:22 AM   #19
Yaakov Ben-Avraham
LQ Newbie
 
Registered: Jan 2013
Location: Vancouver, Canada
Distribution: Slackware 14.0
Posts: 25

Original Poster
Rep: Reputation: Disabled
Smile

Quote:
Originally Posted by volkerdi View Post
You missed the output of "uname -a", which would allow us to see if for some reason you were still running an old kernel.

Was this a fresh installation, or did you install over the top of something that was already there? If the latter, that could lead to all kinds of problems... but, if so, adding --reinstall to that upgradepkg command line would still be able to help clean up the mess, along with the suggestions in UPGRADE.TXT for removing obsolete packages and handling .new config files.
PROBLEM SOLVED - THANK YOU !!!

I was running the "expert" mode of LiLo, and had the line

image = /boot/vmlinuz

which booted the wrong image. I corrected this line to

image = /i/boot/vmlinuz

since the correct boot image was in directory /i/
 
  


Reply

Tags
32-bit, modules, smp


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
modprobe: FATAL: Could not load /lib/modules/.../modules.dep Ankardo Debian 9 02-01-2011 05:09 PM
Slackware 13.1 huge smp is not huge cs_strong Slackware 4 11-16-2010 07:41 AM
Cant load modules for usb in SlackWare 12.2 mike1312 Slackware 2 01-07-2009 05:17 PM
Modules wont load, slackware 10.2 lrolstad Linux - Laptop and Netbook 5 09-15-2006 04:15 AM
FATAL: Could not load /lib/modules/2.6.14-default/modules.dep no such file exist dr_zayus69 Linux - Software 3 12-26-2005 06:44 PM


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