On Tue, Sep 1, 2015 at 5:53 PM, Aleksander Morgado wrote:
> On Tue, Sep 1, 2015 at 6:41 PM, Raul Suarez Moreno
> wrote:
> > Aleksander, you mean using the "--with-newest-qmi-commands" configure is
> not
> > advisable?? In fact, I built using
>
> Sorry, that was my fault. I attach here the full ModemManager debug log just
> from the system booting until the modem enabling process finished. I got it
> after applying Daniels patch, so don't know if anything may be different.
So the modem is indeed being detected as LTE, so that's not
On Tue, Sep 1, 2015 at 12:19 PM, Raul Suarez Moreno
wrote:
> Aleksander, I've enabled debug mode to udev and here is the log content:
I think there was a misunderstanding; what we need is full
ModemManager debug logs, not udev debug logs :)
--
Aleksander
On Tue, Sep 1, 2015 at 5:10 PM, Dan Williams wrote:
> On Tue, 2015-09-01 at 10:35 -0500, Dan Williams wrote:
> > On Tue, 2015-09-01 at 14:16 +0100, Raul Suarez Moreno wrote:
> > > On Tue, Sep 1, 2015 at 1:05 PM, Aleksander Morgado <
> aleksan...@aleksander.es
> > > > wrote:
> >
On Tue, Sep 1, 2015 at 6:41 PM, Raul Suarez Moreno
wrote:
> Aleksander, you mean using the "--with-newest-qmi-commands" configure is not
> advisable?? In fact, I built using that configuration just because it was
> used in the newer ptxdist version building config, should
On Tue, 2015-09-01 at 14:16 +0100, Raul Suarez Moreno wrote:
> On Tue, Sep 1, 2015 at 1:05 PM, Aleksander Morgado > wrote:
>
> > >
> > > Sorry, that was my fault. I attach here the full ModemManager debug log
> > just
> > > from the system booting until the modem
On Tue, 2015-09-01 at 10:35 -0500, Dan Williams wrote:
> On Tue, 2015-09-01 at 14:16 +0100, Raul Suarez Moreno wrote:
> > On Tue, Sep 1, 2015 at 1:05 PM, Aleksander Morgado > > wrote:
> >
> > > >
> > > > Sorry, that was my fault. I attach here the full ModemManager
On Mon, Aug 31, 2015 at 2:17 PM, Raul Suarez Moreno
wrote:
> [947188221.161321] [mm-iface-modem-3gpp.c:751]
> mm_iface_modem_3gpp_run_registration_checks(): Running registration checks
> (CS: 'yes', PS: 'yes', EPS: 'no')
Looks like the modem was detected, but wasn't
Finally, ModemManager detected my modem. Problem was the udev startup
script, udevd was not being correctly initiated.
Now, "mmcli -L" shows my modem device correctly. I could enable it and even
send a text SMS, but I am not being successful at using "mmcli -m 0
--simple-connect", always getting:
Hi everybody,
We are trying to get an embedded device (equipped with Cinterion PLS8 rel.1
radio module) working using ModemManager. The device runs a Linux 3.14
configured using ptxdist-2013.12.0. We've been successful at adding the
ModemManager module to the distribution (or we think so), we
On Thu, Aug 27, 2015 at 2:27 PM, Raul Suarez Moreno
raul.sua...@blue-tc.com wrote:
We are trying to get an embedded device (equipped with Cinterion PLS8 rel.1
radio module) working using ModemManager. The device runs a Linux 3.14
configured using ptxdist-2013.12.0. We've been successful at
On Thu, Aug 27, 2015 at 4:26 PM, Raul Suarez Moreno
raul.sua...@blue-tc.com wrote:
Ok, thinks are clearer now.
Indeed, I did it. I attached the ModemManager log to this message.
Ah, I see it now in the other email.
Do you have udev setup in your system? Looks like ModemManager wasn't
notified
12 matches
Mail list logo