From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] update on that nuc I was fighting with
Date: Thu, 14 Apr 2016 08:40:53 -0700 [thread overview]
Message-ID: <CAA93jw6Nc=gLZJ4UGFbi40UvQ6XCW_xsaWbUKBZuxHPbcFhK=Q@mail.gmail.com> (raw)
In-Reply-To: <20160414065615.GA14284@radio2.ebirdie>
On Wed, Apr 13, 2016 at 11:56 PM, Erkki Lintunen <erkki.lintunen@iki.fi> wrote:
> * Dave Taht <dave.taht@gmail.com> [2016-04-13 17:11:44 -0700]:
>
>> Hoo, boy, did I have issues. I finally got around to trying to get it
>> up and running linux.
>>
>> For reference, this was the:
>>
>> - Jetway NU93-2930 NUC Form Factor Intel Celeron N2930 SoC Bay Trail 2
> ...
>> Well, it turns out there is a BIOS fix here, which I have not installed yet.
>
> Matthew Garrett's blog-post might give peace of mind.
> <https://mjg59.dreamwidth.org/41713.html> and especially in it's
> comments are info about Intel chip microcode versions.
Sigh. Pain shared, reduced, Joy shared, increased.
Corollary: With enough pain shared, fixes can be found.
This will not be the first time I stepped too far off the bleeding
edge, nor the last.
I am still in search of *something* that will let me install an ath10k
and follow along on the wonderful results michal is getting on
fq_codel for wifi on that chipset.
https://lists.bufferbloat.net/pipermail/codel/2016-April/002165.html
I was tempted to swap out for the ivy bridge box and tear apart the
nuc that I use as my main desktop to do it, but with the heat thing
being a potential problem also, reluctant.
/me goes searching for another board
> One might only get microcode through Jetway and Jetway (at least I have
> doubts) might be a vendor not giving much concern toward other OSs. E.g.
> the comments in Garrett's blog say Windows AHCI driver handles
> power-states ok, so the issues with Linux may not be a priority to
> Jetway unless in volume made known to it.
>
> Nice info for me also as I was about to upgrade an old Pentium box
> running 24x7 to a Bay Trail platform, but have to put it on hold and
> watch on this as the comments also reference to Intel's caution about
> theirs chips long term reliability if the power-states aren't right.
>
> - Erkki
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next prev parent reply other threads:[~2016-04-14 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 0:11 Dave Taht
2016-04-14 6:56 ` Erkki Lintunen
2016-04-14 15:40 ` Dave Taht [this message]
2016-04-19 15:19 ` Jonathan Morton
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='CAA93jw6Nc=gLZJ4UGFbi40UvQ6XCW_xsaWbUKBZuxHPbcFhK=Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.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