Am 21.08.2010 01:27, schrieb er...@ikki.ws:

Some questions:
What happens if you leave the usb_modeswitch config file intact but
disable the rule in 61-mobile-action.rules (out-comment, reload rules) ?


Ok,  usb_modeswitch config file intact (19d2:2000)

1) 61-mobile-action.rules, it has the following warning:

# ATTENTION: DO NOT USE THIS FILE FOR ANYTHING EXCEPT
# MOBILE ACTION CABLES.  DO NOT USE IT FOR 3G DEVICES!

So I guess this is not the file to modify, but anyway I comment out the
following rule:

#ATTRS{idVendor}=="0df7", ATTRS{idProduct}=="0800",
RUN+="mobile-action-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t
mobile-action-8280p"


If I get it right, you posted the error when you ran an earlier version of udev (or udev-extras). For a certain time it came with an entry for "19d2:2000" in that same file which conflicted with usb_modeswitch. (Otherwise your bug title wouldn't have made much sense, right?) But Dan Williams of Redhat who oversights that package has stated that he would reduce his switching attempts to exactly one device, an active USB cable named "Mobile Action". All others should be taken care of by usb_modeswitch.

So I suppose this is what we are seeing now. Can you confirm that the conflict no longer exists? If there is no entry for "19d2:2000" in any rules file except in 40-usb_modeswitch.rules, then there is no way to have a conflict. To be on the safe side, check also the rule files in /etc/udev/rules.d. With a simple "grep 19d2.*2000 *" you should be able to catch any conflicting entry.

>> What happens if both ways are intact and you change the config file

"/etc/usb_modeswitch.d/19d2:2000" and add the following line ?

MessageContent3="55534243123456782000000080000c85010101180101010101000000000000"

The result:

- Modem works like a charm :)

I think this is the solution.


This command is added to the latest usb-modeswitch-data package (version 20100817). So your modem should work with this release out-of-the-box.


Cheers,
Josh



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to