From owner-freebsd-stable@freebsd.org Fri Jan 4 17:23:53 2019 Return-Path: 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 F05CE1432DCB for ; Fri, 4 Jan 2019 17:23:52 +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 8458E726E6; Fri, 4 Jan 2019 17:23:52 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by fc.opsec.eu with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1gfTCH-000Aet-G1; Fri, 04 Jan 2019 18:23:49 +0100 Date: Fri, 4 Jan 2019 18:23:49 +0100 From: Kurt Jaeger To: Ruben Cc: Kurt Jaeger , Michael Steinmann , freebsd-stable@freebsd.org Subject: Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot Message-ID: <20190104172349.GY96232@fc.opsec.eu> References: <20181215200040.GO25709@fc.opsec.eu> <20181217103847.GT25709@fc.opsec.eu> <9909d7f5-d92a-3c0a-d6bb-e7b43c4367f3@osfux.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9909d7f5-d92a-3c0a-d6bb-e7b43c4367f3@osfux.nl> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2019 17:23:53 -0000 Hi! > Has there been any progress on this? > > I'm asking because I'd very much like to upgrade my apu's to FreeBSD 12 as > well! Well, if you can upgrade your firmware to 4.8.0.5, it should work (it was a re-install). -- pi@FreeBSD.org +49 171 3101372 One year to go !