From owner-freebsd-stable@freebsd.org  Fri Jan  4 21:17:27 2019
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id CBB9F143A400
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Fri,  4 Jan 2019 21:17:27 +0000 (UTC)
 (envelope-from clay@milos.co.za)
Received: from lisa.milos.co.za (project.milos.za.net [109.169.49.139])
 by mx1.freebsd.org (Postfix) with SMTP id 2F9E485163
 for <freebsd-stable@freebsd.org>; Fri,  4 Jan 2019 21:17:25 +0000 (UTC)
 (envelope-from clay@milos.co.za)
Received: (qmail 4464 invoked by uid 89); 4 Jan 2019 20:50:43 -0000
Received: from unknown (HELO roundcube) (172.16.15.33)
 by vpopmail with SMTP; 4 Jan 2019 20:50:43 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 04 Jan 2019 21:50:43 +0100
From: clay@milos.co.za
To: Kurt Jaeger <pi@freebsd.org>
Cc: Mike Tancsa <mike@sentex.net>, freebsd-stable@freebsd.org, Ruben
 <mail@osfux.nl>, Michael Steinmann <support@pcengines.ch>,
 owner-freebsd-stable@freebsd.org
Subject: Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot
In-Reply-To: <20190104201007.GG96232@fc.opsec.eu>
References: <20181215200040.GO25709@fc.opsec.eu>
 <CAAX=mVNJAHgZ-DoQsFzWX7enyH=vAc4GMZx-k2fApj1g1v7=-Q@mail.gmail.com>
 <20181217103847.GT25709@fc.opsec.eu>
 <9909d7f5-d92a-3c0a-d6bb-e7b43c4367f3@osfux.nl>
 <20190104172349.GY96232@fc.opsec.eu>
 <74872825-65a1-ed2f-29c9-77e225762339@osfux.nl>
 <20190104194621.GF96232@fc.opsec.eu>
 <deac4168-6d76-2725-0306-e101bb20a499@osfux.nl>
 <a0a42088-a3a5-55eb-9e29-0f4b2299fef4@sentex.net>
 <20190104201007.GG96232@fc.opsec.eu>
Message-ID: <d4d85bf984d447f08870b84f2fc05be2@milos.co.za>
X-Sender: clay@milos.co.za
User-Agent: Roundcube Webmail/1.3.3
X-Rspamd-Queue-Id: 2F9E485163
X-Spamd-Bar: ------
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-6.98 / 15.00];
 NEURAL_HAM_MEDIUM(-1.00)[-0.999,0];
 NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[];
 NEURAL_HAM_SHORT(-0.98)[-0.984,0]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2019 21:17:28 -0000

On 2019-01-04 21:10, Kurt Jaeger wrote:
> Hi!
> 
>> What do the newer firmwares give you ? i.e. why upgrade ? On my APU3s 
>> I
>> am running
> 
>> and havent seen any issues with it ? Are there new features ?
> 
> I had an issue, FreeBSD 12.0 would only boot *very* slowly. That's why 
> I started
> upgrading to legacy 4.0.22, which would not boot at all, then to 
> 4.8.05,
> which worked 8-)

I upgraded to 12.0-RELEASE-p1 yesterday and am running coreboot v4.0.18 
on apu2c4 with no issues.

\\Clay