From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] [Q] intel i810 support
Date: Thu, 14 Jun 2001 15:49:12 +0000 [thread overview]
Message-ID: <3B28D793.E99F9A05@null.net> (raw)
In-Reply-To: <Pine.GSO.4.20.0106141432150.28866-100000@konark.ncst.ernet.in>
Jayprasad Hegde wrote:
> I am not able to install Plan 9 on my system.
> I contacted plan 9 support and they say this has to do with the intel 810
> chipset that i am using.
I don't understand that. I have the 815 chipset, which is quite
similar,
and although there were some installation problems, they were not due to
the chipset. Perhaps you could be more specific about the symptoms?
next prev parent reply other threads:[~2001-06-14 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 3:27 [9fans] alarm handling and suspended machines presotto
2001-06-13 12:02 ` Lucio De Re
2001-06-13 19:28 ` Mike Haertel
2001-06-14 14:34 ` [9fans] [Q] intel i810 support Jayprasad Hegde
2001-06-14 15:49 ` Douglas A. Gwyn [this message]
2001-06-14 20:10 ` Martin Harriss
2001-06-15 14:19 ` Douglas A. Gwyn
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=3B28D793.E99F9A05@null.net \
--to=dagwyn@null.net \
--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).