Date: Wed, 12 Jul 1995 11:37:33 -0500 From: "Greg Rowe" <greg@mn.interact.net> To: Robert Watson <rwatson@sidwell.edu>, questions@freebsd.org Subject: Re: NIS config and over 16megs of ramon EISAm Compaq Message-ID: <9507121137.ZM26482@nevis.oss.interact.net> In-Reply-To: Robert Watson <rwatson@sidwell.edu> "NIS config and over 16megs of ramon EISAm Compaq" (Jul 12, 11:25am) References: <Pine.BSD/.3.91.950712111243.25327A-100000@gateway.us.sidwell.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
I just posted this Compaq question to the FreeBSD newsgroup. I'll let you know if I hear anything. >> I've tried before to get past the problems with using over 16 megs of Memory >>on a Compaq EISA bus machine. I followed Terry Lambert's (and a few others) >>suggestions on changing the meminit routine, and although the kernel now says >>I have 24 meg of memory, it then marks the memory over 16 meg as bad. >> >> My question is, has anyone managed to get a Compaq EISA bus system to run >>FreeBSD with over 16 megs of memory, and if so what model Compaq was it ? On Jul 12, 11:25am, Robert Watson wrote: > Subject: NIS config and over 16megs of ramon EISAm Compaq > > I have two questions(and a broken space bar, please excuse any > misformatting of this email) > > I'm running a freebsd system (two,actually) on an ethernet containing a > series of sparc servers and stations. They run NIS+ to handle user > accounting and home directories. I know FreeBSD has NIS support -- odes > it support NIS+, and how would I go about configuring my system as a > client? I read the yp/ypbind manpages and enabled ypbind in > /etc/sysconfig -- I don't know what other changes to make though (eg., > the group/passwd changes.) > > One of the systems is a Compaq 466/33 (486/33 for the un-compaq-literate) > containing 40 megs of RAM. FreeBSD only sees the first 16 megs of RAM > though. BOUNCE_BUFFERS are enabled in the kernel per the suggestion of > the comments in LINT. Thoughts would be welcome (DOS recognizes and uses > it fine. The system runs an EISA bus.) > > Another question,actually. I went through the FreeBSD installation on the > firstsystem, and it didn't write the boot code (this has happened to me a > few times wheile installing FreeBSD on IDE systems -- it just doesn't > write thebootcode.) I did some playing, and I know that the root > partition is fine, and bteasy is fine -- bteasy shows the 386bsd? prompt > for the bootup, but then it just loops there when f1 is hit. I tried > using disklabel to relable the disk as follows: > > > cd /usr/mdec;disklabel -B -b wdboot -s bootwd wd0 > > and got the following messages: > > Warning, revolution/minute 0 > super block size 0 > > and then back at the prompt again. If I stick a boot floppy (eg.,the > installation disk) in the drive and enter wd(0,a)/kernel it will boot off > of the HD fine.So I guess the boot loader didn't get installed?Advice > would be appreciated. > > Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ > The goal of science is to build better mousetraps. The goal of nature > is to build better mice. > >-- End of excerpt from Robert Watson -- Greg Rowe | US West - Interact Services | INTERNET greg@mn.interact.net 111 Washington Ave. South | Fax: (612) 672-8537 Minneapolis, MN USA 55401 | Voice: (612) 672-8535 To err is human, to really foul up requires the root password.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9507121137.ZM26482>