OS to replace FreeBSD

Tomasz CEDRO tomek at cedro.info
Sat Mar 20 13:20:48 UTC 2021

On Sat, Mar 20, 2021, 11:35 Jerry <jerry at seibercom.net> wrote:

> I never said I could not compile a new kernel, I said I could not
> install the OS. Correct me if I am wrong, but doesn't the installation
> of the OS precede the creation of a new kernel? Furthermore, the
> screen just rolls away filling up with the error message ad infinitum.
> By the way, as I understand it, creating a custom kernel nullifies the
> use of "freebsd update". Wow, things just keep getting better & better.
> What I cannot understand is that FreeBSD knows it has a problem, one
> not shared by any other OS as far as I have been able to ascertain,
> and I have done a lot of research, and they refuse to fix it. The
> problem did not exist before version 12.x, so it is not like they never
> were able to get it right.
> --
> Jerry

Hey Jerry :-)

Please just rebuild and install new kernel, at least to see if that fixes
your problem :-)

This is a standard procedure when you find a problem, it seems identified,
workaround seems available, a least try if that works for you :-)

I also use custom compliled kernel to get my Touchpad working on a
non-standard configuration. Until fix is ready and does not break
configuration for others I need to work that way because this is a problem
with _my_setup_. It seems that your problem seems similar.

Look on the other hand you are helping others not to have this problem in
future.. developers are going through this way everyday and we usually have
broken or incomplete setup just to help others not to have such problems.
With new hardware showing up faster and faster, using their own standards,
or enforcing linux like solutions thing are and will get even worse. This
is not really the issue with FreeBSD, it only gets impacted by this
"bleeding edge" approach around :-)

Because of drivers I have chosen Linux over FreeBSD around 1999 on my first
desktop PC. Then when Linux kernel api started changing with every minor
release, and when the stable USB stack was created by HPS, I have abandoned
Linux for good and FreeBSD is my ultimate OS of the choice. I even prefer
FreeBSD over OSX/macOS. The problem of quickly changing things and breaking
compatibility is the Linux by design. You will find many more problems like
this over there. We are experiencing this kind of issues here because world
has changed that way unfortunately.

I can see three effective solutions here:
1. Use Alt+F2 to switch away from terminal flood and recompile your kernel.
2. Maybe XHCI/USB3.0 controller can/could be disabled at runtime in
bootloader so it wont be active and the workaround can be ready with no
kernel recompile.
3. Provide a hardware and development fee for a person that is willing to
fix the problem for you. This will cost time and money but there is a
chance that you will get the fix one day just using freebsd-update :-)

Free Softwate is free to use, but is really cost developers life time and
all other technical resources and experiences. Just imagine how many
problems of this kind developers have everyday. Most of them work for free
in their free time, but they also need to pay the bills.

Best regards :-)

CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

More information about the freebsd-questions mailing list