Re: ModemManager with Sierra EM7305 and GPS

On Mon, 2017-06-12 at 12:41 +, Petr Kloc wrote: > Dear developers. > > > I have a device with embedded Sierra Wireless EM7305 modem. The > device is running custom based linux alongside MS Windows (dualboot). > I am trying to use the full modem capability in linux while retaining > its basic

Re: [review] dcbw/huawei-voice

> > I also have a Sierra 860 PCMCIA card with voice capability (has > > > > a > > > > headset jack on the card itself) that I was going to improve > > > > the > > > > branch > > > > with.  But I know there are Sierr

Re: MC7455 in X220 with ModemManager 1.6.4

ed :) But failing that, either PCOFFEN or the taping of pin20 are probably fine. PCOFFEN is likely the better solution, though that may be reset on firmware updates. Dan > BR > Dominik > > On Fri, Jun 9, 2017 at 12:25 AM, Bjørn Mork <bj...@mork.no> wrote: > > > Dan Wi

Re: MC7455 in X220 with ModemManager 1.6.4

On Thu, 2017-06-08 at 23:05 +0200, Dominik Strnad wrote: > Hi Aleksander, > > thank you > > On Thu, Jun 8, 2017 at 10:56 PM, Aleksander Morgado < > aleksan...@aleksander.es> wrote: > > > Hey, > > > > > > > > so my card is not listed in rfkill at all: > > > > > > litin@x220:~$ rfkill list

Re: MC7455 in X220 with ModemManager 1.6.4

On Thu, 2017-06-08 at 23:57 +0200, Dominik Strnad wrote: > Hello Dan, > > thank you for help. > > > On Thu, Jun 8, 2017 at 11:44 PM, Dan Williams <d...@redhat.com> > wrote: > > > On Thu, 2017-06-08 at 22:56 +0200, Aleksander Morgado wrote: > >

Re: MC7455 in X220 with ModemManager 1.6.4

On Thu, 2017-06-08 at 22:56 +0200, Aleksander Morgado wrote: > Hey, > > > > > so my card is not listed in rfkill at all: > > > > litin@x220:~$ rfkill list all > > 0: hci0: Bluetooth > > Soft blocked: no > > Hard blocked: no > > 1: tpacpi_bluetooth_sw: Bluetooth > > Soft blocked: no

Re: Allow plugins to specify that signal quality/access tech polling isn't needed (v2)

