Date: Wed, 24 May 2000 14:33:25 +0100 From: "Paul Walsh" <paul@walshsimmons.co.uk> To: "Lowell Gilbert" <lowell@world.std.com> Cc: <questions@freebsd.org> Subject: RE: MAXMEM on freeBSD3.4-RELEASE Message-ID: <010c01bfc584$a38dd700$7bd1c8c2@nationnet.com> In-Reply-To: <44vh04uluw.fsf@lowellg.ne.mediaone.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks. It was quicker to recompile - kernels are now built and humming .... Great OS - been using it for 5 years. Regards, Paul Walsh WALSH SIMMONS The Old Bank, 247 Chapel St, Manchester, UK T:01618399337 F:01618399336 ISDN:01618346884 www.walshsimmons.co.uk Paul mobile: 07714 523312 Sweet dreams at http://www.laterooms.com -----Original Message----- From: lowell@lowellg.ne.mediaone.net [mailto:lowell@lowellg.ne.mediaone.net]On Behalf Of Lowell Gilbert Sent: 24 May 2000 14:19 To: Paul Walsh Subject: Re: MAXMEM on freeBSD3.4-RELEASE paul@walshsimmons.co.uk (Paul Walsh) writes: > Only seeing 64M on a Dell P550 with 384M of ram > > Have tried: > > boot -MAXMEM=393216 > > from loader - any suggestions for a temp fix? > > Could I use kernel_options in /boot/defaults/loader.conf - if so what > syntax? > > I have RT'd every FM by the way ;-) > > I intend to rebuild kernel first chance I get ... As a rule, that *is* the recommended temporary fix. None of the other things you mentioned have any chance of working that I can see; MAXMEM is a compile-time variable, and thus can't be set at runtime. There are some references to a hw.maxmem variable, but I can't track it down quickly; you might play with "set hw.maxmem=393216", but it may not help... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?010c01bfc584$a38dd700$7bd1c8c2>