Must be as easy as windows, but in windows the easy way to fix a big problem is install again, un linux you can reinstall or... Fix with commands. Probably in your case you need to write commands because something go wrong with the installation, maybe you did something wrong, or maybe Ubuntu read something in a bad way and make a mistake installing Ubuntu. Is impossible to know if you don't share the exact error message.

Maybe depends for the configs, in my case I need to build the external modules with the same compiler, and in lkml you can see a few warnings about do not mix the compiles: https://lkml.iu.edu/hypermail/linux/kernel/2107.3/08102.html

For rust modules you need to use LVM=1 because you need to use all the LVM stack instead of the GCC stack, if I define in the Makefike the LVM=1 then the build fails with a lot of clang: error: unknown argument: ...

So for me is impossible to build my rust modules for a kernel build with a GCC kernel

The C and C++ compilers use the same backends (and rust to, llvm), just try to build a module with clang for a kernel build with GCC, or it fails in compile phase or when you try to load the module. You can write a module in the lenguaje that you want if you use the same backend, but if we are talking about avoiding to use a kernel with rust, man is the default in the kernel, just read the config, rust is disabled

You can't load modules built with a different compiler. The modules aren't external programs, the modules are literally part of the kernel. And if you want to use a module wrote in rust you also need to have built in the rust support in the kernel

The default is GCC, and you need to build the kernel with clang to build the kernel with the rust support, how is possible rust arrives by default? https://docs.kernel.org/rust/quick-start.html

Maybe is the default in your distribution, but is not the default in the kernel

Is very easy to build the kernel without rust, and is the default scenario

UKIs are good for secureboot/measureboot, because you can sign the uki, and everything inside of it be validated for secureboot. If you really like to have a secure chain without a uki, you need to validate all the boot components. You can do it with grub and gpg signatures, but is more simple to use an uki and a efi bootloader like systemd-boot

Yea this is what I was saying whan I talked about the risc-v ecosistem isn't competitive (at the moment). For me the bests boards at the moment are the based in the spacemmit k1, supports the majority of the rv23 profile extensions (not everything, and for this reason not will be compatible with the new versions for Ubuntu), and full rv22, including rvv 1.0. I have an orange pi rv2 (they use a renamed k1 for some weird reason), and works very well... For 50$, not for more

This boards haven't got the rv23 necessary extensions, and aren't competitive, they are expensive for their performance. There only one attractive is the risc-v cpu for learning, etc

I think this can be a good idea in... 5 years maybe? It will only works on qemu, witch board suppose to have this things? I only know one board with all of thins things in ARM, risc-v is too young. I can't imagine a competitive risc-v board at the moment