public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNC] Linld 0.94 available
Date: Thu, 17 Jan 2002 09:09:48 -0800	[thread overview]
Message-ID: <3C47055C.3010103@zytor.com> (raw)
In-Reply-To: <200201171432.g0HEW4E17589@Port.imtp.ilyichevsk.odessa.ua>

Denis Vlasenko wrote:

> 
> Ok, I brought old Turbo Debugger from home...
> 
> It is not true on this box I type this message right now. 128 MB RAM.
> Under DOS:
> INT 15 AX=E801 returns carry set and AH=86 (have no BIOS manual here to look 
> up this error code), other registers unchanged.


AH=86 is function not supported.

However, once again, you're running UNDER DOS.  You probably should 
query HIMEM.SYS for the memory size,


> INT 15 AH=88 returns AX=0.
> INT 15 AX=E820 - not tested, but obviously not working (or else kernels would 
> boot fine without linld/loadlin kludge or kernel patch)
> 
> So we have "triple-0" failure extracting mem size info from INT 15.


... because you're running under DOS.

> 
> Just imagine old lovely 486 box never tested by manufacturer to work well 
> with 64 MB of RAM. Joe Random Hacker plays Meg-o-Rama, but BIOS does not 
> understand how that can be: int 15 fn 88 does not fit in 16-bit reg?!
> DOS does not boot, Joe says: well, Linux rulez, it will boot! but no...
> 
> OTOH, CMOS reading hack most probably would not work either... memscan time?
> 


By the time 64 MB RAM became supported, INT 15 AX=E801 was already 
common.  For pathological cases like you describe, it's "mem=" time.

	-hpa



  reply	other threads:[~2002-01-17 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 18:31 [ANNC] Linld 0.94 available Denis Vlasenko
2002-01-17 17:09 ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-16 13:10 Denis Vlasenko
2002-01-16 19:10 ` 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=3C47055C.3010103@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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