LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
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 06-15-2011, 11:29 PM   #1
Knightron
Senior Member
 
Registered: Jan 2011
Location: Australia
Distribution: openSUSE
Posts: 1,465
Blog Entries: 6

Rep: Reputation: 200Reputation: 200Reputation: 200
Question How to switch to the generic kernel


Quote:
Originally Posted by piratesmack View Post
One thing I always do is switch to the vmlinuz-generic(-smp) kernel in /etc/lilo.conf and build an initrd (see /boot/README.initrd for details).

The "huge" kernel used by default is only meant for installing and not recommended for everyday use. It has a lot of drivers you don't need built-in and uses more RAM than the "generic" kernels.
Hi guys, still trying to find my feet and get to know Slackware. In one of my previous threads, 'things to do after installing' i was told the above message. When i installed, it used the huge kernel, but i'm unsure if that was the one that got installed. when i start slackware up, above the login screen it say, “wecome to Linux 2.6.37.6-smp (tty1)” I was wondering how to swich to the generic smp kernel, do I just change the vmlinuz to the desired, in lilo?
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 06-15-2011, 11:42 PM   #2
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,639

Rep: Reputation: Disabled
You have two choices, you could either change lilo.conf to specifically point to the generic kernel, or you change the /boot/vmlinuz symlink to point to the generic kernel instead of the huge kernel. You will need to create an initrd and re-run lilo. If you are hesitant, you can create a new stanza in lilo.conf pointing to the generic kernel and keep the entry for the huge kernel.

If this sounds like gobbldy-gook repost and I or someone else can be more detailed as to how to do these things.

Brian
 
Old 06-15-2011, 11:53 PM   #3
D1ver
Member
 
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 598
Blog Entries: 3

Rep: Reputation: 194Reputation: 194
Have a read through the lower half of '/boot/README.initrd'. There is an example command that will generate the initrd and it has an example of how to add it to your lilo.conf. It's a pretty simple process, you execute the one shell command to generate the initrd, add an entry to the bottom of your '/etc/lilo.conf' file and rerun lilo. It's a little intimidating first try though.


I'm sorry I can't give exact syntax as I'm at work on my Windows computer
 
Old 06-15-2011, 11:54 PM   #4
Knightron
Senior Member
 
Registered: Jan 2011
Location: Australia
Distribution: openSUSE
Posts: 1,465

Original Poster
Blog Entries: 6

Rep: Reputation: 200Reputation: 200Reputation: 200
Thanks Brian, i think i might go for the lilo.conf way unless their's an advantage to the other? will i need to create an intrid if i do it this way? I don't know how to make an intrid. I was just skimming through the document on the slack dvd and the file about the intrid sounded daunting.
 
Old 06-16-2011, 12:53 AM   #5
jamesf
Member
 
Registered: Dec 2004
Location: USA
Distribution: Slackware 12, Slackware64 14.2
Posts: 236
Blog Entries: 1

Rep: Reputation: 57
You'll always need an initrd for a generic Slackware kernel. If you want to build one and add the option to use it to lilo then follow these directions. Copy the text from the Code: sections and paste it into the terminal you get in step 1.

1) Get to a command line, like XFCE Terminal or Konsole, and "su -" to root unless you run X as root.
2) Execute this command to add the lilo stanza:
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh --lilo /boot/vmlinuz-generic-smp-2.6.37.6-smp >>/etc/lilo.conf
3) Execute this command to create an initrd:
Code:
$( /usr/share/mkinitrd/mkinitrd_command_generator.sh --run /boot/vmlinuz-generic-smp-2.6.37.6-smp )
4) Run lilo
Code:
lilo
5) Reboot.

You'll see a new option named 2.6.37.6(maybe something more). Arrow down to pick that option and hit enter. Your old kernel (huge) is the first option, and the default one when the time runs out and it boots automatically.

