# QMI interface unresponsive for first command **URL:** \ **Category:** MC/EM Series\ **Created:** [November 3, 2021, 7:05am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432 "2021-11-03T07:05:45Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![anjo.john](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@anjo.john](https://forum.sierrawireless.com/u/anjo.john)\ **Post date:** [November 3, 2021, 7:05am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/1 "2021-11-03T07:05:45Z")
Hi, While using EM7431 module, we encounter the QMI interface to be unresponsive in few conditions. 1. After power cycling, leaving the module for ~20 second, the first QMI request to the module is giving timeout “error: couldn’t create client for the ‘nas’ service: CID allocation failed in the CTL client: Transaction timed out”. From second command inwards, it working properly 2. After continuously using for 2 days, the internet is stopped, QMI and AT command interfaces are unresponsive. We had to manually reset the module to make it work. For the first issue, i would like to know if the module is going to some sleep or power saving mode because of inactivity. For second, How to debug this issue. I am using qmicli command for checking. Firmware version of module : [/dev/cdc-wdm0] Software version: S.AT.2.5.1-00666-9655\_GEN\_PACK-1 Revision: ‘SWI9X50C\_01.14.03.00 b06bd3 jenkins 2020/09/23 10:53:35’ ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [November 3, 2021, 2:21pm UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/2 "2021-11-03T14:21:48Z")
are you using the MBPL USB driver? > [@Example on establishing data connection by AT!SCACT via MBPL R20 driver](https://forum.sierrawireless.com/t/example-on-establishing-data-connection-by-at-scact-via-mbpl-r20-driver/24130): > > Here is an example to establish data connection by AT!SCACT via MBPL R20 driver: Module: WP7609 FW: R13 MBPL: R20 PC Environment: Ubuntu 18 need to install the MBPL R20 driver for qmi\_wwan and qcserial (MBPL\_Drivers\_USB\_R20\_ENG1-src.tar.gz) avoid the Ubuntu changing the network name: ln -s /dev/null /etc/systemd/network/99-default.link sudo apt-get install libqmi-utils sudo apt-get install udhcpc now insert the USB to PC sudo chmod 777 /sys/class/net/wwan0/qmi/raw\_ip … ---
**Author:** ![anjo.john](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@anjo.john](https://forum.sierrawireless.com/u/anjo.john)\ **Post date:** [November 4, 2021, 9:18am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/3 "2021-11-04T09:18:33Z")
Thanks for the quick reply. I am using generic driver of qmi\_wwan from mainline kernel version 4.14. The driver in MBPL R20 and this looks same. From the commands, where to specify the APN name. Does the module detects APN name automatically after calling the “AT!SCACT=1,1” command. ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [November 4, 2021, 9:31am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/4 "2021-11-04T09:31:11Z")
seems cannot use the default qmi\_wwan, you need to use the driver of MBPL. To enter APN, you can use AT+CGDCONT. e.g. AT+CGDCONT=1,“IP”,“APN” ---
**Author:** ![anjo.john](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@anjo.john](https://forum.sierrawireless.com/u/anjo.john)\ **Post date:** [November 4, 2021, 9:32am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/5 "2021-11-04T09:32:35Z")
Hi, Let me try this and comeback ---
**Author:** ![anjo.john](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@anjo.john](https://forum.sierrawireless.com/u/anjo.john)\ **Post date:** [November 5, 2021, 7:16am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/6 "2021-11-05T07:16:58Z")
Hi, I tried the default driver. it’s also showing the same issue for the first command. I would like to know why the first command to the device failed. Any methods to get the debug info from the module. ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [November 5, 2021, 8:18am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/7 "2021-11-05T08:18:10Z")
as said before, you should not use the default driver. BTW, does it work if you enter “sudo qmicli --device=/dev/cdc-wdm0 --wds-noop --client-no-release-cid” first? ---
**Author:** ![anjo.john](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@anjo.john](https://forum.sierrawireless.com/u/anjo.john)\ **Post date:** [November 5, 2021, 10:10am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/8 "2021-11-05T10:10:41Z")
Hi, I used the driver from MBPL SDK Still, The first qmi command is giving timeout. This is if i wait for sometime after power cycling the module. If the qmi command was given immediately after the power cycling, there no issue. That’s why i want to know whether the module is going to some power saving mode or something. ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [November 5, 2021, 10:20am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/9 "2021-11-05T10:20:04Z")
You can disable the usb selective suspend mode of your platform to verify ---
**Author:** ![anjo.john](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@anjo.john](https://forum.sierrawireless.com/u/anjo.john)\ **Post date:** [November 5, 2021, 10:30am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/10 "2021-11-05T10:30:48Z")
Hi, I could only see below command to make the module in suspend/active mode AT+CFUN=1 for active and AT+CFUN=0 for suspend. i could see the SIM registration getting disabled with the AT+CFUN=1=0 command. Still, the first QMI command is still failing. ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [November 5, 2021, 10:39am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/11 "2021-11-05T10:39:28Z")
BTW, does it work if you enter “sudo qmicli --device=/dev/cdc-wdm0 --wds-noop --client-no-release-cid” first? ---
**Author:** ![anjo.john](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@anjo.john](https://forum.sierrawireless.com/u/anjo.john)\ **Post date:** [November 5, 2021, 11:51am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/12 "2021-11-05T11:51:56Z")
No, having same result ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [November 5, 2021, 1:47pm UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/13 "2021-11-05T13:47:30Z")
If you keep typing AT command, the usb will be always turned on, you can check whether it is due to sleep mode ---
**Author:** ![anjo.john](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@anjo.john](https://forum.sierrawireless.com/u/anjo.john)\ **Post date:** [November 5, 2021, 2:21pm UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/14 "2021-11-05T14:21:46Z")
Thanks, Let me check this ---
**Author:** ![luxuemei](https://avatars.discourse-cdn.com/v4/letter/l/46a35a/32.png) [@luxuemei](https://forum.sierrawireless.com/u/luxuemei)\ **Post date:** [August 9, 2023, 8:04pm UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/15 "2023-08-09T20:04:02Z")
Does anybody have answer to this issue? I’m seeing the save behavior with when using the qmicli for the first time with a EM7590 modem the first time after a reboot, but the subsequent commands are OK. ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [August 10, 2023, 2:01am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/16 "2023-08-10T02:01:44Z")
have you disabled selective suspend mode? If you keep typing AT command, the usb will be always turned on, you can check whether it is due to sleep mode ---
**Author:** ![luxuemei](https://avatars.discourse-cdn.com/v4/letter/l/46a35a/32.png) [@luxuemei](https://forum.sierrawireless.com/u/luxuemei)\ **Post date:** [August 10, 2023, 2:22am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/17 "2023-08-10T02:22:07Z")
How do I disable the selective suspend mode? I tried issuing an AT command followed immediately by the qmicli command, but still gets the timeout: root@sar:~# echo -e ‘at+cfun?\r\n’ \> /dev/ttyUSB2 root@sar:~# at+cfun? +CFUN: 1 OK root@sar:~# qmicli -p --device=/dev/cdc-wdm0 --dms-get-model error: couldn’t create client for the ‘dms’ service: CID allocation failed in the CTL client: Transaction timed out ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [August 10, 2023, 2:35am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/18 "2023-08-10T02:35:55Z")
I tried selective suspend setting on other module SL808x. see if this document can be reused: [How to test the sleep mode for SL808X under Linux.docx](https://forum.sierrawireless.com/uploads/short-url/5mN0YGZJ0B5MFXJawZfMZ5B9Etp.docx) (13.2 KB) ---
**Author:** ![luxuemei](https://avatars.discourse-cdn.com/v4/letter/l/46a35a/32.png) [@luxuemei](https://forum.sierrawireless.com/u/luxuemei)\ **Post date:** [August 10, 2023, 2:56am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/19 "2023-08-10T02:56:58Z")
The EM7590 doesn’t seem to have the same suspend setting, but thanks for the info anyways. root@sar:/sys/bus/usb/devices/1-1# ls 1-1:1.0 authorized bDeviceProtocol bNumConfigurations busnum dev driver ltm\_capable product rx\_lanes tx\_lanes 1-1:1.2 avoid\_reset\_quirk bDeviceSubClass bNumInterfaces configuration devnum ep\_00 manufacturer quirks speed uevent 1-1:1.3 bConfigurationValue bMaxPacketSize0 bcdDevice consumers devpath idProduct maxchild removable subsystem urbnum 1-1:1.8 bDeviceClass bMaxPower bmAttributes descriptors devspec idVendor port remove suppliers version ---
**Author:** ![gbrideau](https://avatars.discourse-cdn.com/v4/letter/g/7cd45c/32.png) [@gbrideau](https://forum.sierrawireless.com/u/gbrideau)\ **Post date:** [June 13, 2025, 12:03am UTC](https://forum.sierrawireless.com/t/qmi-interface-unresponsive-for-first-command/25432/20 "2025-06-13T00:03:49Z")
I was having the same problem and finally figured it out. Disabling modem manager sudo systemctl disable ModemManager solved the problem for me. Hope this helps!