you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 months ago* (last edited 2 months ago)

There's way too much info here to parse.

Can we get the output of:
lspci | grep Network && lsusb | grep Bluetooth && rfkill
This is the first step to diagnosing issues with your wireless radios such as wifi and bluetooth. This command (you can copy and paste it into a terminal, this command is totally safe, but normally you shouldn't copy commands you don't understand) will probe your PCI devices and USB devices to find anything matching the words "Network", "Wireless", or "Bluetooth", then it will run the "rfkill" command, which will tell us if these devices are "blocked" or "unblocked". If they are "blocked", you will need to "unblock" them.

To "unblock" your devices, using the number under "ID" as reported by the rfkill command instead of %ID%, run the following (this one cannot be copy-pasted, you must type it manually to ensure the correct command is entered):
sudo rfkill unblock %ID%

If this doesn't help:
You may have updated everything except your 'linux-headers'. Headers are special files that teach the kernel how to talk to userspace programs. Sometimes they're important for your drivers to work correctly. It would be worth running dpkg --list | grep linux-headers and seeing that you have an option that matches with the version supplied by uname -r. If you lack a matching header, manually install it via the apt package manager from the command line. It is as simple as sudo apt install linux-headers

Also, forgive my intrusion on your personal choices, but I would strongly recommend using Chromium or Ungoogled-Chromium unless you have a use-case for real full-fat Google Chrome. Google Chrome is an egregious piece of malware under the definition supplied by the Free Software Foundation.

Edit: Corrected first command, was too verbose and caused issues on my system, I was trying to solve every edge case at once and that was silly.

  • source