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

Tue Mar 21 18:42:58 UTC 2017

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:dcbw at redhat.com] 
Sent: Tuesday, March 21, 2017 11:17 AM
To: Jan Graczyk <JanG at nytec.com>; Aleksander Morgado <aleksander at aleksander.es>
Cc: modemmanager-devel at lists.freedesktop.org
Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1' service name

On Tue, 2017-03-21 at 17:30 +0000, 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 at 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/2100000.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}=="0x10000000"
>     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}=="80000000"
>     ATTR{xmit_fifo_size}=="32"
> 
>   looking at parent device '/devices/soc0/soc/2100000.aips-
> bus/21ec000.serial':
>     KERNELS=="21ec000.serial"
>     SUBSYSTEMS=="platform"
>     DRIVERS=="imx-uart"
>     ATTRS{driver_override}=="(null)"
> 
>   looking at parent device '/devices/soc0/soc/2100000.aips-bus':
>     KERNELS=="2100000.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 at 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:dcbw at redhat.com]
> Sent: Tuesday, March 21, 2017 10:21 AM
> To: Jan Graczyk <JanG at nytec.com>; Aleksander Morgado <aleksander at alek 
> sander.es>
> Cc: modemmanager-devel at lists.freedesktop.org
> Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1'
> service name
> 
> On Tue, 2017-03-21 at 16:59 +0000, 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:
> 
> udevadm info --attribute-walk /sys/class/tty/ttymxc2
> 
> Dan
> 
> > root at linaro-alip:~# udevadm info /dev/ttymxc2
> > P: /devices/soc0/soc/2100000.aips-bus/21ec000.serial/tty/ttymxc2
> > N: ttymxc2
> > E: DEVNAME=/dev/ttymxc2
> > E: DEVPATH=/devices/soc0/soc/2100000.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 at 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:dcbw at redhat.com]
> > Sent: Tuesday, March 21, 2017 9:41 AM
> > To: Jan Graczyk <JanG at nytec.com>; Aleksander Morgado <aleksander at al 
> > ek sander.es>
> > Cc: modemmanager-devel at lists.freedesktop.org
> > Subject: Re: Could not acquire the 'org.freedesktop.ModemManager1'
> > service name
> > 
> > On Tue, 2017-03-21 at 16:33 +0000, 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:aleksander at aleksander.es]
> > > Sent: Tuesday, March 21, 2017 2:15 AM
> > > To: Jan Graczyk <JanG at nytec.com>
> > > Cc: modemmanager-devel at 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 <JanG at 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 at lists.freedesktop.org
> > > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel