From: Nicholas Knight <tegeran@home.com>
To: Floydsmith@aol.com, hpa@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re1: LOADLIN and 2.4 kernels
Date: Sat, 8 Sep 2001 02:21:05 -0700 [thread overview]
Message-ID: <01090802210500.00424@c779218-a> (raw)
In-Reply-To: <109.548ddae.28cb3697@aol.com>
In-Reply-To: <109.548ddae.28cb3697@aol.com>
On Saturday 08 September 2001 01:53 am, Floydsmith@aol.com wrote:
> >Hi everyone,
> >
> >I got a bug report of LOADLIN not working with recent -ac kernels, and
> >thought it might have something to do with my recent A20 changes that
> >were added to -ac. However, in trying to reproduce this bug, I have
> >been completely unable to boot *any* 2.4 kernel with LOADLIN-1.6,
> > trying this from Win98 DOS mode.
> >
> >Anyone have any insight into this? I really don't understand how the
> >A20 changes could affect LOADLIN, and it's starting to look to me that
> >there is some other problem going on...
> >
> > -hpa
>
<snip>
> loads the 2.4.x kernel into a buffer. The kernel then attempts boot
> just the "boot" sector stuff. This again probes for the total amount of
> system ram (64MB). But, because of the much greater size of 2.4.x
> kernels some memory location that himem uses (I think - maybe BIOS
Sounds like something booting to Safe Mode Command Prompt Only would fix,
as opposed to booting to plain command prompt mode
command prompt mode will load some drivers (such as himem), better not to
load them when using LOADLIN. Safe Mode Command Prompt Only boots
straight to the command prompt, very similar to setting init to /bin/sh
for a completely bare single-user mode.
prev parent reply other threads:[~2001-09-08 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 8:53 Re1: LOADLIN and 2.4 kernels Floydsmith
2001-09-08 9:21 ` Nicholas Knight [this message]
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=01090802210500.00424@c779218-a \
--to=tegeran@home.com \
--cc=Floydsmith@aol.com \
--cc=hpa@transmeta.com \
--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