From owner-freebsd-current@FreeBSD.ORG Fri Apr 25 09:42:57 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E665A37B401; Fri, 25 Apr 2003 09:42:57 -0700 (PDT) Received: from baraca.united.net.ua (vlan1.baraca.united.net.ua [195.234.212.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 388B143F85; Fri, 25 Apr 2003 09:42:56 -0700 (PDT) (envelope-from max@vega.com) Received: from vega.vega.com (xDSL-2-2.united.net.ua [193.111.9.226]) h3PGgpVG063412; Fri, 25 Apr 2003 19:42:51 +0300 (EEST) (envelope-from max@vega.com) Received: from vega.vega.com (max@localhost.vega.com [127.0.0.1]) by vega.vega.com (8.12.6/8.12.5) with ESMTP id h3PGhOQ8066629; Fri, 25 Apr 2003 19:43:24 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: (from max@localhost) by vega.vega.com (8.12.6/8.12.5/Submit) id h3PGhNgC066628; Fri, 25 Apr 2003 19:43:23 +0300 (EEST) Date: Fri, 25 Apr 2003 19:43:23 +0300 From: Maxim Sobolev To: John Baldwin Message-ID: <20030425164323.GA66424@vega.vega.com> References: <20030425061745.GD32731@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.7-STABLE i386 cc: Ruslan Ermilov cc: current@FreeBSD.ORG Subject: Re: i386/loader compiled with NOFORTH X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Apr 2003 16:42:58 -0000 On Fri, Apr 25, 2003 at 12:07:35PM -0400, John Baldwin wrote: > > On 25-Apr-2003 Ruslan Ermilov wrote: > > On Thu, Apr 24, 2003 at 05:45:15PM -0400, John Baldwin wrote: > >> > >> On 24-Apr-2003 Ruslan Ermilov wrote: > >> > On Thu, Apr 24, 2003 at 02:21:17PM -0400, John Baldwin wrote: > >> >> > >> >> On 24-Apr-2003 Ruslan Ermilov wrote: > >> >> > On 5.x, loader(8) compiled with -DNOFORTH, results in > >> >> > a system without a console. This does not affect the > >> >> > RELENG_4. > >> >> > > >> >> > Can someone who knows this code please look into it? > >> >> > >> >> No kernel console or no loader console? The usual problem with > >> >> no kernel console on 5.x is lack of device.hints. > >> >> > >> > No kernel console. The device.hints, it's there under /boot; > >> > I only reinstalled loader(8) with -DNOFORTH, and this gave me > >> > "no console" behavior. Can you try it locally? > >> > >> Since device.hints is read in by Forth code, I wouldn't be > >> surprised if it didn't work. When you break into the 10 > >> second countdown, do you have any hints set in the loader > >> environment? > >> > > Yes, figured this out by myself already. I've ended up > > uncommenting the "hints" line in GENERIC config, everything > > is OK now, and bzip2(1) also works, modulo the memory > > restrictions -- only level 1 bzipping works that requires > > ~250K of memory. > > > > John, is there a way to fix btx/loader/whatever so that > > heap memory is not limited to 640K? > > Not really. At least, not easily. We load the kernel up above 1mb, > but we don't know how much memory lives up above 1mb and we assume > that there is enough for the kernel and that's it. Why we can't just test it - i.e. write some value into each page and try to read it back? This will give at least rough estimate. -Maxim