linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brett <generica@email.com>
To: Wichert Akkerman <wichert@wiggy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.69 just doesn't boot (neither does anything > .67)
Date: Tue, 6 May 2003 22:34:04 +1000 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0305062230420.2201-100000@bad-sports.com> (raw)
In-Reply-To: <20030506124249.GG20419@wiggy.net>

On Tue, 6 May 2003, Wichert Akkerman wrote:

> Previously Brett wrote:
> > (0.93 fails to compile, reported to grub savannah page, and have heard 
> > nothing back from)
> 
> 0.92 is over a year old and a lot has changed since then. Debian has
> grub 0.93 packages which work fine with 2.5.67-69 for me, you could try
> that.
> 

linuxfromscratch system
unless they fix the source compilation problem i reported
<http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3343&group_id=68>
then i can't install it

and anyway, can you provide any backup that this will fix it ?? what 
changed between 2.5.66 and 2.5.67 to stop grub loading the kernel ? why 
hasn't anyone else reported this ???

i'm just highly dubious that upgrading grub one revision will help

and it isn't something i can do right now anyway

thanks,

	/ Brett


  reply	other threads:[~2003-05-06 12:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 11:39 2.5.69 just doesn't boot (neither does anything > .67) Brett
2003-05-06 12:06 ` Wichert Akkerman
2003-05-06 12:00   ` Brett
2003-05-06 12:42     ` Wichert Akkerman
2003-05-06 12:34       ` Brett [this message]
2003-05-06 12:57         ` Wichert Akkerman
2003-05-06 12:58           ` Brett
2003-05-06 13:23             ` Wichert Akkerman
2003-05-07  0:19               ` Brett
2003-05-06 13:26           ` Daniel Pittman
2003-05-07  0:20             ` Brett
2003-05-06 12:08 ` William Lee Irwin III
2003-05-06 11:53   ` Brett

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=Pine.LNX.4.44.0305062230420.2201-100000@bad-sports.com \
    --to=generica@email.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wichert@wiggy.net \
    /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;
as well as URLs for NNTP newsgroup(s).