If you don't need to add any special modules for your hardware to the initrd and you don't need any special lilo options then you'll boot into a generic SMP kernel. If the boot fails just Ctrl-Alt-Del to reboot, or hold down Alt and the SysReq key and hit (while holding down Alt and SysReq the whole time) R E I S U B The mnemonic for that reboot is Raising Elephants Is So Utterly Boring.

If you've had to reboot because the generic SMP kernel failed then remember that the huge kernel is the first choice on the lilo screen.

Most don't need any special options or modules, so you'll probably work first time.

Good luck!

Last edited by jamesf; 06-16-2011 at 12:54 AM.
 
2 members found this post helpful.
Old 06-16-2011, 01:12 AM   #6
piratesmack
Member
 
Registered: Feb 2009
Distribution: Slackware, Arch
Posts: 519

Rep: Reputation: 142Reputation: 142
Alien Bob made a script that can help you

Run this and it will give you a command to create an initrd for your system:
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh
If using Slackware (32-Bit), this command will give you a menu entry for /etc/lilo.conf:
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh -l /boot/vmlinuz-generic-smp-$(uname -r)
If using Slackware64, this command will give you a menu entry (Note: You might need to use this one on Slackware 32-Bit if your computer can't use the SMP kernel for some reason):
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh -l /boot/vmlinuz-generic-$(uname -r)
edit: jamesf was faster
 
1 members found this post helpful.
Old 06-16-2011, 02:21 AM   #7
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,298
Blog Entries: 61

Rep: Reputation: Disabled
Knightron
If you had scrolled down in that thread you got piratesmack's quote from, you might have noticed this:
http://www.linuxquestions.org/questi...0/#post4366389
 
Old 06-16-2011, 03:27 AM   #8
Knightron
Senior Member
 
Registered: Jan 2011
Location: Australia
Distribution: openSUSE
Posts: 1,465

Original Poster
Blog Entries: 6

Rep: Reputation: 200Reputation: 200Reputation: 200
Smile

Quote:
Originally Posted by brianL View Post
Knightron
If you had scrolled down in that thread you got piratesmack's quote from, you might have noticed this:
http://www.linuxquestions.org/questi...0/#post4366389

lol now i feel a little silly. Anyways guys, thankyou all, even you D1ver, i felt kinda bad before when i post a direct thanks to Brian and then by the time i'd published it, you'd also post, and it looked like i didn't care what you'd said.
I've successfully done it, i followed piratesmack's guide and have made a few personal edits so it's the default. Thanks heaps
 
Old 06-16-2011, 03:36 AM   #9
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,298
Blog Entries: 61

Rep: Reputation: Disabled
Quote:
Originally Posted by Knightron View Post
lol now i feel a little silly.
Don't worry about it. I've done a few (thousand...million?) silly things in my time.
 
1 members found this post helpful.
Old 06-16-2011, 05:52 AM   #10
D1ver
Member
 
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 598
Blog Entries: 3

Rep: Reputation: 194Reputation: 194
Quote:
Originally Posted by Knightron View Post
lol now i feel a little silly. Anyways guys, thankyou all, even you D1ver, i felt kinda bad before when i post a direct thanks to Brian and then by the time i'd published it, you'd also post, and it looked like i didn't care what you'd said.
I've successfully done it, i followed piratesmack's guide and have made a few personal edits so it's the default. Thanks heaps
All good mate Glad to see you got it working.
 
1 members found this post helpful.
  


Reply



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] setting up initrd / generic kernel in Grub2...can't load generic Ubunoob001 Slackware 12 03-20-2015 07:32 AM
[SOLVED] switch Huge SMP to Generic czezz Slackware 16 07-07-2011 09:07 AM
how to switch from hugesmp.s to generic.s after intallation markluocanada Slackware 47 06-16-2008 07:41 AM
slack 12, switch to generic kernel from huge kernel, using grub? jaguarrh Slackware 8 09-19-2007 06:29 AM
Switch from huge-smp-2.6.21.5 to generic-2.6.21.5 tronayne Slackware 1 07-30-2007 08:34 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:45 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
Open Source Consulting | Domain Registration