NetworkManager 0.8 can't find my 3g modem (Huawei E180); installing modemmanager fixes it

[Andreas Gustafsson]

Binary package hint: network-manager

after updating network-manager in keramic (from 0.7.1.git.5.272c6a626-0ubuntu1_i386 to 0.8~git.20090804t185522.4bab334-0ubuntu1_i386) the 3g connection option does not appear when inserting the modem. Rolling back and restarting NetworkManager resolves the problem.

[Ante Karamatić (ivoks)]

I have simillar issue. NM detects my modem, but it doesn't set up a connection. Reverting to older NM and purging modemmanager solves the issue.

Log:

Aug 12 10:29:38 titan NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Aug 12 10:29:38 titan NetworkManager: <info> (ttyUSB0): device state change: 5 -> 6 (reason 0)
Aug 12 10:29:38 titan pppd[5012]: PAP authentication succeeded
Aug 12 10:29:38 titan NetworkManager: <info> (ttyUSB0): device state change: 6 -> 7 (reason 0)
Aug 12 10:29:47 titan pppd[5012]: Could not determine remote IP address: defaulting to 10.64.64.64
Aug 12 10:29:47 titan pppd[5012]: Cannot determine ethernet address for proxy ARP
Aug 12 10:29:47 titan pppd[5012]: local IP address x.x.x.x
Aug 12 10:29:47 titan pppd[5012]: remote IP address 10.64.64.64
Aug 12 10:29:47 titan pppd[5012]: primary DNS address y.y.y.y
Aug 12 10:29:47 titan pppd[5012]: secondary DNS address z.z.z.z
Aug 12 10:29:47 titan NetworkManager: <info> PPP manager(IP Config Get) reply received.
Aug 12 10:29:47 titan NetworkManager: <info> Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Aug 12 10:29:47 titan NetworkManager: <info> Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) started...
Aug 12 10:29:47 titan NetworkManager: <info> Activation (ttyUSB0) Stage 4 of 5 (IP4 Configure Get) complete.

Older (working) Network Manager:

Aug 12 10:32:09 titan NetworkManager: <info> (ttyUSB0): device state change: 5 -> 6 (reason 0)
Aug 12 10:32:09 titan pppd[3449]: PAP authentication succeeded
Aug 12 10:32:09 titan NetworkManager: <info> (ttyUSB0): device state change: 6 -> 7 (reason 0)
Aug 12 10:32:12 titan pppd[3449]: Could not determine remote IP address: defaulting to 10.64.64.64
Aug 12 10:32:12 titan pppd[3449]: Cannot determine ethernet address for proxy ARP
Aug 12 10:32:12 titan pppd[3449]: local IP address x.x.x.x
Aug 12 10:32:12 titan pppd[3449]: remote IP address 10.64.64.64
Aug 12 10:32:12 titan pppd[3449]: primary DNS address y.y.y.y
Aug 12 10:32:12 titan pppd[3449]: secondary DNS address z.z.z.z
Aug 12 10:32:12 titan NetworkManager: <info> PPP manager(IP Config Get) reply received.
Aug 12 10:32:12 titan NetworkManager: <info> Activation (ttyUSB0) Stage 4 of 5 (IP Configure Get) scheduled...
Aug 12 10:32:12 titan NetworkManager: <info> Activation (ttyUSB0) Stage 4 of 5 (IP Configure Get) started...
Aug 12 10:32:12 titan NetworkManager: <info> Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) scheduled...
Aug 12 10:32:12 titan NetworkManager: <info> Activation (ttyUSB0) Stage 4 of 5 (IP Configure Get) complete.
Aug 12 10:32:12 titan NetworkManager: <info> Activation (ttyUSB0) Stage 5 of 5 (IP Configure Commit) started...

[Tony Espy (awe)]

Can you please try updating? We released a new version of network-manager to karmic this morning which fixes numerous 3g issues:

0.8~a~git.20090820t182117.cb60390-0ubuntu3

[Andreas Gustafsson (andreas-gustafsson)]

Still no go...

What do you want me to attach to this bugreport?

[Tony Espy (awe)]

Can you run apport-collect <bug number>?

This will attach the relevant system logs...

[Andreas Gustafsson (andreas-gustafsson)]

Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 9.10
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 172.17.17.0/24 dev wlan0 proto kernel scope link src 172.17.17.102 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 172.17.17.1 dev wlan0 proto static
Package: network-manager 0.8~a~git.20090820t182117.cb60390-0ubuntu2
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=sv_SE.UTF-8
 LANGUAGE=sv_SE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
Uname: Linux 2.6.31-6-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
WpaSupplicantLog:

[Andreas Gustafsson (andreas-gustafsson)]

Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 9.10
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 172.17.17.0/24 dev wlan0 proto kernel scope link src 172.17.17.102 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 172.17.17.1 dev wlan0 proto static
Package: network-manager 0.8~a~git.20090820t182117.cb60390-0ubuntu2
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=sv_SE.UTF-8
 LANGUAGE=sv_SE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
Uname: Linux 2.6.31-6-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
WpaSupplicantLog:

[Pedro Villavicencio (pedro)]

confirming since the reporter provided the information asked in previous comment.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 446146, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Andreas Gustafsson (andreas-gustafsson)]

This is not a duplicate.
My modem works fine under the newer kernel. The problem for me is the network manager.

Running successful now with 2.6.31-16-generic and network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2.

Breaks if I install the latest 0.8 package of nm.

[Andreas Gustafsson (olangu)]

Apperently modem support is lifted out and needs its own package.

Installing modemmanager solves the problem.

Please close bug.

[Thomas Hood (jdthood)]

The modemmanager package is Recommended by network-manager. Should something else be done to help the user to become aware of the need to install that package under the appropriate circumstances? If so then please reopen and explain.