RTL8822be - Issues with Realtek Wifi

Issues & Assistance Networking Support
41

Could disabling the wifi adapter in Windows' device manager help?

42

I guess that's a possibility.

I think a kernel boot parameter is your best bet at this point,

You can test these grub kernel boot parameters to hopefully change your power state at boot:

pcie_aspm=off

pcie_aspm.policy=powersave

pcie_aspm.policy=performance
2 Likes
43

I'll try them all out and let you know what happened. Thanks for being so willing to help, by the way.

1 Like
44

I also think the driver configuration file is a good route.

/etc/modprobe.d/50-rtw_pci.conf

Add:

options rtw_pci disable_aspm=y

The key is changing your power states I'd say.

You're very welcome.

2 Likes
45

I think I've already done that. This is what the file looks like:

 ā•­ā”€gauravchandan@gauravchandan in ~ 
 ā•°ā”€Ī» cat /etc/modprobe.d/50-rtw_pci.conf

File: /etc/modprobe.d/50-rtw_pci.conf
options rtw_pci disable_aspm=y disable_msi=y
46

Yes I know, but with all the changes and a reinstall I thought it was worth trying again. I feel changing your power state settings is the key to this.

2 Likes
47

As the modules you are currently using are included in the kernel, a kernel change may also be worth testing. I would recommend testing the newest developmental kernels in this order:

linux
linux-mainline
linux-next-git

Likewise, it might be worth testing the newest firmware package (although I didn't check to see if revisions to your specific firmware are included). Just looking for the newest possible fixes available.

Considering your bios was updated in May I assumed it was current. However, you may want to double check if there has been a newer bios version released just in case.

3 Likes
48

sorry fell asleep here it was late,
This is really bizarre, that the live usb doesnt work
You could try turning wireless of in the bios completly and bluetooth, then run windows so that drivers are not loaded, then run garuda with it of ,
Check fastboot is still of in bios,
reenable wireless in bios and boot live usb garuda first?

1 Like
49

I just tried this. However, neither wifi nor bluetooth showed up when I booted into the live usb after re-enabling wireless in bios. But now that I rebooted into the installation, the wifi is working. So it seems as though booting into the live usb or windows before booting into the installation makes the wifi work.

50

Um weird !

ok last thing i can suggest is download different iso ,say dragonize kde and test live

2 Likes
51

This is a fairly rare occurrence but I have dealt with these cases before. That was why I knew a live boot disk or Windows can revive the connection. Removing all power sources is also a good method to reset. A bios reset is sometimes required to revive the connectionā€¦ Usually disabling MAC randomization and turning off all power saving options is sufficient.

You should not have MAC filtering enabled in your router and wifi power saving needs to be disabled.

You did disable wifi power saving as I instructed many posts back right?

While your testing kernels give the LTS kernel a go as well.

4 Likes
52

Yeah Iā€™ve done that.

53

Try adding options rtw88_pci disable_aspm=1 to /etc/modprobe.d/rtw88_pci.conf then reboot.

Also try adding options ideapad_laptop override_has_hw_rfkill_switch=0 to /etc/modprobe.d/ideapad_laptop.conf and reboot.

There is a kernel quirks list for Lenovo laptops with these wifi issues. I guess yours might be too new to be included (unless you test developmental kernels).

I'm about out of ideas now.

Edit:

One more Hail Mary, try blacklisting btusb. This will temporarily disable bluetooth. Remove the blacklist if no improvement. This is only a troubleshooting test.

1 Like
54

After I turned off wireless lan in the bios, booted into windows and then booted back into Garuda, I got the internet working, as I mentioned in one of my previous posts. So after that I turned the computer off waited for 2 hours and now that I've turned my computer on the wifi is still working. Booting windows with wireless turned off to ensure that it doesn't load the drivers, might be the fix that I'm in need of. But I'm not jumping to any conclusions till I turn the computer off for the night and then fire it back up in the morning to check.

Also, would you guys say that disabling the device under Windows' device management will have the same effect, as in that it wouldn't load the drivers when I booted into it? 'Cos then I could just disable the inbuilt wireless card in windows, and just use the external adapter whenever I use Windows (which I do very rarely, so it won't be much of a bother).

55

If you do that I would uninstall the Windows drivers completely. Worth a try. Watch out for Windows update re-enabling fastboot.

Did you try this^^^

2 Likes
56

I havenā€™t tried this yet because it seems to be fixed at the moment. Iā€™ll try disabling the device in Windows now, and if that doesnā€™t work, then Iā€™ll try this out.

57

I would reset your bios to default and then disable and enable what is needed!
Then i would try the live usb for wireless connection that should be working ?
As you installed garuda with fast boot enabled i would think about a reinstall as fast boot can really mess up a install, and give you lots of little gremlins to fix,
As you disabled wireless in the bios and rebooted windows no driver was installed, so when you reboot with windows it will reinstall drivers and hopefully not try to take over the world :smiley:

58

The wifi has died again after I went into windows to disable the devices there.

So now that I have fastboot and secure boot disabled, Iā€™m gonna try a clean reinstall of the OS as suggested by @TilliDie and see if it helps. If it doesnā€™t, Iā€™ll edit all those conf files and try different kernel boot parameters as suggested by @tbg. Iā€™ll also install and try the various developmental kernels this time. Iā€™ll try disabling btusb in the reinstalled OS if the wifi still doesnā€™t work.

And could you maybe send me a link to this?

Thank you!

1 Like
59

Sorry I read so many links I can't seem to locate the bug report ATM.

Best of luck.

1 Like
60

Ok ive done abit of digging as this was bugging me as to why it would work after you first boot another op system. it would seem that the lenovo bios is to blame. its geared for windows.
Can you enable PXE boot to LAN in bios then set it to the first device to boot then garuda!
If not set network boot to boot first, then garuda.
This should wake the wifi for garuda to grab and own it when it boots

Edit: update your bios if it has a bios update