LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 10-13-2017, 08:22 PM   #1
aguador
Member
 
Registered: Sep 2014
Location: Madrid, Spain
Distribution: Mageia (Cauldron)
Posts: 66

Rep: Reputation: Disabled
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:

https://gist.github.com/kylemanna/6930087

with not luck. I even found an open wifi signal as I was writing this, but connman will not connect.

Here is the anonymised output of one of my attempts:

Code:
connmanctl> connect wifi_XXXXXXXXX_managed_psk
Agent ReportError wifi_XXXXXXXXX_managed_psk
  connect-failed
Agent request cancelled by ConnMan
Error /net/connman/service/wifi_XXXXXXXXXXXXX_managed_psk: Operation aborted
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 05:17 AM. Reason: Clarification that networking in general works
 
Old 10-19-2017, 03:18 PM   #2
nini09
Senior Member
 
Registered: Apr 2009
Posts: 1,519

Rep: Reputation: 137Reputation: 137
What's output of "connmanctl scan wifi"? Which AP do you connect?
 
Old 10-19-2017, 03:57 PM   #3
aguador
Member
 
Registered: Sep 2014
Location: Madrid, Spain
Distribution: Mageia (Cauldron)
Posts: 66

Original Poster
Rep: Reputation: Disabled
Code:
$ connmanctl scan wifi
Scan completed for wifi
Similarly, connmanctl services displays APs, including my TP-Link AC1750 router which, in this case, sits directly behind this machine.
 
Old 10-20-2017, 03:42 PM   #4
nini09
Senior Member
 
Registered: Apr 2009
Posts: 1,519

Rep: Reputation: 137Reputation: 137
How do you know your configuration is correct? We need information to help you.
 
Old 10-21-2017, 01:40 PM   #5
aguador
Member
 
Registered: Sep 2014
Location: Madrid, Spain
Distribution: Mageia (Cauldron)
Posts: 66

Original Poster
Rep: Reputation: Disabled
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.

Last edited by aguador; 10-21-2017 at 01:50 PM.
 
Old 10-21-2017, 02:47 PM   #6
aguador
Member
 
Registered: Sep 2014
Location: Madrid, Spain
Distribution: Mageia (Cauldron)
Posts: 66

Original Poster
Rep: Reputation: Disabled
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.
 
Old 10-22-2017, 05:11 PM   #7
aguador
Member
 
Registered: Sep 2014
Location: Madrid, Spain
Distribution: Mageia (Cauldron)
Posts: 66

Original Poster
Rep: Reputation: Disabled
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.
 
Old 10-23-2017, 04:06 PM   #8
nini09
Senior Member
 
Registered: Apr 2009
Posts: 1,519

Rep: Reputation: 137Reputation: 137
Dump dmesg and show output relative to your WiFi module.
 
Old 10-23-2017, 05:16 PM   #9
aguador
Member
 
Registered: Sep 2014
Location: Madrid, Spain
Distribution: Mageia (Cauldron)
Posts: 66

Original Poster
Rep: Reputation: Disabled
[ 4.673695] Intel(R) Wireless WiFi driver for Linux
[ 4.673696] Copyright(c) 2003- 2015 Intel Corporation
[ 4.673798] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[ 4.677583] Linux video capture interface: v2.00
[ 4.680522] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-26.ucode failed with error -2
[ 4.680562] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-25.ucode failed with error -2
[ 4.680575] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
[ 4.680588] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2
[ 4.684000] SSE version of gcm_enc/dec engaged.
[ 4.689510] iwlwifi 0000:02:00.0: loaded firmware version 22.391740.0 op_mode iwlmvm
.
. {Partition mounting, video, USB}
.
[ 4.760023] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210
[ 4.761687] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 4.761870] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
.
. {Video. Bluetooth, touchpad, etc.}
.
[ 5.148652] r8169 0000:01:00.1 enp1s0f1: renamed from eth0
[ 5.244458] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
 
Old 10-24-2017, 03:46 PM   #10
nini09
Senior Member
 
Registered: Apr 2009
Posts: 1,519

Rep: Reputation: 137Reputation: 137
Firmware loading is failure. Execute "lspci" to find out WiFi module's detail information and then find out how to load firmware on Mageia.
 
Old 10-25-2017, 05:42 AM   #11
aguador
Member
 
Registered: Sep 2014
Location: Madrid, Spain
Distribution: Mageia (Cauldron)
Posts: 66

Original Poster
Rep: Reputation: Disabled
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:

Code:
$ modinfo
modinfo: ERROR: missing module or filename.
[aguador@localhost ~]$ modinfo iwlwifi
filename:       /lib/modules/4.9.56-desktop-1.mga6/kernel/drivers/net/wireless/i
ntel/iwlwifi/iwlwifi.ko.xz
license:        GPL
author:         Copyright(c) 2003- 2015 Intel Corporation <linuxwifi@intel.com>
description:    Intel(R) Wireless WiFi driver for Linux
     **SNIP**
firmware:       iwlwifi-7265D-26.ucode
firmware:       iwlwifi-7265-17.ucode
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?
 
Old 10-25-2017, 03:37 PM   #12
nini09
Senior Member
 
Registered: Apr 2009
Posts: 1,519

Rep: Reputation: 137Reputation: 137
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.
 
Old 10-26-2017, 01:14 AM   #13
aguador
Member
 
Registered: Sep 2014
Location: Madrid, Spain
Distribution: Mageia (Cauldron)
Posts: 66

Original Poster
Rep: Reputation: Disabled
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.
 
Old 10-26-2017, 10:35 AM   #14
aguador
Member
 
Registered: Sep 2014
Location: Madrid, Spain
Distribution: Mageia (Cauldron)
Posts: 66

Original Poster
Rep: Reputation: Disabled
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.
 
Old 10-26-2017, 03:27 PM   #15
nini09
Senior Member
 
Registered: Apr 2009
Posts: 1,519

Rep: Reputation: 137Reputation: 137
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.
 
  


Reply

Tags
connman, networking


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Can connect to cellphone through WIFI HOTSPOT, but cannot connect to my own WIFI network diegoandresalvarez Linux - Networking 7 10-22-2016 12:54 PM
Connman and WiFi network with multiple AP and same SSID RonanG Linux - Networking 1 04-05-2016 03:09 AM
opensuse 10.2 recognises wireless card, but won't connect nmsuaussie Linux - Newbie 3 05-24-2007 04:21 AM
eth1 recognises ipw2100-FC6, but can't connect idk666 Linux - Wireless Networking 3 11-29-2006 10:23 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 09:05 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration