Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Mar 2021 11:34:03 -0400
From:      Jerry <jerry@seibercom.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: OS to replace FreeBSD
Message-ID:  <20210321113403.00004056@seibercom.net>
In-Reply-To: <38EDD406-3EC4-4F71-B990-DDD1E753D091@kreme.com>
References:  <20210320132339.00004d9a@seibercom.net> <38EDD406-3EC4-4F71-B990-DDD1E753D091@kreme.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
--Sig_/pMJuUhaJJ2wwzFpA0EQ+o8E
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, 21 Mar 2021 07:26:09 -0600, LuKreme stated:
>On Mar 20, 2021, at 11:24, Jerry <jerry@seibercom.net> wrote:
>> Can you provide verifiable proof of that statement relating to the
>> know defect in the USB controller? =20
>
>I read the big thread. There is a post there about the controller
>returning an out of bounds or invalid ID. That would be a problem,
>with the controller.
>
>Dell is a company that largely deals with Windows. I=E2=80=99m sure Windows
>does not care one whit about invalid USB controllers that maybe
>hijacking your hardware, and neither does Dell because 99% of their
>customers are using windows.
>
>But here=E2=80=99s the thing.
>
>YOU have a problem. You have been given two suggestions on how to
>mitigate your problem, and your response is =E2=80=9CI don=E2=80=99t WANNA=
!=E2=80=9D Which is
>fine, but then you repeatedly complain about how your problems is not
>solved. It=E2=80=99s no ones job to solve your problem. This is not a comm=
on
>problem. This is an edge case. Sucks, but that=E2=80=99s the way it is.
>
>If you want to use Linux, fine, this is NOT the place to ask for
>suggestions on what Linux to switch to, because this is not a Linux
>list, and you asking that here comes across as you simply bring a
>shit-stirrer.
>
>If you think compiling a kernel is too hard and you can=E2=80=99t figure o=
ut
>how/refuse to disable the errant usb in your UEFI, then yes, switching
>OS is another, possible, solution for you. I would not be at all
>surprised to find you have problems on current Linux.
>
>I would buy a USB3 card ($20?) with a different controller, put that
>in, and disable the onboard USB-3, but that=E2=80=99s me.

I agree that replacing the controller might be an option. The BIOS
gives me the option of disabling the front, rear or both sets of USB
ports. The ones in front are all USB3 but there are two USB2 ports and
four USB3 + one USB3-c port on the rear. And at least USB2 has to be
active for mouse and keyboard.

I have Googled extensively on this problem over the past year. All of
the information that I have accumulated infers that FreeBSD has
somewhat poor support for USB3. With that aside, I can find NO
documentation that shows the controller has a bug. In fact, just the
opposite. Everything I can find that relates to this problem says that
FreeBSD is the one with the BUG. Remember, versions <=3D 11.x worked fine
with this setup. Well, I never tested <=3D 9, so I cannot say for sure.
They are long ago EOL'd anyway. Furthermore, I have requested from at
least one user who stated that the card was the problem to send or
direct me to some verifiable proof of that statement. If I had such
documentation, I would attempt to shove it up Dell's ass.

Replacing the controller is an option I suppose. It is rather ass
backwards though. I have always believed in buying the product or
products I want and then finding an OS or software that supports them.

In addition, if you read the entire bug report
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237666>; you will
immediately notice that it is not just a Dell problem. Read comments 7,
15 and 17 for starters. Better yet, read the entire PR -- 169 comments.
Not a single one accuses the controller of being the problem. In fact,
no one seems to know exactly what the problem is, except that it
stated in versions =3D> 12.x. That, in itself, is mighty suspicious.

What really infuriates me is that FreeBSD will not at least post a
warning on their site of the problem. Something like this:

FreeBSD had been notified that the following systems are not compatible
with versions >=3D 12.x [List of units not compatible]. We have no idea
what the problem is and we are not going to invest in the time to
figure it out, and if it is our problem, correct it.

Now that I could live with.

--=20
Jerry




--Sig_/pMJuUhaJJ2wwzFpA0EQ+o8E
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQGzBAEBCAAdFiEELeCiu2K+9VmEYYgTgHBP8gv9FXcFAmBXZ3IACgkQgHBP8gv9
FXf1CAv/T4RwhuanyOiR9LuwRUZU5NiJ6oLoh6nfwFBf9FzMOXyJaIHy/3pIE8Wx
tyJEV6/HrGXSOIsTDYPkPeqairEyEZiKJuqDSzc4g8/LoUDy1IxNfdcmsTiIB6qL
UOd7PlJhW/bezBslPtGhB+nCM2DYKpu5SQTJp7mFxPQ0U848OQT7hy9mhIQ8iSmt
firdwEWTwPi/JrtNeKILuhPusKSd6p7llnwV+Y6B+UDw8YxpfyrK/wIg/zLxTszW
XkwZodxb1CGoheHfgtFPdqukNWfhup7GL4R+mzjaDMSWkMk3TIK7Ygav+4vb+xx/
xirSDCeD/Ixm+yLcgGISyDl22vc4PuefksEPYarNMd/2lZ5u/StZLySVCyhms8VO
IWZSC3xFSTP7cmsYhgRpAXx+mAXtmhOfGv+9FtIsmhT1lQ3hyxHyoBIjQngGSVIz
VpLV1uP4amb6PIeFSu7B3fGZLMTzen0IdYO51//bxQxhAOH/he1aAiwHAdL6/mTY
ciNaocFI
=WiZH
-----END PGP SIGNATURE-----

--Sig_/pMJuUhaJJ2wwzFpA0EQ+o8E--



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