77-mm-usb-device-blacklist.rules - allow blacklisting various devices

[Dan Williams]

On Wed, 2014-09-03 at 19:12 +0200, poma wrote:
> On 03.09.2014 18:37, Dan Williams wrote:
> > On Wed, 2014-09-03 at 18:06 +0200, poma wrote:
> >> On 03.09.2014 10:11, Aleksander Morgado wrote:
> >>> On Wed, Sep 3, 2014 at 3:42 AM, poma <pomidorabelisima at gmail.com> wrote:
> >>>> +# Moschip Semiconductor USB-MAC Controller (MCS7830 10/100 Mbps Ethernet adapter)
> >>>> +ATTRS{idVendor}=="9710", ATTRS{idProduct}=="7830", ENV{ID_MM_DEVICE_IGNORE}="1"
> >>>> +
> >>>> +# Conexant Systems (Rockwell), Inc. USB Modem (TRENDnet TFM-561U 56K USB Modem)
> >>>> +ATTRS{idVendor}=="0572", ATTRS{idProduct}=="1329", ENV{ID_MM_DEVICE_IGNORE}="1"
> >>>> +
> >>>
> >>>
> >>> The purpose of the blacklist is to include there only devices that
> >>> expose TTYs and are not modems.
> >>>
> >>>  * Does the Ethernet adapter expose a TTY? If not, then it doesn't
> >>> need to be in the blacklist (MM does not probe anything in those).
> >>
> >> Why is the MM deals with Ethernet adapters in the first place?
> > 
> > Because many modems for the past 3 or 4 years expose themselves as
> > Ethernet adapters *and* TTYs or other proprietary interfaces.  And it's
> > not easy to say that one kernel network device is a modem and another
> > kernel network device is not a modem.
> > 
> > Dan
> 
> Earth calling!
> 
> Starting Modem Manager...
> <info>  ModemManager (version 1.4.0-1.fc22) starting in system bus...
> Started Modem Manager.
> <warn>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:04.1/usb1/1-4': not supported by any plugin
> <warn>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:0a.0': not supported by any plugin
> <info>  Creating modem with plugin 'Generic' and '1' ports
> <info>  Modem for device at '/sys/devices/pci0000:00/0000:00:04.0/usb2/2-3' successfully created
> <warn>  Modem couldn't be initialized: couldn't load current capabilities: Failed to determine modem capabilities.

This is simply a ModemManager bug, not a blacklist issue.  USB ethernet
adapters should work the same way that PCI ones do, where MM ignores
them if they aren't paired with a control channel.  So we'll look into
this bug and fix it.  Note that NM isn't actually touching the ethernet
device at all, unlike TTY probing.

Dan

> $ (cd /sys/devices/pci0000:00/0000:00:04.1/usb1/1-4 && echo $(cat idVendor idProduct manufacturer product))
> 9710 7830 Moschip Semiconductor USB-MAC Controller
> $ lsusb -d 9710:7830
> Bus 001 Device 005: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter
> 
> $ (cd /sys/devices/pci0000:00/0000:00:0a.0 && echo $(cat vendor device))
> 0x10de 0x0ab0
> $ lspci -nn -d 10de:0ab0
> 00:0a.0 Ethernet controller [0200]: NVIDIA Corporation MCP79 Ethernet [10de:0ab0] (rev b1)
> 
> are the *standard* *known* PCI/USB *Ethernet* adapters, *without* TTYs or other proprietary interfaces. :)
> 
> 
> poma
> 
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel