> From: linux-wireless-owner@xxxxxxxxxxxxxxx [mailto:linux-wireless- > owner@xxxxxxxxxxxxxxx] On Behalf Of Ujjal Roy > Sent: Thursday, October 29, 2015 7:59 PM > To: Amitkumar Karwar > Cc: Julien Cubizolles; Dan Williams; linux-wireless@xxxxxxxxxxxxxxx; > Nishant Sarmukadam > Subject: Re: mwifiex problem: incompatible network settings > > Hi Amit/Julien, > > On Thu, Oct 29, 2015 at 5:57 PM, Amitkumar Karwar <akarwar@xxxxxxxxxxx> > wrote: > > > > Hi Julien, > > > > > From: Julien Cubizolles [mailto:j.cubizolles@xxxxxxx] > > > Sent: Thursday, October 29, 2015 3:09 AM > > > To: Dan Williams > > > Cc: Amitkumar Karwar; linux-wireless@xxxxxxxxxxxxxxx > > > Subject: Re: mwifiex problem: incompatible network settings > > > > > > Dan Williams <dcbw@xxxxxxxxxx> writes: > > > > > > > He actually meant the wpa_supplicant configuration file, not the > > > > supplicant's dbus config file. But when driven by NetworkManager, > > > > there is no supplicant configuration file. > > > > > > Sorry about that. > > > > > > > Instead, you can find out what config NM is pushing to the > > > > supplicant by checking the NetworkManager logs, where NM will log > lines like: > > > > > > Here are the relevant entries from the syslog file: > > > > > > I included the failed attempt to connect to the WPA protected > > > network named "southcentral" and the successful one to a non > > > protected one named "FreeWifi". > > > > > > > Thanks for the logs. I compared your network manager log with the one > on my setup. Both are same. Basically network manager log doesn't show > security info (WPA/WPA2, encryption mode etc). So we can't rely on that. > > I checked your kernel log shared in previous email. It's incomplete. > It didn't include information when connection was actually attempted. > Probably you can run "dmesg -c >> dmesg.log" in loop with some delay to > capture complete info. Otherwise sharing "/var/log/messages" is also an > option. > > I have created a driver debug patch(attached). Could you please apply > it and share complete dmesg log? > > > > Btw, do you see the problem if AP is configured in WPA2 security mode? > > > > You could check it by disabling the NetworkManager and connect using > wpa_supplicant manually. Sometimes NetworkManager does some problem > which is solved by disabling the NetworkManager. > Makes sense. This will narrow down the issue further. Julien, let me know if any help is needed for this. Regards, Amitkumar ��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
