> > 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?) -- Aleksander https://aleksander.es _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel