Update 11.3 > 11.4
aryeh.friedman at gmail.com
Wed Jun 17 21:12:40 UTC 2020
Let's see the fact I am typing this reply on "FreeBSD neomarx
12.1-RELEASE-p6 FreeBSD 12.1-RELEASE-p6 r362146 GENERIC amd64" with a USB
keyboard and mouse via an external hub (and never seen that message) is
proof enough it is fixed (with the same BIOS and processor class as
reported!). Don't believe everything you read in bug reports. Looking
through the bug it is clear that it was likely due to a faulty upgrade (or
pre-release 12.1) not due to an actual bug.
On Wed, Jun 17, 2020 at 4:59 PM Jerry <jerry at seibercom.net> wrote:
> On Wed, 17 Jun 2020 13:46:51 -0400, Aryeh Friedman commented:
> >On Wed, Jun 17, 2020 at 1:42 PM Jerry <jerry at seibercom.net> wrote:
> >> Due to a long standing bug,
> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666, I am unable
> >> to use FreeBSD 12.x.
> >Been fixed in 12.X for eons (the last bug report was on a beta
> >version). Also bsd-update is really not the "right" way (it is a
> >supported way but not the prefered way). Do the update from sources
> >and you should have no problem (I have done the same upgrade on 5
> >machines now with no issue).
> That bug existed until at lest 5/16 when I last attempted to install
> 12.1 on the system. Not exactly eons. Furthermore, if it has been fixed,
> why is it still open?
> Please supply actual proof, not conjecture, that it is fix. I have no
> intention of wasting valuable time on bad info.
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
More information about the freebsd-questions