Date: Fri, 25 Apr 2003 22:59:18 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: i386/loader compiled with NOFORTH Message-ID: <20030425195918.GB28920@sunbay.com> In-Reply-To: <XFMail.20030425152258.jhb@FreeBSD.org> References: <20030425172227.GA11528@sunbay.com> <XFMail.20030425152258.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--MfFXiAuoTsnnDAfZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 25, 2003 at 03:22:58PM -0400, John Baldwin wrote: >=20 > On 25-Apr-2003 Ruslan Ermilov wrote: > > On Fri, Apr 25, 2003 at 12:07:35PM -0400, John Baldwin wrote: > >>=20 > >> On 25-Apr-2003 Ruslan Ermilov wrote: > >> > On Thu, Apr 24, 2003 at 05:45:15PM -0400, John Baldwin wrote: > >> >>=20 > >> >> On 24-Apr-2003 Ruslan Ermilov wrote: > >> >> > On Thu, Apr 24, 2003 at 02:21:17PM -0400, John Baldwin wrote: > >> >> >>=20 > >> >> >> 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. > >> >> >> >=20 > >> >> >> > Can someone who knows this code please look into it? > >> >> >>=20 > >> >> >> No kernel console or no loader console? The usual problem with > >> >> >> no kernel console on 5.x is lack of device.hints. > >> >> >>=20 > >> >> > 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? > >> >>=20 > >> >> 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? > >> >>=20 > >> > 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. > >> >=20 > >> > John, is there a way to fix btx/loader/whatever so that > >> > heap memory is not limited to 640K? > >>=20 > >> 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. > >>=20 > > I was referring to this message from loader(8): > >=20 > > BIOS 639kB/129856kB available memory > >=20 > > So I thought that the memory allocation in i386/loader is > > limited to real mode's 640KB, no? > >=20 > > Also, IIRC, the installation requirement was 8MB or so, > > and the runtime requirement was 4MB (these are 4.x numbers > > from my memory), so we can safely assume that we have at > > least 4MB of memory? Now that I look at it, I see that > > GENERIC kernel in 5.0 is 4.82MB, and so we can probably > > always assume that we have 8MB of memory. >=20 > We assume that we have enough memory to stick the kernel > up there, but that's the only assumption we make. :) >=20 You still does not answer my question: is the memory allocation in loader(8) limited to real mode 640KB? Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --MfFXiAuoTsnnDAfZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+qZOWUkv4P6juNwoRAnxLAJ42uO6nPc/YIL3Fmf16Fav7LUKNfACfWgPo BjuHnkEOIhV1Vv7sGkq5T+s= =iFof -----END PGP SIGNATURE----- --MfFXiAuoTsnnDAfZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030425195918.GB28920>