hp-lt4132 'unavailable' in NetworkManager on Debian 10

[Dan Williams]

On Wed, 2019-09-11 at 10:10 +0000, Focke Christian wrote:
> Hi Aleksander,
> 
> Thanks; I have no idea how to do that because NM is broken with
> regard to the hp-lt4132.
> 
> -- I already shared the NM logs; should I possibly also share the NM
> configuration? Which files?

Can you start up fresh, and then:

systemctl stop ModemManager
systemctl restart NetworkManager
nmcli gen log level trace
systemctl start ModemManager

and then grab logs again? I'd like to see things from the start of when
NM finds the modem.

Also, when you connect the modem through NM, does 'nmcli dev' still
show the cdc-wdm device as "unavailable"?

Dan

> Kind regards, Christian
> 
> -----Original Message-----
> From: Aleksander Morgado <aleksander at aleksander.es<mailto:
> Aleksander%20Morgado%20%3caleksander at aleksander.es%3e>>
> To: Focke Christian <christian.focke at mail.fernfh.ac.at<mailto:
> Focke%20Christian%20%3cchristian.focke at mail.fernfh.ac.at%3e>>
> Cc: Lubomir Rintel <lkundrak at v3.sk<mailto:
> Lubomir%20Rintel%20%3clkundrak at v3.sk%3e>>, Dan Williams <
> dcbw at redhat.com<mailto:Dan%20Williams%20%3cdcbw at redhat.com%3e>>,
> Thomas Haller <thaller at redhat.com<mailto:
> Thomas%20Haller%20%3cthaller at redhat.com%3e>>, 
> modemmanager-devel at lists.freedesktop.org <
> modemmanager-devel at lists.freedesktop.org<mailto:
> %22modemmanager-devel at lists.freedesktop.org
> %22%20%3cmodemmanager-devel at lists.freedesktop.org%3e>>
> Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
> Date: Wed, 11 Sep 2019 11:38:16 +0200
> 
> 
> Hey!
> 
> 
> On Wed, Sep 11, 2019 at 11:22 AM Focke Christian
> 
> <
> 
> <mailto:christian.focke at mail.fernfh.ac.at>
> 
> christian.focke at mail.fernfh.ac.at
> 
> > wrote:
> 
> Yes I know, but with NM-GNOME and nmcli it doesn't work at all;
> that's where I started from.
> 
> 
> Actually it was you who instructed me to use mmcli to analyse the
> issue on MM side.
> 
> 
> 
> Oh, ok, sorry for the confusion then :)
> 
> 
> The MM analysis is done already, e.g. we can see how the whole
> 
> connection sequence works ok with mmcli --simple-connect. Now, the
> 
> missing part is the integration with NM. That is why Lubomir
> requested
> 
> for *NetworkManager* logs while reproducing the issue. Could you
> 
> follow his steps to get the logs and try to repro the problem using
> 
> nmcli?
>