Modemmanager 1.10-1 <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0'

[Glenn.greenfield]

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, February 13, 2019 2:20 AM, Aleksander Morgado <aleksander at aleksander.es> wrote:

> Hey
>
> > Machine: Acer Chromebook 14 CB3-431
> > Init sysem: OpenRC -OR- runit (not systemd) if that matters.
> > Just trying to write a udev rule to simply ignore the onboard Intel Wireless 7265 (Dual Band Wireless-AC 7265) but can't seem to get it right.
> > Thank you much if you can help! Will gladly provide any additional details you would need to get this sorted.
> > On boot, modemmanager hangs the boot process with this informative message:
> > Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0' not supported by any plugin
>
> That is just an informative message. MM is not touching that interface
> for anything, it's just saying it cannot be used as part of a modem,
> as there is no control port. No udev rule to ignore the device will be
> hit, because MM is not even trying to use the device. That is
> definitely nothing to worry about.
>
> Is MM really hanging the boot process?
> What exactly are you seeing?
> Any actual logs you can share?
>
>
> Aleksander
> https://aleksander.es

Aleksander,

Thank you much for your response.

At one time, it did appear to be MM hanging the boot process because once MM was removed, the boot hang was also removed.

Now, it seems MM is not the culprit!  Things have changed along with new iwlwifi firmware.  Additionally, there are some known issues and inconsistencies regarding iwlwifi firmware.

Suffice to say, this no longer seems to be any sort of MM problem.

Now, I only wonder, is it necessary that MM provide the informative message at all?  Can it go to /dev/null?

Perhaps this is a -debug flag set at compile time?  If so, please pardon my ignorance!

-ggreenfield