When I now turn on my computer, it will disconnect from the wifi after about a minute or two and then there will be no networks available after that. It seems like something is turning my wifi off but I don’t know what.
And now, I just rebooted it and now it just says “device not ready”. Maybe I changed something trying to fix it.
Some commands:
ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether ba:90:74:5a:14:88 brd ff:ff:ff:ff:ff:ff permaddr e0:0a:f6:84:86:e5
rfkill list all
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
2: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
lspci -k | grep Net -A 3
01:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852
Subsystem: Lenovo Device 4853
Kernel driver in use: rtw89_8852be
Kernel modules: rtw89_8852be, rtw_8852be
Apologies for being clueless but I haven’t found others with a similar issue.
Try a driver package from the AUR.
yay -S rtw89-dkms-git
The kernel driver has probably been broken for a while.
This is probably because the Blutooth of this chip again requires its own driver.
If this does not work you can remove the driver again with
yay -Rs rtw89-dkms-git
Source:https://bbs.archlinux.org/viewtopic.php?id=281839
I tried installing that driver and it doesn’t seem to work and it says “No network connection” now. Also when I run ip link the wlan0 block doesn’t show up anymore. Removing the driver gives for ip link:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
link/ether 72:d6:d3:ba:ec:db brd ff:ff:ff:ff:ff:ff permaddr e0:0a:f6:84:86:e5
where DEFAULT has changed to DORMANT. I don’t know if that’s relevant though.
Can you post the following.
inxi -Na
Have you rebooted?
What results
sudo modprobe 8852be
The rtw89-dkms-git should work. Check as @HPF-84E has posted above.
Running sudo modprobe 8852be gives:
modprobe: FATAL: Module 8852be not found in directory /lib/modules/6.3.1-arch2-1
regardless of if the driver is installed or not, before and after rebooting.
Do you have bluetooth also?
Yes, that works fine afaik.
It must not be on the same chip?
Can i see the hardware output? Post the url.
inxi -Faz | eos-sendlog
Here’s the link: https://0x0.st/HNQp.txt
I’m using a USB tether with my phone right now, that’s why that shows up.
Nice laptop btw. There is a newer UEFI Bios update for this laptop that you can do in Windows if you are dual booting. Not sure this will fix the issue with the WiFi on EndeavourOS though. I see the bluetooth isn’t on the same chip.
Edit: Is this bluetooth output from your phone?
There is another package that has bluetooth also for the rtl8852be if bluetooth is on the same wifi chip.
rtw89bt-dkms-git
heh thanks, I’m not dual booting, it’s only EndeavourOS.
I’m not entirely sure what you mean. If I disconnect my phone and run inxi -Faz, it just shows
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.81 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-3:3 chip-ID: 0bda:4853
class-ID: e001 serial:
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
for the bluetooth section.
Well it must not be on the same chip then and if it is working?
The rtw89bt-dkms-git driver didn’t work so I uninstalled it and rebooted. But now it seems to have somehow fixed itself. It’s been connected to wifi for a few minutes now. And rtw89-dkms-git is also not installed. I have no clue what happened or if this is just gonna break in an hour or not.
(And rfkill list shows the same output as I pasted in my initial post)
I was just going to say the this chip is supported by the kernel module since 6.2. So you shouldn’t need the AUR packages. Somehow you kicked it into working probably by running the modprobe and then after uninstalling the package it started working.