I have a ZTE ZeroCD device, with the same vendor and product id 19d2:2000, but the above rule doesn't work for me in karmic.
The device is branded by Vodafone It as K3565-Z. Plugging the device result in the cd-rom being displayed, when manually ejected it switchs to a modem as usual. The prod and vendor id after switching are: 19d2:0063.
I have a ZTE ZeroCD device, with the same vendor and product id 19d2:2000, but the above rule doesn't work for me in karmic.
The device is branded by Vodafone It as K3565-Z. Plugging the device result in the cd-rom being displayed, when manually ejected it switchs to a modem as usual. The prod and vendor id after switching are: 19d2:0063.
Neither the rule posted by Sergiu,
SYSFS{idVendor} =="19d2" , SYSFS{idProduct }=="2000" , RUN+="/ usr/bin/ eject %k"
nor the one commited by Martin, works for me.
The former is recognized for the device to apply by udevadm test, the latter doesn't.
It seems my device has a value of "00" for the attributes bDeviceClass and bDeviceSubClass, instead of "ff", as in the rule by Martin.
Changing the rule this way:
SUBSYSTEM=="usb", ATTR{bDeviceCla ss}=="00" , ATTR{bDeviceSub Class}= ="00", ENV{DEVTYPE} =="usb_ device" , GOTO="mobile_ action_ switch"
results in udevadm test recognizing it, but still it doesn't work. After plugging, the fake cd is still there.
I tried with modem-modeswitch but it didn't succeed, too.