Is your apn ok to use?
What is the return of at!impref?
!IMPREF:
preferred fw version: 02.24.05.06
preferred carrier name: GENERIC
preferred config name: GENERIC_002.026_000
current fw version: 02.24.05.06
current carrier name: GENERIC
current config name: GENERIC_002.026_000
what is the “dmesg” in linux?
Well, that puts out a lot of information. Are you looking for something specific? If you’re looking for information about Gobi, then please see my post a few posts ago.
I don’t see the GobiNet driver is generating the ethernet interface like eth1.
I can check the inferfaces with ifconfig, right? Then I have eth0, lo, rndis0, usb0, wlan0
dmesg | grep -i “gobi” returns:
[ 6.989153] GobiNet: loading out-of-tree module taints kernel.
[ 6.989337] GobiNet: loading out-of-tree module taints kernel.
[ 6.995703] GobiNet: 2020-08-17/SWI_2.64
[ 6.995976] usbcore: registered new interface driver GobiNet
[ 7.015844] usbcore: registered new interface driver GobiSerial
[ 7.015884] usbserial: USB Serial support registered for GobiSerial
[ 7.022000] GobiSerial 2-3.4:1.0: GobiSerial converter detected
[ 7.024447] usb 2-3.4: GobiSerial converter now attached to ttyUSB0
[ 7.036449] GobiSerial 2-3.4:1.2: GobiSerial converter detected
[ 7.037751] usb 2-3.4: GobiSerial converter now attached to ttyUSB1
[ 7.047191] GobiSerial 2-3.4:1.3: GobiSerial converter detected
[ 7.049786] usb 2-3.4: GobiSerial converter now attached to ttyUSB2
[ 7.049851] GobiSerial: 2020-08-17/SWI_2.42:GobiSerial
you should check with dmesg, normally I will see eth1 generated by GobiNET driver
you can see a correct log here:
[15382.352606] GobiNet 3-1:1.8 eth1: register ‘GobiNet’ at usb-0000:00:14.0-1, GobiNet Ethernet Device, c6:f9:56:d8:1b:fb
All I can see in my dmesg log about GobiNet is:
[ 7.265759] GobiNet: loading out-of-tree module taints kernel.
[ 7.265779] GobiNet: loading out-of-tree module taints kernel.
[ 7.271937] GobiNet: 2020-08-17/SWI_2.64
[ 7.273527] usbcore: registered new interface driver GobiNet
did you reset the board after setting AT!USBCOMP to enable RMNET
No I did’nt, should I?
yes, please do so
…
AT!RESET done. What do I need to do next?
check dmesg again then…
I did restart my system and now I have:
[ 7.136641] GobiNet: loading out-of-tree module taints kernel.
[ 7.143986] GobiNet: 2020-08-17/SWI_2.64
[ 7.150980] GobiNet 2-3.4:1.8 eth1: register ‘GobiNet’ at usb-3610000.xhci-3.4, GobiNet Ethernet Device, 3e:a7:fa:d6:1a:08
[ 7.152377] usbcore: registered new interface driver GobiNet
Now I also see a mobile broadband connection in the menu of the OS. I was also able to access websites using the web browser ober the mobile broadband connection. Seems to work now, great!
Thank you for your help!
If you’re using Ubuntu, I don’t think the mobile broadband connection in the menu of the OS has nothing to do with the GobiNet driver you just installed. If the connection is working, it’s possibly because you’re using the modem in MBIM mode, using cdc_mbim, libmbim and ModemManager+NetworkManager.
If you run “mmcli -L” and “mmcli -m 0” you could confirm that.
And if so, you could also remove the custom built GobiNet and GobiSerial completely. Unless I’m lost with something, there is absolutely no support for Gobinet+Gobiserial with the standard Ubuntu connection manager menu.
For problems on standard Linux distributions where qmi_wwan, cdc_mbim, libqmi, libmbim, ModemManager and NetworkManager are already available, you could also direct the user questions to the ModemManager mailing list here: ModemManager-devel Info Page
Otherwise you’re expecting the users to be experts in building kernel drivers and manually maintaining the WWAN connections in parallel to what NetworkManager does, and that is a bit overkill IMO. We already support the EM7455 in ModemManager+NetworkManager by default, why make it so complex asking to install the GobiNet driver? I know it’s what Sierra devs are supposed to do in the forum, but really, we don’t bite in the MM mailing list 
Hi aleksanderOm, thanks for your advice. I am not an expert on these modems and thus it is a bit hard to understand the different approaches. Personally I don’t mind which approach to use, I’m just happy if it works at the end 
First the modem was in MBIM mode and I naively expected the modem to work out of the box with the Linux drivers. This was somehow not the case.
By jyijyis advice, I installed the Gobi drivers and changed the modem to RMNET0 mode using the AT!USBCOMP command. So currently the modem is in RMNET0 mode. Then I set the APN of my provider with the command AT+CGDCONT=1,“IP”,“APN” and I was able to get a working data conection.
Later I inserted a SIM card of an other provider, so the APN needed to be changed. I did this via the OS menu. I got a working connection again. If I understand your information correctly, this actually shouldn’t work?
I can run “mmcli -L” and “mmcli -m 0” when I am back in the office next week. If you like to provide step by step guidance I am willing to check out the approach with MBIM mode, cdc_mbim, libmbim etc.