make install requires elevated privileges, while make normally does not, which casts doubt on whatever AI generated the above instructions. You should not be adding 3rd party drivers to the kernel tree. They normally go to /lib/modules/6.11.5-300.fc41.x86_64/extras/.
Hardware that requires out-of-kernel modules should be avoided – they tend to break with kernel upgrades and fixes can take time (if ever) to arrive. USB WiFi adapters are not expensive so most people can afford to buy one that has in-kernel support and is well-constructed.
There are tools that will automate building out-of-kernel modules for each new kernel.
Just to minimize confusion (particularly for those who are not native English speakers), the Nvidia drivers are used by the kernel, but don’t directly alter it. Some readers may interpret “touch” as actually changing something in the kernel. Problems may occur when the rules for interacting with the kernel change. Some 3rd parties only discover changes when their driver stops working. When you use 3rd party drivers, you will see messages that use the word “taint”. Used as a verb, “taint” means: "To affect or associate with something undesirable or reprehensible. "
My elderly iMac needs a 3rd party WiFi driver, so I see:
% journalctl --no-hostname -b -g taint
Nov 02 11:32:22 systemd[1]: System is tainted: unmerged-bin
Nov 02 11:32:25 kernel: wl: loading out-of-tree module taints kernel.
Nov 02 11:32:25 kernel: wl: module license 'MIXED/Proprietary' taints kernel.
Nov 02 11:32:25 kernel: Disabling lock debugging due to kernel taint
Nov 02 11:32:25 kernel: wl: module verification failed: signature and/or required key missing - tainting kernel
Nov 02 11:32:25 kernel: wl: module license taints kernel.
Nov 02 11:32:25 kernel: CPU: 2 UID: 0 PID: 673 Comm: (udev-worker) Tainted: P OE 6.11.5-300.fc41.x86_64 #1
Nov 02 11:32:25 kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
I understand the limitations and risks of these alterations, but my level of knowledge does not understand what to do if they happen, so I avoid interfering with the kernel.
in the past I tried to do these same steps with debian and arch but finally with the kernel update, the driver stopped working and this peripheral is not working anymore.
What can be some good sources of information about verified laptops and peripherals in linux distributions to help people not as advanced as me to use all the components?
Kernel driver modules need to be rebuilt with each new kernel. There are ways to automate rebuilds using akmods or dkms, but those depend on the vendor or some user updating the source when changes to the kernel conflict with the existing version of the driver. Most of us have better things to do with our time.
Thanks George, may you suggest go with compatible devices or make changes every kernel update? its the only peripheral don´t work for me, but the internal NIC in 2.4 Ghz work well.