From owner-freebsd-stable Wed Jan 12 8:50:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 2B79015593 for ; Wed, 12 Jan 2000 08:50:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA02419; Wed, 12 Jan 2000 08:57:32 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001121657.IAA02419@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nate@mt.sri.com (Nate Williams) Cc: "Sean O'Connell" , stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE and ThinkPad 770Z with 256MB memory In-reply-to: Your message of "Wed, 12 Jan 2000 09:46:35 MST." <200001121646.JAA04479@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jan 2000 08:57:32 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I think you're right about what the problem is, but the solution will be a > > > little trickier in this case--the 770Z has 128MB built in. > > > > > > > What if you interrupt the boot process (hit a spacebar before > > the 10 seconds are up)... > > > > disk0s4a> set kern.vm.kmem.size=67108864 > > This is set too late in the boot process, since it's after the memory > sizing has been done. That's correct; you want hw.physmem, but in 4.x where that's available the memory probe itself has been improved to the point where it's not typically necessary to set it... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message