Bitterblue
Bitterblue
You have to decide which driver you want to use. 1. The one in this repository is called „8821ce” 2. The one from lwfinger/rtw88 is called „rtw_8821ce” 3. The one...
Maybe 8821ce doesn't recognise your card. What does ``lspci -nn`` say?
Nevermind, it knows all the device IDs which rtw_8821ce knows.
Anyway, you have to blacklist two of the three drivers, so that only one can load. Otherwise you never know which driver will be in charge.
As a test: ``` rmmod rtw_8821ce rmmod 8821ce modprobe 8821ce ``` Do you have wifi now?
Did ``modprobe 8821ce`` run without errors?
Okay. So the driver from this repository is not working for you. You have some options: * Ask Larry Finger to update [the newer version](https://github.com/lwfinger/rtw88/tree/master/alt_rtl8821ce) of this driver so it...
@SisyphusIsntHappy That's right. The driver is calculating the signal strength the same way for all the chips it supports, but that way is only correct for RTL8723AU and RTL8192CU families....
I finally fixed it! https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/commit/?id=e1dfa21427baeb813f9a2f9ceab6b7d32c3ca425 The fix is in the older stable kernels too.
LoadPlugin works the same way everywhere. Obviously in OS X you will load ffms2.dylib (or libffms2.dylib?), not ffms2.dll, and absolute paths won't start with a drive letter. Paths relative to...