LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 10-28-2007, 09:59 AM   #1
Twister512
Member
 
Registered: Nov 2005
Location: Mansfield, PA
Distribution: Slackware
Posts: 97

Rep: Reputation: 15
problems after using slackpkg


Hey guys. I just ran slackpkg, with my updates set to use the -current mirror. Everything downloaded and installed fine, and after it was all done it suggested that I run LILO. I ran LILO and it gave a warning about "assuming LBA32" or something like that. Now when I reboot my machine, it says

"Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)"

and thats all she wrote.

I can still boot to my old kernel and view my LILO.conf and nothing in there has changed at all.

Any suggestions?

Thanks, Paul
 
Old 10-28-2007, 10:08 AM   #2
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Rep: Reputation: Disabled
As the slackpkg documentation says "# Automated upgrade of kernel packages aren't a good idea ".

Brian
 
Old 10-28-2007, 10:24 AM   #3
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,546

Rep: Reputation: 419Reputation: 419Reputation: 419Reputation: 419Reputation: 419
did you forgot to make initrd??
 
Old 10-28-2007, 10:24 AM   #4
Twister512
Member
 
Registered: Nov 2005
Location: Mansfield, PA
Distribution: Slackware
Posts: 97

Original Poster
Rep: Reputation: 15
pretty much a lost cause then?
 
Old 10-28-2007, 11:15 AM   #5
Twister512
Member
 
Registered: Nov 2005
Location: Mansfield, PA
Distribution: Slackware
Posts: 97

Original Poster
Rep: Reputation: 15
when I installed my 2.6 kernel initially I never made a initrd, and its been working fine all this time. I guess it just slipped my mind about the kernel packages too. If its going to be a pain to try and fix I can just re-install the system. I was just trying to see if there was a solution to what I have messed up.
 
Old 10-28-2007, 11:41 AM   #6
titopoquito
Senior Member
 
Registered: Jul 2004
Location: Ruhr Area, Germany
Distribution: Slackware64 14.0
Posts: 1,517

Rep: Reputation: 90
I think you can try to install the huge kernel and the modules if you don't have them right now from current even when you have booted your old kernel. You have to take care that your lilo config file points to the old kernel, not only "vmlinuz" because installing the kernel package will make "vmlinuz" a symlink to the newly installed kernel. And append lilo.conf for the new kernel, before rerunning /sbin/lilo of course.

Since the "huge" kernel should have all usual file systems compiled in you can boot it. I guess the kernel you're booting with is the "generic" kernel ...
 
Old 10-28-2007, 12:28 PM   #7
Twister512
Member
 
Registered: Nov 2005
Location: Mansfield, PA
Distribution: Slackware
Posts: 97

Original Poster
Rep: Reputation: 15
so I could probably just download the new kernel, which has been partially upgraded anyway by slackpkg and just do a normal "new kernel" install? either way, this is pretty much just a learning system I am running anyways, so I can get the ins and outs figured out.

Thanks
 
Old 10-28-2007, 12:45 PM   #8
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Rep: Reputation: Disabled
You have quite a few choices. You don't need to reinstall everything.

First, a comment about using -current. In Slackware -current is the development version and is not stable. If you are learning, you'd be much better off with the stable version (12.0 is the most recent).

Okay, having said that, your choices are:

1. Continue using your old kernel
2. Try to install the most recent generic kernel (and modules) from whichever tree you decide to use (-current or 12.0) and create the initrd per instructions
3. Compile your own kernel

Do not use the -huge kernels, as they are primarily for installation purposes. The recommendation is to switch to -generic once your system is installed.

Brian
 
Old 10-28-2007, 12:46 PM   #9
titopoquito
Senior Member
 
Registered: Jul 2004
Location: Ruhr Area, Germany
Distribution: Slackware64 14.0
Posts: 1,517

Rep: Reputation: 90
What I would probably do (please check yourself if it makes sense):
  • Adjust lilo.conf so that you get a new entry for your old kernel that points to the full name, not only vmlinuz, for example it could point to vmlinuz-huge-smp-2.6.21.5-smp. if you have already referenced the long name you can skip this step and the next I think
  • run /sbin/lilo and reboot to see if your modified lilo.conf entry is working properly
  • get one of the "huge" kernels from current, either smp or without it and also download the modules
  • install these two, not with "upgradepkg" but with "installpkg", else your old kernels modules might get removed and also the kernel itself. or use tar to unpack the kernel and image files in a seperate folder and copy them over manually, as you like
  • append a new entry to lilo.conf for that kernel, run /sbin/lilo, reboot and pray
 
