hp-lt4132 'unavailable' in NetworkManager on Debian 10
Christian Focke
c.w.focke at gmail.com
Wed Sep 11 15:50:47 UTC 2019
Hi Dan,
cfocke at hp-eb-x360-1030-g3:~$ nmcli radio
WIFI-HW WIFI WWAN-HW WWAN
enabled enabled enabled disabled
cfocke at hp-eb-x360-1030-g3:~$ nmcli radio wwan on
cfocke at hp-eb-x360-1030-g3:~$ nmcli radio
WIFI-HW WIFI WWAN-HW WWAN
enabled enabled enabled enabled
cfocke at hp-eb-x360-1030-g3:~$
Works now; I feel embarrassed ...
Since when must I explicitly enable radio? Never had to in the past ...
Thanks, Christian
-----Original Message-----
From: Dan Williams <dcbw at redhat.com>
To: Christian Focke <c.w.focke at gmail.com>, Aleksander Morgado <
aleksander at aleksander.es>
Cc: Lubomir Rintel <lkundrak at v3.sk>, Thomas Haller <thaller at redhat.com>
, modemmanager-devel at lists.freedesktop.org <
modemmanager-devel at lists.freedesktop.org>
Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
Date: Wed, 11 Sep 2019 10:08:10 -0500
On Wed, 2019-09-11 at 16:13 +0200, Christian Focke wrote:
> Hi Dan,
> Thanks; here's what I did:
How about:
nmcli radio
?
Dan
> 1. reboot
> 2. 1st shellcfocke at hp-eb-x360-1030-g3:~$ sudo journalctl -fl |tee
> simple-connect_then_simple-disconnect_2.log
> 3. 2nd shellcfocke at hp-eb-x360-1030-g3:~$ sudo systemctl stop
> ModemManagercfocke at hp-eb-x360-1030-g3:~$ sudo systemctl restart
> NetworkManagercfocke at hp-eb-x360-1030-g3:~$ sudo nmcli gen log level
> tracecfocke at hp-eb-x360-1030-g3:~$ sudo systemctl start
> ModemManagercfocke at hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple-
> connect="apn=a1.net,user=ppp at a1plus.at,password=ppp"successfully
> connected the modemcfocke at hp-eb-x360-1030-g3:~$ nmcli
> devDEVICE TYPE STATE CONNECTION
> wlp108s0 wifi disconnected -- cdc-
> wdm0 gsm unavailable
> -- lo loopback unmanaged --
> cfocke at hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple-
> disconnectsuccessfully disconnected all bearers in the
> modemcfocke at hp-eb-x360-1030-g3:~$
> 'simple-connect_then_simple-disconnect_2.log' is attached.
> -- Should I unloop modemmanager-devel at lists.freedesktop.org?
> Thanks, Christian
> -----Original Message-----From: Dan Williams <dcbw at redhat.com>To:
> Focke Christian <christian.focke at mail.fernfh.ac.at>,
> AleksanderMorgado <aleksander at aleksander.es>Cc: Lubomir Rintel <
> lkundrak at v3.sk>, Thomas Haller <thaller at redhat.com>,
> modemmanager-devel at lists.freedesktop.org <
> modemmanager-devel at lists.freedesktop.org>Subject: Re: hp-lt4132
> 'unavailable' in NetworkManager on Debian 10Date: Wed, 11 Sep 2019
> 08:07:46 -0500
> 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
> > brokenwithregardto the hp-lt4132.-- I already shared the NM logs;
> > should I possibly also share theNMconfiguration? Which files?
>
> Can you start up fresh, and then:systemctl stop ModemManagersystemctl
> restart NetworkManagernmcli genlog level tracesystemctl start
> ModemManagerand then grab logs again? I'd like to see things from the
> start ofwhenNM finds the modem.Also, when you connect the modem
> through NM, does 'nmcli dev'stillshowthe 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:
> > FockeChristian <christian.focke at mail.fernfh.ac.at<mailto:
> > Focke%20Christian%20%3cchristian.focke at mail.fernfh.ac.at%3e>>Cc:Lub
> > omir 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>>,Tho
> > mas 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 10Date: Wed,
> > 11Sep 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
> > atall;that'swhere I started from.
> > Actually it was you who instructed me to use mmcli to
> > analysetheissue on MM side.
> >
> > Oh, ok, sorry for the confusion then :)
> > The MM analysis is done already, e.g. we can see how the
> > wholeconnection sequence works ok with mmcli --simple-connect. Now,
> > themissing part is the integration with NM. That is
> > whyLubomirrequestedfor *NetworkManager* logs while reproducing the
> > issue. Could youfollow his steps to get the logs and try to repro
> > the problem usingnmcli?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20190911/f27bd7d0/attachment.html>
More information about the ModemManager-devel
mailing list