# Loading GobiNet.ko driver error **URL:** \ **Category:** MC/EM Series\ **Created:** [November 19, 2018, 12:46pm UTC](https://forum.sierrawireless.com/t/loading-gobinet-ko-driver-error/14507 "2018-11-19T12:46:25Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Loo](https://avatars.discourse-cdn.com/v4/letter/l/5e9695/32.png) [@Loo](https://forum.sierrawireless.com/u/Loo)\ **Post date:** [November 19, 2018, 12:46pm UTC](https://forum.sierrawireless.com/t/loading-gobinet-ko-driver-error/14507/1 "2018-11-19T12:46:25Z")
Hi,ALL Has anyone encountered the following situation? The following error occurred when loading the driver,Drive version: S2.34N2.53 /lib/modules/4.1.0 # modprobe GobiSerial [240.742000] usbcore: registered new interface driver GobiSerial [240.743000] usbserial: USB Serial support registered for GobiSerial [240.752000] GobiSerial: 2018-08-24/SWI\_2.34:GobiSerial /lib/modules/4.1.0 # /usr/scripts/modem\_power.sh on /lib/modules/4.1.0 # [258.918000] usb 1-2: new high-speed USB device number 3 using atmel-ehci [259.034000] usb 1-2: config 1 has an invalid interface number: 8 but max is 3 [259.035000] usb 1-2: config 1 has no interface number 1 [259.038000] usb 1-2: New USB device found, idVendor=1199, idProduct=9091 [259.040000] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [259.044000] usb 1-2: Product: Sierra Wireless EM7565 Qualcomm® Snapdragon™ X16 LTE-A [259.045000] usb 1-2: Manufacturer: Sierra Wireless, Incorporated [259.047000] usb 1-2: SerialNumber: UF82338888041037 [259.054000] GobiSerial 1-2:1.0: GobiSerial converter detected [259.059000] usb 1-2: GobiSerial converter now attached to ttyUSB0 [259.069000] GobiSerial 1-2:1.2: GobiSerial converter detected [259.082000] usb 1-2: GobiSerial converter now attached to ttyUSB1 [259.101000] GobiSerial 1-2:1.3: GobiSerial converter detected [259.120000] usb 1-2: GobiSerial converter now attached to ttyUSB2 /lib/modules/4.1.0 # /lib/modules/4.1.0 # ftpget 192.168.0.10 GobiNet.ko /lib/modules/4.1.0 # modprobe GobiNet [287.050000] GobiNet: 2018-08-24/SWI\_2.53 [287.051000] QMAP Disabled [287.064000] GobiNet 1-2:1.8 eth1: register ‘GobiNet’ at usb-700000.ehci-2, GobiNet Ethernet Device, 3a:85:51:39:fe:37 [287.079000] USB Speed : USB 2.0 [287.080000] usbcore: registered new interface driver GobiNet /lib/modules/4.1.0 # [288.080000] BUG: scheduling while atomic: kworker/0:1/16/0x00000002 [288.081000] Modules linked in: GobiNet(O) GobiSerial(O) [last unloaded: GobiSerial] [288.086000] Preemption disabled at:[\< (null)\>] (null) [288.088000] [288.089000] CPU: 0 PID: 16 Comm: kworker/0:1 Tainted: G O 4.1.0 #5 [288.091000] Hardware name: Atmel AT91SAM9 [288.092000] Workqueue: probe0-1-2:1.8 gobi\_work\_handler [GobiNet] [288.093000] [] (unwind\_backtrace) from [] (show\_stack+0x10/0x14) [288.094000] [] (show\_stack) from [] (\_\_schedule\_bug+0x88/0xb4) [288.095000] [] (\_\_schedule\_bug) from [] (\_\_schedule+0x54/0x430) [288.096000] [] (\_\_schedule) from [] (schedule+0x98/0xb0) [288.097000] [] (schedule) from [] (schedule\_timeout+0x180/0x1a8) [288.099000] [] (schedule\_timeout) from [] (wait\_for\_common+0xfc/0x1c0) [288.100000] [] (wait\_for\_common) from [] (usb\_start\_wait\_urb+0x68/0xb0) [288.101000] [] (usb\_start\_wait\_urb) from [] (usb\_control\_msg+0xb4/0xd8) [288.102000] [] (usb\_control\_msg) from [] (RegisterQMIDevice+0x47c/0x6fc [GobiNet]) [288.104000] [] (RegisterQMIDevice [GobiNet]) from [] (work\_function+0xec/0x4e4 [GobiNet]) [288.105000] [] (work\_function [GobiNet]) from [] (gobi\_work\_handler+0xb4/0x100 [GobiNet]) [288.107000] [] (gobi\_work\_handler [GobiNet]) from [] (process\_one\_work+0x1c8/0x33c) [288.108000] [] (process\_one\_work) from [] (worker\_thread+0x364/0x474) [288.109000] [] (worker\_thread) from [] (kthread+0xc4/0xd4) [288.110000] [] (kthread) from [] (ret\_from\_fork+0x14/0x34) [288.124000] BUG: scheduling while atomic: kworker/0:1/16/0x00000005 [288.125000] Modules linked in: GobiNet(O) GobiSerial(O) [last unloaded: GobiSerial] [288.129000] Preemption disabled at:[\< (null)\>] (null) Regards ---
**Author:** ![jleitner](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@jleitner](https://forum.sierrawireless.com/u/jleitner)\ **Post date:** [November 20, 2018, 1:47am UTC](https://forum.sierrawireless.com/t/loading-gobinet-ko-driver-error/14507/2 "2018-11-20T01:47:17Z")
Hello, Which module are you using? EM/MX74xx or the EM75xx series? Are you running ARM 32 or 65-bit arch? What Linux kernel on your host? ---
**Author:** ![Loo](https://avatars.discourse-cdn.com/v4/letter/l/5e9695/32.png) [@Loo](https://forum.sierrawireless.com/u/Loo)\ **Post date:** [November 20, 2018, 1:55am UTC](https://forum.sierrawireless.com/t/loading-gobinet-ko-driver-error/14507/3 "2018-11-20T01:55:53Z")
@jleitner 1. Sierra Wireless EM7565 2. ARM-32 and mips have been reported to load GobiNet.ko error 3. arm-32 linux kernel version is： 4.1.0 4. mips kernel version is 3.10.49 Regards ---
**Author:** ![jleitner](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@jleitner](https://forum.sierrawireless.com/u/jleitner)\ **Post date:** [November 21, 2018, 4:04pm UTC](https://forum.sierrawireless.com/t/loading-gobinet-ko-driver-error/14507/4 "2018-11-21T16:04:46Z")
Is this occurring on both MIPS and ARM archs? Both of those kernels are supported and so please try the latest .54 drivers on the source site: [https://source.sierrawireless.com/resources/airprime/software/usb-drivers-linux-qmi-software-s2,-d-,35n2,-d-,54/](https://source.sierrawireless.com/resources/airprime/software/usb-drivers-linux-qmi-software-s2,-d-,35n2,-d-,54/) We might need to provide you a patch if you still can’t properly load the GobiNet driver. Where are you located? Jon ---
**Author:** ![Loo](https://avatars.discourse-cdn.com/v4/letter/l/5e9695/32.png) [@Loo](https://forum.sierrawireless.com/u/Loo)\ **Post date:** [November 27, 2018, 2:02am UTC](https://forum.sierrawireless.com/t/loading-gobinet-ko-driver-error/14507/5 "2018-11-27T02:02:27Z")
@jleitner I tried the latest .54 driver, ARM reported the same error, the kernel always prints the error message. The kernel of mips is also reported incorrectly. I am from Guangzhou, China. Regards ---
**Author:** ![jleitner](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@jleitner](https://forum.sierrawireless.com/u/jleitner)\ **Post date:** [November 27, 2018, 3:58am UTC](https://forum.sierrawireless.com/t/loading-gobinet-ko-driver-error/14507/6 "2018-11-27T03:58:35Z")
You will likely need a patch for the GobiNet driver. Are you working through a distributor or direct Sierra Wireless account manager? We will need a support ticket created by the Chinese distributor or account manager in order for our Linux team to provide you with the patch. Please let me know and I will forward to the appropriate team. ---
**Author:** ![jleitner](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@jleitner](https://forum.sierrawireless.com/u/jleitner)\ **Post date:** [December 5, 2018, 4:50pm UTC](https://forum.sierrawireless.com/t/loading-gobinet-ko-driver-error/14507/7 "2018-12-05T16:50:16Z")
Hello, any update on this issue? I have a GobiNet patch that might address this issue. ---
**Author:** ![Loo](https://avatars.discourse-cdn.com/v4/letter/l/5e9695/32.png) [@Loo](https://forum.sierrawireless.com/u/Loo)\ **Post date:** [December 17, 2018, 1:39am UTC](https://forum.sierrawireless.com/t/loading-gobinet-ko-driver-error/14507/8 "2018-12-17T01:39:23Z")
Hi， @jleitner Sorry, I haven’t submitted this question to the distributor. When I submit the problem to the dealer, I will inform you, thank you. Recently, I adapted the EM7565 device on the mipsel platform. The driver is loaded without error, but there will be some zombie processes. ---
**Author:** ![jleitner](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@jleitner](https://forum.sierrawireless.com/u/jleitner)\ **Post date:** [December 17, 2018, 11:26pm UTC](https://forum.sierrawireless.com/t/loading-gobinet-ko-driver-error/14507/9 "2018-12-17T23:26:44Z")
No worries and good to hear about the initial testing with the EM7565 for MIPSEL. For further support on issues that might require gobi driver patches and the like, again best to have your distributor submit a ticket with sierra wireless.