From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: "Dave Täht" <dave@taht.net>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] hardware from hell
Date: Fri, 4 Mar 2016 12:27:17 +0000 [thread overview]
Message-ID: <CANmMgnHwOswyd5x9LfpBfscSnevBTpYZxGFHZbB9MHQaRqns9w@mail.gmail.com> (raw)
In-Reply-To: <56D8F016.6000100@taht.net>
On 04/03/2016, Dave Täht <dave@taht.net> wrote:
> I am A) still fiddling with alternate web site generators and B) just
> finished writing up (grousing) about all the hardware I just tried to
> make work.
>
> http://the-edge.taht.net/post/hardware_from_hell/
>
> I am about to tear apart the dual ethernet nuc we discussed here, again,
> swapping out everything in it to see if I can get it to work. I fear I
> fried it by trying to compile a kernel on it, or something....
Oo. I've got an Atom NUC I managed to "brick" by running kernel
4.5-rc which crashed. Twice in an hour, and now it's running without
problems but I can't trust it again yet. Sigh.
This is telling you to suck eggs, but I was able to get mine back
following the bios recovery procedure. It involves removing the
motherboard jumper.
http://www.intel.co.uk/content/www/uk/en/support/boards-and-kits/000005532.html?_ga=1.101398017.1051470898.1456842695
The weird part is I only had to "reset the CMOS" (their words), and
all that means on my model is entering "visual bios" (second wince)
and reset the settings to default.
Which you're _supposed_ to be able to do using the "power button menu"
(hold down power button to power on, release when the power button
changes e.g. from blue to orange). That did a number of different
things but nothing helpful.
Alan
next prev parent reply other threads:[~2016-03-04 12:27 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
2016-03-04 12:27 ` Alan Jenkins [this message]
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=CANmMgnHwOswyd5x9LfpBfscSnevBTpYZxGFHZbB9MHQaRqns9w@mail.gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--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