<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>Hi Dan,</div><div><br></div><div>Thanks; here's what I did:</div><div><br></div><div>1. reboot</div><div><br></div><div>2. 1st shell</div><div><a href="mailto:cfocke@hp-eb-x360-1030-g3"><a href="mailto:cfocke@hp-eb-x360-1030-g3">cfocke@hp-eb-x360-1030-g3</a></a>:~$ sudo journalctl -fl |tee simple-connect_then_simple-disconnect_2.log</div><div><br></div><div>3. 2nd shell</div><div><a href="mailto:cfocke@hp-eb-x360-1030-g3">cfocke@hp-eb-x360-1030-g3</a>:~$ sudo systemctl stop ModemManager</div><div><a href="mailto:cfocke@hp-eb-x360-1030-g3">cfocke@hp-eb-x360-1030-g3</a>:~$ sudo systemctl restart NetworkManager</div><div><a href="mailto:cfocke@hp-eb-x360-1030-g3">cfocke@hp-eb-x360-1030-g3</a>:~$ sudo nmcli gen log level trace</div><div><a href="mailto:cfocke@hp-eb-x360-1030-g3">cfocke@hp-eb-x360-1030-g3</a>:~$ sudo systemctl start ModemManager</div><div><a href="mailto:cfocke@hp-eb-x360-1030-g3">cfocke@hp-eb-x360-1030-g3</a>:~$ mmcli -m 0 --simple-connect="apn=a1.net,<a href="mailto:user=ppp@a1plus.at">user=ppp@a1plus.at</a>,password=ppp"</div><div>successfully connected the modem</div><div><a href="mailto:cfocke@hp-eb-x360-1030-g3">cfocke@hp-eb-x360-1030-g3</a>:~$ nmcli dev</div><div>DEVICE TYPE STATE CONNECTION </div><div>wlp108s0 wifi disconnected -- </div><div>cdc-wdm0 gsm unavailable -- </div><div>lo loopback unmanaged -- </div><div><a href="mailto:cfocke@hp-eb-x360-1030-g3">cfocke@hp-eb-x360-1030-g3</a>:~$ mmcli -m 0 --simple-disconnect</div><div>successfully disconnected all bearers in the modem</div><div><a href="mailto:cfocke@hp-eb-x360-1030-g3">cfocke@hp-eb-x360-1030-g3</a>:~$ </div><div><br></div><div>'simple-connect_then_simple-disconnect_2.log' is attached.</div><div><br></div><div>-- Should I unloop <a href="mailto:modemmanager-devel@lists.freedesktop.org">modemmanager-devel@lists.freedesktop.org</a>?</div><div><br></div><div>Thanks, Christian</div><div><br></div><div>-----Original Message-----</div><div><b>From</b>: Dan Williams <<a href="mailto:Dan%20Williams%20%3cdcbw@redhat.com%3e">dcbw@redhat.com</a>></div><div><b>To</b>: Focke Christian <<a href="mailto:Focke%20Christian%20%3cchristian.focke@mail.fernfh.ac.at%3e">christian.focke@mail.fernfh.ac.at</a>>, Aleksander Morgado <<a href="mailto:Aleksander%20Morgado%20%3caleksander@aleksander.es%3e">aleksander@aleksander.es</a>></div><div><b>Cc</b>: Lubomir Rintel <<a href="mailto:Lubomir%20Rintel%20%3clkundrak@v3.sk%3e">lkundrak@v3.sk</a>>, Thomas Haller <<a href="mailto:Thomas%20Haller%20%3cthaller@redhat.com%3e">thaller@redhat.com</a>>, modemmanager-devel@lists.freedesktop.org <<a href="mailto:%22modemmanager-devel@lists.freedesktop.org%22%20%3cmodemmanager-devel@lists.freedesktop.org%3e">modemmanager-devel@lists.freedesktop.org</a>></div><div><b>Subject</b>: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10</div><div><b>Date</b>: Wed, 11 Sep 2019 08:07:46 -0500</div><div><br></div><pre>On Wed, 2019-09-11 at 10:10 +0000, Focke Christian wrote:</pre><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>Hi Aleksander,</pre><pre><br></pre><pre>Thanks; I have no idea how to do that because NM is broken with</pre><pre>regard to the hp-lt4132.</pre><pre><br></pre><pre>-- I already shared the NM logs; should I possibly also share the NM</pre><pre>configuration? Which files?</pre></blockquote><pre><br></pre><pre>Can you start up fresh, and then:</pre><pre><br></pre><pre>systemctl stop ModemManager</pre><pre>systemctl restart NetworkManager</pre><pre>nmcli gen log level trace</pre><pre>systemctl start ModemManager</pre><pre><br></pre><pre>and then grab logs again? I'd like to see things from the start of when</pre><pre>NM finds the modem.</pre><pre><br></pre><pre>Also, when you connect the modem through NM, does 'nmcli dev' still</pre><pre>show the cdc-wdm device as "unavailable"?</pre><pre><br></pre><pre>Dan</pre><pre><br></pre><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>Kind regards, Christian</pre><pre><br></pre><pre>-----Original Message-----</pre><pre>From: Aleksander Morgado <</pre><a href="mailto:aleksander@aleksander.es"><pre>aleksander@aleksander.es</pre></a><pre><mailto:</pre><a href="mailto:Aleksander%20Morgado%20%3caleksander@aleksander.es"><pre>Aleksander%20Morgado%20%3caleksander@aleksander.es</pre></a><pre>%3e>></pre><pre>To: Focke Christian <</pre><a href="mailto:christian.focke@mail.fernfh.ac.at"><pre>christian.focke@mail.fernfh.ac.at</pre></a><pre><mailto:</pre><a href="mailto:Focke%20Christian%20%3cchristian.focke@mail.fernfh.ac.at"><pre>Focke%20Christian%20%3cchristian.focke@mail.fernfh.ac.at</pre></a><pre>%3e>></pre><pre>Cc: Lubomir Rintel <</pre><a href="mailto:lkundrak@v3.sk"><pre>lkundrak@v3.sk</pre></a><pre><mailto:</pre><a href="mailto:Lubomir%20Rintel%20%3clkundrak@v3.sk"><pre>Lubomir%20Rintel%20%3clkundrak@v3.sk</pre></a><pre>%3e>>, Dan Williams <</pre><a href="mailto:dcbw@redhat.com"><pre>dcbw@redhat.com</pre></a><pre><mailto:</pre><a href="mailto:Dan%20Williams%20%3cdcbw@redhat.com"><pre>Dan%20Williams%20%3cdcbw@redhat.com</pre></a><pre>%3e>>,</pre><pre>Thomas Haller <</pre><a href="mailto:thaller@redhat.com"><pre>thaller@redhat.com</pre></a><pre><mailto:</pre><a href="mailto:Thomas%20Haller%20%3cthaller@redhat.com"><pre>Thomas%20Haller%20%3cthaller@redhat.com</pre></a><pre>%3e>>, </pre><a href="mailto:modemmanager-devel@lists.freedesktop.org"><pre>modemmanager-devel@lists.freedesktop.org</pre></a><pre> <</pre><a href="mailto:modemmanager-devel@lists.freedesktop.org"><pre>modemmanager-devel@lists.freedesktop.org</pre></a><pre><mailto:</pre><a href="mailto:%22modemmanager-devel@lists.freedesktop.org"><pre>%22modemmanager-devel@lists.freedesktop.org</pre></a><pre><br></pre><a href="mailto:%22%20%3cmodemmanager-devel@lists.freedesktop.org"><pre>%22%20%3cmodemmanager-devel@lists.freedesktop.org</pre></a><pre>%3e>></pre><pre>Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10</pre><pre>Date: Wed, 11 Sep 2019 11:38:16 +0200</pre><pre><br></pre><pre><br></pre><pre>Hey!</pre><pre><br></pre><pre><br></pre><pre>On Wed, Sep 11, 2019 at 11:22 AM Focke Christian</pre><pre><br></pre><pre><</pre><pre><br></pre><pre><mailto:</pre><a href="mailto:christian.focke@mail.fernfh.ac.at"><pre>christian.focke@mail.fernfh.ac.at</pre></a><pre>></pre><pre><br></pre><a href="mailto:christian.focke@mail.fernfh.ac.at"><pre>christian.focke@mail.fernfh.ac.at</pre></a><pre><br></pre><pre><br></pre><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>wrote:</pre></blockquote><pre><br></pre><pre>Yes I know, but with NM-GNOME and nmcli it doesn't work at all;</pre><pre>that's where I started from.</pre><pre><br></pre><pre><br></pre><pre>Actually it was you who instructed me to use mmcli to analyse the</pre><pre>issue on MM side.</pre><pre><br></pre><pre><br></pre><pre><br></pre><pre>Oh, ok, sorry for the confusion then :)</pre><pre><br></pre><pre><br></pre><pre>The MM analysis is done already, e.g. we can see how the whole</pre><pre><br></pre><pre>connection sequence works ok with mmcli --simple-connect. Now, the</pre><pre><br></pre><pre>missing part is the integration with NM. That is why Lubomir</pre><pre>requested</pre><pre><br></pre><pre>for *NetworkManager* logs while reproducing the issue. Could you</pre><pre><br></pre><pre>follow his steps to get the logs and try to repro the problem using</pre><pre><br></pre><pre>nmcli?</pre><pre><br></pre></blockquote><pre><br></pre></body></html>