Just noticed that I did not reply to the list... Next try...
On Thu, Sep 7, 2023 at 10:46 AM Bjørn Mork <bj...@mork.no> wrote:
> Nice! And I assume you have some ideas on how to compute the sha256
> hash? Blind guessing would be very hard....
>
I hope so (keeping fingers crossed) ;-)
> > Is there a way to try this procedure through mbimcli? I am currently
> > running libmbim 1.28.4-1.
>
> I guess you need the "Intel Mutual Authentication" service for that,
> which looks like it will be in libmbim 1.30
>
> I.e. you need to build a current development version of libmbim to test
> it for now.
>
I built the current dev version and applied a Linux kernel patch [1] on top
of 6.5.2 that is supposed to improve handling for the FM350-GL's T7xx
chipset, but I am still seeing pretty unreliable behavior communicating
with the modem:
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
FCC lock status: locked
Challenge: 0
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
[10 Sep 2023, 20:23:35] -Warning ** [/dev/wwan0mbim0] error reading from
the IOChannel: 'Input/output error'
error: operation failed: Transaction timed out
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
FCC lock status: locked
Challenge: 0
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
FCC lock status: locked
Challenge: 0
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
FCC lock status: locked
Challenge: 0
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
FCC lock status: locked
Challenge: 0
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
FCC lock status: locked
Challenge: 0
error: couldn't close device: Transaction timed out
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
FCC lock status: locked
Challenge: 0
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
FCC lock status: locked
Challenge: 0
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
error: operation failed: Transaction timed out
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
FCC lock status: locked
Challenge: 0
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
[10 Sep 2023, 20:36:39] -Warning ** [/dev/wwan0mbim0] error reading from
the IOChannel: 'Input/output error'
error: operation failed: Transaction timed out
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
error: operation failed: Transaction timed out
error: couldn't close device: Transaction timed out
$ sudo mbimcli -d /dev/wwan0mbim0 --query-fcc-lock
error: operation failed: Transaction timed out
dmesg error log (for some of the above errors):
[ 8012.377611] mtk_t7xx 0000:08:00.0: Port AT is not opened, drop packets
[ 8012.377632] mtk_t7xx 0000:08:00.0: Port AT is not opened, drop packets
[ 8012.390960] mtk_t7xx 0000:08:00.0: Port AT is not opened, drop packets
[ 8012.409126] mtk_t7xx 0000:08:00.0: Port AT is not opened, drop packets
[ 8257.303095] mtk_t7xx 0000:08:00.0: Port AT is not opened, drop packets
[ 8257.313695] mtk_t7xx 0000:08:00.0: Port AT is not opened, drop packets
[ 8265.620529] mtk_t7xx 0000:08:00.0: Port AT is not opened, drop packets
[ 8265.622356] mtk_t7xx 0000:08:00.0: Port AT is not opened, drop packets
By coincidence I spotted [2]. Could that be related? Both modems are
manufactured by Fibocom.
Regards,
Thilo
P.S.: The challenge always being zero is also somewhat suspicious - I
haven't been able to perform a successful unlock so far.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/patch/?id=ba2274dcfda859b8a27193e68ad37bfe4da28ddc
[2]
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/184
