Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Jun 2020 07:14:56 -0400
From:      Jerry <jerry@seibercom.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: Update 11.3 > 11.4
Message-ID:  <20200618071456.00004fdd@seibercom.net>
In-Reply-To: <CAGBxaXkvj6aMQeQ2mScsB6VsGye-Y+Z7WDp=q48uS6uCZ2vrVg@mail.gmail.com>
References:  <20200617134146.00004ce8@seibercom.net> <CAGBxaXmN0wAhZq36H7y7H8f2qnCrjFyos9vPf_em47KCL2TvLA@mail.gmail.com> <20200617165853.000070ca@seibercom.net> <CAGBxaXn-WzZ_J8Ec=FaetqF-p4=dZtWU=b1rgipvs8MD0wsEjA@mail.gmail.com> <20200617195705.000069f0@seibercom.net> <CAGBxaXkvj6aMQeQ2mScsB6VsGye-Y+Z7WDp=q48uS6uCZ2vrVg@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Wed, 17 Jun 2020 20:44:04 -0400, Aryeh Friedman commented:
>On Wed, Jun 17, 2020 at 7:57 PM Jerry <jerry@seibercom.net> wrote:
>
>> On Wed, 17 Jun 2020 17:12:27 -0400, Aryeh Friedman commented:  
>> >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.  
>>
>> Are you using it on the exact same PC that the error has been
>> reported on? Actually, I believe there are three units. Furthermore,
>> just last month I again tried to install 12.1 and it filed
>> immediately with the message as depicted in the PC.
>>  
>
>It was reported on three different BIOS's and motherboards therefore
>it is almost certainly not tied to a specific configuration (the only
>clue is it on older machines, but even here I have 12.1 working just
>fine on a machine that is older than the any the list, I also have it
>running on newer machines).   The fact that it is not tied to a
>specific hardware configuration means it *SHOULD* appear on any x86
>based machine running 12.1.   But, of course that is not true because
>the above just described the vast majority of 12.1 machines out there.
>  Thus we are left with only one possible conclusion who ever reported
> it and/or experiences it is
>making some kind of user error (what it is who knows!).
>
>
>> Sorry, but I do not have time to waste on unsubstantiated gossip.
>>  
>
>Yet you have time to complain about how the FreeBSD community refuses
>to get with the times when it comes to MUA's.   I guess your
>experience here disproves your claim that "newer is better" in all
>regards and that "shiny objects" are more important than
>functionality.   Perhaps your time is better spent figuring out what
>user error you made to trigger the "bug" that you're complaining about
>(since it almost certainly is not an actual bug).

If you check the PR, you will notice this recent notation:

<quote>
This bug is not fixed in 12.1-STABLE as of April 26 (r360337)
</quote>

Since the error presents itself immediately upon bootup with a fresh
12.x disk, it is highly unlikely a configuration error. I have even
reformatted the HD via the manufacturers disk and returned the BIOS to
factory defaults, and the problem still exists. It appears to be some
sort of 'regression' error, according to the notes posted pertaining to
the PR.

BTW, you use the term, "shiny", I prefer more advanced or mature, but
that is not the important point here. Anchoring yourself to the past
and or refusing to move forward is what dooms most projects. They reach
a level to which they are either unable or unwilling to advance from. I
guess its a good thing Thomas Edison thought reading by candle light
was not the optimum solution.

-- 
Jerry



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20200618071456.00004fdd>