LinuxQuestions.org
Visit Jeremy's Blog.
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 01-10-2013, 06:43 PM   #1
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,125

Rep: Reputation: 46
/boot: how do I change the current kernel?


Slackware 14.0

Hi:
I once changed the smp kernel running in my system by another one in /boot. What I did was to relink /boot/System.map, /boot/vmlinuz and /boot/config. But I don't remember if I did something else. Would that alone be OK.
 
Old 01-10-2013, 06:50 PM   #2
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 755

Rep: Reputation: 226Reputation: 226Reputation: 226
You need to rerun lilo so that it reads a new sector list to load the new kernel.

Have you considered adding both kernels into lilo.conf so you can just select the one you want at boot time?
 
1 members found this post helpful.
Old 01-10-2013, 06:50 PM   #3
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,563
Blog Entries: 2

Rep: Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035
You also have to run lilo to make it aware of the changes.
 
Old 01-10-2013, 07:10 PM   #4
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,125

Original Poster
Rep: Reputation: 46
ok. An according to CHANGES_AND_HINTS.txt I should make an initrd? I mean, if I use a generic kernel? That thing of the two kernels I like it. I'll do it. Another question.
Code:
                Advanced Linux Sound Architecture - Driver
                ==========================================
                            Installation guide





Quick install
=============

1) You must have full configured source for the Linux kernel which you
   want to use for the ALSA drivers. Note that ALSA drivers are part
   of the kernel, so there is necessary to resolve all symbol dependencies
   between the used kernel and ALSA driver code. Partly installed kernels
   (for example from distributor makers) can be unuseable for this action.
What is the meaning of "full configured source for the Linux kernel"?

Last edited by stf92; 01-10-2013 at 07:17 PM.
 
Old 01-10-2013, 07:21 PM   #5
TommyC7
Member
 
Registered: Mar 2012
Distribution: Slackware, CentOS, OpenBSD, FreeBSD
Posts: 436

Rep: Reputation: Disabled
If you use a generic kernel, yes. The generic kernel doesn't have the filesystems (ext4, ext3, btrfs, etc.) that you (might) use built-in.
 
1 members found this post helpful.
Old 01-10-2013, 07:49 PM   #6
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,125

Original Poster
Rep: Reputation: 46
Well then, lilo says the ram disk will be loaded above 16M, OK. But what is this token 'large-memory' that can be put in /etc/lilo.conf. I am having trouble booting with a live Linux CD, which is unobjectionable. May it be related to 'large-memory'?
 
Old 01-10-2013, 08:50 PM   #7
TommyC7
Member
 
Registered: Mar 2012
Distribution: Slackware, CentOS, OpenBSD, FreeBSD
Posts: 436

Rep: Reputation: Disabled
I think your /etc/lilo.conf is still using the huge kernel. You can append "large-memory" to /etc/lilo.conf if you want, but I would just recommend using the smaller, generic kernel in your /etc/lilo.conf instead (and then running lilo).
 
Old 01-10-2013, 09:04 PM   #8
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,125

Original Poster
Rep: Reputation: 46
Oh no. I have just replaced the huge by the generic, precisely. It's in /etc/lilo.conf_example where I saw 'large-memory' used. Would this command (large_memory) be obsolete?
 
Old 01-11-2013, 01:27 AM   #9
wigry
Member
 
Registered: Jul 2004
Distribution: slackware
Posts: 218

Rep: Reputation: 52
I haven't used it in my lilo confs. Anyway you can always man lilo to see the meanings of config options.
 
Old 01-11-2013, 01:32 AM   #10
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,125

Original Poster
Rep: Reputation: 46
Of course I've done that. That's why I ask. But if your machine is a modern one, as mine is too, I wound bother to further inquire. Thanks.
 
Old 01-11-2013, 05:05 AM   #11
wigry
Member
 
Registered: Jul 2004
Distribution: slackware
Posts: 218

Rep: Reputation: 52
After reading this link: http://manpages.ubuntu.com/manpages/...lo.conf.5.html it appears that actually large-memory option specifies that your system is new enough to be able to handle the initrd location beyond 15Mb limit. Without it, the Initrd will be put within the first 15Mb. As I haven't had any problems with loading initrd from the first 15Mb never ever then I haven't investigated about the large-memory option. It is just one of many lilo's capabilities and there might be some special cases where it would be necessary. But usually you can live without it.
 
Old 01-11-2013, 05:14 AM   #12
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 755

Rep: Reputation: 226Reputation: 226Reputation: 226
Loading the initrd after that point is required on some distros that try to do everything in it and bloat it out to the point where it's almost a distro in of itself.

Have not had such a problem with Slackware, though maybe if you forced every module to be in it you might see that problem rear its head.
 
Old 01-11-2013, 05:39 AM   #13
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,563
Blog Entries: 2

Rep: Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035Reputation: 4035
The 15MB limit was a problem back in the days of 486 CPUs, if I remember correctly, on modern machines that specific option isn't even available in the BIOS settings. Nonetheless, I only had this message when I misconfigured mkinitrd and it bloated the initrd and when I attempted to run Slackware entirely from the initrd. Usually the initrd shouldn't be that large that you get this message.
What was your command to create the initrd?
 
Old 01-11-2013, 06:32 AM   #14
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,125

Original Poster
Rep: Reputation: 46
I must tell you I didn't got any message from lilo about the memory limit. I only read /etc/lilo.conf_example and saw that command (large_memory). I suspected it to be obsolete (not deprecated but of little use, I you explained). The command I issued was
Code:
mkinitrd -c -k 3.2.29 -m ext2
where 3.2.29 is my kernel version and ext2 the fs I use in the hard.
 
  


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] Can't boot into -current partition after slackpkg upgrade-all, after kernel upgraded gabytf Slackware 7 08-12-2012 10:42 AM
how to make boot able image from the current kernel elili Linux - Kernel 0 02-16-2011 11:35 AM
[SOLVED] custom kernel not boot after current lastest update zhoun Slackware 13 03-06-2010 09:33 PM
canīt boot updated kernel slackware current jcamez Slackware 19 01-10-2010 08:20 AM
Current Huge Kernel Will Not Boot With cx23885 Module Woodsman Slackware 7 05-29-2009 10:46 AM


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