Hi Dan, cfocke@hp-eb-x360-1030-g3:~$ nmcli radio WIFI-HW WIFI WWAN-HW WWAN enabled enabled enabled disabled
cfocke@hp-eb-x360-1030-g3:~$ nmcli radio wwan on cfocke@hp-eb-x360-1030-g3:~$ nmcli radio WIFI-HW WIFI WWAN-HW WWAN enabled enabled enabled enabled cfocke@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 <d...@redhat.com> To: Christian Focke <c.w.fo...@gmail.com>, Aleksander Morgado < aleksan...@aleksander.es> Cc: Lubomir Rintel <lkund...@v3.sk>, Thomas Haller <thal...@redhat.com> , modemmanager-devel@lists.freedesktop.org < modemmanager-devel@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@hp-eb-x360-1030-g3:~$ sudo journalctl -fl |tee > simple-connect_then_simple-disconnect_2.log > 3. 2nd shellcfocke@hp-eb-x360-1030-g3:~$ sudo systemctl stop > ModemManagercfocke@hp-eb-x360-1030-g3:~$ sudo systemctl restart > NetworkManagercfocke@hp-eb-x360-1030-g3:~$ sudo nmcli gen log level > tracecfocke@hp-eb-x360-1030-g3:~$ sudo systemctl start > ModemManagercfocke@hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple- > connect="apn=a1.net,user=p...@a1plus.at,password=ppp"successfully > connected the modemcfocke@hp-eb-x360-1030-g3:~$ nmcli > devDEVICE TYPE STATE CONNECTION > wlp108s0 wifi disconnected -- cdc- > wdm0 gsm unavailable > -- lo loopback unmanaged -- > cfocke@hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple- > disconnectsuccessfully disconnected all bearers in the > modemcfocke@hp-eb-x360-1030-g3:~$ > 'simple-connect_then_simple-disconnect_2.log' is attached. > -- Should I unloop modemmanager-devel@lists.freedesktop.org? > Thanks, Christian > -----Original Message-----From: Dan Williams <d...@redhat.com>To: > Focke Christian <christian.fo...@mail.fernfh.ac.at>, > AleksanderMorgado <aleksan...@aleksander.es>Cc: Lubomir Rintel < > lkund...@v3.sk>, Thomas Haller <thal...@redhat.com>, > modemmanager-devel@lists.freedesktop.org < > modemmanager-devel@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 <aleksan...@aleksander.es<mailto: > > aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>To: > > FockeChristian <christian.fo...@mail.fernfh.ac.at<mailto: > > focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>Cc:Lub > > omir Rintel <lkund...@v3.sk<mailto: > > lubomir%20rintel%20%3clkund...@v3.sk%3e>>, Dan Williams < > > d...@redhat.com<mailto:dan%20williams%20%3cd...@redhat.com%3e>>,Tho > > mas Haller <thal...@redhat.com<mailto: > > thomas%20haller%20%3cthal...@redhat.com%3e>>, > > modemmanager-devel@lists.freedesktop.org < > > modemmanager-devel@lists.freedesktop.org<mailto: > > %22modemmanager-de...@lists.freedesktop.org > > %22%20%3cmodemmanager-de...@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.fo...@mail.fernfh.ac.at>christian.fo...@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?
_______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
