NCM error: "Network device is not present"

Hello,

After a few hours to operate without problems, connection with NCM stop working suddenly.

I have a Huawei E3372 + Archer C7 v2 with OpenWrt 18.06.2.

In LuCI:
Screenshot_20190613_213630

In console:
ifstatus wwan

{
"up": false,
"pending": false,
"available": false,
"autostart": true,
"dynamic": false,
"proto": "ncm",
"data": {

    },
    "errors": [
            {
                    "subsystem": "interface",
                    "code": "NO_DEVICE"
            }
    ]

}

When I restart the router, everything is OK.

Do you have same problem? How can I debug?

Thanks.

I've seen this behaviour, too. Whilst I haven't found a reliable solution, I do find that ifup is usually adequate; no need to reboot the router (usually!)

Look at dmesg or logread output to see if your E3372 is disconnected somehow or if there are any relevant errors logged.

I have this:

$ dmesg
[224059.319848] usb 2-1: new full-speed USB device number 2 using ehci-platform
[245815.400022] usb 2-1: USB disconnect, device number 2

$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 12d1:1506 Huawei Technologies Co., Ltd. Modem/Networkcard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ ls /dev/ttyUSB0
/dev/ttyUSB0

It may be that the USB device is not getting enough power from the port and disconnect/restart. If you have a powered hub, you can test with that. (but this is a wild guess). The led on your usb stick can be helpful in telling what the stick is doing currently.

Ultimately, it is difficult to say with so little information... Perhaps somebody else with Archer C7 v2 can comment on the issue.

I am at home for a time now. And the problem is present at the moment!

So if you have ideas, I can send you logs or something else, I really don't know how to find the real problem :confused:

You already posted log that your device thinks your USB disconnected. If you did not remove it yourself.
Either your USB stick is faulty or it does not get enough power. Those are my guesses.
You could try to use a powered USB hub and see if it resolves the issue.

1 Like