ID_MM_DEVICE_MANUAL_SCAN_ONLY not applied properly?

Aleksander Morgado aleksander at
Sun May 20 06:52:58 UTC 2018

On 18/05/18 18:20, Bjørn Mork wrote:
> Bjørn Mork <bjorn at> writes:
>> Aleksander Morgado <aleksander at> writes:
>>>>> The ID_MM_DEVICE_MANUAL_SCAN_ONLY is applied on the usb_device matched
>>>>> by vid:pid from the list of rules we have.
>>>>> This first run is after booting the machine: I don't see the tag applied.
>>>> Maybe you forgot to update your initramfs after adding the new rule?
>>> Hum... why would that be needed? udev rules are applied on boot as
>>> soon as the USB devices gets exposed by the system. Or am I missing
>>> something?
>> This tends to happen before the real root system is mounted.  And there
>> is no later rediscovery of already discovered USB devices.  At least
>> that's how I thought this worked.  Could be wrong, as usual...
>> Looking at my initramfs I guess I must be.  I note that *some* udev
>> rules are copied there.  But most of them are not, and in particular the
>> default MM rules.  Weird.  Have to look further at this.
> The responsible for that is this hook, which has a short hardcoded list
> of rules to copy:
> I wonder why?  I would have thought that you either needed all or none?

Does this theory explain the fact that ID_MM_CANDIDATE on the *tty* device is applied during boot as expected, but ID_MM_DEVICE_MANUAL_SCAN_ONLY on the *usb* device isn't applied?

Can any of you try to reproduce this issue? (e.g. make && make install from git master, then reboot, then start ModemManager without any filter applied). 


More information about the ModemManager-devel mailing list