7354 Not Working in Kubuntu

IoT Modules MC/EM Series
1

I’ve compiled GobiNet and GobiSerial devices for 2.24 and 2.18 respectively, but when I plug in my MC7354, it’s not detected. I’m getting the following dmesg output:

[ 874.901737] GobiNet: 2014-04-15/SWI_2.24
[ 874.901765] usbcore: registered new interface driver GobiNet
[ 880.059989] usbcore: registered new interface driver usbserial
[ 880.060003] usbcore: registered new interface driver usbserial_generic
[ 880.060274] usbserial: USB Serial support registered for generic
[ 880.065681] usbcore: registered new interface driver GobiSerial
[ 880.065699] usbserial: USB Serial support registered for GobiSerial
[ 880.065705] GobiSerial: 2014-04-15/SWI_2.18:GobiSerial
[ 922.976260] usb 1-2: new full-speed USB device number 3 using ohci-pci
[ 923.421216] usb 1-2: config 1 has an invalid interface number: 8 but max is 5
[ 923.421226] usb 1-2: config 1 has an invalid interface number: 10 but max is 5
[ 923.421232] usb 1-2: config 1 has an invalid interface number: 11 but max is 5
[ 923.421239] usb 1-2: config 1 has no interface number 1
[ 923.421245] usb 1-2: config 1 has no interface number 4
[ 923.421251] usb 1-2: config 1 has no interface number 5
[ 923.437165] usb 1-2: New USB device found, idVendor=1199, idProduct=68c0
[ 923.437171] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 923.437176] usb 1-2: Product: MC7354
[ 923.437180] usb 1-2: Manufacturer: Sierra Wireless, Incorporated
[ 923.439162] usb 1-2: can’t set config #1, error -32

Neither the qcqmiX nor ttyUSBX devices appear in the device list.

I’m currently running Linux 3.11.0-17-generic. Also, the module works fine in Windows using Skylight Connection Manager.

2

Hi,

Can you try on a slightly older version of kernel i.e. 3.5? Is there any specific reason you are using 3.11?

Also just as background can you send the following in a terminal

lsusb
modinfo GobiSerial
modinfo GobiNet
ls /dev

Regards

Matt

3

This is unexpected. What kind of hardware is your USB host controller? Do you have the ehci-hcd and ehci-pci modules installed?

That’s a pretty final error from the USB core. Drivers don’t matter at all if you can’t even set the active configuration. We can rule out hardware errors since it works with Windows. So we should start looking at the host controller driver(s). The first question is the above: Why is the modem detected as a full speed device handled by ohci-pci instead of a high speed device handled by ehci-pci. I suspect the answer to that is related to the error.