It just happened now, like I said it seems to happen randomly, sometimes the bluetooth works for a while and then crashes, sometimes it crashes when I try to search for the device I want to connect to. Feel free to ask me for any additional information about this issue now, while I still have the logs.
The rtl8821 ce should be supported by the kernel module r8169. You may need to remove the r8168 package so that r8169 is loading on boot. If it doesn’t work on that module then the rtw88-dkms-git is what you will have to use.
I did not uninstall r8168 but I blacklisted the r8168 module so it would not load, then I tried to lsmod | grep r81 and I get not result so I guess the r8169 driver does not load(I am able to load it using sudo modprobe r8169), the bluetooth seems to work though(even without the r8169 module loaded). I will see if it fails randomly again and come back, but at the moment this seems to be the solution.
If you have installed and are using rtw88-dkms-git. Try the following and create a file named /etc/modprobe.d/rtl8821ce.conf
sudo nano /etc/modprobe.d/rtl8821ce.conf
add
blacklist rtw88_8821ce
ctrl + o then enter to save the file
ctrl + x to exit nano
reboot.
This will blacklist the default Realtek driver module that is included in the kernel which should enable the out of kernel rtw88-dkms-git driver to work for you.
Edit: Hopefully this isn’t blocking the r8169 module that runs the Ethernet?
Edit2: I have also seen this kernel parameter used in the default grub command line and update grub.
I already had this, but I added the blacklist into blacklist.conf. The driver from rtw88-dkms-git is already loaded.
It is not blocking the r8169 driver(I do not get why it would, they are 2 different drivers).
Will add this.
Edit: Borked my install(I even managed to bork my timeshift backup kekw) while trying to fix no sound after recent update(I saw a post about it, seems like sound works on a fresh install), I reinstalled and will see if the issue still persists.
Can you elaborate? Do you ask me if the pci=noaer caused the sound malfunction? Because I really do not know, but I doubt it was from that as I saw a post of someone else blaming it on a recent update(And I digged a little bit and it seems that updating some alsa packages from 1.2.2 to 1.2.4 borked it, or something similar I might not recall correctly).