incorrect rule in usb_modeswitch.rules for 19d2:2000

[Cleber Santz]

The rule in /etc/udev/rules/ usb_modeswitch.rules seens to be incorrect for device 19d2:2000, the actual rule does not change to modem device.

Actual rule:
SUBSYSTEM=="usb", SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="2000", RUN+="/usr/sbin/usb_modeswitch --DefaultVendor 0x19d2 --DefaultProduct 0x2000 --MessageEndpoint 0x04 --MessageContent 55534243123456780000000000000600000000000000000000000000000000"

Rule that work for me, copied from VMC (Vodafone Mobile Connector):
ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", \
   ATTR{idVendor}=="19d2", ATTR{idProduct}=="2000", \
   RUN+="/usr/sbin/vmc-usb_modeswitch-eject.sh %s{idVendor} %s{idProduct}"

Content of vmc-usb_modeswitch-eject.sh :
#!/bin/sh
VID="$1"
PID="$2"
# Need to wait for the device to settle before sending the command
sleep 1
# Standard SCSI eject
usb_modeswitch -v ${VID} -p ${PID} -M 5553424312345678000000000000061b000000020000000000000000000000 -R 1

$ apt-cache policy usb-modeswitch
usb-modeswitch:
  Installed: 0.9.7-1
  Candidate: 0.9.7-1
  Version table:
 *** 0.9.7-1 0
        500 http://br.archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status

$ lsb_release
Description: Ubuntu karmic (development branch)
Release: 9.10

$ uname
Linux ubuntu 2.6.30-8-generic #9-Ubuntu SMP Wed Jun 3 15:38:38 UTC 2009 x86_64 GNU/Linux

[Didier Raboud (odyx)]

I will try to give a closer look to this bug soon. Note that 1.0.2-1 went uploaded to Debian today. You might want to try this new version (even though I don't think it might help).

[Cleber Santz (clebersantz)]

Hi Didier, version 1.0.2 didn't solve the problem.

[Didier Raboud (odyx)]

Hi,

I am considering to add a configuration entry for your device (which you'll have to activate manually). What is your device (I don't want the VendorID, but a "name" which refers to that device easily) ?

Regards,

OdyX

[Cleber Santz (clebersantz)]

  I don't understand exactly what "name" you want: in LSUSB says "ONDA Communication S.p.A.", in the BOX says "ZTE MF 636 3G Modem" .

  Regards,

  Cleber

[Didier Raboud (odyx)]

Exactly this ! Thank you !

I will prepare a patch with your new rule and it will be part of the next upload to Debian (and then I don't know how it ends in Ubuntu...)

Regards, OdyX

[Didier Raboud (odyx)]

Hi again, I committed a patch to the git repository. It will be part of next upload (due in some days probably).

http://git.debian.org/?p=collab-maint/usb-modeswitch.git;h=26848ac72b1fbf716ce5fc5b29254dd86f6fc407

Best regards,

OdyX

[Id2ndR (id2ndr)]

I've got an ZTE K3565-Z usb modem (same product and vendor id : 19d2:2000). Target ids are 19d2:0052. I get it working in jaunty, and at least recognize in karmic (is modemmanager preventing me to get it connected ?). following instructions of https://answers.launchpad.net/ubuntu/+question/77675.

So I modifiy /etc/udev/rules.d/usb_modeswitch.rules to get it working without installing vodafone-mobile-connect package. See attached patch.

Maybe I had to fill an other bug ?

As there are many products with ids 19d2:2000, I'm wondering how it's possible to distinguish them with udev ?

[Didier Raboud (odyx)]

Hi Id2ndr,

Please file a bug at upstream's bts:
http://www.draisberghof.de/usb_modeswitch/bb

Regards,

OdyX

[Id2ndR (id-2ndr)]

> Please file a bug at upstream's bts:
> http://www.draisberghof.de/usb_modeswitch/bb
Done here : http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=202

Hope this will help them.

[Didier Raboud (odyx)]

This is most probably fixed in usb-modeswitch-data 20100127-1, actually in Lucid.

Best regards, OdyX