[Desktop-packages] [Bug 1949621] Re: libmbim cannot make use of Quectel EM120
Please note the libmbim 1.24 branch is not actively maintained any more in upstream. If you want to keep on using that release, you're fully on your own. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
> The snap "dpr-wwan_1.0-wwan-test_amd64.snap" is provided by Lenovo (not published yet) Is there any estimated date when it will be released? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific
[Desktop-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
And where is the dpr-wwan_1.0-wwan-test_amd64.snap file? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options . For ex., there is a patched 5.11 kernel which is working for:
[Desktop-packages] [Bug 1780606] [NEW] NetworkManager not able to manage WWAN devices in 18.04 server
Public bug reported: Installed a 18.04 server image, and installed NetworkManager. NetworkManager comes with a "/usr/lib/NetworkManager/conf.d/10-globally- managed-devices.conf" file where it speciefies that all devices are by default unmanaged except for types "wifi" and "wwan". Now, the problem is that the filter should apply to "gsm" or "cdma" types, not "wwan". E.g.: [keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma Before the change: $ nmcli d DEVICETYPE STATE CONNECTION wlan0 wifi connected Bumbu eth0 ethernet unmanaged -- cdc-wdm0 gsm unmanaged -- loloopback unmanaged -- After the change: $ nmcli d DEVICETYPE STATE CONNECTION wlan0 wifi connected Bumbu cdc-wdm0 gsm connected cell eth0 ethernet unmanaged -- loloopback unmanaged -- ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1780606 Title: NetworkManager not able to manage WWAN devices in 18.04 server Status in network-manager package in Ubuntu: New Bug description: Installed a 18.04 server image, and installed NetworkManager. NetworkManager comes with a "/usr/lib/NetworkManager/conf.d/10 -globally-managed-devices.conf" file where it speciefies that all devices are by default unmanaged except for types "wifi" and "wwan". Now, the problem is that the filter should apply to "gsm" or "cdma" types, not "wwan". E.g.: [keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma Before the change: $ nmcli d DEVICETYPE STATE CONNECTION wlan0 wifi connected Bumbu eth0 ethernet unmanaged -- cdc-wdm0 gsm unmanaged -- loloopback unmanaged -- After the change: $ nmcli d DEVICETYPE STATE CONNECTION wlan0 wifi connected Bumbu cdc-wdm0 gsm connected cell eth0 ethernet unmanaged -- loloopback unmanaged -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1780606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 540003]
For reference, I'm testing with a F3507g, and it seems that this modem does receive and store the string properly: AT*EIAAUW=2,1,"p...@a1plus.at","ppp" OK AT*EIAAUR=2,1 *EIAAUR: 2,1,"p...@a1plus.at","ppp",00111,0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/540003 Title: network-manager doesn't work with dell 5530 hsdpa mobile broadband Status in ModemManager: Unknown Status in network-manager package in Ubuntu: Invalid Bug description: Network manager doesn't connect to mobile broadband using the Dell 5530 hsdpa mini-pci card. Shows up in network-manager as having a gsm device, but even with the correct settings it wont connect. I did manage to get it working by installing gnome-ppp and manually configuring AT commands the card requires to active the radio and set the APN. I can get connected this way, but it is not as nice as being able to use network-manager. It also required my user to be added to the dialout and dip groups I think. The 5530 card requires these AT commands to activate radio and set the APN and so on: AT+CFUN=1 ATQ0 V1 E1 S0=0 +FCLASS=0 AT+CGDCONT=1,"IP","VirginBroadband" Obviously replacing the VirginBroadband with the appropriate APN for the connection. I don't know if its worthwhile but maybe if the network-manager tool had the ability to customise AT init strings under and advanced button for mobile broadband or dial-up modems? Also the card also supports GPS which can be enabled with (for example): AT+CFUN=1 AT+E2GPSCTL=1,5,1 AT+E2GPSNPD lsb_release -rd : Description: Ubuntu lucid (development branch) Release: 10.04 timw@timw-laptop:~$ apt-cache policy network-manager network-manager: Installed: 0.8-0ubuntu2 Candidate: 0.8-0ubuntu2 Version table: *** 0.8-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/540003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1326954]
(In reply to Aleksander Morgado from comment #17) > (In reply to russianneuromancer from comment #16) > > And in case it could help someone, this workaround systemd unit helps me. > > With this unit connection could be established after suspend. > > Did you compile ModemManager with 'systemd' suspend/resume support? Ideally, > MM should detect the suspend/resume events and reprobe the devices from > scratch. Nevermind, I see the suspend/resume is in place in MM so the bug is still applicable there; I'll analyze the logs and let you know what I find. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... <<<<<< RAW: <<<<<< length = 16 <<<<<< data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... <<<<<< Header: <<<<<< length = 16 <<<<<< type= open (0x0001) <<<<<< transaction = 1 <<<<<< Contents: <<<<<< max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >>>>>> RAW: >>>>>> length = 16 >>>>>> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... <<<<<< RAW: <<<<<< length = 12 <<<<<< data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... <<<<<< Header: <<<<<< length = 12 <<<<<< type= close (0x0002) <<<<<< transaction = 2 [/dev/cdc-wdm0] Received message... >>>>>> RAW: >>>>>> length = 16 >>>>>> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [140199
[Desktop-packages] [Bug 1326954]
(In reply to russianneuromancer from comment #20) > Hi > > Any news? Yes, see: https://lists.freedesktop.org/archives/modemmanager- devel/2017-August/005668.html Could you apply the patch in a custom build and retry, to see if it fixes your issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' |
[Desktop-packages] [Bug 1326954]
If you want to apply it on a 1.6.x version, use this patch instead: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?h=mm-1-6=196b8d619ad16d625ab0cc520854c2a044c0e4eb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0
[Desktop-packages] [Bug 1326954]
(In reply to russianneuromancer from comment #16) > And in case it could help someone, this workaround systemd unit helps me. > With this unit connection could be established after suspend. Did you compile ModemManager with 'systemd' suspend/resume support? Ideally, MM should detect the suspend/resume events and reprobe the devices from scratch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6'
[Desktop-packages] [Bug 1326954]
(In reply to Adrian Perez de Castro from comment #10) > I also have this issue, with a Fujitsu S936 laptop which includes an EM7305. > After adding the udev rules in the post at 0xf8.org (modifying them to fit > use the USB identifier that shows in my laptop, 1199:9041), the “mbim-proxy” > program seems to hang in some kind of loop, chewing 80% of CPU time according > to “top”. Here are the details of my configuration: > > - Arch Linux > - ModemManager 1.6.4 > - NetworkManager 1.4.4 > - libmbim 1.14.0 > - Kernel 4.9.5 > > I will be posting the output from “lsusb -v -d 1199:9041” as an attachment. I believe you misread what the rules in the blogpost are doing :) I think the rules try to force the device into QMI mode, instead of the MBIM mode that would be picked up by default. This was a better choice for the Dell modem at that time because there wasn't support for running QMI commands over MBIM, and the Dell modem really required the FCC Auth command; but that is no longer the case, as MM already handles QMI over MBIM automatically as well as the FCC auth command for the Dell device. Anyway, in your case it seems the rules didn't work as expected because you're still in MBIM mode, which is the one I would anyway suggest. I believe you can remove all the udev rules, as the kernel (or usb_modeswitch, it depends) should choose the MBIM configuration as preferred automatically. That said, could you gather MM and mbim-proxy debug logs? I'd like to check whether the issue is exactly the same one: $> sudo systemctl stop ModemManager $> sudo killall -9 mbim-proxy $> sudo /usr/libexec/mbim-proxy --verbose > /tmp/mbim-proxy.log 2>&1 & $> sudo /usr/sbin/ModemManager --debug > /tmp/mm.log 2>&1 & (and retry reproducing the issue) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Unknown Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0)
[Desktop-packages] [Bug 1117944] Re: [SRU] intltool confused by separate build-dir
@monsta AFAIK, this bug report is the "upstream" bug report as well. As long as you're not the upstream intltool maintainer, please don't set it as wontfix. Even if it does seem unmaintained... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to intltool in Ubuntu. https://bugs.launchpad.net/bugs/1117944 Title: [SRU] intltool confused by separate build-dir Status in intltool: Confirmed Status in intltool package in Ubuntu: Fix Committed Status in intltool source package in Xenial: Fix Committed Status in intltool source package in Artful: Fix Committed Bug description: [Impact] An old bug in intltool breaks out-of-tree builds, including "make distcheck", in a lot of intltool-using projects when automake version is 1.15 or newer. The fix for this issue (by Aleksander Morgado) is provided in the debdiffs attached to the report. It's a long-standing bug which is present in all current Ubuntu releases, starting from Xenial. Would be really nice to get it finally fixed. The developers have to patch their intltool locally just to have a working distcheck target (which is used when making release tarballs). [Test Case] Try making release tarball for some upstream package. For example, it can be mate-desktop, a base project for various MATE components. $ sudo apt-get build-dep mate-desktop $ git clone https://github.com/mate-desktop/mate-desktop $ cd mate-desktop $ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict $ make -j5 && make dist -j5 && make distcheck -j5 This will build the project, make release tarball and check it by unpacking it into a new directory and building (again) in it. The last step will fail: --- srcdir=../../../po /usr/bin/intltool-update -m The following files contain translations and are currently not in use. Please consider adding these to the POTFILES.in file, located in the po/ directory. sub/mate-about/mate-about.desktop.in sub/tools/mate-color-select.desktop.in If some of these files are left out on purpose then please add them to POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list of left out files has been written in the current directory. Please report to https://github.com/mate-desktop/mate-desktop/ if [ -r missing -o -r notexist ]; then \ exit 1; \ fi Makefile:179: recipe for target 'check' failed --- The out-of-tree build breaks here. [Regression Potential] None. This is a fix for a broken feature, it doesn't affects other ones. Also the fix had been tested by MATE developers in various distros, including Debian, Ubuntu and Fedora. [Original Description] systemd uses 'intltool-update -m' from intltoolize in its 'make check'. $(top_srcdir)/po/POTFILES.skip contains the name of a generated file (src/core/org.freedesktop.systemd1.policy.in), which will be generated as $(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If $(builddir)==$(srcdir) than everything works fine. When they are different, there's no way to instruct intltool-update to skip the file. Since the name of the build directory is not known and can be arbitrary, there should be a way to instruct intltool-update to ignore files relative to the $(top_builddir), or something like that. One option would be to turn the file list into a list of globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in our case). To manage notifications about this bug go to: https://bugs.launchpad.net/intltool/+bug/1117944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1117944] Re: intltool confused by separate build-dir
Yeah I know, it's just not my problem any more. Everyone should migrate, gettext is at least maintained. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to intltool in Ubuntu. https://bugs.launchpad.net/bugs/1117944 Title: intltool confused by separate build-dir Status in intltool: Confirmed Status in intltool package in Ubuntu: Confirmed Bug description: systemd uses 'intltool-update -m' from intltoolize in its 'make check'. $(top_srcdir)/po/POTFILES.skip contains the name of a generated file (src/core/org.freedesktop.systemd1.policy.in), which will be generated as $(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If $(builddir)==$(srcdir) than everything works fine. When they are different, there's no way to instruct intltool-update to skip the file. Since the name of the build directory is not known and can be arbitrary, there should be a way to instruct intltool-update to ignore files relative to the $(top_builddir), or something like that. One option would be to turn the file list into a list of globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in our case). To manage notifications about this bug go to: https://bugs.launchpad.net/intltool/+bug/1117944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1117944] Re: intltool confused by separate build-dir
intltool is dead, long live gettext-only :) https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=984625165e09f02b4d6b8389092d5055fdbb0f03 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to intltool in Ubuntu. https://bugs.launchpad.net/bugs/1117944 Title: intltool confused by separate build-dir Status in intltool: Confirmed Status in intltool package in Ubuntu: Confirmed Bug description: systemd uses 'intltool-update -m' from intltoolize in its 'make check'. $(top_srcdir)/po/POTFILES.skip contains the name of a generated file (src/core/org.freedesktop.systemd1.policy.in), which will be generated as $(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If $(builddir)==$(srcdir) than everything works fine. When they are different, there's no way to instruct intltool-update to skip the file. Since the name of the build directory is not known and can be arbitrary, there should be a way to instruct intltool-update to ignore files relative to the $(top_builddir), or something like that. One option would be to turn the file list into a list of globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in our case). To manage notifications about this bug go to: https://bugs.launchpad.net/intltool/+bug/1117944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1117944] Re: intltool confused by separate build-dir
"WTF broke my distcheck!", then apply it to N projects using intltool, sum the amount of hours wasted by everyone applying workarounds in their own projects... I have to admit this is very very sad. A bug like this one, affecting every project using intltool, with one suggested patch even, still open 2 years later. Of course this is no longer critical because *every* project using intltool ended up patching their own POTFILES.skip... how very sad. Let's see each other again here when automake updates again the default builddir during dist. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to intltool in Ubuntu. https://bugs.launchpad.net/bugs/1117944 Title: intltool confused by separate build-dir Status in intltool: Confirmed Status in intltool package in Ubuntu: Confirmed Bug description: systemd uses 'intltool-update -m' from intltoolize in its 'make check'. $(top_srcdir)/po/POTFILES.skip contains the name of a generated file (src/core/org.freedesktop.systemd1.policy.in), which will be generated as $(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If $(builddir)==$(srcdir) than everything works fine. When they are different, there's no way to instruct intltool-update to skip the file. Since the name of the build directory is not known and can be arbitrary, there should be a way to instruct intltool-update to ignore files relative to the $(top_builddir), or something like that. One option would be to turn the file list into a list of globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in our case). To manage notifications about this bug go to: https://bugs.launchpad.net/intltool/+bug/1117944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1117944] Re: intltool confused by separate build-dir
For reference, what projects are doing: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=1ae6a7be8abab4b13520679f42c6cc8e2fb57d05 https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/po/POTFILES.skip?id=66c3b673e32b7d055349a2a96ca2c2dfbbfc03ba https://git.gnome.org/browse/gnome-control- center/commit/po/POTFILES.skip?id=5e0db6aaeb0e88161a0bb76fac5293c4dec22ed1 https://cgit.freedesktop.org/geoclue/commit/po/POTFILES.skip?id=ece2a872c1b944cf24bd631d907c3b7cfcb484a9 ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to intltool in Ubuntu. https://bugs.launchpad.net/bugs/1117944 Title: intltool confused by separate build-dir Status in intltool: New Status in intltool package in Ubuntu: New Bug description: systemd uses 'intltool-update -m' from intltoolize in its 'make check'. $(top_srcdir)/po/POTFILES.skip contains the name of a generated file (src/core/org.freedesktop.systemd1.policy.in), which will be generated as $(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If $(builddir)==$(srcdir) than everything works fine. When they are different, there's no way to instruct intltool-update to skip the file. Since the name of the build directory is not known and can be arbitrary, there should be a way to instruct intltool-update to ignore files relative to the $(top_builddir), or something like that. One option would be to turn the file list into a list of globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in our case). To manage notifications about this bug go to: https://bugs.launchpad.net/intltool/+bug/1117944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1441095]
Comment on attachment 118426 Increase the retry interval to 5 seconds. This breaks the timeout value given by the user. In open_message_ready() we'll do a ctx->timeout--; if we got a timeout error, so that we can retry. Instead of ctx->timeout--; there should be a ctx->timeout-=5 there, and along with that: make timeout a gint (not guint) and also don't do the (ctx->timeout) check, and instead do (ctx->timeout > 0) Also, better #define RETRY_TIMEOUT_SECS 5 and use the symbol everywhere. Could you update the patch and retest? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1441095 Title: novatel: improve probing for Dell branded modems Status in ModemManager: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: Confirmed Status in libmbim package in Ubuntu: In Progress Status in modemmanager package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in libmbim source package in Trusty: Confirmed Status in modemmanager source package in Trusty: Confirmed Status in network-manager source package in Trusty: Confirmed Bug description: Dell rebrands modems from different vendors, including Novatel, Sierra and Ericsson. Until now we defaulted to the Novatel plugin when a Dell device was found, but then we're breaking newer MBIM Sierra Dell- branded modems, as we don't have MBIM support in the Novatel plugin. So, we should try to improve the probing in the Novatel, Sierra and MBM plugins, so that they probe also Dell devices, and we'll then try to match via AT-probing which plugin should be handling the Dell device. https://bugs.freedesktop.org/show_bug.cgi?id=86713 Could we backport this patch into trusty? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1441095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1441095]
Merged the patch to mbim-1-12 and git master, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1441095 Title: novatel: improve probing for Dell branded modems Status in ModemManager: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: Confirmed Status in libmbim package in Ubuntu: In Progress Status in modemmanager package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in libmbim source package in Trusty: Confirmed Status in modemmanager source package in Trusty: Confirmed Status in network-manager source package in Trusty: Confirmed Bug description: Dell rebrands modems from different vendors, including Novatel, Sierra and Ericsson. Until now we defaulted to the Novatel plugin when a Dell device was found, but then we're breaking newer MBIM Sierra Dell- branded modems, as we don't have MBIM support in the Novatel plugin. So, we should try to improve the probing in the Novatel, Sierra and MBM plugins, so that they probe also Dell devices, and we'll then try to match via AT-probing which plugin should be handling the Dell device. https://bugs.freedesktop.org/show_bug.cgi?id=86713 Could we backport this patch into trusty? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1441095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1377577] Re: ModemManager Still connects to UMTS when set to GPRS/EDGE only..
Since ModemManager 1.0, allowed/preferred modes aren't retrieved from NetworkManager connection settings; instead explicit calls in the MM API are required: https://sigquit.wordpress.com/2013/06/03/changing-modes-and- capabilities-in-modemmanager/ ** Changed in: modemmanager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1377577 Title: ModemManager Still connects to UMTS when set to GPRS/EDGE only.. Status in modemmanager package in Ubuntu: Invalid Bug description: [connection] id=Connection 1 uuid=*** type=gsm timestamp=1411919833 [ppp] lcp-echo-failure=5 lcp-echo-interval=30 [ipv4] method=auto dns=8.8.8.8;8.8.4.4; ignore-auto-dns=true [serial] baud=115200 [gsm] number=*99# apn=aircelgrps network-type=1 That is my NetworkManager System-connection config file. But it still Connects to UTMS. network-type=1 (GPRS/EDGE only). Then whats the problem NetworkManager 0.9.8.8-0ubuntu7 ModemManager 1.0.0-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1377577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473246] Re: MediaTek Preloader on a mobile device triggers cdc_acm kernel module usage by ModemManager
I'm assuming those ttys are not to be treated as modem ttys; so long story short, you'll need to blacklist them for now in MM udev rules... I fixed this already in git master and the mm-1-4 branch for this specific MediaTek device, so will be available in the next releases: http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=0e7fc1dff9b3b8f72f6537f7f2b68e5c94a4c751 If you know of more non-modem devices to blacklist, please report bugs to the ModemManager bugzilla: https://bugs.freedesktop.org/enter_bug.cgi?product=ModemManager And yes, the blacklist is far from the best solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1473246 Title: MediaTek Preloader on a mobile device triggers cdc_acm kernel module usage by ModemManager Status in modemmanager package in Ubuntu: Confirmed Bug description: This is an interesting bug that is triggered under some circumstances if one of the official, MediaTek-SoC-based Ubuntu phones is connected to a Linux host via USB. Tested host: Ubuntu 15.04 Desktop, kernel 3.19.0-21-generic, package linux-image-generic 3.19.0.22.21 amd64, package modemmanager 1.4.0-1 Tested phones: Meizu MX4 (arale) and bq Aquaris E4.5 (krillin), image version irrelevant because the Preloader comes with all devices and cannot be changed How to reproduce, possibility 1: 1. Disconnect the USB connection, if necessary. 2. Turn off the phone. 3. Connect the phone via USB. It will take a bit and then turn on, displaying the charge animation. How to reproduce, possibility 2: 1. Reboot the phone while it is still attached to the host. The kernel ringbuffer will contain the following log messages (example for krillin): [288774.244158] usb 1-1: new high-speed USB device number 22 using xhci_hcd [288774.373589] usb 1-1: New USB device found, idVendor=0e8d, idProduct=2000 [288774.373593] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [288774.373594] usb 1-1: Product: MT65xx Preloader [288774.373596] usb 1-1: Manufacturer: MediaTek [288774.435247] cdc_acm 1-1:1.1: ttyACM26: USB ACM device [288774.874607] usb 1-1: USB disconnect, device number 22 [288774.874755] cdc_acm 1-1:1.1: failed to set dtr/rts And syslog will contain the following log messages: Jul 10 00:58:07 fire ModemManager[1103]: info (tty/ttyACM27): released by modem /sys/devices/pci:00/:00:14.0/usb1/1-1 Jul 10 00:58:10 fire ModemManager[1103]: warn (Plugin Manager) (Iridium) [ttyACM27] error when checking support: '(Iridium) Missing port probe for port (tty/ttyACM27)' Jul 10 00:58:10 fire ModemManager[1103]: warn (Plugin Manager) (Cinterion) [ttyACM27] error when checking support: '(Cinterion) Missing port probe for port (tty/ttyACM27)' Jul 10 00:58:10 fire ModemManager[1103]: warn (Plugin Manager) (Nokia) [ttyACM27] error when checking support: '(Nokia) Missing port probe for port (tty/ttyACM27)' Jul 10 00:58:10 fire ModemManager[1103]: warn (Plugin Manager) (Generic) [ttyACM27] error when checking support: '(Generic) Missing port probe for port (tty/ttyACM27)' Jul 10 00:58:10 fire ModemManager[1103]: warn Couldn't find support for device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any plugin The allocated ttyACMx device is never freed, and after a couple of days developing on the phone (with lots of phone restarts) I've noticed that my machine has accumulated an usage count of 58: $ lsmod | grep cdc_acm cdc_acm36864 58 lsof show that ModemManager still holds the devices: # sudo lsof | grep ACM ModemMana 9214 root9u CHR 166,1 0t07599355 /dev/ttyACM1 (deleted) ModemMana 9214 root 10u CHR 166,0 0t07596974 /dev/ttyACM0 (deleted) ... Restarting ModemManager immediately reduces the usage count to 0 again and frees all devices. Why does this happen? Luckily I've read the MediaTek Preloader source code. The Preloader is the first-stage bootloader on MediaTek SoCs and exposes a proprietary USB interface that can be used for debugging purposes and to download firmware to the device. The implementation of this interface is rudimentary and emulates a CDC ACM serial port, which probably doesn't fully conform to the standard and also just falls from the bus after a short amount of time if the host doesn't initiate the proprietary protocol. So I think the kernel and ModemManager immediately try to use the emulated device when it becomes available, but because the implementation in the Preloader is incomplete some bug (timeout?) is triggered and ModemManager never closes the device. Sadly I don't have the expertise to decide if this is a bug in ModemManager or the kernel or both, so I file it with
[Desktop-packages] [Bug 1404068]
Marius, could you ask the original reporter about the concerns Lars had? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch-data in Ubuntu. https://bugs.launchpad.net/bugs/1404068 Title: No internet connection with Huawei E3272 4G modem Status in ModemManager (with NetworkManager support): Incomplete Status in modemmanager package in Ubuntu: Incomplete Status in usb-modeswitch-data package in Ubuntu: Invalid Status in usb-modeswitch-data package in Debian: Fix Released Bug description: There is no internet connection. My mobile broadband LTE modem is Huawei E3272. Attached a syslog. Ubuntu 14.10 modemmanager 1.2.0-1 This might contain useful information: http://askubuntu.com/questions/525965/huawei-e3272-ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1404068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1404068]
Also, may be not modeswitched properly? See: http://askubuntu.com/questions/525965/huawei-e3272-ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch-data in Ubuntu. https://bugs.launchpad.net/bugs/1404068 Title: No internet connection with Huawei E3272 4G modem Status in ModemManager (with NetworkManager support): Incomplete Status in modemmanager package in Ubuntu: Incomplete Status in usb-modeswitch-data package in Ubuntu: Invalid Status in usb-modeswitch-data package in Debian: Fix Released Bug description: There is no internet connection. My mobile broadband LTE modem is Huawei E3272. Attached a syslog. Ubuntu 14.10 modemmanager 1.2.0-1 This might contain useful information: http://askubuntu.com/questions/525965/huawei-e3272-ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1404068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1057834]
Merged branch to git master. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1057834 Title: Haier CE81B is not detected on 12.04 Status in ModemManager (with NetworkManager support): Fix Released Status in modemmanager package in Ubuntu: Triaged Bug description: I have reported this bug under https://bugzilla.gnome.org/show_bug.cgi?id=685011 However, I'm not sure to report only to gnome people. I hope this problem will be fixed on upcoming 12.10. Problem: Modem Haier CE81B EVDO is not working. ModemManager failed to scan the right TTYUSB. Solution: 1. Add udev blacklist for modem manager rule (attached) 2. Type command: sudo modprobe usbserial vendor=0x201e product=0x10f8 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1057834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1057834]
(In reply to Airlangga Cahya Utama from comment #9) Hello Aleksander, Thank you for your patch. I'm a bit busy atm. I'll try to look out for fedora source build this weekend. When does the merge window happen? There's no merge window; as soon as you test it, if it works OK, I'll merge :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1057834 Title: Haier CE81B is not detected on 12.04 Status in ModemManager (with NetworkManager support): In Progress Status in “modemmanager” package in Ubuntu: Triaged Bug description: I have reported this bug under https://bugzilla.gnome.org/show_bug.cgi?id=685011 However, I'm not sure to report only to gnome people. I hope this problem will be fixed on upcoming 12.10. Problem: Modem Haier CE81B EVDO is not working. ModemManager failed to scan the right TTYUSB. Solution: 1. Add udev blacklist for modem manager rule (attached) 2. Type command: sudo modprobe usbserial vendor=0x201e product=0x10f8 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1057834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1057834]
(In reply to Dan Williams from comment #7) aleksander/haier-plugin looks good to me. I tried to ping the original reporter to see if he can test the patch; it's pretty much very low risk I would say anyway, so if we don't get tests back I'll just merge it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1057834 Title: Haier CE81B is not detected on 12.04 Status in ModemManager (with NetworkManager support): In Progress Status in “modemmanager” package in Ubuntu: Triaged Bug description: I have reported this bug under https://bugzilla.gnome.org/show_bug.cgi?id=685011 However, I'm not sure to report only to gnome people. I hope this problem will be fixed on upcoming 12.10. Problem: Modem Haier CE81B EVDO is not working. ModemManager failed to scan the right TTYUSB. Solution: 1. Add udev blacklist for modem manager rule (attached) 2. Type command: sudo modprobe usbserial vendor=0x201e product=0x10f8 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1057834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 977761]
Superb! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue in Ubuntu. https://bugs.launchpad.net/bugs/977761 Title: Add support for using QMI protocol Status in GNOME Control Center: Fix Released Status in GNOME Shell: Fix Released Status in KDE Network - network-related apps: Unknown Status in QMI modem protocol helper library: Fix Released Status in ModemManager (with NetworkManager support): Fix Released Status in NetworkManager: Fix Released Status in Network Manager GNOME Applet: Fix Released Status in “geoclue” package in Ubuntu: New Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-shell” package in Ubuntu: Confirmed Status in “libqmi” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “modemmanager” package in Ubuntu: Triaged Status in “network-manager” package in Ubuntu: Confirmed Status in “network-manager-applet” package in Ubuntu: Confirmed Status in “networkmanagement” package in Ubuntu: New Status in “wader” package in Ubuntu: New Status in “libqmi” package in Debian: Fix Released Bug description: USB modeswitching works ok, and the network operator appears in the NM menu, but it fails to connect. Nm-applet needs to be updated upstream. See the same change for Gnome shell: https://bugzilla.gnome.org/show_bug.cgi?id=687359 We also need libqmi packaged, see bug #1075801. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: modemmanager 0.5.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Tue Apr 10 08:48:55 2012 EcryptfsInUse: Yes SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 DistroRelease: Ubuntu 12.04 EcryptfsInUse: Yes Package: modemmanager 0.5.2.0-0ubuntu2 [modified: lib/udev/rules.d/77-mm-zte-port-types.rules] PackageArchitecture: i386 ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm PATH=(custom, user) LANG=nb_NO.UTF-8 SHELL=/bin/bash Tags: precise precise Uname: Linux 3.4.0-030400rc4-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm dialout lpadmin sambashare sudo PPA for testing/development: https://launchpad.net/~mariusko/+archive /network-manager-snapshots To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/977761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1232329] Re: modem-manager crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1099766 *** https://bugs.launchpad.net/bugs/1099766 So, yeah, just make this bug a duplicate of a private bug which cannot be looked at; and while doing the duplication, make sure the attachments of this bug get also removed so that no one can look at them... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1232329 Title: modem-manager crashed with SIGABRT in g_assertion_message() Status in “modemmanager” package in Ubuntu: New Bug description: Plugged in Serria 3G modem and App crashed - although it did connect successfully ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: modemmanager 0.6.0.0.really-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Sat Sep 28 13:07:17 2013 ExecutablePath: /usr/sbin/modem-manager InstallationDate: Installed on 2013-03-22 (189 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130319) MarkForUpload: True ProcCmdline: /usr/sbin/modem-manager ProcEnviron: PATH=(custom, no user) TERM=linux Signal: 6 SourcePackage: modemmanager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () mm_plugin_base_supports_task_complete () Title: modem-manager crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to saucy on 2013-08-28 (30 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1232329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1231858] Re: modem-manager state doesn't match hardware state after suspend (not able to connect)
In ModemManager 1.x, the current power state of the modem is not assumed when the modem is enabled; i.e. we always re-check current power status before trying to power-up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1231858 Title: modem-manager state doesn't match hardware state after suspend (not able to connect) Status in “modemmanager” package in Ubuntu: New Bug description: After suspend/resume cycle USB 3G modem is in disconnected state. Modem-manager reports device state just changing between disconnecting and connected: Sep 27 11:17:02 rantapallo modem-manager[1198]: info Modem /org/freedesktop/ModemManager/Modems/8: state changed (connected - disconnecting) Sep 27 11:17:02 rantapallo modem-manager[1198]: info Modem /org/freedesktop/ModemManager/Modems/8: state changed (disconnecting - connected) But I can make modem-manager to reset the complete state just by killing it. Sep 27 11:17:25 rantapallo modem-manager[1198]: info Caught signal 15, shutting down... Sep 27 11:17:25 rantapallo modem-manager[1198]: info Modem /org/freedesktop/ModemManager/Modems/8: state changed (connected - disconnecting) Sep 27 11:17:25 rantapallo modem-manager[1198]: info Modem /org/freedesktop/ModemManager/Modems/8: state changed (disconnecting - connected) Sep 27 11:17:25 rantapallo modem-manager[1198]: disable_disconnect_done: (/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2): error disconnecting the modem while disabling: (5) The serial port is not open. Sep 27 11:17:25 rantapallo modem-manager[1198]: (mm-generic-gsm.c:2285):disable: runtime check failed: (priv-cid == -1) Sep 27 11:17:25 rantapallo modem-manager[1198]: info Modem /org/freedesktop/ModemManager/Modems/8: state changed (connected - disabling) Sep 27 11:17:25 rantapallo NetworkManager[1270]: info WWAN now disabled by management service Sep 27 11:17:25 rantapallo modem-manager[1198]: info (ttyUSB2) closing serial port... Sep 27 11:17:25 rantapallo modem-manager[1198]: info (ttyUSB2) serial port closed Sep 27 11:17:25 rantapallo modem-manager[1198]: info Modem /org/freedesktop/ModemManager/Modems/8: state changed (disabling - disabled) Sep 27 11:17:25 rantapallo NetworkManager[1270]: info (ttyUSB0): device state change: disconnected - unmanaged (reason 'removed') [30 10 36] Sep 27 11:17:25 rantapallo NetworkManager[1270]: info (ttyUSB0): cleaning up... Sep 27 11:17:25 rantapallo NetworkManager[1270]: info (ttyUSB0): taking down device. Sep 27 11:17:25 rantapallo NetworkManager[1270]: nm_system_iface_set_up: assertion `ifindex 0' failed Sep 27 11:17:25 rantapallo NetworkManager[1270]: info the modem manager disappeared Sep 27 11:17:25 rantapallo dbus[729]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) Sep 27 11:17:25 rantapallo modem-manager[8154]: info ModemManager (version 0.6.0.0) starting... Sep 27 11:17:25 rantapallo modem-manager[8156]: info ModemManager (version 0.6.0.0) starting... Sep 27 11:17:25 rantapallo dbus[729]: [system] Successfully activated service 'org.freedesktop.ModemManager' Sep 27 11:17:25 rantapallo NetworkManager[1270]: info modem-manager is now available *** plugin loading *** *** Serial port opening spam *** Sep 27 11:17:54 rantapallo modem-manager[8154]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled - enabling) Sep 27 11:17:55 rantapallo modem-manager[8154]: info (ttyUSB2): using PDU mode for SMS Sep 27 11:17:55 rantapallo modem-manager[8154]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling - enabled) Sep 27 11:17:55 rantapallo NetworkManager[1270]: info WWAN now enabled by management service Sep 27 11:17:55 rantapallo modem-manager[8154]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabled - registered) Sep 27 11:17:55 rantapallo modem-manager[8154]: info (ttyUSB0) opening serial port... Sep 27 11:17:55 rantapallo modem-manager[8154]: warn (ttyUSB0): port attributes not fully set Sep 27 11:17:55 rantapallo modem-manager[8154]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered - connecting) Sep 27 11:17:55 rantapallo modem-manager[8154]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting - connected) To me it seems that modem-manager would just need to know about suspend/resume and how to close and reopen with completely clean state the modem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: modemmanager 0.6.0.0.really-0ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Fri Sep 27 11:19:21 2013 InstallationDate: Installed on 2011-11-02 (695 days ago)
[Desktop-packages] [Bug 1229748] Re: modem manager probing causes bluegiga BLE112B to reset
Done in git master; http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=0dd93549a175f05cd5290ca8b3a3fd78e59863b5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1229748 Title: modem manager probing causes bluegiga BLE112B to reset Status in “modemmanager” package in Ubuntu: New Bug description: putting this device in the machine shows this in syslog Sep 24 14:57:33 alanlaptop kernel: [227323.226530] cdc_acm 2-1.5:1.0: ttyACM0: USB ACM device Sep 24 14:57:33 alanlaptop modem-manager[5505]: info (ttyACM0) opening serial port... Sep 24 14:57:34 alanlaptop modem-manager[5505]: info (ttyACM0) closing serial port... Sep 24 14:57:34 alanlaptop modem-manager[5505]: info (ttyACM0) serial port closed Sep 24 14:57:34 alanlaptop kernel: [227324.245624] cdc_acm 2-1.5:1.0: ttyACM0: USB ACM device Sep 24 14:57:34 alanlaptop modem-manager[5505]: info (ttyACM0) opening serial port... Sep 24 14:57:35 alanlaptop modem-manager[5505]: info (ttyACM0) closing serial port... Sep 24 14:57:35 alanlaptop modem-manager[5505]: info (ttyACM0) serial port closed Sep 24 14:57:35 alanlaptop kernel: [227325.273609] cdc_acm 2-1.5:1.0: ttyACM0: USB ACM device Sep 24 14:57:35 alanlaptop modem-manager[5505]: info (ttyACM0) opening serial port... Sep 24 14:57:36 alanlaptop modem-manager[5505]: info (ttyACM0) closing serial port... Sep 24 14:57:36 alanlaptop modem-manager[5505]: info (ttyACM0) serial port closed which appears to be repeated re-probing and resetting of the device lsusb shows the following vendor/product id Bus 002 Device 023: ID 2458:0001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1229748/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102343] Re: Missing MBIM (Mobile Broadband Interface Model) support
MBIM support is now merged into ModemManager git master, and a preliminary version of libmbim is already available: http://www.freedesktop.org/software/libmbim/libmbim-0.0.1.tar.xz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch-data in Ubuntu. https://bugs.launchpad.net/bugs/1102343 Title: Missing MBIM (Mobile Broadband Interface Model) support Status in The Linux Kernel: In Progress Status in ModemManager (with NetworkManager support): In Progress Status in Usb Modeswitch: New Status in “linux” package in Ubuntu: Triaged Status in “modemmanager” package in Ubuntu: New Status in “usb-modeswitch” package in Ubuntu: New Status in “usb-modeswitch-data” package in Ubuntu: New Bug description: The USB Communications Device Class Mobile Broadband Interface Model (MBIM) is the USB-IFs alternative to the current chipset/vendor specific solutions to Mobile Broadband device management. The specification, including the management protocol description, can be downloaded from http://www.usb.org/developers/devclass_docs#approved A new project similar to libqmi needs to be created: https://bugs.freedesktop.org/show_bug.cgi?id=59161 and is now in progress: https://gitorious.org/lanedo/libmbim and a modemmanager branch 'aleksander/mbim'. See also bug #1169117. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1102343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167852] Re: [0bdb:1926] REGRESSION: Ericsson H5321 gw not working
Marius: out of curiosity, did you try MM git master with this modem? Did it work ok? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1167852 Title: [0bdb:1926] REGRESSION: Ericsson H5321 gw not working Status in NetworkManager: New Status in “modemmanager” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Confirmed Bug description: 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-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1167852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164023] Re: modem-manager crashed with SIGSEGV in g_slice_alloc() - REGRESSION: No internet access via mobile broadband
Ok, so the MM_06 branch in git is actually free of your problem. Your issue is fixed (99% chance :)) in the following commit: http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?h=MM_06id=5d854a32cf2d04cbdb3d16f019d277caaba69ab4 So, either compile directly that branch, or ask Ubuntu packagers to also include that commit in the build. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1164023 Title: modem-manager crashed with SIGSEGV in g_slice_alloc() - REGRESSION: No internet access via mobile broadband Status in ModemManager (with NetworkManager support): New Status in “modemmanager” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: Happened again, after some attempts to connect via mobile broadband. With 12.10 access via mobile broadband works with this machine. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: modemmanager 0.6.0.0.really-0ubuntu4 Uname: Linux 3.9.0-030900rc5-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CrashCounter: 1 Date: Wed Apr 3 18:37:32 2013 ExecutablePath: /usr/sbin/modem-manager InstallationDate: Installed on 2013-03-28 (5 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130328) MarkForUpload: True ProcCmdline: /usr/sbin/modem-manager ProcEnviron: PATH=(custom, no user) TERM=linux SegvAnalysis: Segfault happened at: 0x7f7286b66f7f g_slice_alloc+223:mov (%rbx),%rax PC (0x7f7286b66f7f) ok source (%rbx) (0x10001) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: modemmanager StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: modem-manager crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2013-03-28 (12 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130328) MarkForUpload: True Package: network-manager PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Tags: raring Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1164023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164023] Re: modem-manager crashed with SIGSEGV in g_slice_alloc() - REGRESSION: No internet access via mobile broadband
Whoever gets this issue again, please make sure to grab SYSLOG around the time of the *crash* (not the connection issue), and attach it here :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1164023 Title: modem-manager crashed with SIGSEGV in g_slice_alloc() - REGRESSION: No internet access via mobile broadband Status in ModemManager (with NetworkManager support): New Status in “modemmanager” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: New Bug description: Happened again, after some attempts to connect via mobile broadband. With 12.10 access via mobile broadband works with this machine. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: modemmanager 0.6.0.0.really-0ubuntu4 Uname: Linux 3.9.0-030900rc5-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CrashCounter: 1 Date: Wed Apr 3 18:37:32 2013 ExecutablePath: /usr/sbin/modem-manager InstallationDate: Installed on 2013-03-28 (5 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130328) MarkForUpload: True ProcCmdline: /usr/sbin/modem-manager ProcEnviron: PATH=(custom, no user) TERM=linux SegvAnalysis: Segfault happened at: 0x7f7286b66f7f g_slice_alloc+223:mov (%rbx),%rax PC (0x7f7286b66f7f) ok source (%rbx) (0x10001) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: modemmanager StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: modem-manager crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1164023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1088984] Re: 3G connection is established, but no data is transferred -- ZTE MF 118
Please try with latest stable ModemManager 0.6.x, and get debug logs: https://wiki.ubuntu.com/DebuggingModemmanager -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1088984 Title: 3G connection is established, but no data is transferred -- ZTE MF 118 Status in “network-manager” package in Ubuntu: New Bug description: The connection is established properly and signal is strong, yet I cannot access any websites or other network service. Using ZTE MF 118 on 3G Mobile Broadband (Aircel INDIA). Worked when connected with sakis3g script. My Ubuntu version is Ubuntu 12.04.1 LTS 64-bit and network-manager version is 0.9.4.0. Modem-manager version is 0.5.2.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1088984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1113703] Re: Trying to connect using a GSM modem without SIM card is not reported to user
In the case of errors in call management; those are already passed back
to NetworkManager, but they get lost in there without getting to the UI
probably.
And for the case of the no SIM errors, you're right, the UI may not want
to spam the user with notifications about the missing SIM; but it may
just show the modem item with the error string in either the NM applet
or the Shell Indicator.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1113703
Title:
Trying to connect using a GSM modem without SIM card is not reported
to user
Status in ModemManager (with NetworkManager support):
Unknown
Status in NetworkManager:
Confirmed
Status in “gnome-shell” package in Ubuntu:
New
Status in “modemmanager” package in Ubuntu:
New
Status in “network-manager” package in Ubuntu:
New
Status in “network-manager-applet” package in Ubuntu:
New
Status in “networkmanagement” package in Ubuntu:
New
Bug description:
Trying to connect using a GSM modem that lacks a SIM card does just
give the user a general connection failure message without any hints
about the missing SIM card.
This can fool the user into thinking something other is wrong than the
fact that he forgot to insert the SIM card, or inserted it improperly.
Latest modemmanager master branch gives in log:
Feb 2 20:21:24 marius-T1005 ModemManager[1105]: warn Modem
couldn't be initialized: Couldn't check unlock status: SIM failure
but there is no indication to the user (nm-applet behaves as if mobile
broadband is unavailable).
Seems I get (from src/mm-error-helpers.c):
{ MM_MOBILE_EQUIPMENT_ERROR_SIM_FAILURE,
simfailure,SIM failure },
but should have got:
{ MM_MOBILE_EQUIPMENT_ERROR_SIM_NOT_INSERTED,
simnotinserted,SIM not inserted }
Anyway (any of them should be enough hint to the user), it seems like
the error state is not propagated (src/mm-broadband-modem.c):
static void
iface_modem_initialize_ready (MMBroadbandModem *self,
GAsyncResult *result,
InitializeContext *ctx)
{
GError *error = NULL;
/* If the modem interface fails to get initialized, we will move the modem
* to a FAILED state. Note that in this case we still export the
interface. */
if (!mm_iface_modem_initialize_finish (MM_IFACE_MODEM (self), result,
error)) {
/* Report the new FAILED state */
mm_warn (Modem couldn't be initialized: %s, error-message);
g_error_free (error);
mm_iface_modem_update_state (MM_IFACE_MODEM (self),
MM_MODEM_STATE_FAILED,
MM_MODEM_STATE_CHANGE_REASON_UNKNOWN);
/* Jump to the firmware step. We allow firmware switching even in
failed
* state */
ctx-step = INITIALIZE_STEP_IFACE_FIRMWARE;
initialize_step (ctx);
return;
}
Network Manager logs:
20:21:24 marius-T1005 NetworkManager[1128]: warn (ttyUSB2): unusable
modem detected
To manage notifications about this bug go to:
https://bugs.launchpad.net/modemmanager/+bug/1113703/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1113703] Re: Trying to connect using a GSM modem without SIM card is not reported to user
The first step is to let MM say why it is in Failed state; then the UI
can pick that up and show the proper message to the user.
See https://bugzilla.gnome.org/show_bug.cgi?id=691778
** Bug watch added: GNOME Bug Tracker #691778
https://bugzilla.gnome.org/show_bug.cgi?id=691778
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1113703
Title:
Trying to connect using a GSM modem without SIM card is not reported
to user
Status in NetworkManager:
Confirmed
Status in “modemmanager” package in Ubuntu:
New
Status in “network-manager” package in Ubuntu:
New
Status in “network-manager-applet” package in Ubuntu:
New
Bug description:
Trying to connect using a GSM modem that lacks a SIM card does just
give the user a general connection failure message without any hints
about the missing SIM card.
This can fool the user into thinking something other is wrong than the
fact that he forgot to insert the SIM card, or inserted it improperly.
Latest modemmanager master branch gives in log:
Feb 2 20:21:24 marius-T1005 ModemManager[1105]: warn Modem
couldn't be initialized: Couldn't check unlock status: SIM failure
but there is no indication to the user (nm-applet behaves as if mobile
broadband is unavailable).
Seems I get (from src/mm-error-helpers.c):
{ MM_MOBILE_EQUIPMENT_ERROR_SIM_FAILURE,
simfailure,SIM failure },
but should have got:
{ MM_MOBILE_EQUIPMENT_ERROR_SIM_NOT_INSERTED,
simnotinserted,SIM not inserted }
Anyway (any of them should be enough hint to the user), it seems like
the error state is not propagated (src/mm-broadband-modem.c):
static void
iface_modem_initialize_ready (MMBroadbandModem *self,
GAsyncResult *result,
InitializeContext *ctx)
{
GError *error = NULL;
/* If the modem interface fails to get initialized, we will move the modem
* to a FAILED state. Note that in this case we still export the
interface. */
if (!mm_iface_modem_initialize_finish (MM_IFACE_MODEM (self), result,
error)) {
/* Report the new FAILED state */
mm_warn (Modem couldn't be initialized: %s, error-message);
g_error_free (error);
mm_iface_modem_update_state (MM_IFACE_MODEM (self),
MM_MODEM_STATE_FAILED,
MM_MODEM_STATE_CHANGE_REASON_UNKNOWN);
/* Jump to the firmware step. We allow firmware switching even in
failed
* state */
ctx-step = INITIALIZE_STEP_IFACE_FIRMWARE;
initialize_step (ctx);
return;
}
Network Manager logs:
20:21:24 marius-T1005 NetworkManager[1128]: warn (ttyUSB2): unusable
modem detected
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1113703/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1071853] Re: Huawei K3565 Rev 2 (12d1:140c): Randomly disconnects from mobile broadband network and behaves as if USB modem physically disconnected
Restarting the applet does nothing; if the logic got stuck somewhere, you much better killall -9 modem-manager and/or restart NetworkManager directly; that should be equivalent to a reboot. Also, please attach ModemManager debug logs as per: https://wiki.ubuntu.com/DebuggingModemmanager And please test with latest package (from the PPA) as suggested by Marius, we fixed some critical issue in Huawei modems a couple of weeks ago. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1071853 Title: Huawei K3565 Rev 2 (12d1:140c): Randomly disconnects from mobile broadband network and behaves as if USB modem physically disconnected Status in “linux” package in Ubuntu: Incomplete Status in “modemmanager” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Status in “modemmanager” package in Debian: New Bug description: I connect to a mobile broadband network through a Huawei USB 3G modem. I stay connected all the time. Every once in a while, with almost systematic periodicity (like every 20-30 minutes), without any apparent reason, whether or not I am using the network or not, the nonnection suddenly goes down, and: - the indicator shows I'm disconnected, the - the mobile broadband networks (I have two of them configured, though I only use one now) disappear from the list in nm-applet - The option Enable Mobile Broadband at the bottom of the nm-applet menu DISAPPEARS (not that it gets unchecked, it _disappears_ completely) In order to reconnect I have to unplug and replug the usb modem, wait a few seconds for it to be initialized or whatever, and then reconnect via the nm-applet (when the nm-applet doesn't become unresponsive because of another old known bug). All the symptoms are EXACTLY as if someone had suddenly unplogged the modem physically, so this may as well be a usb problem. I have no idea what logs I should look for and attach. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 Date: Fri Oct 26 20:10:24 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) IpRoute: default via 10.64.64.64 dev ppp0 proto static 10.64.64.64 dev ppp0 proto kernel scope link src 77.210.172.228 169.254.0.0/16 dev ppp0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-05-17 (162 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-08-30T13:38:55.126319 nmcli-dev: DEVICE TYPE STATE DBUS-PATH ttyUSB0gsm connected /org/freedesktop/NetworkManager/Devices/19 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled enabled --- ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) NonfreeKernelModules: nvidia Package: network-manager PackageArchitecture: i386 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Tags: precise running-unity Uname: Linux 3.2.0-33-generic i686 UpgradeStatus: Upgraded to precise on 2012-05-17 (163 days ago) UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare vboxusers video --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2582 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49' Mixer name : 'Realtek ALC660-VD' Components : 'HDA:10ec0660,1043,0011 HDA:10573055,10431316,00100700' Controls : 28 Simple ctrls : 16 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MachineType:
[Desktop-packages] [Bug 861282] Re: 19d2:1015 ZTE K3806-Z network connection established, but does not work
Wader is another program offering the same DBus interface as ModemManager offers. NetworkManager can play well both with Wader and ModemManager. I would still like to see debug logs of ModemManager running with this modem, to see why we don't handle it well, while Wader does. So, please, anyone, try with NM and MM as suggested in comment #24. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/861282 Title: 19d2:1015 ZTE K3806-Z network connection established, but does not work Status in “modemmanager” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Incomplete Status in “usb-modeswitch” package in Ubuntu: New Bug description: usb_modeswitch properly switches from 1013 to 1015 after I set up a mobile broadband connection using networkmanager's gui. The connection is for Hungary, Vodafone. the swithc seemingly connects, IP is received, but can't access anything on the net could someone help me, please? I'm running natty on an eeepc x101 $ lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 005: ID 19d2:1015 ONDA Communication S.p.A. Bus 001 Device 003: ID 13d3:5711 IMC Networks Bus 001 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ ifconfig loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:19 errors:0 dropped:0 overruns:0 frame:0 TX packets:19 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1408 (1.4 KB) TX bytes:1408 (1.4 KB) usb0 Link encap:Ethernet HWaddr 02:46:82:e2:cb:5a inet addr:94.44.212.240 Bcast:94.44.212.240 Mask:255.255.255.255 inet6 addr: fe80::46:82ff:fee2:cb5a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:54 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:8742 (8.7 KB) wlan0 Link encap:Ethernet HWaddr 74:2f:68:8b:82:30 inet6 addr: fe80::762f:68ff:fe8b:8230/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:6195 errors:0 dropped:0 overruns:0 frame:0 TX packets:3709 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5353778 (5.3 MB) TX bytes:701868 (701.8 KB) thanks for any support! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/861282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1042456] Re: Huawei e398 doesn't work
Current MM in Ubuntu fully ignores WWAN ports handled using the QMI protocol; which means the modem is stuck to use PPP over a serial port. That method seems to be enough for slower connections like GSM/HSPA, but definitely not for LTE. The fix for this is to use QMI and the WWAN port, as done in current git master of MM :-/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1042456 Title: Huawei e398 doesn't work Status in “gvfs” package in Ubuntu: Invalid Status in “modemmanager” package in Ubuntu: Incomplete Bug description: After configuring in Network Manager all parameters specific to my ISP I can't connect to the network with such results: Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) starting connection 'Cyfrowy Polsat Default' Aug 28 00:01:07 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: disconnected - prepare (reason 'none') [30 40 0] Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) scheduled... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) starting... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: prepare - config (reason 'none') [40 50 0] Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) successful. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) scheduled. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) complete. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) started... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: config - ip-config (reason 'none') [50 70 0] Aug 28 00:01:07 ubuntu NetworkManager[1152]: info starting PPP connection Aug 28 00:01:07 ubuntu pppd[2849]: Plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info pppd started with pid 2849 Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) complete. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) started... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) complete. Aug 28 00:01:07 ubuntu pppd[2849]: pppd 2.4.5 started by root, uid 0 Aug 28 00:01:07 ubuntu pppd[2849]: Using interface ppp0 Aug 28 00:01:07 ubuntu pppd[2849]: Connect: ppp0 -- /dev/ttyUSB0 Aug 28 00:01:07 ubuntu NetworkManager[1152]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Aug 28 00:01:07 ubuntu NetworkManager[1152]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Aug 28 00:01:07 ubuntu NetworkManager[1152]: warn /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring... Aug 28 00:01:27 ubuntu NetworkManager[1152]: warn pppd timed out or didn't initialize our dbus module Aug 28 00:01:27 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... Aug 28 00:01:27 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) started... Aug 28 00:01:27 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: ip-config - failed (reason 'ip-config-unavailable') [70 120 5] Aug 28 00:01:27 ubuntu NetworkManager[1152]: warn Activation (ttyUSB0) failed for connection 'Cyfrowy Polsat Default' Aug 28 00:01:27 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) complete. Aug 28 00:01:27 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: failed - disconnected (reason 'none') [120 30 0] Aug 28 00:01:27 ubuntu NetworkManager[1152]: info (ttyUSB0): deactivating device (reason 'none') [0] Aug 28 00:01:27 ubuntu pppd[2849]: Terminating on signal 15 Aug 28 00:01:27 ubuntu modem-manager[1140]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected - disconnecting) Aug 28 00:01:27 ubuntu modem-manager[1140]: info Modem /org/freedesktop/ModemManager/Modems/0: state
[Desktop-packages] [Bug 1042456] Re: Huawei e398 doesn't work
@Marius: in your modems, are you using PPP for LTE? Maybe it's a Huawei- only issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1042456 Title: Huawei e398 doesn't work Status in “gvfs” package in Ubuntu: Invalid Status in “modemmanager” package in Ubuntu: Incomplete Bug description: After configuring in Network Manager all parameters specific to my ISP I can't connect to the network with such results: Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) starting connection 'Cyfrowy Polsat Default' Aug 28 00:01:07 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: disconnected - prepare (reason 'none') [30 40 0] Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) scheduled... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) starting... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: prepare - config (reason 'none') [40 50 0] Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) successful. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) scheduled. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) complete. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) started... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: config - ip-config (reason 'none') [50 70 0] Aug 28 00:01:07 ubuntu NetworkManager[1152]: info starting PPP connection Aug 28 00:01:07 ubuntu pppd[2849]: Plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info pppd started with pid 2849 Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) complete. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) started... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) complete. Aug 28 00:01:07 ubuntu pppd[2849]: pppd 2.4.5 started by root, uid 0 Aug 28 00:01:07 ubuntu pppd[2849]: Using interface ppp0 Aug 28 00:01:07 ubuntu pppd[2849]: Connect: ppp0 -- /dev/ttyUSB0 Aug 28 00:01:07 ubuntu NetworkManager[1152]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Aug 28 00:01:07 ubuntu NetworkManager[1152]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Aug 28 00:01:07 ubuntu NetworkManager[1152]: warn /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring... Aug 28 00:01:27 ubuntu NetworkManager[1152]: warn pppd timed out or didn't initialize our dbus module Aug 28 00:01:27 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... Aug 28 00:01:27 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) started... Aug 28 00:01:27 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: ip-config - failed (reason 'ip-config-unavailable') [70 120 5] Aug 28 00:01:27 ubuntu NetworkManager[1152]: warn Activation (ttyUSB0) failed for connection 'Cyfrowy Polsat Default' Aug 28 00:01:27 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) complete. Aug 28 00:01:27 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: failed - disconnected (reason 'none') [120 30 0] Aug 28 00:01:27 ubuntu NetworkManager[1152]: info (ttyUSB0): deactivating device (reason 'none') [0] Aug 28 00:01:27 ubuntu pppd[2849]: Terminating on signal 15 Aug 28 00:01:27 ubuntu modem-manager[1140]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected - disconnecting) Aug 28 00:01:27 ubuntu modem-manager[1140]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting - connected) It's also not possible to successfully launch this device under Server version using wvdial. ppp connection is dissconnected imediatly after first attempt to establish LTE connection. Best
[Desktop-packages] [Bug 1042456] Re: Huawei e398 doesn't work
Don't know; have not played with that modem. But what I can tell is that using AT+PPP in such a modem is probably a fallback method which is not supposed to be used... LTE speeds need a net port, PPP just introduces too much unnecessary overhead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1042456 Title: Huawei e398 doesn't work Status in “gvfs” package in Ubuntu: Invalid Status in “modemmanager” package in Ubuntu: Confirmed Bug description: After configuring in Network Manager all parameters specific to my ISP I can't connect to the network with such results: Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) starting connection 'Cyfrowy Polsat Default' Aug 28 00:01:07 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: disconnected - prepare (reason 'none') [30 40 0] Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) scheduled... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) starting... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: prepare - config (reason 'none') [40 50 0] Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) successful. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) scheduled. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 2 of 5 (Device Configure) complete. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) started... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: config - ip-config (reason 'none') [50 70 0] Aug 28 00:01:07 ubuntu NetworkManager[1152]: info starting PPP connection Aug 28 00:01:07 ubuntu pppd[2849]: Plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info pppd started with pid 2849 Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 3 of 5 (IP Configure Start) complete. Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) started... Aug 28 00:01:07 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv6 Configure Timeout) complete. Aug 28 00:01:07 ubuntu pppd[2849]: pppd 2.4.5 started by root, uid 0 Aug 28 00:01:07 ubuntu pppd[2849]: Using interface ppp0 Aug 28 00:01:07 ubuntu pppd[2849]: Connect: ppp0 -- /dev/ttyUSB0 Aug 28 00:01:07 ubuntu NetworkManager[1152]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Aug 28 00:01:07 ubuntu NetworkManager[1152]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Aug 28 00:01:07 ubuntu NetworkManager[1152]: warn /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring... Aug 28 00:01:27 ubuntu NetworkManager[1152]: warn pppd timed out or didn't initialize our dbus module Aug 28 00:01:27 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... Aug 28 00:01:27 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) started... Aug 28 00:01:27 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: ip-config - failed (reason 'ip-config-unavailable') [70 120 5] Aug 28 00:01:27 ubuntu NetworkManager[1152]: warn Activation (ttyUSB0) failed for connection 'Cyfrowy Polsat Default' Aug 28 00:01:27 ubuntu NetworkManager[1152]: info Activation (ttyUSB0) Stage 4 of 5 (IPv4 Configure Timeout) complete. Aug 28 00:01:27 ubuntu NetworkManager[1152]: info (ttyUSB0): device state change: failed - disconnected (reason 'none') [120 30 0] Aug 28 00:01:27 ubuntu NetworkManager[1152]: info (ttyUSB0): deactivating device (reason 'none') [0] Aug 28 00:01:27 ubuntu pppd[2849]: Terminating on signal 15 Aug 28 00:01:27 ubuntu modem-manager[1140]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected - disconnecting) Aug 28 00:01:27 ubuntu modem-manager[1140]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting - connected) It's also not possible to successfully
[Desktop-packages] [Bug 1070006] Re: Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)
Try to run nm-connection-editor and create a mobile broadband connection
setup for your provider. Once done, it should appear in the shell menu
and it also may be activated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1070006
Title:
Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)
Status in “gnome-control-center” package in Ubuntu:
New
Status in “modemmanager” package in Ubuntu:
Invalid
Status in “network-manager” package in Fedora:
Unknown
Bug description:
The modem (ZTE MF622) is recognised and 'Mobile Broadband' can be
enabled. The network is shown ('3' in the UK) and has signal strength
bars (2 for me). However, the modem doesn't connect.
Ubuntu Desktop displays a Mobile Broadband Connection dialog/wizard
which allows me to select and configure my network provider. Ubuntu
Gnome doesn't - I'm not sure if this is relevant.
Syslog does not show any activity by pppd, whereas it does on Desktop.
In fact, nothing relevant is shown in syslog after ModemManager shows
the change of state of the modem from 'enabled' to 'registered'.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: modemmanager 0.6.0.0.really-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
Date: Mon Oct 22 20:50:33 2012
InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Release
i386(20121018)
SourcePackage: modemmanager
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070006/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1060831] Re: Sierra/ZTE LTE modem gives no signal quality in LTE mode (only in 3G/2G mode)
Weird... is this happening for every LTE modem out there? We could have a new property in MMBroadbandModem specifying that +CSQ is always preferred over +CIND for signal quality updates (talking about git master here), so that plugins can set it when that happens. Or, if the issue is really more generic and happens with most LTE modems out there, we could force using +CSQ when in LTE. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1060831 Title: Sierra/ZTE LTE modem gives no signal quality in LTE mode (only in 3G/2G mode) Status in “modemmanager” package in Ubuntu: Triaged Status in “network-manager-applet” package in Ubuntu: Invalid Bug description: In LTE mode, the sierra modem (MC7710) gives no indication of signal quality in nm-applet. It looks like icon gsm-3g-none.svg. I suspect this is caused by this in the modemmanager debug log when connected: modem-manager[25672]: debug [1349256755.558392] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'AT*CNTI=0CR' modem-manager[25672]: debug [1349256755.579056] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF*CNTI: 0,LTECRLFCRLFOKCRLF' modem-manager[25672]: debug [1349256758.802283] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'AT+CIND?CR' modem-manager[25672]: debug [1349256758.821538] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF+CIND: 5,0,1,1,0,0,1,0CRLFCRLFOKCRLF' Seems like the signal quality is the second number: Oct 1 19:23:39 marius-T1005 ModemManager[22170]: debug [1349112219.280233] [mm-at-serial-port.c:392] debug_log(): (ttyUSB3): -- 'CRLF+CIND: (battchg,(0-5)),(signal,(0-5)),(service,(0-1)),(call,(0-1)),(roam,(0-1)),(s msfull,(0-1)),(GPRS coverage,(0-1)),(callsetup,(0-3))CRLFCRLFOKCRLF' Oct 1 19:23:39 marius-T1005 ModemManager[22170]: debug [1349112219.280871] [mm-broadband-modem.c:1704] cind_format _check_ready(): Modem supports signal quality indications via CIND at index '2'(min: 0, max: 5) which is reported as zero. The signal is good (I measure download rate of 37 mbits/s), and in 3G/2G mode I get the correct signal quality indication. Could it be that MM should not use +CIND but instead +CSQ? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu5 Uname: Linux 3.6.0-030600rc6-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Wed Oct 3 11:19:55 2012 EcryptfsInUse: Yes IpRoute: default via 89.9.192.92 dev wwan0 proto static 89.9.192.0/24 dev wwan0 proto kernel scope link src 89.9.192.92 metric 7 169.254.0.0/16 dev wwan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm PATH=(custom, no user) LANG=nb_NO.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-08-31 (32 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wwan0 gsm connected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1060831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1060831] Re: Sierra/ZTE LTE modem gives no signal quality in LTE mode (only in 3G/2G mode)
On 10/03/2012 02:19 PM, Marius Kotsbak wrote: Well, those two modems have in common that they are both using Qualcomm chipsets (supporting QMI protocol), so it might just be a bug there. I think there is such property in place, at least in the MM_06 branch. The question is just when we want to change the default. I am not sure if the indication in my modems are worse using CSQ than CIND in 3G mode (although CSQ seems more fine grained). Maybe we can detect when the CSQ value is bogous (e.g. +CSQ: 99, 99) instead and only then use CIND? Do we get the proper values through QMI? -- Aleksander -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1060831 Title: Sierra/ZTE LTE modem gives no signal quality in LTE mode (only in 3G/2G mode) Status in “modemmanager” package in Ubuntu: Triaged Status in “network-manager-applet” package in Ubuntu: Invalid Bug description: In LTE mode, the sierra modem (MC7710) gives no indication of signal quality in nm-applet. It looks like icon gsm-3g-none.svg. I suspect this is caused by this in the modemmanager debug log when connected: modem-manager[25672]: debug [1349256755.558392] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'AT*CNTI=0CR' modem-manager[25672]: debug [1349256755.579056] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF*CNTI: 0,LTECRLFCRLFOKCRLF' modem-manager[25672]: debug [1349256758.802283] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'AT+CIND?CR' modem-manager[25672]: debug [1349256758.821538] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF+CIND: 5,0,1,1,0,0,1,0CRLFCRLFOKCRLF' Seems like the signal quality is the second number: Oct 1 19:23:39 marius-T1005 ModemManager[22170]: debug [1349112219.280233] [mm-at-serial-port.c:392] debug_log(): (ttyUSB3): -- 'CRLF+CIND: (battchg,(0-5)),(signal,(0-5)),(service,(0-1)),(call,(0-1)),(roam,(0-1)),(s msfull,(0-1)),(GPRS coverage,(0-1)),(callsetup,(0-3))CRLFCRLFOKCRLF' Oct 1 19:23:39 marius-T1005 ModemManager[22170]: debug [1349112219.280871] [mm-broadband-modem.c:1704] cind_format _check_ready(): Modem supports signal quality indications via CIND at index '2'(min: 0, max: 5) which is reported as zero. The signal is good (I measure download rate of 37 mbits/s), and in 3G/2G mode I get the correct signal quality indication. Could it be that MM should not use +CIND but instead +CSQ? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu5 Uname: Linux 3.6.0-030600rc6-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Wed Oct 3 11:19:55 2012 EcryptfsInUse: Yes IpRoute: default via 89.9.192.92 dev wwan0 proto static 89.9.192.0/24 dev wwan0 proto kernel scope link src 89.9.192.92 metric 7 169.254.0.0/16 dev wwan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm PATH=(custom, no user) LANG=nb_NO.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-08-31 (32 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wwan0 gsm connected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1060831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1060831] Re: Sierra/ZTE LTE modem gives no signal quality in LTE mode (only in 3G/2G mode)
+CSQ is usually defined as a value between 1 and 31; plus 99 for unknown. ModemManager scales this value to the expected [0,100] range. The signal strength reported with QMI is based on RSSI, which we then convert to the same [0,100] range. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1060831 Title: Sierra/ZTE LTE modem gives no signal quality in LTE mode (only in 3G/2G mode) Status in “modemmanager” package in Ubuntu: Triaged Status in “network-manager-applet” package in Ubuntu: Invalid Bug description: In LTE mode, the sierra modem (MC7710) gives no indication of signal quality in nm-applet. It looks like icon gsm-3g-none.svg. I suspect this is caused by this in the modemmanager debug log when connected: modem-manager[25672]: debug [1349256755.558392] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'AT*CNTI=0CR' modem-manager[25672]: debug [1349256755.579056] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF*CNTI: 0,LTECRLFCRLFOKCRLF' modem-manager[25672]: debug [1349256758.802283] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'AT+CIND?CR' modem-manager[25672]: debug [1349256758.821538] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF+CIND: 5,0,1,1,0,0,1,0CRLFCRLFOKCRLF' Seems like the signal quality is the second number: Oct 1 19:23:39 marius-T1005 ModemManager[22170]: debug [1349112219.280233] [mm-at-serial-port.c:392] debug_log(): (ttyUSB3): -- 'CRLF+CIND: (battchg,(0-5)),(signal,(0-5)),(service,(0-1)),(call,(0-1)),(roam,(0-1)),(s msfull,(0-1)),(GPRS coverage,(0-1)),(callsetup,(0-3))CRLFCRLFOKCRLF' Oct 1 19:23:39 marius-T1005 ModemManager[22170]: debug [1349112219.280871] [mm-broadband-modem.c:1704] cind_format _check_ready(): Modem supports signal quality indications via CIND at index '2'(min: 0, max: 5) which is reported as zero. The signal is good (I measure download rate of 37 mbits/s), and in 3G/2G mode I get the correct signal quality indication. Could it be that MM should not use +CIND but instead +CSQ? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu5 Uname: Linux 3.6.0-030600rc6-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Wed Oct 3 11:19:55 2012 EcryptfsInUse: Yes IpRoute: default via 89.9.192.92 dev wwan0 proto static 89.9.192.0/24 dev wwan0 proto kernel scope link src 89.9.192.92 metric 7 169.254.0.0/16 dev wwan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm PATH=(custom, no user) LANG=nb_NO.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-08-31 (32 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wwan0 gsm connected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1060831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1060831] Re: Sierra/ZTE LTE modem gives no signal quality in LTE mode (only in 3G/2G mode)
Not really, no. What I'm not sure is why CIND is preferred over CSQ by default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1060831 Title: Sierra/ZTE LTE modem gives no signal quality in LTE mode (only in 3G/2G mode) Status in “modemmanager” package in Ubuntu: Triaged Status in “network-manager-applet” package in Ubuntu: Invalid Bug description: In LTE mode, the sierra modem (MC7710) gives no indication of signal quality in nm-applet. It looks like icon gsm-3g-none.svg. I suspect this is caused by this in the modemmanager debug log when connected: modem-manager[25672]: debug [1349256755.558392] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'AT*CNTI=0CR' modem-manager[25672]: debug [1349256755.579056] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF*CNTI: 0,LTECRLFCRLFOKCRLF' modem-manager[25672]: debug [1349256758.802283] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'AT+CIND?CR' modem-manager[25672]: debug [1349256758.821538] [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF+CIND: 5,0,1,1,0,0,1,0CRLFCRLFOKCRLF' Seems like the signal quality is the second number: Oct 1 19:23:39 marius-T1005 ModemManager[22170]: debug [1349112219.280233] [mm-at-serial-port.c:392] debug_log(): (ttyUSB3): -- 'CRLF+CIND: (battchg,(0-5)),(signal,(0-5)),(service,(0-1)),(call,(0-1)),(roam,(0-1)),(s msfull,(0-1)),(GPRS coverage,(0-1)),(callsetup,(0-3))CRLFCRLFOKCRLF' Oct 1 19:23:39 marius-T1005 ModemManager[22170]: debug [1349112219.280871] [mm-broadband-modem.c:1704] cind_format _check_ready(): Modem supports signal quality indications via CIND at index '2'(min: 0, max: 5) which is reported as zero. The signal is good (I measure download rate of 37 mbits/s), and in 3G/2G mode I get the correct signal quality indication. Could it be that MM should not use +CIND but instead +CSQ? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu5 Uname: Linux 3.6.0-030600rc6-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Wed Oct 3 11:19:55 2012 EcryptfsInUse: Yes IpRoute: default via 89.9.192.92 dev wwan0 proto static 89.9.192.0/24 dev wwan0 proto kernel scope link src 89.9.192.92 metric 7 169.254.0.0/16 dev wwan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm PATH=(custom, no user) LANG=nb_NO.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-08-31 (32 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wwan0 gsm connected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1060831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 977761] Re: Connection with ZTE MF820D LTE/4G modem not using new qmi-wdm/qmi_wwan kernel modules
Backporting the QMI support from MM git master (0.7) to 0.5/0.6 is a thousand times more complex than improving NetworkManager to support MM 0.7, which is anyway something planned to be done. Help welcome :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/977761 Title: Connection with ZTE MF820D LTE/4G modem not using new qmi-wdm/qmi_wwan kernel modules Status in ModemManager (with NetworkManager support): In Progress Status in “linux” package in Ubuntu: Fix Released Status in “modemmanager” package in Ubuntu: Triaged Status in “network-manager” package in Ubuntu: Invalid Bug description: USB modeswitching works ok, and the network operator appears in the NM menu, but it fails to connect. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: modemmanager 0.5.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Tue Apr 10 08:48:55 2012 EcryptfsInUse: Yes SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 DistroRelease: Ubuntu 12.04 EcryptfsInUse: Yes Package: modemmanager 0.5.2.0-0ubuntu2 [modified: lib/udev/rules.d/77-mm-zte-port-types.rules] PackageArchitecture: i386 ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm PATH=(custom, user) LANG=nb_NO.UTF-8 SHELL=/bin/bash Tags: precise precise Uname: Linux 3.4.0-030400rc4-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm dialout lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/977761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 438150] Re: NetworkManager fails to reconnect 3G modem after disconnect -- Huawei
I found this to be caused by ModemManager using the PPP port for both control and PPP; instead of the PCUI port for control and the PPP port for PPP. This issue should be fixed in the MM_06 branch of ModemManager already, as well as in git master. If anyone can try with MM_06 branch to confirm it, it would be great. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/438150 Title: NetworkManager fails to reconnect 3G modem after disconnect -- Huawei Status in “modemmanager” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Invalid Bug description: Binary package hint: network-manager Running latest Karmic updates (but this has been happening since I first tested with alpha 6). First connection to the network on my 3G USB modem works perfectly. However, if I lose connection (if I'm moving and roam outside cell coverage) then I lose connection but when I come back into coverage (blue blinking light on modem indicates coverage) I am unable to reconnect. Each time I select the network from the nm-applet I just get the OSD notify that the GSM network disconnected. Unplugging and re-plugging in my modem does not help. The only way to successfully connect is by rebooting my laptop. Syslog shows the following: Sep 28 07:36:24 spitfire-karmic NetworkManager: info (ttyUSB0): device state change: 8 - 9 (reason 13) Sep 28 07:36:24 spitfire-karmic NetworkManager: info Activation (ttyUSB0) failed. Sep 28 07:36:24 spitfire-karmic NetworkManager: info (ttyUSB0): device state change: 9 - 3 (reason 0) Sep 28 07:36:24 spitfire-karmic NetworkManager: info (ttyUSB0): deactivating device (reason: 0). Sep 28 07:36:24 spitfire-karmic modem-manager: (ttyUSB0) closing serial device... Sep 28 07:36:24 spitfire-karmic NetworkManager: WARN monitor_cb(): Could not read ppp stats: No such device Sep 28 07:36:24 spitfire-karmic NetworkManager: flush_routes: assertion `iface_idx = 0' failed Sep 28 07:36:24 spitfire-karmic NetworkManager: flush_addresses: assertion `iface_idx = 0' failed Sep 28 07:36:24 spitfire-karmic NetworkManager:SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Sep 28 07:36:26 spitfire-karmic NetworkManager: debug [1254119786.002657] ensure_killed(): waiting for ppp pid 5661 to exit Sep 28 07:36:26 spitfire-karmic NetworkManager: debug [1254119786.002994] ensure_killed(): ppp pid 5661 cleaned up Sep 28 07:37:56 spitfire-karmic NetworkManager: info Activation (ttyUSB0) starting connection '3 Internet' Sep 28 07:37:56 spitfire-karmic NetworkManager: info (ttyUSB0): device state change: 3 - 4 (reason 0) Sep 28 07:37:56 spitfire-karmic NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Sep 28 07:37:56 spitfire-karmic NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Sep 28 07:37:56 spitfire-karmic NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Sep 28 07:37:56 spitfire-karmic modem-manager: (ttyUSB0) opening serial device... Sep 28 07:37:56 spitfire-karmic NetworkManager: WARN stage1_prepare_done(): GSM modem connection failed: Could not open serial device ttyUSB0: No such device Sep 28 07:37:56 spitfire-karmic NetworkManager: info (ttyUSB0): device state change: 4 - 9 (reason 1) Sep 28 07:37:56 spitfire-karmic NetworkManager: info Marking connection '3 Internet' invalid. Sep 28 07:37:56 spitfire-karmic NetworkManager: Tried to set deprecated property gsm/puk ProblemType: Bug Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Mon Sep 28 14:37:31 2009 DistroRelease: Ubuntu 9.10 IfupdownConfig: auto lo iface lo inet loopback IpRoute: 10.64.64.64 dev ppp0 proto kernel scope link src 92.40.27.251 169.254.0.0/16 dev ppp0 scope link metric 1000 default via 10.64.64.64 dev ppp0 proto static Package: network-manager 0.8~a~git.20090923t064445.b20cef2-0ubuntu1 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic SourcePackage: network-manager Uname: Linux 2.6.31-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/438150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 977761] Re: Connection with ZTE MF820D LTE/4G modem not using new qmi-wdm/qmi_wwan kernel modules
There is work in progress already to use the cdc-wdm0 interface for QMI with libqmi in ModemManager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/977761 Title: Connection with ZTE MF820D LTE/4G modem not using new qmi-wdm/qmi_wwan kernel modules Status in ModemManager (with NetworkManager support): New Status in “linux” package in Ubuntu: Fix Released Status in “modemmanager” package in Ubuntu: Triaged Status in “network-manager” package in Ubuntu: Invalid Bug description: USB modeswitching works ok, and the network operator appears in the NM menu, but it fails to connect. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: modemmanager 0.5.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Tue Apr 10 08:48:55 2012 EcryptfsInUse: Yes SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 DistroRelease: Ubuntu 12.04 EcryptfsInUse: Yes Package: modemmanager 0.5.2.0-0ubuntu2 [modified: lib/udev/rules.d/77-mm-zte-port-types.rules] PackageArchitecture: i386 ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm PATH=(custom, user) LANG=nb_NO.UTF-8 SHELL=/bin/bash Tags: precise precise Uname: Linux 3.4.0-030400rc4-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm dialout lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/977761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 977761] Re: Connection with ZTE MF820D LTE/4G modem not using new qmi-wdm/qmi_wwan kernel modules
Still quite some things to do before being able to use QMI in ModemManager, including finishing to port all pending MM plugins to the new codebase, and updating NetworkManager to talk to the new redesigned interface... Current MM git master is not yet able to talk to NM git master. Help really welcome :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/977761 Title: Connection with ZTE MF820D LTE/4G modem not using new qmi-wdm/qmi_wwan kernel modules Status in ModemManager (with NetworkManager support): New Status in “linux” package in Ubuntu: Fix Released Status in “modemmanager” package in Ubuntu: Triaged Status in “network-manager” package in Ubuntu: Invalid Bug description: USB modeswitching works ok, and the network operator appears in the NM menu, but it fails to connect. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: modemmanager 0.5.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Tue Apr 10 08:48:55 2012 EcryptfsInUse: Yes SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 DistroRelease: Ubuntu 12.04 EcryptfsInUse: Yes Package: modemmanager 0.5.2.0-0ubuntu2 [modified: lib/udev/rules.d/77-mm-zte-port-types.rules] PackageArchitecture: i386 ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm PATH=(custom, user) LANG=nb_NO.UTF-8 SHELL=/bin/bash Tags: precise precise Uname: Linux 3.4.0-030400rc4-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm dialout lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/977761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 868034] Re: Huawei E220 can't connect on Ubuntu 11.10
Sleepy John: syslog log is pretty useless if ModemManager wasn't run with --debug, :-/ And regarding the priority, I really don't give a s*** about it :-) I personally do this in my free time, so at least for me, it doesn't matter if it was low or super-critical, I'll try to help if I have time. Josua Dietze: The first test I suggest is to ensure that the newer kernel has no effect on this issue. If MM 0.4 works ok with the newer kernel, it's probably MM's fault. The second test I suggest is to completely avoid using the secondary port. If that test succeeds we can probably force MM to avoid using the secondary port for this specific Huawei device, at least until we can figure out why it failed that way. So logs (in debug mode) for these tests will really help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/868034 Title: Huawei E220 can't connect on Ubuntu 11.10 Status in ModemManager (with NetworkManager support): Unknown Status in “modemmanager” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “modemmanager” package in Debian: New Status in “modemmanager” package in Fedora: Unknown Bug description: I'm using Ubuntu in my HP Pavilion dv6745tx laptop. I cannot connect the Huawei E220 usb modem since 11.10 beta1 (now I'm in beta2). There is no problem in natty. I have found this in syslog Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) starting connection 'Dialog GSM Postpaid' Oct 5 07:10:51 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: disconnected - prepare (reason 'none') [30 40 0] Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Oct 5 07:10:58 ubuntu NetworkManager[1681]: warn GSM connection failed: (32) Sending command failed: 'Resource temporarily unavailable' Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: prepare - failed (reason 'unknown') [40 120 1] Oct 5 07:10:58 ubuntu NetworkManager[1681]: warn Activation (ttyUSB0) failed. Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: failed - disconnected (reason 'none') [120 30 0] Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): deactivating device (reason: 0). Oct 5 07:10:58 ubuntu NetworkManager[1681]: nm_system_iface_flush_routes: assertion `ifindex 0' failed Oct 5 07:10:58 ubuntu NetworkManager[1681]: nm_system_iface_flush_addresses: assertion `ifindex 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/868034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 868034] Re: Huawei E220 can't connect on Ubuntu 11.10
I'll follow up the issue in GB#662113 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/868034 Title: Huawei E220 can't connect on Ubuntu 11.10 Status in ModemManager (with NetworkManager support): Unknown Status in “modemmanager” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “modemmanager” package in Debian: New Status in “modemmanager” package in Fedora: Unknown Bug description: I'm using Ubuntu in my HP Pavilion dv6745tx laptop. I cannot connect the Huawei E220 usb modem since 11.10 beta1 (now I'm in beta2). There is no problem in natty. I have found this in syslog Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) starting connection 'Dialog GSM Postpaid' Oct 5 07:10:51 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: disconnected - prepare (reason 'none') [30 40 0] Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Oct 5 07:10:58 ubuntu NetworkManager[1681]: warn GSM connection failed: (32) Sending command failed: 'Resource temporarily unavailable' Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: prepare - failed (reason 'unknown') [40 120 1] Oct 5 07:10:58 ubuntu NetworkManager[1681]: warn Activation (ttyUSB0) failed. Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: failed - disconnected (reason 'none') [120 30 0] Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): deactivating device (reason: 0). Oct 5 07:10:58 ubuntu NetworkManager[1681]: nm_system_iface_flush_routes: assertion `ifindex 0' failed Oct 5 07:10:58 ubuntu NetworkManager[1681]: nm_system_iface_flush_addresses: assertion `ifindex 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/868034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 868034] Re: Huawei E220 can't connect on Ubuntu 11.10
Great, so anyone requiring to use MM with the Huawei modem can fallback to 0.4 until the proper fix arrives in a 0.5 update. Mark: step 4 not really needed; just killall modem-manager should do it after installing the new .deb; and even that may not be needed depending on the post install packaging rules. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/868034 Title: Huawei E220 can't connect on Ubuntu 11.10 Status in ModemManager (with NetworkManager support): Unknown Status in “modemmanager” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “modemmanager” package in Debian: New Status in “modemmanager” package in Fedora: Unknown Bug description: I'm using Ubuntu in my HP Pavilion dv6745tx laptop. I cannot connect the Huawei E220 usb modem since 11.10 beta1 (now I'm in beta2). There is no problem in natty. I have found this in syslog Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) starting connection 'Dialog GSM Postpaid' Oct 5 07:10:51 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: disconnected - prepare (reason 'none') [30 40 0] Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Oct 5 07:10:58 ubuntu NetworkManager[1681]: warn GSM connection failed: (32) Sending command failed: 'Resource temporarily unavailable' Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: prepare - failed (reason 'unknown') [40 120 1] Oct 5 07:10:58 ubuntu NetworkManager[1681]: warn Activation (ttyUSB0) failed. Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: failed - disconnected (reason 'none') [120 30 0] Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): deactivating device (reason: 0). Oct 5 07:10:58 ubuntu NetworkManager[1681]: nm_system_iface_flush_routes: assertion `ifindex 0' failed Oct 5 07:10:58 ubuntu NetworkManager[1681]: nm_system_iface_flush_addresses: assertion `ifindex 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/868034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 868034] Re: Huawei E220 can't connect on Ubuntu 11.10
Upstream devs know about the issue, and I was supposed to try to reproduce this with my Huawei 220. I just don't have time to test it myself whenever I remember that I have to test it. Can someone provide modem-manager debug logs with the previous version, the one that worked? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/868034 Title: Huawei E220 can't connect on Ubuntu 11.10 Status in NetworkManager: New Status in “modemmanager” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “modemmanager” package in Fedora: Unknown Bug description: I'm using Ubuntu in my HP Pavilion dv6745tx laptop. I cannot connect the Huawei E220 usb modem since 11.10 beta1 (now I'm in beta2). There is no problem in natty. I have found this in syslog Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) starting connection 'Dialog GSM Postpaid' Oct 5 07:10:51 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: disconnected - prepare (reason 'none') [30 40 0] Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Oct 5 07:10:58 ubuntu NetworkManager[1681]: warn GSM connection failed: (32) Sending command failed: 'Resource temporarily unavailable' Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: prepare - failed (reason 'unknown') [40 120 1] Oct 5 07:10:58 ubuntu NetworkManager[1681]: warn Activation (ttyUSB0) failed. Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): device state change: failed - disconnected (reason 'none') [120 30 0] Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): deactivating device (reason: 0). Oct 5 07:10:58 ubuntu NetworkManager[1681]: nm_system_iface_flush_routes: assertion `ifindex 0' failed Oct 5 07:10:58 ubuntu NetworkManager[1681]: nm_system_iface_flush_addresses: assertion `ifindex 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/868034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 868034] Re: Huawei E220 can't connect on Ubuntu 11.10
Mark: Thanks for the logs
I can find two main differences in the MM 0.4 (the one which worked) and
MM 0.5 (the one which failed) log.
1) In the MM 0.5 log, the secondary ttyUSB1 gets probed and grabbed as
secondary port; while in the MM 0.4 log capability probing in that port
is not even launched (just grep for USB1 in both logs, and compare the
results)
In the MM 0.4 log:
debug [mm-modem-base.c:155] mm_modem_base_add_port(): (ttyUSB1) type ignored
claimed by /sys/devices/pci:00/:00:1a.1/usb4/4-2
In the MM 0.5 log:
debug [mm-modem-base.c:155] mm_modem_base_add_port(): (ttyUSB1) type
secondary claimed by /sys/devices/pci:00/:00:1a.1/usb4/4-2
This is already pretty weird, as in MM 0.4 the ttyUSB1 port is grabbed
but wasn't probed at all. I wonder if there is some kind of issue with
the kernel driver which exposes two ports with usbif=0. Don't know if
that is even possible.
2) MM 0.5 has some changes in the Huawei plugin. We now use AT^CURC,
AT^GETPORTMODE commands when it gets initialized. AT^CURC=0 when the
first port is tried will disable unsolicited messages in the secondary
port, and AT^GETPORTMODE tries to query
In any case, the problem seems to be that the modem gets rebooted at some
point. This happens after we enable unsolicited messages in the secondary port
with AT^CURC=1, and after we send the first commands to that secondary port.
Last logs from the modem show this BOOT message.
debug [mm-at-serial-port.c:298] debug_log(): (ttyUSB1): --
'CRLF^BOOT:92988511,0,0,0,6CRLF'
If someone can do more tests, I would now try:
A) Try the MM 0.4 version from Ubuntu 11.04 directly in Ubuntu 11.10.
You should be able to dpkg --purge modem-manager (no package depends on
it in Ubuntu) ad then dpkg -i the specific deb retrieved from the Ubuntu
11.04 archive. This would help to see if we do get ttyUSB1 grabbed also
as secondary port in the newer kernel.
B) Hack the Huawei plugin in a custom MM 0.5 branch so that it ignores
all ports except for the primary one grabbed. This can be done by
changing the whole last else {} switch in grab_port() within plugins/mm-
plugin-huawei.c, to just mm_modem_grab_port() passing ptype =
MM_PORT_TYPE_IGNORED. This would help to see if we really are managing
wrong the secondary port, and is just better to skip it in this specific
modem, or try to refix it if we know how.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/868034
Title:
Huawei E220 can't connect on Ubuntu 11.10
Status in NetworkManager:
New
Status in “modemmanager” package in Ubuntu:
Confirmed
Status in “network-manager” package in Ubuntu:
In Progress
Status in “modemmanager” package in Fedora:
Unknown
Bug description:
I'm using Ubuntu in my HP Pavilion dv6745tx laptop. I cannot connect
the Huawei E220 usb modem since 11.10 beta1 (now I'm in beta2). There
is no problem in natty.
I have found this in syslog
Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0)
starting connection 'Dialog GSM Postpaid'
Oct 5 07:10:51 ubuntu NetworkManager[1681]: info (ttyUSB0): device state
change: disconnected - prepare (reason 'none') [30 40 0]
Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0)
Stage 1 of 5 (Device Prepare) scheduled...
Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0)
Stage 1 of 5 (Device Prepare) started...
Oct 5 07:10:51 ubuntu NetworkManager[1681]: info Activation (ttyUSB0)
Stage 1 of 5 (Device Prepare) complete.
Oct 5 07:10:58 ubuntu NetworkManager[1681]: warn GSM connection failed:
(32) Sending command failed: 'Resource temporarily unavailable'
Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): device state
change: prepare - failed (reason 'unknown') [40 120 1]
Oct 5 07:10:58 ubuntu NetworkManager[1681]: warn Activation (ttyUSB0)
failed.
Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): device state
change: failed - disconnected (reason 'none') [120 30 0]
Oct 5 07:10:58 ubuntu NetworkManager[1681]: info (ttyUSB0): deactivating
device (reason: 0).
Oct 5 07:10:58 ubuntu NetworkManager[1681]: nm_system_iface_flush_routes:
assertion `ifindex 0' failed
Oct 5 07:10:58 ubuntu NetworkManager[1681]: nm_system_iface_flush_addresses:
assertion `ifindex 0' failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/868034/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
