Send connman mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."


Today's Topics:

   1. Re: Error "wifi: No carrier" only to connman (Jun Nie)
   2. Re: Error "wifi: No carrier" only to connman (Daniel Wagner)


----------------------------------------------------------------------

Message: 1
Date: Wed, 13 Mar 2019 16:40:50 +0800
From: Jun Nie <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: connman <[email protected]>
Subject: Re: Error "wifi: No carrier" only to connman
Message-ID:
        <CABymUCMjSzdmDyh6E2YBPp5sWbf2oAwO1coaSXXS+0V9=td...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Daniel Wagner <[email protected]> ?2019?3?13??? ??4:27???
>
> > For dbus message, I did not collect any log yet due to connection
> > issue. I am not sure why DBUS_SESSION_BUS_ADDRESS cannot be found on
> > board as on PC. Do you have any suggestion to collect dbus message?
>
> I think wpa_s prints also message when running with -ddd that a scan has
> been trigger. So you don't have to intercept the D-Bus message if that
> is a prroblem in your setup.

But the scan operation trace in wpa_s log is aligned with the
"connmanctl scan wifi" success case. Or the scan trace may be earlier
than the success case by one scan command. Does this means the bug is
connman internal issue, instead of dbus/wpa_s related? I mean the scan
message is not sent by connman yet.

> > I am not sure which driver is default one. But I killed wpa_supplicant
> > and run below two commands in different test, and see bug in both
> > case. Is this the right test?
>
> Also no idea what the default is but my bet would be on wext :)
>
> > wpa_supplicant -D nl80211 -u -t -ddd 2>&1 > /tmp/wpa.log &
> > wpa_supplicant -D wext -u -t -ddd 2>&1 > /tmp/wpa.log &
>
> That looks about right.


------------------------------

Message: 2
Date: Wed, 13 Mar 2019 09:47:38 +0100
From: Daniel Wagner <[email protected]>
To: Jun Nie <[email protected]>
Cc: connman <[email protected]>
Subject: Re: Error "wifi: No carrier" only to connman
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed

> But the scan operation trace in wpa_s log is aligned with the
> "connmanctl scan wifi" success case. Or the scan trace may be earlier
> than the success case by one scan command. Does this means the bug is
> connman internal issue, instead of dbus/wpa_s related? I mean the scan
> message is not sent by connman yet.

Not sure what you are seeing and it's hard to say where your problem is.

Anyway, another option might be to add CONNMAN_SUPPLICANT_DEBUG to 
environment and see if you get more info, e.g. something like

        CONNMAN_SUPPLICANT_DEBUG=1 connmand -n -d plugins/wifi.c


------------------------------

Subject: Digest Footer

_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman


------------------------------

End of connman Digest, Vol 41, Issue 15
***************************************

Reply via email to