ttyUSBx does not appear in /dev/ when connecting my MangOH green to my Ubuntu machine


#1

Hello,

I have a MangOH green board with WP8548.
I installed Release 12.2 via one-click program on Windows.
The board seems to work ok on Windows. When I connect it via USB to my Win 7 machine I can see all the COM ports enumerating correctly. I can connect to the AT port and issue AT commands.

However, when I connect the board via USB to my Ubuntu machine, there is no ttyUSBx device in the /dev/ directory.

acal@acal-Latitude-E6430:~$ ls /dev/ttyU*
ls: cannot access ‘/dev/ttyU*’: No such file or directory

I can still connect via Ethernet Over USB. This is the cm info output:
root@swi-mdm9x15:~# cm info
Device: WP8548
IMEI: 359377060014130
FSN: LL604200060105
Firmware: SWI9X15Y_07.11.11.00 r33161 CARMD-EV-FRMWR1 2016/09/20 16:36:44
Bootloader: SWI9X15Y_07.11.11.00 r33161 CARMD-EV-FRMWR1 2016/09/20 16:36:44

I can see that the board is listed in the usb device list (Bus 003 Device 010: ID 1199:68c0 Sierra Wireless, Inc.):

acal@acal-Latitude-E6430:~$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 0c45:643f Microdia Dell Integrated HD Webcam
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 04f3:0212 Elan Microelectronics Corp. Laser Mouse
Bus 003 Device 010: ID 1199:68c0 Sierra Wireless, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

However, when I run the dmesg program after connecting the board, I get the following:

[65679.336090] usb 3-2: new high-speed USB device number 10 using xhci_hcd
[65679.472760] usb 3-2: config 1 has an invalid interface number: 16 but max is 11
[65679.472767] usb 3-2: config 1 has an invalid interface number: 17 but max is 11
[65679.472771] usb 3-2: config 1 has an invalid interface number: 17 but max is 11
[65679.472774] usb 3-2: config 1 has an invalid interface number: 18 but max is 11
[65679.472777] usb 3-2: config 1 has an invalid interface number: 18 but max is 11
[65679.472780] usb 3-2: config 1 has an invalid interface number: 19 but max is 11
[65679.472783] usb 3-2: config 1 has an invalid interface number: 20 but max is 11
[65679.472785] usb 3-2: config 1 has an invalid interface number: 20 but max is 11
[65679.472788] usb 3-2: config 1 has no interface number 1
[65679.472791] usb 3-2: config 1 has no interface number 6
[65679.472794] usb 3-2: config 1 has no interface number 7
[65679.472796] usb 3-2: config 1 has no interface number 9
[65679.472799] usb 3-2: config 1 has no interface number 11
[65679.473443] usb 3-2: New USB device found, idVendor=1199, idProduct=68c0
[65679.473450] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[65679.473454] usb 3-2: Product: WP8548
[65679.473457] usb 3-2: Manufacturer: Sierra Wireless, Incorporated
[65679.473459] usb 3-2: SerialNumber: 4a01c075c38d
DEF
[65679.520573] cdc_ether 3-2:1.19 usb0: register ‘cdc_ether’ at usb-0000:00:14.0-2, CDC Ethernet Device, c6:96:65:fb:64:16
[65679.571858] cdc_ether 3-2:1.19 enp0s20u2i19: renamed from usb0
[65679.612232] IPv6: ADDRCONF(NETDEV_UP): enp0s20u2i19: link is not ready
[65679.612409] cdc_ether 3-2:1.19 enp0s20u2i19: kevent 12 may have been dropped
[65679.612417] cdc_ether 3-2:1.19 enp0s20u2i19: kevent 12 may have been dropped
[65679.717059] cdc_ether 3-2:1.19 enp0s20u2i19: kevent 12 may have been dropped

My conclusion is that the usb drivers on my Ubuntu machine are compromised or missing.
What’s your view? What can I do to fix this problem?

BR
Luigi


#2

what version of ubuntu are you using?


#3

I’m using Ubuntu 16.04


#4

on your linux host, please run the following command:

$ sudo apt-get remove modemmanager

The reason for this the modem manager is broken on Ubuntu 16.04(it broke in 15.10 to be precise)

This should fix this issue


#5

Hi,

thanks for your answer.

Unfortunately, in my case the modemmanager package had been already removed, so the suggested command does not solve the problem. See below:

acal@acal-Latitude-E6430:~$ sudo apt-get remove modemmanager
[sudo] password for acal:
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package ‘modemmanager’ is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.
acal@acal-Latitude-E6430:~$ ls /dev/ttyU*
ls: cannot access ‘/dev/ttyU*’: No such file or directory
acal@acal-Latitude-E6430:~$

BR
Luigi


#6

Luigi,

My guess is that the drivers are broken (if they were there in the first place) on the host and need rebuilding into the system, just to confirm this what does the below return

modinfo GobiSerial //This is the key one
modinfo GobiNet

Do you see the qcqmi interface (create by GobiNet)?

When it is plugged into windows and you can send AT commands what does the below give back?

at!entercnd="A710"
at!usbcomp? //This is just to confirm the correct USB configuration as it might be that Windows has messed with this

I presume the host does not enumerate any other FX30’s or mangOH boards correctly?

Regards

Matt


#7

Hi Matt,

your guess is right. My USB drivers, that had been working for a long time, stopped working for unknown reasons. I re-istalled them and now i can see that the ttyUSB devices are correctly enumerated on my Linux system.

thanks and regards
Luigi