What happens if you delete the ` from the end of
GRUB_DISTRIBUTOR="Xubuntu26March"`
Type: Posts; User: jeremy31; Keyword(s):
What happens if you delete the ` from the end of
GRUB_DISTRIBUTOR="Xubuntu26March"`
See the wireless script link in my signature and post results
Try
sudo depmod -a
Then reboot
So what is happening when you try to compile the modules from the source code on github?
Unplug the wifi, open terminal and run
sudo dmesg -w
Plug in the wifi wait 20 seconds, then paste terminal output here along with result for
modprobe -c | grep -i c811
The internal may...
Do a
cat wireless-info.txt|nc termbin.com 9999
Paste URL from terminal
See the wireless script link in my signature and post results
Try https://github.com/morrownr/8821cu-20210916
You may have to edit the Makefile in the source to allow the driver to build for raspi
What result from terminal for
dpkg --print-architecture
Check the power settings and see if automatic brightness control is on
You could try resetting the BIOS to defaults and see if the results for lsusb change
What shows in results from terminal for
lsusb
I remember issues trying to find wifi/BT combos that would work in my old Toshibas, likely made 14 years ago
Post results from terminal for
lspci -nnk | grep -iA3 net; lsusb; sudo dmesg|egrep -i 'blue|firm'
Try
sudo apt remove rtl8812au-dkms
sudo apt install git dkms
git clone https://github.com/lwfinger/rtl8852au.git
sudo dkms add ./rtl8852au
sudo dkms install rtl8852au -v 1.15.0.1
Reboot
Please see the wireless script link in my signature and post results
See the wireless script link in my signature and post results
Post results from terminal for
lsusb; sudo dmesg | egrep -i 'blue|firm'
You may just have to do
bluetoothctl
power on
scan on
exit
Can you post results from terminal for
lsusb
I may be able to help if I see results from the command I posted. I would guess the wifi used iwlwifi-so-a0-gf-a0-64.ucode as that does exist. The iwlwifi module looks for the newest firmware...
That file was likely deleted because of a bug and it has nothing to do with Bluetooth
Post results from terminal for
sudo dmesg |egrep -i 'blue|firm'
I uploaded the report to https://paste.ubuntu.com/p/PmcNZNQ4RD/ from the other site
Sounds like what the Windows hybrid shutdown does to a drive
The usual fix is to boot into Windows, disable the hybrud shutdown/fast startup and then boot into Ubuntu
the only thing i can think of is to open termina and run
xev
Drag the event tester terminal box to that area and see if any errors show in the main terminal window when you click in the event...