Installed ndiswrapper versions 1.57 (from repositories, with dkms) and 1.58rc1 (compiled from source from ndiswrapper's website). Both failed: version 1.57 does not provide an interface for the functions IoWMIOpenBlock and IoWMIQueryAllData. 1.58rc1 has dummy functions in their places, but it fails with a "ioremap failed" message.
Upon further investigation, I have found that the function NdisMMapIOSpace (ndis.c:808), in 1.58rc1, gets called with physical address and length zero, which causes the failure. Since this function doesn't seem to be called from anywhere in ndiswrapper's code, I'd assume the Windows driver is somehow calling it with bogus parameters.
I tried using both the 64-bit version (on my installed system, which uses the x86_64 version of Ubuntu) and the 32-bit version (on a live-USB x86 system with persistence enabled) of the Windows XP driver. The same errors occurred for both versions.
Support for the RTL8273AE-BT has been added by Realtek in the 92-series driver, version 0006.0514.2012. For unknown reasons, neither the Windows nor Linux drivers are available on their website (yet). But Realtek tech support has been providing a Dropbox link with the source code/firmware tarball which numerous users have reported as working.
Commenting out/removing the IEEE80211_HW_BEACON_FILTER (line 320 in base.c) makes it possible to compile when using the 3.4 kernel. So far I haven't experienced any problems. The card seems to work as it did before, although it might be less power-efficient. I can't guarantee it won't cause any problems, but it's better than nothing.
Well, then here's some new feedback for ya: I did all of the above and got the same compile error and fixed it with your suggestion. Then the driver worked ONCE. After rebooting, no longer it could open any wireless connections.Tried booting into windows 7 and still, no longer it can detect any wireless connections.
I am now convinced this procedure has bricked my wlan adapter - windows still recognizes the device but there is some problem because it no longer senses any wireless connections. I have to use an external linksys adapter because my onboard realtek is gone :/
UPDATE: I found out that somehow that driver has set my WLAN module's 'Roaming Sensitivity' setting to 'Low', which was causing it to not be able to detect any wireless signal whatsoever. In Windows 7, I went to device manager and changed that setting to 'High' and voil - it went back alive!phew...
I talked with a support guy from Realtek and received the very same files hosted on Dropbox submitted by another user on this question. I compiled the drivers as the readme instructed and it worked, you might need to copy the 8723* firmware files into the rtlwifi folder.
The 3.4 kernel have removed some calls in the mac80211 module that this driver needs to compile and thus exits with an error and can not compile. This is not an issue for ubuntu right now, but it means you can't install the driver on a up-to-date Fedora 17 or any other distro using the 3.4+ kernel - including upcoming versions of Ubuntu.
To anyone browsing this thread with the same problem, I'd say the best solution is to wait for Realtek to release the official driver for 8723 on its website. They usually do that, and it's symptomatic that not even the Windows drivers are available on the official website (I guess this indicates this is a fairly new chipset).
For some reason the install script didn't copy the firmware correctly, so I had to do it manually. I moved rtl8723fw.bin and rtl8723fw_B.bin from the rtlwifi folder in the source directory to /lib/firmware/rtlwifi/, rebooted and it worked.
realtek often only does very few codes dump with questionable maintainability. Then it is on the community and maybe the card manufacturers to update the driver. Since there is now an alternative driver in the kernel which in theory is better structured there is not much incentive to keep the rotting drivers going.
I had to make this post to help anyone else who might be having issues with this network adapter and possibly other network adapters which work with the realtek 8814au 8812au chipsets. I'm on ubuntu 20.04 with kernel 5.4.0-28-generic, and I own a netgear a7000 wireless adapter that works fine with windows but wouldnt function with my linux dual boot.
I recently discovered that only when I enable Wi-Fi, htop shows an abnormal CPU usage of more than 90% for /usr/lib/systemd/systemd-journald, which then leads to a bunch of problems.
I guess it's logging multiple errors in the background, maybe the PCIe Bus Error?
Anyways, I then disabled Wi-Fi & enabled Airplane mode. When I restarted my laptop, I was bombarded with multiple PCIe Bus Error for three seconds on the screen, then proceeds to restart.
After restarting my laptop & booted on my desktop (Wi-Fi is still disabled & Airplane mode enabled), I checked htop and the CPU usage this time was normal or mostly at 0.7% - 2%.
I restarted one more time and there were no PCIe Bus Error if Wi-Fi is disabled. Restarting was smooth & normal.
There is indeed something wrong with the Wi-Fi, specifically the Wi-Fi driver.
By the way, this issue doesn't occur on a Wired connection or when I use USB tethering from phone to laptop. The Wi-Fi driver in question and responsible for this headache is the RTL8821AE.
I searched on Google & the Garuda forum for similar or related issues for the rtl8821ae driver and I found some. Although I haven't attempted any of the fixes yet because I want to verify here first with you, the experts, for my particular case and because I don't know what I'm doing. I still need help.
#newbie
I just wanted to tell you, you did a very well post for your issue in the forum which (sadly) rarely appears. I'm sure there will be someone with deep insight into the issue who will help you out.
We've some great ppl here.
Perhaps stupid question : shouldn't it be rtl8821ae instead of rtl8723ae in those command sequences?
Furthermore, I think the system should be monitored after each of the 3 commands (3 different tests). Maybe this was done. Just in case, for clarity...
My bad, it was very late in the morning when I posted those commands and I got my wires crossed on the adapter driver in use. I will edit the commands to make sure they are what the user needs to run for their adapter.
Actually, I did them twice in a row, from first to the third command and repeat again to notice some changes.
CPU usage stays 50% & above with the three commands, the second attempt may have lowered the CPU usage of some commands that were higher on the first attempt so I wouldn't base any changes with just the random +/-30% up & down changes.
Hello, everyone !
After many a search, I finally decided to ask for help in a more personalized manner : trust me, I've tried a lot of stuff, also what's said in the wiki, and it made no difference.
I installed Arch about 1-2 months ago and since then the wifi connection worked on-and-off : most of the time it works for 5-15 minutes and then stops until I hard-reboot the machine ("reboot" doesn't help; only "poweroff" does..). Sometimes I doesn't work at all for a few days.
I've been dealing with this thanks to my trusty phone and usb-tethering, all the while reocurringly searching for a solution. I found a nice script that should grab everything you'd need for this kind of thread, "wireless-info" ( -info) which, though designed for ubuntu, still should be of help here.
I have seen this thread, but I haven't tried out its contents since installing connman, so here goes.
According to the thread, the ant_sel option is now available in the default driver, so I did not install anything else. I have tried all option sets, namely:
Edit: repo mentioned above no longer exists. This seems to be the current repository: GitHub - lwfinger/rtw88: A backport of the Realtek Wifi 5 drivers from the wireless-next repo. (please check lwfinger GitHub for other realtek hardware too)
First, check if we have the driver loaded. Is there a folder called rtw_pci in /sys/bus/pci/drivers/? Or any other rtl folder?
If so, you will see that in this folder is a file, called new_id. If we write vendor ID and product ID to the file, the device should be dynamically paired.
So in your case, and given that the driver rtl_pci is there, the following command might make it work. But again, be warned: this might also break your system. So if in doubt maybe a better way would be to fill an issue with the lwfinger github repo an check if they can help.
Hey Ji m,
thanks, this looks like a very good walk-through. Unfortunately, on my new HP with RTL8821CE wifi adapter, this has not yet done the trick. Still no wifi adapter found under ubuntu 18.04 (works fine under windows).
1. I used modprobe on the rtl8821ae module (number matches my card, but ae instead of ce, no idea if that is a problem?)
2. I noticed that no rtl8821ae.conf has been created in my /etc/modprobe.d/ directory.
Do you have a suggestion what I could try? Thanks a lot!
hello lutz , i am using 18.04 and hp 15 pavilion cw0096nb , this wifi adapter rtl8821ce was also not working !, intill i went to the updatemanager in ubuntu, the A in the black round background app,i have download about 500 mb, it went to a higher kernel and other updates ,,REBOOT your computer , then i have used all the commands in a terminal as here discribed above .:::How to Install RTL8723DE Wifi Driver in Ubuntu 19.04
None-the-less, I went to the website mentioned in the second command ( ), downloaded the .zip file to a pen drive,
and unzipped the contents to a rtl18821ce folder on the desktop of my Ubuntu machine. Followed the rest of the instructions (which worked as advertised)
and did a cold restart; my Ubuntu WiFi is now enabled.
I am thinking of buying a new laptop which has a Realtek 8723DE wifi
adapter. It seems the rtl8723de driver does not
to exist anymore. The rtl8723de folder is also almost empty in the git tree. Can
somebody clarify this ? Does the rtr8723be now also support the
rtl8723de card ?