❦ 21 juillet 2019 22:11 +02, Aleksander Morgado :
>> > ModemManager[989]: Simple connect state (4/8): Wait to get fully
>> > enabled
>> > ModemManager[989]: Simple connect state (5/8): Register
>> > ModemManager[989]: Simple connect state (6/8): Bearer
>> > ModemManager[989]: Simple conn
❦ 20 juillet 2019 12:00 +02, Vincent Bernat :
> ModemManager[989]: Simple connect state (4/8): Wait to get fully
> enabled
> ModemManager[989]: Simple connect state (5/8): Register
> ModemManager[989]: Simple connect state (6/8): Bearer
> ModemManager[989]: Simple con
Hey!
I am getting the following error when trying to connect:
ModemManager[989]: Simple connect state (4/8): Wait to get fully enabled
ModemManager[989]: Simple connect state (5/8): Register
ModemManager[989]: Simple connect state (6/8): Bearer
ModemManager[989]: Simple connect state (7/8
❦ 16 août 2018 11:18 +0200, Aleksander Morgado :
If this modem is going to end up stuck with pure PPP and therefore maxing
out at 25Mbps, then I'm not too concerned anyways since its use is rather
limited. I just wish I could figure out how to switch this thing to MBIM
(Tried
❦ 13 août 2018 21:02 +0200, Aleksander Morgado :
>> If this modem is going to end up stuck with pure PPP and therefore maxing
>> out at 25Mbps, then I'm not too concerned anyways since its use is rather
>> limited. I just wish I could figure out how to switch this thing to MBIM
>> (Tried everythi
❦ 25 mars 2016 10:24 +0100, Aleksander Morgado :
>> My plan including free roaming in some countries. On my Android phone,
>> when I am under this condition, the phone doesn't display the "R" for
>> roaming. So, it seems to detect that I will not be charged. With modem
>> manager, there is no su
Hey!
My plan including free roaming in some countries. On my Android phone,
when I am under this condition, the phone doesn't display the "R" for
roaming. So, it seems to detect that I will not be charged. With modem
manager, there is no such distinction, I always get the "roaming"
mention.
I don
❦ 25 janvier 2016 19:37 +0100, Vincent Bernat :
>> I wonder if you might just have been "lucky" and hit some unrelated
>> network error? The closest defined codes are 17 - "Network failure" and
>> 22 - "Congestion".
>
> Maybe. I tried again
❦ 24 janvier 2016 22:38 +0100, Bjørn Mork :
> I wonder if you might just have been "lucky" and hit some unrelated
> network error? The closest defined codes are 17 - "Network failure" and
> 22 - "Congestion".
Maybe. I tried again this morning after a clean reboot and it did
connect immediately.
❦ 24 janvier 2016 22:19 +0100, Bjørn Mork :
>> I am being "denied" by 3GPP. What could be the cause? MCC and MNC are
>> correct.
>
> Sorry, I'm totallt lost here. AFAICS, you get the NwError code '19' here:
>
> 07:00:00:80:5C:00:00:00:00:00:00:00:01:00:00:00:00:00:00:00:A2:89:CC:33:BC:BB:8B:4F:
❦ 20 janvier 2016 09:58 +0100, Bjørn Mork :
> A firmware update will probably help on stability, but I don't think
> they've ever fixed the "wrong APN" bug I refer to above. Not that I've
> bothered reporting it either. Sierra doesn't want to support this modem
> directly (which I can understa
❦ 20 janvier 2016 09:58 +0100, Bjørn Mork :
> The other messages look pretty similar. As you point out: The only
> observable difference is the lack of DNS addresses. And a minor
> difference in the allocated addresses, which may or may not be related.
> You wouldn't happen to know if the oper
❦ 19 janvier 2016 23:59 +0100, Aleksander Morgado :
> Would be interesting to see what ModemManager says in each of those
> tries (--debug); and check which are the IP details given by the modem
> for each case, before we even try to run the DHCP client. Could you
> gather logs for both situatio
Hey!
I got an odd problem since some time.
Bus 002 Device 045: ID 1199:a001 Sierra Wireless, Inc.
ii modemmanager 1.4.12-1 amd64 D-Bus service for managing
modems
Linux zoro 4.3.0-1-amd64 #1 SMP Debian 4.3.3-5 (2016-01-04) x86_64 GNU/Linux
When I am connected over LTE for the
❦ 7 juin 2015 00:12 +0200, Aleksander Morgado :
> When the modem is detected it always goes into disabled state.
>
> You can then manually enable the modem with mmcli --enable or
> otherwise use NetworkManager to just launch a connection attempt, that
> will also trigger the modem enabling.
Oh
Hey!
I didn't use ModemManager since quite some time (since March?). I am now
running those versions:
Linux zoro 4.0.0-1-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 GNU/Linux
ii modemmanager 1.4.8-1 amd64D-Bus service for
managing modems
ii libmbim-glib4:amd6
16 matches
Mail list logo