Hi, It seems the previous mail was rejected, so here it is with a zip for trace. Vincent
-----Message d'origine-----
De : Vincent ESCARGUEL
Envoyé : mardi 24 octobre 2023 15:53
À : Aleksander Morgado <aleksande...@chromium.org>
Cc : ModemManager (development) <modemmanager-devel@lists.freedesktop.org>
Objet : RE: EM9191 PCIe with CM4
Hi,
I've tried your solution but another error shows up:
root@NeptuLinkV3:~# mmcli -L
/org/freedesktop/ModemManager1/Modem/0 [generic] EM9191 root@NeptuLinkV3:~#
mmcli -m 0
----------------------------------
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 8754ef9f19884192804f905b3db0a74c6592c561
----------------------------------
Hardware | manufacturer: generic
| model: EM9191
| firmware revision: 02.08.01.00_GENERI_020.007_001
| carrier config: default
| h/w revision: EM9191
| supported: gsm-umts, lte, 5gnr
| current: gsm-umts, lte, 5gnr
| equipment id: 355890340276992
----------------------------------
System | device:
/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0
| physdev:
/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0
| drivers: mhi_net, mhi-pci-generic
| plugin: generic
| primary port: wwan0mbim0
| ports: mhi_hwip0 (net), wwan0mbim0 (mbim),
wwan0qcdm0 (ignored)
----------------------------------
Status | lock: sim-pin2
| unlock retries: sim-pin2 (3)
| state: disabled
| power state: on
----------------------------------
Modes | supported: allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 3g, 4g; preferred: 4g
| allowed: 3g, 4g; preferred: 3g
| allowed: 5g; preferred: none
| allowed: 4g, 5g; preferred: 5g
| allowed: 4g, 5g; preferred: 4g
| allowed: 3g, 5g; preferred: 5g
| allowed: 3g, 5g; preferred: 3g
| allowed: 3g, 4g, 5g; preferred: 5g
| allowed: 3g, 4g, 5g; preferred: 4g
| allowed: 3g, 4g, 5g; preferred: 3g
| current: allowed: 3g, 4g, 5g; preferred: 4g
----------------------------------
Bands | supported: utran-1, utran-3, utran-4, utran-6,
utran-5, utran-8,
| utran-9, utran-2, eutran-1, eutran-2,
eutran-3, eutran-4, eutran-5,
| eutran-7, eutran-8, eutran-12, eutran-13,
eutran-14, eutran-17,
| eutran-18, eutran-19, eutran-20,
eutran-25, eutran-26, eutran-28,
| eutran-29, eutran-30, eutran-32,
eutran-34, eutran-38, eutran-39,
| eutran-40, eutran-41, eutran-42,
eutran-46, eutran-48, eutran-66,
| eutran-71, utran-19, ngran-1, ngran-2,
ngran-3, ngran-5, ngran-28,
| ngran-41, ngran-66, ngran-71, ngran-77,
ngran-78, ngran-79
| current: utran-1, utran-3, utran-4, utran-6,
utran-5, utran-8,
| utran-9, utran-2, eutran-1, eutran-2,
eutran-3, eutran-4, eutran-5,
| eutran-7, eutran-8, eutran-12, eutran-13,
eutran-14, eutran-17,
| eutran-18, eutran-19, eutran-20,
eutran-25, eutran-26, eutran-28,
| eutran-29, eutran-30, eutran-32,
eutran-34, eutran-38, eutran-39,
| eutran-40, eutran-41, eutran-42,
eutran-46, eutran-48, eutran-66,
| eutran-71, utran-19, ngran-1, ngran-2,
ngran-3, ngran-5, ngran-28,
| ngran-41, ngran-66, ngran-71, ngran-77,
ngran-78, ngran-79
----------------------------------
IP | supported: ipv4, ipv6, ipv4v6
----------------------------------
3GPP | imei: 355890340276992
| enabled locks: sim, fixed-dialing
----------------------------------
3GPP EPS | initial bearer ip type: ipv4v6
----------------------------------
SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0
| sim slot paths: slot 1:
/org/freedesktop/ModemManager1/SIM/0 (active)
# mmcli -m 0 --simple-connect="apn=,multiplex=requested"
error: couldn't connect the modem:
'GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code0:
failed to create net link for device: failed to add link for device: Could not
allocate link: Failed to add link with mux id 1: Netlink message with
transaction 1 failed'
# logread -f
Wed Oct 18 13:28:22 2023 daemon.info [1962]: <inf> [modem0] processing user
request to connect modem...
Wed Oct 18 13:28:22 2023 daemon.info [1962]: <inf> [modem0] apn:
Wed Oct 18 13:28:22 2023 daemon.info [1962]: <inf> [modem0] allowed auth:
unknown
Wed Oct 18 13:28:22 2023 daemon.info [1962]: <inf> [modem0] multiplex:
requested
Wed Oct 18 13:28:22 2023 daemon.notice [1962]: <msg> [modem0] simple connect
started...
Wed Oct 18 13:28:22 2023 daemon.notice [1962]: <msg> [modem0] simple connect
state (6/10): register Wed Oct 18 13:28:22 2023 daemon.info [1962]: <inf>
[modem0] already registered automatically in network '20801', automatic
registration not launched...
Wed Oct 18 13:28:22 2023 daemon.notice [1962]: <msg> [modem0] simple connect
state (7/10): wait to get packet service state attached Wed Oct 18 13:28:22
2023 daemon.notice [1962]: <msg> [modem0] simple connect state (8/10): bearer
Wed Oct 18 13:28:22 2023 daemon.notice [1962]: <msg> [modem0] simple connect
state (9/10): connect Wed Oct 18 13:28:22 2023 daemon.notice [1962]: <msg>
[modem0] state changed (registered -> connecting) Wed Oct 18 13:28:22 2023
daemon.warn [1962]: <wrn> [modem0/bearer3] connection attempt #1 failed: failed
to create net link for device: failed to add link for device: Could not
allocate link: Failed to add link with mux id 1: Netlink message with
transaction 1 failed Wed Oct 18 13:28:22 2023 daemon.notice [1962]: <msg>
[modem0] state changed (connecting -> registered) Wed Oct 18 13:28:22 2023
daemon.notice [1962]: <msg> [modem0/bearer3] connection #1 finished: duration
0s Wed Oct 18 13:28:22 2023 daemon.warn [1962]: <wrn> [modem0] couldn't connect
bearer: failed to create net link for device: failed to add link for device:
Could not allocate link: Failed to add link with mux id 1: Netlink message with
transaction 1 failed
# service modemmanager stop
# vi /etc/rc.d/S70modemmanager ***change log level*** # service modemmanager
start *** trace in the 01 file *** # mmcli -m 0
--simple-connect="apn=,multiplex=requested" *** trace in the 02 file ***
successfully connected the modem
/// restart interface in LUCI \\\
*** trace in the 03 file ***
connection done, IP obtained but no answer to ping 8.8.8.8
/// Power cycle \\\ *** trace in the 04 file ***
Luci doesn't see the device, no way to make it restart:
Protocol: ModemManager
RX: 0 B (0 Pkts.)
TX: 0 B (0 Pkts.)
Error: Network device is not present
Does it help to understand what's happening?
Vincent
-----Message d'origine-----
De : Aleksander Morgado <aleksande...@chromium.org>
Envoyé : mardi 24 octobre 2023 11:46
À : Vincent ESCARGUEL <vincent.escarg...@mvg-world.com>
Cc : ModemManager (development) <modemmanager-devel@lists.freedesktop.org>
Objet : Re: EM9191 PCIe with CM4
Hey,
> I’m using a Sierra EM9191(sdx55) with PCIe on a raspberry CM4.
> Until now I had a firmware based on openWRT21.02, for which Aleksander had
> tuned the MM1.18.2 and few drivers.
> It worked nicely but we bought a new lot of CM4 and I need to upgrade few
> files for it to boot (start4.elf and fixup.dat).
> Upgrading the gpu-firmware package of the bcm2711 did the trick but it seems
> to have a side effect because the modem can’t connect properly anymore.
> For every new attempt (through luci) it attach, register and fail to connect,
> leaving the modem in a disabled state.
>
> My first move was to try the ‘official’ new openwrt, with latest update and
> better support to my hardware.
> I had the same result with openwrt 23.05/MM1.20.6 and openwrt
> master/MM1.22
>
> If I delete my interface in luci, then recreate it, sometimes it connects but
> there is no downlink traffic.
>
> When I try manually to establish the connection, I have this return:
> # mmcli -m 0 -e
> successfully enabled the modem.
> # mmcli -m 0 --simple-connect="apn="
> error: couldn't connect the modem:
> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot
> disable multiplex support'
>
> I managed to make the MHI driver handle the modem but I’m struggling with MM,
> anyone has a clue of what’s going on?
> If you need more information or trace, just let me know.
>
Could you try adding "multiplex=requested" to your --simple-connect call?
That "cannot disable multiplex support" error happens when we detect there is a
data aggregation protocol configured in the port. Could you post a full MM
debug log to try to understand where that comes from?
--
Aleksander
<<attachment: trace.zip>>
