Re: MM 0.6.0 conflicts with USB GPS device?

[Aleksander Morgado <aleksander lanedo com>]

Hey Poma,

On 08/06/13 09:02, poma wrote:
> OK, that can be overcome via 'ID_MM_DEVICE_IGNORE' within a custom rule.
> As for this device,
> http://www.koutech.com/proddetail.asp?linenumber=56[1]
> 'ID_MM_DEVICE_IGNORE' *must* be applied, if we want to prevent scanning
> connected ups and nut-driver/server breakage.
> And all this as a result of
> /lib/udev/rules.d/80-mm-candidate.rules
> SUBSYSTEM=="tty", ENV{ID_MM_CANDIDATE}="1"
> Therefore 'ID_MM_PLATFORM_DRIVER_PROBE' is redundant, in the first
> place, in this case.
>
> mmcli --version
> mmcli 0.7.991
>
>
> poma
>
>
> [1]
> DEVPATH=/class/pci_bus/0000:01/device/0000:01:06.0
> DRIVER=serial
> ID_MODEL_FROM_DATABASE=1P2S
> ID_PCI_CLASS_FROM_DATABASE=Communication controller
> ID_PCI_SUBCLASS_FROM_DATABASE=Communication controller
> ID_VENDOR_FROM_DATABASE=MosChip Semiconductor Technology Ltd.
> MODALIAS=pci:v00009710d00009835sv00001000sd00000012bc07sc80i02
> PCI_CLASS=78002
> PCI_ID=9710:9835
> PCI_SLOT_NAME=0000:01:06.0
> PCI_SUBSYS_ID=1000:0012
> SUBSYSTEM=pci

I don't think we should probe devices in the 'pci' subsystem unless
whitelisted with ID_MM_PLATFORM_DRIVER_PROBE. Can you grab this patch,
replace 'pnp' with 'pci' and retest?

https://mail.gnome.org/archives/networkmanager-list/2013-June/txtfYzWozQRdF.txt

-- 
Aleksander