NM can't power off Ericsson F3507g WWAN (but can power it on)

[Jan Simon]

Like in https://bugs.launchpad.net/bugs/756553 described: On a Thinkpad X200 Tablet network-manager can power on the f3507g but is not able to power it off. This is only possible with the hardware flight mode switch.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: network-manager 0.8.9997+git.20110721t045648.36db194-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Jul 26 14:34:28 2011
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
IpRoute:
 default via 10.10.7.254 dev wlan0 proto static
 10.10.0.0/21 dev wlan0 proto kernel scope link src 10.10.4.236 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=C
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to oneiric on 2011-07-26 (0 days ago)

[Jan Simon (jan-simon)]

Still a problem in network-manager 0.9.1.90

[Thomas Hood (jdthood)]

@Jan: Has this bug been fixed in Ubuntu 12.04?

(Note: Ericsson F3507g listed as supported upstream.)

[Jan Simon (jan-simon)]

Still an issue in 12.04, networkmanger 0.9.4

[Marius B. Kotsbak (mariusko)]

Are anyone able to test the patch I posted in the upstream bug report here?: https://bugzilla.gnome.org/show_bug.cgi?id=665877

I just switched out my Ericsson modem.

[Marius B. Kotsbak (mariusko)]

@Daniel Oertwig or anyone else, are you able to test this? Now it is in the MM_05 branch so you should be able to download it here:

http://cgit.freedesktop.org/ModemManager/ModemManager/snapshot/ModemManager-850d78b938e895e3a1628f8ce45a67c7d5cfd2ca.tar.gz

then build it (run "apt-get build-dep modemmanager" first) , stop network-manager, start the built modem-manager and then start network-manager again.

[Daniel Jour (danieloertwig)]

Tested it, but didn't fix the issue. More information tomorrow, as I just wiped out my complete comment (due to my deactivated network connection) that I wrote the past half an hour -,-
for now just dmesg and messages.log Logs.
I hope there is not .. too much information in my messages.log.

[Marius B. Kotsbak (mariusko)]

How do you detect that it is not working? Looking at a status LED, measuring power consumption or looking at killswitches?

I see a lot about killswitches in the log. Are you modifying them? Could you please strip down the logs to the actual modem sessions without wlan etc. Also the output when modemmanager is started with the --debug flag would be useful.

[Daniel Jour (danieloertwig)]

How do I start modemmanager with this flag?
Should I start it manually before starting networkmanager?
I'll write more later, am busy at the moment.

[Marius B. Kotsbak (mariusko)]

Yes, you need to start it manually before NM starts it automatically. And make sure it is the new version you built that you start.

[Daniel Jour (danieloertwig)]

Ok, I did another test. Here are the results.
Test sequence:

* Clean reboot, disabled networkmanager at startup/boot (it was never started)
* sudo modem-manager --debug --timestamp
* Started networkmanager service
* Disabled wlan right after connection was up (could not be done earlier due to ... interface)
* Enabled Mobile Broadband => LED ON, NET INFORMATION DISPLAYED
* Disabled Mobile Broadband => LED OFF, NET INFORMATION STILL DISPLAYED, THOUGH
* /sys/devices/.../wwan_enable = 1
* Enabled Mobile Broadband => LED ON
* Disabled Mobile Broadband => LED OFF
* Connect to mobile broadband link => LED ON, CONNECTION UP AND RUNNING
* Disabling Mobile Broadband -> HAD to enabled it first because the GUI didn't recognize the change => LED OFF, CONNECTION STOPPED
* Stopping networkmanager
* Killed modem-manager (Ctrl-C)

After that, I started networkmanager again.
This worked fine, the mobile broadband connection was displayed but could not
be activated (neither LED nor GUI indicator), see MESSAGES.log line 1062

So I did:
echo 0 | sudo tee /sys/devices/platform/thinkpad_acpi/wwan_enable
echo 1 | sudo tee /sys/devices/platform/thinkpad_acpi/wwan_enable

and then the modem worked fine. I'm sending this via the mobile broadband connection.

So finally:
Disabling seems to work now. I have NO idea why it didn't work yesterday. Will try to reproduce that case.
But the GUI should be updated, of course (I think this is probably another persons job?)

A short note on yesterday's test:

I'm sure that I really used the new modem-manager with the test yesterday. The first time switching the modem off
seemed to work, the led turned off a second or so after disabling mobile broadband. But then, about ten seconds later,
the led turned back on.
So I enabled mobile broadband via applets gui, and disabled it again. This had THEN no effect.

As I noted above, I will try to reproduce that behaviour. But I hope, that I will fail to do so ;)

