GNOME Bugzilla – Bug 697781
[0bdb:1926] Ericsson H5321 gw not working
Last modified: 2013-04-15 20:07:21 UTC
Originally reported at: https://bugs.launchpad.net/bugs/1167852 First, I reported bug 1164023 as there was also a crash of modemmanager, but after this crash being fixed I still do not get a connection to mobile broadband. This bug is a regression against 12.10. Booting from a 12.10 live CD I can use the mobile broadband. The modem is built-in (Ericsson Business Mobile Networks BV). I do not get any crashes any more, but no connection. According to syslog, modem-manager is trying something infinitely. I do not know whether really modemmanager or network-manager is the culprit. I have switched to debug logging via sudo python debug-helper.py --mm debug sudo python debug-helper.py --nm debug Then I have captured the syslog via tail -n0 -f /var/log/syslog > /tmp/syslog While capturing, I have first clicked "Enable Mobile Broadband" in the Network Manager menu, near the bottom. After some seconds I got an OSD pop-up that I am registered for GSN or so. Now I clicked on "T-Mobile (Telekom) Default" in the "Mobile Broadband" section. The indicator applet icon of the Network Manager started spinning, telling that it is searched for a network. After some time it stopped spinning without connection established. After that, modem-manager is still active in the syslog. I waited some minutes before stopping to capture. syslog is attached. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Thu Apr 11 12:29:41 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-03-28 (13 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.58 metric 1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.57 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wwan0 gsm disconnected /org/freedesktop/NetworkManager/Devices/5 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /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 enabled
Is this the mbim vs. ncm issue that Bjorn's been talking about on the lists? With a recent kernel the device will be handled by default with MBIM instead of NCM. Unfortunately the kernel simply cannot autodetect which one should handle it, and we dont' yet have MBIM support in ModemManager 0.6. Thus you need to have a modprobe script or something to tell cdc-ncm to use NCM mode instead of MBIM. I'll reproduce part of Bjorns email: ---- I believe the Dell 5560 is a re-branded Ericsson F5321? If this is a new laptop, or you have recently upgraded the wwan firmware, then you may have hit the "NCM/MBIM problem". Do you have this parameter, and is it set to yes?: bjorn@nemi:~$ grep . /sys/module/cdc_ncm/parameters/prefer_mbim Y If so, then the problem may be solved by echo N >/sys/module/cdc_ncm/parameters/prefer_mbim followed by unbinding the modem from cdc_mbim and rebinding it to cdc_ncm. Which should happen automatically if you "unplug" and replug it (I know it's an internal module, but this might still be possible using rfkill). Or just unload the drivers and reload them to test: modprobe -r cdc_mbim modprobe cdc_ncm prefer_mbim=N If this works, then you may want to add a config workaround until MM support for MBIM is ready. Put something like this into a new /etc/modprobe.d/avoid-mbim.conf file: options cdc_ncm prefer_mbim=N (Note that you probably do want to remove this again when the MBIM support is available, because that will enable MM to better manage your modem). ----
Sure it was that one.