LinuxQuestions.org
Review your favorite Linux distribution.
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 07-14-2007, 07:22 PM   #1
somae
Member
 
Registered: Nov 2006
Posts: 56

Rep: Reputation: 15
going from "huge" to generic kernel - slack 12


We are using the 2.6.21.5 huge.smp kernel and I want to switch over to the generic.

According to the README file, I downloaded the 2.6.21.5-generic kernel to my /home directory and

Code:
 gzip -cd linux-2.6.21.5.tgz | tar xvf -
I then went into /usr/src/linux and

Code:
 make mrproper
Now the README says to go into /usr/src/linux and
Quote:
kernel source code: /usr/src/linux-2.6.N
build directory: /home/name/build/kernel

To configure and build the kernel use:
cd /usr/src/linux-2.6.N
make O=/home/name/build/kernel menuconfig
however, there is no /build/kernel directory in my /home directory.

Is the README file talking about installing the kernel source, which would create these directories?

Help appreciated.

Last edited by somae; 07-14-2007 at 07:49 PM.
 
Old 07-14-2007, 08:02 PM   #2
Berhanie
Senior Member
 
Registered: Dec 2003
Location: phnom penh
Distribution: Fedora
Posts: 1,625

Rep: Reputation: 165Reputation: 165
I think you're doing too much. Check your /boot. All the kernels should already be there. All you need to do is change a few symlinks in /boot, make an initrd as explained in the REAME.initrd there, and run lilo.
 
Old 07-15-2007, 04:31 AM   #3
somae
Member
 
Registered: Nov 2006
Posts: 56

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by Berhanie
I think you're doing too much. Check your /boot. All the kernels should already be there. All you need to do is change a few symlinks in /boot, make an initrd as explained in the REAME.initrd there, and run lilo.
I had thought to do that, but there is no system.map for the generic kernel. I thought maybe this was created by compiling.
 
Old 07-15-2007, 07:48 AM   #4
yakoub
Member
 
Registered: Oct 2006
Posts: 99

Rep: Reputation: 15
slackware/a

slackware/a has several kernel packages , check them out

what you are doing is not installing a generic kernel
but compiling your own custom kernel
there are documentation about installing the
generic kernel packages using mkinitrd tool
 
Old 07-15-2007, 09:48 AM   #5
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Hi,

Quote:
Excerpt /usr/src/linux-2.6.21.5/README;
INSTALLING the kernel:

- If you install the full sources, put the kernel tarball in a
directory where you have permissions (eg. your home directory) and
unpack it:
I usually do a '~#user mkdir /home/build' as a ~#/home/user. That way I can move to an from the build user space without problems. That way you will be able to compile the kernel independent of the root. Of course you would become root to to the install portion, 'make modules_install' or copy the 'bzImage' to the /boot. Or modify the '/etc/lilo.conf' and then write the 'lilo'.

Code:
~#gws@odin:~$ ls ../build   
hdb_backup/  slackware-current/
I sometimes create a build in my /home directory. This is just ease of use. But if I want someone else to have access then I create in the /home/build and provide permissions.

Quote:
Excerpt /usr/src/linux-2.6.21.5/README;

Do NOT use the /usr/src/linux area! This area has a (usually
incomplete) set of kernel headers that are used by the library header
files. They should match the library, and not get messed up by
whatever the kernel-du-jour happens to be.
This warning is sometimes ignored by users but should not present you with a problem if you use the build technique.

Quote:
Excerpt /usr/src/linux-2.6.21.5/README;

BUILD directory for the kernel:

When compiling the kernel all output files will per default be
stored together with the kernel source code.
Using the option "make O=output/dir" allow you to specify an alternate
place for the output files (including .config).
Example:
kernel source code: /usr/src/linux-2.6.N
build directory: /home/name/build/kernel

To configure and build the kernel use:
cd /usr/src/linux-2.6.N
make O=/home/name/build/kernel menuconfig
make O=/home/name/build/kernel
sudo make O=/home/name/build/kernel modules_install install

Please note: If the 'O=output/dir' option is used then it must be
used for all invocations of make.
This should be self defining but;

They are speaking of a build area that is independent of the 'usr/src/linux'. Most programmers use this technique so as not to mess with the original space or tree.

The build is independent of the '/usr/src/linux-2.6.N' directory.

Notice the 'sudo'! You could also do a 'su' if you haven't modified the '/etc/sudoers' file to include yourself. You will have to provide the root password.

Also remember the lib warning!

You can make your compile unique by editing the 'Makefile' by adding a unique label to the 'EXTRAVERSION ='
option before you compile.

edit: clarify a statement

Last edited by onebuck; 07-15-2007 at 07:59 PM.
 
Old 07-15-2007, 09:57 AM   #6
Berhanie
Senior Member
 
Registered: Dec 2003
Location: phnom penh
Distribution: Fedora
Posts: 1,625

Rep: Reputation: 165Reputation: 165
I did the full the install. System.map-generic-smp-2.6.21.5-smp is part of the kernel-generic-smp-2.6.21.5_smp-i686-2. If you don't have that package, find it in slackware/a/, and install it:
Code:
installpkg kernel-generic-smp-2.6.21.5_smp-i686-2.tgz

Last edited by Berhanie; 07-15-2007 at 10:15 AM.
 
Old 07-15-2007, 06:17 PM   #7
somae
Member
 
Registered: Nov 2006
Posts: 56

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by Berhanie
I did the full the install. System.map-generic-smp-2.6.21.5-smp is part of the kernel-generic-smp-2.6.21.5_smp-i686-2. If you don't have that package, find it in slackware/a/, and install it:
Code:
installpkg kernel-generic-smp-2.6.21.5_smp-i686-2.tgz
We do have the generic-smp system.map but it's for i686 which gives us problems. The non-smp generic is for i486 but there's no system.map
 
Old 07-15-2007, 06:41 PM   #8
somae
Member
 
Registered: Nov 2006
Posts: 56

Original Poster
Rep: Reputation: 15
I have to revise that. I tried using the generic-smp kernel again and now it functions. Maybe all the rearranging we did on the rc.* files made it so that now it functions. (We had rc.new files for the new kernel that I made functional.)

Thanks all.
 
  


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
Slack install question M$ISBS Slackware - Installation 2 12-04-2006 12:14 AM
Slack 10.2, 2.6.13 kernel, SMP question Twister512 Slackware 18 11-28-2005 10:22 PM
slack 10 kernel question salahuddin_66 Slackware 3 08-09-2004 12:04 AM
slack install question bandofmercy Slackware 1 03-24-2003 10:48 PM
Slack install question hanzerik Linux - Software 12 01-09-2002 03:15 PM

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

All times are GMT -5. The time now is 07:18 AM.

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