Originally reported at: https://bugzilla.gnome.org/show_bug.cgi?id=637140 This linktop device (VID 0x230D PID 0x0001) fails to process AT+CIND? requests sent to the secondary port when the modem gets connected in the primary port. Furthermore, there seems to be some additional issues with the +CMER setup for CIEV indications, as the original reporter states that just configuring unsolicited messages in both primary and secondary ports doesn't make it work. So, even if the modem actually allows to get connected in any of the two ports, there actually seems to be a preference of which port needs to be considered primary (ttyUSB0) and which port needs to be considered as data (ttyUSB2). This preference would be only so that the primary port is left usable during a connection. The currently suggested solution would be to tag primary/data ports as we do with the ZTE plugin. Debug logs with MM 1.x are also needed, plus "lsusb -v" output. Minor severity, as it doesn't prevent connection.
Created attachment 108962 [details] lsusb -v -d 230d:0001
You mention ttyUSB0 and ttyUSB2, please be aware that this is a cdc_acm device.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/14.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.