Nathan
-----Original Message-----
From: Prashant TR [mailto:prashant_news@yahoo.com]
Sent: Saturday, December 04, 1999 7:03 AM
To: Paul
Cc: linux-kernel@vger.rutgers.edu
Subject: Re: memory detection problems: 2.0.x vs. 2.2.x
Paul <set@pobox.com> wrote:
> I have an odd 386 machine running a 2.0.33 kernel. This kernel boots
>fine, and detects the correct amount of ram, as did many 2.0.x kernels
>before it.
> Recently, I needed the old beast for some tests, and it required a
>2.2.x kernel. However, the 2.2.[12, 13] kernels that I tried detect
>a strange large amount of ram. Using mem=xxxx solves the problem,
>but I am curious
>why there should be a problem.
The new kernel is probably using the real mode AX=E801H/INT 15H
to get the total memory size. Since there are a few buggy old 386
BIOSes, this can happen. Your old version must have used the
standard AH=88H/INT 15H to get the memory size.
Since using MEM=xxx overrides the detection, you don't get
problems with this.
Prashant
__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/