Re: NM 0.9 with Sierra USB 305 modem connection problems
On Fri, 2011-08-26 at 02:55 +0700, Arief M Utama wrote: Hi all, I'm using Debian's NM 0.9 with MM 0.5 (from experimental repo), with Sierra Wireless modem USB 305 (USB id: 1199:68a3) mobile broadband connection does not work. I bought a 305 off ebay and implemented support for it in latest git master and MM 0.5 last week. If you're able, please try it out and let me know how it works for you. Dan Actually since 0.8 it never really worked well, but on 0.8.4 release it was bit better, at least sometimes it managed to connect. Connecting with ppp chatscripts always worked flawlessly though so we can be sure it's not an issue with the modem hardware. Attached is a copy of syslog of a latest session. I'll be happy to help with more debugging. Thank you for helps and pointers. All the best. -arief ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.9 with Sierra USB 305 modem connection problems
Hey! One thing I do see is 'ATD*99***1***2#CR'. This does not match the settings I entered in. Mobile Broadband Settings: Connection name: ATT Mobile IPv4 Method: Automatic(PPP) Mobile Broadband Number: *99***1# Mobile Broadband APN: isp.cingular Type: Any Allow roaming PPP Authentication Allowed methods: EAP,PAP,CHAP,MSCHAPv2,MSCHAP Do not use MPPE Allow BSD compression Allow Deflate data compression Use TCP header compression Do not Send PPP echo packets That connect string does indeed look wrong to me. ModemManager found in the AT+CGDCONT? reply that the PDP context with CID=2 matches the APN you passed to use, so it appends ***2# to the number to be called. Question is, why do you have ***1# specified in the Mobile Broadband Number? Try using *99# as number in the settings and let ModemManager append the CID when it finds the context. Anyway, we should possibly fix ModemManager to not add the extra chunk with the CID if there is already one available. -- Aleksander That did work! Good to know :) The reason I used *99***1# is because that's what the settings in Win7 showed. What is the difference between the 1# and the 2#? '1' and '2' are context identifiers (CIDs) of different PDP contexts. In your case #1 was a PDP context without predefined APN, and #2 was a PDP context with 'isp.cingular' as APN (as per the +CGDCONT? reply). If an APN is given to ModemManager when trying to connect, it will try to find an exact match in the list of PDP contexts, and in your case it found it (#2), so it does the ATD call specifying to use PDP context #2. Now, you already had specified the CID yourself in the number passed, with the ***1# extra chunk, so MM ended up appending the extra ***2#. It should be pretty safe from the MM side to avoid that and don't even bother looking for the match in the list of PDP contexts if the number passed already has the PDP context identifier. I'll implement that in the 06-api branch. And Thank you ! :-D Welcome :-) Cheers, -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.9 with Sierra USB 305 modem connection problems
One thing I do see is 'ATD*99***1***2#CR'. This does not match the settings I entered in. Mobile Broadband Settings: Connection name: ATT Mobile IPv4 Method: Automatic(PPP) Mobile Broadband Number: *99***1# Mobile Broadband APN: isp.cingular Type: Any Allow roaming PPP Authentication Allowed methods: EAP,PAP,CHAP,MSCHAPv2,MSCHAP Do not use MPPE Allow BSD compression Allow Deflate data compression Use TCP header compression Do not Send PPP echo packets The procedure I followed: $ sudo service network-manager stop $ sudo killall -TERM modem-manager $ sudo modem-manager --debug 21 | tee ~cynthia/john/modem-manager.log $ sudo NM_PPP_DEBUG=1 /usr/sbin/NetworkManager --no-daemon 21 | tee ~cynthia/john/NetworkManager.log insert modem click network-manager icon click ATT Mobile $ fg 2 ^C $ fg 1 ^C NetworkManager.log: Failed to read classid file: Object not found NetworkManager[2208]: info NetworkManager (version 0.9.1.90) is starting... NetworkManager[2208]: info Read config file /etc/NetworkManager/NetworkManager.conf NetworkManager[2208]: info VPN: loaded org.freedesktop.NetworkManager.pptp NetworkManager[2208]:SCPlugin-Ifupdown: init! NetworkManager[2208]:SCPlugin-Ifupdown: update_system_hostname NetworkManager[2208]:SCPluginIfupdown: management mode: unmanaged NetworkManager[2208]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:1c.1/:05:00.0/net/eth0, iface: eth0) NetworkManager[2208]:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:1c.1/:05:00.0/net/eth0, iface: eth0): no ifupdown configuration found. NetworkManager[2208]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:1c.3/:09:00.0/net/wlan0, iface: wlan0) NetworkManager[2208]:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:1c.3/:09:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found. NetworkManager[2208]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo) NetworkManager[2208]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. NetworkManager[2208]:SCPlugin-Ifupdown: end _init. NetworkManager[2208]: info Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. NetworkManager[2208]: info Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager[2208]:Ifupdown: get unmanaged devices count: 0 NetworkManager[2208]:SCPlugin-Ifupdown: (35422000) ... get_connections. NetworkManager[2208]:SCPlugin-Ifupdown: (35422000) ... get_connections (managed=false): return empty list. NetworkManager[2208]:keyfile: parsing ATT Mobile ... NetworkManager[2208]:keyfile: read connection 'ATT Mobile' NetworkManager[2208]:keyfile: parsing John's ... NetworkManager[2208]:keyfile: read connection 'John's' NetworkManager[2208]:keyfile: parsing Wired connection 1 ... NetworkManager[2208]:keyfile: read connection 'Wired connection 1' NetworkManager[2208]:Ifupdown: get unmanaged devices count: 0 NetworkManager[2208]: info modem-manager is now available NetworkManager[2208]: info monitoring kernel firmware directory '/lib/firmware'. NetworkManager[2208]: info found WiFi radio killswitch rfkill3 (at /sys/devices/pci:00/:00:1c.3/:09:00.0/ieee80211/phy0/rfkill3) (driver (unknown)) NetworkManager[2208]: info found WiFi radio killswitch rfkill1 (at /sys/devices/platform/dell-laptop/rfkill/rfkill1) (driver dell-laptop) NetworkManager[2208]: info WiFi disabled by radio killswitch; disabled by state file NetworkManager[2208]: info WWAN enabled by radio killswitch; enabled by state file NetworkManager[2208]: info WiMAX enabled by radio killswitch; enabled by state file NetworkManager[2208]: info Networking is enabled by state file NetworkManager[2208]: info (eth0): carrier is OFF NetworkManager[2208]: info (eth0): new Ethernet device (driver: 'r8169' ifindex: 2) NetworkManager[2208]: info (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager[2208]: info (eth0): now managed NetworkManager[2208]: info (eth0): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] NetworkManager[2208]: info (eth0): bringing up device. NetworkManager[2208]: info (eth0): preparing device. NetworkManager[2208]: info (eth0): deactivating device (reason 'managed') [2] NetworkManager[2208]: info (wlan0): driver supports SSID scans (scan_capa 0x01). NetworkManager[2208]: info (wlan0): new 802.11 WiFi device (driver: 'iwlagn' ifindex: 3) NetworkManager[2208]: info (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 NetworkManager[2208]: info (wlan0): now managed NetworkManager[2208]: info (wlan0): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] NetworkManager[2208]: info (wlan0): bringing up device.
Re: NM 0.9 with Sierra USB 305 modem connection problems
On 12/21/2011 07:00 PM, John Hibbs wrote: One thing I do see is 'ATD*99***1***2#CR'. This does not match the settings I entered in. Mobile Broadband Settings: Connection name: ATT Mobile IPv4 Method: Automatic(PPP) Mobile Broadband Number: *99***1# Mobile Broadband APN: isp.cingular Type: Any Allow roaming PPP Authentication Allowed methods: EAP,PAP,CHAP,MSCHAPv2,MSCHAP Do not use MPPE Allow BSD compression Allow Deflate data compression Use TCP header compression Do not Send PPP echo packets That connect string does indeed look wrong to me. ModemManager found in the AT+CGDCONT? reply that the PDP context with CID=2 matches the APN you passed to use, so it appends ***2# to the number to be called. Question is, why do you have ***1# specified in the Mobile Broadband Number? Try using *99# as number in the settings and let ModemManager append the CID when it finds the context. Anyway, we should possibly fix ModemManager to not add the extra chunk with the CID if there is already one available. -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.9 with Sierra USB 305 modem connection problems
Has this been resolved? I have the same modem. http://mail.gnome.org/archives/networkmanager-list/2011-August/msg00238.html ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.9 with Sierra USB 305 modem connection problems
Pardon me for butting in, but I'm curious. I've never seen any GSM modem (including the Sierra 305) that didn't work with +CGDCONT. Is there something that the $IPDPCFG and $QCPDPP gives you +CGDCONT doesn't? On Thu, Aug 25, 2011 at 5:09 PM, Dan Williams d...@redhat.com wrote: On Fri, 2011-08-26 at 03:48 +0700, Arief M Utama wrote: On 08/26/2011 03:27 AM, Dan Williams wrote: On Fri, 2011-08-26 at 02:55 +0700, Arief M Utama wrote: Hi all, I'm using Debian's NM 0.9 with MM 0.5 (from experimental repo), with Sierra Wireless modem USB 305 (USB id: 1199:68a3) mobile broadband connection does not work. When the modem is inserted, is the 'sierra_net' driver loaded? Any chance you can get ModemManager debug logging so we can diagnose? Yep, it is loaded. http://live.gnome.org/NetworkManager/Debugging the instructions under Debugging NetworkManager 0.8.x 3G connections still apply to 0.9. FYI I have a 306 that I've tested with so at least we expect it to work. Following that instructions, herewith I attached the log result. Bit more info, I already created a Telkomsel Flash connection using nm-connection-editor, connecting by clicking on it from the gnome-shell applet. Tried twice, same result no connection. On first try it shows you are connected notification but it's actually not connected (probably a gnome-shell issue). On second try it just went to disconnected message quickly. I left my WiFi connection up during the test. One more thing, I noted from the debug log, so many AT commands was sent to the modem. Wondered about this, as with my ppp chatscripts, basically I only use following AT commands to make it work flawlessly: Using wvdial doesn't allow use of the network port the modem exposes, which limits the connection speed; at the higher 3G/4G speeds we're seeing these days, PPP just doesn't allow full throughput. Plus, when using the network port, we can get connection status and signal strength on the AT command port, which you can't do when you're using PPP on a lot of devices. Basically, MM does a lot more than just connect, it also delivers status updates, signal strength, SMS, etc. --- start chatscript snippet --- # cease if the modem is not attached to the network yet ABORT+CGATT: 0 AT TIMEOUT12 OKATH OKATE1 OKAT+CGDCONT=1,IP,\T,,0,0 OKATD*99# TIMEOUT22 CONNECT --- end chatscript snippet --- Hope this helps, let me know if more is needed and thanks for the help. So the core problem is this: modem-manager[27390]: debug [1314304573.585330] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0): -- 'AT$QCPDPP=1,1,wap123,wapCR' modem-manager[27390]: debug [1314304573.619827] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0): -- 'CRLFERRORCRLF' Grr. You've got the USB Lightning, which appears to use an Icera chipset, not a Qualcomm one: http://sierrawireless.custhelp.com/app/answers/detail/a_id/641/~/can-i-use-a-sierra-wireless-modem-on-linux-machines-%28direct-ip-modems%29%3Fhttp://sierrawireless.custhelp.com/app/answers/detail/a_id/641/%7E/can-i-use-a-sierra-wireless-modem-on-linux-machines-%28direct-ip-modems%29%3F So we need to update ModemManager to use AT%IPDPCFG in this case instead of AT$QCPDPP like we do for Option NV modems that also use Icera chipsets. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM 0.9 with Sierra USB 305 modem connection problems
Hi all, I'm using Debian's NM 0.9 with MM 0.5 (from experimental repo), with Sierra Wireless modem USB 305 (USB id: 1199:68a3) mobile broadband connection does not work. Actually since 0.8 it never really worked well, but on 0.8.4 release it was bit better, at least sometimes it managed to connect. Connecting with ppp chatscripts always worked flawlessly though so we can be sure it's not an issue with the modem hardware. Attached is a copy of syslog of a latest session. I'll be happy to help with more debugging. Thank you for helps and pointers. All the best. -arief Aug 26 02:44:11 mawar NetworkManager[1396]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:1d.7/usb2/2-1/2-1:1.7/net/wwan0, iface: wwan0) Aug 26 02:44:11 mawar NetworkManager[1396]:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:1d.7/usb2/2-1/2-1:1.7/net/wwan0, iface: wwan0): no ifupdown configuration found. Aug 26 02:44:11 mawar modem-manager[1420]: info (ttyUSB0) opening serial port... Aug 26 02:44:11 mawar modem-manager[1420]: info (ttyUSB3) opening serial port... Aug 26 02:44:11 mawar modem-manager[1420]: info (ttyUSB2) opening serial port... Aug 26 02:44:11 mawar modem-manager[1420]: info (ttyUSB1) opening serial port... Aug 26 02:44:13 mawar modem-manager[1420]: info (ttyUSB0) closing serial port... Aug 26 02:44:13 mawar modem-manager[1420]: info (ttyUSB0) serial port closed Aug 26 02:44:13 mawar modem-manager[1420]: info (ttyUSB0) opening serial port... Aug 26 02:44:13 mawar modem-manager[1420]: info (Sierra): GSM modem /sys/devices/pci:00/:00:1d.7/usb2/2-1 claimed port ttyUSB0 Aug 26 02:44:13 mawar modem-manager[1420]: info (ttyUSB2) closing serial port... Aug 26 02:44:13 mawar modem-manager[1420]: info (ttyUSB2) serial port closed Aug 26 02:44:13 mawar modem-manager[1420]: info (Sierra): GSM modem /sys/devices/pci:00/:00:1d.7/usb2/2-1 claimed port ttyUSB2 Aug 26 02:44:13 mawar modem-manager[1420]: info (ttyUSB0) closing serial port... Aug 26 02:44:13 mawar modem-manager[1420]: info (ttyUSB0) serial port closed Aug 26 02:44:14 mawar modem-manager[1420]: info (Sierra): GSM modem /sys/devices/pci:00/:00:1d.7/usb2/2-1 claimed port wwan0 Aug 26 02:44:19 mawar modem-manager[1420]: info (ttyUSB3) closing serial port... Aug 26 02:44:19 mawar modem-manager[1420]: info (ttyUSB3) serial port closed Aug 26 02:44:24 mawar modem-manager[1420]: info (ttyUSB1) closing serial port... Aug 26 02:44:24 mawar modem-manager[1420]: info (ttyUSB1) serial port closed Aug 26 02:44:24 mawar modem-manager[1420]: info (ttyUSB1) opening serial port... Aug 26 02:44:30 mawar modem-manager[1420]: info (ttyUSB1) closing serial port... Aug 26 02:44:30 mawar modem-manager[1420]: info (ttyUSB1) serial port closed Aug 26 02:44:30 mawar NetworkManager[1396]: info WWAN now disabled by management service Aug 26 02:44:30 mawar NetworkManager[1396]: info (wwan0): new GSM/UMTS device (driver: 'sierra' ifindex: 6) Aug 26 02:44:30 mawar NetworkManager[1396]: info (wwan0): exported as /org/freedesktop/NetworkManager/Devices/3 Aug 26 02:44:30 mawar NetworkManager[1396]: info (wwan0): now managed Aug 26 02:44:30 mawar NetworkManager[1396]: info (wwan0): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Aug 26 02:44:30 mawar NetworkManager[1396]: info (wwan0): deactivating device (reason: 2). Aug 26 02:44:30 mawar NetworkManager[1396]: info (wwan0): device state change: unavailable - disconnected (reason 'none') [20 30 0] Aug 26 02:44:34 mawar NetworkManager[1396]: info Activation (wwan0) starting connection 'Telkomsel Flash' Aug 26 02:44:34 mawar NetworkManager[1396]: info (wwan0): device state change: disconnected - prepare (reason 'none') [30 40 0] Aug 26 02:44:34 mawar NetworkManager[1396]: info Activation (wwan0) Stage 1 of 5 (Device Prepare) scheduled... Aug 26 02:44:34 mawar NetworkManager[1396]: info Activation (wwan0) Stage 1 of 5 (Device Prepare) started... Aug 26 02:44:34 mawar NetworkManager[1396]: info (wwan0): device state change: prepare - need-auth (reason 'none') [40 60 0] Aug 26 02:44:34 mawar NetworkManager[1396]: info Activation (wwan0) Stage 1 of 5 (Device Prepare) complete. Aug 26 02:44:34 mawar NetworkManager[1396]: info Activation (wwan0) Stage 1 of 5 (Device Prepare) scheduled... Aug 26 02:44:34 mawar NetworkManager[1396]: info Activation (wwan0) Stage 1 of 5 (Device Prepare) started... Aug 26 02:44:34 mawar NetworkManager[1396]: info (wwan0): device state change: need-auth - prepare (reason 'none') [60 40 0] Aug 26 02:44:34 mawar NetworkManager[1396]: info Activation (wwan0) Stage 1 of 5 (Device Prepare) complete. Aug 26 02:44:34 mawar modem-manager[1420]: info (ttyUSB0) opening serial port... Aug 26 02:44:34 mawar modem-manager[1420]: info Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled - enabling) Aug 26 02:44:45 mawar modem-manager[1420]: info (ttyUSB2) opening serial port... Aug 26 02:44:45
Re: NM 0.9 with Sierra USB 305 modem connection problems
On Fri, 2011-08-26 at 02:55 +0700, Arief M Utama wrote: Hi all, I'm using Debian's NM 0.9 with MM 0.5 (from experimental repo), with Sierra Wireless modem USB 305 (USB id: 1199:68a3) mobile broadband connection does not work. When the modem is inserted, is the 'sierra_net' driver loaded? Any chance you can get ModemManager debug logging so we can diagnose? http://live.gnome.org/NetworkManager/Debugging the instructions under Debugging NetworkManager 0.8.x 3G connections still apply to 0.9. FYI I have a 306 that I've tested with so at least we expect it to work. Thanks, Dan Actually since 0.8 it never really worked well, but on 0.8.4 release it was bit better, at least sometimes it managed to connect. Connecting with ppp chatscripts always worked flawlessly though so we can be sure it's not an issue with the modem hardware. Attached is a copy of syslog of a latest session. I'll be happy to help with more debugging. Thank you for helps and pointers. All the best. -arief ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.9 with Sierra USB 305 modem connection problems
On 08/26/2011 03:27 AM, Dan Williams wrote: On Fri, 2011-08-26 at 02:55 +0700, Arief M Utama wrote: Hi all, I'm using Debian's NM 0.9 with MM 0.5 (from experimental repo), with Sierra Wireless modem USB 305 (USB id: 1199:68a3) mobile broadband connection does not work. When the modem is inserted, is the 'sierra_net' driver loaded? Any chance you can get ModemManager debug logging so we can diagnose? Yep, it is loaded. http://live.gnome.org/NetworkManager/Debugging the instructions under Debugging NetworkManager 0.8.x 3G connections still apply to 0.9. FYI I have a 306 that I've tested with so at least we expect it to work. Following that instructions, herewith I attached the log result. Bit more info, I already created a Telkomsel Flash connection using nm-connection-editor, connecting by clicking on it from the gnome-shell applet. Tried twice, same result no connection. On first try it shows you are connected notification but it's actually not connected (probably a gnome-shell issue). On second try it just went to disconnected message quickly. I left my WiFi connection up during the test. One more thing, I noted from the debug log, so many AT commands was sent to the modem. Wondered about this, as with my ppp chatscripts, basically I only use following AT commands to make it work flawlessly: --- start chatscript snippet --- # cease if the modem is not attached to the network yet ABORT+CGATT: 0 AT TIMEOUT12 OKATH OKATE1 OKAT+CGDCONT=1,IP,\T,,0,0 OKATD*99# TIMEOUT22 CONNECT --- end chatscript snippet --- Hope this helps, let me know if more is needed and thanks for the help. Thanks, Dan All the best. -arief NM-SierraUSB305_debuglog.tar.gz Description: GNU Zip compressed data ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.9 with Sierra USB 305 modem connection problems
On Fri, 2011-08-26 at 03:48 +0700, Arief M Utama wrote: On 08/26/2011 03:27 AM, Dan Williams wrote: On Fri, 2011-08-26 at 02:55 +0700, Arief M Utama wrote: Hi all, I'm using Debian's NM 0.9 with MM 0.5 (from experimental repo), with Sierra Wireless modem USB 305 (USB id: 1199:68a3) mobile broadband connection does not work. When the modem is inserted, is the 'sierra_net' driver loaded? Any chance you can get ModemManager debug logging so we can diagnose? Yep, it is loaded. http://live.gnome.org/NetworkManager/Debugging the instructions under Debugging NetworkManager 0.8.x 3G connections still apply to 0.9. FYI I have a 306 that I've tested with so at least we expect it to work. Following that instructions, herewith I attached the log result. Bit more info, I already created a Telkomsel Flash connection using nm-connection-editor, connecting by clicking on it from the gnome-shell applet. Tried twice, same result no connection. On first try it shows you are connected notification but it's actually not connected (probably a gnome-shell issue). On second try it just went to disconnected message quickly. I left my WiFi connection up during the test. One more thing, I noted from the debug log, so many AT commands was sent to the modem. Wondered about this, as with my ppp chatscripts, basically I only use following AT commands to make it work flawlessly: Using wvdial doesn't allow use of the network port the modem exposes, which limits the connection speed; at the higher 3G/4G speeds we're seeing these days, PPP just doesn't allow full throughput. Plus, when using the network port, we can get connection status and signal strength on the AT command port, which you can't do when you're using PPP on a lot of devices. Basically, MM does a lot more than just connect, it also delivers status updates, signal strength, SMS, etc. --- start chatscript snippet --- # cease if the modem is not attached to the network yet ABORT+CGATT: 0 AT TIMEOUT12 OKATH OKATE1 OKAT+CGDCONT=1,IP,\T,,0,0 OKATD*99# TIMEOUT22 CONNECT --- end chatscript snippet --- Hope this helps, let me know if more is needed and thanks for the help. So the core problem is this: modem-manager[27390]: debug [1314304573.585330] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0): -- 'AT$QCPDPP=1,1,wap123,wapCR' modem-manager[27390]: debug [1314304573.619827] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0): -- 'CRLFERRORCRLF' Grr. You've got the USB Lightning, which appears to use an Icera chipset, not a Qualcomm one: http://sierrawireless.custhelp.com/app/answers/detail/a_id/641/~/can-i-use-a-sierra-wireless-modem-on-linux-machines-%28direct-ip-modems%29%3F So we need to update ModemManager to use AT%IPDPCFG in this case instead of AT$QCPDPP like we do for Option NV modems that also use Icera chipsets. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.9 with Sierra USB 305 modem connection problems
On Thu, 2011-08-25 at 16:09 -0500, Dan Williams wrote: On Fri, 2011-08-26 at 03:48 +0700, Arief M Utama wrote: On 08/26/2011 03:27 AM, Dan Williams wrote: On Fri, 2011-08-26 at 02:55 +0700, Arief M Utama wrote: Hi all, I'm using Debian's NM 0.9 with MM 0.5 (from experimental repo), with Sierra Wireless modem USB 305 (USB id: 1199:68a3) mobile broadband connection does not work. When the modem is inserted, is the 'sierra_net' driver loaded? Any chance you can get ModemManager debug logging so we can diagnose? Yep, it is loaded. http://live.gnome.org/NetworkManager/Debugging the instructions under Debugging NetworkManager 0.8.x 3G connections still apply to 0.9. FYI I have a 306 that I've tested with so at least we expect it to work. Following that instructions, herewith I attached the log result. Bit more info, I already created a Telkomsel Flash connection using nm-connection-editor, connecting by clicking on it from the gnome-shell applet. Tried twice, same result no connection. On first try it shows you are connected notification but it's actually not connected (probably a gnome-shell issue). On second try it just went to disconnected message quickly. I left my WiFi connection up during the test. One more thing, I noted from the debug log, so many AT commands was sent to the modem. Wondered about this, as with my ppp chatscripts, basically I only use following AT commands to make it work flawlessly: Using wvdial doesn't allow use of the network port the modem exposes, which limits the connection speed; at the higher 3G/4G speeds we're seeing these days, PPP just doesn't allow full throughput. Plus, when using the network port, we can get connection status and signal strength on the AT command port, which you can't do when you're using PPP on a lot of devices. Basically, MM does a lot more than just connect, it also delivers status updates, signal strength, SMS, etc. --- start chatscript snippet --- # cease if the modem is not attached to the network yet ABORT+CGATT: 0 AT TIMEOUT12 OKATH OKATE1 OKAT+CGDCONT=1,IP,\T,,0,0 OKATD*99# TIMEOUT22 CONNECT --- end chatscript snippet --- Hope this helps, let me know if more is needed and thanks for the help. So the core problem is this: modem-manager[27390]: debug [1314304573.585330] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0): -- 'AT$QCPDPP=1,1,wap123,wapCR' modem-manager[27390]: debug [1314304573.619827] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0): -- 'CRLFERRORCRLF' Grr. You've got the USB Lightning, which appears to use an Icera chipset, not a Qualcomm one: http://sierrawireless.custhelp.com/app/answers/detail/a_id/641/~/can-i-use-a-sierra-wireless-modem-on-linux-machines-%28direct-ip-modems%29%3F So we need to update ModemManager to use AT%IPDPCFG in this case instead of AT$QCPDPP like we do for Option NV modems that also use Icera chipsets. Any chance you can check something for me quickly with minicom or screen or such? I'm interested in the response to the following commands: ATV AT+CLAC AT%IPSYS? AT!SELRAT? and we'll see how many of the Icera commands and how many of the normal Qualcomm/Sierra commands the device supports. That affects how we go about supporting this modem. If it's more of an Icera device, we'll use the generic Icera code we already have. If it's more of a Qualcomm/Sierra device (which I suspect isn't true because !SELRAT returned an error) then we'll just slightly modify the existing code. Thanks! Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.9 with Sierra USB 305 modem connection problems
On 08/26/2011 04:28 AM, Dan Williams wrote: On Thu, 2011-08-25 at 16:09 -0500, Dan Williams wrote: On Fri, 2011-08-26 at 03:48 +0700, Arief M Utama wrote: On 08/26/2011 03:27 AM, Dan Williams wrote: On Fri, 2011-08-26 at 02:55 +0700, Arief M Utama wrote: Hi all, I'm using Debian's NM 0.9 with MM 0.5 (from experimental repo), with Sierra Wireless modem USB 305 (USB id: 1199:68a3) mobile broadband connection does not work. When the modem is inserted, is the 'sierra_net' driver loaded? Any chance you can get ModemManager debug logging so we can diagnose? Yep, it is loaded. http://live.gnome.org/NetworkManager/Debugging the instructions under Debugging NetworkManager 0.8.x 3G connections still apply to 0.9. FYI I have a 306 that I've tested with so at least we expect it to work. Following that instructions, herewith I attached the log result. Bit more info, I already created a Telkomsel Flash connection using nm-connection-editor, connecting by clicking on it from the gnome-shell applet. Tried twice, same result no connection. On first try it shows you are connected notification but it's actually not connected (probably a gnome-shell issue). On second try it just went to disconnected message quickly. I left my WiFi connection up during the test. One more thing, I noted from the debug log, so many AT commands was sent to the modem. Wondered about this, as with my ppp chatscripts, basically I only use following AT commands to make it work flawlessly: Using wvdial doesn't allow use of the network port the modem exposes, which limits the connection speed; at the higher 3G/4G speeds we're seeing these days, PPP just doesn't allow full throughput. Plus, when using the network port, we can get connection status and signal strength on the AT command port, which you can't do when you're using PPP on a lot of devices. Basically, MM does a lot more than just connect, it also delivers status updates, signal strength, SMS, etc. --- start chatscript snippet --- # cease if the modem is not attached to the network yet ABORT+CGATT: 0 AT TIMEOUT12 OKATH OKATE1 OKAT+CGDCONT=1,IP,\T,,0,0 OKATD*99# TIMEOUT22 CONNECT --- end chatscript snippet --- Hope this helps, let me know if more is needed and thanks for the help. So the core problem is this: modem-manager[27390]:debug [1314304573.585330] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0): -- 'AT$QCPDPP=1,1,wap123,wapCR' modem-manager[27390]:debug [1314304573.619827] [mm-at-serial-port.c:298] debug_log(): (ttyUSB0):-- 'CRLFERRORCRLF' Grr. You've got the USB Lightning, which appears to use an Icera chipset, not a Qualcomm one: http://sierrawireless.custhelp.com/app/answers/detail/a_id/641/~/can-i-use-a-sierra-wireless-modem-on-linux-machines-%28direct-ip-modems%29%3F So we need to update ModemManager to use AT%IPDPCFG in this case instead of AT$QCPDPP like we do for Option NV modems that also use Icera chipsets. Any chance you can check something for me quickly with minicom or screen or such? I'm interested in the response to the following commands: Sure, here they are ATV ATV ACTIVE PROFILE E: 1 L: 0 M: 0 Q: 0 V: 1 X: 4 S0: 0 S2: 43 S3: 13 S4: 10 S5: 8 S6: 2 S7: 60 S8: 2 S10: 15 +CRC: 0 +CR: 0 +FCLASS: 0 +IMODE: 0 +CMGF: 0 +CSDH: 0 +ILRR: 0 +CRLP: 61,61,128,6,1,3 +CMEE: 2 +CBST: 116,1,0 +CNMI: 2,1,0,0,0 +CSTA: 129 +CSCS: IRA +CSNS: 0 +DS: 3,0,512,20 C: 1 D: 2 +CCWE: 0 *TDTX: 0 +CTZU: 0 +CTZR: 0 +CV120: 1,1,1,0,0,0 +CGAUTO: 3 *TGMTPCACT: 0 *TGMTPCA: 1 *THCFG: 0 *TTS61: 1 *TLDCA: 1 *TFFOS: 0 +CHSN: 0,0,0,0 *TLLC: 0 *TESTCSD: 0 *TRLP: 0,0 *TGPPPLOG: 0 *TSIMINS: 0 +CMUX: 0 +CCUG: 0,0,0 +CLIP: 0 +COLP: 0 +CCWA: 0 +CAOC: 1 +CLIR: 0 +CUSD: 0 +CSSU: 0 +CSSI: 0 +CDIP: 0 +VCID: 0 *TSTMODE: 2 +CSCA: +628110,145 +CSMP: 17,255,0,0 OK AT+CLAC AT+CLAC +CGMI +CGMM +CGMR +GMI +GMM +GMR D DT DP A DL D H +CHUP O +CMOD +CIND +CMEC +CMER +CACM +CAMM +CCLK $CCLK +CEER +CGSN +CIMI +CKPD +CLAC +CNUM +CPAS +CPBF +CPBR +CPBS +CPBW +CPUC +GCAP +GSN I P T +CGACT +CGANS +CGATT +CGCLASS +CGCMOD +CGDATA +CGDCONT +CGDSCONT +CGEREP +CGEQMIN +CGEQNEG +CGEQREQ +CGPADDR +CGQMIN +CGQREQ +CGREG +CGSMS +CGTFT +COPS +CPOL +COPN +CSQ $CSQ +CREG $CREG +CPLS +CMGD +CMGR +CSCA +CMGS +CMGC +CMSS +CMGL +CMGW +CPMS +CNMA +CMMS +CSCB C D F V W +CBST +CCWE +CGAUTO +CHSN +CMEE +CMGF +CNMI +CR +CRC +CRES +CRLP +CSAS +CSCS +CSNS +CSDH +CSTA +CSMP +CSMS +CTZR +CTZU +CV120 +FCLASS +ILRR E L M Q S0 S10 S2 S3 S4 S5 S6 S7 S8 V X Z +CFUN +CMAR +CPIN +CSIM +CRSM +CCHO +CCHC +CGLA +CRLA +CUAD +PACSP H +CAOC +CCFC +CCWA +CCUG +CDIP +CHLD +CLCK +CLCC +CLIP +CLIR +COLP +CPWD +CSSN +CUSD +VCID *TSTCR *TSTEV *TSTGC *TSTMODE *TSTMS *TSTPD *TSTRT *TSTRF *TSTTONE !LB I +GMI +CGMI +GMM +CGMM %SERIAL !SIMNOTINSTALLED +GMR +CGMR !SMSSTSEN !OSPSTAT !GVER !GRESET %MODE !BCINF !SWOCMODE !SWOCINVALIDATE !SWOCINFO !NE !NESIG !RSSI OK AT%IPSYS? AT%IPSYS? %IPSYS: 5,2 OK AT!SELRAT? AT!SELRAT? ERROR Thanks! Dan Thank
