Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Valent Turkovic <valent@otvorenamreza.org>
Cc: Outback Dingo <outbackdingo@gmail.com>,
	 "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] nuc stuff
Date: Sun, 27 Mar 2016 09:48:28 -0700	[thread overview]
Message-ID: <CAA93jw4PWES4wE6qmUusLYTe1XokZnXbtHkEUv90m+Hyr14aYA@mail.gmail.com> (raw)
In-Reply-To: <CAGOios5qDwu3W3VmGjS9WEgheLVA1uaQ0hy7f_0D+cKTN_Sp7Q@mail.gmail.com>

The problem I had had with this nuc is that it can't drive any of my 3
HDMI monitors properly. Still have that problem... and darn it, all I
need the thing to do is install *something*... and then I'll never use
the screen again.

On Sat, Mar 26, 2016 at 6:01 PM, Valent Turkovic
<valent@otvorenamreza.org> wrote:
> If you are looking for absolutely most powerful device but in smaller form
> factor than NUC then check out PC Engines APU.1D, this amazing board is x86
> so it blows all other non-x86 devices away...

In general I am looking for a range of devices from low end to high.
This box does not count as
"high" (10GigE), but it looks equivalent to the turris omnia in most
respects. I like that it is x86 (for dev purposes).

> it should be similar or more
> powerful that Mikrotik CCR Cloud Routers.
>
> Software wise it can run FreeBSD, OpenWrt or Mikrotik OS.
>
> [1]
> http://www.pluscom.pl/en/pc-engines-apu-1d-3xgigabit-lan-2gb-ram-t40e-cpu-board-p2412.html
> - http://www.pcengines.ch/apu1d.htm
> [2] https://schemen.me/routeros-on-apu/
> - https://wiki.openwrt.org/toh/pcengines/apu
> - https://forum.openwrt.org/viewtopic.php?pid=316913

When I had last looked at this board there was no openwrt support, and
no BQL support for the onboard ethernet.

My experience with running bigger OSes on x86 off of a USB stick has
been dismal (all praise openwrt for nearly never writing to flash)

It looks like all that has improved in the past year or so. It runs
coreboot, which makes me happy, and having two easy to access mini-pci
slots would be helpful right now.  I ordered one.

Elsewhere I'd had a mostly dismal experience with current hackerboards
(c1,c2,rpi3), ipv6, and wifi usb sticks. The nice thing about that is
I just filed bugs on all of those issues and perhaps someone else will
fix 'em.

https://github.com/hardkernel/linux/issues/177 - fixed upstream already

https://github.com/raspberrypi/linux/issues/1370 - ignored

https://github.com/raspberrypi/linux/issues/1371 - pretty nasty kernel
bug in the rpi3's ipv6 stack (I think it's the ethernet driver, the
rpi2 does not have this problem)

...

I have a bunch of usb wifi sticks that all didn't work right for
various reasons. So moving to a mini-pcie set of boxes will help.

>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

  reply	other threads:[~2016-03-27 16:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 18:26 [Cerowrt-devel] archer c7v2 gets third party unupgradable firmware Dave Täht
2016-02-14 19:21 ` Michael Richardson
2016-02-14 21:25 ` Eric Johansson
2016-02-15  0:46 ` Rich Brown
2016-02-15 16:11   ` dpreed
2016-02-15 18:38     ` [Cerowrt-devel] nuc stuff Dave Täht
2016-02-15 19:25       ` Outback Dingo
2016-03-27  1:01         ` Valent Turkovic
2016-03-27 16:48           ` Dave Taht [this message]
2016-03-28  1:45           ` Outback Dingo
2016-03-28  1:51             ` David Lang
2016-03-28  1:54               ` Outback Dingo
2016-03-28  2:04                 ` Outback Dingo
2016-02-16  2:35     ` [Cerowrt-devel] archer c7v2 gets third party unupgradable firmware Matt Taggart

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=CAA93jw4PWES4wE6qmUusLYTe1XokZnXbtHkEUv90m+Hyr14aYA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=outbackdingo@gmail.com \
    --cc=valent@otvorenamreza.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox