Unable to connect to wwan on lenovo x1 carbon

Bug #1183197 reported by Marc Ramaekers
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

network manager fails to establish a connection with the wwan on my lenovo x1 carbon.
I've disabled mbim using "options cdc_ncm prefer_mbim=0", so the driver indicated by network manager is cdc_acm.

When I try to make the connection, the process remains stuck at "Preparing to connect".
In the syslog I find the following (GSM connection failed: (32) Busy) :

May 21 20:11:24 x1 modem-manager[11921]: <debug> [1369167084.070302] [mm-at-serial-port.c:334] debug_log(): (ttyACM0): --> 'AT*ENAP?<CR>'
May 21 20:11:24 x1 modem-manager[11921]: <debug> [1369167084.084417] [mm-at-serial-port.c:334] debug_log(): (ttyACM0): <-- '<CR><LF>*ENAP:2,""<CR><LF>'
May 21 20:11:24 x1 modem-manager[11921]: <debug> [1369167084.085541] [mm-at-serial-port.c:334] debug_log(): (ttyACM0): <-- '<CR><LF>OK<CR><LF>'
May 21 20:11:24 x1 NetworkManager[11930]: <warn> GSM connection failed: (32) Busy
May 21 20:11:24 x1 NetworkManager[11930]: <info> (ttyACM0): device state change: prepare -> failed (reason 'modem-busy') [40 120 23]
May 21 20:11:24 x1 NetworkManager[11930]: <info> Marking connection 'Mobile Vikings' invalid.
May 21 20:11:24 x1 NetworkManager[11930]: <warn> Activation (ttyACM0) failed for connection 'Mobile Vikings'
May 21 20:11:24 x1 NetworkManager[11930]: <info> (ttyACM0): device state change: failed -> disconnected (reason 'none') [120 30 0]
May 21 20:11:24 x1 NetworkManager[11930]: <info> (ttyACM0): deactivating device (reason 'none') [0]

Connecting with wvdial allows to establish a connection, as can be seen from the log below.

--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
ATDT*99#
CONNECT
~[7f]}#@!}!}!} }=}#}%B#}%}(}"}'}"}!}$}%\}"}&} } } } }%}&anNBK{~
--> Carrier detected. Waiting for prompt.
~[7f]}#@!}!}"} }=}#}%B#}%}(}"}'}"}!}$}%\}"}&} } } } }%}&anNBx!~
--> PPP negotiation detected.
--> Starting pppd at Thu May 23 05:40:08 2013
--> Pid of pppd: 18795
--> Using interface ppp0
--> pppd: �[7f]
--> pppd: �[7f]
--> pppd: �[7f]
--> pppd: �[7f]
--> pppd: �[7f]
--> pppd: �[7f]
--> local IP address 10.44.86.76
--> pppd: �[7f]
--> remote IP address 10.64.64.64
--> pppd: �[7f]
--> primary DNS address 217.72.230.1
--> pppd: �[7f]
--> secondary DNS address 217.72.230.129
--> pppd: �[7f]

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: network-manager 0.9.8.0-0ubuntu6
Uname: Linux 3.8.4-030804-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Thu May 23 05:31:16 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-04-28 (25 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IpRoute:
 default via 192.168.42.129 dev usb0 proto static
 169.254.0.0/16 dev usb0 scope link metric 1000
 192.168.24.0/24 dev vmnet1 proto kernel scope link src 192.168.24.1
 192.168.42.0/24 dev usb0 proto kernel scope link src 192.168.42.17 metric 1
 192.168.245.0/24 dev vmnet8 proto kernel scope link src 192.168.245.1
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 usb0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/8
 ttyACM0 gsm disconnected /org/freedesktop/NetworkManager/Devices/7
 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.0 connected enabled enabled enabled enabled disabled

Revision history for this message
Marc Ramaekers (marc-ramaekers) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
hamish cunningham (hamish-dcs) wrote :

I have a similar problem on the X1 Carbon, running 12.04, trying to connect to a Vodafone contract mobile broadband

My symptoms are: mobile broadband is always disabled; to connect I first enable it, then click on the Vodafone connection to activate it. Most of the time it fails to connect. I do sometimes get a working connection, but in a minute or two it kicks me off.

Below what I get in syslog if I use nmcli to start the connection via
  nmcli -t con up id 'Vodafone Contract'

Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> Activation (ttyACM1) starting connection 'Vodafone Contract'
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> (ttyACM1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> Activation (ttyACM1) Stage 1 of 5 (Device Prepare) scheduled...
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> Activation (ttyACM1) Stage 1 of 5 (Device Prepare) started...
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> (ttyACM1): device state change: prepare -> need-auth (reason 'none') [40 60 0]
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> Activation (ttyACM1) Stage 1 of 5 (Device Prepare) complete.
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> Activation (ttyACM1) Stage 1 of 5 (Device Prepare) scheduled...
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> disconnect failed: (32) The serial port is not open.
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> Activation (ttyACM1) Stage 1 of 5 (Device Prepare) started...
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> (ttyACM1): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> Activation (ttyACM1) Stage 1 of 5 (Device Prepare) complete.
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <warn> GSM connection failed: (32) Sending command failed: device is not enabled
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> (ttyACM1): device state change: prepare -> failed (reason 'unknown') [40 120 1]
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> Marking connection 'Vodafone Contract' invalid.
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <warn> Activation (ttyACM1) failed.
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> (ttyACM1): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> (ttyACM1): deactivating device (reason 'none') [0]
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: nm_system_iface_flush_routes: assertion `ifindex > 0' failed
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: nm_system_iface_flush_addresses: assertion `ifindex > 0' failed
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> Policy set 'eduroam' (wlan0) as default for IPv4 routing and DNS.
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> Policy set 'eduroam' (wlan0) as default for IPv4 routing and DNS.
Jun 6 11:00:03 hc-x1 NetworkManager[1016]: <info> disconnect failed: (32) The serial port is not open.

Any ideas?
Thanks,
Hamish

Revision history for this message
Daniel Aleksandersen (da2x) wrote :

I have the same problem as Hamish.

Revision history for this message
Marc Ramaekers (marc-ramaekers) wrote :

Hi,

I work around it for now using wvdial. But not very practical...

Marc

Revision history for this message
Christian Weber (cw-k) wrote :

Hi,

"options cdc_ncm prefer_mbim=N" works if you use a newer kernel. It's an option for the kernel module only available in kernels > 3.8.5 I think. Personally I use kernel 3.11.x from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ with Lubuntu.

Chris

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.