able. Are there any
> > additional benefits in the newer versions regarding this issue?
>
> Well, those versions are extremely old. Please upgrade to the newest
> ones and retry, to avoid any possible issue that may already have been
> fixed. Those upgrades should be 100% compatible.
Upgrade done, but it's unrelated.
Behaves the same on the new libs, but should be fixed by calling
ifdown. In testing as we speak.
--
Regards
Einar Jón
> --
> Aleksander
> https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
eason (1008): 'gsm-wcdma-regular-deactivation'
Aug 6 08:08:14 armxl ModemManager[932]: bearer verbose call
end reason (6,36): [3gpp] regular-deactivation
Aug 6 08:08:22 armxl ModemManager[932]: Modem
/org/freedesktop/ModemManager1/Modem/0: state changed (registered ->
? -> 'UnlockRequired'
# Testing Subscriber Identity
AT+CIMI
# Testing error level setting
AT+CMEE=2
# Testing Antenna Power
AT+CIND?
# Testing check power mode
AT+CFUN? 'PowerState'
# Testing Signal Power
AT+RSCP?
# Testing Signal Quality
AT+CSQ -> 'SignalQ
ll the letters in
"@T*BFLH" are off by one, except T.
In ascii, T is the only letter that is even.
So minicom sems to be zeroing out the last bit of your messages, (A =
ascii 0x41 -> ascii 0x40 = @ and I = ascii 0x49 -> ascii 0x48 -> I).
That's the "what", but I
Hi
Sorry for the late response. I only get the digest and don't follow
all the topics. See below.
Regards
Einar Jón
+31 610 957234
On 7 April 2017 at 10:41,
wrote:
>2. Re: ModemManager: symbol lookup error: ModemManager:
> undefined symbol: mm_kernel_event_properti
On 23 March 2017 at 02:42, Dan Williams wrote:
> On Wed, 2017-03-22 at 21:36 +0100, Einar Jón wrote:
>> On 20 March 2017 at 19:33, Dan Williams wrote:
>> > On Mon, 2017-03-20 at 12:14 +0100, Einar Jón wrote:
>> >
>> > > 4) Is ModemManager 1.4.10 too old?
unch of ttyUSB ports in the System
section of mmcli -m 0:
System | device:
'/sys/devices/pci:00/:00:17.0/:01:00.0/:02:08.3/usb2/2-3'
|drivers: 'qmi_wwan, option1'
| plugin: 'Generic'
| primary
Get data bearer technology
--wds-get-current-data-bearer-technology
Get current data bearer technology
--wds-get-profile-list=[3gpp|3gpp2]
Get profile list
--wds-get-default-settings=[3gpp|3gpp2]
Get default settings
--wds-reset
Reset the service state
--wds-noop
Just allocate or release a WDS client. Use with
`--client-no-release-cid' and/or `--client-cid'
Thanks for the help so far,
Einar Jón
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
2/2-3'
2) There's also a Control Signal Pin PERST# on the UC20 Mini PCIe board:
- You can reset the module by driving the PERST# to a low level
voltage of more than 150ms and then release it.
Messing with the pins seems a bit drastic...
3) Rebooting the linux machine als
TLDR: I guess most of my problems are from calling ifup in the wrong
state (CONNECTING instead of CONNECTED). More inline.
I might bring some follow-up questions next week.
On 20 March 2017 at 19:33, Dan Williams wrote:
> On Mon, 2017-03-20 at 12:14 +0100, Einar Jón wrote:
>> Hello,
&
Ubuntu 12.04 with kernel 3.13.0-57-generic
CPU : Intel(R) Atom(TM) CPU E680 @ 1.60GHz
using qmi_wwan, cdc_wdm kernel modules
ModemManager 1.4.10
$ mmcli -m 0
/org/freedesktop/ModemManager1/Modem/0 (device id '4dd8d723ec[...]')
----------
11 matches
Mail list logo
