Sven,
I've been using the HL7588 successfully with ModemManager for a year
or two. There are quite a few patches required to make this work. Some
of them likely need to be rebased onto a more recent modemmanager
revision. Feel free to take a look around
https://github.com/temperednetworks/ModemMan
On Wed, 2019-03-13 at 08:36 +0100, Sven Schwermer wrote:
> Hi,
>
> I’m currently trying to get the Sierra HL7692 up and running. In my
> first attempt, I set the USB composition to AT+KUSBCOMP=2 so that I
> would get 1x MBIM + 3x CDC-ACM. This worked but the modem was only
> recognised as “generic
> Could you give me a pointer?
Never mind, I found a way to make it work. However, I’m not sure whether it’s a
good idea to add the 0x8087 VendorID to the Sierra plugin.
diff --git a/plugins/Makefile.am b/plugins/Makefile.am
index 17a21a0d..3b555194 100644
--- a/plugins/Makefile.am
+++ b/plugins
> -Original Message-
> From: Aleksander Morgado
> Sent: Wednesday, March 13, 2019 6:36 AM
> To: Bowden, Brendan
> Cc: ModemManager (development) de...@lists.freedesktop.org>
> Subject: Re: Random MM and/or qmi-proxy hang?
>
> EXTERNAL EMAIL
>
>
>
> Hey,
>
> >
> > This is RHEL7 so I’m us
> 8087 is Intel's VID, and we don't have a specific plugin in MM for
> devices with the Intel VID. We could extend the "xmm" plugin to do
> this though.
That sounds like a good idea. I’ve had a quick look at the code but couldn’t
find where the VID:PID matching is happening or where the VID:PID t
Bjørn Mork writes:
> Aleksander Morgado writes:
>
>>> I can even connect via --simple-connect. The problem is that
>>> NetworkManager always connects via pppd over the CDC-ACM port. I
>>> would have expected to establish the connection via one of the
>>> CDC-NCM ports (wwan0..4).
>>
>> ModemManag
Aleksander Morgado writes:
>> I can even connect via --simple-connect. The problem is that
>> NetworkManager always connects via pppd over the CDC-ACM port. I
>> would have expected to establish the connection via one of the
>> CDC-NCM ports (wwan0..4).
>
> ModemManager does not know how to use t
> > ModemManager does not know how to use the cdc-ncm ports exposed by the
> > modem, the implementation is missing.
> > IIRC we had some attempt to implement this, and I even got some HL
> > modules sent by Sierra to me, but I'm missing the devkit to use them
>
> That explains the issues I’m seein
Hi Aleksander,
> ModemManager does not know how to use the cdc-ncm ports exposed by the
> modem, the implementation is missing.
> IIRC we had some attempt to implement this, and I even got some HL
> modules sent by Sierra to me, but I'm missing the devkit to use them
That explains the issues I’m
Hey,
> I can even connect via --simple-connect. The problem is that NetworkManager
> always connects via pppd over the CDC-ACM port. I would have expected to
> establish the connection via one of the CDC-NCM ports (wwan0..4).
ModemManager does not know how to use the cdc-ncm ports exposed by th
> > Random question, what does +CSQ report? MM uses +CIND because it gives
> > async notifications, which +CSQ does not. CSQ is usually tied to RSSI
> > though, which still isn't as useful for LTE.
>
> Interestingly, the ublox AT manual says, that +CSQ reports the RSRP in LTE,
> but it doesn’t see
Hey,
>
> This is RHEL7 so I’m using the 1.6 branch of MM and 1.18.0 libqmi; for MM I
> tried building our own 1.16.4 when we suspected MM being the core issue, with
> no change in behavior.
>
Hard to say what the issue is, but you're really using somewhat old
versions. Any chance you can upgrad
> > The following commit introduced a hard dependency on libqmi for the dell
> > plugin:
> >
> > commit 1093c124b4cb "dell,dw5821e: use DMS extension method to load
> > properly formatted firmware version"
> >
> > so ModemManager fails to build under --without-qmi.
>
> Oops, let me fix that.
>
>
I managed to pull the following NetworkManager debug logs:
[1552470915.7827] platform: signal: link added: 7: wwan0
mtu 1500 arp 1 wwan? not-init
addrgenmode eui64 addr 00:00:11:12:13:14 driver cdc_ncm rx:0,0 tx:0,0
[1552470915.7849] manager: wwan0: factory failed to create device:
Device
Hey!
On Tue, Mar 12, 2019 at 10:50 PM Ben Chan wrote:
>
> The following commit introduced a hard dependency on libqmi for the dell
> plugin:
>
> commit 1093c124b4cb "dell,dw5821e: use DMS extension method to load properly
> formatted firmware version"
>
> so ModemManager fails to build under --
Hi Dan,
> ETSI 27.007 says for the "signal" CIND indicator:
>
> "signal" signal quality (0-5)
>
> so if the modem isn't presenting something useful here, I'm not sure
> why it's implementing this indicator in the first place :)
For ublox, the “signal” indicator translates directly to power leve
Hi,
I’m currently trying to get the Sierra HL7692 up and running. In my first
attempt, I set the USB composition to AT+KUSBCOMP=2 so that I would get 1x MBIM
+ 3x CDC-ACM. This worked but the modem was only recognised as “generic” which
didn’t allow for extended signal query, etc.
Next, I set
17 matches
Mail list logo
