public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matthew R. Lee" <gentoo@matthewlee.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] grub boot problem
Date: Sat, 5 Jul 2008 20:13:20 -0400	[thread overview]
Message-ID: <200807052013.20461.gentoo@matthewlee.org> (raw)
In-Reply-To: <487007FE.8090805@genestate.com>

On Saturday 05 July 2008 19:47:10 Matt Harrison wrote:
> Matthew R. Lee wrote:
> > On Saturday 05 July 2008 19:15:05 Mick wrote:
> >> On Sunday 06 July 2008, Matthew R. Lee wrote:
> >>> I've just compiled a new kernel, but when I reboot grub will not load
> >>> the new kernel. I get error 15 (file not found). But the file is there.
> >>> Yes grub is install properly and yes the boot partition was mounted
> >>> when I copied the new kernel across and changed the grub.conf. What's
> >>> really confusing me is there's no syntax error in the grub.conf that I
> >>> can see, and the first kernel on the list boots fine.  Anyone got any
> >>> cluse as to why grub can't see the second kernel?
> >>>
> >>> [grub.conf]
> >>> default 0
> >>>
> >>> timeout 30
> >>>
> >>> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> >>>
> >>> title=Gentoo 2.6.22-r2
> >>>
> >>> root (hd0,0)
> >>> kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
> >>> video=vesafb:mtrr,ywrap,1280x800-24@70
> >>>
> >>> title=Gentoo 2.6.24-r8
> >>>
> >>> root (hd0,0)
> >>> kernel /boot/kernel-2.6.24-r8 root=/dev/sda3
> >>> video=vesafb:mtrr,ywrap,1280x800-24@70
> >>
> >> Could you please show us:
> >>
> >> $ mount
> >>
> >> and
> >>
> >> # ls -la /boot
> >
> > /dev/sda3 on / type ext3 (rw,noatime)
> > proc on /proc type proc (rw)
> > sysfs on /sys type sysfs (rw,nosuid,nodev,noexec)
> > udev on /dev type tmpfs (rw,nosuid)
> > devpts on /dev/pts type devpts (rw,nosuid,noexec)
> > shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
> > usbfs on /proc/bus/usb type usbfs
> > (rw,noexec,nosuid,devmode=0664,devgid=85) /dev/sda1 on /boot type ext2
> > (rw)
> >
> > total 17256
> > drwxr-xr-x  5 root root    1024 Jul  5 18:28 .
> > drwxr-xr-x 21 root root    4096 Dec 29  2007 ..
> > drwxr-xr-x  4 root root    1024 Aug 16  2007 boot
> > -rw-r--r--  1 root root   37395 Dec 25  2006 config-2.6.18-r5
> > -rw-r--r--  1 root root   35286 Dec 28  2006 config-2.6.18-r6
> > -rw-r--r--  1 root root   29907 Jul 19  2007 config-2.6.21-r4
> > -rw-r--r--  1 root root   39449 Aug  4  2007 config-2.6.22-r2
> > -rw-r--r--  1 root root   44583 Jul  5 18:48 config-2.6.24-r8
> > -rw-r--r--  1 root root   44541 Jun 23 18:25 config-2.6.25-r5
> > drwxr-xr-x  2 root root    1024 Jun 23 17:02 grub
> > -rw-r--r--  1 root root  486761 Oct  7  2006 initrd.img-2.6.17-sata
> > -rw-r--r--  1 root root 1637016 Dec 25  2006 kernel-2.6.18-r5
> > -rw-r--r--  1 root root 1606118 Dec 28  2006 kernel-2.6.18-r6
> > -rw-r--r--  1 root root 1916280 Jul 19  2007 kernel-2.6.21-r4
> > -rw-r--r--  1 root root 1740624 Aug  4  2007 kernel-2.6.22-r2
> > -rw-r--r--  1 root root 1847000 Jul  5 18:48 kernel-2.6.24-r8
> > -rw-r--r--  1 root root 2952220 Jun 23 18:24 kernel-2.6.25-r5
> > drwx------  2 root root   12288 Dec 27  2007 lost+found
> > -rw-r--r--  1 root root  738926 Dec 25  2006 system.map-2.6.18-r5
> > -rw-r--r--  1 root root  712206 Dec 28  2006 system.map-2.6.18-r6
> > -rw-r--r--  1 root root  813409 Jul 19  2007 system.map-2.6.21-r4
> > -rw-r--r--  1 root root  810321 Aug  4  2007 system.map-2.6.22-r2
> > -rw-r--r--  1 root root  870491 Jul  5 18:48 system.map-2.6.24-r8
> > -rw-r--r--  1 root root 1183038 Jun 23 18:25 system.map-2.6.25-r5
> >
> > I should probably give /boot a clean, but could this be the problem?
>
> According to your grub.conf your default is the top entry, but the
> kernel image for that doesn't exist in your boot partition.
>
> kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
>
> should probably be
>
> kernel /boot/kernel-2.6.22-r2 root=/dev/sda3
>
> Thats if 2.6.22-r2 is the kernel your trying to boot.
>
> HTH
>
> Matt

This is wierd, I hadn't noticed that, but that's not causing the problem.
I'm running the 2.6.22-r2 kernel now, that's the one that boots, the 2.6.24-r8 
is the one grub can't find. 
Matt

-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Dr. Matthew R. Lee
Instituto Biologia Marina 'Jurgen Winter'
Universidad Austral de Chile
Campus Isla Teja
Valdivia

matt@matthewlee.org

URL: meiochile.matthewlee.org
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-- 
gentoo-user@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-07-06  0:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-05 23:04 [gentoo-user] grub boot problem Matthew R. Lee
2008-07-05 23:15 ` Mick
2008-07-05 23:38   ` Matthew R. Lee
2008-07-05 23:47     ` Matt Harrison
2008-07-05 23:59       ` Dale
2008-07-06  0:13       ` Matthew R. Lee [this message]
2008-07-06  0:33         ` Matthew R. Lee
2008-07-06  7:05           ` Dirk Heinrichs
2008-07-06  0:27     ` Volker Armin Hemmann
2008-07-06 13:49 ` Neil Bothwick
2008-07-06 14:23   ` Volker Armin Hemmann
2008-07-06 14:41     ` Mick
2008-07-06 14:47       ` Dirk Heinrichs
2008-07-06 15:08         ` Alan McKinnon
2008-07-06 15:12       ` Volker Armin Hemmann
2008-07-06 14:47     ` Dirk Heinrichs
2008-07-06 15:12       ` Volker Armin Hemmann
2008-07-06 16:36         ` Dirk Heinrichs
2008-07-06 18:13           ` Volker Armin Hemmann
2008-07-07  6:58             ` Dirk Heinrichs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200807052013.20461.gentoo@matthewlee.org \
    --to=gentoo@matthewlee.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox