LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (http://www.linuxquestions.org/questions/linux-software-2/)
-   -   Kernel Install Odd Error (http://www.linuxquestions.org/questions/linux-software-2/kernel-install-odd-error-374457/)

inescapeableus 10-18-2005 07:01 PM

Kernel Install Odd Error
 
Hello again, I am writing you all from my Windows box so you know this is not a good sign. Anyway I have just install Suse Linux, OpenSuse 10.0 to be exact and I am having a rather frustrating time with the kernel installation progress. I have kernel experience as I have been compling my own on various systems for a year now yet it seems to be with Suse I am having the worst time with. Now because Suse is using an initialram disk I need to have a initrd image file in order for me to boot. I have used this method in Fedora quite often. What happens is, after many times searching with google and LinuxQuestions I enter the following command.

mkinitrd -k vmlinuz-2.6.13.4 -i initrd-2.6.13.4

and this makes the initrd file in the present working directory. I then issue the command to send the file to boot everything goes well. Now I adjust my grub menu accordingly and upon boot up I get this error

error 15: file not found

I have gone over grub for typos etc. and have found none. Is there another means I should make my initrd image? Thanks again I would really love to get on my Linux machine again.

anomie 10-18-2005 10:03 PM

Have a look at grub's documentation: http://www.gnu.org/software/grub/man...e2-errors.html

Quote:

15 : File not found
This error is returned if the specified file name cannot be found, but everything else (like the disk/partition info) is OK.
Probably you are referring to either your kernel name or your initrd name incorrectly in the grub entry. If you can't figure it out, post your /boot/grub/menu.lst file contents here.

inescapeableus 10-19-2005 12:00 AM

I will do that promptly in the morning I have to head out for a nine hour drive to install some servers to I will post when I get a chance. Thanks for the reply

inescapeableus 10-20-2005 08:06 PM

all the info is correct any other ideas?

anomie 10-20-2005 10:00 PM

Could you post the results of
Code:

ls -l /boot
and
Code:

cat /boot/grub/menu.lst

inescapeableus 10-21-2005 08:32 PM

ok this is my boot menu list:

linux:/home/mike # ls -l /boot
total 11807
drwxr-xr-x 3 root root 616 2005-10-18 16:49 .
drwxr-xr-x 24 root root 560 2005-10-21 11:13 ..
-rw------- 1 root root 512 2005-10-16 14:50 backup_mbr
lrwxrwxrwx 1 root root 1 2005-10-16 14:44 boot -> .
-rw-r--r-- 1 root root 55580 2005-09-13 10:00 config-2.6.13-15-default
drwxr-xr-x 2 root root 512 2005-10-18 16:50 grub
lrwxrwxrwx 1 root root 24 2005-10-16 14:50 initrd -> initrd-2.6.13-15-def ault
-rw-r--r-- 1 root root 2497233 2005-10-16 14:50 initrd-2.6.13-15-default
-rw-r--r-- 1 root root 2492313 2005-10-18 16:50 initrd-2.6.13.4
-rw-r--r-- 1 root root 128000 2005-10-16 14:50 message
-rw-r--r-- 1 root root 70888 2005-09-13 10:02 symvers-2.6.13-15-x86_64-defau lt.gz
lrwxrwxrwx 1 root root 25 2005-10-18 16:49 System.map -> /boot/System.map -2.6.13.4
-rw-r--r-- 1 root root 899321 2005-09-13 09:48 System.map-2.6.13-15-default
-rw-r--r-- 1 root root 875648 2005-10-18 16:16 System.map-2.6.13.4
-rw-r--r-- 1 root root 1886359 2005-09-13 10:00 vmlinux-2.6.13-15-default.gz
lrwxrwxrwx 1 root root 25 2005-10-16 14:47 vmlinuz -> vmlinuz-2.6.13-15-d efault
-rw-r--r-- 1 root root 1606360 2005-09-13 09:48 vmlinuz-2.6.13-15-default
-rw-r--r-- 1 root root 1542156 2005-10-18 16:15 vmlinuz-2.6.13.4

and this is the other:

linux:/home/mike # cat /boot/grub/menu.lst
# Modified by YaST2. Last modification on Sun Oct 16 21:50:33 UTC 2005

color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,2)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 10.0
root (hd0,2)
kernel /boot/vmlinuz root=/dev/hda3 vga=0x314 selinux=0 resume=/dev/hda4 splash=silent showopts
initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: SUSE LINUX 10.0 (/dev/hda2)###
title SUSE LINUX 10.0 (/dev/hda2)
kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 vga=0x314 selinux=0 resume=/dev/hda4 splash=silent showopts
initrd (hd0,1)/boot/initrd

## Custom Kernel Entry
title Custom (/dev/hda2)
kernel (hd0,1)/boot/vmlinuz-2.6.13.4 root=/dev/hda2 vga=0x314 selinux=0 resume=/dev/hda4 splash=silent showopts
initrd (hd0,1)/boot/initrd-2.6.13.4

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows XP Professional
chainloader (hd0,0)+1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 10.0
root (hd0,2)
kernel /boot/vmlinuz root=/dev/hda3 vga=normal showopts ide=nodma apm=off acpi=off noresume selinux=0 edd=off 3
initrd /boot/initrd

anomie 10-21-2005 09:31 PM

Help me understand something here. You have a number of different SuSE entries. How many entirely different SuSE installations do you have? Two?

In one case you are starting from first drive, second partition and going to the path /boot/file_here. In another case you are starting from first drive, third partition and going to the path /boot/file_here.

This will not work if you have only one SuSE installation.

inescapeableus 10-21-2005 09:41 PM

For some reason or another SuSe added entries to the Menu list. It has 3 entries and one failsafe mode. That is correct. The entry that is going to the 3 partition is for safe mode. Any idea on what I to do from here?

anomie 10-21-2005 09:42 PM

Can you post the results of
Code:

fdisk -l
You will need to run that command as root.

anomie 10-21-2005 09:53 PM

Quote:

That is correct.
P.S. That is not correct. Your / filesystem does not live on two different partitions if you only have one SuSE installation.

inescapeableus 10-22-2005 02:22 AM

I changed the:

title Custom (/dev/hda2)
kernel (hd0,1)/boot/vmlinuz-2.6.13.4 root=/dev/hda2 vga=0x314 selinux=0 resume=/dev/hda4 splash=silent showopts
initrd (hd0,1)/boot/initrd-2.6.13.4

to the harddrive root of hda3 without any luck

anomie 10-22-2005 09:26 AM

This
Code:

kernel (hd0,1)
and the initrd entry needs to change.

0,1 = first physical drive, second partition.

Like I said, posting the output of
Code:

fdisk -l
would make this puzzle a lot simpler.

inescapeableus 10-22-2005 04:54 PM

Alright thanks, here is the feedback:

Disk /dev/hda: 60.0 GB, 60011642880 bytes
255 heads, 63 sectors/track, 7296 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 2578 20707753+ 7 HPFS/NTFS
/dev/hda2 2579 4014 11534670 83 Linux
/dev/hda3 4015 7148 25173855 83 Linux
/dev/hda4 7149 7279 1052257+ 82 Linux swap / Solaris
linux:/home/mike #

inescapeableus 10-22-2005 06:11 PM

Alright I just figured her out, this is my first time seriously sitting down with Suse so there are a few things that I have to watch out for, I went through the YAST configure utility where I send the options to my kernel and my initial RAM image. From there I had to tweak a few things manual to direct it to where my root partition was, which I had forgot to add previous thus making my kernel not boot. Thanks for all your help i appreciate it.


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