Needs usb_modeswitch rule for UM175 (Verizon/Alltel 3G Modem)

Bug #419357 reported by Noel J. Bergman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udev
Fix Released
Medium
udev (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

As noted in Bug 328309, we need a udev rule for the UM175. This is Verizon's current 3G modem (http://shop.verizonwireless.com/?id=Verizon+Wireless+UM175+USB+Modem+USB%20Modem).

My (current, but see below) rule is:

SUBSYSTEM=="usb", ATTR{idProduct}="3b03", ATTR{idVendor}=="106c", RUN+="/usr/local/sbin/usb_modeswitch"

having previously configured /etc/usb_modeswitch. I understand that the new udev code uses modem-modeswitch, but we still need a udev rule to invoke a switcher for this modem. Accordingly, I replaced my rule with:

ATTRS{idVendor}=="106c", ATTRS{idProduct}=="3b03", RUN+="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t option-zerocd"

but that appears NOT to work (see below).

Perhaps someone should go through the current usb_modeswitch.conf file and generate udev rules for the missing {idVendor,idProduct}-pairs (q.v., http://<email address hidden>/msg08733.html)? And modem-modeswitch should be modified to handle more mode switching strings than the one hardcoded into it, or replaced by the more functional usb_modeswitch.

Noel J. Bergman (noeljb)
summary: - Needs rule for UM175 (Verizon/Alltell 3G Modem)
+ Needs rule for UM175 (Verizon/Alltel 3G Modem)
Revision history for this message
Noel J. Bergman (noeljb) wrote : Re: Needs rule for UM175 (Verizon/Alltel 3G Modem)

> [modem-modeswitch] appears to work

Nope. After a clean reboot, I could not get the modem to switch on, regardless of whether udev or I ran the command. It required reverting to usb_modeswitch.

So we not only need a rule, apparently we need a fix/enhancement to modem-modeswitch.

Noel J. Bergman (noeljb)
description: updated
Revision history for this message
In , Noel (noel-redhat-bugs) wrote :

Description of problem:

modem-modeswitch lacks the necessary rules and content to handle many of the modems that need switching. usb_modeswitch is far more complete.

In particular, the current Verizon offering, the UM175, is not supported by modem-modeswitch, either by rule or code. Even if the correct command is executed, the code fails to switch the device to modem mode because it it doesn't use the right string. usb_modeswitch handles it perfectly.

modem-modeswitch has the right idea, but needs to be expanded, or should simply be replaced by usb_modeswitch, since it works.

Version-Release number of selected component (if applicable):

udev-extras-20090226-0.5.20090302git.fc11.x86_64

How reproducible:

Very.

Steps to Reproduce:

Insert the device, and watch with udevadm.

Actual results:

The storage device is recognized, but the modem never switches on, even if you run the command by hand.

Expected results:

The device should switch to modem mode.

Noel J. Bergman (noeljb)
description: updated
Changed in udev:
status: Unknown → Confirmed
Changed in udev (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

Let's try method #4 for those devices:

Does the modem start to work if you disable that udev rule, plug it in, and then call "eject" on the fake CD-ROM drive?

Revision history for this message
Noel J. Bergman (noeljb) wrote :

Martin,

> Does the modem start to work if you disable that udev rule, plug it in, and then call "eject" on the fake CD-ROM drive?

No. I tried it for you (several times to be sure). Clean reboot. The storage device is recognized, I can mount it (or not), eject it, no difference. I monitor with udevadm, and nothing enables the modem until I (manually in this case) run usb_modeswitch.

Revision history for this message
Martin Pitt (pitti) wrote :

Thanks for testing. Dan Williams says

"2) usb_modeswitch - the common tool to handle the fake CD case.
However, I've found it is *completely* unsuited to distro usage, it's
really meant for the user to configure exactly the modem they want to
eject. First, it isn't out-of-the-box-ready, you need to (a) edit a
config file and uncomment your modem, and (b) write the udev rules
yourself. It doesn't just look for all the modems that it can switch
and then switch all of them, it requires being told explicitly about
every modem to switch. Ugh.

3) modem-modeswitch - my attempt to make stuff Just Work, but I never
had time to really handle it. I'd be happy to kill modem-modeswitch if
usb_modeswitch would get easier to package for distributions.

So yeah, I'm happy with the change, and (2) and (3) can co-exist on the
same system. But I think since I have less attention to pay to
modem-modeswitch than people have to give usb_modeswitch, we probably
want to fix usb_modeswitch and just use that in the shiny distant
future.

So this cannot be fixed out of the box in udev, I'm afraid.

Changed in udev (Ubuntu):
assignee: Martin Pitt (pitti) → nobody
status: Confirmed → Triaged
summary: - Needs rule for UM175 (Verizon/Alltel 3G Modem)
+ Needs usb_modeswitch rule for UM175 (Verizon/Alltel 3G Modem)
Revision history for this message
Josua Dietze (digidietze) wrote :

The recent versions of "usb_modeswitch" have a ready made rule file and - using a wrapper like "sane" - do work without user interaction if the respective device is known.

The UM175 is supported.

Revision history for this message
Didier Raboud (odyx) wrote :

IMHO, this bug can be closed as it seems to be fixed by usb-modeswitch-data (which you need to have installed).

Revision history for this message
Didier Raboud (odyx) wrote :

Hi all,

the resolution to this bug is to ship a udev that incorporates the upstream commit 4dd9b291354e76f34b0d6d7b5c3b28d03a624418 (post-151).

"modeswitch: morph into tool that only switches Mobile Action cables

 Remove option modeswitching code; use usb_modeswitch already, people."

Cheers,

OdyX

Revision history for this message
Martin Pitt (pitti) wrote :

Fixed in usb-modeswitch, wont fix in udev.

Changed in udev (Ubuntu):
status: Triaged → Won't Fix
Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Dan (dan-redhat-bugs) wrote :

This has already happened upstream; modem-modeswitch has been removed from udev and usb_modeswitch is the way to go.

Revision history for this message
asux (ckasux) wrote :

try install hwinfo .and updateing

Changed in udev:
importance: Unknown → Medium
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.