From: Jean Mehat <jm@ai.univ-paris8.fr>
To: 9fans@cse.psu.edu
Subject: [9fans] #i: no frame buffer
Date: Fri, 10 Nov 2000 12:54:45 +0100 [thread overview]
Message-ID: <200011101154.eAABsjM04073@hon.ai.univ-paris8.fr> (raw)
At last, I received the machines where I intend to install the new release
of Plan 9.
The system went nicely as a terminal (Pentium III/Xeon 733MHz on an
ASUS CUV4XM motherboard, HD IDE 15G, 3C905 TXM network card and Matrox
vga card based on MGA2164W AGP rev. 0).
Trying to configure the very same machine as a cpu/auth server, I
have the same 'bind: #i: no frame buffer' problem that some others
encountered.
I tried to add (blindly) in main.c:confinit the memory allocation
done on terminals, but if doesn't change anything.
I know video is not necessary on cpu servers, but out of curiosity,
has anyone a working draw device on a cpu server ?
jmehat@ai.univ-paris8.fr
next reply other threads:[~2000-11-10 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 11:54 Jean Mehat [this message]
2000-11-10 12:42 ` arisawa
2000-11-10 15:33 ` Fco. J. Ballesteros
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=200011101154.eAABsjM04073@hon.ai.univ-paris8.fr \
--to=jm@ai.univ-paris8.fr \
--cc=9fans@cse.psu.edu \
/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).