RE: ModemManager: symbol lookup error: ModemManager: undefined symbol: mm_kernel_event_properties_get_type
Hello Aleksander,
I have used ./configure --with-qmi=yes than make and make install and I have
run ModemManager with a command ModemManager --debug. Am I missing any other
option in ./configure? Thank you for your help.
Jan Graczyk
-Original Message-
From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
Sent: Thursday, April 6, 2017 12:21 PM
To: Jan Graczyk <j...@nytec.com>; modemmanager-devel@lists.freedesktop.org
Subject: Re: ModemManager: symbol lookup error: ModemManager: undefined symbol:
mm_kernel_event_properties_get_type
On 06/04/17 21:14, Jan Graczyk wrote:
> I am using Quectel UC20 mini PCIe modem on my development board and running
> ModemManager on it. Since ModemManager is using by default baud rate set to
> 57600 I have decided to move to the latest version of ModemManager (1.7.0)
> since there is a possibility to set udev rule for baud rate
> ENV{ID_MM_TTY_BAUDRATE}="115200". However after rebuilding ModemManager
> version 1.7.0 for ARM architecture and running it on my development board I
> have got the following error:
>
> ModemManager[1624]: [1491504870.296599]
> [mm-plugin-manager.c:1609] load_plugins(): [plugin manager]
> successfully loaded 32 plugins
> ModemManager[1624]: [1491504870.304070] [main.c:106]
> name_acquired_cb(): Service name 'org.freedesktop.ModemManager1' was
> acquired
> ModemManager[1624]: [1491504870.636683] [mm-base-manager.c:573]
> mm_base_manager_start(): Starting automatic device scan...
> ModemManager[1624]: [1491504870.720354] [mm-base-manager.c:575]
> mm_base_manager_start(): Finished device scan...
> ModemManager: symbol lookup error: ModemManager: undefined symbol:
> mm_kernel_event_properties_get_type
>
> [1]+ Exit 127ModemManager -debug
>
> The only stable version of ModemManager which runs on my development board is
> 1.4.0. But when using that version I need to set Quectel UC20 modem baud rate
> to 57600 using AT+IPR=57600 command. I would like to take advantage of
> ModemManager version 1.7.0 but unfortunately I am getting the above error
> while running it.
Looks like you didn't install the newly compiled version properly.
You're running the ModemManager daemon from git master, and looks like it's
linking to "libmm-glib" from an older version.
How did you configure ModemManager to build, and how are you running it?
--
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
ModemManager: symbol lookup error: ModemManager: undefined symbol: mm_kernel_event_properties_get_type
Hello All,
I am using Quectel UC20 mini PCIe modem on my development board and running
ModemManager on it. Since ModemManager is using by default baud rate set to
57600 I have decided to move to the latest version of ModemManager (1.7.0)
since there is a possibility to set udev rule for baud rate
ENV{ID_MM_TTY_BAUDRATE}="115200". However after rebuilding ModemManager version
1.7.0 for ARM architecture and running it on my development board I have got
the following error:
ModemManager[1624]: [1491504870.296599] [mm-plugin-manager.c:1609]
load_plugins(): [plugin manager] successfully loaded 32 plugins
ModemManager[1624]: [1491504870.304070] [main.c:106]
name_acquired_cb(): Service name 'org.freedesktop.ModemManager1' was acquired
ModemManager[1624]: [1491504870.636683] [mm-base-manager.c:573]
mm_base_manager_start(): Starting automatic device scan...
ModemManager[1624]: [1491504870.720354] [mm-base-manager.c:575]
mm_base_manager_start(): Finished device scan...
ModemManager: symbol lookup error: ModemManager: undefined symbol:
mm_kernel_event_properties_get_type
[1]+ Exit 127ModemManager -debug
The only stable version of ModemManager which runs on my development board is
1.4.0. But when using that version I need to set Quectel UC20 modem baud rate
to 57600 using AT+IPR=57600 command. I would like to take advantage of
ModemManager version 1.7.0 but unfortunately I am getting the above error while
running it.
Best Regards,
Jan Graczyk
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
RE: Failed to find primary AT port
Hello Dan, I have built ModemManager1.4.0 (only this version is running properly on Quectel UC20 modem currently) for ARM architecture with your suggestions: > The UC20 should be using QMI, not AT ports. qmi_wwan support for the > UC20 has been there since 2013. But to use it, you need to: > > 1) ensure qmi_wwan has been built for your kernel > 2) ensure you build ModemManager with libqmi support (--with-qmi=yes) However after executing these commands: mmcli -m 0 --simple-disconnect mmcli -m 0 --simple-connect="pin=1234,apn=internet" I am still getting the message: "Failed to find primary AT port" What else need to be done to fix this problem? Best Regards, Jan Graczyk -Original Message- From: Dan Williams [mailto:d...@redhat.com] Sent: Wednesday, April 5, 2017 10:58 AM To: Jan Graczyk <j...@nytec.com> Cc: modemmanager-devel@lists.freedesktop.org Subject: Re: Failed to find primary AT port On Wed, 2017-04-05 at 17:29 +, Jan Graczyk wrote: > Hello Dan, > > Is ModemManager baud rate configurable to a different value? I know > that by default ModemManager runs properly with modem baud rate set to > 57600. Aleksander committed a patch two weeks ago that allow configuring 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] > Sent: Tuesday, April 4, 2017 12:19 PM > To: Jan Graczyk <j...@nytec.com> > Cc: modemmanager-devel@lists.freedesktop.org > Subject: Re: Failed to find primary AT port > > On Tue, 2017-04-04 at 18:45 +, Jan Graczyk wrote: > > Hello All, > > > > I am trying to build ModemManager for ARM architecture. However > > during the compilation I have got the following problem: > > > > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02- > > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux- > > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find > > -lgmodule-2.0 > > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02- > > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux- > > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find > > -lgio-2.0 > > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02- > > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux- > > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find > > -lgobject-2.0 > > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02- > > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux- > > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find > > -lglib-2.0 > > > > How can I resolve this problem? I appreciate your help very much. > > You need to install neccesary build dependencies for your chosen > architecture too. Looks like you're missing glib and its associated > libraries for ARM installed in the cross-compile library directory. > > Dan > > > Jan Graczyk > > > > -Original Message- > > From: Jan Graczyk > > Sent: Monday, April 3, 2017 2:27 PM > > To: 'Dan Williams' <d...@redhat.com> > > Cc: modemmanager-devel@lists.freedesktop.org > > Subject: RE: Failed to find primary AT port > > > > Hello Dan, > > > > Thank you for your response. The next question I have for you is how > > to cross compile ModemManager for ARM architecture. I am using > > ModemManager version 1.4.2 to build. Is that version stable enough > > to run on ARM based processor? The version of ModemManager on my > > target is 1.4.0 and it is working well. > > > > Best Regards, > > > > Jan Graczyk > > > > -Original Message- > > From: Dan Williams [mailto:d...@redhat.com] > > Sent: Friday, March 31, 2017 3:15 PM > > To: Jan Graczyk <j...@nytec.com> > > Cc: modemmanager-devel@lists.freedesktop.org > > Subject: Re: Failed to find primary AT port > > > > On Fri, 2017-03-31 at 21:09 +, Jan Graczyk wrote: > > > Hello Dan, > > > > > > There is no problem with connecting to this modem (mini PCIe > > > Quectel > > > UC20 modem module) from kermit and sending AT commands. However > > > when I issue the following commands: > > > > > > mmcli -m 0 --simple-disconnect > > > mmcli -m 0 --simple-connect="pin=1234,apn=internet" > > > > > > the ModemManager sends debug message "Failed to find primary AT > > > port" > &g
RE: Failed to find primary AT port
Hello Dan,
Thank you for your response. I have looked into ModemManager version 1.6.4 and
this patch you are mentioning in your e-mail does not reflect the line number
in src/mm-base-modem.c:
@@ -219,6 +219,12 @@ mm_base_modem_grab_port (MMBaseModem *self,
"timed-out",
G_CALLBACK (serial_port_timed_out_cb),
self);
+
+/* For serial ports, optionally use a specific baudrate */
+if (mm_kernel_device_has_property (kernel_device,
"ID_MM_TTY_BAUDRATE"))
+g_object_set (port,
+ MM_PORT_SERIAL_BAUD,
mm_kernel_device_get_property_as_int (kernel_device, "ID_MM_TTY_BAUDRATE"),
+ NULL);
}
/* Net ports... */
else if (g_str_equal (subsys, "net")) {
I also have built ModemManager1.6.4 for ARM architecture and run on my
development board. However I am getting the following error:
ModemManager[1631]: [1491431437.689341] [mm-plugin.c:804]
mm_plugin_supports_port(): (Generic) [ttymxc2] probe required: 'at, qcdm'
ModemManager[1631]: [1491431437.689422] [mm-port-probe.c:1376]
mm_port_probe_run(): (tty/ttymxc2) port probing finished: no more probings
needed
ModemManager[1631]: [1491431437.689575] [mm-plugin-manager.c:283]
port_context_supported(): [plugin manager] task 0,ttymxc2: found best plugin
for port (Generic)
ModemManager[1631]: [1491431437.689678] [mm-plugin-manager.c:265]
port_context_complete(): [plugin manager] task 0,ttymxc2: finished in
'10.416165' seconds
ModemManager[1631]: [1491431437.690192] [mm-plugin-manager.c:979]
device_context_continue(): [plugin manager] task 0: no more ports to probe
ModemManager[1631]: [1491431437.690297] [mm-plugin-manager.c:813]
device_context_complete(): [plugin manager] task 0: finished in '10.417578'
seconds
ModemManager[1631]: [1491431437.690453] [mm-device.c:525]
mm_device_create_modem(): Creating modem with plugin 'Generic' and '1' ports
ModemManager: symbol lookup error: ModemManager: undefined symbol:
mm_gdbus_modem_voice_skeleton_get_type
Could you tell me which version of ModemManager I should use?
Best Regards,
Jan Graczyk
-Original Message-
From: Dan Williams [mailto:d...@redhat.com]
Sent: Wednesday, April 5, 2017 10:58 AM
To: Jan Graczyk <j...@nytec.com>
Cc: modemmanager-devel@lists.freedesktop.org
Subject: Re: Failed to find primary AT port
On Wed, 2017-04-05 at 17:29 +, Jan Graczyk wrote:
> Hello Dan,
>
> Is ModemManager baud rate configurable to a different value? I know
> that by default ModemManager runs properly with modem baud rate set to
> 57600.
Aleksander committed a patch two weeks ago that allow configuring 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]
> Sent: Tuesday, April 4, 2017 12:19 PM
> To: Jan Graczyk <j...@nytec.com>
> Cc: modemmanager-devel@lists.freedesktop.org
> Subject: Re: Failed to find primary AT port
>
> On Tue, 2017-04-04 at 18:45 +, Jan Graczyk wrote:
> > Hello All,
> >
> > I am trying to build ModemManager for ARM architecture. However
> > during the compilation I have got the following problem:
> >
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgmodule-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgio-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgobject-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lglib-2.0
> >
> > How can I resolve this problem? I appreciate your help very much.
>
> You need to install neccesary build dependencies for your chosen
> architecture too. Looks like you're missing glib and its associated
> libraries for ARM installed in the cross-compile library directory.
>
> Dan
>
> > Jan Graczyk
> >
> > -Original Message-
> > From: Jan Graczyk
> > Sent: Monday, April 3, 2017 2:27 PM
> > To: 'Dan Williams' <d...@redha
RE: Failed to find primary AT port
Hello Dan, Is ModemManager baud rate configurable to a different value? I know that by default ModemManager runs properly with modem baud rate set to 57600. Best Regards, Jan Graczyk -Original Message- From: Dan Williams [mailto:d...@redhat.com] Sent: Tuesday, April 4, 2017 12:19 PM To: Jan Graczyk <j...@nytec.com> Cc: modemmanager-devel@lists.freedesktop.org Subject: Re: Failed to find primary AT port On Tue, 2017-04-04 at 18:45 +0000, Jan Graczyk wrote: > Hello All, > > I am trying to build ModemManager for ARM architecture. However during > the compilation I have got the following problem: > > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02- > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux- > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find > -lgmodule-2.0 > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02- > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux- > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find > -lgio-2.0 > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02- > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux- > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find > -lgobject-2.0 > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02- > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux- > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find > -lglib-2.0 > > How can I resolve this problem? I appreciate your help very much. You need to install neccesary build dependencies for your chosen architecture too. Looks like you're missing glib and its associated libraries for ARM installed in the cross-compile library directory. Dan > Jan Graczyk > > -Original Message- > From: Jan Graczyk > Sent: Monday, April 3, 2017 2:27 PM > To: 'Dan Williams' <d...@redhat.com> > Cc: modemmanager-devel@lists.freedesktop.org > Subject: RE: Failed to find primary AT port > > Hello Dan, > > Thank you for your response. The next question I have for you is how > to cross compile ModemManager for ARM architecture. I am using > ModemManager version 1.4.2 to build. Is that version stable enough to > run on ARM based processor? The version of ModemManager on my target > is 1.4.0 and it is working well. > > Best Regards, > > Jan Graczyk > > -Original Message- > From: Dan Williams [mailto:d...@redhat.com] > Sent: Friday, March 31, 2017 3:15 PM > To: Jan Graczyk <j...@nytec.com> > Cc: modemmanager-devel@lists.freedesktop.org > Subject: Re: Failed to find primary AT port > > On Fri, 2017-03-31 at 21:09 +, Jan Graczyk wrote: > > Hello Dan, > > > > There is no problem with connecting to this modem (mini PCIe Quectel > > UC20 modem module) from kermit and sending AT commands. However when > > I issue the following commands: > > > > mmcli -m 0 --simple-disconnect > > mmcli -m 0 --simple-connect="pin=1234,apn=internet" > > > > the ModemManager sends debug message "Failed to find primary AT > > port" > > to Linux console. However if I will power down and power up the > > development board the ModemManager starts running properly. The > > problem only happen when I issue the above disconnect and then > > connect command. > > The UC20 should be using QMI, not AT ports. qmi_wwan support for the > UC20 has been there since 2013. But to use it, you need to: > > 1) ensure qmi_wwan has been built for your kernel > 2) ensure you build ModemManager 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: Jan Graczyk <j...@nytec.com>; modemmanager-devel@lists.freedesk > > to p.org > > Subject: 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 with 'minicom' on that port when > > ModemManager isn't running? > > > > Dan > > > > > root@linaro-alip:~# ModemManager --debug& [1] 1574 root@linaro-al > > > ip :~# > > > ModemManager[1574]: [1490989871.011
RE: Failed to find primary AT port
Hello Dan, Thank you for your response. The next question I have for you is how to cross compile ModemManager for ARM architecture. I am using ModemManager version 1.4.2 to build. Is that version stable enough to run on ARM based processor? The version of ModemManager on my target is 1.4.0 and it is working well. Best Regards, Jan Graczyk -Original Message- From: Dan Williams [mailto:d...@redhat.com] Sent: Friday, March 31, 2017 3:15 PM To: Jan Graczyk <j...@nytec.com> Cc: modemmanager-devel@lists.freedesktop.org Subject: Re: Failed to find primary AT port On Fri, 2017-03-31 at 21:09 +0000, Jan Graczyk wrote: > Hello Dan, > > There is no problem with connecting to this modem (mini PCIe Quectel > UC20 modem module) from kermit and sending AT commands. However when I > issue the following commands: > > mmcli -m 0 --simple-disconnect > mmcli -m 0 --simple-connect="pin=1234,apn=internet" > > the ModemManager sends debug message "Failed to find primary AT port" > to Linux console. However if I will power down and power up the > development board the ModemManager starts running properly. The > problem only happen when I issue the above disconnect and then connect > command. The UC20 should be using QMI, not AT ports. qmi_wwan support for the UC20 has been there since 2013. But to use it, you need to: 1) ensure qmi_wwan has been built for your kernel 2) ensure you build ModemManager 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: Jan Graczyk <j...@nytec.com>; modemmanager-devel@lists.freedeskto > p.org > Subject: 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 with 'minicom' on that port when > ModemManager isn't running? > > Dan > > > root@linaro-alip:~# ModemManager --debug& [1] 1574 root@linaro-alip > > :~# > > ModemManager[1574]: [1490989871.011911] [main.c:140] > > main(): > > ModemManager (version 1.4.0) starting in system bus... > > ModemManager[1574]: [1490989871.035558] [main.c:65] > > bus_acquired_cb(): Bus acquired, creating manager... > > ModemManager[1574]: [1490989871.047317] [mm-plugin- > > manager.c:852] load_plugins(): Looking for plugins in > > '/usr/lib/arm- > > linux-gnueabihf/ModemManager' > > ModemManager[1574]: [1490989871.049618] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Option' > > ModemManager[1574]: [1490989871.051062] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Novatel LTE' > > ModemManager[1574]: [1490989871.052389] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Linktop' > > ModemManager[1574]: [1490989871.053841] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Samsung' > > ModemManager[1574]: [1490989871.055357] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Sierra' > > ModemManager[1574]: [1490989871.056738] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Gobi' > > ModemManager[1574]: [1490989871.058087] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'X22X' > > ModemManager[1574]: [1490989871.059471] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'MTK' > > ModemManager[1574]: [1490989871.060811] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'AnyDATA' > > ModemManager[1574]: [1490989871.062214] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Pantech' > > ModemManager[1574]: [1490989871.063564] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Novatel' > > ModemManager[1574]: [1490989871.065070] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Nokia' > > ModemManager[1574]: [1490989871.066426] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Motorola' > > ModemManager[1574]: [1490989871.067906] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Huawei' > > ModemManager[1574]: [1490989871.069276] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'SimTech' > > ModemManager[1574]: [1490989871.070701] [mm-plugin- > > manager.c:877] load_plugins(): Loaded plugin 'Option High-Speed' >
RE: Failed to find primary AT port
Hello Dan, There is no problem with connecting to this modem (mini PCIe Quectel UC20 modem module) from kermit and sending AT commands. However when I issue the following commands: mmcli -m 0 --simple-disconnect mmcli -m 0 --simple-connect="pin=1234,apn=internet" the ModemManager sends debug message "Failed to find primary AT port" to Linux console. However if I will power down and power up the development board the ModemManager starts running properly. The problem only happen when I issue the above disconnect and then connect command. Best Regards, Jan Graczyk -Original Message- From: Dan Williams [mailto:d...@redhat.com] Sent: Friday, March 31, 2017 1:51 PM To: Jan Graczyk <j...@nytec.com>; modemmanager-devel@lists.freedesktop.org Subject: 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 with 'minicom' on that port when ModemManager isn't running? Dan > root@linaro-alip:~# ModemManager --debug& [1] 1574 root@linaro-alip:~# > ModemManager[1574]: [1490989871.011911] [main.c:140] main(): > ModemManager (version 1.4.0) starting in system bus... > ModemManager[1574]: [1490989871.035558] [main.c:65] > bus_acquired_cb(): Bus acquired, creating manager... > ModemManager[1574]: [1490989871.047317] [mm-plugin- > manager.c:852] load_plugins(): Looking for plugins in '/usr/lib/arm- > linux-gnueabihf/ModemManager' > ModemManager[1574]: [1490989871.049618] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Option' > ModemManager[1574]: [1490989871.051062] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Novatel LTE' > ModemManager[1574]: [1490989871.052389] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Linktop' > ModemManager[1574]: [1490989871.053841] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Samsung' > ModemManager[1574]: [1490989871.055357] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Sierra' > ModemManager[1574]: [1490989871.056738] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Gobi' > ModemManager[1574]: [1490989871.058087] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'X22X' > ModemManager[1574]: [1490989871.059471] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'MTK' > ModemManager[1574]: [1490989871.060811] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'AnyDATA' > ModemManager[1574]: [1490989871.062214] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Pantech' > ModemManager[1574]: [1490989871.063564] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Novatel' > ModemManager[1574]: [1490989871.065070] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Nokia' > ModemManager[1574]: [1490989871.066426] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Motorola' > ModemManager[1574]: [1490989871.067906] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Huawei' > ModemManager[1574]: [1490989871.069276] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'SimTech' > ModemManager[1574]: [1490989871.070701] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Option High-Speed' > ModemManager[1574]: [1490989871.072078] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Generic' > ModemManager[1574]: [1490989871.073583] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Iridium' > ModemManager[1574]: [1490989871.075071] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Altair LTE' > ModemManager[1574]: [1490989871.076609] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Cinterion' > ModemManager[1574]: [1490989871.078085] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Via CBP7' > ModemManager[1574]: [1490989871.079495] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Telit' > ModemManager[1574]: [1490989871.081009] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'ZTE' > ModemManager[1574]: [1490989871.082448] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Wavecom' > ModemManager[1574]: [1490989871.083927] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Longcheer' > ModemManager[1574]: [1490989871.085477] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Nokia (Icera)' > ModemManager[1574]: [1490989871.086972] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Ericsson MBM' > ModemManager[1574]: [1490989871.087122] [mm
Failed to find primary AT port
or device at '/sys/devices/soc0/soc/210.aips-bus/21ec000.serial': Failed to find primary AT port Anyone has an idea why this is happening? I appreciate very much a help from you. Best Regards, Jan Graczyk ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Couldn't refresh signal quality: 'Serial command timed out'
Hello All, I have a problem with getting the proper signal level from ModemManager. Here is the Linux console output from ModemManager -debug session: ModemManager[1580]: [1490979773.483400] [mm-broadband-modem.c:1991] modem_load_signal_quality(): loading signal quality... ModemManager[1580]: [1490979773.483759] [mm-port-serial.c:1237] mm_port_serial_open(): (ttymxc2) device open count is 2 (open) ModemManager[1580]: [1490979773.484146] [mm-port-serial-at.c:440] debug_log(): (ttymxc2): --> 'AT+CIND?' ModemManager[1580]: [1490979776.462143] [mm-port-serial.c:1237] mm_port_serial_open(): (ttymxc2) device open count is 3 (open) ModemManager[1580]: [1490979776.462543] [mm-port-serial.c:1296] mm_port_serial_close(): (ttymxc2) device open count is 2 (close) ModemManager[1580]: [1490979776.462821] [mm-port-serial-at.c:440] debug_log(): (ttymxc2): --> 'AT+CSQ' ModemManager[1580]: [1490979779.462935] [mm-port-serial.c:1296] mm_port_serial_close(): (ttymxc2) device open count is 1 (close) ModemManager[1580]: [1490979779.463338] [mm-iface-modem.c:1221] signal_quality_check_ready(): Couldn't refresh signal quality: 'Serial command timed out' This happen when I have issued the following command to ModemManager: mmcli -m 0 --simple-disconnect The command: mmcli -m 0 --simple-connect="pin=1234,apn=internet" does not bring the ModemManager back to receive proper signal quality. What I need to do to get ModemManager properly detecting signal quality? In order to get ModemManager updating signal quality I needed to power down and power up the development board. Best Regards, Jan Graczyk ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
No SIM card inserted
Hello All, I am working on a development board which has mini PCIe based QUECTEL UC20 modem card. Unfortunately the modem AT command AT+CPIN? returns SIM not inserted. Anyone has come across this problem? Thank you for your support. Best Regards, Jan Graczyk ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
RE: mmcli -m 0 -e command fails
Hello All, The command AT+GCAP? returns ERROR. Also the AT command AT+CPIN? Returns +CME ERROR: SIM not inserted. I am checking whether the SIM card I am using is working or there is a development board hardware issue. Jan Graczyk -Original Message- From: Dan Williams [mailto:d...@redhat.com] Sent: Wednesday, March 22, 2017 7:03 PM To: Jan Graczyk <j...@nytec.com>; Aleksander Morgado <aleksan...@aleksander.es> Cc: modemmanager-devel@lists.freedesktop.org Subject: 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. mm_port_serial_close(): (ttymxc2) device open count is 2 (close) debug_l og(): (ttymxc2): --> 'AT+GCAP' debug_log(): (ttymxc2): <-- 'ERROR' mm_serial_parser_v1_parse(): Got failure code 100: Unknown error debug_log(): (ttymxc2): --> 'ATI' debug_log(): (ttymxc2): <-- 'QuectelUC20Revision: UC20GQBR03A14E1GOK' debug_log(): (ttymxc2): --> 'AT+CPIN?' debug_log(): (ttymxc2): <-- '+CME ERROR: 10' mm_serial_parser_v1_parse(): Got failure code 10: SIM not inserted debug_log(): (ttymxc2): --> 'AT+CGMM' debug_log(): (ttymxc2): <-- 'UC20OK' This could be due to the SIM failure. But you could you run minicom or something and manually run "AT+GCAP" and "AT+GCAP?" for us? Dan > Best Regards, > Jan Graczyk > > -Original Message- > From: ModemManager-devel [mailto:modemmanager-devel-boun...@lists.fre > edesktop.org] On Behalf Of Aleksander Morgado > Sent: Wednesday, March 22, 2017 4:55 PM > To: Jan Graczyk <j...@nytec.com> > Cc: modemmanager-devel@lists.freedesktop.org > Subject: Re: mmcli -m 0 -e command fails > > Hey Jan, > > On Thu, Mar 23, 2017 at 12:46 AM, Jan Graczyk <j...@nytec.com> wrote: > > But there I another problem with mmcli ‘enable’ command. Here is the > > output: > > > > > > > > root@linaro-alip:~# mmcli -m 0 > > > > > > > > /org/freedesktop/ModemManager1/Modem/0 (device id 'unknown') > > > > - > > > > Hardware | manufacturer: 'unknown' > > > > | model: 'unknown' > > > > | revision: 'unknown' > > > > | supported: 'none' > > > > |current: 'none' > > > > | equipment id: 'unknown' > > > > This is bad, it couldn't load any of the HW information. > > > - > > > > System | device: > > '/sys/devices/soc0/soc/210.aips-bus/21ec000.serial' > > > > |drivers: 'imx-uart' > > > > | plugin: 'Generic' > > > > | primary port: 'ttymxc2' > > > > | ports: 'ttymxc2 (at)' > > > > - > > > > Numbers | own : 'unknown' > > > > - > > > > Status | lock: 'unknown' > > > > | unlock retries: 'unknown' > > > > | state: 'unknown' > > > > |power state: 'unknown' > > > > |access tech: 'unknown' > > > > | signal quality: '0' (cached) > > > > Bad bad, there really wasn't anything loaded at all... > > > - > > > > Modes| supported: 'allowed: any; preferred: none' > > > > |current: 'allowed: any; preferred: none' > > > > - > > > > Bands| supported: 'unknown' > > > > |current: 'unknown' > > > > - > > > > IP | supported: 'none' > > > > - > > > > SIM | path: 'none' > > > > > > > > - > > > > Bearers | paths: 'none' > > > > > > > > root@linaro-alip:~# > > > > root@linaro-alip:~# > > > > root@linaro-alip:~# mmcli -m 0 -e > > > > error: couldn't enable the modem: > > 'GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method Enable > > is not implemented on interface org.freedesktop.ModemManager1.Modem' > > > > root@linaro-alip:~# > > > &g
RE: mmcli -m 0 -e command fails
Hello Aleksander, I have attached a file with the logs from ModemManager --debug command. Best Regards, Jan Graczyk -Original Message- From: ModemManager-devel [mailto:modemmanager-devel-boun...@lists.freedesktop.org] On Behalf Of Aleksander Morgado Sent: Wednesday, March 22, 2017 4:55 PM To: Jan Graczyk <j...@nytec.com> Cc: modemmanager-devel@lists.freedesktop.org Subject: Re: mmcli -m 0 -e command fails Hey Jan, On Thu, Mar 23, 2017 at 12:46 AM, Jan Graczyk <j...@nytec.com> wrote: > But there I another problem with mmcli ‘enable’ command. Here is the output: > > > > root@linaro-alip:~# mmcli -m 0 > > > > /org/freedesktop/ModemManager1/Modem/0 (device id 'unknown') > > - > > Hardware | manufacturer: 'unknown' > >| model: 'unknown' > >| revision: 'unknown' > >| supported: 'none' > >|current: 'none' > >| equipment id: 'unknown' > This is bad, it couldn't load any of the HW information. > - > > System | device: > '/sys/devices/soc0/soc/210.aips-bus/21ec000.serial' > >|drivers: 'imx-uart' > >| plugin: 'Generic' > >| primary port: 'ttymxc2' > >| ports: 'ttymxc2 (at)' > > - > > Numbers | own : 'unknown' > > - > > Status | lock: 'unknown' > >| unlock retries: 'unknown' > >| state: 'unknown' > >|power state: 'unknown' > >|access tech: 'unknown' > >| signal quality: '0' (cached) > Bad bad, there really wasn't anything loaded at all... > - > > Modes| supported: 'allowed: any; preferred: none' > >|current: 'allowed: any; preferred: none' > > - > > Bands| supported: 'unknown' > >|current: 'unknown' > > - > > IP | supported: 'none' > > - > > SIM | path: 'none' > > > > - > > Bearers | paths: 'none' > > > > root@linaro-alip:~# > > root@linaro-alip:~# > > root@linaro-alip:~# mmcli -m 0 -e > > error: couldn't enable the modem: > 'GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method Enable > is not implemented on interface org.freedesktop.ModemManager1.Modem' > > root@linaro-alip:~# > > > > Is that there is a problem with SIM card? Not with the SIM card; not yet. Looks like the TTY replied only to AT probing and failed to reply to the remaining commands we sent to e.g. query manufacturer or model; all that is before the SIM card can be used. You'll need to run ModemManager daemon manually with --debug and grab all the debug logs while you reproduce the issue, see: https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/ -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel console Description: console ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
mmcli -m 0 -e command fails
Hello Aleksander, But there I another problem with mmcli 'enable' command. Here is the output: root@linaro-alip:~# mmcli -m 0 /org/freedesktop/ModemManager1/Modem/0 (device id 'unknown') - Hardware | manufacturer: 'unknown' | model: 'unknown' | revision: 'unknown' | supported: 'none' |current: 'none' | equipment id: 'unknown' - System | device: '/sys/devices/soc0/soc/210.aips-bus/21ec000.serial' |drivers: 'imx-uart' | plugin: 'Generic' | primary port: 'ttymxc2' | ports: 'ttymxc2 (at)' - Numbers | own : 'unknown' - Status | lock: 'unknown' | unlock retries: 'unknown' | state: 'unknown' |power state: 'unknown' |access tech: 'unknown' | signal quality: '0' (cached) - Modes| supported: 'allowed: any; preferred: none' |current: 'allowed: any; preferred: none' - Bands| supported: 'unknown' |current: 'unknown' - IP | supported: 'none' - SIM | path: 'none' - Bearers | paths: 'none' root@linaro-alip:~# root@linaro-alip:~# root@linaro-alip:~# mmcli -m 0 -e error: couldn't enable the modem: 'GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method Enable is not implemented on interface org.freedesktop.ModemManager1.Modem' root@linaro-alip:~# Is that there is a problem with SIM card? Best Regards, Jan Graczyk ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
FW: About your ModemManager issue and the emails to the mailng list
From: Aleksander Morgado [mailto:aleksan...@aleksander.es] Sent: Wednesday, March 22, 2017 4:18 PM To: Jan Graczyk <j...@nytec.com> Subject: RE: About your ModemManager issue and the emails to the mailng list Yeah, that is what I suggested you should do a while back :) Could you also reply that to the mailing list for reference, please? On Mar 23, 2017 00:11, "Jan Graczyk" <j...@nytec.com<mailto:j...@nytec.com>> wrote: Hello Aleksander, I finally got connection of ModemManager to modem device /dev/ttymxc2. The problem was that the modem device baud rate should be set to 57600. I have changed the modem device baud rate with AT command AT+IPR=57600. Best Regards, Jan Graczyk This email message may contain confidential and privileged information. Any 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: Aleksander Morgado [mailto:aleksan...@aleksander.es<mailto:aleksan...@aleksander.es>] Sent: Wednesday, March 22, 2017 2:36 PM To: Jan Graczyk <j...@nytec.com<mailto:j...@nytec.com>> Subject: About your ModemManager issue and the emails to the mailng list Hey Jan (off list) Please retest the "mmcli -S" with ModemManager from git master; i.e. built from the "master" branch from this git repository: https://cgit.freedesktop.org/ModemManager/ModemManager And once you have results, post them in a totally new email thread, and let's start from scratch in that new email thread. If you have any question about how to send emails to the mailing list or doubts about the things I asked you to do, please don't hesitate to ask me, I'm glad to help. I'm just here to organize a bit how the mailing list runs, as I said in the other email, not everyone is interested in every email thread, and mixing them is a true mess. Cheers! -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
RE: [PATCH] serial: allow specifying baudrate to use via udev tags
Hello Aleksander, When you are saying not to mix e-mail threads you mean not to reply all? I am only replying to e-mails which are related to my problem. I have done mmcli -S and that command response with "successfully requested to scan devices". Here is the output from ModemManager debug session: ModemManager[1532]: [1490186663.752548] [mm-plugin.c:767] mm_plugin_supports_port(): (Generic) [ttymxc2] probe required: 'at, qcdm' ModemManager[1532]: [1490186663.752733] [mm-port-probe.c:1353] mm_port_probe_run(): (tty/ttymxc2) launching port probing: 'qcdm' ModemManager[1532]: [1490186663.752965] [mm-port-probe.c:658] serial_probe_qcdm(): (tty/ttymxc2) probing QCDM... ModemManager[1532]: [1490186663.753384] [mm-port-serial.c:1099] mm_port_serial_open(): (ttymxc2) opening serial port... ModemManager[1532]: [1490186663.755754] [mm-port-serial.c:1237] mm_port_serial_open(): (ttymxc2) device open count is 1 (open) ModemManager[1532]: [1490186663.756270] [mm-port-serial-qcdm.c:201] debug_log(): (ttymxc2): --> 7e 00 78 f0 7e ModemManager[1532]: [149018.742982] [mm-port-serial-qcdm.c:201] debug_log(): (ttymxc2): --> 7e 00 78 f0 7e ModemManager[1532]: [1490186669.743253] [mm-port-probe.c:258] mm_port_probe_set_result_qcdm(): (tty/ttymxc2) port is not QCDM-capable ModemManager[1532]: [1490186669.746282] [mm-port-serial.c:1296] mm_port_serial_close(): (ttymxc2) device open count is 0 (close) ModemManager[1532]: [1490186669.748909] [mm-port-serial.c:1312] mm_port_serial_close(): (ttymxc2) closing serial port... ModemManager[1532]: [1490186669.759468] [mm-port-serial.c:1361] mm_port_serial_close(): (ttymxc2) serial port closed ModemManager[1532]: [1490186669.759689] [mm-port-serial.c:1415] port_serial_close_force(): (ttymxc2) forced to close port ModemManager[1532]: [1490186669.760001] [mm-plugin-manager.c:462] plugin_supports_port_ready(): (Plugin Manager) (Generic) [ttymxc2] found best plugin for port ModemManager[1532]: [1490186669.760300] [mm-plugin-manager.c:316] port_probe_context_finished(): (Plugin Manager) 'ttymxc2' port probe finished, last one in device ModemManager[1532]: [1490186669.760459] [mm-plugin-manager.c:138] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/soc0/soc/210.aips-bus/21ec000.serial] device support check finished in '15.800204' seconds ModemManager[1532]: [1490186669.760657] [mm-device.c:509] mm_device_create_modem(): Creating modem with plugin 'Generic' and '1' ports ModemManager[1532]: [1490186669.773671] [mm-plugin.c:905] mm_plugin_create_modem(): Could not grab port (tty/ttymxc2): 'Cannot add port 'tty/ttymxc2', unhandled serial type' ModemManager[1532]: [1490186669.774134] [mm-base-modem.c:1485] finalize(): Modem (Generic) '/sys/devices/soc0/soc/210.aips-bus/21ec000.serial' completely disposed ModemManager[1532]: [1490186669.774314] [mm-base-manager.c:158] find_device_support_ready(): Couldn't create modem for device at '/sys/devices/soc0/soc/210.aips-bus/21ec000.serial': Failed to find primary AT port It looks like the ttymxc2 modem port is not QCDM-capable. Is there anything I can do to make it QCDM-capable? The ModemManager software version running on my development board is 1.4.0. Does this make difference? Best Regards, Jan Graczyk This email message may contain confidential and privileged information. Any 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: Aleksander Morgado [mailto:aleksan...@aleksander.es] Sent: Wednesday, March 22, 2017 1:39 AM To: Jan Graczyk <j...@nytec.com> Cc: Dan Williams <d...@redhat.com>; modemmanager-devel@lists.freedesktop.org Subject: Re: [PATCH] serial: allow specifying baudrate to use via udev tags Hey Jan, On Tue, Mar 21, 2017 at 11:16 PM, Jan Graczyk <j...@nytec.com> wrote: > I have tried running ModemManager with /dev/ttymxc2 port set to 57600 baud > rate. It looks like as I can see from ModemManager debug logging the QUECTEL > UC20 device is not recognized. I have looked into the ModemManager supported > devices website > https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/#index2h1 > and there is no support for this device. I would need to create a new plugin > for this device. Maybe, or maybe not. The first step is to have the TTY recognized by ModemManager. If it is an AT port, ModemManager should be able to do basic AT probing there and fallback to the "generic" plugin if it doesn't find any specific plugin. If baudrate is already 57600bps in the modem, and still isn't recognized, it has to be due to some other reason. Try maybe to run "mmcli -S" after some time, so that a manual re-scan is relaunched (but use ModemManager git master to do so, or it may really not work as I
RE: [PATCH] serial: allow specifying baudrate to use via udev tags
Hello Dan,
I have tried running ModemManager with /dev/ttymxc2 port set to 57600 baud
rate. It looks like as I can see from ModemManager debug logging the QUECTEL
UC20 device is not recognized. I have looked into the ModemManager supported
devices website
https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/#index2h1
and there is no support for this device. I would need to create a new plugin
for this device.
Best Regards,
Jan Graczyk
This email message may contain confidential and privileged information. Any
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: ModemManager-devel
[mailto:modemmanager-devel-boun...@lists.freedesktop.org] On Behalf Of Dan
Williams
Sent: Tuesday, March 21, 2017 2:09 PM
To: Aleksander Morgado <aleksan...@aleksander.es>
Cc: modemmanager-devel@lists.freedesktop.org
Subject: 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"
> DEVPATH=="/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/*",
> ENV{ID_MM_TTY_BAUDRATE}="115200"
> LABEL="mm_my_modem_end"
>
> https://bugs.freedesktop.org/show_bug.cgi?id=100158
LGTM.
Dan
> ---
>
> Hey,
>
> How about this patch? It really is a nice thing to have when
> integrating non-USB RS232 modems, as we avoid requiring to stick to
> 57600bps when the device can work perfectly with a much higher
> baudrate.
>
> ---
> src/mm-base-modem.c | 6 +++
> src/mm-port-probe.c | 10 +
> src/mm-port-serial.c | 118 ++---
> --
> 3 files changed, 39 insertions(+), 95 deletions(-)
>
> diff --git a/src/mm-base-modem.c b/src/mm-base-modem.c index
> 50717471..430ce59d 100644
> --- a/src/mm-base-modem.c
> +++ b/src/mm-base-modem.c
> @@ -219,6 +219,12 @@ mm_base_modem_grab_port (MMBaseModem
> *self,
> "timed-out",
> G_CALLBACK (serial_port_timed_out_cb),
> self);
> +
> +/* For serial ports, optionally use a specific baudrate */
> +if (mm_kernel_device_has_property (kernel_device,
> "ID_MM_TTY_BAUDRATE"))
> +g_object_set (port,
> + MM_PORT_SERIAL_BAUD,
> mm_kernel_device_get_property_as_int (kernel_device,
> "ID_MM_TTY_BAUDRATE"),
> + NULL);
> }
> /* Net ports... */
> else if (g_str_equal (subsys, "net")) { diff --git
> a/src/mm-port-probe.c b/src/mm-port-probe.c index f5dc90d2..c6c5897f
> 100644
> --- a/src/mm-port-probe.c
> +++ b/src/mm-port-probe.c
> @@ -712,6 +712,11 @@ serial_probe_qcdm (MMPortProbe *self)
> return G_SOURCE_REMOVE;
> }
>
> +if (mm_kernel_device_has_property (self->priv->port,
> "ID_MM_TTY_BAUDRATE"))
> +g_object_set (ctx->serial,
> + MM_PORT_SERIAL_BAUD,
> mm_kernel_device_get_property_as_int (self->priv->port,
> "ID_MM_TTY_BAUDRATE"),
> + NULL);
> +
> /* Try to open the port */
> if (!mm_port_serial_open (ctx->serial, )) {
> port_probe_task_return_error (self, @@ -1220,6 +1225,11 @@
> serial_open_at (MMPortProbe *self)
> MM_PORT_SERIAL_AT_SEND_LF, ctx-
> >at_send_lf,
> NULL);
>
> +if (mm_kernel_device_has_property (self->priv->port,
> "ID_MM_TTY_BAUDRATE"))
> +g_object_set (ctx->serial,
> + MM_PORT_SERIAL_BAUD,
> mm_kernel_device_get_property_as_int (self->priv->port,
> "ID_MM_TTY_BAUDRATE"),
> + NULL);
> +
> parser = mm_serial_parser_v1_new ();
> mm_serial_parser_v1_add_filter (parser,
> serial_parser_filter_cb, diff
> --git a/src/mm-port-serial.c b/src/mm-port-serial.c index
> 470de031..2b6b92d3 100644
> --- a/src/mm-port-serial.c
> +++ b/src/mm-port-serial.c
> @@ -210,95 +210,13 @@ mm_port_serial_command (MMPortSerial *self,
>
> /***
> **/
>
> -#if 0
> -static const char *
> -baud_to_string (int baud)
> -{
&g
RE: Could not acquire the 'org.freedesktop.ModemManager1' service name
Hello Aleksander, How to set ModemManager baudrate? Best Regards, Jan Graczyk This email message may contain confidential and privileged information. Any 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: Aleksander Morgado [mailto:aleksan...@aleksander.es] Sent: Tuesday, March 21, 2017 1:27 PM To: Jan Graczyk <j...@nytec.com> Cc: Dan Williams <d...@redhat.com>; modemmanager-devel@lists.freedesktop.org Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1' service name On Tue, Mar 21, 2017 at 9:18 PM, Jan Graczyk <j...@nytec.com> wrote: > The baudrate of /dev/ttymxc2 is 115200. That won't work, unless you instruct ModemManager to use that specific baudrate on the TTY. Last week I sent a patch for review to allow that with per-port udev rules, see: https://lists.freedesktop.org/archives/modemmanager-devel/2017-March/004075.html Any comments on that one, btw? You could otherwise change the modem TTY baudrate to 57600bps. -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
RE: Could not acquire the 'org.freedesktop.ModemManager1' service name
Hello Aleksander, The baudrate of /dev/ttymxc2 is 115200. Best Regards, Jan Graczyk This email message may contain confidential and privileged information. Any 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: Aleksander Morgado [mailto:aleksan...@aleksander.es] Sent: Tuesday, March 21, 2017 1:01 PM To: Jan Graczyk <j...@nytec.com> Cc: Dan Williams <d...@redhat.com>; modemmanager-devel@lists.freedesktop.org Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1' service name On Tue, Mar 21, 2017 at 8:56 PM, Jan Graczyk <j...@nytec.com> wrote: > ModemManager[1623]: [1490123698.126826] [mm-port-serial-at.c:440] > debug_log(): (ttymxc2): --> 'AT' > ModemManager[1623]: [1490123699.675043] [mm-plugin-manager.c:710] > min_probing_timeout_cb(): (Plugin Manager) > [/sys/devices/soc0/soc/210.aips-bus/21ec000.serial] Minimum probing time > consumed > ModemManager[1623]: [1490123701.676723] [mm-port-probe-at.c:43] > mm_port_probe_response_processor_is_at(): Parsing AT got: 'Serial command > timed out' > ModemManager[1623]: [1490123701.677231] [mm-port-serial-at.c:440] > debug_log(): (ttymxc2): --> 'AT' > ModemManager[1623]: [1490123704.677040] [mm-port-probe-at.c:43] > mm_port_probe_response_processor_is_at(): Parsing AT got: 'Serial command > timed out' > ModemManager[1623]: [1490123704.677497] [mm-port-serial-at.c:440] > debug_log(): (ttymxc2): --> 'AT' > ModemManager[1623]: [1490123707.677319] [mm-port-probe-at.c:43] > mm_port_probe_response_processor_is_at(): Parsing AT got: 'Serial command > timed out' What's the baudrate of the TTY in the modem? MM by default uses 57600 bps. -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
RE: Could not acquire the 'org.freedesktop.ModemManager1' service name
Hello Dan, Yes, I am able to talk to this modem through command: kermit -l /dev/ttymxc2 -b 115200 set flow none set carrier-watch off connect AT OK at+cops=? +COPS: (1,"T-Mobile","T-Mobile","310260",2),(1,"AT","AT","310410",2),(1,"T-Mobile","T-Mobile","310260",0),,(0-4),(0-2) OK Best Regards, Jan Graczyk This email message may contain confidential and privileged information. Any 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 1:01 PM To: Jan Graczyk <j...@nytec.com>; Aleksander Morgado <aleksan...@aleksander.es> Cc: modemmanager-devel@lists.freedesktop.org Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1' service name On Tue, 2017-03-21 at 19:56 +, Jan Graczyk wrote: > Hello Dan, > > Here is the ModemManager debug logging with my recent udev rule > added: For whatever reason, ttymxc2 is not responding to AT commands. Are you able to talk to that port directly with minicom or something similar? Dan > root@linaro-alip:~# ModemManager --debug > ModemManager[1623]: [1490123697.480062] [main.c:140] main(): > ModemManager (version 1.4.0) starting in system bus... > ModemManager[1623]: [1490123697.502634] [main.c:65] > bus_acquired_cb(): Bus acquired, creating manager... > ModemManager[1623]: [1490123697.520416] [mm-plugin- > manager.c:852] load_plugins(): Looking for plugins in '/usr/lib/arm- > linux-gnueabihf/ModemManager' > ModemManager[1623]: [1490123697.522802] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Nokia (Icera)' > ModemManager[1623]: [1490123697.524392] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'AnyDATA' > ModemManager[1623]: [1490123697.525883] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Option' > ModemManager[1623]: [1490123697.527330] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'X22X' > ModemManager[1623]: [1490123697.528752] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Pantech' > ModemManager[1623]: [1490123697.530279] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Iridium' > ModemManager[1623]: [1490123697.531809] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Novatel' > ModemManager[1623]: [1490123697.533273] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'MTK' > ModemManager[1623]: [1490123697.534832] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Generic' > ModemManager[1623]: [1490123697.536357] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Gobi' > ModemManager[1623]: [1490123697.537969] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Huawei' > ModemManager[1623]: [1490123697.539526] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Sierra' > ModemManager[1623]: [1490123697.541052] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Option High-Speed' > ModemManager[1623]: [1490123697.542537] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Motorola' > ModemManager[1623]: [1490123697.544192] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Via CBP7' > ModemManager[1623]: [1490123697.545752] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Samsung' > ModemManager[1623]: [1490123697.547194] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'SimTech' > ModemManager[1623]: [1490123697.548733] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Nokia' > ModemManager[1623]: [1490123697.550220] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Wavecom' > ModemManager[1623]: [1490123697.551770] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Novatel LTE' > ModemManager[1623]: [1490123697.553265] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Longcheer' > ModemManager[1623]: [1490123697.555024] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Cinterion' > ModemManager[1623]: [1490123697.556584] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'ZTE' > ModemManager[1623]: [1490123697.558134] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Linktop' > ModemManager[1623]: [1490123697.559682] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Telit' > ModemManager[1623]: [1490123697.561223] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Altair LTE' > ModemManager[1623]: [1490123697.562785] [mm-plugin- > manager.c:877] load_plugins(): Loaded plugin 'Ericsson MBM' > ModemManager[1623]: [
RE: Could not acquire the 'org.freedesktop.ModemManager1' service name
to find primary
AT port
Best Regards,
Jan Graczyk
This email message may contain confidential and privileged information. Any
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 12:48 PM
To: Jan Graczyk <j...@nytec.com>; Aleksander Morgado <aleksan...@aleksander.es>
Cc: modemmanager-devel@lists.freedesktop.org
Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1' service name
On Tue, 2017-03-21 at 19:46 +, Jan Graczyk wrote:
> Hello Dan,
>
> I have got better result with that udev rule:
>
> ACTION=="add", KERNEL=="21ec000.serial",
> ENV{ID_MM_PLATFORM_DRIVER_PROBE}="1"
>
> However mmcli -L still cannot find the modem. May be I need to add the
> support for QUECTEL UC20 device inside ModemManager.
Please provide ModemManager debug logging. We can't help figure out what's
going on without it here.
Dan
> Best Regards,
> Jan Graczyk
>
>
> This email message may contain confidential and privileged
> information. Any 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 11:17 AM
> To: Jan Graczyk <j...@nytec.com>; Aleksander Morgado <aleksander@alek
> sander.es>
> Cc: modemmanager-devel@lists.freedesktop.org
> Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1'
> service name
>
> On Tue, 2017-03-21 at 17:30 +, Jan Graczyk wrote:
> > Hello Dan,
> >
> > I have not noticed that I am getting an e-mail from you. I am sorry
> > for that. Here is the output for the requested command:
> >
> > root@linaro-alip:~# udevadm info --attribute-walk
> > /sys/class/tty/ttymxc2/
> >
> > Udevadm info starts with the device specified by the devpath and
> > then walks up the chain of parent devices. It prints for every
> > device found, all possible attributes in the udev rules key format.
> > A rule to match, can be composed by the attributes of the device and
> > the attributes from one single parent device.
>
> Ok, so it's not actually PCIe, at least according to the kernel data.
>
> You want to whitelist the "imx-uart" driver. Add a file called
> /etc/udev/rules.d/60-mm-imx-uart-whitelist.rules that contains:
>
> ACTION!="add|change|move", GOTO="mm_platform_device_whitelist_end"
> SUBSYSTEM!="platform", GOTO="mm_platform_device_whitelist_end"
> DRIVERS=="imx-uart", ENV{ID_MM_PLATFORM_DRIVER_PROBE}="1"
> LABEL="mm_platform_device_whitelist_end"
>
> and then restart the machine. Does that work?
>
> Dan
>
> > looking at device '/devices/soc0/soc/210.aips-
> > bus/21ec000.serial/tty/ttymxc2':
> > KERNEL=="ttymxc2"
> > SUBSYSTEM=="tty"
> > DRIVER==""
> > ATTR{close_delay}=="50"
> > ATTR{closing_wait}=="3000"
> > ATTR{custom_divisor}=="0"
> > ATTR{flags}=="0x1000"
> > ATTR{io_type}=="2"
> > ATTR{iomem_base}=="0x21EC000"
> > ATTR{iomem_reg_shift}=="0"
> > ATTR{irq}=="305"
> > ATTR{line}=="2"
> > ATTR{port}=="0x0"
> > ATTR{type}=="62"
> > ATTR{uartclk}=="8000"
> > ATTR{xmit_fifo_size}=="32"
> >
> > looking at parent device '/devices/soc0/soc/210.aips-
> > bus/21ec000.serial':
> > KERNELS=="21ec000.serial"
> > SUBSYSTEMS=="platform"
> > DRIVERS=="imx-uart"
> > ATTRS{driver_override}=="(null)"
> >
> > looking at parent device '/devices/soc0/soc/210.aips-bus':
> > KERNELS=="210.aips-bus"
> > SUBSYSTEMS=="platform"
> > DRIVERS==""
> > ATTRS{driver_override}=="(null)"
> >
> > looking at parent device '/devices/soc0/soc':
> > KERNELS=="soc"
> > SUBSYSTEMS=="platform"
> > DRIVERS==""
> > ATTRS{driver_override}=="(null)"
> >
> > looking at parent device '/devices/soc0':
> > KERNELS=="soc0"
> > SUBSYSTEMS=="soc"
>
RE: Could not acquire the 'org.freedesktop.ModemManager1' service name
Hello Dan,
When I have applied that rule you have provided for me the target serial
console is printing garbage characters and I do not have access to target
serial console any more. I had to remove that rule to get the target serial
console back.
Best Regards,
Jan Graczyk
This email message may contain confidential and privileged information. Any
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 11:17 AM
To: Jan Graczyk <j...@nytec.com>; Aleksander Morgado <aleksan...@aleksander.es>
Cc: modemmanager-devel@lists.freedesktop.org
Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1' service name
On Tue, 2017-03-21 at 17:30 +, Jan Graczyk wrote:
> Hello Dan,
>
> I have not noticed that I am getting an e-mail from you. I am sorry
> for that. Here is the output for the requested command:
>
> root@linaro-alip:~# udevadm info --attribute-walk
> /sys/class/tty/ttymxc2/
>
> Udevadm info starts with the device specified by the devpath and then
> walks up the chain of parent devices. It prints for every device
> found, all possible attributes in the udev rules key format.
> A rule to match, can be composed by the attributes of the device and
> the attributes from one single parent device.
Ok, so it's not actually PCIe, at least according to the kernel data.
You want to whitelist the "imx-uart" driver. Add a file called
/etc/udev/rules.d/60-mm-imx-uart-whitelist.rules that contains:
ACTION!="add|change|move", GOTO="mm_platform_device_whitelist_end"
SUBSYSTEM!="platform", GOTO="mm_platform_device_whitelist_end"
DRIVERS=="imx-uart", ENV{ID_MM_PLATFORM_DRIVER_PROBE}="1"
LABEL="mm_platform_device_whitelist_end"
and then restart the machine. Does that work?
Dan
> looking at device '/devices/soc0/soc/210.aips-
> bus/21ec000.serial/tty/ttymxc2':
> KERNEL=="ttymxc2"
> SUBSYSTEM=="tty"
> DRIVER==""
> ATTR{close_delay}=="50"
> ATTR{closing_wait}=="3000"
> ATTR{custom_divisor}=="0"
> ATTR{flags}=="0x1000"
> ATTR{io_type}=="2"
> ATTR{iomem_base}=="0x21EC000"
> ATTR{iomem_reg_shift}=="0"
> ATTR{irq}=="305"
> ATTR{line}=="2"
> ATTR{port}=="0x0"
> ATTR{type}=="62"
> ATTR{uartclk}=="8000"
> ATTR{xmit_fifo_size}=="32"
>
> looking at parent device '/devices/soc0/soc/210.aips-
> bus/21ec000.serial':
> KERNELS=="21ec000.serial"
> SUBSYSTEMS=="platform"
> DRIVERS=="imx-uart"
> ATTRS{driver_override}=="(null)"
>
> looking at parent device '/devices/soc0/soc/210.aips-bus':
> KERNELS=="210.aips-bus"
> SUBSYSTEMS=="platform"
> DRIVERS==""
> ATTRS{driver_override}=="(null)"
>
> looking at parent device '/devices/soc0/soc':
> KERNELS=="soc"
> SUBSYSTEMS=="platform"
> DRIVERS==""
> ATTRS{driver_override}=="(null)"
>
> looking at parent device '/devices/soc0':
> KERNELS=="soc0"
> SUBSYSTEMS=="soc"
> DRIVERS==""
> ATTRS{family}=="Freescale i.MX"
> ATTRS{machine}=="Variscite i.MX6 DL/Solo SOM-SOLO SOM-DUAL"
> ATTRS{revision}=="1.3"
> ATTRS{soc_id}=="i.MX6DL"
>
> root@linaro-alip:~#
>
> Best Regards,
> Jan Graczyk
>
> This email message may contain confidential and privileged
> information. Any 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 10:21 AM
> To: Jan Graczyk <j...@nytec.com>; Aleksander Morgado <aleksander@alek
> sander.es>
> Cc: modemmanager-devel@lists.freedesktop.org
> Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1'
> service name
>
> On Tue, 2017-03-21 at 16:59 +, Jan Graczyk wrote:
> > Hello Aleksander,
> >
> > The Queltec UC20 modem is sitting on my development board PCIe bus.
> > When I issue the command udevadm info /dev/ttymxc2 I am getting
> > response:
>
> We care more about the parents though, so could you:
>
>
RE: Could not acquire the 'org.freedesktop.ModemManager1' service name
Hello Aleksander, The Queltec UC20 modem is sitting on my development board PCIe bus. When I issue the command udevadm info /dev/ttymxc2 I am getting response: root@linaro-alip:~# udevadm info /dev/ttymxc2 P: /devices/soc0/soc/210.aips-bus/21ec000.serial/tty/ttymxc2 N: ttymxc2 E: DEVNAME=/dev/ttymxc2 E: DEVPATH=/devices/soc0/soc/210.aips-bus/21ec000.serial/tty/ttymxc2 E: ID_MM_CANDIDATE=1 E: MAJOR=207 E: MINOR=18 E: SUBSYSTEM=tty E: TAGS=:systemd: E: USEC_INITIALIZED=8343793 root@linaro-alip:~# Also the command mmcli -L reports: No modems were found. Do I need to create udev rule for this device? How the udev rule should look like for this device? Also after connecting to modem through Kermit I can issue AT command and see the mobile networks. Best Regards, Jan Graczyk This email message may contain confidential and privileged information. Any 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 AM To: Jan Graczyk <j...@nytec.com>; Aleksander Morgado <aleksan...@aleksander.es> Cc: modemmanager-devel@lists.freedesktop.org Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1' service name On Tue, 2017-03-21 at 16:33 +, Jan Graczyk wrote: > Hello Aleksander, > > Thank you for your response. I have actually stopped running Modem > Manger and then I have issued the command ModemManager --debug. This > time the service name was acquired. However I have got another > problem. The mm-base-manager.c:314 reports error device added(): > (tty/ttymxc2): port's parent platform driver is not whitelisted. Do > you know the solution for this problem? Thank you for your support. What is the device hooked up to on the machine itself? ModemManager does not usually auto-probe various platform drivers, because it cannot know that a modem is connected as these are not USB/PCI/etc and either do not provide device identifiers, or the device is a generic serial adapter which doesn't necessarily indicate a modem either (eg, it could have a UPS attached or something). So generally for these devices, if you have one you know what you are doing, and you can add a whitelist entry for it quite easily with udev rules. But let's confirm the details first. Dan > Best Regards, > Jan Graczyk > > This email message may contain confidential and privileged > information. Any 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: Aleksander Morgado [mailto:aleksan...@aleksander.es] > Sent: Tuesday, March 21, 2017 2:15 AM > To: Jan Graczyk <j...@nytec.com> > Cc: modemmanager-devel@lists.freedesktop.org > Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1' > service name > > On Tue, Mar 21, 2017 at 12:55 AM, Jan Graczyk <j...@nytec.com> wrote: > > > > I have installed Quectel UC20 modem on my development board PCIe > > bus. The Linux modem device for Quectel UC20 modem is showing up as > > /dev/ttymxc2. When I try to run mmcli -L or ModemManager –debug the > > message “Could not acquire the 'org.freedesktop.ModemManager1' > > service name” is showing up. How to connect my Linux modem device > > /dev/ttymxc2 to ModemManger? I appreciate very much help from you. > > > Do you have the DBus daemon running in your system? ModemManager will > grab the "org.freedesktop.ModemManager1" name in the system bus > exposed by DBus; mmcli talks to ModemManager through that bus. > > > -- > Aleksander > https://aleksander.es > ___ > ModemManager-devel mailing list > ModemManager-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
RE: Could not acquire the 'org.freedesktop.ModemManager1' service name
Hello Aleksander, Thank you for your response. I have actually stopped running Modem Manger and then I have issued the command ModemManager --debug. This time the service name was acquired. However I have got another problem. The mm-base-manager.c:314 reports error device added(): (tty/ttymxc2): port's parent platform driver is not whitelisted. Do you know the solution for this problem? Thank you for your support. Best Regards, Jan Graczyk This email message may contain confidential and privileged information. Any 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: Aleksander Morgado [mailto:aleksan...@aleksander.es] Sent: Tuesday, March 21, 2017 2:15 AM To: Jan Graczyk <j...@nytec.com> Cc: modemmanager-devel@lists.freedesktop.org Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1' service name On Tue, Mar 21, 2017 at 12:55 AM, Jan Graczyk <j...@nytec.com> wrote: > > I have installed Quectel UC20 modem on my development board PCIe bus. The > Linux modem device for Quectel UC20 modem is showing up as /dev/ttymxc2. When > I try to run mmcli -L or ModemManager –debug the message “Could not acquire > the 'org.freedesktop.ModemManager1' service name” is showing up. How to > connect my Linux modem device /dev/ttymxc2 to ModemManger? I appreciate very > much help from you. Do you have the DBus daemon running in your system? ModemManager will grab the "org.freedesktop.ModemManager1" name in the system bus exposed by DBus; mmcli talks to ModemManager through that bus. -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
