[SOLVED] How to user vmlinuz-generic instead of vmlinuz-huge-smp?

cola · 09-15-2009, 01:33 PM

How to use vmlinuz-generic instead of vmlinuz-huge-smp?

Code:

user1@darkstar:/boot$ ls -l
total 19572
lrwxrwxrwx  1 root root      37 2009-09-15 17:57 README.initrd -> /usr/doc/mkinitrd-1.3.2/README.initrd
lrwxrwxrwx  1 root root      32 2009-09-15 17:56 System.map -> System.map-huge-smp-2.6.27.7-smp
-rw-r--r--  1 root root  927553 2008-11-20 20:01 System.map-generic-2.6.27.7
-rw-r--r--  1 root root  965704 2008-11-20 19:20 System.map-generic-smp-2.6.27.7-smp
-rw-r--r--  1 root root 1393024 2008-11-20 20:20 System.map-huge-2.6.27.7
-rw-r--r--  1 root root 1432921 2008-11-20 19:33 System.map-huge-smp-2.6.27.7-smp
-rw-r--r--  1 root root     512 2009-09-14 05:21 boot.0300
-rw-r--r--  1 root root     209 2009-09-14 05:21 boot_message.txt
lrwxrwxrwx  1 root root      28 2009-09-15 17:56 config -> config-huge-smp-2.6.27.7-smp
-rw-r--r--  1 root root   89202 2008-11-20 20:01 config-generic-2.6.27.7
-rw-r--r--  1 root root   89505 2008-11-20 19:20 config-generic-smp-2.6.27.7-smp
-rw-r--r--  1 root root   89081 2008-11-20 20:20 config-huge-2.6.27.7
-rw-r--r--  1 root root   89384 2008-11-20 19:33 config-huge-smp-2.6.27.7-smp
-rw-r--r--  1 root root    5040 2008-11-29 09:43 diag1.img
drwxr-xr-x 10 root root    4096 2009-09-15 18:04 initrd-tree/
-rw-r--r--  1 root root  910052 2009-09-15 18:04 initrd.gz
-rw-------  1 root root   80896 2009-09-14 05:21 map
-rw-r--r--  1 root root   15754 2008-02-21 15:08 slack.bmp
lrwxrwxrwx  1 root root      29 2009-09-15 17:56 vmlinuz -> vmlinuz-huge-smp-2.6.27.7-smp
-rw-r--r--  1 root root 2220880 2008-11-20 20:01 vmlinuz-generic-2.6.27.7
-rw-r--r--  1 root root 2347888 2008-11-20 19:20 vmlinuz-generic-smp-2.6.27.7-smp
-rw-r--r--  1 root root 4540208 2008-11-20 20:20 vmlinuz-huge-2.6.27.7
-rw-r--r--  1 root root 4727664 2008-11-20 19:33 vmlinuz-huge-smp-2.6.27.7-smp