Unfortunately, I tried to catch modem-managers output via:
sudo modem-manager --debug --timestamp | tee MM.log
As the messages seemed to come via FD 2 (stderr), the log is now empty.
But I noticed the log messages are in MESSAGES.log, too. Is this sufficient?
I copied everything what was left in the terminal buffer into MM.log, but this is not the complete log!

[Marius B. Kotsbak (mariusko)]

Okay, the logs are fine. I see the added CFUN=4 seems to be accepted and works.

What do you mean by net information? And do you use autoconnection? There might be some other bugs related to the enabling applet switch. I recommend turning it on before starting the connection. If autoconnect is on, it is sufficient to just switch it on to start the connection.

And for the case that you had to turn it off and on again, I have experienced something similar with my previous Ericsson module. Turning it off and on using the keyboard switch let me connect again.

I think we can conclude that the patch was successful (given those other observations would be there without the patch too).

[Daniel Jour (danieloertwig)]

Yes, it works, so the patch was successful.

By net information I mean the string displayed directly under the applet's switch. I honestly have no idea why this has been changed for the latest gnome3, but back with the gnome2 applets gui I had there a string displaying net provider, signal strength and net type (UMTS, EDGE, ...)

I guess this information is still accessible via modem-manager (?) but just not displayed anymore.

This information is still displayed after the mobile boadband device has been disabled. And as I assume that there is no possible way to keep the device powered off AND at the same time keep those information updated (because of movement of the laptop, i.e. in a train) I think it might be the best to hide that information once the device is turned off.
But that's rather a gui issue and does not belong to this bug.

Same applies to the problem that the gui switch is not enabled when connecting via a click on a connection (and previously disabled mobile broadband)

Last but not least: No, I do not (and didn't or the test) use autoconnect. This could be a possible way to "solve" the gui problem for now.

[Marius B. Kotsbak (mariusko)]

The menu in the screenshot does not look familiar, but I see signal strength and maybe operator there. I would expect too see GSM/edge/UMTS as well. Please open a new bug report using "ubuntu-bug network-manager" for that.

And for the status, does it help to disconnect before disabling mobile broadband?

[Marius B. Kotsbak (mariusko)]

This is fixed in the current Quantal version. See bug #1043486 ("36ef5fa mbm: use +CFUN=4 for powering down"). Would be nice if it was backported to the LTSes.

[Marius B. Kotsbak (mariusko)]

Related to this, there seems to be a problem with entering power down state without first enabling and disabling modem:

https://bugzilla.gnome.org/show_bug.cgi?id=683681

[Jan Simon (jan-simon)]

I've reopened it, as it is still an issue in Modemmanager 0.6.0.0-0ubuntu4 in quantal.

[Jan Simon (jan-simon)]

syslog:

Oct 7 21:19:25 jfm-tp NetworkManager[1005]: <info> WWAN now disabled by management service
Oct 7 21:19:25 jfm-tp modem-manager[3815]: <info> (ttyACM1) closing serial port...
Oct 7 21:19:25 jfm-tp modem-manager[3815]: <info> (ttyACM1) serial port closed
Oct 7 21:19:25 jfm-tp modem-manager[3815]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> disabling)
Oct 7 21:19:25 jfm-tp modem-manager[3815]: <info> (ttyACM0) closing serial port...
Oct 7 21:19:50 jfm-tp NetworkManager[1005]: <warn> failed to enable/disable modem: (4) Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Oct 7 21:19:55 jfm-tp modem-manager[3815]: <info> (ttyACM0) serial port closed
Oct 7 21:19:55 jfm-tp modem-manager[3815]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabling -> disabled)

LED is still on.

[Marius B. Kotsbak (mariusko)]

That error does not look related. Does it happens every time?

[Jan Simon (jan-simon)]

Yes i've never managed to turn off the card via the network-manager. It the same behaviour like written in my original bug description.

[Aleksander Morgado (aleksander-m)]

Jan: Could you grab MM debug logs?

https://wiki.ubuntu.com/DebuggingModemmanager

[Jan Simon (jan-simon)]

Here are the logs. I switched the device on and then tried to power it off.

[Marius B. Kotsbak (mariusko)]

Checked the source now, and it seems somehow the patch seems not to be included in the Ubuntu package.

In the mean time, you could try this PPA https://launchpad.net/~network-manager/+archive/trunk

[Jan Simon (jan-simon)]

Thanks Marius, the ppa-version (nm 0.9.6.0+git201208141753.5718-0~pkg570~quantal1, mm 0.6.0.0+git201210061703.1176-0~pkg164~quantal1) works for me.

[Mathieu Trudel-Lapierre (cyphermox)]

Should be fixed in Quantal now (with https://launchpad.net/ubuntu/+source/modemmanager/0.6.0.0.really-0ubuntu1).