Date: Fri, 31 Oct 1997 16:56:12 -0800 From: Ed Hudson <elh@svic.com> To: "John S. Dyson" <toor@dyson.iquest.net> Cc: dg@root.com, bugs@FreeBSD.ORG, hackers@FreeBSD.ORG, elh@svic.com, elh@spnet.com Subject: Re: 2.2.5 installation bug on 1gig machines Message-ID: <199711010056.QAA00276@xy.svic.com> In-Reply-To: Your message of "Fri, 31 Oct 1997 19:46:23 EST." <199711010046.TAA00336@dyson.iquest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
folks, thanks for the suggestions and clarifications. however, am i incorrect in my assumption that i can from another (2.2.5) machine rebuild the boot floppy w/o bounce buffers (and w/o any of the isa controllers that depend upon it) ? (in this case, internal access to the machine is the choice of last resort). btw, if i recollect correctly, i upgraded this machine from 2.2.1 to 2.2.2, all with the 1gig installed (2.2.2 just couldn't see the whole gig until i modified the kernel configuration and rebuilt). also, as a generic workaround, it would probably be usefull if at boot time i could say something like: boot: fd(0,a)/kernel -c MAXMEM=16384K thx, -elh > The problem with this is that the memory is already sized before > 'userconfig' is called (it needs to be that way for various reasons). This > basically means that we can't limit the memory during an install. You'll > have to physically pull out some of the memory and/or replace it with > lower density SIMMs until you've finished the installation and built a > customized kernel. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711010056.QAA00276>