9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] another dual-atom motherboard: jetway nc92-330
Date: Wed,  5 Aug 2009 07:38:47 -0400	[thread overview]
Message-ID: <1accc23e60dfc56339f2bb8e0708d6d0@quanstro.net> (raw)
In-Reply-To: <a54b6b9d427b86f1a6c8ebc6b5265bff@hamnavoe.com>

On Wed Aug  5 05:05:26 EDT 2009, 9fans@hamnavoe.com wrote:
> and a normal 20-pin atx power connector compared
> to the Intel's newer 24-pin one.

note that a 24-pin connector is preferable.  my atom
mb has a 24 pin connector but it is sold with a 20 pin
power supply.  the extra 4 pins are not required, but
they do give one extra flexability in selecting a power
supply.

this is analogous to having a 16-lane pcie connector
rather than an 8-lane pcie connector.

just to defend the intel and supermicro motherboards's
sata (it has nothing to do with the processor or motherboard):
this is an intel bug that i've verified exists on the following
southbridges: ich0, ich5, ich7r, ich9, ich9m, ich10r.  the bug manifests
when using sata disks in ide mode.  there is no problem
using sata disks in ahci mode or ide disks in ide mode.

i think defending against this bug will greatly reduce the number
of install failures.

anyway to contrast with the x7sla  you have:

	jetway		x7sla-h
gbe	1		2x
mptables	no		yes
s.b.	ich7		ich7r
p/sata	1/2		1/4 (ahci)
mem	1		2 slots
pci/pcie	1/0		1/2
audio	yes		no
fan	"noisy"		"quieter than my mouse"

here's the url for the jetway:
http://www.jetway.com.tw/jw/ipcboard_view.asp?productid=573&proname=NC92-330-LF
'
- erik



  reply	other threads:[~2009-08-05 11:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05  9:03 Richard Miller
2009-08-05 11:38 ` erik quanstrom [this message]
2009-08-05 11:55   ` Richard Miller
2009-08-05 13:52   ` Charles Forsyth

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=1accc23e60dfc56339f2bb8e0708d6d0@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=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).