<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 5, 2021 at 8:41 AM Andreas Hartmann <<a href="mailto:hartan@7x.de">hartan@7x.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
<br>
> 1. The SIM is sold by a "carrier" (or MNO or MVNO) and contains a<br>
> credential (the IMSI) that will have a prefix that corresponds to the<br>
> MCC/MNC. If you bought the new SIM from O2, then the modem should<br>
> register on O2.<br>
<br>
Thanks for clarifying. What would make a SIM (or mmcli) decide to try<br>
and register in another carriers network, then?<br></blockquote><div><br></div><div>If Roaming is enabled, the modem will check to see if it is able to roam on any other carriers. In your case the O2 network is marked as "forbidden" and so it seems that you don't have an O2 SIM ... or it's not active or something strange is going on.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> 2. Inserting the SIM *should* then show that the registration has<br>
> occurred with that carrier when you do the scan.<br>
<br>
Yep, I thought so. That's what pretty much every other PinePhone user<br>
I've talked to has reported to me.<br>
<br>
> 3. Each SIM/Carrier/MNO/MVNO has their own APN that you must<br>
> provide in most cases.<br>
<br>
I did do that. I've looked at various places in the internet, they all<br>
listed the exact same APN for O2 in this case. But it didn't work<br>
regardless.<br></blockquote><div><br></div><div>Have you tried the Vodafone APN since you seem to be connecting to Vodafone?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> There is a "AT Command<br>
> Tester" tool for Windows, and they provide a Quectel specific<br>
> version, if you want to experiment and learn.<br>
<br>
That's good to know, thanks. Unfortunately the modem is baked into an<br>
embedded device, and there's no way I will get it out of there or<br>
Windows running on that device. I was thinking of entirely killing the<br>
ModemManager before attempting to fiddle with AT commands.<br>
<br>
On a sidenote I decided to try some more mmcli options at my modem and<br>
I got the QMI call error again. Here's an excerpt from systemctl, note<br>
that I attempted to perform a simple connect using the O2 APN (which<br>
can be seen at the bottom of this output). Maybe anyone can read<br>
something from that? Should the "warning" related to the SIM card make<br>
me worry?<br></blockquote><div><br></div><div>At this point, you'd need a Modem Manager expert to reply. It does seem to say that it's not finding the SIM for some reason?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
```<br>
Jun 04 08:59:02 dhcp-10-132-126-186 ModemManager[6634]: <info> [base-<br>
manager] couldn't check support for device<br>
'/sys/devices/platform/soc/1c10000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:000<br>
1:1': not supported by any plugin<br>
Jun 04 08:59:08 dhcp-10-132-126-186 ModemManager[6634]: <info> [device<br>
/sys/devices/platform/soc/1c1b000.usb/usb5/5-1] creating modem with<br>
plugin 'quectel' and '6' ports<br>
Jun 04 08:59:08 dhcp-10-132-126-186 ModemManager[6634]: <warn> <br>
[plugin/quectel] could not grab port ttyUSB3: Cannot add port<br>
'tty/ttyUSB3', unhandled port type<br>
Jun 04 08:59:08 dhcp-10-132-126-186 ModemManager[6634]: <info> [base-<br>
manager] modem for device<br>
'/sys/devices/platform/soc/1c1b000.usb/usb5/5-1' successfully created<br>
Jun 04 08:59:08 dhcp-10-132-126-186 ModemManager[6634]: [/dev/cdc-wdm0]<br>
Opening device with flags 'version-info, proxy'...<br>
Jun 04 08:59:08 dhcp-10-132-126-186 ModemManager[6634]: [/dev/cdc-wdm0]<br>
created endpoint<br>
Jun 04 08:59:08 dhcp-10-132-126-186 ModemManager[6634]: [/dev/cdc-wdm0]<br>
Checking version info (25 retries)...<br>
Jun 04 08:59:08 dhcp-10-132-126-186 ModemManager[6634]: [/dev/cdc-wdm0]<br>
QMI Device supports 30 services:<br>
<br>
[ ... More outputs here ... ]<br></blockquote><div><br></div><div>There might be some real value in seeing what the "More outputs" are ... they might be valuable to see.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Jun 04 08:59:10 dhcp-10-132-126-186 ModemManager[6634]: <warn> <br>
[modem0] couldn't query SIM slots: QMI protocol error (94):<br>
'NotSupported'<br>
Jun 04 08:59:11 dhcp-10-132-126-186 ModemManager[6634]: <warn> <br>
[modem0] couldn't load supported assistance data types: LOC service:<br>
general failure<br>
Jun 04 08:59:11 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0] state changed (unknown -> disabled)<br>
Jun 04 08:59:11 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0] state changed (disabled -> enabling)<br>
Jun 04 08:59:11 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0] 3GPP registration state changed (unknown -> idle)<br>
Jun 04 08:59:12 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0] state changed (enabling -> enabled)<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0] simple connect started...<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0] simple connect state (4/8): wait to get fully enabled<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0] simple connect state (5/8): register<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0] simple connect state (6/8): bearer<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0] simple connect state (7/8): connect<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0] state changed (enabled -> connecting)<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: [/dev/cdc-wdm0]<br>
Allocating new client ID...<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: [/dev/cdc-wdm0]<br>
Registered 'wds' (version 1.67) client with ID '6'<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0/bearer0] couldn't start network: QMI protocol error (14):<br>
'CallFailed'<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0/bearer0] call end reason (3): generic-no-service<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0/bearer0] verbose call end reason (3,2001): [cm] no-service<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <warn> <br>
[modem0/bearer0] connection attempt #1 failed: QMI protocol error (14):<br>
'CallFailed'<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0] state changed (connecting -> enabled)<br>
Jun 04 08:59:39 dhcp-10-132-126-186 ModemManager[6634]: <info> <br>
[modem0/bearer0] connection #1 finished: duration 0s, tx: 0 bytes, rx<br>
:0 bytes<br>
<br>
```<br>
<br>
<br>
Thanks again!<br>
<br>
Andreas<br><br>
</blockquote></div></div>