We failed to bring-up C7430 module in Ubuntu 16.04 Server edition. We compiled the driver source tree (SierraLinuxQMIdriversS2.34N2.53.tar.bz2) and expected driver are in place.
GobiSerial 20480 0
usbserial 53248 1 GobiSerial
GobiNet 155648 0
usbnet 45056 2 GobiNet,cdc_ether
But we failed to make this interface up and running. And noticed that dmesg throws the below error. Anyone can suggest where we are wrong ?
Below the logs generated, at the time of compiling and inserting the desired modules. We have noticed that the MODEM is rebooting in frequent intervals( there is no defined pattern). Is this because of the above mentioned bug ?
Dec 19 11:51:07 SugarOS kernel: [65523.417592] usbcore: registered new interface driver GobiSerial
Dec 19 11:51:07 SugarOS kernel: [65523.417618] usbserial: USB Serial support registered for GobiSerial
Dec 19 11:51:07 SugarOS kernel: [65523.418440] GobiSerial 1-1:1.0: GobiSerial converter detected
Dec 19 11:51:07 SugarOS kernel: [65523.418634] usb 1-1: GobiSerial converter now attached to ttyUSB0
Dec 19 11:51:07 SugarOS kernel: [65523.419294] GobiSerial 1-1:1.2: GobiSerial converter detected
Dec 19 11:51:07 SugarOS kernel: [65523.419448] usb 1-1: GobiSerial converter now attached to ttyUSB1
Dec 19 11:51:07 SugarOS kernel: [65523.420060] GobiSerial 1-1:1.3: GobiSerial converter detected
Dec 19 11:51:07 SugarOS kernel: [65523.420201] usb 1-1: GobiSerial converter now attached to ttyUSB2
Dec 19 11:51:07 SugarOS kernel: [65523.420252] GobiSerial: 2019-11-22/SWI_2.39:GobiSerial
Dec 19 11:52:46 SugarOS kernel: [65623.044271] GobiNet: 2019-11-22/SWI_2.60
Dec 19 11:52:46 SugarOS kernel: [65623.046249] GobiNet 1-1:1.8 eth0: register ‘GobiNet’ at usb-0000:00:15.0-1, GobiNet Ethernet Device, 96:57:4d:fd:43:08
Dec 19 11:52:46 SugarOS kernel: [65623.046661] USB Speed : USB 2.0
Dec 19 11:52:46 SugarOS kernel: [65623.047678] GobiNet 1-1:1.10 eth1: register ‘GobiNet’ at usb-0000:00:15.0-1, GobiNet Ethernet Device, 96:57:4d:fd:43:0a
Dec 19 11:52:46 SugarOS kernel: [65623.048059] USB Speed : USB 2.0
Dec 19 11:52:46 SugarOS kernel: [65623.048096] usbcore: registered new interface driver GobiNet
Dec 19 11:52:46 SugarOS kernel: [65623.057284] GobiNet 1-1:1.8 enp0s21f0u1i8: renamed from eth0
Dec 19 11:52:46 SugarOS kernel: [65623.077706] GobiNet 1-1:1.10 enp0s21f0u1i10: renamed from eth1
Dear @siji.sunny ,
I don’t think the issue comes from the GobiNet & GobiSerial drivers, because your dmesg log shows that the module was detected and attached to ttyUSB*. Besides, my dmesg log is also the same as yours, but I’m still able to connect to the AT port (ttyUSB2 or ttyUSB0 depends on the module’s USB configuration).
To help you find the solution, you could do some following steps:
1/ Unplug the module, reboot the ubuntu server, then re-plug the module
2/ Please make sure you use appropriate power supply for your module
3/ You could try plugging the module into different USB port
4/ You could consider update different firmware version for your module.
5/ If all of the above steps are useless, you could try different ubuntu computer
Dear Vianney,
Apologies for a late response.
We tried the recommended suggestions, 1,2,3,4 & 5 but no success yet. This issue been identified more than 20 devices (Ubuntu boxes) which we have deployed.
Dear @siji.sunny,
From your log, I’ve seen that ttyUSB* interfaces enumerated.
From understading of your issue, there are 2 things I need to make clear.
1/ If your issue is about AT command port. Please use Minicom to access to the ttyUSB0 or ttyUSB2 to check if you can use the AT port of the MC7430
2/ If your issue is about getting IP address for the GobiNet interface, then your could try the Linux QMI SDK https://source.sierrawireless.com/resources/airprime/software/linux-qmi-sdk-application-developer-guide-1,-d-,26/#sthash.sSjXrk2u.dpbs to bring up the interface or you could dial up the interface with shell script.