From: Paul Borman prb@bsdi.com
Subject: cant start 9pcfs
Date: Thu, 14 Mar 1996 13:29:49 -0500 [thread overview]
Message-ID: <19960314182949.jMSCwRsmkewCrLdmXCKtVxQqxDUoaTAX3d9FhuQmVG0@z> (raw)
> >>This is most certainly due to a memory sizing problem (heaven knows
> >>we have made the rounds with this one with BSD/OS...) For now I
>
> are the bytes in the CMOS that give the extended memory size not standard,
> or do some machines not set them correctly?
Well, we have found that many (all?) Dell machines think that the CMOS
can never report more than 16MB, so it doesn't, even if you have more
than 16MB of memory. Then there are machines which we can't accurately
probe for how much memory there is, but the CMOS is right! There are
also weird caching affect (i.e. you can read/write memory beyond the
end of memory as long as it stays in cache) as well as new and unique
ways to remap addresses that are beyond the end of memory. To give you
and idea, here are the various parameters one can set in their boot.default
file for BSD/OS:
-basemen mem Assume this much base memory (memory below 1M)
-cmosmem Limit memory search to the mount given by the CMOS
-extended mem Limit the amount of memory to check
-memsize mem Just assume this it the amount of memory
-noflushcache Don't flush the cache while sizing memory
Each one of these is needed for at least one machine that we have had
problems with. I should note that we can probe the proper amount of
memory on *most* machines, but...
Finding out how much memory you have is certainly a black art.
-Paul Borman
prb@bsdi.com
next reply other threads:[~1996-03-14 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-14 18:29 Paul [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-03-14 9:32 forsyth
1996-03-14 4:45 Paul
1996-03-14 1:46 jim
1996-03-13 21:39 Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19960314182949.jMSCwRsmkewCrLdmXCKtVxQqxDUoaTAX3d9FhuQmVG0@z \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).