9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: Cannot boot Plan 9 in my motherboard
Date: Sun, 10 Sep 1995 19:11:53 -0400	[thread overview]
Message-ID: <19950910231153.aQF8YXTGJdn8P82S-_D5WnqTD8xzoe1XM8ZdUJqJ0GM@z> (raw)

>>as the argument, but the system continued to fail to enlarge the window.

>>	Starting other programs such as mothra gave "Not enough bitmap
>>memory..." (more or less, I haven't written down the messages, sorry).
i completed the fix for part of this today: it's a refinement of a change i had to
make earlier for just the reason given above.  the problem is that on the PC
architecture, the screen dimensions and depth are highly variable within certain limits.
when the /dev/bitblt device is initialised, it allocates three screenfuls
of memory for bitmaps (failing that, a single screenful).  this works on most
machines, but the key variables can be zero (or at least too small) on the PC.
aux/vga sorts nearly everything out, but the memory allocated by /dev/bitblt
after that can be given back to the system for general allocation.  /dev/bitblt
will try to get it back on demand, but it allocates screenfuls,
and internal fragmentation of the kernel's memory pool means it can fail
(even though on my 16Mbyte machine there was over 3Mbytes available in all).

i'll try to post the changes tomorrow.  meanwhile, try adding

kernelpercent=40

to the plan9.ini file; see plan9.ini(8) for details and further explanation.

i find this makes things work as well as can be expected on a 4mbyte terminal.






             reply	other threads:[~1995-09-10 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-09-10 23:11 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-09-11 21:30 Jeremy
1995-09-10 22:38 Borja
1995-09-10 17:35 Borja

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=19950910231153.aQF8YXTGJdn8P82S-_D5WnqTD8xzoe1XM8ZdUJqJ0GM@z \
    --to=forsyth@plan9.cs.york.ac.uk \
    /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).