menu.lst: (it doesn't work)

Code:

title           Slackware 12-generic, kernel 2.6.27.7
root            (hd0,4)
kernel          /boot/vmlinuz-generic-smp-2.6.27.7-smp root=/dev/hda5
initrd          /boot/initrd.gz
quiet

mobinskariya · 09-15-2009, 01:35 PM

thats it..you are right

cola · 09-15-2009, 01:39 PM

Quote:

Originally Posted by mobinskariya

thats it..you are right

Sorry,it's not working.

Code:

title           Slackware 12-generic, kernel 2.6.27.7
root            (hd0,4)
kernel          /boot/vmlinuz-generic-smp-2.6.27.7-smp root=/dev/hda5
initrd          /boot/initrd.gz
quiet

This works only:

Code:

title           Slackware 12-generic, kernel 2.6.27.7
root            (hd0,4)
kernel          /boot/vmlinuz root=/dev/hda5
quiet

mobinskariya · 09-15-2009, 01:42 PM

what is your error when using the first entry??

samac · 09-15-2009, 01:47 PM

Did you read the file on the cd README.initrd?

samac

cola · 09-15-2009, 02:10 PM

Quote:

Originally Posted by samac

Did you read the file on the cd README.initrd?

samac

I read this:

Code:

Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
Sun Oct 26 00:38:49 CDT 2008

This document describes how to create and install an initrd, which may be 
required to use the 2.6 kernel.  Also see "man mkinitrd".

1.  What is an initrd?
2.  Why to I need an initrd?
3.  How do I build the initrd?
4.  Now that I've built an initrd, how do I use it?


1.  What is an initrd?

Initrd stands for "initial ramdisk".  An initial ramdisk is a very small 
Linux filesystem that is loaded into RAM and mounted as the kernel boots, 
and before the main root filesystem is mounted.

2.  Why do I need an initrd?

The usual reason to use an initrd is because you need to load kernel 
modules before mounting the root partition.  Usually these modules are 
required to support the filesystem used by the root partition (ext3, 
reiserfs, xfs), or perhaps the controller that the hard drive is attached 
to (SCSI, RAID, etc).  Essentially, there are so many different options 
available in modern Linux kernels that it isn't practical to try to ship 
many different kernels to try to cover everyone's needs.  It's a lot more 
flexible to ship a generic kernel and a set of kernel modules for it.

3.  How do I build the initrd?

The easiest way to make the initrd is to use the mkinitrd script included 
in Slackware's mkinitrd package.  We'll walk through the process of 
upgrading to the generic 2.6.27.4-smp Linux kernel using the packages
found in Slackware's slackware/a/ directory.

First, make sure the kernel, kernel modules, and mkinitrd package are 
installed (the current version numbers might be a little different, so 
this is just an example):

  installpkg kernel-generic-2.6.27.4_smp-i686-1.tgz
  installpkg kernel-modules-2.6.27.4_smp-i686-1.tgz
  installpkg mkinitrd-1.3.2-i486-3.tgz

Change into the /boot directory:

  cd /boot

Now you'll want to run "mkinitrd".  I'm using reiserfs for my root
filesystem, and since it's an IDE system the reiserfs module will be
the only one I need to load:

  mkinitrd -c -k 2.6.27.4-smp -m reiserfs

This should do two things.  First, it will create a directory
/boot/initrd-tree containing the initrd's filesystem.  Then it will
create an initrd (/boot/initrd.gz) from this tree.  If you wanted to,
you could make some additional changes in /boot/initrd-tree/ and
then run mkinitrd again without options to rebuild the image.  That's
optional, though, and only advanced users will need to think about that.

Here's another example:  Build an initrd image using Linux 2.6.27.4-smp
kernel modules for a system with an ext3 root partition on /dev/hdb3.
Note that you need the mbcache, jbd, and ext3 modules to use ext3:

  mkinitrd -c -k 2.6.27.4-smp -m mbcache:jbd:ext3 -f ext3 -r /dev/hdb3


4.  Now that I've built an initrd, how do I use it?

Now that you've got an initrd (/boot/initrd.gz), you'll want to load
it along with the kernel at boot time.  If you use LILO for your boot
loader you'll need to edit /etc/lilo.conf and add a line to load the
initrd.  Here's an example section of lilo.conf showing how this is
done:

# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.27.4-smp
  initrd = /boot/initrd.gz
  root = /dev/hda6
  label = Lnx26274smp
  read-only
# Linux bootable partition config ends

The initrd is loaded by the "initrd = /boot/initrd.gz" line.
Just add the line right below the line for the kernel image you use.
Save the file, and then run LILO again ('lilo' at the command line).
You'll need to run lilo every time you edit lilo.conf or rebuild the
initrd.

Other bootloaders such as syslinux also support the use of an initrd.
See the documentation for those programs for details on using an
initrd with them.


---------

Have fun!

Here it's image = /boot/vmlinuz-generic-2.6.27.4-smp
But in /boot i get:

Code:

user1@darkstar:/boot$ ls -l
total 19572
lrwxrwxrwx  1 root root      37 2009-09-15 17:57 README.initrd -> /usr/doc/mkinitrd-1.3.2/README.initrd
lrwxrwxrwx  1 root root      32 2009-09-15 17:56 System.map -> System.map-huge-smp-2.6.27.7-smp
-rw-r--r--  1 root root  927553 2008-11-20 20:01 System.map-generic-2.6.27.7
-rw-r--r--  1 root root  965704 2008-11-20 19:20 System.map-generic-smp-2.6.27.7-smp
-rw-r--r--  1 root root 1393024 2008-11-20 20:20 System.map-huge-2.6.27.7
-rw-r--r--  1 root root 1432921 2008-11-20 19:33 System.map-huge-smp-2.6.27.7-smp
-rw-r--r--  1 root root     512 2009-09-14 05:21 boot.0300
-rw-r--r--  1 root root     209 2009-09-14 05:21 boot_message.txt
lrwxrwxrwx  1 root root      28 2009-09-15 17:56 config -> config-huge-smp-2.6.27.7-smp
-rw-r--r--  1 root root   89202 2008-11-20 20:01 config-generic-2.6.27.7
-rw-r--r--  1 root root   89505 2008-11-20 19:20 config-generic-smp-2.6.27.7-smp
-rw-r--r--  1 root root   89081 2008-11-20 20:20 config-huge-2.6.27.7
-rw-r--r--  1 root root   89384 2008-11-20 19:33 config-huge-smp-2.6.27.7-smp
-rw-r--r--  1 root root    5040 2008-11-29 09:43 diag1.img
drwxr-xr-x 10 root root    4096 2009-09-15 18:04 initrd-tree/
-rw-r--r--  1 root root  910052 2009-09-15 18:04 initrd.gz
-rw-------  1 root root   80896 2009-09-14 05:21 map
-rw-r--r--  1 root root   15754 2008-02-21 15:08 slack.bmp
lrwxrwxrwx  1 root root      29 2009-09-15 17:56 vmlinuz -> vmlinuz-huge-smp-2.6.27.7-smp
-rw-r--r--  1 root root 2220880 2008-11-20 20:01 vmlinuz-generic-2.6.27.7
-rw-r--r--  1 root root 2347888 2008-11-20 19:20 vmlinuz-generic-smp-2.6.27.7-smp
-rw-r--r--  1 root root 4540208 2008-11-20 20:20 vmlinuz-huge-2.6.27.7
-rw-r--r--  1 root root 4727664 2008-11-20 19:33 vmlinuz-huge-smp-2.6.27.7-smp

Code:

-rw-r--r--  1 root root 2220880 2008-11-20 20:01 vmlinuz-generic-2.6.27.7
-rw-r--r--  1 root root 2347888 2008-11-20 19:20 vmlinuz-generic-smp-2.6.27.7-smp

menu.lst:

Code:

itle           Slackware 12-generic, kernel 2.6.27.7
root            (hd0,4)
kernel          /boot/vmlinuz-generic-smp-2.6.27.7-smp root=/dev/hda5
initrd          /boot/initrd.gz
quiet

cola · 09-15-2009, 02:12 PM

Quote:

Originally Posted by samac

Did you read the file on the cd README.initrd?

samac

How can i check whether those are installed successfully or not?

Code:

  installpkg kernel-generic-2.6.27.4_smp-i686-1.tgz
  installpkg kernel-modules-2.6.27.4_smp-i686-1.tgz
  installpkg mkinitrd-1.3.2-i486-3.tgz

mobinskariya · 09-15-2009, 02:15 PM

if you chose full install then no need to install it again.it is there in your machine.

cola · 09-15-2009, 02:22 PM

Quote:

Originally Posted by mobinskariya

what is your error when using the first entry??

Code:

/bin/sh:can't access tty; job control off
sh$

mobinskariya · 09-15-2009, 02:26 PM

it can be due to initrd.img..i had the same problem but got it solved by buiding an initrd.img as follows..you better try it again as following

Code:

mkinitrd -c -k 2.6.27.7-smp -m ext3 -f ext3 -r /dev/sda5

cola · 09-15-2009, 02:40 PM

Quote:

Originally Posted by mobinskariya

it can be due to initrd.img..i had the same problem but got it solved by buiding an initrd.img as follows..you better try it again as following

Code:

mkinitrd -c -k 2.6.27.7-smp -m ext3 -f ext3 -r /dev/sda5

At first i ran this:

Code:

mkinitrd -c -k 2.6.27.4-smp -m reiserfs

This time i ran this:

Code:

mkinitrd -c -k 2.6.27.7-smp -m ext3 -f ext3 -r /dev/sda5

It works.
Thank you.

NB:Why /dev/sda5? It's /dev/hda5 for me(slackware 12.2).

mobinskariya · 09-15-2009, 02:43 PM

you have sata hard drive isnt it??any way congrats.

cola · 09-15-2009, 02:54 PM

Quote:

Originally Posted by mobinskariya

you have sata hard drive isnt it??any way congrats.

No, it's IDE.
From fdisk -l:

Code:

/dev/hda5            4590        5902    10546641   83  Linux