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! ** Attachment added: "MESSAGES.log" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/816400/+attachment/3256346/+files/MESSAGES.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816400 Title: NM can't power off Ericsson F3507g WWAN (but can power it on) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/816400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
