ID_MM_DEVICE_MANUAL_SCAN_ONLY not applied properly?

Aleksander Morgado aleksander at aleksander.es
Fri May 18 11:45:03 UTC 2018


Hey,

Looking for some extra pairs of eyes here.

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.

[aleksander at ares ~]$ sudo udevadm info -p
/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.4
P: /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.4
N: bus/usb/001/006
E: BUSNUM=001
E: DEVNAME=/dev/bus/usb/001/006
E: DEVNUM=006
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.4
E: DEVTYPE=usb_device
E: DRIVER=usb
E: ID_BUS=usb
E: ID_FOR_SEAT=usb-pci-0000_00_14_0-usb-0_5_4
E: ID_MODEL=Quad_RS232-HS
E: ID_MODEL_ENC=Quad\x20RS232-HS
E: ID_MODEL_FROM_DATABASE=FT4232H Quad HS USB-UART/FIFO IC
E: ID_MODEL_ID=6011
E: ID_PATH=pci-0000:00:14.0-usb-0:5.4
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_5_4
E: ID_REVISION=0800
E: ID_SERIAL=FTDI_Quad_RS232-HS
E: ID_USB_INTERFACES=:ffffff:
E: ID_VENDOR=FTDI
E: ID_VENDOR_ENC=FTDI
E: ID_VENDOR_FROM_DATABASE=Future Technology Devices International, Ltd
E: ID_VENDOR_ID=0403
E: MAJOR=189
E: MINOR=5
E: PRODUCT=403/6011/800
E: SUBSYSTEM=usb
E: TAGS=:uaccess:seat:
E: TYPE=0/0/0
E: USEC_INITIALIZED=3061802

If I manually reload rules and re-trigger, the tag appears...

[aleksander at ares ~]$ sudo udevadm control --reload
[aleksander at ares ~]$ sudo udevadm trigger

[aleksander at ares ~]$ sudo udevadm info -p
/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.4
P: /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.4
N: bus/usb/001/006
E: BUSNUM=001
E: DEVNAME=/dev/bus/usb/001/006
E: DEVNUM=006
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.4
E: DEVTYPE=usb_device
E: DRIVER=usb
E: ID_BUS=usb
E: ID_FOR_SEAT=usb-pci-0000_00_14_0-usb-0_5_4
E: ID_MM_DEVICE_MANUAL_SCAN_ONLY=1
E: ID_MODEL=Quad_RS232-HS
E: ID_MODEL_ENC=Quad\x20RS232-HS
E: ID_MODEL_FROM_DATABASE=FT4232H Quad HS USB-UART/FIFO IC
E: ID_MODEL_ID=6011
E: ID_PATH=pci-0000:00:14.0-usb-0:5.4
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_5_4
E: ID_REVISION=0800
E: ID_SERIAL=FTDI_Quad_RS232-HS
E: ID_USB_INTERFACES=:ffffff:
E: ID_VENDOR=FTDI
E: ID_VENDOR_ENC=FTDI
E: ID_VENDOR_FROM_DATABASE=Future Technology Devices International, Ltd
E: ID_VENDOR_ID=0403
E: MAJOR=189
E: MINOR=5
E: PRODUCT=403/6011/800
E: SUBSYSTEM=usb
E: TAGS=:seat:uaccess:
E: TYPE=0/0/0
E: USEC_INITIALIZED=3061802

Any idea?

I'm seeing several ttyUSBx devices being probed on MM boot that
shouldn't be probed at all.... :/

-- 
Aleksander
https://aleksander.es


More information about the ModemManager-devel mailing list