mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: kmh@nerdshack.com, linux-kernel@vger.kernel.org,
	lermen@elserv.ffm.fgan.de, lermen@fgan.de, davej@redhat.com,
	cebbert@redhat.com
Subject: Re: PROBLEM: loadlin incompatible with 2.6.23 kernels
Date: Thu, 22 Jan 2009 00:43:47 +0100	[thread overview]
Message-ID: <20090121234347.GI5237@const.famille.thibault.fr> (raw)
In-Reply-To: <4977AB27.8080608@zytor.com>

Hello,

H. Peter Anvin, le Wed 21 Jan 2009 15:09:27 -0800, a écrit :
> Kenneth Howlett wrote:
> >I do not know if the problem is with the kernel or with loadlin. Probably
> >some people will say it is the kernel's fault, and other people will say it
> >is loadlin's fault.
> >
> >I do not know why this occurs with loadlin and not with other boot loaders.
> 
> LOADLIN uses memory it isn't allowed to use by the boot protocol.  Newer 
> kernels use more memory than previous ones, and starts using memory 
> LOADLIN expects to use.
> 
> Unfortunately LOADLIN hasn't been updated for a very long time, and 
> there doesn't seem to be much interest in maintaining it.

I've fixed loadlin in debian and actually plan to maintain it upstream.
I had to patch it quite a bit to make it compilable by yasm, but it can
now boot recent big kernels & initrds.

Samuel

  reply	other threads:[~2009-01-21 23:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-24 22:00 Kenneth Howlett
2007-12-03  2:13 ` Bill Davidsen
2009-01-21 23:09 ` H. Peter Anvin
2009-01-21 23:43   ` Samuel Thibault [this message]
2009-01-22  0:16     ` H. Peter Anvin
2009-01-22  0:24       ` Samuel Thibault
2009-02-08  2:08       ` Samuel Thibault
2007-12-04 11:54 Etienne Lorrain

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=20090121234347.GI5237@const.famille.thibault.fr \
    --to=samuel.thibault@ens-lyon.org \
    --cc=cebbert@redhat.com \
    --cc=davej@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kmh@nerdshack.com \
    --cc=lermen@elserv.ffm.fgan.de \
    --cc=lermen@fgan.de \
    --cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®