Snapdragon X55 (Thinkpad X1 Nano w/5G Modem)
Oskar Stenman
oskar at cetex.se
Thu May 20 13:30:28 UTC 2021
Hi!
I've tested it. ModemManager doesn't automatically activate it, hence the
relatively large ModemManager log (NetworkManager is spamming
activations).. But activating with qmicli works (although now with the new
command).
$ qmicli -p -d /dev/wwan0p2MBIM --device-open-mbim
--dms-foxconn-set-fcc-authentication=00
[20 May 2021, 15:22:51] -Warning ** [/dev/wwan0p2MBIM] couldn't detect
transport type of port: couldn't detect device driver
[20 May 2021, 15:22:51] -Warning ** [/dev/wwan0p2MBIM] requested MBIM mode
but unexpected transport type found
[/dev/wwan0p2MBIM] Successfully run Foxconn FCC authentication
I didn't check version before recompiling, but the binary is reporting as
1.17.1.
$ ModemManager --version
ModemManager 1.17.1
...
oskar at oskar-ThinkPad-X1-Nano-Gen-1:~$ which ModemManager
/usr/local/sbin/ModemManager
oskar at oskar-ThinkPad-X1-Nano-Gen-1:~$ ls -la /usr/local/sbin/ModemManager
-rwxr-xr-x 1 root root 7781472 May 20 14:55 /usr/local/sbin/ModemManager
oskar at oskar-ThinkPad-X1-Nano-Gen-1:~$ ps axu | grep ModemManager
root 1081 0.3 0.0 317800 15356 ? Ssl 15:22 0:01
/usr/local/sbin/ModemManager --log-level DEBUG
So seems like the correct / newest version is running.
/Oskar Stenman
On Wed, 19 May 2021 at 15:49, Aleksander Morgado <aleksander at aleksander.es>
wrote:
> Hey Oskar
>
> On Wed, May 12, 2021 at 9:38 AM Aleksander Morgado
> <aleksander at aleksander.es> wrote:
> >
> > > > After that i could run:
> > > > $ sudo qmicli -p -d /dev/wwan0p2MBIM --device-open-mbim
> > > > --dms-dell-cuskit-unlock=00
> > > > [11 maj 2021, 23:42:36] -Warning ** [/dev/wwan0p2MBIM] couldn't
> detect
> > > > transport type of port: couldn't detect device driver
> > > > [11 maj 2021, 23:42:36] -Warning ** [/dev/wwan0p2MBIM] requested
> MBIM mode
> > > > but unexpected transport type found
> > > > [/dev/wwan0p2MBIM] Successfully run Dell cuskit unlock
> > > >
> > > > I've attached the log from ModemManager and i can see a ton of stuff
> > > > happening after i send that command with cuskit,
> > >
> > >
> > > Coool! So that actually worked. Have to talk to my boss about getting
> > > a new laptop, then :-)
> > >
> > >
> > > Not sure why you get those QMI indications, but anyway - this is good:
> > >
> > >
> <<<<<< QMUX:
> > >
> <<<<<< length = 43
> > >
> <<<<<< flags = 0x80
> > >
> <<<<<< service = "nas"
> > >
> <<<<<< client = 4
> > >
> <<<<<< QMI:
> > >
> <<<<<< flags = "indication"
> > >
> <<<<<< transaction = 11
> > >
> <<<<<< tlv_length = 31
> > >
> <<<<<< message = "Serving System" (0x0024)
> > >
> <<<<<< TLV:
> > >
> <<<<<< type = "Serving System" (0x01)
> > >
> <<<<<< length = 6
> > >
> <<<<<< value = 01:01:01:02:01:08
> > >
> <<<<<< translated = [ registration_state = 'registered' cs_attach_state =
> 'attached' ps_attach_state = 'attached' selected_network = '3gpp'
> radio_interfaces = '{ [0] = 'lte '}' ]
> > >
> > >
> >
> > Hahaha! :D That was a truly truly long shot. RF is now on, hopefully
> > the connection will go on without issues as well.
> >
> > Time to add built-in support for this in libqmi+MM, maybe naming the
> > message differently (foxconn fcc unlock?)
> >
>
> Completely untested; could you give libqmi git master plus this
> ModemManager branch a try?
>
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534
> If you could gather debug logs it would be great.
>
> --
> Aleksander
> https://aleksander.es
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20210520/b69a47f5/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ModemManager.log.gz
Type: application/gzip
Size: 310198 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20210520/b69a47f5/attachment-0001.gz>
More information about the ModemManager-devel
mailing list