ModemManager 1.14.2 Setup - undefined symbol error and/or 'libmbim-glib.la' was moved error

Dani Anderson dani.anderson at strath.ac.uk
Thu Oct 22 17:14:01 UTC 2020


Hey Aleksander,

>I would be very surprised if this issue was due to changes in the kernel driver. Are you able to post those qmi_wwan driver changes somewhere to review? Or, could you ask the manufacturer to do so?

I can ask for permission to share these. Not sure what the status is.

> MM git master has additional changes 5G related, but I believe everything should work as expected in MM 1.14 as long as you're using the modem in QMI mode. I would first validate that; i.e. what's the output of "mmcli -m 0"?

I believe we did the ./configure with --with-qmi=yes
I'll need to verify this, and will let you know. 

>And then, I would probably go on and either enable debug logging in MM (launching the daemon manually with --debug or otherwise running mmcli -G DEBUG to change the level on runtime"), and see what QMI messages are being transferred between the module and MM.

We'll definitely need to repeat some steps debugging with ModemManager. 
We're keen to get to the stage where this functionality is as "plug and play" as using LTE. 

> Also, is this 5G NSA or 5G SA? There are some reports about 5G SA IIRC,
This is currently in SA mode. We have the option to do NSA mode as well.


To start our initial debugging, we disabled both NetworkManager and ModemManager.
Then actually started based on instructions from this Techship Link 
(https://techship.com/faq/how-to-step-by-step-set-up-a-data-connection-over-qmi-interface-using-qmicli-and-in-kernel-driver-qmi-wwan-in-linux/)

Effectively:

ip link set dev wwan0 down
echo Y > /sys/class/net/wwan0/qmi/raw_ip
ip link set dev wwan0 up
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --wds-start-network="ip-type=4,apn=<apn_name>" --client-no-release-cid
udhcpc -q -f -n -i wwan0

Which (honestly, to our surprise) established the link.
We were allocated an IP address and could ping between gNB and UE.


With the connection established (with NM and MM still disabled), running 

sudo qmicli --device=/dev/cdc-wdm0 --nas-get-system-info

returns

[/dev/cdc-wdm0] Successfully got system info:
	WCDMA service:
		Status: 'none'
		True Status: 'none'
		Preferred data path: 'no'
	LTE service:
		Status: 'none'
		True Status: 'none'
		Preferred data path: 'no'
		Registration restriction: 'unrestricted'
	SIM reject info: 'available

And running:

sudo qmicli -p --device=/dev/cdc-wdm0 --nas-get-signal-info

[/dev/cdc-wdm0] Successfully got signal info
5G:
	RSRP: '-52 dBm'
	SNR: '35.0 dB'
	RSRQ: '-11 dB'

Obviously it seems strange that system-info doesn't give any details regarding 5G capability, while signal-info is returning details on an active 5G connection...
I would suspect this is also why MM does not report 5gnr capability?

I don't have a great deal of experience working with qmicli.
We should be able to replicate this connection now, so any commands you can suggest (or any advice in general) to help debug our MM set-up are appreciated.

Will repeat some processes in the lab soon using the debug mode to validate.

Thank-you for your help in getting us to this stage.

Kind regards,

Dani Anderson
University of Strathclyde

-----Original Message-----
From: Aleksander Morgado <aleksander at aleksander.es> 
Sent: 22 October 2020 16:26
To: Dani Anderson <dani.anderson at strath.ac.uk>
Cc: modemmanager-devel at lists.freedesktop.org; Douglas Allan <d.allan at strath.ac.uk>
Subject: Re: ModemManager 1.14.2 Setup - undefined symbol error and/or 'libmbim-glib.la' was moved error

Hey,

> Thank-you for your advice. We've managed to install version 1.14.2 with no further issues following the steps you outlined.
>
> Unfortunately, when using the software, we didn't quite get the result that we were hoping for - our modem reported capability is still only shown as being 4g when we would expect/hope to see 5gnr.
> We're working with the SIMCOM8200-M2 unit 
> (https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
> .simcom.com%2Fproduct%2FSIM8200-M2_series.html&data=04%7C01%7Cdani
> .anderson%40strath.ac.uk%7Ca1f23cbf39df46b2015d08d8769ed685%7C631e0763
> 153347eba5cd0457bee5944e%7C0%7C0%7C637389771858349751%7CUnknown%7CTWFp
> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn
> 0%3D%7C1000&sdata=cvl5bJWfX8UYD53VjlQGYSiLyT0nf82uRPPOuHUBW40%3D&a
> mp;reserved=0)
>
> We think this issue might be related to the qmi driver rather than a problem with ModemManager.
>
> We received a qmi_wwan driver for the module from the manufacturer that we haven't installed yet.

I would be very surprised if this issue was due to changes in the kernel driver. Are you able to post those qmi_wwan driver changes somewhere to review? Or, could you ask the manufacturer to do so?

> We didn't need to do this update when doing operations in LTE (which was using MM 1.12.8) as everything was happy with the default drivers.
>
> We have a functioning gNB in our lab, which the modem will connect to (verified by the gNB / 5GPC and the modem using AT Commands) but we can't "share" this connectivity with the compute platform connected to the modem.
>
> Is there anything that you could maybe suggest to address this?

MM git master has additional changes 5G related, but I believe everything should work as expected in MM 1.14 as long as you're using the modem in QMI mode. I would first validate that; i.e. what's the output of "mmcli -m 0"?

And then, I would probably go on and either enable debug logging in MM (launching the daemon manually with --debug or otherwise running mmcli -G DEBUG to change the level on runtime"), and see what QMI messages are being transferred between the module and MM.

You could also try running qmicli NAS operations like qmicli --nas-get-system-info and --nas-get-signal-info and such.

Also, is this 5G NSA or 5G SA? There are some reports about 5G SA IIRC, e.g. https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fmobile-broadband%2FModemManager%2F-%2Fissues%2F256&data=04%7C01%7Cdani.anderson%40strath.ac.uk%7Ca1f23cbf39df46b2015d08d8769ed685%7C631e0763153347eba5cd0457bee5944e%7C0%7C0%7C637389771858349751%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=muNRlYySr3lFiTNWEgQQ7e7RCWDuAEr7ZWHQM2jbGhc%3D&reserved=0


--
Aleksander
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Faleksander.es%2F&data=04%7C01%7Cdani.anderson%40strath.ac.uk%7Ca1f23cbf39df46b2015d08d8769ed685%7C631e0763153347eba5cd0457bee5944e%7C0%7C0%7C637389771858349751%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zQ3f5ELMtqK1%2FeT%2FZryYpU809ZMJtcvcfoz%2B%2Fw%2FLaf8%3D&reserved=0


More information about the ModemManager-devel mailing list