On Tue, 2017-05-30 at 20:09 +0200, Aleksander Morgado wrote: > Hey Dan and everyone, > > This patch series contains the following updates w.r.t. the v1 > patches: > >  * When a explicit signal refresh is requested, setup the initial > fast-polling configuration (this was suggested in the review

Re: Enabling GPS support for the Cinterion PLS8 devices

On Wed, 2017-05-17 at 15:23 +0200, Aleksander Morgado wrote: > Hey Dan, Matthew & everyone, > > The following patches implement support for GPS capabilities in the > Cinterion PLS8-X, PLS8-E and similar devices, plus some additional > improvements in how GPS support is handled. > > The logic is

Re: [PATCH 4/5] cinterion: support AT^SGPSC capable modems

On Wed, 2017-05-17 at 15:24 +0200, Aleksander Morgado wrote: > The AT^SGPSS command provides an easy way to just start/stop GPS, but > unfortunately it isn't supported by all Cinterion modems. > > The AT^SGPSC command instead is more widely available but it requires > several steps to start and

Re: [PATCH 1/2] altair,hso,samsung: setup send-delay=0 for probing

On Tue, 2017-05-23 at 18:39 +0200, Aleksander Morgado wrote: > The Altair, Option HSO and Samsung plugins all use the send-delay=0 > setting once the modem object has been created. For consistency, use > the same setting during port probing. Tested on an Option 225 and 452, and a Samsung GTY3300.

Re: Received SMS and where they'll be stored

On Tue, 2017-05-23 at 18:50 +0200, Aleksander Morgado wrote: > On 23/05/17 15:19, colin.helliw...@ln-systems.com wrote: > > I'm re-exploring what happens through MM with received SMS - and > > could do > > with some clarification on how it all interacts (modem vs. MM). > > > > # mmcli -m 0

Re: [PATCH] udev: remove default ID_MM_PLATFORM_DRIVER_PROBE whitelist

On Thu, 2017-05-18 at 10:15 +0200, Aleksander Morgado wrote: > The whitelist made all platform TTYs managed by the 'atmel_usart' > kernel driver probed by ModemManager, which isn't something we want, > as most of these aren't broadband modems. > > We leave the logic supporting the

Re: [PATCH 4/4] cinterion: use ^SIND unsolicited messages for access tech reporting

On Sun, 2017-05-21 at 21:49 +0200, Aleksander Morgado wrote: > If the modem supports ^SIND psinfo reporting, we enable the URC and > flag the access technology polling unsupported, so that we only update > access technology via the +CIEV URCs. > > E.g.: > > (ttyACM1): -->

Re: [PATCH 2/4] iface-modem: if bands, capabilities or modes change, refresh signal

On Sun, 2017-05-21 at 21:49 +0200, Aleksander Morgado wrote: > We also remove the explicit refresh request from the Cinterion > plugin, > as this is a generic action applicable to all modems that require > polling for signal quality and/or access technology. Should the poll interval get reset to

Re: Translating AT commands to ModemManager commands?

On Wed, 2017-05-17 at 10:27 +0200, Einar Jón wrote: > Hi > > I have a problem with our modems. > We are trying to move from simple AT commands to using ModemManager > in > python, but we still have some connectivity tests that are only done > with AT commands. > > I have been trying to search

Re: ModemManager will not start on raspberry pi jessie lite

On Tue, 2017-05-16 at 19:08 +0200, marcel wrote: > Hey, I got like the a very similar error as in: > https://lists.freedesktop.org/archives/modemmanager-devel/2015-April/ > 001885.html > > but I got no /usr/share/dbus-1/system-services, as those files are > in  > /etc/dbus-1/ on my system > >

Re: ublox SARA-U260 not showing up in mmcli

On Mon, 2017-05-15 at 21:31 +0200, Aleksander Morgado wrote: > On Mon, May 15, 2017 at 5:48 PM, Dan Williams <d...@redhat.com> > wrote: > > > > ...So, does mean I need to modify the code somewhere to disable > > > > the > > > > send >

Re: ublox SARA-U260 not showing up in mmcli

On Mon, 2017-05-15 at 17:26 +0200, Aleksander Morgado wrote: > On Mon, May 15, 2017 at 5:06 PM, Brent Sink > wrote: > > ...So, does mean I need to modify the code somewhere to disable the > > send > > delay?  Could you point me to where that may be in the > > code?  Thanks!

Re: huawei: duplicated DTMF tone

On Mon, 2017-05-08 at 15:24 +0200, Riccardo Vangelisti wrote: > Hi all, > I've found a strange behavior when I receive DTMF during voice call. > It seems that DTMF code are received and signaled twice, > specifically  > one time for each active AT port. So in this case, it should probably just be

Re: Passing Operator to NetworkManager

On Mon, 2017-05-08 at 10:17 +0100, colin.helliw...@ln-systems.com wrote: > I'm hooking together ModemManager and NetworkManager (without > systemd) and > would like to grab the Operator determined by MM when it enables the > modem > and use it to set the apn setting in the NM connection. Basically

Re: QMI modems with MM-master branch error

On Fri, 2017-05-05 at 14:08 +, Penalva, Salvador wrote: > I thought that too, > >  but this modem still worked with the commit before the last changes > I mentioned in the email before. Why is the connection attempt > cancelled then an in the second retry working again? The issue from the

Re: [review] dcbw/huawei-voice

coming from /dev/ttyUSB1. > > > Example: # cat /dev/ttyUSB1 | aplay -f S16_BE > > > > > > Dan, could you indicate the correct sequence to make a call when > > > CVOICE > > > is supported ? How ModemManager tells me what is the correct > > > device

Re: [review] dcbw/huawei-voice

escribed what the value returned from "AT^DDSETEX?" actually means, though perhaps it means the USB interface # or something. But the only usage I can find is for "2", so it's unclear. Is there any way with the MU709 and ME909 to determine conclusively that they support voice

Re: MMKernelDevice ID_USB_INTERFACE_NUM property isn't set anymore

On Wed, 2017-05-03 at 20:21 +0200, Aleksander Morgado wrote: > On Wed, May 3, 2017 at 5:08 PM, Dan Williams <d...@redhat.com> wrote: > > > > > Do you have a /lib/udev/rules.d/60-serial.rules in your > > > > > system > > > > > that > &

Re: MMKernelDevice ID_USB_INTERFACE_NUM property isn't set anymore

On Wed, 2017-05-03 at 14:55 +0200, Aleksander Morgado wrote: > On Wed, May 3, 2017 at 2:09 PM, Carlo Lobrano > wrote: > > > > > When using the "udev" backend, which you are, the property > > > > > isn't > > > > > "loaded" or "stored" anywhere in our code. We directly look > >

Re: Parallel enables occurring (when SIM PIN enabled)

On Wed, 2017-04-26 at 12:12 +0200, Aleksander Morgado wrote: > On Tue, Apr 25, 2017 at 4:43 PM, Dan Williams <d...@redhat.com> > wrote: > > > > I've encountered a problem when using MM with Network Manager, > > > > when > > > > the SIM PI

Re: Parallel enables occurring (when SIM PIN enabled)

On Tue, 2017-04-25 at 10:32 +0200, Aleksander Morgado wrote: > On Tue, Apr 25, 2017 at 10:20 AM, Colin Helliwell > wrote: > > I've encountered a problem when using MM with Network Manager, when > > the SIM PIN is enabled - in short it seems that MM is able to hit a

Re: [PATCH] blacklist: add Analog Devices EVAL-ADXL362Z-DB

On Sun, 2017-04-23 at 20:39 +0300, Maksim Salau wrote: > Signed-off-by: Maksim Salau Thanks! Pushed to git master, mm-1-6, and mm-1-4. Dan > --- >  src/77-mm-usb-device-blacklist.rules | 3 +++ >  1 file changed, 3 insertions(+) > > diff --git

Re: [PATCH] telit: add error_code recognition to +CSIM parser

On Tue, 2017-04-18 at 17:46 +0200, Aleksander Morgado wrote: > On Mon, Apr 3, 2017 at 5:01 PM, Carlo Lobrano > wrote: > > * 6300 - Verification failed > > * 6983 - Authentication method blocked > > * 6984 - Reference data invalidated > > * 6A86 - Incorrect parameters > > *

Re: [PATCH v2] broadband-bearer: once connected, set flow control settings

On Tue, 2017-04-18 at 17:49 +0200, Aleksander Morgado wrote: > On Tue, Apr 18, 2017 at 4:58 PM, Dan Williams <d...@redhat.com> > wrote: > > > > > I made the flow control setting a readable property in the > > > > > Modem > > > > > obj

Re: Sierra HL7588

On Tue, 2017-04-18 at 00:12 +, Paul Bartell wrote: > Hello, > > I've been trying to bring up a Sierra HL7588 modem on the latest > version of > ModemManager. The HL7588 seems to be based on the Sierra EM7345 with > an > Intel/Infineon chipset. > > This modem has three different USB

Re: [PATCH v2] broadband-bearer: once connected, set flow control settings

On Tue, 2017-04-18 at 12:24 +0200, Aleksander Morgado wrote: > On Mon, Apr 17, 2017 at 6:54 PM, Dan Williams <d...@redhat.com> > wrote: > > > I made the flow control setting a readable property in the Modem > > > object, and a RW property in the Bearer object. T

Re: MC7455 location support

when converting the enum to the QMI protocol, while "public-format" is the fancy enum that we've defined that will be used in the libqmi API. Let us know if you have more questions... Thanks! Dan > LG, > Károly Pados > > tec4data > finding of facts! > thoerl 35; 8621

[review] dcbw/huawei-voice

Hi, Reworked the audio format stuff and added mmcli support. Removed the 'blocked' stuff and started using 'connected' instead. Now the larger change: call state handling in mm-base-call.c. I removed most of the base class call state setting for the MO (mobile- originated, eg outgoing) call

Re: [review] dcbw/qcdm-cleanups

On Sat, 2017-04-15 at 22:48 +0200, Aleksander Morgado wrote: > Hey Dan, > > On 10/04/17 17:50, Dan Williams wrote: > > Port some stuff over to GTask, clean up some QCDM stuff, and also > > make > > sure QCDM code opens the port when it needs to instead of assuming >

Re: [PATCH] core: prefer g_task_return_error_if_cancelled() than custom errors

On Sat, 2017-04-15 at 23:26 +0200, Aleksander Morgado wrote: > When the GCancellable is added to the GTask, we can use a single > method call to check for the task being cancelled, and complete it > right away if so. > > This patch also clears up the logic in the Novatel plugin, where the > code

Re: [PATCH v2] broadband-bearer: once connected, set flow control settings

On Sun, 2017-04-09 at 14:14 +0200, Aleksander Morgado wrote: > During modem initialization we detected the flow control settings > supported by the modem, and selected the best one to use from them, > notifying it to the device via AT+IFC. The device was therefore > instructed to use that flow

Re: MC7455 location support

ug log? It doesn't seem to mention "MBIM" at all. Or maybe I need > to check this using another way? > > All files I attached will tell you in the top how that output was > created. I hope these will help narrow down what is missing. Let me > know if there is any

Re: MC7455 location support

with (I don't have a clue yet about MM's code either), I > might give it a go if you don't mind. > > Regards, > > Károly > > April 12, 2017 5:58 PM, "Dan Williams" <d...@redhat.com> wrote: > > > On Wed, 2017-04-12 at 13:21 +, Karoly

Re: Porting to GTask: pointer to self in context?

On Thu, 2017-04-06 at 20:09 +0200, Aleksander Morgado wrote: > Hey Ben, Dan and everyone else, > > Related to the ports to GTask sent by Ben... > > When using the GSimpleAsyncResult logic, I usually always added a > full > reference to the "source object" of the async operation in the >

Re: Failed to find primary AT port

guring the baud rate from udev rules, see: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=11a26f10668659fb0c043ec9bc88debacce8cab1 Dan > Best Regards, > > Jan Graczyk > > -Original Message- > From: Dan Williams [mailto:d...@redhat.com]  > S

Re: [PATCH] novatel-lte: revert to original plugin library name

On Mon, 2017-04-03 at 13:05 -0700, Ben Chan wrote: > Commit f9c63bfa0 "build,plugins: update build rules" accidentally > changed the Novatel LTE plugin from 'libmm-plugins-novatel-lte.so' to > 'libmm-plugins-novatel_lte.so'. The name becomes inconsistent with > other > plugin names. Seems fine to

[PATCH] telit: fix AT+SERVICE 3GPP2 access technology reporting

Looks like a C error from the AT#PSNT codepath; all the docs I can find indicate that AT+SERVICE returns only an integer and no commas: (ttyUSB2): --> 'AT+SERVICE?' (ttyUSB2): <-- '+SERVICE: 3OK' Couldn't refresh access technologies: 'Failed to parse +SERVICE response: '+SERVICE: 3'' ---  

Re: [PATCH] telit: add error_code recognition to +CSIM parser

On Mon, 2017-04-03 at 17:01 +0200, Carlo Lobrano wrote: > Updated mm_telit_parse_csim_response in order to correctly recognize > the > following +CSIM error codes: > > * 6300 - Verification failed > * 6983 - Authentication method blocked > * 6984 - Reference data invalidated > * 6A86 - Incorrect

Re: [PATCH 2/2] broadband-modem: normalize also operator code

On Sat, 2017-03-25 at 21:39 +0100, Aleksander Morgado wrote: > The operator code (MCCMNC) may also be given encoded in the current > charset (e.g. UCS2). LGTM. Dan > Based on a patch from Colin Helliwell > > --- >  plugins/altair/mm-broadband-modem-altair-lte.c

Re: [PATCH 1/2] modem-helpers: if operator not in UCS2, see if already valid UTF-8

On Sat, 2017-03-25 at 21:39 +0100, Aleksander Morgado wrote: > The method doing the operator name normalization takes as input the > current configured modem charset. If this is UCS2, we will now just > assume this is a hint: the string may or may not come in hex/UCS2. > > This logic makes the

Re: Flow control settings for RS232 modems

On Sat, 2017-03-25 at 19:32 +0100, Aleksander Morgado wrote: > Hey Dan, Daniele, Carlo & everyone, > > This series of patches tries to implement proper flow control > settings on the serial port, and is based on letting MM detect which > are the supported modes with AT+IFC=?. This makes it

Re: Failed to find primary AT port

mManager with libqmi support (--with-qmi=yes) This will solve both your problems, most likely. Dan > Best Regards,        > > Jan Graczyk > > -Original Message- > From: Dan Williams [mailto:d...@redhat.com]  > Sent: Friday, March 31, 2017 1:51 PM > To: J

Re: Failed to find primary AT port

On Fri, 2017-03-31 at 20:35 +, Jan Graczyk wrote: > Hello All, > > I have a problem with ModemManager failing to find primary AT port. > Her is the ModemManager debug log: What kind of modem is this? Does it require a specific baud rate and/or serial settings? Can you talk to the modem

Re: AW: AW: h5321gw Problem with --location-get

n...@aleksander.es]  > Gesendet: Donnerstag, 23. März 2017 13:01 > An: Thomas Lang <thomas.l...@tactilo.eu>; Dan Williams <dcbw@redhat.c > om>; ModemManager (development) <modemmanager-devel@lists.freedesktop > .org> > Betreff: Re: AW: h5321gw Problem with --location-get >

