Realtek Rtl8723bs Driver
Baldovino Caya
I recently installed windows 7. As a part of this, I was required to install the drivers for my onboard wireless adapter (Realtek 8187). However, with the driver came this annoying management studio called Realtek Wireless Lan Utility. It's not a huge burden, except that every time I log in to my computer (if I've been idle for a while), this idiot application is up on the screen and I need to click 'close' to close it.
I can't seem to find any 'do not start at windows startup' on the application or anything that would cause it to just let windows manage my wireless settings. I've done the preliminary google search, but searches for 'disable realtek wireless lan utility' seem to come up with nada for results. Anyone know how to disable this stupid program?
So, hopefully this might help someone in the future, but I was able to find the solution. In the Program Files directory, there is a Realtek Wireless Lan Utility and Driver folder. Within this folder is a driver/ folder. I copied this folder to another location, uninstalled the realtek wireless lan utility (which also uninstalled the driver). I then went into Device Manager, searched for new hardware (which it found the wireless adapter, but required a driver). I pointed the driver installation system to the driver/ folder, and it installed JUST the driver.
RealTek Wireless Lan Utility-It's listed as a service - you can close the utiltiy by right clicking on the icon on the tray and choosing QUIT - if you want to stop it from running - open services - find 'Realtek87b' open it by double clicking on it - stop it - then disable it - then forget about it. The utility will not run when you restart and will be removed the next time you update or remove the driver. It is a small utility that shows what other ReaTek wireless users are on your lan. that's all nothing insidious - just a driver writer's utility that might be of use to an organization. It allows wireless users on the same lan to discover and quickly communicate with each other - the same way that windows lan users used to do with the lan utility that used to be bundled in all lan drivers.
Power off, unplug the Alfa from USB and restart. The Alfa utility should not appear. Plug in the Alfa when needed or turn it on if it is an onboard device and connect to network as usual. This will just use the normal Windows interface.
First you should look if the utility maybe has some preferences like load on startup or use windows utility or something like that. Maybe the programm is showed at systemsettings; programms and functions. If so, you can uninstall it like every other programm.
Hello, and have a nice day!I have Freescale IMX6q sabresd. and Android 4.3 on it.Trying to connect SDIO wifi rtl8723bs. All configuratoin i do from manual with rtl8723bs.Compiling the driver as module, then put it system/lib/modules and load by insmod. No warning then i load the module, but wifi is not working.If execute the netcfg or ifconfig, there is no wifi.One obscure thing: My driver consists only of:8723bs.koOther drivers consist of:
carlix, as per given this driver is in staging, it's not available in the linux-stable tree which Ubuntu typically pulls from (but testing it with the driver installed simultaneously provides evidence of stability with it).
So, there are two things that would need to happen here. One is for this staging driver to be considered for inclusion into Ubuntu. Second is for this driver to be considered for inclusion into linux-stable, where it would be pulled into Ubuntu as a matter of course.
They are using which is a forked proyect of and it has no activity on 11 months meanwhile the original from hadess has periodic activity thats perhaps the reason of the delay to make it an oficial driver
carlix, could you please request upstream submit the rtl8723bs driver to linux-stable via the appropriate mailing list (TO: Greg Kroah-Hartman, Larry Finger, and Bastien Nocera CC driverdev-devel)? This will help get the ball rolling towards your hardware.
With 19 more months of support for 16.04 (and the 4.4 kernel), consider the 8723bs drivers in the
trusty-chestersmill repository ( trusty-chestersmill public)
These drivers worked fine through the Ubuntu 4.4.0-142 release (when the API change broke many drivers). The fix for that problem may be much simpler than changing the lwfinger or hadess drivers. Note, bug 1755309 for the header fix necessary for the audio packages from that repo.