Hi again!
On Mon, Feb 6, 2017 at 3:39 AM, Aleksander Morgado
wrote:
> Hey,
>
>>> > Can you help me understand how I can check this?
>>>
>>> Did you use my openwrt feed without modifications? If so you're
>>> probably building 0bf4db6561de9be61028eb6bc1792a3b7cc410b5:
>>>
>>>
https://bitbucket.org
Hi!
On Mon, Feb 6, 2017 at 3:39 AM, Aleksander Morgado
wrote:
>
> Hey,
>
> >> > Can you help me understand how I can check this?
> >>
> >> Did you use my openwrt feed without modifications? If so you're
> >> probably building 0bf4db6561de9be61028eb6bc1792a3b7cc410b5:
> >>
> >> https://bitbucket.o
Do you know of any method to send an "ifup broadband" whenever this is
logged?
7 daemon.info [1096]: Modem /org/freedesktop/ModemManager1/Modem/0:
state changed (connected -> registered)
It seems that any band change or drop produces this and an ifup broadband
is needed to bring it back. A pin
Hi,
On Mon, Feb 6, 2017 at 3:39 AM, Aleksander Morgado
wrote:
> Hey,
>
>>> > Can you help me understand how I can check this?
>>>
>>> Did you use my openwrt feed without modifications? If so you're
>>> probably building 0bf4db6561de9be61028eb6bc1792a3b7cc410b5:
>>>
>>>
https://bitbucket.org/aleks
On 2017-02-06 11:06 AM, Bjørn Mork wrote:
> I'm using a hackish hook like this to let gpsd autmatically do the
> $GPS_START and $GPS_STOP as required.
Thank you for proving that, it seems to work great!
A.
--
Adam Sherman
signature.asc
Description: OpenPGP digital signature
On 2017-02-06 02:08 PM, Adam Sherman wrote:
> In this test, qmi-proxy did not deadlock. I rill try again right now.
I think I can reproduce it by sending the AT command to start GPS to the
TTY. Log of that, attached.
A.
--
Adam Sherman
qmi-proxy.log.bz2
Description: application/bzip
On 2017-02-06 11:28 AM, Aleksander Morgado wrote:
>> At some point after adding the rule change, qmi-proxy seems to peg one
>> of my cores basically forever. Is there a log I could look at to
>> troubleshoot this?
> Can you try to manually run the qmi-proxy?
>
> $ sudo systemctl stop ModemManager
On Mon, Feb 6, 2017 at 5:19 PM, Adam Sherman wrote:
> Sorry for the flood of emails! I'm trying to convey information as it
> comes along.
> On 2017-02-06 10:54 AM, Adam Sherman wrote:
>>> Output of mmcli shows ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), cdc-wdm0
>>> (qmi), wwp0s20u4i8 (net)'.
>> After
Sorry for the flood of emails! I'm trying to convey information as it
comes along.
On 2017-02-06 10:54 AM, Adam Sherman wrote:
>> Output of mmcli shows ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), cdc-wdm0
>> (qmi), wwp0s20u4i8 (net)'.
> After adding the udev rules, mmcli shows ports: 'ttyUSB0 (unknown),
Adam Sherman writes:
> On 2017-02-06 09:20 AM, Adam Sherman wrote:
>> Output of mmcli shows ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), cdc-wdm0
>> (qmi), wwp0s20u4i8 (net)'.
>
> After adding the udev rules, mmcli shows ports: 'ttyUSB0 (unknown),
> ttyUSB1 (unknown), ttyUSB2 (unknown), cdc-wdm0 (qmi), w
On 2017-02-06 09:40 AM, Adam Sherman wrote:
>> Output of mmcli shows ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), cdc-wdm0
>> (qmi), wwp0s20u4i8 (net)'.
> After adding the udev rules, mmcli shows ports: 'ttyUSB0 (unknown),
> ttyUSB1 (unknown), ttyUSB2 (unknown), cdc-wdm0 (qmi), wwp0s20u4i8
> (net)'. Notab
On 2017-02-06 09:20 AM, Adam Sherman wrote:
> Output of mmcli shows ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), cdc-wdm0
> (qmi), wwp0s20u4i8 (net)'.
After adding the udev rules, mmcli shows ports: 'ttyUSB0 (unknown),
ttyUSB1 (unknown), ttyUSB2 (unknown), cdc-wdm0 (qmi), wwp0s20u4i8
(net)'. Notable is t
On 2017-02-06 07:42 AM, Aleksander Morgado wrote:
> No, there is a way to do that, enabling the GPS receiver with AT
> commands and processing the NMEA traces received from another TTY; it
> just isn't implemented in ModemManager. We could implement the
> "unmanaged gps" location su
On Mon, Feb 6, 2017 at 1:35 PM, Adam Sherman wrote:
> So, am I understanding correctly that there is no way to get GPS data
> via a serial device, with this card?
>
No, there is a way to do that, enabling the GPS receiver with AT
commands and processing the NMEA traces receiv
On 2017-02-06 07:31 AM, Aleksander Morgado wrote:
So, am I understanding correctly that there is no way to get GPS data
via a serial device, with this card?
>>> No, there is a way to do that, enabling the GPS receiver with AT
>>> commands and processing the NMEA traces received from
On Mon, Feb 6, 2017 at 1:24 PM, Adam Sherman wrote:
>>> So, am I understanding correctly that there is no way to get GPS data
>>> via a serial device, with this card?
>>>
>> No, there is a way to do that, enabling the GPS receiver with AT
>> commands and processing the NMEA traces received from an
On 2017-02-06 07:17 AM, Aleksander Morgado wrote:
>> So, am I understanding correctly that there is no way to get GPS data
>> via a serial device, with this card?
>>
> No, there is a way to do that, enabling the GPS receiver with AT
> commands and processing the NMEA traces received from another TT
On Mon, Feb 6, 2017 at 1:00 PM, Adam Sherman wrote:
> On 2017-02-06 04:21 AM, Aleksander Morgado wrote:
>>> The primary port was cdc-wdm0 in my previous message. What is changing?
>>> And I never seem to get the nice data I put in my previous messages.
>>>
>> Looks like QMI probing failed and MM d
On 2017-02-06 04:21 AM, Aleksander Morgado wrote:
>> The primary port was cdc-wdm0 in my previous message. What is changing?
>> And I never seem to get the nice data I put in my previous messages.
>>
> Looks like QMI probing failed and MM didn't grab the cdc-wdm port?
>
>>
>> So, as an attempt an
On Mon, Feb 6, 2017 at 5:10 AM, Adam Sherman wrote:
> On 2017-02-05 10:32 PM, matthew stanger wrote:
>> First check to make sure you can get GPS location and not just 3gpp
>> location, i.e. location from just the cell tower.
>
> Building on my previous message, I restarted the system to see how it
On Mon, Feb 6, 2017 at 4:48 AM, Adam Sherman wrote:
> On 2017-02-05 10:32 PM, matthew stanger wrote:
>> First check to make sure you can get GPS location and not just 3gpp
>> location, i.e. location from just the cell tower. Run 'mmcli -m 0
>> --location-status' and check capabilities. You'll want
On Mon, Feb 6, 2017 at 4:32 AM, matthew stanger wrote:
> If you see more than the 3gpp option then you should be able to run 'sudo
> mmcli -m 0 --location-enable-gps-raw'. This will setup the GPS but keep MM
> from grabbing the GPS stream.
That is not right. With GPS we have 3 sources that you ca
Hey,
>> > Can you help me understand how I can check this?
>>
>> Did you use my openwrt feed without modifications? If so you're
>> probably building 0bf4db6561de9be61028eb6bc1792a3b7cc410b5:
>>
>> https://bitbucket.org/aleksander0m/modemmanager-openwrt/src/a840e8174cfe2ba80e89147f92f48a718dc31a9c
23 matches
Mail list logo
