9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Running an ASUS M8300 on Plan9
Date: Sun,  4 Feb 2001 11:08:18 +0000	[thread overview]
Message-ID: <E14PN1n-000BFB-0U@anchor-post-30.mail.demon.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 566 bytes --]

Though generalisations are generally wrong, generally it is safe to
say 'no vgas which are embedded in the motherboard chipset are
supported by Plan 9'.

But it's worse than that (generally).

Typically they main memory for their frame buffer, provide no means to
disable it, and the BIOS has no generic way to indicate which memory
it is.

So, even though fileservers don't need a vga, don't use embedded vga
chipsets as a fileserver unless you can disable framebuffer stealing.
It's a bit embarrassing when the buffer cache meets the console I/O.



[-- Attachment #2: Type: message/rfc822, Size: 1406 bytes --]

From: William Staniewicz <wstan@localhostnl.demon.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] Running an ASUS M8300 on Plan9
Date: Sun, 4 Feb 2001 11:34:44 -0500
Message-ID: <20010204103828.9A2D2199D7@mail.cse.psu.edu>

Here is a little more information:

the "SMI 721 3D video chip"

is found on the "MAGIC-765 Socket 370 Celeron
	Multimedia & Dual Ethernet Embedded Board"

ICP Electronics, Inc.

I know this is not on the list of preferred
hardware but can it be made to run? Also,
will the ethernet feature work?

		-Bill


             reply	other threads:[~2001-02-04 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-04 11:08 nigel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-04 16:34 William Staniewicz
2001-02-03  3:17 William Staniewicz
2001-02-03  1:30 William Staniewicz
2001-02-02 21:31 Russ Cox

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=E14PN1n-000BFB-0U@anchor-post-30.mail.demon.net \
    --to=nigel@9fs.org \
    --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).