Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Dave Täht" <dave@taht.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] hardware from hell
Date: Fri, 4 Mar 2016 06:48:41 +0200	[thread overview]
Message-ID: <CBFF0C6F-D092-448B-B354-902F984A5D7B@gmail.com> (raw)
In-Reply-To: <CAA93jw5sh-oMDzzbKjzyqy7f6j69=JzKCdnF5TB-m9vr1WaYMA@mail.gmail.com>


> On 4 Mar, 2016, at 05:11, Dave Taht <dave.taht@gmail.com> wrote:
> 
> So I am hard pressed for space in the general case. "Quiet", and low
> power are always my watchwords, also. Yurt couldn't draw more than 350
> watts, for example.

If space is the overriding concern, you might stack several identical machines vertically using standoffs through the mounting holes, and use PicoPSUs instead of standard ones.  That would mostly save you length rather than width or height, compared to the InWin case, but it’s something.  The limiting factor for height would be either the CPU heatsink or the NIC.

Alternatively, the InWin case can be left horizontal instead of vertical, and then you can stack identical machines on top of each other without messing around with standoffs.

The AMD box draws at most 25W for the CPU, so the heatsink scarcely has anything to do, so it’ll be quiet as long as the PSU is.  It certainly draws less power than an Intel-based box, unless it’s based on one of those (frankly awful) Atoms, and even then it’d be tricky to find a full-featured Atom machine which reliably stays below 25W under load.  There’s very little active hardware on the m/board, since the “CPU” is actually an SoC, and the NIC is low-power enough to not require a heatsink.

The PicoPSU has the advantage of being fanless, as well as taking up almost literally no space.  The downside is that it (and the 12V brick to supply it) costs more than the entire InWin case (with PSU) by some margin.

I recently used my old passively-cooled E-450 board (displaced by an upgrade to a Kaveri APU), a spare SSD, a PicoPSU and a CarTFT case to build a truly silent PC (which also happens to be very small).  That however leaves no room to add a second Ethernet port - the CarTFT case has no external slot corresponding to the PCIe slot.  It does still have the ath9k card in the mini-PCIe slot, and I can still attach antennae to the connectors on the rear panel.  Because it is passively cooled, though, I am keeping it vertical to permit convection through the heatsink.

If you want to copy that, here’s the board - if you can still find it on sale - and the case:

	https://www.asus.com/Motherboards/E45M1I_DELUXE/
	http://www.cartft.com/catalog/il/1058

 - Jonathan Morton


  reply	other threads:[~2016-03-04  4:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  2:16 Dave Täht
2016-03-04  2:47 ` Jonathan Morton
2016-03-04  3:03   ` Jonathan Morton
2016-03-04  3:11     ` Dave Taht
2016-03-04  4:48       ` Jonathan Morton [this message]
2016-03-04 12:27 ` Alan Jenkins
2016-03-04 21:57 ` Valent Turkovic
2016-03-05 16:08   ` moeller0
2016-03-05 10:09 ` Laurent GUERBY
2016-03-05 10:40   ` Sébastien Gaggini
2016-03-05 14:03     ` Outback Dingo
2016-03-05 22:28 ` dpreed
2016-03-11 11:34   ` Outback Dingo

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CBFF0C6F-D092-448B-B354-902F984A5D7B@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=dave@taht.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