Re: error: modem has no firmware capabilities

On Thu, 2017-03-30 at 19:04 +0200, poma wrote: > Hello > > # mmcli --version | head -2 > > mmcli 1.6.4 > > # mmcli -v -m 0 --firmware-list > [30 Mar 2017, 18:56:51] [Debug] ModemManager process found at ':1.4' > [30 Mar 2017, 18:56:51] [Debug] Assuming '0' is the modem index > [30 Mar 2017,

Re: Manage 3G modem with ModemManager through Network Manager

On Thu, 2017-03-30 at 11:39 +0200, Francesco Andrisani wrote: > This is my NetworkManager Log in debug mode...i don't see anything > about > ModemManager I'm a bit late to the party here, and I see you've solved it already, but from these logs it doesn't look like the WWAN device plugin is built

Re: [PATCH] broadband-bearer: set TTY as connected as soon as ATD replies

On Fri, 2017-03-24 at 15:03 +0100, Aleksander Morgado wrote: > When the connection request is done via ATD, flag the port as > connected as soon as the successful response is received, so that we > remove our polling on the device right away. > > https://bugs.freedesktop.org/show_bug.cgi?id=99541

Re: [PATCH] base-bearer: stop connection status monitoring if no TTY available

On Fri, 2017-03-24 at 14:55 +0100, Aleksander Morgado wrote: > On modems with a single TTY for both control and data, we cannot use > the TTY to load connection status once we're in connected mode: > > Connection through a plain serial AT port (ttyUSB2) > (ttyUSB2): --> 'ATD*99***2#' >    

