Re: [back to this topic] Re: PIN handling problem on Connect automatically

[Dan Williams <dcbw redhat com>]

On Fri, 2012-02-03 at 20:55 +0000, Sérgio Basto wrote:
> On Thu, 2011-10-27 at 11:29 -0500, Dan Williams wrote: 
> > On Thu, 2011-10-27 at 06:25 +0100, Sérgio Basto wrote:
> > > On Wed, 2011-10-26 at 19:53 -0500, Dan Williams wrote: 
> > > > On Wed, 2011-10-26 at 17:48 +0100, Sérgio Basto wrote:
> > > > > Hi, on my HUAWEI E1550 HSDPA usb stick,
> > > > > 
> > > > > If I do automatically , I got always 
> > > > > Oct 26 17:33:19 segulix modem-manager[1014]: <info>  (ttyUSB3) opening
> > > > > serial port...
> > > > > Oct 26 17:33:19 segulix modem-manager[1014]: Invalid error code: 500
> > > > > Oct 26 17:33:19 segulix modem-manager[1014]: Invalid error code: 303
> > > > > 
> > > > > but now I checked, if I use PIN dialog that pop-up and go, very fast, to
> > > > > nm-applet to connect broad band , I got same error.
> > > > > If, I use PIN dialog  , to unlock modem , and wait a few seconds, I
> > > > > connect without problems .
> > > > > In short, we have to wait a few time (one or two seconds) after unlock
> > > > > modem, to connect.
> > > > 
> > > > THis could be a quirk with your modem's firmware, any chance you can
> > > > grab verbose modem-manager debug logs as described here?
> > > 
> > > sure 
> > > 
> > > 
> > > > http://live.gnome.org/NetworkManager/Debugging
> > > > 
> > > > under the "3G" section.  Basically, we need to see what your modem is
> > > > doing and how it's responding.  Some modems do need quirks and we could
> > > > add one for yours.  We'd also need to know what kind of  modem and what
> > > > model it is.
> > > 
> > > HUAWEI E1550 HSDPA usb stick,
> > 
> > So what appears to be going on here is that obviously the modem isn't
> > unlocked when it's exported over D-Bus from MM.  NM sees the new modem
> > and tries to enable it, successfully sends the pin, gets a reply from
> > MM, and then tries to enable the modem.  It looks like a race between
> > modem-manager cleanup of the PIN unlock and NM trying to immediately
> > re-enable the modem after sending the PIN.  So yeah, a bug in
> > ModemManager, but probably best to work around it in NM for now.
> 
> Hi, back to this topic ,
> Now that we have on F-16 automatically unblock PIN, we just have to wait
> for closing doors like this, to dial/connect automatically.
>   
> Feb  3 20:14:25 segulix modem-manager[1230]: <info>  (ttyUSB0) closing
> serial port...
> Feb  3 20:14:25 segulix dbus-daemon[1160]: modem-manager[1230]: <info>
> (ttyUSB0) closing serial port...
> Feb  3 20:14:25 segulix modem-manager[1230]: <info>  (ttyUSB0) serial
> port closed
> Feb  3 20:14:25 segulix dbus-daemon[1160]: modem-manager[1230]: <info>
> (ttyUSB0) serial port closed

The serial port status isn't exported over dbus, so the real fix here is
to make sure that ModemManager doesn't return from the Unlock method
until it's done, and that MM can handle a dial request coming in right
after that.  However, it wouldn't hurt NetworkManager to wait a second
or two after unlocking the modem too.

Dan