From: Justin Schoeman <justin@expertron.co.za>
To: linux-hotplug@vger.kernel.org
Subject: Blacklisting certain functions on a USB device in udev?
Date: Mon, 09 Nov 2009 20:12:30 +0000 [thread overview]
Message-ID: <4AF877AE.3040302@expertron.co.za> (raw)
Hi all,
I am trying to get my Huawei E220 3G modem working with the new Linux
kernels.
The USB device registers 3 functions. 2 usb-serial devices, and 1
usb-storage device. Unfortunately, a firmware bug is causing the device
to reset when userland apps try to mount the usb-storage device.
A simple way to get things working is to just kill udevd after the
serial ports are registered, and before the scsi device scan completes,
but obviously this is not ideal ;-) .
I have been experimenting by creating /etc/udev/rules.d/01-blacklist,
and adding rules to try ignore the storage device.
This:
SUBSYSTEMS="usb", ATTRS{idVendor}="12d1", OPTIONS:="ignore_device"
successfully ignores the USB device entirely (serial and storage options).
This:
SUBSYSTEMS="usb", ATTRS{idVendor}="12d1",
ATTRS{bInterfaceClass}="08", OPTIONS:="ignore_device"
should only match the storage device, and ignore it, but it doesn't seem
to work.
I have tried more exotic solutions like:
SUBSYSTEM="usb-serial", ATTRS{idVendor}="12d1",
GOTO="blacklist_skip_huawei"
SUBSYSTEMS="usb", ATTRS{idVendor}="12d1", OPTIONS:="ignore_device"
LABEL="blacklist_skip_huawei"
but the storage device is still mounted.
Is there any way to debug the rule parsing to see exactly which rules
are matched/violated?
Can anybody perhaps help with tips/advice on how to construct this
blacklist?
Thanks,
Justin
PS I am not subscribed to the list. Please CC me any replies.
next reply other threads:[~2009-11-09 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 20:12 Justin Schoeman [this message]
2009-11-11 17:14 ` Blacklisting certain functions on a USB device in udev? Justin Schoeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF877AE.3040302@expertron.co.za \
--to=justin@expertron.co.za \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.