From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] Intel 82810-DC100 card and two PCs configuration
Date: Mon, 11 Nov 2002 10:36:47 +0900 [thread overview]
Message-ID: <2143e3e95e46b2feefec71ea6b130b41@granite.cias.osakafu-u.ac.jp> (raw)
I tried to use that on-board graphic chips for my Plan 9 terminal
at home. Yes, it does work (thank you very much who wrote this
driver, Who?), however, I got success for 640x480x8mode, but
failed for 1024x768x8. Is this the intended nature for this card?
Am I doing something wrong there?
Can the two machine configuration for home as suggested in Wiki,
auth/kfs server + diskless terminal, work? I've just tried it last night,
and got strange behaviour, such that I could not get kernel from
network etc.
Kenji
next reply other threads:[~2002-11-11 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 1:36 okamoto [this message]
2002-11-11 1:39 Russ Cox
2002-11-11 2:03 okamoto
2002-11-14 1:33 okamoto
2002-11-14 1:39 okamoto
2002-11-14 1:49 okamoto
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=2143e3e95e46b2feefec71ea6b130b41@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).