I am using Fedora 20 with the rhughes/f20-gnome-3-12 COPR on a Lenovo ThinkPad X1 Carbon (2014). Since a recent package update the mobile broadband connection is no longer listed in NetworkManager. When I restart the ModemManager service ("sudo service ModemManager restart") I get the following: SELinux is preventing /usr/sbin/ModemManager from execute access on the file . ***** Plugin catchall (100. confidence) suggests ************************** If you believe that ModemManager should be allowed execute access on the file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep ModemManager /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:modemmanager_t:s0 Target Context system_u:object_r:bin_t:s0 Target Objects [ file ] Source ModemManager Source Path /usr/sbin/ModemManager Port <Unknown> Host localhost.localdomain Source RPM Packages ModemManager-1.2.0-1.fc20.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-153.fc20.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name localhost.localdomain Platform Linux localhost.localdomain 3.13.10-200.fc20.x86_64 #1 SMP Mon Apr 14 20:34:16 UTC 2014 x86_64 x86_64 Alert Count 108 First Seen 2014-04-03 16:40:53 CEST Last Seen 2014-05-01 07:55:02 CEST Local ID 719e2a94-1a7c-4b37-9b06-850b35c92701 Raw Audit Messages type=AVC msg=audit(1398923702.379:399): avc: denied { execute } for pid=2696 comm="ModemManager" path="/usr/lib64/gvfs/libgvfscommon.so" dev="dm-2" ino=2490810 scontext=system_u:system_r:modemmanager_t:s0 tcontext=system_u:object_r:bin_t:s0 tclass=file type=SYSCALL msg=audit(1398923702.379:399): arch=x86_64 syscall=mmap success=no exit=EACCES a0=0 a1=23cdb8 a2=5 a3=802 items=0 ppid=1 pid=2696 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=ModemManager exe=/usr/sbin/ModemManager subj=system_u:system_r:modemmanager_t:s0 key=(null) Hash: ModemManager,modemmanager_t,bin_t,file,execute
I ran grep ModemManager /var/log/audit/audit.log | audit2allow -M mypol semodule -i mypol.pp service ModemManager restart and no longer the SELinux error. However, I also still do not see the mobile broadband connection in NetworkManager.
Can you try with SELinux disabled? (sudo setenforce 0) If that doesn't help, please include system logs.
"sudo setenforce 0" does not seem to have an effect: $ sudo setenforce 0 $ getenforce Permissive $ sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Max kernel policy version: 29
I booted with "selinux=0" now just to make sure $ getenforce disabled $ sestatus SELinux status: disabled But even with SELinux completely disabled NetworkManager does not list my mobile broadband connection. Looks like this is not related to SELinux after all.
Is the ModemManager service enabled? Try: systemctl enable ModemManager systemctl start ModemManager If that fails to make things work on restart, then lets get the output of: systemctl status ModemManager
ModemManager.service - Modem Manager Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled) Active: active (running) since Wed 2014-05-21 07:06:16 CEST; 26s ago Main PID: 924 (ModemManager) CGroup: /system.slice/ModemManager.service └─924 /usr/sbin/ModemManager May 21 07:06:19 localhost.localdomain ModemManager[924]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0': not supported by any plugin May 21 07:06:20 localhost.localdomain ModemManager[924]: [/dev/cdc-wdm0] Queried max control message size: 512 May 21 07:06:20 localhost.localdomain ModemManager[924]: <info> Creating modem with plugin 'Generic' and '3' ports May 21 07:06:20 localhost.localdomain ModemManager[924]: <info> Modem for device at '/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4' successfully created May 21 07:06:20 localhost.localdomain ModemManager[924]: [/dev/cdc-wdm0] Queried max control message size: 512 May 21 07:06:29 localhost.localdomain ModemManager[924]: <warn> Modem couldn't be initialized: Couldn't check unlock status: SIM not inserted May 21 07:06:29 localhost.localdomain ModemManager[924]: <info> Modem: state changed (unknown -> failed) May 21 07:06:32 localhost.localdomain ModemManager[924]: <info> Creating modem with plugin 'Generic' and '1' ports May 21 07:06:32 localhost.localdomain ModemManager[924]: <warn> Could not grab port (tty/ttyS0): 'Cannot add port 'tty/ttyS0', unhandled serial type' May 21 07:06:32 localhost.localdomain ModemManager[924]: <warn> Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port
I do not understand the "SIM not inserted" warning as a SIM is inserted. When I initially got and set up the laptop the mobile broadband connection worked find with that SIM.
Do you have /dev/ttyACM0 or ACM1 devices on the system? If so, could you install 'minicom' and then: systemctl mask ModemManager systemctl stop ModemManager minicom -D /dev/ttyACM0 once that has started, type: AT+CPIN? and hit Return/Enter. What is the response? After you get the response, then try: AT+CIMI and hit Return/Enter. *Don't* paste this number, but just tell me if it is a ~15 number. For example, the whole exchange should look like this if everything is going well: ---------------- AT+CPIN? +CPIN: READY OK AT+CIMI 311480000012345 OK ---------------- If the modem doesn't think the SIM is inserted, you will see something like this: ---------------- AT+CPIN? +CME ERROR: SIM not inserted AT+CIMI ERROR ---------------- Sometimes the SIM can be inserted the wrong way becuase the machine allows you to do that. Sometimes it can be vibrated loose. If the device really doesn't think you have a SIM card inserted, try ejecting the SIM and re-inserting it, making sure it's inserted correctly. Let me know!
The SIM card is inserted correctly. I removed it and put it back in. I do not see the characters ("AT+CPIN?") when I type them in minocom. After Return/Enter I get an "+CME ERROR: 10": Welcome to minicom 2.6.2 OPTIONS: I18n Compiled on Aug 7 2013, 13:32:48. Port /dev/ttyACM0, 18:42:24 Press CTRL-A Z for help on special keys +CME ERROR: 10
The output of "systemctl status ModemManager" has changed: ModemManager.service - Modem Manager Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled) Active: active (running) since Wed 2014-05-21 18:46:21 CEST; 3s ago Main PID: 3340 (ModemManager) CGroup: /system.slice/ModemManager.service └─3340 /usr/sbin/ModemManager May 21 18:46:21 localhost.localdomain ModemManager[3340]: <info> ModemManager (version 1.2.0-1.fc20) starting... May 21 18:46:21 localhost.localdomain systemd[1]: Started Modem Manager. May 21 18:46:24 localhost.localdomain ModemManager[3340]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin May 21 18:46:24 localhost.localdomain ModemManager[3340]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0': not supported by any plugin May 21 18:46:25 localhost.localdomain ModemManager[3340]: [/dev/cdc-wdm0] Queried max control message size: 512 May 21 18:46:25 localhost.localdomain ModemManager[3340]: [/dev/cdc-wdm0] No transaction matched in received message May 21 18:46:25 localhost.localdomain ModemManager[3340]: <info> Creating modem with plugin 'Generic' and '3' ports May 21 18:46:25 localhost.localdomain ModemManager[3340]: <info> Modem for device at '/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4' successfully created May 21 18:46:25 localhost.localdomain ModemManager[3340]: [/dev/cdc-wdm0] Queried max control message size: 512 So it's no longer complaining about the SIM card missing. The mobile broadband connection is still not listed in the NetworkManager applet, though.
So CME ERROR: 10 is "SIM not inserted". So the modem is at least being consistent :) If the modem reports that the SIM is not inserted, there's not much that ModemManager or NetworkManager can do; the modem simply doesn't think there is a SIM and it will not connect to the network. However, you said that the output has changed; so lets check that out: mmcli -L That will return one or more modems; look at the number on the end of each modem. For that modem, type: mmcli -m <number> and lets take a look at the output to see what state the modem is now in. For example: $ mmcli -L Found 2 modems: /org/freedesktop/ModemManager1/Modem/1 [Sierra Wireless, Incorporated] USB 306 /org/freedesktop/ModemManager1/Modem/0 [HP] HP hs2350 HSPA+ MobileBroadband $ mmcli -m 1 ... ------------------------- Status | lock: 'unknown' | unlock retries: 'unknown' | state: 'failed' | failed reason: 'sim-missing' | power state: 'on' | access tech: 'unknown' | signal quality: '0' (cached) ... This modem reports the SIM card missing.
/org/freedesktop/ModemManager1/Modem/0 (device id '11fbc76eb2f51d02e3b7fc8c7623856b10539f96') ------------------------- Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:A001]' | revision: 'FIH7160_V1.1_MODEM_01.1349.12' | supported: 'gsm-umts, lte' | current: 'gsm-umts, lte' | equipment id: '013937000279826' ------------------------- System | device: '/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4' | drivers: 'cdc_acm, cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'wwp0s20u4 (net), cdc-wdm0 (mbim), ttyACM0 (at)' ------------------------- Numbers | own : 'unknown' ------------------------- Status | lock: 'unknown' | unlock retries: 'unknown' | state: 'failed' | failed reason: 'sim-missing' | power state: 'low' | access tech: 'unknown' | signal quality: '0' (cached) ------------------------- Modes | supported: 'allowed: 2g, 3g, 4g; preferred: none' | current: 'allowed: any; preferred: none' ------------------------- Bands | supported: 'unknown' | current: 'unknown' ------------------------- IP | supported: 'ipv4, ipv6, ipv4v6' ------------------------- SIM | path: 'none' ------------------------- Bearers | paths: 'none'
Hi, I'm seeing a similar problem with my Sierra 320U. This device has previously worked with ModemManager, but has broken since around when I started using the f20-gnome-3-12 copr repo. I can still use the card by running dhclient against its interface. I see a similar output to Comment 10 above: ~ ᐅ systemctl status ModemManager -l ModemManager.service - Modem Manager Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled) Active: active (running) since Fri 2014-06-06 21:51:44 EST; 1h 22min ago Main PID: 740 (ModemManager) CGroup: /system.slice/ModemManager.service └─740 /usr/sbin/ModemManager Jun 06 21:51:44 laphroaig systemd[1]: Starting Modem Manager... Jun 06 21:51:44 laphroaig ModemManager[740]: <info> ModemManager (version 1.2.0-1.fc20) starting... Jun 06 21:51:44 laphroaig systemd[1]: Started Modem Manager. Jun 06 21:51:46 laphroaig ModemManager[740]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin Jun 06 21:51:46 laphroaig ModemManager[740]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0': not supported by any plugin Jun 06 21:52:02 laphroaig ModemManager[740]: <info> Creating modem with plugin 'Generic' and '1' ports Jun 06 21:52:02 laphroaig ModemManager[740]: <warn> Could not grab port (tty/ttyS0): 'Cannot add port 'tty/ttyS0', unhandled serial type' Jun 06 21:52:02 laphroaig ModemManager[740]: <warn> Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port
Similar problem with a Huawei K3765 I can manually connect, but it doesn't show up in Gnome's list of available network connections (even when connected!) After powercycle: $ systemctl status ModemManager ModemManager.service - Modem Manager Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled) Active: active (running) since Thu 2014-09-11 11:43:23 SAST; 4h 11min ago Main PID: 657 (ModemManager) CGroup: /system.slice/ModemManager.service └─657 /usr/sbin/ModemManager Sep 11 15:54:27 klatch.company.net ModemManager[657]: <warn> (ttyUSB2): port attributes not fully set Sep 11 15:54:27 klatch.company.net ModemManager[657]: <warn> (ttyUSB1): port attributes not fully set Sep 11 15:54:28 klatch.company.net ModemManager[657]: <warn> (ttyUSB0): port attributes not fully set Sep 11 15:54:31 klatch.company.net ModemManager[657]: <warn> (ttyUSB2): port attributes not fully set Sep 11 15:54:31 klatch.company.net ModemManager[657]: <warn> (ttyUSB1): port attributes not fully set Sep 11 15:54:41 klatch.company.net ModemManager[657]: <info> Creating modem with plugin 'Huawei' and '4' ports Sep 11 15:54:41 klatch.company.net ModemManager[657]: <warn> (ttyUSB2): port attributes not fully set Sep 11 15:54:41 klatch.company.net ModemManager[657]: <info> Modem for device at '/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.2' successfully created Sep 11 15:54:41 klatch.company.net ModemManager[657]: Error while checking ^SYSCFGEX format: Unknown error Sep 11 15:54:46 klatch.company.net ModemManager[657]: <info> Modem: state changed (unknown -> disabled) Manually connect: $ mmcli --modem '/org/freedesktop/ModemManager1/Modem/3' --simple-connect="apn=internet" successfully connected the modem $ systemctl status ModemManager ModemManager.service - Modem Manager Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled) Active: active (running) since Thu 2014-09-11 11:43:23 SAST; 4h 12min ago Main PID: 657 (ModemManager) CGroup: /system.slice/ModemManager.service └─657 /usr/sbin/ModemManager Sep 11 15:56:03 klatch.company.net ModemManager[657]: <info> Simple connect state (5/8): Register Sep 11 15:56:03 klatch.company.net ModemManager[657]: <info> Simple connect state (6/8): Bearer Sep 11 15:56:03 klatch.company.net ModemManager[657]: <info> Simple connect state (7/8): Connect Sep 11 15:56:03 klatch.company.net ModemManager[657]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: state changed (registered -> connecting) Sep 11 15:56:03 klatch.company.net ModemManager[657]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: signal quality updated (60) Sep 11 15:56:03 klatch.company.net ModemManager[657]: <warn> (ttyUSB0): port attributes not fully set Sep 11 15:56:03 klatch.company.net ModemManager[657]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: access technology changed (unknown -> umts) Sep 11 15:56:03 klatch.company.net ModemManager[657]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: state changed (connecting -> connected) Sep 11 15:56:03 klatch.company.net ModemManager[657]: <info> Simple connect state (8/8): All done Sep 11 15:56:06 klatch.company.net ModemManager[657]: <info> Modem /org/freedesktop/ModemManager1/Modem/3: signal quality updated (64) No "Mobile Broadband" in gnome control center. Bluetooth connections to my cellphone don't show up as a network connection either. I can send files to my cellphone, but not connect through it. ------------------------- Hardware | manufacturer: 'huawei' | model: 'K3765' | revision: '11.126.03.06.00' | supported: 'gsm-umts' | current: 'gsm-umts' | equipment id: '358880030011657' ------------------------- System | device: '/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.2' | drivers: 'option1, cdc_ether' | plugin: 'Huawei' | primary port: 'ttyUSB2' | ports: 'ttyUSB0 (at), ttyUSB1 (qcdm), ttyUSB2 (at), wwp0s29u1u2i1 (net)' ------------------------- Numbers | own : 'unknown' ------------------------- Status | lock: 'none' | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)' | state: 'connected' | power state: 'on' | access tech: 'umts' | signal quality: '80' (recent) ------------------------- Modes | supported: 'allowed: 2g, 3g; preferred: none | allowed: 2g, 3g; preferred: 2g | allowed: 2g, 3g; preferred: 3g | allowed: 2g; preferred: none | allowed: 3g; preferred: none' | current: 'allowed: 2g, 3g; preferred: none' ------------------------- Bands | supported: 'unknown' | current: 'unknown' ------------------------- IP | supported: 'ipv4, ipv6'
Downgrading networkmanager from NetworkManager 0.9.9.1-4.git20140319.fc20 to 0.9.9.0-20.git20131003.fc20 fixed my problem.
Never downgraded a package before. How did you do that, Berend?
In my case: 1. download it (from Fedora ftp sites) 2. rpm -Uvh package.rpm [package.rpm ...] --oldpackage In general you wanna avoid mixing rpm and yum/dnf, but hey! Packages you'll need: libnm-gtk-0.9.9.0-7.git20131028.fc20.x86_64.rpm ModemManager-1.1.0-2.git20130913.fc20.x86_64.rpm ModemManager-glib-1.1.0-2.git20130913.fc20.x86_64.rpm NetworkManager-0.9.9.0-20.git20131003.fc20.x86_64.rpm network-manager-applet-0.9.9.0-7.git20131028.fc20.x86_64.rpm NetworkManager-glib-0.9.9.0-20.git20131003.fc20.x86_64.rpm nm-connection-editor-0.9.9.0-7.git20131028.fc20.x86_64.rpm The networkmanager downgrade in particular fixed *my* problem, but it will moan at you if you don't downgrade the others too. Note: dnf or yum update will re-upgrade them. I don't know how to hold a .rpm.
I can confirm that downgrading as mentioned in comment #15 solves the problem. For comment #16 and comment #17:- As of this writing, I did not need to download the packages manually and install using rpm. The required package versions were still available in the Fedora and Updates repositories, so su -c 'dnf downgrade NetworkManager NetworkManager-glib ModemManager ModemManager-glib libnm-gtk nm-connection-editor' worked for me, (although I did have to downgrade more than once to get to the required versions). network-manager-applet was not required. > dnf or yum update will re-upgrade them. I don't know how to hold a .rpm. In the repo file for rhughes-f20-gnome-3-12 (in /etc/yum.repos.d/) add the line exclude=*NetworkManager*,*ModemManager*,*libnm*,*nm-connection-editor* to prevent these packages from being upgraded.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.