![]() ![]() ![]() Then, make a backup of your old /etc/wpa_supplicant/wpa_nf (if it already exists), and then put this in it:Ĭtrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel I use OpenRC, but Mint uses either Upstart or systemd and I don't know how to use either of them. Then, tell your init system to stop NetworkManager. I imagine wpa_supplicant will already be installed, but it might not be a bad idea to explicitly tell it to install it anyway, so that it knows that you actually want it and that it's not just installed because something else happens to need it. It might break your system, and a quick googling didn't find anyone else using wpa_supplicant on Mint.įirst, you'll need to make sure wpa_supplicant and wpa_gui are installed. It might not be possible to get wpa_gui to work properly on Mint without some hackery, but here's what I would try. I'll tell you what worked for me on my Gentoo, but it might not work for you, since, while Gentoo makes you (lets you, oh the freedom!) do everything yourself, Mint and friends are "user friendly" and want to do things in their own way. I switched to Gentoo Linux about two years ago, and I've been loving it ever since. After that, I tried some other distros and eventually gave up and just used OSX for a while. I used Ubuntu a long time ago until I got fed up with it. Did you install an update that broke it, or is it time to reboot? Things don't usually just break with time like that. Tell me more about the switch to the wpa_ gui. I switched to Mint recently and on initial setup, the wi-fi worked fine, two days later it stopped working even though the blue light on the panel remains lit. ![]() It uses almost zero CPU while connecting, and takes half as long as wicd does to connect. I haven't had a single disconnect or failed connection since I got it working. You don't need to write any configuration files, contrary to what I was previously told - there's a wpa_gui that works great. While connecting, wicd would use 100% CPU for the entire 10 seconds it took to connect, and if it failed, it would continue reporting progress anyway and using 100% CPU even after my kernel logs clearly indicated that the connection had already failed.Ī few days ago, I switched to wpa_supplicant. It would often have trouble giving me a list of networks when I wasn't connected, and it would refuse to list any networks if it was already connected to one. I used to use wicd, and it was often nearly impossible to get it to connect to certain networks and it would randomly get disconnected. Are you sure it's actually a driver problem? What are you using to actually control your wifi device: wpa_supplicant, wicd, networkmanager, or something else? I had always assumed all of my problems were due to my wifi drivers - a Broadcom (the worst, when it comes to Linux drivers) BCM4321 in a macbook, but, as it turns out, it was actually the userspace program (wicd, in my case) that tells driver what to do that was at fault ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |