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> In-Reply-To: <74872825-65a1-ed2f-29c9-77e225762339@osfux.nl> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190104194621.GF96232>