From: Floydsmith@aol.com
To: tegeran@home.com, linux-kernel@vger.kernel.org
Cc: Floydsmith@aol.com
Subject: Re2: LOADLIN and 2.4 kernels
Date: Sat, 8 Sep 2001 06:46:16 EDT [thread overview]
Message-ID: <51.10cc64a8.28cb50f8@aol.com> (raw)
>> >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.
Yes, indeed, not loading himem does solve the problem I had. But, do to the
fact that I need extented memory (for a DOS ramdisk) and for some TSR(s)
(like smartdrv) for a LS-120 boot disk I use as both a Linux and DOS "rescue"
disk, I need "himem".
Floyd,
next reply other threads:[~2001-09-08 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 10:46 Floydsmith [this message]
2001-09-08 20:02 ` Re2: LOADLIN and 2.4 kernels H. Peter Anvin
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=51.10cc64a8.28cb50f8@aol.com \
--to=floydsmith@aol.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tegeran@home.com \
/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