Re: [PATCH 2/2] broadband-modem: fix capabilities in 4G-only devices

On Sun, 2017-03-12 at 21:05 +0100, Aleksander Morgado wrote: > The +CGSM capability is saying that the modem is a 3GPP modem, but > that doesn't necessarily mean it's a GSM/UMTS modem, it could be a > LTE-only device. > > We did add the GSM_UMTS capability when +CGSM was found, so now we'll >

Re: [PATCH 1/2] broadband-modem,helpers: implement AT+WS46=? response parser

On Sun, 2017-03-12 at 21:05 +0100, Aleksander Morgado wrote: > We want a parser that returns the full list of combinations found. Looks good to me except the comment: +/* Fixup the ANY value, based on whether LTE is supported or not the code under that comment seems to use all modes, not

Re: LibMM-Glib Ansi C Example

On Thu, 2017-03-23 at 18:17 +0100, Francesco Andrisani wrote: > Hi, > please can someone help me to find some examples for use libmm-glib > into my > C application? > I want: > - start a modem connection (with ppp interface) Note that most modems do not use PPP these days. But if yours does,

Re: h5321gw Problem with --location-get

On Thu, 2017-03-23 at 01:00 -0500, Dan Williams wrote: > On Wed, 2017-03-22 at 22:14 -0500, Dan Williams wrote: > > On Wed, 2017-03-22 at 20:34 +, Thomas Lang wrote: > > > Hi, > > > I'm trying to get the cellId info from an Ericsson module. I'm > > > using

Re: h5321gw Problem with --location-get

On Wed, 2017-03-22 at 22:14 -0500, Dan Williams wrote: > On Wed, 2017-03-22 at 20:34 +, Thomas Lang wrote: > > Hi, > > I'm trying to get the cellId info from an Ericsson module. I'm > > using > > the modemmanager version 1.6.4. > > What firmware versio

Re: h5321gw Problem with --location-get

On Wed, 2017-03-22 at 20:34 +, Thomas Lang wrote: > Hi, > I'm trying to get the cellId info from an Ericsson module. I'm using > the modemmanager version 1.6.4. What firmware version? Is the firmware MBIM-mode or AT-mode? Dan > tactilo@VirtualBox001:~$ mmcli -m 0 --location-status > >

Re: mmcli -m 0 -e command fails

On Thu, 2017-03-23 at 00:28 +, Jan Graczyk wrote: > Hello Aleksander, > > I have attached a file with the logs from ModemManager --debug > command. The modem doesn't reply to any of the Capabilities requests commands and thus MM can't figure out what to do with the modem.

Re: Quectel UC20: Correct way to get it up and running on embedded?

ch: we're not quite sure what that error represents; we've determined that in some cases it means IPv4 vs. IPv6 mismatch and profiles in the modem, but that doesn't seem to always be the case. Dan > On 20 March 2017 at 19:33, Dan Williams <d...@redhat.com> wrote: > > On Mon, 2017-03-

Re: PPP modem differences

On Wed, 2017-03-22 at 14:41 +, Colin Helliwell wrote: > > On 22 March 2017 at 13:50 Dan Williams <d...@redhat.com> wrote: > > > > On Wed, 2017-03-22 at 13:23 +, colin.helliw...@ln-systems.com > > wrote: > > > > > I know this might not be an i

Re: PPP port being left open?

On Wed, 2017-03-22 at 10:40 +, colin.helliw...@ln-systems.com wrote: > I've noticed a situation where MM seems to not be fully closing the > PPP > port. [1.8 Master, updated probably a couple of days ago] >   mmcli -m 0 --enable  >   mmcli -m 0 --simple-connect="apn=.." >   pppd nodetach

Re: [PATCH] kernel-device: device-specific properties in either port or physdev

On Sat, 2017-03-11 at 13:00 +0100, Aleksander Morgado wrote: > There are 2 main types of udev properties: device-specific and > port-specific. > > The port-specific properties are set independently per port (e.g. > port > type hints set per interface number for a given vid:pid). > > The

Re: [PATCH] serial: allow specifying baudrate to use via udev tags

On Sat, 2017-03-11 at 13:15 +0100, Aleksander Morgado wrote: > A new 'ID_MM_TTY_BAUDRATE' per-port udev tag is introduced, which > allows specifying the baudrate that will be used when opening a > specific serial port. > > E.g.: > > ACTION!="add|change|move", GOTO="mm_my_modem_end" >

Re: Could not acquire the 'org.freedesktop.ModemManager1' service name

y unauthorized use is prohibited.  If you are not the > intended recipient, please contact the sender by reply email and > destroy all copies of the original message. > > > -Original Message- > From: Dan Williams [mailto:d...@redhat.com]  > Sent: Tuesday, March 21, 2017 9:41 A

Re: AW: MC7455 not listed as usb device any more after reboot

On Mon, 2017-03-20 at 09:45 +, Thomas Lang wrote: > Hi Dan, > thanks for your comments. > I have included a trace of the working start and the reboot. I > noticed that in the reboot case the usb 3-1.3 device is not detected > anymore. The usb 3-1 is an ehci-pci. Would it help to reset the

Re: Integration into NetworkManager

On Mon, 2017-03-20 at 16:48 +, colin.helliw...@ln-systems.com wrote: > So I've got a [reasonably?] sorted MM setup now - a mux driver > providing two > virtual ports: ttyMux0 (PPP) and ttyMux1 (Primary). I'm now wanting > to hook > the former into NetworkManager. > > From a fresh

Re: MC7455 not listed as usb device any more after reboot

On Fri, 2017-03-17 at 11:57 +, Thomas Lang wrote: > Hi all, > perhaps you have seen this bug before. I’m using the MC7455 with a > linux system after normal power cycle (unplugged power) the mc 7455 > can be found  with lsusb: > > > > go@ubuntu:~$ lsusb > > Bus 003 Device 003: ID 1199:9071

[PATCH] iface-modem-3gpp: use mm_3gpp_parse_operator_id() instead of custom code

--- src/mm-iface-modem-3gpp.c | 43 --- 1 file changed, 8 insertions(+), 35 deletions(-) diff --git a/src/mm-iface-modem-3gpp.c b/src/mm-iface-modem-3gpp.c index d38c4ca..8b93550 100644 --- a/src/mm-iface-modem-3gpp.c +++ b/src/mm-iface-modem-3gpp.c @@

Re: Unexpected COPS format

On Fri, 2017-03-17 at 16:13 +, Colin Helliwell wrote: > > On 17 March 2017 at 15:02 Colin Helliwell > ms.com> wrote: > > > > > On 17 March 2017 at 14:16 colin.helliw...@ln-systems.com wrote: > > > > > > I’m reviewing the info fetched on my modems, and one of them

Re: 'port forced close' after failed ppp

On Thu, 2017-03-16 at 13:36 +, Colin Helliwell wrote: > > On 14 March 2017 at 14:18 Colin Helliwell > ms.com> wrote: > > > > > On 13 March 2017 at 09:53 Colin Helliwell > > tems.com> wrote: > > > > > > > On 13 March 2017 at 09:06 Colin

Re: [PATCH] telit: lock/unlock CSIM operations by default

On Wed, 2017-03-15 at 10:28 +0100, Aleksander Morgado wrote: > On Wed, Mar 15, 2017 at 2:40 AM, Dan Williams <d...@redhat.com> > wrote: > > > > > > Can you guys review and test this patch? It looks like it solved > > > the > > > issue I s

Re: [PATCH] telit: lock/unlock CSIM operations by default

On Wed, 2017-03-15 at 00:19 +0100, Aleksander Morgado wrote: > Wrap the AT+CSIM=XX commands between lock (CSIM=1) and > unlock (CSIM=0) operations. > > This seems to avoid the TTY lockup seen in several different Telit > modules. > > https://bugs.freedesktop.org/show_bug.cgi?id=100205 > >

Re: 'port forced close' after failed ppp

On Tue, 2017-03-14 at 14:18 +, Colin Helliwell wrote: > > On 13 March 2017 at 09:53 Colin Helliwell > ms.com> wrote: > > > > > On 13 March 2017 at 09:06 Colin Helliwell > > tems.com> wrote: > > > > > > > On 10 March 2017 at 16:54

Re: [PATCH] telit: don't ignore AT ports without an explicit port type hint tag

On Sat, 2017-03-11 at 13:29 +0100, Aleksander Morgado wrote: > The telit plugin is based on two main ways of checking the purpose of > each port: udev tags flagging specific interfaces (with info taken > from Windows .inf drivers), or otherwise using AT#PORTCFG? to query > the modem about that

Re: [PATCH] iface-modem: improve network registration checks for LTE devices

On Sun, 2017-03-12 at 20:41 +0100, Aleksander Morgado wrote: > If a device reports "LTE" in the list of current capabilities, we'll > set EPS network supported by default. This will enable CEREG > registration checks for AT based devices. > > If a device reports only "LTE" in the list of current

Re: [PATCH] telit: support RS232 modems

On Sun, 2017-03-12 at 20:47 +0100, Aleksander Morgado wrote: > Adding the vendor string match allows us to support RS232 devices in > the Telit plugin: the USB vendor id check may now be ignored and > instead we probe for the vendor string via AT commands, which works > even if the device is

Re: 'port forced close' after failed ppp

On Thu, 2017-03-09 at 09:19 +, Colin Helliwell wrote: > > On 08 March 2017 at 14:38 Aleksander Morgado > .es> wrote: > > > > On Wed, Mar 8, 2017 at 3:08 PM, Colin Helliwell > > > > wrote: > > > > > But this brings me back (in a

Re: 'port forced close' after failed ppp

On Mon, 2017-03-06 at 15:35 +, colin.helliw...@ln-systems.com wrote: > I have MM hooked into a Mux driver which is presenting two virtual > ports: > one as the Primary, one for PPP. I'm attempting to fire up the > data/PPP with > --enable and --simple-connect=. > > The PPP is failing, no

[PATCH] bearer-qmi: add WDS event reporting support

Don't do anything with the events yet, but at least turn them on and capture them in debug logging. --- src/mm-bearer-qmi.c | 265 +--- 1 file changed, 229 insertions(+), 36 deletions(-) diff --git a/src/mm-bearer-qmi.c b/src/mm-bearer-qmi.c index

Re: [PATCH 3/3] kernel-device: simplify handling of platform/pci/pnp/sdio parent

On Thu, 2017-02-23 at 11:45 -0800, Ben Chan wrote: > This patch simplifies the handling of platform/pci/pnp/sdio device in > find_physical_gudevdevice(). When the code finds the first parent > device > under the subsystem 'platform', 'pci', 'pnp', or 'sdio', it stops > traversing up the device

Re: [PATCH v2 1/2] kernel-device: handle SDIO device in find_physical_gudevdevice

On Tue, 2017-02-28 at 18:49 -0800, Ben Chan wrote: > A few crashes have been observed in the field with the following > signature: Pushed to git master, backported to mm-1-6 and mm-1-4. Thanks! Dan >   Thread 0 CRASHED [SIGSEGV @ 0x ] MAGIC SIGNATURE THREAD >   0xf53ff5e8  

Re: [PATCH 3/3] kernel-device: simplify handling of platform/pci/pnp/sdio parent

On Thu, 2017-02-23 at 11:45 -0800, Ben Chan wrote: > This patch simplifies the handling of platform/pci/pnp/sdio device in > find_physical_gudevdevice(). When the code finds the first parent > device > under the subsystem 'platform', 'pci', 'pnp', or 'sdio', it stops > traversing up the device

Re: How to issue an "ifup broadband" when this is logged

On Wed, 2017-02-15 at 17:09 -0600, Russ Westrem wrote: > On Feb 15, 2017 4:37 PM, "Dan Williams" <d...@redhat.com> wrote: > > On Wed, 2017-02-15 at 21:14 +0100, Aleksander Morgado wrote: > > On Wed, Feb 15, 2017 at 9:00 PM, Russ Westrem > &g

Re: How to issue an "ifup broadband" when this is logged

On Wed, 2017-02-15 at 21:14 +0100, Aleksander Morgado wrote: > On Wed, Feb 15, 2017 at 9:00 PM, Russ Westrem > wrote: > > Is there anything in the modemmanager scripts that I could change > > to have it > > ignore the deregistered modem and stop it from removing it

Re: How to issue an "ifup broadband" when this is logged

On Wed, 2017-02-15 at 21:14 +0100, Aleksander Morgado wrote: > On Wed, Feb 15, 2017 at 9:00 PM, Russ Westrem > wrote: > > Is there anything in the modemmanager scripts that I could change > > to have it > > ignore the deregistered modem and stop it from removing it

Re: How to issue an "ifup broadband" when this is logged

On Tue, 2017-02-14 at 15:46 -0600, Russ Westrem wrote: > You mean you can still use the WWAN even if MM says it's > disconnected? > Not sure I understood, otherwise. > > > -- > Aleksander > https://aleksander.es > > > > No, nothing is usable untill i ifup. Here's what's probably going on...

Re: Modem creation/startup order

On Tue, 2017-02-14 at 15:16 +, Colin Helliwell wrote: > > On 14 February 2017 at 12:59 Aleksander Morgado > der.es> wrote: > > > > On Tue, Feb 14, 2017 at 12:54 PM, Colin Helliwell > > > > ... > > > > Yes, the idea is that both ports end up grabbed in the same > > > >

Re: Fetching signal quality during data connection?

On Wed, 2017-02-08 at 14:46 +, colin.helliw...@ln-systems.com wrote: > I'm re-visiting this initial issue, of MM not spotting the 'NO > CARRIER' when the modem times out of data mode. Because of aggro > getting it working direct on the serial port, I'm back with my mux > driver (which is what

Re: How to issue an "ifup broadband" when this is logged

Is it at all related to the amount of data transferred? Dan On Thu, 2017-02-09 at 12:54 -0600, Russ Westrem wrote: > More info on these disconects.  It seems that the better the signal > and > faster the speed results in faster and more frequent disconects. > Around 5 > to 10 min.  When the

Re: How to issue an "ifup broadband" when this is logged

On Tue, 2017-02-07 at 10:02 -0600, Russ Westrem wrote: > I asked this in someone else's e-mail but maybe i should have made my > own > so here it is. > My goal is to issue an ifup broadband in LEDE whenever this line is > logged > from modemmanager. > > daemon.info [1035]:   Modem >

Re: Fetching signal quality during data connection?

en ports; but I'd also considered other routes such as > ofono [seems ok on the face of it, but documentation appalling!]. So > putting in the mux driver kept those parts of code re-usable & non- > replicated while we settle on what apps to use/write. It's ultimately > changeable

Re: Fetching signal quality during data connection?

On Thu, 2017-01-26 at 15:58 +, colin.helliw...@ln-systems.com wrote: > Odd though that the signal quality doesn't work again until I ' > --disconnect'. Testing from a terminal app it seemed to re-respond to > this as soon as the timeout/'NO CARRIER' occurs. It may be that MM is > sending some

Re: [systemd-devel] WebUSB

ken by probing, or the AT/DM requests themselves? Most devices I know of (modem or not) will disregard communication they don't know about as a function of their protocol. MM's probe process does not alter device state in any way, just requests informational responses. Dan > On Wed, Jan 11, 2017 a

Re: [systemd-devel] WebUSB

On Tue, 2017-01-10 at 18:33 +0100, Greg KH wrote: > On Tue, Jan 10, 2017 at 06:23:13PM +0100, Lars Knudsen wrote: > > > > > > On Jan 10, 2017 18:19, "Greg KH" wrote: > > > > On Tue, Jan 10, 2017 at 06:04:46PM +0100, Lars Knudsen wrote: > > > I figured that made most

Re: [systemd-devel] WebUSB

On Tue, 2017-01-10 at 01:01 +0100, Lars Knudsen wrote: > On Tue, Jan 10, 2017 at 12:47 AM, Lars Knudsen > wrote: > > > A small update:  When the modemmanager finishes probing (~16 secs > > after > > connection) data seems to stop flowing in from the WebUSB bulk > > endpoint > >

Re: [systemd-devel] WebUSB

to the modem and does nothing else until the user (or the desktop environment configuration) tells MM to do something. Dan > On Jan 9, 2017 19:40, "Dan Williams" <d...@redhat.com> wrote: > > > On Mon, 2017-01-09 at 19:22 +0100, Lars Knudsen wrote: > > > On

Re: [RFC] stanger/cinterion branch

On Thu, 2017-01-05 at 19:30 +0100, Aleksander Morgado wrote: > On Thu, Jan 5, 2017 at 6:29 PM, matthew stanger > wrote: > > Only thing I haven't been able to test is SIM's with User/Pass. > > Does anyone > > out there have one they are able to test with? > > You mean APN

<    1   2   3   4   5   >