© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Nope, there are no "interfaces" at this stage, and nm-modem-probe has nothing to do with CD-ROMs.
A little background:
When ZeroCD devices are plugged in, they are not modems at all. They appear as real CD-ROM drives, with data on them. No interfaces, no modems. USB IDs (e.g. for ZTE MF series) are 19d2:2000.
These CD-ROMs can be ejected with a right click -> Eject, or from the terminal with 'eject sr0'.
Mode-switching is embedded into these devices, this is why usb-modeswitch is not necessary. They switch modes when the CD-ROM is ejected, OR when a special message is sent (e.g. via usb-modeswitch).
The trouble with usb-modeswitch is that each device firmware can have its own "special message" and we never get it done right.
OTOH ejecting the CD works the same for all ZeroCD devices and nobody needs to care about the messages for each single device model/firmware.
After the ZeroCD has been ejected, the device automatically switches to modem mode (19d2:0031 for ZTE MF6xx), and presents 3 interfaces. This is when nm-modem-probe does its job, probing the interfaces for modem capabilities.
The udev rule I have posted is confirmed to work with different ZTE models. I have no other ZeroCD devices to test with, but it has to be the same for all of them.