Re: Problems with gobi 4000 connecting via QMI

[Dan Williams <dcbw redhat com>]

On Tue, 2016-02-09 at 05:57 +0100, Harald Jung wrote:
> yeah, its the vodafone apn i always use in my tests.
> It was running for weeks inside an arm based router with the same 
> settings, before i took it back.
> The SIM has a PIN and was succesfully unlocked.

How long is it between when the PIN unlocks and the connection attempt
occurs?

Also, any chance you can connect to the AT port with minicom and run
"AT+CGDCONT?" for me?

Dan

> Harald
>
> Am 08.02.2016 um 17:32 schrieb Dan Williams:
> > On Mon, 2016-02-08 at 14:51 +0100, Harald Jung wrote:
> > > Hi,
> > >
> > > finally the notebook was sent to me and i have the same problems.
> > > I use a SIM which has been succesfully used in other notebooks.
> > > The problem is still the same:
> > Are you 100% sure the APN used is correct?
> >
> > Also, does the SIM have a PIN enabled?  I seem to recall some
> > reports
> > that connections right after unblocking the SIM PIN fail, but
> > waiting a
> > bit makes things work.
> >
> > Dan
> >
> > > Feb  8 14:52:40 ThinClient NetworkManager[2243]: <info> keyfile:
> > > add
> > > connection /etc/NetworkManager/system-connections/1&1 Mobile
> > > Broadband
> > > (c29aa52c-56fa-47cd-b0b4-b44b00175d29,"1&1 Mobile Broadband")
> > > Feb  8 14:52:40 ThinClient NetworkManager[2243]: <info> (cdc
> > > -wdm0):
> > > Activation: starting connection '1&1 Mobile Broadband'
> > > (c29aa52c-56fa-47cd-b0b4-b44b00175d29)
> > > Feb  8 14:52:40 ThinClient NetworkManager[2243]: <info> (cdc
> > > -wdm0):
> > > device state change: disconnected -> prepare (reason 'none') [30
> > > 40
> > > 0]
> > > Feb  8 14:52:40 ThinClient NetworkManager[2243]: <info>
> > > NetworkManager
> > > state is now CONNECTING
> > > Feb  8 14:52:40 ThinClient ModemManager[2146]: <info> Simple
> > > connect
> > > started...
> > > Feb  8 14:52:40 ThinClient ModemManager[2146]: <info> Simple
> > > connect
> > > state (4/8): Wait to get fully enabled
> > > Feb  8 14:52:40 ThinClient ModemManager[2146]: <info> Simple
> > > connect
> > > state (5/8): Register
> > > Feb  8 14:52:40 ThinClient ModemManager[2146]: <info> Simple
> > > connect
> > > state (6/8): Bearer
> > > Feb  8 14:52:40 ThinClient ModemManager[2146]: <info> Simple
> > > connect
> > > state (7/8): Connect
> > > Feb  8 14:52:40 ThinClient ModemManager[2146]: <info>  Modem
> > > /org/freedesktop/ModemManager1/Modem/0: state changed (registered
> > > ->
> > > connecting)
> > > Feb  8 14:52:40 ThinClient ModemManager[2146]: [/dev/cdc-wdm0]
> > > Allocating new client ID...
> > > Feb  8 14:52:40 ThinClient NetworkManager[2243]: <info> (cdc
> > > -wdm0):
> > > modem state changed, 'registered' --> 'connecting' (reason: user
> > > -requested)
> > > Feb  8 14:52:40 ThinClient ModemManager[2146]: [/dev/cdc-wdm0]
> > > Registered 'wds' (version 1.23) client with ID '1'
> > > Feb  8 14:52:43 ThinClient ModemManager[2146]: <info> error:
> > > couldn't
> > > get current settings: QMI protocol error (15): 'OutOfCall'
> > > Feb  8 14:52:43 ThinClient ModemManager[2146]: [/dev/cdc-wdm0]
> > > Allocating new client ID...
> > > Feb  8 14:52:43 ThinClient ModemManager[2146]: [/dev/cdc-wdm0]
> > > Registered 'wds' (version 1.23) client with ID '2'
> > > Feb  8 14:52:43 ThinClient ModemManager[2146]: <info> error:
> > > couldn't
> > > start network: QMI protocol error (64): '(null)'
> > > Feb  8 14:52:43 ThinClient ModemManager[2146]: <info>  Modem
> > > /org/freedesktop/ModemManager1/Modem/0: state changed (connecting
> > > ->
> > > connected)
> > > Feb  8 14:52:43 ThinClient ModemManager[2146]: <info> Simple
> > > connect
> > > state (8/8): All done
> > > Feb  8 14:52:43 ThinClient NetworkManager[2243]: <info> (cdc
> > > -wdm0):
> > > modem state changed, 'connecting' --> 'connected' (reason: user
> > > -requested)
> > > Feb  8 14:52:43 ThinClient NetworkManager[2243]: <warn> (cdc
> > > -wdm0):
> > > failed to connect modem: invalid bearer IP configuration
> > > Feb  8 14:52:43 ThinClient NetworkManager[2243]: <info> (cdc
> > > -wdm0):
> > > device state change: prepare -> failed (reason 'config-failed')
> > > [40
> > > 120 4]
> > > Feb  8 14:52:43 ThinClient NetworkManager[2243]: <info>
> > > NetworkManager
> > > state is now DISCONNECTED
> > > Feb  8 14:52:43 ThinClient NetworkManager[2243]: <warn> (cdc
> > > -wdm0):
> > > Activation: failed for connection '1&1 Mobile Broadband'
> > > Feb  8 14:52:43 ThinClient ModemManager[2146]: <info>  Modem
> > > /org/freedesktop/ModemManager1/Modem/0: state changed (connected 
> > > ->
> > > disconnecting)
> > > Feb  8 14:52:43 ThinClient NetworkManager[2243]: <info> (cdc
> > > -wdm0):
> > > device state change: failed -> disconnected (reason 'none') [120
> > > 30
> > > 0]
> > > Feb  8 14:52:43 ThinClient NetworkManager[2243]: <info> (cdc
> > > -wdm0):
> > > modem state changed, 'connected' --> 'disconnecting' (reason:
> > > user-requested)
> > > Feb  8 14:52:44 ThinClient ModemManager[2146]: <info>  Modem
> > > /org/freedesktop/ModemManager1/Modem/0: state changed
> > > (disconnecting
> > > ->
> > > registered)
> > > Feb  8 14:52:44 ThinClient NetworkManager[2243]: <info> (cdc
> > > -wdm0):
> > > modem state changed, 'disconnecting' --> 'registered' (reason:
> > > user-requested
> > >
> > >
> > > regards Harald
> > >
> > >
> > > Am 20.01.2016 um 13:46 schrieb Harald Jung:
> > > > Hi,
> > > >
> > > > when another SIM is used, the messages are  "user request" oder
> > > > "none", nm-applet gives a messages
> > > > Creating object path
> > > > '/org/freedesktop/NetworkManager/ActiveConnection/1" failed in
> > > > nm
> > > > -glib.
> > > > But I have no logfile from that test.
> > > > Anyway the connection was tried with the installed Windows and
> > > > it
> > > > worked with any SIM.
> > > >
> > > >
> > > > Harald
> > > >
> > > > Am 06.01.2016 um 17:14 schrieb Dan Williams:
> > > > > On Wed, 2016-01-06 at 17:11 +0100, Harald Jung wrote:
> > > > > > Hi Dan,
> > > > > >
> > > > > > yeah the sim was tested with a mobile phone and in another
> > > > > > notebook.
> > > > > > The SIM also works from the windows installation on the
> > > > > > notebook.
> > > > > > ModemManager is version 1.4.10
> > > > > Do other SIMs work in the same modem?
> > > > >
> > > > > Dan
> > > > >
> > > > > > Harald
> > > > > >
> > > > > > Am 06.01.2016 um 16:57 schrieb Dan Williams:
> > > > > > > On Wed, 2016-01-06 at 16:01 +0100, Harald Jung wrote:
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > the "HP lt4112 Gobi 4G Module" can't establish a
> > > > > > > > network
> > > > > > > > connection.
> > > > > > > > The device is recognozied by the system, but the IP
> > > > > > > > connection
> > > > > > > > fails.
> > > > > > > >
> > > > > > > > Details and logs can be found here:
> > > > > > > > http://www.hjit.de/lt4112.txt
> > > > > > > What version of ModemManager?  I see a ModemManager
> > > > > > > errors
> > > > > > > there
> > > > > > > (like
> > > > > > > "ModemManager[2018]: (mm-broadband-modem
> > > > > > > -qmi.c:1238):dms_get_ids_ready:
> > > > > > > code should not be reached")  but those are recovered.
> > > > > > >
> > > > > > > In any case, your SIM is not provisioned for the
> > > > > > > operator:
> > > > > > > 'Couldn't
> > > > > > > get MSISDN: QMI protocol error (16): 'NotProvisioned''
> > > > > > >
> > > > > > > Does the SIM work in a different device?
> > > > > > >
> > > > > > > Dan
> > > > > > > _______________________________________________
> > > > > > > ModemManager-devel mailing list
> > > > > > > ModemManager-devel lists freedesktop org
> > > > > > > http://lists.freedesktop.org/mailman/listinfo/modemmanage
> > > > > > > r-de
> > > > > > > vel
> > > > > !DSPAM:416,568d3d6423792141272438!
> > > > _______________________________________________
> > > > networkmanager-list mailing list
> > > > networkmanager-list gnome org
> > > > https://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > >
> > > > !DSPAM:416,569f83bd19411175919390!