Date: Thu, 14 Nov 1996 13:34:27 -0500 (EST) From: John Dyson <dyson@dyson.iquest.net> To: karl@Mcs.Net (Karl Denninger) Cc: hackers@freebsd.org Subject: Re: Hmmmm... now I'm confused Message-ID: <199611141834.NAA01376@dyson.iquest.net> In-Reply-To: <199611141807.MAA29039@Jupiter.Mcs.Net> from "Karl Denninger" at Nov 14, 96 12:07:42 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > Hi folks, > > Ok, now I don't understand..... > > I built a new kernel with -current to support more than 128MB with the > following options.... > > options "MAXMEM=262144" # 256 * 1024, 256MB maximum RAM > options "MAXDSIZ=201326592" > options "DFLDSIZ=201326592" > > 256MB supported RAM and huge process sizes... > > Those were the only changes from a working kernel which is running on > the same hardware (a Pentium PRO 200 with 128MB of RAM). Then I added > more physical memory. > > I rebooted, and the "de" cards in the box (two 100BaseTX boards) both > disappeared! > > They identify ok during the boot, and claim to be there, but an "ifconfig > de0" comes up "no such device"! > > I removed the extra RAM and went back to 128M, and it STILL happens! > With or without the memory in there; it appears that the MAXMEM line up > there blows the de cards out of the water! > > What's going on here, and is there a work-around for this? > Did you control the experiment and determine if it is/might be the MAXMEM (phys mem) or the MAX/DFL DSIZ definitions? It sounds to me that it is the (MAX/DFL)DSIZ definitions -- right, or am I dense? :-)... John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611141834.NAA01376>