On Wed, 2017-01-04 at 23:45 +, Pedro Pessoa wrote:
> Hi,
>
> I'm looking for hints on why I can't seem to get this modem to
> connect. This is Fedora 25 with ModemManager-1.6.4-1.fc25.x86_64.
>
> From what I can tell on the debug session further down, it aborts the
> connection in progress
On Wed, 2017-01-04 at 16:12 +0100, Bjørn Mork wrote:
> lately I've been having some problems connecting, using the EM7455 in
> my
> laptop. Connections often fail like this:
>
> Jan 4 15:58:01 miraculix NetworkManager[513]:
> [1483541881.5964] device (cdc-wdm0): Activation: starting
>
On Thu, 2016-12-08 at 08:42 +0100, Aleksander Morgado wrote:
> On Tue, Dec 6, 2016 at 6:53 PM, Dan Williams <d...@redhat.com> wrote:
> >
> > I've cherry-picked that and other signal-related stuff (+CESQ
> > support)
> > to the dcbw/mm-1-6-signal branch. We'll s
On Wed, 2016-12-07 at 08:04 +, Mats Berndtsson wrote:
> Den 6 dec. 2016 6:53 em skrev Dan Williams <d...@redhat.com>:
> >
> >
> > On Tue, 2016-12-06 at 13:19 +, Mats Berndtsson wrote:
> > >
> > > Hi,
> > >
> > > sorry fo
On Wed, 2016-12-07 at 12:59 +0100, Carlo Lobrano wrote:
> ---
> plugins/telit/77-mm-telit-port-types.rules | 5 +
> 1 file changed, 5 insertions(+)
Would you mind moving this to the blacklist in 77-mm-usb-device-
blacklist.rules instead? We try to keep all the blacklisted devices
On Tue, 2016-12-06 at 13:19 +, Mats Berndtsson wrote:
> Hi,
>
> sorry for some basic building related questions...
>
> i would like to test the patch from 8/31/16 with extended signal
> quality monitoring for huawei (by Dan Williams)
>
>
> i git-cloned the source
On Wed, 2016-11-02 at 15:15 +0100, Andreas Fett wrote:
> Hi,
>
> for certain SIM cards (Vodafone Germany) and in certain Systems (ie.
> Lenovo t460s) ModemManager seems to have trouble detecting the modem.
>
> We have observed this for a couple of those combinations. Other SIM
> cards seem to
On Mon, 2016-10-24 at 13:43 -0600, matthew stanger wrote:
> Hi all,
>
> I just upgraded our little box with MM 1.6 to systemd 230 and I'm now
> getting a PolicyKit error from mmcli. The issue only happens about 1
> out of
> 10 times after a reboot. The other 9 times everything is fine, weird.
>
On Wed, 2016-10-05 at 16:27 +0200, Aleksander Morgado wrote:
> Hey Dan & everyone,
>
> After Dan's review, I've updated the branch implementing support for
> the ublox devices with the following changes:
>
> * +CGCONTRDP parser is generic, and now supports both formats (pre
> and post TS 27.007
On Fri, 2016-09-30 at 22:33 +0200, Aleksander Morgado wrote:
> On Fri, Sep 30, 2016 at 3:24 PM, Alfredo Palhares e> wrote:
> >
> > ModemManager[31417]: Simple connect started...
> > ModemManager[31417]: PIN:
> > ModemManager[31417]: Operator ID: unspecified
> >
On Thu, 2016-09-29 at 15:39 +0200, Aleksander Morgado wrote:
> The mm_base_modem_grab_port() now receives a MMKernelDevice directly
> from the
> plugin, which is then stored in the MMPort corresponding to the port.
>
> This means that we have direct access to e.g. all properties set by
> udev
On Thu, 2016-09-29 at 15:39 +0200, Aleksander Morgado wrote:
> This commit enables a new core ModemManager daemon option, so that
> automatic
> detection of available modems is totally disabled: '--no-auto-scan'.
> Note that
> this option also replaces the previously used '--test-no-auto-scan'
>
On Thu, 2016-09-29 at 15:39 +0200, Aleksander Morgado wrote:
> Instead of relying constantly on GUdevDevice objects reported by
> GUdev, we now
> use a new generic object (MMKernelDevice) for which we provide an
> initial GUdev
> based backend.
LGTM.
Dan
On Thu, 2016-09-29 at 15:38 +0200, Aleksander Morgado wrote:
> All ports of the same modem reported by the kernel will all be
> associated with
> a common 'uid' (unique id), which uniquely identifies the physical
> device. This
> logic was already in place, what we do now is avoid calling it the
calls to the device.
Dan
>
> Harald
>
>
>
>
>
>
> -Ursprüngliche Nachricht-
> Von: Harald Jung - ECOS Technology <harald.j...@ecos.de>
> Gesendet: Mit 21 September 2016 15:12
> An: Bjørn Mork <bj...@mork.no>
> CC: Dan Williams <d.
On Mon, 2016-09-19 at 22:06 +0200, Harald Jung wrote:
> At this point i have no idea why cdc_mbim doen't grab the device.
> Just that it is loaded but i think it is just loaded by cdc_ncm
> dependencies.
Check usb_modeswitch/usb_modeswitch_dispatcher. If you move them out
of the way, does that
Hi Aleksander,
I'll put in another recommendation for g_clear_object() :)
> ublox: new +UIPADDR=N response parser
> ublox: new +CGCONTRDP=N response parser
> ublox: implement connection using the 2G/3G logic in router or bridge
It seems like the +CGCONTRDP parsing code could be generic and not
f (output);
/* Flag that the command is unsupported, and try with the new way
*/
Dan
> Still trying to contact with Quectel tech support.
>
> On Thu, Sep 8, 2016 at 9:55 PM, Dan Williams <d...@redhat.com> wrote:
> >
> > On Thu, 2016-09-08 at 19:05 +0200, José
ctable behavior.
Dan
>
> On Thu, Sep 8, 2016 at 1:59 PM, Dan Williams <d...@redhat.com> wrote:
>
> >
> > On Thu, 2016-09-08 at 11:27 -0600, matthew stanger wrote:
> > >
> > > I'm trying to understand the difference of what these properties
&
On Thu, 2016-09-08 at 11:27 -0600, matthew stanger wrote:
> I'm trying to understand the difference of what these properties tell
> the
> user? I want to make sure I don't update the status of one in the
> wrong way
> because of my interpretation.
If there's at least one bearer that's connected,
es to libqmi and then apply the attached patch. Does that make
things work?
Dan
> On Thu, Sep 8, 2016 at 6:31 PM, Dan Williams <d...@redhat.com> wrote:
> >
> > On Thu, 2016-09-08 at 17:56 +0200, José wrote:
> > >
> > > Sure:
> > >
> > > r
, I'll post a patch to work around the DMS stupidity.
> Also, if I patch libqmi to get rid of both ModemManager errors, the
> modem still does not work.
Can you post ModemManager --debug logs when you've patched libqmi to
get past this issue?
Dan
> On Thu, Sep 8, 2016 at 4:47 PM,
nfo
for me?
Thanks,
Dan
> On Wed, Sep 7, 2016 at 6:32 PM, Dan Williams <d...@redhat.com> wrote:
> >
> > On Wed, 2016-09-07 at 17:05 +0200, José wrote:
> > >
> > > Hi Dan,
> > >
> > > thanks for your answer.
> > >
&
status: Couldn't get SIM lock status after 6 retries
> ModemManager[710]: Modem: state changed (unknown -> failed)
>
> Will this allow a similar fix?
>
> On Wed, Sep 7, 2016 at 4:29 PM, Dan Williams <d...@redhat.com> wrote:
> >
> > On Wed, 2016-09-0
On Wed, 2016-09-07 at 15:33 +0200, José wrote:
> Maybe I was wrong. I am trying now with the last versions but it is
> still not working:
>
> ModemManager 1.6.0
> libqmi-1.16.0-r0.4.cortexa9hf_vfp_neon
>
> The problem is still reproducible:
Interesting; even though it's a recent device, it's
On Tue, 2016-08-30 at 20:34 +0530, Ajay Garg wrote:
> Thanks Aleksander, for your (as always) detailed and crisp analysis.
>
>
> On Tue, Aug 30, 2016 at 8:09 PM, Aleksander Morgado
> wrote:
> >
> > On Tue, Aug 30, 2016 at 8:56 AM, Ajay Garg
>
On Mon, 2016-08-29 at 20:09 +0200, Aleksander Morgado wrote:
> On Mon, Aug 29, 2016 at 5:33 PM, Dan Williams <d...@redhat.com>
> wrote:
> >
> > >
> > > >
> > > > +static gboolean
> > > > +signal_load_values_finish (MMIfaceModemSign
On Tue, 2016-08-23 at 10:54 +0200, Bjørn Mork wrote:
> Jun 27 10:29:22 jessie4 ModemManager[573]: [/dev/cdc-wdm1] QMI Device
> supports 6 services:
> Jun 27 10:29:22 jessie4 ModemManager[573]: [/dev/cdc-wdm1]ctl
> (1.0)
> Jun 27 10:29:22 jessie4 ModemManager[573]: [/dev/cdc-wdm1]wds
>
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
On Sat, 2016-08-06 at 15:03 +0200, Aleksander Morgado wrote:
> In order to cope with devices already available in the system when
> the daemon
> starts, we allow loading a list of kernel events from an input text
> file where
> the kernel events were recorded since boot.
What's the use-case for
On Sat, 2016-08-06 at 15:03 +0200, Aleksander Morgado wrote:
> Instead of relying constantly on GUdevDevice objects reported by
> GUdev, we now
> use a new generic object (MMKernelDevice) for which we provide an
> initial GUdev
> based backend.
>
> This will help make udev monitoring support
On Thu, 2016-08-18 at 18:53 -0500, ITwrx Info wrote:
>
> On 08/18/2016 11:41 AM, Dan Williams wrote:
> >
> > On Thu, 2016-08-18 at 10:46 -0500, ITwrx Info wrote:
> > >
> > > On 08/18/2016 10:09 AM, Dan Williams wrote:
> > > >
> > &
On Wed, 2016-08-17 at 18:48 -0500, ITwrx Info wrote:
>
> On 08/17/2016 04:26 PM, Dan Williams wrote:
> >
> > On Wed, 2016-08-17 at 15:37 -0500, ITwrx Info wrote:
> > >
> > > On 08/17/2016 01:40 PM, Bjørn Mork wrote:
> > >
On Wed, 2016-08-17 at 15:37 -0500, ITwrx Info wrote:
>
> On 08/17/2016 01:40 PM, Bjørn Mork wrote:
> >
> > ITwrx Info writes:
> >
> > >
> > > On 08/17/2016 10:08 AM, Bjørn Mork wrote:
> > > >
> > > > "ITwrx.org" writes:
> > > >
> > > > >
> > > > > my MM
On Wed, 2016-08-17 at 12:48 +0200, Bjørnar Ness wrote:
> I see others are having similar problems, and wonder if you have any
> idea what is going on here?
>
> Some details:
>
> Kernel: 4.7
> libmbim-1.14.0
> libqmi-1.16.0
> ModemManager-1.6.0
>
> Logfile attached. Sim card is verified working
On Wed, 2016-08-17 at 20:40 +0200, Bjørn Mork wrote:
> ITwrx Info writes:
>
> >
> > On 08/17/2016 10:08 AM, Bjørn Mork wrote:
> > >
> > > "ITwrx.org" writes:
> > >
> > > >
> > > > my MM debug log is here: http://pastebin.com/ev8TGi8J
> > > OK, so that
On Mon, 2016-08-15 at 09:04 -0400, Neil Cherry wrote:
> On 08/15/2016 04:19 AM, Aleksander Morgado wrote:
> >
> > On 15/08/16 03:01, Neil Cherry wrote:
> > >
> > > Okay this was interesting ... I can now reach the modem (Netgear
> > > 341u)
> > > from my server (and browser). But I can't seem to
On Thu, 2016-08-04 at 17:13 +0200, Nicolas Christener wrote:
> Hi Dan :)
>
> On Wed, 2016-08-03 at 11:09 -0500, Dan Williams wrote:
> [...]
> >
> > Any chance you can try the SIM in another WWAN card in the
> > computer, or
> > in a USB stick? Or try
On Wed, 2016-08-03 at 05:47 +0200, Nicolas Christener wrote:
> Hi Dan :)
>
> On Tue, 2016-08-02 at 16:53 -0500, Dan Williams wrote:
> [...]
> >
> > I forget; have you tried the SIM in a different device, and if so
> > does
> > that work correctly?
> Th
On Tue, 2016-08-02 at 22:42 +0200, Nicolas Christener wrote:
> Hi :)
>
> Today I updated my system firmware and searched some more information
> regarding my issue. Then I found this - which seems related:
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commi
> t/drivers
>
On Thu, 2016-07-28 at 18:42 +0200, Aleksander Morgado wrote:
> On Thu, Jul 28, 2016 at 5:38 PM, Dan Williams <d...@redhat.com>
> wrote:
> >
> > On Thu, 2016-07-28 at 00:14 +0200, Aleksander Morgado wrote:
> > >
> > > The rules were matched only against d
On Thu, 2016-07-28 at 00:14 +0200, Aleksander Morgado wrote:
> The rules were matched only against devices with an exact 'tty'
> subsystem, and
> that means that we were not properly adding additional tags on e.g.
> wwan or
> cdc-wdm devices.
>
Good catch, though perhaps we want to limit the
On Thu, 2016-07-28 at 10:19 -0500, Dan Williams wrote:
> On Thu, 2016-07-28 at 00:13 +0200, Aleksander Morgado wrote:
> >
> > They're actually a subcase of SUBSYSTEM!="usb", which we apply just
> > before.
> Actually I thought this was to ensure we match
On Tue, 2016-07-26 at 17:44 +0200, Aleksander Morgado wrote:
> On Tue, Jul 26, 2016 at 5:24 PM, Dan Williams <d...@redhat.com>
> wrote:
> >
> > When a CDMA-only modem is registered with the EVDO network, its not
> > possible to
> > read signal strength in th
On Tue, 2016-07-26 at 17:44 +0200, Aleksander Morgado wrote:
> On Tue, Jul 26, 2016 at 5:24 PM, Dan Williams <d...@redhat.com>
> wrote:
> >
> > When a CDMA-only modem is registered with the EVDO network, its not
> > possible to
> > read signal strength in th
On Tue, 2016-07-26 at 10:24 -0500, Dan Williams wrote:
> When a CDMA-only modem is registered with the EVDO network, its not
> possible to
> read signal strength in the following cases:
>
> 1) while a data connection is active on single-AT-port modems,
> because the AT
>
When a CDMA-only modem is registered with the EVDO network, its not possible to
read signal strength in the following cases:
1) while a data connection is active on single-AT-port modems, because the AT
port is used for PPP and not available for AT+CSQ, AT+CIND or vendor-specific
signal strength
On Sat, 2016-07-23 at 20:39 +0200, Thomas Schäfer wrote:
> Hi,
>
> I have had a chance to test the built in EM8805.
>
> At first I tried windows (it was already installed) to be sure the
> device
> works and to have an idea about the configuration. Unfortunately I
> have only
> pictures of it.
On Thu, 2016-06-30 at 16:16 +0200, Aleksander Morgado wrote:
> On Wed, Jun 1, 2016 at 6:16 PM, Dan Williams <d...@redhat.com> wrote:
> >
> > On Wed, 2016-06-01 at 16:48 +0200, Aleksander Morgado wrote:
> > >
> > > On Wed, Jun 1, 2016 at 4:34 PM, Ca
On Thu, 2016-06-30 at 00:38 +0200, Philipp Hagemeister wrote:
> On 30.06.2016 00:22, Aleksander Morgado wrote:
> >
> > Can you run "mmcli -m 0 --3gpp-register-home" ?
> $ sudo mmcli -m 0 --3gpp-register-home
> error: couldn't register the modem: 'Timeout was reached'
>
> (hangs for 30seconds
Thomas,
Could you test this patch out and make sure it works? It should fix
the problem you saw before.
Dan
On Fri, 2016-06-17 at 13:58 -0500, Dan Williams wrote:
> MM never passes MBIM_CONTEXT_IP_TYPE_DEFAULT which would require
> paying
> attention to the ip_type in the reply to f
On Fri, 2016-06-17 at 20:31 +0200, Bjørn Mork wrote:
> Dan Williams <d...@redhat.com> writes:
>
> >
> > ___
> > ModemManager-devel mailing list
> > ModemManager-devel@lists.freedesktop.org
> > https://lists.fre
MM never passes MBIM_CONTEXT_IP_TYPE_DEFAULT which would require paying
attention to the ip_type in the reply to figure out what type the modem
activated. Instead, MM always specifies the ip_type it wants to activate,
and some modems (K5160) return a different type in the response. The modem
is
On Fri, 2016-06-17 at 19:31 +0200, Thomas Schäfer wrote:
> Hi,
>
>
> Assumed I applied the patch correctly. It doesn't work.
And for good reason... try the updated patch I just sent, that should
do the trick. Thanks for testing!
Dan
___
On Tue, 2016-06-14 at 21:42 +0200, Thomas Schäfer wrote:
> Hi,
>
> the good news first. The modem works under linux in both modes
> (cdc_ether and
> mbim).
>
> cdc-ether-mode works well in dualstack too without special treatment.
>
> I have some problem with dualstack in mbim-mode.
> Using
On Fri, 2016-06-10 at 14:31 -0700, Aleksander Morgado wrote:
> On Fri, Jun 10, 2016 at 11:57 AM, Bjørn Mork wrote:
> >
> > >
> > > On a unrelated note: my 4G signal is rather poor. Mobile phone
> > > typically flips back and forth between 2g and 3g. I have the
> > > feeling
> > >
On Wed, 2016-06-01 at 14:51 +0200, Carlo Lobrano wrote:
> A brief explaination of the issue that this patch solves.
> I observed a probing failure at resume from memory (S3), caused by a
> missing or wrong reply to #PORTCFG? AT command sent during port
> probing.
> This error is probably due to
On Thu, 2016-06-09 at 09:27 +0200, Ralph Plawetzki wrote:
> Am 08.06.2016 um 15:25 schrieb Bjørn Mork:
> >
> > Well, back to the real problem and possible soution: You can flip
> > the
> > modem into QMI mode by using a Sierra vendor specific QMI request,
> > via
> > the QMI-over-MBIM service. I
On Fri, 2016-06-03 at 20:36 +0200, Ralph Plawetzki wrote:
> Am 03.06.2016 um 17:15 schrieb Dan Williams:
> >
> > For allowed modes, combinations are joined with "|". That's non-
> > obvious I suppose, though 'mmcli --help-modem' does say:
> >
> >
On Fri, 2016-06-03 at 14:38 +0200, Ralph Plawetzki wrote:
> Am 03.06.2016 um 14:09 schrieb Aleksander Morgado:
> >
> > --set-preferred-mode must be given along with --set-allowed-modes;
> > and
> > as values for them you should use one of the combinations listed as
> > supported when showing the
On Wed, 2016-06-01 at 19:20 +0200, Aleksander Morgado wrote:
> On Wed, Jun 1, 2016 at 7:13 PM, Dan Williams <d...@redhat.com> wrote:
> >
> > On Wed, 2016-06-01 at 15:46 +0200, Aleksander Morgado wrote:
> > >
> > > On Wed, Jun 1, 2016 at 11:15 AM, Ral
On Wed, 2016-06-01 at 15:46 +0200, Aleksander Morgado wrote:
> On Wed, Jun 1, 2016 at 11:15 AM, Ralph Plawetzki
> wrote:
> >
> > iface_modem_firmware_initialize_ready(): Couldn't initialize
> > interface:
> > 'Firmware not supported'
> We should change that message; it does
On Wed, 2016-06-01 at 16:48 +0200, Aleksander Morgado wrote:
> On Wed, Jun 1, 2016 at 4:34 PM, Carlo Lobrano
> wrote:
> >
> > Hi, has this change already merged?
> Not yet; IIRC Dan suggested to merge it after releasing 1.6.0.
Yeah, I did suggest that, because I thought it
On Tue, 2016-05-31 at 11:24 +0200, Aleksander Morgado wrote:
> ---
>
> Hey Yegor,
>
> Sorry, completely forgot about it.
>
> Could you try this patch and see if it works?
Looks good to me.
> ---
> plugins/simtech/mm-plugin-simtech.c | 79 ---
> --
> 1 file
On Tue, 2016-05-24 at 16:54 +0200, Aleksander Morgado wrote:
> On Tue, May 24, 2016 at 4:37 PM, Dan Williams <d...@redhat.com>
> wrote:
> >
> > On Fri, 2016-05-13 at 20:03 +0200, Aleksander Morgado wrote:
> > >
> > > On Wed, May 11, 2016 at 8:26 PM,
On Fri, 2016-05-13 at 20:03 +0200, Aleksander Morgado wrote:
> On Wed, May 11, 2016 at 8:26 PM, Dan Williams <d...@redhat.com>
> wrote:
> >
> > Please review the dcbw/mbm-connect-disconnect-cleanup branch.
> >
> > https://cgit.freedesktop.org/ModemManag
On Fri, 2016-05-13 at 20:05 +0200, Aleksander Morgado wrote:
> On Wed, May 11, 2016 at 11:25 PM, Dan Williams <d...@redhat.com>
> wrote:
> >
> > If the modem thinks a PDP context is already active it'll return
> > 583 errors from IPDPCFG and IPDPACT until
On Wed, 2016-05-04 at 17:21 +0200, Carlo Lobrano wrote:
> Hi,
>
> I observed a problem in getting the number of unlock retries of some
> SIMs soon after the unlock (the SIM in not completely ready I assume)
> and I saw that some plug-ins inserted a little delay in
> modem_after_sim_unlock to cope
Hi,
Please review the dcbw/mbm-connect-disconnect-cleanup branch.
https://cgit.freedesktop.org/ModemManager/ModemManager/log/?h=dcbw/mbm-connect-disconnect-cleanup
Git commit comments should have a pretty good overview of what's going
on; these were spawned out of the following bugs that
On Tue, 2016-05-03 at 14:56 +0200, Jan Haegeman wrote:
> Hi all,
>
> After some trial and error, I managed to get the Sierra Wireless
> MC7455
> modem online on Debian, kernel version 4.5.0.1.
>
> ModemManager version is 1.4.14-1.
> PPP version is 2.4.6-3.1.
> NetworkManager version is
On Fri, 2016-04-29 at 12:50 +0200, Daniele Palmas wrote:
> This patch series adds support for Telit modems in Dell plugin.
Looks good to me, pushed to git master. Thanks!
Dan
> Probing and init output available at:
> http://pastebin.com/uQV87Gqa
>
> mmcli -m 0
>
>
tps://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=80ce59385fb0bc24f9167f339d5673ede735e1c3
MM debug logging should print out the indication, even though MM
doesn't handle it until this patch.
Dan
> On Mon, May 2, 2016 at 6:25 PM, Dan Williams <d...@redhat.com> wrote:
> >
&
On Mon, 2016-05-02 at 11:31 -0400, Neil Cherry wrote:
> If this is the incorrect place to ask, please point me to the correct
> place.
>
> I have a Netgear 341u modem and I'm trying to use it as a backup
> connection.
> I'm not sure how to begin. The modem works fine under Win7 but I want
> to
>
On Fri, 2016-04-29 at 17:35 +0200, Diego López wrote:
> Hi Dan,
>
> Thank you for the information, it helped a lot for approaching the
> problem.
>
> I've been making more tests but sending traffic doesn't wake up the
> modem.
>
> I'm going to continue working on it because I suspect that my
On Tue, 2016-04-26 at 17:27 +0200, Diego López wrote:
> Hi,
>
> I'm still working with Sierra Wireless MC7354 modem, this time with
> only
> LTE connection. My tests are made by using a signal attenuator with
> only
> one cell.
>
> Bringing the modem al low signal levels I discovered two
On Sat, 2016-04-23 at 00:02 +0200, Thomas Schäfer wrote:
> Hi,
>
> despite windows doesn't use the mbim-mode, I attached the usb-trace.
> (readable
> with wireshark).
>
> Maybe somebody sees the difference in what mm does different at the
> beginning
> compared to the dlink-dialer.
>
> The
On Wed, 2016-04-20 at 17:13 +0200, Andreas Fett wrote:
> Hi,
>
> any news on this one?
>
> On 03/12/15 17:54, Dan Williams wrote:
> >
> > For IPv6 MM should report "DHCP" if there is *any* information
> > missing
> > (DNS or Gateway) because tha
Hook up to the WDS Packet Service Status indication, listen for
disconnection events, and disconnect the bearer when we get one.
---
src/mm-bearer-qmi.c | 139
1 file changed, 139 insertions(+)
*** testing with dual-stack (IPV4V6) appreciated!
On Fri, 2016-04-08 at 17:04 +0200, Aleksander Morgado wrote:
> On Fri, Apr 8, 2016 at 3:59 PM, Diego López Montes .es> wrote:
> >
> > >
> > > >
> > > > >
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > QMI:
> > > > > > > > flags = "indication"
> > > >
On Wed, 2016-04-06 at 10:49 +0200, Aleksander Morgado wrote:
> On Mon, Apr 4, 2016 at 11:13 AM, Jarosław Bielski m> wrote:
> >
> > >
> > > Could you gather debug ModemManager logs while the capabilities
> > > are
> > > set to "gsm-umts" only? Get the modem registered in the
On Tue, 2016-04-05 at 15:35 +0100, Patrick Clark wrote:
> Hi,
>
> I am currently running ModemManager-1.4.2 which supports an Altair
> plugin
> for their LTE modem. The device is found by ModemManger and can be
> seen
> using the command:
>
> mmcli -L
>
> However the device is locked:
>
>
On Tue, 2016-04-05 at 10:56 +0200, Yegor Yefremov wrote:
> I have a problem with SIM7100E. Though kernel creates wwan0 device,
> it
> is not visible in ModemManager.
Try the following patch if you can; also ensure you are building
ModemManager with QMI support (which is the default). Basically,
On Mon, 2016-03-21 at 22:07 +0100, Aleksander Morgado wrote:
> On Mon, Mar 21, 2016 at 5:12 PM, Dan Williams <d...@redhat.com>
> wrote:
> >
> > On Mon, 2016-03-21 at 10:16 +0100, Aleksander Morgado wrote:
> > >
> > > On 20/03/16 20:39, poma wrote:
> &
On Mon, 2016-03-21 at 10:16 +0100, Aleksander Morgado wrote:
> On 20/03/16 20:39, poma wrote:
> >
> > "Newer upower versions no longer emit that signal since this
> > handled by systemd."
> > by Michael Biebl
> >
On Fri, 2016-03-11 at 19:17 +0100, Marcin Szewczyk wrote:
> Hi,
>
> sorry for writing on a devel group but I really did not find any
> better
> place to ask. I am working on a phone-like device that could make a
> voice call and sometimes send some data over the internet. I am
> confused,
On Thu, 2016-03-10 at 17:47 +0100, Aleksander Morgado wrote:
> On Thu, Mar 10, 2016 at 5:02 PM, Dan Williams <d...@redhat.com>
> wrote:
> >
> > >
> > > In addition to the problems with the references, we also update
> > > the
> > > common_
On Thu, 2016-03-10 at 09:10 +0100, Aleksander Morgado wrote:
> We no longer need to complete in idle, because the limitation imposed
> by the
> serial port methods no longer exists.
>
LGTM.
Dan
> ---
> src/mm-port-probe.c | 230 ++--
>
> 1 file
Aleksander,
Just ran across this; haven't looked into it yet but feel free to get
there before me. mm-1-4 git head.
Dan
ModemManager[19109]: [1455814962.494537] [mm-plugin-manager.c:316]
port_probe_context_finished(): (Plugin Manager) 'eno1' port probe finished,
last one in device
On Fri, 2016-02-12 at 10:15 -0600, Dan Williams wrote:
> On Thu, 2016-02-11 at 16:05 +0100, Thomas Sailer wrote:
> > On 02/11/2016 03:25 PM, Aleksander Morgado wrote:
> > > Why not just make the single quote characters optionals? (instead
> > > of
> > > pro
On Tue, 2016-02-09 at 11:27 +1100, Brendan Simon (eTRIX) wrote:
> On 9/02/2016 9:08 AM, Dan Williams wrote:
> > On Tue, 2016-02-09 at 07:31 +1100, Brendan Simon (eTRIX) wrote:
> > > I have a number or remotely deployed arm embedded linux systems
> > > that
> >
On Wed, 2016-02-10 at 09:10 +1100, Brendan Simon (eTRIX) wrote:
>
> On 10/02/2016 3:39 AM, Dan Williams wrote:
> > On Tue, 2016-02-09 at 11:27 +1100, Brendan Simon (eTRIX) wrote:
> > > On 9/02/2016 9:08 AM, Dan Williams wrote:
> > > > On Tue, 2016-02-09 at 07:31 +
On Mon, 2016-02-01 at 14:53 +0100, Daniele Palmas wrote:
> This patch series adds supported and current modes loading for Telit
> plugin
>
> Daniele Palmas (2):
> plugin: telit: add supported modes loading
> plugin: telit: add current mode loading
>
>
On Tue, 2016-02-02 at 08:33 -0800, Aleksander Morgado wrote:
> On Mon, Feb 1, 2016 at 9:19 AM, Bjørn Mork wrote:
> > > > FWIW, the issue could be either the now outdated firmware
> > > > (which I
> > > > believe is not distributed widely enough to be a real problem),
> > > > or the
On Sat, 2016-01-30 at 19:27 -0800, Aleksander Morgado wrote:
> Hey hey,
>
> ModemManager git master is already using GTask already for some
> things, instead of the good old GSimpleAsyncResult. GTask was
> released
> in GLib/GIO 2.36, and it has a really good API, including built-in
>
On Fri, 2016-01-29 at 01:00 +0100, Tomas Jura wrote:
> Hi Alex
>
> Thanks for the feedback. The patches layout got broken due to my
> email
> client. Before I incorporate your comments I and send it in regular
> for
> review, I created a temporary git repo to see the patches in clear
> format:
On Tue, 2016-01-26 at 10:03 +0100, Daniele Palmas wrote:
> This patch adds supported modes loading in Telit plugin.
>
> The patch has basically been written for removing the only AT command
> that
> returns error during the initialization sequence (due to AT*CNTI not
> supported
> by Telit
On Mon, 2016-01-18 at 16:55 +0100, José wrote:
> I was not sure what caused the 'limited' registration state... I am
> going to check if there is any firmware updates available and try
> that.
>
> They all are nanoSIM. Not sure if there is any errors when using
> Movistar and Yoigo SIMs, I will
On Sun, 2016-01-17 at 18:24 +0100, Aleksander Morgado wrote:
> On 17/01/16 16:55, Dan Williams wrote:
> > > When valid responses were returned to the caller of the serial
> > > > command, the
> > > > caller itself was responsible for removing from the
On Mon, 2016-01-18 at 15:15 -0600, Glenn Washburn wrote:
> Hi All,
>
> I've had a ton of headaches getting my MC7354 on Verizon's M2M data
> network. Using NM+MM I can get the interface to come up with an IP,
> so
> it seems as though I'm connected to verizon's network. However, when
> I
> run
On Tue, 2015-12-29 at 17:56 +0100, Aleksander Morgado wrote:
> Hey,
>
> The new Sierra MC74XX modules are very very different to all previous
> Sierra modules. Among other things, they always work in raw-ip mode,
> and they also don't implement "DMS UIM" commands.
>
> This series of patches
301 - 400 of 444 matches
Mail list logo