<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 06/11/13 00:59, <a
class="moz-txt-link-abbreviated"
href="mailto:david.a58@optusnet.com.au">david.a58@optusnet.com.au</a>
wrote:<br>
</div>
<blockquote
cite="mid:38201c4a8c86ac69536ac34cc118d7e5933f878d@webmailnew.optuszoo.com.au"
type="cite"><br>
<br>
<br>
<br>
<blockquote>----- Original Message -----<br>
<div class="replyForwardedMainHeader"
style="width:100%;background:rgb(228,228,228);">
<div class="replyForwardedMessageHeaders"
style="font-weight:bold;">From:</div>
"Aleksander Morgado" <a class="moz-txt-link-rfc2396E"
href="mailto:aleksander@lanedo.com"><aleksander@lanedo.com></a></div>
<br>
<div class="replyForwardedMessageHeaders"
style="font-weight:bold;">To:</div>
"David Allen" <a class="moz-txt-link-rfc2396E"
href="mailto:david.a58@optusnet.com.au"><david.a58@optusnet.com.au></a><br>
<div class="replyForwardedMessageHeaders"
style="font-weight:bold;">Sent:</div>
Tue, 05 Nov 2013 09:20:31 +0100<br>
<div class="replyForwardedMessageHeaders"
style="font-weight:bold;">Subject:</div>
Re: Huawei E160E USB modem fails to connect with
ModemManager-1.0.0 and NetworkManager-0.9.8.8<br>
<br>
>>><br>
>> Could you get ModemManager debug logs?<br>
>> <a class="moz-txt-link-freetext"
href="http://www.freedesktop.org/wiki/Software/ModemManager/Debugging">http://www.freedesktop.org/wiki/Software/ModemManager/Debugging</a><br>
>><br>
>> MM 1.0 is using the QMI support in the modem; not
AT+PPP. We need to<br>
>> understand where and why it fails.<br>
>><br>
> Thankyou for your interest. It is much appreciated.<br>
> <br>
> I had tried to get the debug messages from ModemManager
using the<br>
> instructions from the page you linked, but something must
be different<br>
> with my setup.<br>
> I have found that if I use the command "su -c
'/usr/sbin/ModemManager<br>
> --debug; /usr/sbin/NetworkManager --no-daemon
--log-level=DEBUG &' " the<br>
> logs appear to be complete and I can then use nmcli to
attempt a<br>
> connection<br>
> <br>
> Please find attached the revised debug logs:<br>
> dump_working_revised.txt - Recorded with earlier versions<br>
> dump_notworking_revised.txt - Recorded with later versions<br>
> <br>
> <br>
<br>
For some reason ModemManager debug logs in the
'notworking_revised' one<br>
do *not* have the chunk of info where the connection attempt is
done...<br>
Can you retry that test, with the commands that best work for
you to<br>
setup debug logging, and then retry the connection attempt with
nmcli?<br>
<br>
Also, please CC the mailing list as well in your reply.<br>
<br>
<br>
-- <br>
Aleksander<br>
</blockquote>
</blockquote>
Please find attached another attempt at getting a full debug log.
This time I renamed the ModemManager and NetworkManager executables
and created scripts that called these renamed files with the debug
options in the hope that any respawned processes would continue
debug logging.<br>
<br>
David<br>
<br>
<br>
<blockquote
cite="mid:38201c4a8c86ac69536ac34cc118d7e5933f878d@webmailnew.optuszoo.com.au"
type="cite">
<hr><br>
</blockquote>
<br>
</body>
</html>