Changes between Version 60 and Version 61 of wireless/modem

Timestamp:

11/12/2020 05:21:49 PM (4 years ago)

Author:

Ryan Erbstoesser

Comment:

update troubleshooting and add note about routing interfaces conflict

wireless/modem

@@ -1149 +1149 @@
 
 
-[=#troubleshooting]
+[=#troubleshootingonubuntu]
 === Troubleshooting Modem support on Ubuntu ===
+
+Please use this section as well as the [#troubleshooting Generic Modem Troubleshooting] section below. 
+
 Because modem technology is constantly changing it is often best to try to get it working on the most modern Linux system possible with up to date kernel drivers and libraries. Often this is easily accomplished with Ubuntu under the following circumstances:
- - use the latest mainline Linux kernel if you can, otherwise use the most recent available Ubuntu kernel
- - use the latest !ModemManager, libqmi, and libmbim PPA's (see above)
+ - Use the latest mainline Linux kernel if you can, otherwise use the most recent available Ubuntu kernel
+ - Use the latest !ModemManager, libqmi, and libmbim PPA's (see above)
 
 Use !ModemManager to see if your modem is detected and attempt connecting. Querying a modem with !ModemManager will also tell you what control interfaces exist and what type of control they use which is critical to understanding the requirements for your modem.
@@ -1884 +1887 @@
  * Make sure your modem is being recognized on the USB bus with {{{lsusb}}}
   - if not, check that the USB bus is correctly steered to the miniPCIe socket the modem is installed in (see the [wiki:USB#steering USB Steering] wiki page)
-  - make sure the modem supports USB 2.0
-  - check the modem pinout and ensure that it is compatible with PCIe signalling if used on a miniPCIe socket with PCIe (Sierra Wireless -V modems can not have the PERST# signal at 3p3V - see [#vaux1 here])
+  - Make sure the modem supports USB 2.0
+  - Check the modem pinout and ensure that it is compatible with PCIe signalling if used on a miniPCIe socket with PCIe (Sierra Wireless -V modems can not have the PERST# signal at 3p3V - see [#vaux1 here])
  * Does your modem require a driver or driver update that is not available in the Linux kernel version you are using?
-  - a {{{lsusb}}} will show the Vendor ID and Product ID of your device which typically need to match known ID's in drivers (some newer devices match USB class ID's and are more forgiving)
-  - look at the kernel messages from the {{{dmesg}}} command for messages that might indicate a modem is not supported or lack of a known driver supporting that device. Most modem drivers will create a number of 'tty' devices in /dev/tty* - if you see no messages about this you may be missing driver support.
+  - A {{{lsusb}}} will show the Vendor ID and Product ID of your device which typically need to match known ID's in drivers (some newer devices match USB class ID's and are more forgiving)
+  - Look at the kernel messages from the {{{dmesg}}} command for messages that might indicate a modem is not supported or lack of a known driver supporting that device. Most modem drivers will create a number of 'tty' devices in /dev/tty* - if you see no messages about this you may be missing driver support.
  * Make sure no other processes are interacting with your M2M device communication ports (ie mis-configured {{{gpsd}}})
  * Is your GSM module locked to a Carrier/Network/SIM/PIN? - if so you have to unlock it (if possible/allowed)
@@ -1901 +1904 @@
 [ -e /dev/ttyUSBX ] && echo -e -n "AT~RESET\r" > /dev/ttyUSBX
 }}}
+ * There cannot be two routes to the internet. This means if the modem is connecting to the internet, and eth0 is also connected to a network with an internet, this will cause conflict. Only one interface in the routing table can connect to the internet. Thus, it can be important to check other interfaces, such as eth0, and ensure they are not configured to connect to a WAN / or to a gateway.