From owner-freebsd-current Sat May 2 08:34:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08305 for freebsd-current-outgoing; Sat, 2 May 1998 08:34:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles196.castles.com [208.214.165.196]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08245 for ; Sat, 2 May 1998 08:34:07 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id HAA00312; Sat, 2 May 1998 07:31:00 -0700 (PDT) Message-Id: <199805021431.HAA00312@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: ken@tydfam.machida.tokyo.jp cc: current@FreeBSD.ORG Subject: Re: Q) Strange mem size w/ current kernel In-reply-to: Your message of "Sat, 02 May 1998 18:31:02 +0900." <19980502183102D.ken@ns1.tydfam.machida.tokyo.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 02 May 1998 07:30:58 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sorry, it was a BIOS issue, although why the old kernel > showed correct mem size and new one not remains me as a > question. > > Mine was #401A0-0104, and upgrade to #401A0-0106 solved > the problem. The new kernel is probably using the BIOS get-memory functions to obtain more detailed memory information. Your old BIOS obviously didn't get this right. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message