From: "Johannes Grødem" <st@kopkillah.com>
To: linux-smp@vger.kernel.org
Subject: Re: Asus A7M266-D mainboard.
Date: Sun, 11 Aug 2002 23:38:48 +0200 [thread overview]
Message-ID: <lzu1m1gjo7.fsf@unity.copyleft.no> (raw)
In-Reply-To: 1029103166.16236.85.camel@irongate.swansea.linux.org.uk
* Alan Cox <alan@lxorguk.ukuu.org.uk>:
> Yes on the whole. BIOS version matters and there are problems sometimes
> with broadcomm nics and some other boards.
We thought we'd go with some Intel NICs. (i82550-based, IIRC.)
> They suck power too so you need a big case 430W+ PSU and plenty of
> fans.
Hm. They've only got 340W. I'm thinking of getting this Asus-board
instead of some MSI-board (K7D Master-L) which seem to be broken, but
could the malfunctions (Tekram SCSI-controllers not working,
filesystem corruption, segfaults at weird places) be caused by too
little power? Or would it just simply not work with too little power?
The cooling should be sufficient, though.
> The dual Athlons are pretty decent but they've lost the edge (from
> my current benchmarks) to Intel on speed with the 2.4GHz PIV.
It isn't that critical that they're fast so long as they're
reliable/stable. If PIV is more reliable, maybe we should go for
those. Do you have any motherboard-recommendations? (I'm having a
hard time finding good hardware-advice when it comes to stability,
people seem to test mostly for performance.)
Thanks a lot for the response, by the way.
--
Johannes Grødem
next prev parent reply other threads:[~2002-08-11 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-11 19:28 Asus A7M266-D mainboard Johannes Grødem
2002-08-11 21:59 ` Alan Cox
2002-08-11 21:38 ` Johannes Grødem [this message]
2002-08-11 23:12 ` Alan Cox
2002-08-19 19:36 ` Christian HOFFMANN
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=lzu1m1gjo7.fsf@unity.copyleft.no \
--to=st@kopkillah.com \
--cc=linux-smp@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.