LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 11-17-2012, 08:58 AM   #1
michijo
Member
 
Registered: Apr 2011
Posts: 162

Rep: Reputation: 0
3.2.29 kernel and Lilo


Slackware 14 uses 3.2.29 kernel. in my boot directory after upgrading are vmlinuz-generic-smp-3.2.29-smp and vmlinuz-huge-smp-3.2.29-smp, etc. Is there a difference in these, and which should lilo point to?
 
Old 11-17-2012, 10:32 AM   #2
NorthBridge
LQ Newbie
 
Registered: Oct 2012
Location: Somewhere after <?php
Distribution: Slackware-current
Posts: 15

Rep: Reputation: 1
See the "switch to a generic kernel" part on this page, it explains them very well.

In short, you want a generic kernel running the system after you're done with the installation, since it runs a little bit faster and loads fewer things.
 
Old 11-17-2012, 06:32 PM   #3
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by NorthBridge View Post
See the "switch to a generic kernel" part on this page, it explains them very well.

In short, you want a generic kernel running the system after you're done with the installation, since it runs a little bit faster and loads fewer things.
Ah, somehow I messed up. I think I did it right, but there is a kernel panic and now I cant boot. I am using an Ubuntu livedisk to access my slackware data, so I was able to edit the lilo.conf. But now I cant set it to the MBR due to the inability to run the command "lilo -v" from inside the livedisk.

Any way to manually move the new lilo conf to MBR? For now I cant bootmy computer either way.
 
Old 11-17-2012, 06:58 PM   #4
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
Ive been using these directions that I found on a different threadZ

Code:
~#mkdir /slacktemp                   #temporary mount point
~#mount /dev/your_device /slacktemp  #the device you installed to
~#chroot /slacktemp                  #change to yours
~#cd /slacktemp/etc                  #change to directory with lilo.conf 
~#vi lilo.conf                       #edit lilo.conf, if need be
~#lilo -v -t -b /dev/your_device     #sda, hda this will only test 
~#lilo -v -b /dev/your_device        #this will write to your boot device
So far I was able to mount my slackware inside an Ubuntu liveCD that I happened to have around. Then I was able to chroot it. Finally I am able to run lilo! Very tricky! But there is an error:

"Fatal: Default image doesn't exist."

Not sure what that means. It says it added

Code:
Boot image: /boot/vmlinuz-generic-3.2.29
Added 3.2.29
then it errors.

Last edited by michijo; 11-17-2012 at 07:00 PM.
 
Old 11-17-2012, 07:42 PM   #5
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
You need to create an initrd.gz for the generic kernel to work
Add an entry to similar to this
Code:
image = /boot/vmlinuz
  root = /dev/sda?
  label = Linux
  read-only
reboot, use this entry to boot slackware. Then run this
Code:
sh /usr/share/mkinitrd/mkinitrd_command_generator.sh
to find out what is needed to run mkinitrd. After creating an initrd.gz. Edit you generic entry to look like this
Code:
image = /boot/vmlinuz-generic-3.2.29
  initrd = /boot/initrd.gz
  root = /dev/sda?
  label = slack
  read-only
rerun lilo then the generic kernel should work. Vmlinuz is linked to the huge kernel

Last edited by colorpurple21859; 11-17-2012 at 07:48 PM.
 
Old 11-17-2012, 07:44 PM   #6
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
why cant I use /dev/root anymore? It returns

Code:
Fatal: Illegal 'root=' specification: /dev/root
This always worked before. I am going to use it anyway and see if it works.
 
Old 11-17-2012, 07:51 PM   #7
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by colorpurple21859 View Post
You need to create an initrd.gz for the generic kernel to work
Add an entry to similar to this
Code:
image = /boot/vmlinuz
  root = /dev/sda?
  label = Linux
  read-only
reboot, use this entry to boot slackware. Then run this
Code:
sh /usr/share/mkinitrd/mkinitrd_command_generator.sh
to find out what is needed to run mkinitrd. After creating an initrd.gz. Edit you generic entry to look like this
Code:
image = /boot/vmlinuz-generic-3.2.29
  initrd = /boot/initrd.gz
  root = /dev/sda?
  label = slack
  read-only
rerun lilo then the generic kernel should work. Vmlinuz is linked to the huge kernel
I did that before actually. I ran that command and used the output. Well, trying your smp edition.
 
Old 11-17-2012, 07:53 PM   #8
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
use it if it works
 
Old 11-17-2012, 07:54 PM   #9
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by colorpurple21859 View Post
use it if it works
I didnt include this originally:

initrd = /boot/initrd.gz

I think that is what was missing! The output from lilo is different now. Thanks!
 
Old 11-17-2012, 08:06 PM   #10
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
I
Quote:
didnt include this originally:

initrd = /boot/initrd.gz
Yeah that was the problem, glad you got it working,
 
Old 11-17-2012, 08:29 PM   #11
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by colorpurple21859 View Post
I Yeah that was the problem, glad you got it working,
It doesnt kernel panic now, but I still cant boot that generic kernel. It gives an error related to not being able to find "mnt" or to mount /dev/sda2 as root, even though that is root. It also said could not find "init". That is from what I remember. I installed a non-generic kernel in order to get around using that suck livedisk. Though I restarted so many times with that livedisk I became proficient at mounting and chrooting folders and filesystems as root. Good experience, but I would rather just avoid such troubles. Never realized what chroot was for.
 
Old 11-17-2012, 09:02 PM   #12
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
at the lilo prompt hit tab select the entry for the generic kernel type root=/dev/sda2 then boot if it works then add the line
Code:
append =  "root=/dev/sda2"
to the generic entry
 
Old 11-18-2012, 09:23 AM   #13
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by colorpurple21859 View Post
at the lilo prompt hit tab select the entry for the generic kernel type root=/dev/sda2 then boot if it works then add the line
Code:
append =  "root=/dev/sda2"
to the generic entry
Nope, the error is the same:
Code:
mounting /dev/sda2 on /mnt failed: no such device

No /sbin/init found on rootdev (or not mounted)

Trouble ahead

Cant access TTY
 
Old 11-18-2012, 12:48 PM   #14
michijo
Member
 
Registered: Apr 2011
Posts: 162

Original Poster
Rep: Reputation: 0
I am sure it is /dev/sda2, because the command

# df -h

produces sda2 in the '/' root.
 
Old 11-18-2012, 01:16 PM   #15
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
Are you able to boot slackware with the huge kernel?
 
  


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
[SOLVED] lilo says my 2.6 kernel image is to large&new problem kernel will not boot smeezekitty Linux - Newbie 3 10-13-2009 08:41 PM
Kernel Header files needed for lilo (config.h no longer in kernel!) gvp87 Linux - Software 1 04-29-2008 02:32 PM
Upgraded kernel, lilo.conf, didn't run /sbin/lilo dtashima Linux - Newbie 4 10-18-2004 11:21 AM
No new kernel-option in LILO after editing lilo.conf corwax Debian 3 08-26-2003 08:55 PM
new kernel causes lilo crash; /sbin/lilo = Warning: device 0x0305 exceeds 1024 cylind dandysf Linux - Software 0 08-26-2003 04:50 PM


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