Why the secure boot blocked the wifi drivers

Solution 1:

The problem with open source drivers is that not all of them are "signed" drivers. "Signed" drivers are drivers which have been signed with a digital identity code signing certificate to indicate the legitimacy of the developers.

Many open source drivers don't have this digital signature (it's not the easiest thing in the world to get a code signing certificate, and it's not really that cheap - $170/year and it requires you to provide detailed documentation that you as a business entity are real and can be considered a business or organization under the law), and as a result SecureBoot can't properly permit them, because they're not 'signed' and 'secured' drivers.

In those cases, you have to disable SecureBoot. In Windows, most drivers are signed, except for open source ones which you install separately, which aren't always signed.

Regardless of the OS, SecureBoot requires signed drivers. It's just an extra layer of security, so unless you're installing suspicious drivers and such all the time, it's up to you whether you keep SecureBoot on or off, and if hardware you're using isn't signed and you need the hardware because it's critical, then you've got no choice but to disable SecureBoot, or sign the drivers yourself (which for various reasons might not be doable).

Having to disable SecureBoot for Linux installs and drivers is also not uncommon, either, as this is and was a common occurrence ever since SecureBoot was initially introduced.