Re: HP lt4120 failing to make single-stack connections on LTE using MM
On Fri, 2018-09-07 at 09:26 +0200, Bjørn Mork wrote: > Dan Williams writes: > > > Not sure this does exactly what we want though, as the Telit xN930 > > documentation for CID_MODEM_REBOOT says: > > > > "This command reboots the device into firmware update mode. After > > the > > command is sent the device shuts down and reboots in firmware > > update > > mode." > > Ah, didn't know that. Thanks. No, that's definitely not something > we'd > want for a normal "reset" operation. > > There's one of the problems trying to figure out stuff by observing > behaviour: It's easy to miss important details. I am pretty sure my > modem rebooted and ended up running the already installed application > firmware. But I might have missed a delay where it waited for > firmware > update. And that timeout could very well be specific to the > vendor/modem/firmware, so it's not something to depend on But it might be useful to use CID_MODEM_REBOOT on a case-by-case basis where we know it'll just restart into the existing firmware. I didn't mean to say we *shouldn't* use it, just that we should be careful :) Dan > And I had completely forgotten about the xN930 docs, which I see that > I > also have. Should read more of that and less of my own experimental > notes ;-) > > > > Bjørn > ___ > ModemManager-devel mailing list > ModemManager-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
Dan Williams writes: > Not sure this does exactly what we want though, as the Telit xN930 > documentation for CID_MODEM_REBOOT says: > > "This command reboots the device into firmware update mode. After the > command is sent the device shuts down and reboots in firmware update > mode." Ah, didn't know that. Thanks. No, that's definitely not something we'd want for a normal "reset" operation. There's one of the problems trying to figure out stuff by observing behaviour: It's easy to miss important details. I am pretty sure my modem rebooted and ended up running the already installed application firmware. But I might have missed a delay where it waited for firmware update. And that timeout could very well be specific to the vendor/modem/firmware, so it's not something to depend on And I had completely forgotten about the xN930 docs, which I see that I also have. Should read more of that and less of my own experimental notes ;-) Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
On Thu, 2018-09-06 at 11:02 +0200, Aleksander Morgado wrote: > On Thu, Sep 6, 2018 at 10:46 AM, Bjørn Mork wrote: > > Aleksander Morgado writes: > > > > > Oh wait, this is a Intel based MBIM modem, right? If so, we need > > > AT-based reset operations. I believe I still have the HPlt4120 > > > around > > > here, will try to implement that. Tracking it here: > > > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issu > > > es/86 > > > > Don't know if we've discussed this before, but based on testing > > with the > > EM7345 and looking at the Windows stuff, I believe it supports a > > vendor > > MBIM service usable for reset: > > > > UUID_FWUSVC => UNKNOWN (0ed374cb-f835-4474-bc11-3b3fd76f5641) > > DssPayload: 0x > > MaxDssInstances:0 > > CidCount: 1 > > CidList:1 > >CID_MODEM_REBOOT(1) > > > > > > My notes are a bit sketchy as always, and the modem is stowed away, > > but > > I believe that was the only CID of that service and that it only > > supported SET requests. With immediate modem reset as a result. > > > > Ah, even better, thanks for the pointer :) > https://gitlab.freedesktop.org/mobile-broadband/libmbim/issues/3 Not sure this does exactly what we want though, as the Telit xN930 documentation for CID_MODEM_REBOOT says: "This command reboots the device into firmware update mode. After the command is sent the device shuts down and reboots in firmware update mode." Dan ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
Aleksander Morgado writes: > On Thu, Sep 6, 2018 at 11:29 AM, Tore Anderson wrote: >> * Aleksander Morgado >> >>> Oh wait, this is a Intel based MBIM modem, right? If so, we need >>> AT-based reset operations. I believe I still have the HPlt4120 around >>> here, will try to implement that. Tracking it here: >>> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/86 >> >> I don't really know, to be honest. I'm using qmicli to manage it and that >> works (including «--dms-set-operating-mode=foo»). ModemManager says it's >> MBIM, however. Is MBIM/QMI an either/or thing? It seems to me that this >> modem is both. >> >> - >> Hardware | manufacturer: 'HP' >>| model: 'MBIM [03F0:9D1D]' >>| revision: 'T77W595.F0.0.0.6.6.GC.029' >>| H/W revision: 'HP lt4120 Snapdragon X5 LTE' >>| supported: 'gsm-umts, lte' >>|current: 'gsm-umts, lte' >>| equipment id: '358894065774253' >> - >> System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-3' >>|drivers: 'cdc_mbim' >>| plugin: 'Generic' >>| primary port: 'cdc-wdm0' >>| ports: 'cdc-wdm0 (mbim), wwp0s20f0u3c3 (net)' >> - >> > > Ok, then no, this is not Intel based, it's Qualcomm based. And now > that I recall, this is the one for which the firmware upgrade is done > using PDC service. > It is indeed doing QMI over MBIM, if you're using qmicli nicely. I now > wonder why the reset operation didn't work for you. It doesn't work for me either, if that helps ;-) bjorn@miraculix:~$ mmcli -m 34 /org/freedesktop/ModemManager1/Modem/34 (device id '2044c6a3d2d068ca9f96e9bbc50c30b56e90ee91') - Hardware | manufacturer: 'Sierra Wireless, Incorporated' | model: 'MBIM [1199:9079]' | revision: 'SWI9X30C_02.24.05.06' | H/W revision: 'EM7455' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '01458200078' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-2' |drivers: 'cdc_mbim, qcserial' | plugin: 'Sierra' | primary port: 'cdc-wdm0' | ports: 'ttyUSB0 (qcdm), ttyUSB1 (unknown), ttyUSB2 (at), cdc-wdm0 (mbim), wwan0 (net)' - Numbers | own : 'unknown' - Status | lock: 'none' | unlock retries: 'sim-puk2 (10)' | state: 'connected' |power state: 'on' |access tech: 'lte' | signal quality: '32' (cached) - Modes| supported: 'allowed: 3g, 4g; preferred: none' |current: 'allowed: 3g, 4g; preferred: none' - Bands| supported: 'unknown' |current: 'unknown' - IP | supported: 'ipv4, ipv6, ipv4v6' - 3GPP | imei: '01458200078' | enabled locks: 'sim, fixed-dialing' |operator id: '24201' | operator name: 'TELENOR' | subscription: 'unknown' | registration: 'home' |EPS UE mode: 'csps-2' - SIM | path: '/org/freedesktop/ModemManager1/SIM/33' - Bearers | paths: '/org/freedesktop/ModemManager1/Bearer/33' bjorn@miraculix:~$ mmcli -m 34 -r error: couldn't reset the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot reset the modem: operation not supported' I seem to be running a Frankenstein libqmi version, but modemmanager and libmbim are plain Debian sid packages: bjorn@miraculix:~$ dpkg -l modemmanager libmbim\* libqmi\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=-=-=== ii libmbim-glib-dev:amd641.17.0-0 amd64 Header files for adding MBIM support to applications that use glib ii libmbim-glib-doc 1.17.0-0 all API documentation for the MBIM protocol library ii libmbim-glib4:amd64
Re: HP lt4120 failing to make single-stack connections on LTE using MM
On Thu, Sep 6, 2018 at 11:29 AM, Tore Anderson wrote: > * Aleksander Morgado > >> Oh wait, this is a Intel based MBIM modem, right? If so, we need >> AT-based reset operations. I believe I still have the HPlt4120 around >> here, will try to implement that. Tracking it here: >> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/86 > > I don't really know, to be honest. I'm using qmicli to manage it and that > works (including «--dms-set-operating-mode=foo»). ModemManager says it's > MBIM, however. Is MBIM/QMI an either/or thing? It seems to me that this > modem is both. > > - > Hardware | manufacturer: 'HP' >| model: 'MBIM [03F0:9D1D]' >| revision: 'T77W595.F0.0.0.6.6.GC.029' >| H/W revision: 'HP lt4120 Snapdragon X5 LTE' >| supported: 'gsm-umts, lte' >|current: 'gsm-umts, lte' >| equipment id: '358894065774253' > - > System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-3' >|drivers: 'cdc_mbim' >| plugin: 'Generic' >| primary port: 'cdc-wdm0' >| ports: 'cdc-wdm0 (mbim), wwp0s20f0u3c3 (net)' > - > Ok, then no, this is not Intel based, it's Qualcomm based. And now that I recall, this is the one for which the firmware upgrade is done using PDC service. It is indeed doing QMI over MBIM, if you're using qmicli nicely. I now wonder why the reset operation didn't work for you. -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
* Aleksander Morgado > Oh wait, this is a Intel based MBIM modem, right? If so, we need > AT-based reset operations. I believe I still have the HPlt4120 around > here, will try to implement that. Tracking it here: > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/86 I don't really know, to be honest. I'm using qmicli to manage it and that works (including «--dms-set-operating-mode=foo»). ModemManager says it's MBIM, however. Is MBIM/QMI an either/or thing? It seems to me that this modem is both. - Hardware | manufacturer: 'HP' | model: 'MBIM [03F0:9D1D]' | revision: 'T77W595.F0.0.0.6.6.GC.029' | H/W revision: 'HP lt4120 Snapdragon X5 LTE' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '358894065774253' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-3' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim), wwp0s20f0u3c3 (net)' - Tore ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
On Thu, Sep 6, 2018 at 10:46 AM, Bjørn Mork wrote: > Aleksander Morgado writes: > >> Oh wait, this is a Intel based MBIM modem, right? If so, we need >> AT-based reset operations. I believe I still have the HPlt4120 around >> here, will try to implement that. Tracking it here: >> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/86 > > Don't know if we've discussed this before, but based on testing with the > EM7345 and looking at the Windows stuff, I believe it supports a vendor > MBIM service usable for reset: > > UUID_FWUSVC => UNKNOWN (0ed374cb-f835-4474-bc11-3b3fd76f5641) > DssPayload: 0x > MaxDssInstances:0 > CidCount: 1 > CidList:1 >CID_MODEM_REBOOT(1) > > > My notes are a bit sketchy as always, and the modem is stowed away, but > I believe that was the only CID of that service and that it only > supported SET requests. With immediate modem reset as a result. > Ah, even better, thanks for the pointer :) https://gitlab.freedesktop.org/mobile-broadband/libmbim/issues/3 -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
Aleksander Morgado writes: > Oh wait, this is a Intel based MBIM modem, right? If so, we need > AT-based reset operations. I believe I still have the HPlt4120 around > here, will try to implement that. Tracking it here: > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/86 Don't know if we've discussed this before, but based on testing with the EM7345 and looking at the Windows stuff, I believe it supports a vendor MBIM service usable for reset: UUID_FWUSVC => UNKNOWN (0ed374cb-f835-4474-bc11-3b3fd76f5641) DssPayload: 0x MaxDssInstances:0 CidCount: 1 CidList:1 CID_MODEM_REBOOT(1) My notes are a bit sketchy as always, and the modem is stowed away, but I believe that was the only CID of that service and that it only supported SET requests. With immediate modem reset as a result. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
> $ sudo mmcli -m 0 --reset Thanks - I had overlooked that one, but it doesn't quite work: error: couldn't reset the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot reset the modem: operation not supported' >>> >>> Oh wow, which MM are you using? This has been implemented for QMI >>> modems since a very long time ago. >> >> Whatever's in Fedora - v1.6.12. Guess I should upgrade. :-) > I tried upgrading now (rebuilt the F29 SRPM): > > $ rpm -qa ModemManager libmbim libqmi > ModemManager-1.8.0-4.fc28.x86_64 > libqmi-1.20.0-2.fc28.x86_64 > libmbim-1.16.0-2.fc28.x86_64 > > But still: > > $ mmcli -m 0 --reset > error: couldn't reset the modem: > 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot > reset the modem: operation not supported' > > $ mmcli -m 0 --factory-reset=00 > error: couldn't reset the modem to factory state: > 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot > reset the modem to factory defaults: operation not supported' > > For what it's worth, these two commands result in no log output from MM > whatsoever, even with debug level logging active. > > v1.8.0 ought to be on the right side of «a very long time ago», right? > There's no reason why this shouldn't work? > Oh wait, this is a Intel based MBIM modem, right? If so, we need AT-based reset operations. I believe I still have the HPlt4120 around here, will try to implement that. Tracking it here: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/86 -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
* Tore Anderson > * Aleksander Morgado >>> $ sudo mmcli -m 0 --reset >>> >>> Thanks - I had overlooked that one, but it doesn't quite work: >>> >>> error: couldn't reset the modem: >>> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot >>> reset the modem: operation not supported' >> >> Oh wow, which MM are you using? This has been implemented for QMI >> modems since a very long time ago. > > Whatever's in Fedora - v1.6.12. Guess I should upgrade. :-) I tried upgrading now (rebuilt the F29 SRPM): $ rpm -qa ModemManager libmbim libqmi ModemManager-1.8.0-4.fc28.x86_64 libqmi-1.20.0-2.fc28.x86_64 libmbim-1.16.0-2.fc28.x86_64 But still: $ mmcli -m 0 --reset error: couldn't reset the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot reset the modem: operation not supported' $ mmcli -m 0 --factory-reset=00 error: couldn't reset the modem to factory state: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot reset the modem to factory defaults: operation not supported' For what it's worth, these two commands result in no log output from MM whatsoever, even with debug level logging active. v1.8.0 ought to be on the right side of «a very long time ago», right? There's no reason why this shouldn't work? Tore ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
* Aleksander Morgado >> >>> $ sudo mmcli -m 0 --reset >> >> Thanks - I had overlooked that one, but it doesn't quite work: >> >> error: couldn't reset the modem: >> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot >> reset the modem: operation not supported' >> > > Oh wow, which MM are you using? This has been implemented for QMI > modems since a very long time ago. Whatever's in Fedora - v1.6.12. Guess I should upgrade. :-) > The correct sequence is: --dms-set-operating-mode=offline and > --dms-set-operating-mode=reset :) That is what MM does when you run > "mmcli -m 0 --reset" That kicked it off into some sort of endless reboot sequence. Cool! :-) A full power cycle of the laptop didn't even fix it. I actully needed to boot the laptop into Windows 10 to make it work again...wonder why. I'll dig some more. Might be that the mmcli --reset actually is a dangerous command on this particular modem. Tore ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
> >> $ sudo mmcli -m 0 --reset > > Thanks - I had overlooked that one, but it doesn't quite work: > > error: couldn't reset the modem: > 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot > reset the modem: operation not supported' > Oh wow, which MM are you using? This has been implemented for QMI modems since a very long time ago. > (Similar result with --factory-reset=123456.) > > That said, now that I thought to search for «factory» I realised there's > «qmicli --dms-restore-factory-defaults». That's probably even better than > just a powercycle, considering my goal is to have a way to bring it back > to a clean slate. Luckily the required code was easy to guess: 00. > > However it says «Device needs to get power-cycled for reset to take effect». > > «qmicli --dms-set-operating-mode=low-power» followed by > «qmicli --dms-set-operating-mode=online» does not do the trick, and if I > use «offline» instead of «low-power» I can't bring it back to «online» > again as it fails with «QMI protocol error (60): 'InvalidTransition'». > > Are there any other ways to powercycle a modem? > The correct sequence is: --dms-set-operating-mode=offline and --dms-set-operating-mode=reset :) That is what MM does when you run "mmcli -m 0 --reset" -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
* matthew stanger > it only seems to happen with the single-stack IP types (both IPv4- and > IPv6-only), never with dual-stack. > > From what I've seen many carriers (and subsets of towers) don't support every > IP type, especially IPv6. In my case, that's not the issue. I'm using SIM cards from carriers that do support IPv6/IPv4v6 in (v)PLMNs that do support it. As I mentioned, it does work fine when using «qmicli --wds-start-network» and or if I try using other UEs (phones). It's only when using ModemManager (and, by extension, NetworkManager) that it gets stuck sometimes. * Aleksander Morgado > $ sudo mmcli -m 0 --reset Thanks - I had overlooked that one, but it doesn't quite work: error: couldn't reset the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot reset the modem: operation not supported' (Similar result with --factory-reset=123456.) That said, now that I thought to search for «factory» I realised there's «qmicli --dms-restore-factory-defaults». That's probably even better than just a powercycle, considering my goal is to have a way to bring it back to a clean slate. Luckily the required code was easy to guess: 00. However it says «Device needs to get power-cycled for reset to take effect». «qmicli --dms-set-operating-mode=low-power» followed by «qmicli --dms-set-operating-mode=online» does not do the trick, and if I use «offline» instead of «low-power» I can't bring it back to «online» again as it fails with «QMI protocol error (60): 'InvalidTransition'». Are there any other ways to powercycle a modem? Tore ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
> > it only seems to happen with the single-stack IP types (both IPv4- and > IPv6-only), never with dual-stack. >From what I've seen many carriers (and subsets of towers) don't support every IP type, especially IPv6. On Tue, Sep 4, 2018 at 6:17 AM Aleksander Morgado wrote: > Hey, > > > > > I have an 'HP lt4120 Snapdragon X5 LTE' WWAN module running firmware > > revision 'T77W595.F0.0.0.6.6.GC.029 1 [Jul 06 2016 23:00:00' (latest > > available on HP's web site). > > > > It tends to frequently get to a state where MM fails to establish single- > > stack connections while in LTE coverage. I'm pretty sure it's not a > > network or subscription problem as the problem is there in different > > PLMNs and SIM cards from different operators, and it works fine using > > other UEs like Android and Jolla phones. I've set up the 3GPP profile > > like so: > > > > $ sudo qmicli -p -d /dev/cdc-wdm0 --wds-get-profile-list=3gpp > > Profile list retrieved: > > [1] 3gpp - profile1 > > APN: 'telenor.smart' > > PDP type: 'ipv6' > > Auth: 'none' > > > > Using qmicli it seems to connect without problems: > > > > $ sudo qmicli -p -d /dev/cdc-wdm0 --wds-start-network=3gpp-profile=1 > > [/dev/cdc-wdm0] Network started > > Packet data handle: '68385664' > > > > But MM fails (and so does NM): > > > > $ sudo /usr/bin/mmcli -m 0 > --simple-connect=apn=telenor.smart,ip-type=ipv6 > > error: couldn't connect the modem: 'Timeout was reached' > > > > This results in the following being logged: > > > > Simple connect started... > > Simple connect state (4/8): Wait to get fully enabled > > Simple connect state (5/8): Register > > Simple connect state (6/8): Bearer > > Simple connect state (7/8): Connect > > Modem /org/freedesktop/ModemManager1/Modem/0: state changed > (registered -> connecting) > > Modem /org/freedesktop/ModemManager1/Modem/0: state changed > (connecting -> registered) > > [/dev/cdc-wdm0] No transaction matched in received message > > [/dev/cdc-wdm0] Received unexpected message (translated)... > >>> Header: > >>> length = 76 > >>> type= command-done (0x8003) > >>> transaction = 31 > >>> Fragment header: > >>> total = 1 > >>> current = 0 > >>> Contents: > >>> status error = 'Failure' (0x0002) > >>> service = 'basic-connect' > (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df) > >>> cid = 'packet-service' (0x000a) > > > > It only happens in LTE coverage, UMTS and GSM has no issues at all. Also > > it only seems to happen with the single-stack IP types (both IPv4- and > > IPv6-only), never with dual-stack. > > > > Anyone seen something like this before and have any suggestion on how to > > avoid/prevent it? > > > > No idea, sorry. > > > If I power down my laptop completely and bring it back up, that might > > might shake it loose for a while, but my test scripts that iterates > > through all PLMNs and all RATs and tries to connect in each using all > > three IP types will usually get it back in the stuck state again. > > > > Is there a way to fully power cycle the WWAN module without > > powercycling the entire laptop, by the way? > > > > $ sudo mmcli -m 0 --reset > > -- > Aleksander > https://aleksander.es > ___ > ModemManager-devel mailing list > ModemManager-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel > ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: HP lt4120 failing to make single-stack connections on LTE using MM
Hey, > > I have an 'HP lt4120 Snapdragon X5 LTE' WWAN module running firmware > revision 'T77W595.F0.0.0.6.6.GC.029 1 [Jul 06 2016 23:00:00' (latest > available on HP's web site). > > It tends to frequently get to a state where MM fails to establish single- > stack connections while in LTE coverage. I'm pretty sure it's not a > network or subscription problem as the problem is there in different > PLMNs and SIM cards from different operators, and it works fine using > other UEs like Android and Jolla phones. I've set up the 3GPP profile > like so: > > $ sudo qmicli -p -d /dev/cdc-wdm0 --wds-get-profile-list=3gpp > Profile list retrieved: > [1] 3gpp - profile1 > APN: 'telenor.smart' > PDP type: 'ipv6' > Auth: 'none' > > Using qmicli it seems to connect without problems: > > $ sudo qmicli -p -d /dev/cdc-wdm0 --wds-start-network=3gpp-profile=1 > [/dev/cdc-wdm0] Network started > Packet data handle: '68385664' > > But MM fails (and so does NM): > > $ sudo /usr/bin/mmcli -m 0 --simple-connect=apn=telenor.smart,ip-type=ipv6 > error: couldn't connect the modem: 'Timeout was reached' > > This results in the following being logged: > > Simple connect started... > Simple connect state (4/8): Wait to get fully enabled > Simple connect state (5/8): Register > Simple connect state (6/8): Bearer > Simple connect state (7/8): Connect > Modem /org/freedesktop/ModemManager1/Modem/0: state changed > (registered -> connecting) > Modem /org/freedesktop/ModemManager1/Modem/0: state changed > (connecting -> registered) > [/dev/cdc-wdm0] No transaction matched in received message > [/dev/cdc-wdm0] Received unexpected message (translated)... >>> Header: >>> length = 76 >>> type= command-done (0x8003) >>> transaction = 31 >>> Fragment header: >>> total = 1 >>> current = 0 >>> Contents: >>> status error = 'Failure' (0x0002) >>> service = 'basic-connect' (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df) >>> cid = 'packet-service' (0x000a) > > It only happens in LTE coverage, UMTS and GSM has no issues at all. Also > it only seems to happen with the single-stack IP types (both IPv4- and > IPv6-only), never with dual-stack. > > Anyone seen something like this before and have any suggestion on how to > avoid/prevent it? > No idea, sorry. > If I power down my laptop completely and bring it back up, that might > might shake it loose for a while, but my test scripts that iterates > through all PLMNs and all RATs and tries to connect in each using all > three IP types will usually get it back in the stuck state again. > > Is there a way to fully power cycle the WWAN module without > powercycling the entire laptop, by the way? > $ sudo mmcli -m 0 --reset -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
