From owner-freebsd-questions Thu Oct 22 16:22:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21093 for freebsd-questions-outgoing; Thu, 22 Oct 1998 16:22:35 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from laker.net (jet.laker.net [205.245.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21084 for ; Thu, 22 Oct 1998 16:22:33 -0700 (PDT) (envelope-from sfriedri@laker.net) Received: from nt (digital-pbi-150.laker.net [208.0.233.50]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id TAA31275; Thu, 22 Oct 1998 19:21:44 -0400 Message-Id: <199810222321.TAA31275@laker.net> From: "Steve Friedrich" To: "Geoffrey Robinson" , "questions@FreeBSD.ORG" Date: Thu, 22 Oct 1998 19:08:39 -0400 Reply-To: "Steve Friedrich" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Installing on a System with Too Much RAM Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Oct 1998 18:18:27 -0400, Geoffrey Robinson wrote: >I'm trying to install FBSD 2.2.7 on a server with a gig of RAM. Problem is, >when it reboots to load the generic kernel for the first time it panics >with a bounce buffers error. Somebody on IRC talked vaguely about a way of >telling the kernel to assume the amount of system memory is less that the >actual amount so I could recompile the kernel without BOUNCE_BUFFERS then >reboot and use the full amount. Unfortunately I can't get it to work the >way it was described and I'm not sure such a feature even exists. Dose it? When you get the boot prompt, enter -c to enter the configuration screen... at the config> prompt, enter ? to get help enter ls to list devices. there is a device called npx0, and if you set it's iosize to 32768, the kernel will only see 32MB NEXT time you boot (NOT this time). so set it like this... iosize npx0 32768 (or whatever) then use ls again to see the change use q to quit the system will finish this boot sequence and probably panic like before. Don't worry, be happy. Next boot should recognize your change (check the "avail memory" during boot process) For more reading, search for MAXMEM in /sys/i386/conf/LINT Unix systems measure "uptime" in years, Winblows measures it in minutes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message