Hi, sorry for interfering in this discussion, but as I'm having the same problem than Eduard, I would like to provide some info about the issue. But before this, a probably important point: I have here a proprietary ModemManager (see [1]) but this doesn't matter as the failure seems to be the same: after an unexpected PPP-disconnection, the modem disappears from the NM devices list even the ModemManager didn't emitted the 'DeviceRemoved' signal.
For reproducing the issue you can try killing the ppp-daemon when a PDP-context is up. Here this leads to the described issue: The modem is gone from the NM devices list even 'lsusb' shows that the modem is still there and the ModemManager too. Regards, Luis [1] ModemManager from this site: http://movilforum.com/escritoriomovistar/ -------- Original-Nachricht -------- > Datum: Wed, 25 Jan 2012 16:08:59 -0600 > Von: Dan Williams <[email protected]> > An: Eduard Hasenleithner <[email protected]> > CC: [email protected] > Betreff: Re: how to get 3g modem back in managed state > On Fri, 2011-12-30 at 11:46 +0100, Eduard Hasenleithner wrote: > > 2011/12/30 José Queiroz <[email protected]>: > > > Try to SIGTERM modem-manager. > > > > > > sudo killall -TERM modem-manager > > > > This does not work for me. Is there no way to tell network-manager to > > manage a particular device again while keeping nm (and mm) running? > > We need a bit more information here. Does the device actually disappear > from the USB bus (ie, it crashes)? When this happens check with lsusb > to see if it's still there or not. > > If it is still there, we'll need some more detailed logs from > ModemManager. I did notice that disconnecting the device failed, so it > would be good to figure out why that happened. ie this line > specifically from the logs: > > Dec 29 18:17:28 eeepc modem-manager[519]: <info> Modem > /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting > -> connected) > > indicates that MM was not able to tell the modem to terminate the packet > connection successfully, and thus it has no choice but to assume you're > still connected. A detailed MM debug log would indicate which command > is failing there. See: > > http://live.gnome.org/NetworkManager/Debugging > > for how to get that log. > > > btw, is there a utility which allows to show all devices managed by > > network manager, and their state (over dbus)? > > nm-tool or "nmcli dev" > > Dan > > > _______________________________________________ > networkmanager-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de _______________________________________________ networkmanager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
