connman recognises available wifi but will not connect
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
connman recognises available wifi but will not connect
I am running E21 and E22 under Mageia.
Mageia installs with systemd.networkd and systemd.resolved enabled by default. (Edit: and there is not problem connecting with networkd) Those services have been disabled and connman.service enabled. The wired connection is fine, but while connman detects available wifi, it is impossible to connect.
I have tried entering my password through econnman and using connmanctl with no luck. I also tried manually creating a configuration file following the steps here:
My suspicion is that there is something else going on with systemd, or perhaps it's just my increasing perception of it as the evil empire.
In any event here are the other "network" services running:
Code:
$ systemctl | grep network
network-up.service loaded active exited LSB: Wait for the hotplugged network to be up
network.service loaded active running LSB: Bring up/down networking
network-online.target loaded active active Network is Online
network.target loaded active active Network
Last edited by aguador; 10-14-2017 at 04:17 AM.
Reason: Clarification that networking in general works
Thanks for helping with this. I know that connman is not generally a network favorite.
I am not sure what configuration information to provide. However, the contents of /var/lib/connman/settings shows OfflineMode, Bluetooth, P2P are all set to false; WiFi and Wired are set to true with tethering false.
Your message prompted me to try again. I have successfully activated connman on my Mageia 7 system using connmanctl.
However, on the Mageia 6 system I tried activating using econnman and apparently made an error in entering the password. I do not know if that has affected what is happening, but even after making a couple of attempts with the correct password and even, between attempts, removing the wifi configuration file in /var/lib/connman and rebooting, connmanctl returns an "invalid-key" error, rejects registration, and aborts.
As I was investigating more, a mention of wpa_supplicant brought an AHA! Both machines are running wpa_supplicant 2.6. However, the latest bug fix patch was packaged and released to Mageia 7, but has yet to arrive in Mageia 6. I'll see if I can find out more.
I have not installed first, the updated wpa_supplicant (and dependencies) and, second, updated connman in my Mageia 6 laptop. However, I still get the "invalid-key" error.
Fantastic, thank you. I am obviously in new territory here. I saw the errors, but did not think much about it given that I do have connectivity under systemd.
That said, according to Intel I need iwlwifi-7265-14/iwlwifi-7265D-14 versions of the ucode, which were not present on my system. I have downloaded, decompressed and copied them into /lib/firmware. However . . .
Correct me if I am wrong, but the problem seems to be with the kernel or the way it is complied. Here is a snippet of the output of modinfo:
From dmseg it seems that the kernel looks to load iwlwifi-7265D-26.ucode, which is not present on my system, them drops down progressively to lower versions, none of which are not on my system.
I have not seen in Mageia documentation anything about loading specific firmware. Can this be done or should the kernel be repackaged?
How do you download WiFi firmware? Based on Mageia release note, you need download the firmware from Mageia online repositories. Following link could help you, https://wiki.mageia.org/en/Software_management.
Yes, that's standard software installation. There seem to be two issues. First, although I think the Intel wifi may be an older chipset, the correct driver seems to be fairly new, or at least fairly recently updated. Second, why is the boot routine trying to load drivers that do not exist? So, in the first instance, while the driver is not present in the Mageia iwlwifi package (yet), why isn't it attempting an earlier package? Now that the driver IS present, why is it not being selected? (I have confirmed that the proper driver is identified at boot by changing the name of that driver to the first one it attempts to boot. However, it is explicitly rejected because the file name does not match the driver sought.)
I have a question in the Mageia forums and will let you know.
I am still exploring the issue, but missed this line from dmseg (above):
[ 4.689510] iwlwifi 0000:02:00.0: loaded firmware version 22.391740.0 op_mode iwlmvm
iwlwifi-7265D-22.ucode is actually being loaded, and does, obviously work with systemd-networkd.service, at least for strong wifi signals given that I am connecting in the same room as the router!
I am still trying to determine if there is a way to load iwlwifi-7265D-14 with the current kernel (4.9.56) to see if that makes a difference.
Normally, WiFi driver decide what firmware version is used. It is not always last firmware is better. Important is firmware version match with driver version.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.