From owner-freebsd-stable@freebsd.org  Fri Jan  4 19:46:24 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 D74DC14376C2
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Fri,  4 Jan 2019 19:46:24 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 68A198100C;
 Fri,  4 Jan 2019 19:46:24 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from pi by fc.opsec.eu with local (Exim 4.91 (FreeBSD))
 (envelope-from <pi@freebsd.org>)
 id 1gfVQD-00096b-6q; Fri, 04 Jan 2019 20:46:21 +0100
Date: Fri, 4 Jan 2019 20:46:21 +0100
From: Kurt Jaeger <pi@freebsd.org>
To: Ruben <mail@osfux.nl>
Cc: Kurt Jaeger <pi@freebsd.org>, freebsd-stable@freebsd.org,
 Michael Steinmann <support@pcengines.ch>
Subject: Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot
Message-ID: <20190104194621.GF96232@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <74872825-65a1-ed2f-29c9-77e225762339@osfux.nl>
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 19:46:25 -0000

Hi!

> It was my understanding FreeBSD only worked with the "legacy" firmware
> releases.

Well, that's what I thought as well, but when the legacy did not work,
I tried the mainline (the 4.8.0.5), it worked.

> Since 4.8.0.5 is a "mainline" release, is there any particular
> reason not to go for the newest "mainline" release (v4.8.0.7) ?

I did not test the .7, due to my fatfingering during the download/update 8-}
As it worked, I'm fine for now.

-- 
pi@FreeBSD.org         +49 171 3101372                  One year to go !