AW: AW: SIM PIN unlock timeout

[Dominik Nille]

Hey,
thank you very much for your reply.

I was not expecting that type of behavior. I did only connect one modem, so I was expecting the "any" keyword to work.
I am wondering why ModemManager lists two different Modems.

I tried it again and "mmcli -m any" lists the modem as modem0 and SIM0 before sending the command.

When I send the command "mmcli -i any --pin=<SIM-PIN>", the timeout will be reached.
Afterwards, the same modem will be listed as Modem1 with Sim1.

Result of "lsusb":
Bus 002 Device 003: ID 2c7c:0801 Quectel Wireless Solutions Co., Ltd. RM520N-GL

Result of "mmcli --list-modems"
/org/freedesktop/ModemManager1/Modem/1 [Quectel] RM520N-GL

"mmcli -m any" lists also only one modem.

These outputs do not match the information of a second modem being connected.

Are you able to explain the behavior?

Thank you very much!

Best regards,
Dominik


-----Ursprüngliche Nachricht-----
Von: Dan Williams <dan at ioncontrol.co> 
Gesendet: Mittwoch, 19. Februar 2025 19:36
An: Dominik Nille <Dominik.Nille at balluff.de>; Aleksander Morgado <aleksandermj at chromium.org>
Cc: modemmanager-devel at lists.freedesktop.org
Betreff: Re: AW: SIM PIN unlock timeout

[Sie erhalten nicht häufig E-Mails von dan at ioncontrol.co. Weitere Informationen, warum dies wichtig ist, finden Sie unter https://aka.ms/LearnAboutSenderIdentification ]

On Mon, 2025-01-20 at 14:34 +0000, Dominik Nille wrote:
>
>
>
> Hey Aleksander, hey Dan,
>
> I ran the ModemManager with debug logs and produced the same behavior 
> as in the previous mail again.
>
> Maybe, you can gain some knowledge from the debug log I attached.
>
> Any ideas, why the command keeps failing, but after waiting a little 
> the state changes from “locked” to “registered”?

Looks like you've got two modems on the system, and the other one
(modem0) isn't happy:

ModemManager[4639]: <debug> [1737381559.914951] [modem0] couldn't check if unlock required: Couldn't peek QMI port
ModemManager[4639]: <debug> [1737381559.915068] [modem0] retrying (22) unlock required check

so what happens is that modem1 gets unlocked just fine, but because you sent "-i any" MM will try to unlock both modems, and the other one times out.

We could debug why modem0 isn't happy, or alternatively you could send the PIN to modem1's SIM and it shouldn't take long.

Dan

>
> BR
> Dominik
>
>
>
> Von: Aleksander Morgado <aleksandermj at chromium.org>
> Gesendet: Mittwoch, 11. Dezember 2024 09:46
> An: Dominik Nille <Dominik.Nille at balluff.de>
> Cc: modemmanager-devel at lists.freedesktop.org
> Betreff: Re: SIM PIN unlock timeout
>
>
>
>
>
> Hey Dominik,
>
>
>
>
>
> >
> >
> >
> >
> >
> >
> > I am currently trying to unlock myQuectel RM520N-GL on Linux Debian 
> > with the ModemManager (Version1.20.4).
> >
> > mmcli -i any --pin=<SIMPIN>
> > > > error: couldn't send PIN code to the SIM: 'Timeout was reached'
> >
> > Runs into atimeout and still manages to unlock the SIM-Card.
> > Afterwards the state changes from “locked” to “registered”.
> >
>
>
>
>
>
>
> Please run MM with debug logs (use "mmcli -G DEBUG" or 
> followhttps://modemmanager.org/docs/modemmanager/debugging/), as that 
> will give us much more information about the specific sequence in 
> place here.
>
>
>
> --
>
>
>
>
>
>
> Aleksander
>
>
> Dominik Nille
> Technology
> Innovation Management
>
>
>
>
> Balluff GmbH · Schurwaldstrasse 9 · 73765 Neuhausen a.d.F. · Germany 
> Phone +497158173-8020 · Fax +4971585010 · Dominik.Nille at balluff.de · 
> www.balluff.com
>
> Facebook
> LinkedIn
> Twitter
> Youtube
> Xing
> Blog
>
>
> Place of incorporation/Sitz der Gesellschaft: Neuhausen a.d.F., 
> Germany · Register court/Registergericht: Amtsgericht Stuttgart, 
> Germany Trade register/Handelsregister: HRB 214038 · Managing
> directors/Geschäftsführer: Katrin Stegmaier-Hermle, Florian Hermle, 
> Frank Nonnenmann Chairman board of directors/Vorsitzender des 
> Aufsichtsrats: Michael Unger · VAT ID/USt-ID: DE213 402 337
>
>
>