Created attachment 110692 [details] ModemManager debug logs Hi, I have a Huawei E153 (Model: E153u-1) USB stick modem, which does not connect with newer versions of ModemManager (1.2 and 1.4 were tested) under ArchLinux. Symptoms/steps to reproduce: 1) Insert the USB modem stick, the SIM PIN entry dialog pops up 2) Enter the correct SIM PIN 3) There is a 'Mobile Broadband' device is correctly configured under NM, and appears under nm-applet (initially in 'Off' state) after PIN unlock. 4) Click on 'Connect' in nm-applet: no connection is made, and the 'Mobile Broadband' device suddenly disappears from nm-applet. After several seconds, the SIM PIN input dialog pops up again. These steps can be repeated any times, but the connection will never be established. Just for completeness, it connects flawlessly with older versions of MM (0.6) and NM (0.9.6.4), I used SystemRescueCd 4.4.1 to test it. It also works when I use ArchLinux's netctl tool to connect (it uses pppd internally). I attached both the MM and NM debug logs. Sensitive information (IMEI, PIN) was removed from the logs. Thanks, norbig
Created attachment 110693 [details] NetworkManager debug logs
When using MM 1.x this modem is being handled as a QMI modem (not with AT commands). When the connection process in QMI ends, the modem firmware just reboots: >>>>>> value = 04:D6:02:00:00:3E:03:00:00:00:00:00:00:00:00:00:00:02:DC:05:00:00:04:07:03:00:00:00:00:03:00:00:00 ModemManager[5396]: <debug> [1418239318.959602] [mm-bearer-qmi.c:482] get_current_settings_ready(): IP Family: failed (Field 'IP Family' was not found in the message); assuming IPv4 ModemManager[5396]: <debug> [1418239318.959618] [mm-bearer-qmi.c:488] get_current_settings_ready(): IP Family: IPv4 ModemManager[5396]: <debug> [1418239318.959632] [mm-bearer-qmi.c:491] get_current_settings_ready(): MTU: failed (Field 'MTU' was not found in the message) ModemManager[5396]: <debug> [1418239318.959676] [mm-bearer-qmi.c:302] get_ipv4_config(): QMI IPv4 Settings: ModemManager[5396]: <debug> [1418239318.959728] [mm-bearer-qmi.c:513] get_current_settings_ready(): Domains: failed (Field 'Domain Name List' was not found in the message) ModemManager[5396]: <debug> [1418239318.959756] [mm-port.c:95] mm_port_set_connected(): (wwp0s29u1u2i1): port now connected ModemManager[5396]: <debug> [1418239318.959793] [mm-base-bearer.c:488] connect_ready(): Connected bearer '/org/freedesktop/ModemManager1/Bearer/0' ModemManager[5396]: <info> [1418239318.959928] [mm-iface-modem.c:1392] __iface_modem_update_state_internal(): Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) ModemManager[5396]: <info> [1418239318.960176] [mm-iface-modem-simple.c:602] connection_step(): Simple connect state (8/8): All done ModemManager[5396]: <info> [1418239324.237897] [mm-base-manager.c:375] device_removed(): (tty/ttyUSB0): released by modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 ModemManager[5396]: <info> [1418239324.241099] [mm-base-manager.c:375] device_removed(): (net/wwp0s29u1u2i1): released by modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 ModemManager[5396]: <info> [1418239324.256620] [mm-base-manager.c:375] device_removed(): (usbmisc/cdc-wdm0): released by modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 ModemManager[5396]: <debug> [1418239324.256901] [mm-port-serial.c:889] common_input_available(): (ttyUSB3) unexpected port hangup! ModemManager[5396]: <debug> [1418239324.256928] [mm-port-serial.c:1415] port_serial_close_force(): (ttyUSB3) forced to close port ModemManager[5396]: <info> [1418239324.258517] [mm-base-manager.c:375] device_removed(): (tty/ttyUSB3): released by modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 ModemManager[5396]: <debug> [1418239324.258578] [mm-port-serial.c:889] common_input_available(): (ttyUSB4) unexpected port hangup! ModemManager[5396]: <debug> [1418239324.260295] [mm-port-serial.c:1415] port_serial_close_force(): (ttyUSB4) forced to close port ModemManager[5396]: <info> [1418239324.269728] [mm-base-manager.c:375] device_removed(): (tty/ttyUSB4): released by modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 ModemManager[5396]: <debug> [1418239324.270845] [mm-base-manager.c:380] device_removed(): Removing empty device '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2' ModemManager[5396]: <debug> [1418239324.272299] [mm-base-bearer.c:895] base_bearer_dbus_unexport(): Removing from DBus bearer at '/org/freedesktop/ModemManager1/Bearer/0' ModemManager[5396]: <debug> [1418239324.272939] [mm-device.c:382] unexport_modem(): Unexported modem '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2' from path '/org/freedesktop/ModemManager1/Modem/0' I know it's not what you want to hear (because it works with AT+ppp), but could you try to update the firmware to the latest one given by Huawei for that modem? Truth be told, this is the first time I see Huawei QMI firmware crashing like that.
Thanks for the clear explanation of the issue. I tried to upgrade the firmware from 11.609.18.00.00 to 11.609.18.00.158 (I was not able to find newer), it seemed that everything went fine. But since then, I get "The Specified SIM/USIM Card Can Be Used On This Device" from the official Huawei Mobile Partner (Windows) application. It is a T-Mobile HU operator branded modem, with a T-Mobile HU issued SIM. What did I do wrong? Do you have any idea?
(In reply to norbig from comment #3) > Thanks for the clear explanation of the issue. > > I tried to upgrade the firmware from 11.609.18.00.00 to 11.609.18.00.158 (I > was not able to find newer), it seemed that everything went fine. But since > then, I get "The Specified SIM/USIM Card Can Be Used On This Device" from > the official Huawei Mobile Partner (Windows) application. > It is a T-Mobile HU operator branded modem, with a T-Mobile HU issued SIM. > > What did I do wrong? Do you have any idea? You mean the modem does no longer work? If it was T-Mobile branded, did you use the firmware from T-Mobile or directly from Huawei? I have never used the Huawei Mobile Partner, so cannot tell. How does the modem show up in your Linux-based system now?
Created attachment 110746 [details] ModemManager debug logs #2
Created attachment 110747 [details] NetworkManager debug logs #2
(In reply to Aleksander Morgado from comment #4) > (In reply to norbig from comment #3) > > Thanks for the clear explanation of the issue. > > > > I tried to upgrade the firmware from 11.609.18.00.00 to 11.609.18.00.158 (I > > was not able to find newer), it seemed that everything went fine. But since > > then, I get "The Specified SIM/USIM Card Can Be Used On This Device" from > > the official Huawei Mobile Partner (Windows) application. > > It is a T-Mobile HU operator branded modem, with a T-Mobile HU issued SIM. > > > > What did I do wrong? Do you have any idea? > > You mean the modem does no longer work? If it was T-Mobile branded, did you > use the firmware from T-Mobile or directly from Huawei? I have never used > the Huawei Mobile Partner, so cannot tell. > > How does the modem show up in your Linux-based system now? I think the modem is still functioning, at least, partially. After inserting the dongle, SIM PIN entry dialog pops up, when entering the correct PIN, the device shows up in nm-applet. But neither AT+ppp nor QMI mode connection works. I used the stock Huawei firmware, not the T-Mobile one (because I did not find any). Maybe this is the cause. Meanwhile I tested it with different operator's SIM, the result is the same. I attached the new debug logs.
(In reply to norbig from comment #5) > Created attachment 110746 [details] > ModemManager debug logs #2 That log doesn't have any QMI connection attempt; the modem just got into enabled state but no connection requested. If you retry, check that you end up seeing some "WDS Start Network" message in the QMI logs.
Created attachment 110750 [details] ModemManager debug log #3
Created attachment 110751 [details] NetworkManager debug logs #3
(In reply to Aleksander Morgado from comment #8) > (In reply to norbig from comment #5) > > Created attachment 110746 [details] > > ModemManager debug logs #2 > > That log doesn't have any QMI connection attempt; the modem just got into > enabled state but no connection requested. If you retry, check that you end > up seeing some "WDS Start Network" message in the QMI logs. Strange. I can not get such message. It seems it stucks at the following: [mm-broadband-modem-qmi.c:3907] common_process_serving_system_3gpp(): Processing 3GPP info... [mm-iface-modem-3gpp.c:273] run_registration_checks_ready(): 3GPP registration check timed out
FYI. The operator has replaced my faulty modem with another and newer one. So I am closing this bug now. Aleksander, thank you very much for all of your work and help.
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.