From: Jeremy Fitzhardinge jeremy@suede.sw.oz.au
Subject: Cannot boot Plan 9 in my motherboard
Date: Mon, 11 Sep 1995 17:30:04 -0400 [thread overview]
Message-ID: <19950911213004.1gq88s-_JdVlqUkPHB2yacBU2zpt1wEucyraMB4yR5Q@z> (raw)
On Sep 10, 6:38pm, Borja Marcos wrote:
> Starting other programs such as mothra gave "Not enough bitmap
> memory..." (more or less, I haven't written down the messages, sorry).
> If I opened another shell window, the menu for the button three appeared
> garbled with the background.
>
> Do you think it's an incompatibility with the motherboard? Or is
> it just a small swap partition? ( I have the default 10 MB partition).
I get this too. I doubt it's a motherboard compatability problem.
When I use 1152x864x8 I can only get up a couple of small windows.
Enlarging them or trying to create new ones just fails. Creating
windows with the window command fails with a message something like
"out of resources". If I run sam on the bare console in this mode, it
often fails with a message about not being able to allocate bitmap
memory.
If I run the system at 1024x768x1, none of this happens, so I assume
it's a memory problem. However, there doesn't seem to be a shortage of
either real or virtual memory when the allocations fail, so I assume
it's some pool of kernel memory which is being exhausted. I looked at
the code, but not closely enough to see what was going on.
How does one run a reasonable number of usefully sized windows at high
resolutions?
Details: #9 GXE 64 video card, i486 DX2 66, 16MB memory, IDE drive.
J
next reply other threads:[~1995-09-11 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-11 21:30 Jeremy [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-09-10 23:11 forsyth
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=19950911213004.1gq88s-_JdVlqUkPHB2yacBU2zpt1wEucyraMB4yR5Q@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).