After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685011 - ModemManager probe wrong tty on Haier CE81B
ModemManager probe wrong tty on Haier CE81B
Status: RESOLVED NOTGNOME
Product: NetworkManager
Classification: Platform
Component: ModemManager
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-09-27 23:49 UTC by Airlangga Cahya Utama
Modified: 2014-10-14 14:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
udev modemmanager port blacklist (698 bytes, text/plain)
2012-09-27 23:50 UTC, Airlangga Cahya Utama
Details
Modem manager log without udev port-ban rules (59.30 KB, application/octet-stream)
2012-10-11 09:00 UTC, Airlangga Cahya Utama
Details
Network manager log without udev port-ban rules. (22.57 KB, text/x-log)
2012-10-11 09:01 UTC, Airlangga Cahya Utama
Details
Modem manager log WITH udev port-ban rules. (22.09 KB, text/x-log)
2012-10-11 09:05 UTC, Airlangga Cahya Utama
Details

Description Airlangga Cahya Utama 2012-09-27 23:49:40 UTC
Modem Type: Haier CE81B
Modem Vendor: 0x201e
Modem Product: 0x10f8

After successful probe using command:
 sudo modprobe usbserial vendor=0x201e product=0x10f8
ModemManager start scanning for right ttyUSB.
However, ModemManager confused by ttyUSB02 that responded to AT command.
The right tty for ppp dialing is ttyUSB03.

Below is my udev rule to block ModemManager scan on ttyUSB00-ttyUSB02.
As a side effect, blocking port will speed up ModemManager detection.
Comment 1 Airlangga Cahya Utama 2012-09-27 23:50:27 UTC
Created attachment 225302 [details]
udev modemmanager port blacklist
Comment 2 Dan Williams 2012-10-04 20:20:51 UTC
Instead of ignoring the port that responds to AT but confusingly, I suggest we fix ModemManager to handle the port correctly.  We do this for a lot of other devices that don't have full parsers on some AT port, or that only provide PPP connections on a specific port.

To do this, can we:

1) get a ModemManager debug log of device detection
2) before the modeswitch runs tar up the fake CD and email it to me so I can determine what AT commands the device uses and what the Windows driver does with the ports
Comment 3 Airlangga Cahya Utama 2012-10-05 16:15:03 UTC
With number 1 do you mean something like https://wiki.ubuntu.com/DebuggingModemmanager?

For number 2, do you need the content of fake CD? It seems I can't mount the fake CD, so I think I will copy it from windows machine. Is that still counts?
Comment 4 Aleksander Morgado 2012-10-08 06:46:06 UTC
Yes for both.
Comment 5 Airlangga Cahya Utama 2012-10-11 09:00:34 UTC
Created attachment 226235 [details]
Modem manager log without udev port-ban rules
Comment 6 Airlangga Cahya Utama 2012-10-11 09:01:02 UTC
Created attachment 226236 [details]
Network manager log without udev port-ban rules.
Comment 7 Airlangga Cahya Utama 2012-10-11 09:05:27 UTC
Created attachment 226238 [details]
Modem manager log WITH udev port-ban rules.
Comment 8 Airlangga Cahya Utama 2012-10-11 09:15:41 UTC
Here all the log, two log for network and modem manager without blocking port udev rule. One log for modem manager with block port rule.

Link for setup file: http://www.mediafire.com/download.php?l39t0qk2kad9l02
Comment 9 Aleksander Morgado 2014-10-14 14:47:27 UTC
I wrote a patch to try to handle this issue; which you can find in the new bugreport created in the new ModemManager bugzilla in freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=85001

Could you please try with that patch?


Also,  I'm moving over all bugs to the new bugzilla, and hence I'll close this bug (but the issue is NOT closed!). Please follow the status of the fix in the freedesktop.org bugzilla from now on, and comment there the results of your tests.