Old 10-28-2007, 12:48 PM   #10
titopoquito
Senior Member
 
Registered: Jul 2004
Location: Ruhr Area, Germany
Distribution: Slackware64 14.0
Posts: 1,517

Rep: Reputation: 90
Quote:
Originally Posted by BCarey View Post
Do not use the -huge kernels, as they are primarily for installation purposes. The recommendation is to switch to -generic once your system is installed.
IMHO it won't do any harm to use the huge kernel at least to get your system working with the new kernel. You can do a custom compile later without any problem. This way Twister512 can first forget about an initrd.
 
Old 10-28-2007, 01:20 PM   #11
digger95
Member
 
Registered: Oct 2007
Location: Indiana, PA
Distribution: Slackware 14
Posts: 330

Rep: Reputation: 45
Hi Paul,

I'm brand new here (two-week old linux newbie) and I just went through the exact same thing myself. The generic kernels don't have the filesystem built into the kernel like the huge ones do so that's why you got the kernel panic.

You just need to make an initrd like the others said above. This loads your filesystem module before linux loads. Piece of cake. If I can do it anyone can.

Pat's instructions in /boot/readme.initrd are pretty good. I just copied one of his examples and substituted my correct boot partition.

As far as the lba32 warning that's actually harmless. You can simply add "lba32" in /etc/lilo.conf under global (minus the quotes) and that message will go away.

Running with the default huge kernel is fine to get up and running, but it loads SO much stuff that I had conflicts with device drivers. I switched to the generic kernel pretty quickly.

Good luck,

Dig

Last edited by digger95; 10-28-2007 at 01:50 PM.
 
Old 10-28-2007, 01:45 PM   #12
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Rep: Reputation: Disabled
Quote:
Originally Posted by titopoquito View Post
IMHO it won't do any harm to use the huge kernel at least to get your system working with the new kernel. You can do a custom compile later without any problem. This way Twister512 can first forget about an initrd.
My understanding of his situation is that he does have a working system, he just doesn't have a (new) working kernel. So why install the huge kernel just to replace it with the generic kernel? Making an initrd is straight-forward and quick and well document.

Brian
 
Old 10-28-2007, 02:21 PM   #13
titopoquito
Senior Member
 
Registered: Jul 2004
Location: Ruhr Area, Germany
Distribution: Slackware64 14.0
Posts: 1,517

Rep: Reputation: 90
You are right. And all roads lead to Rome, sooner or later
 
Old 10-28-2007, 02:59 PM   #14
digger95
Member
 
Registered: Oct 2007
Location: Indiana, PA
Distribution: Slackware 14
Posts: 330

Rep: Reputation: 45
Personally I'm still too scared to approach slackware -current yet. LoL. I simply used the default generic kernels already installed in /boot, created initrd's for them both, and then added them to LiLo. Worked like a charm and got me a more streamlined system I could really play around with. I find 2.6.21.5 to be a nice stable kernel. Is there really any reason to upgrade? Just asking, not commenting.
 
Old 10-28-2007, 08:44 PM   #15
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Rep: Reputation: Disabled
Quote:
Originally Posted by digger95 View Post
Is there really any reason to upgrade? Just asking, not commenting.
That is the right question to ask, although there are many answers, depending on you, your computer, and how you use your computer. I have a server running 2.6.17 and Slack 11. It is stable, fast and I see no urgent reason to upgrade it. On the other hand, I have a laptop that is running 12.0 and my own custom 2.6.22 kernel, which I intend to upgrade to 2.6.23 soon. I like to keep that system on the kernel version used in -current, and will to upgrade to -current at some point.

For the OP, who expressed interest in learning, I would recommend that he build his own kernel, because it is a good learning experience.

My own two cents.

Brian
 
  


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
slackpkg bookie Linux - Newbie 22 05-31-2007 09:49 AM
slackpkg doesn't works (problems with awk) sparc86 Slackware 8 04-11-2007 11:08 AM
Slackpkg: missing something in /usr/libexec/slackpkg/functions.d/dialog-functions.sh michelino Slackware 4 03-20-2007 12:22 PM
Slackpkg? vharishankar Slackware 13 08-04-2006 09:10 PM
slackpkg problems dive Slackware 3 11-16-2005 04:08 PM


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