Networkmanager 1.0.12-1 -> no Wireless connection

aligator · 2016-04-02 14:20:49

hi

I upgraded to Networkmanager 1.0.12-1. After this I did't get any wireless connection.
I have not tested LAN, since I have no LAN here.

After downgrading to 1.0.10-2 it works again.

I have:
4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 x86_64 GNU/Linux

WorMzy · 2016-04-02 14:43:54

Soooo, are you just telling us, or do you need help debugging the problem? If it's the latter, please include the relevant logs.

Mod note: Moving to networking.

Revelation60 · 2016-04-02 18:38:50

My wireless network connection disappeared as well. It is not a problem with the driver: wifi-menu works perfectly (you can use this as a workaround).

Card: Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Driver: 8192cu-dkms from AUR

Here is an output of journalctl -u NetworkManager (normal looking):

Apr 02 20:31:05 PC_NMG systemd[1]: Starting Network Manager...
Apr 02 20:31:05 PC_NMG systemd[1]: Started Network Manager.
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  NetworkManager (version 1.0.12) is starting...
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Read config: /etc/NetworkManager/NetworkManager.conf
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded settings plugin keyfile: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  keyfile: new connection /etc/NetworkManager/system-connections/SKYNET 1 (8b02e45e-ad2b-40a5-81b7-722975a59758,"SKYNET 1")
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  monitoring kernel firmware directory '/usr/lib/firmware'.
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMVxlanFactory (internal)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMVlanFactory (internal)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMVethFactory (internal)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMTunFactory (internal)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMMacvlanFactory (internal)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMInfinibandFactory (internal)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMGreFactory (internal)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMEthernetFactory (internal)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMBridgeFactory (internal)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMBondFactory (internal)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/libnm-device-plugin-wwan.so)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/libnm-device-plugin-adsl.so)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/libnm-device-plugin-team.so)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/libnm-device-plugin-wifi.so)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  WiFi enabled by radio killswitch; enabled by state file
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  WWAN enabled by radio killswitch; enabled by state file
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  WiMAX enabled by radio killswitch; enabled by state file
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  Networking is enabled by state file
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  (enp3s0): new Ethernet device (carrier: OFF, driver: 'alx', ifindex: 2)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  (enp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  keyfile: add connection in-memory (7a76fff9-90c2-464a-9f8a-8c04c3228e6b,"Wired connection 1")
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  (enp3s0): created default wired connection 'Wired connection 1'
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  (lo): link connected
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1)
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  (enp0s20u5): driver supports SSID scans (scan_capa 0x3F).
Apr 02 20:31:05 PC_NMG NetworkManager[304]: <info>  (enp0s20u5): using WEXT for WiFi device control
Apr 02 20:31:11 PC_NMG NetworkManager[304]: <info>  startup complete

Last edited by Revelation60 (2016-04-03 07:08:14)

misiunt · 2016-04-02 19:44:45

I had a similiar issue after upgrading networkmanager to 1.0.12-1. My usb-wifi connection disappeared, the pci-connection worked still properly with networkmanager. I was able to start the usb-wifi connection with ip link or wifi-menu but networkmanager couldn't start it. After downgrading to 1.0.10-2 both connections work again with networkmanager.

melog · 2016-04-03 02:05:03

I have the same problem, downgrading solved the issue

Edit: Sorry, this is my Wifi-Adapter:

Bus 002 Device 005: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter

This are the log entries before downgrading:

Apr 03 03:04:23 arch NetworkManager[618]: <info> WiFi enabled by radio killswitch; enabled by state file
Apr 03 03:04:23 arch NetworkManager[618]: <info> WWAN enabled by radio killswitch; enabled by state file
Apr 03 03:04:23 arch NetworkManager[618]: <info> WiMAX enabled by radio killswitch; enabled by state file
Apr 03 03:04:23 arch NetworkManager[618]: <info> Networking is enabled by state file
Apr 03 03:04:23 arch NetworkManager[618]: <info> (wlp0s29u1u7): driver does not support SSID scans (scan_capa 0x00).
Apr 03 03:04:23 arch NetworkManager[618]: <info> (wlp0s29u1u7): using WEXT for WiFi device control
Apr 03 03:04:23 arch NetworkManager[618]: <info> (enp5s0): new Ethernet device (carrier: OFF, driver: 'r8169', ifindex: 2)
Apr 03 03:04:23 arch NetworkManager[618]: <info> (enp5s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 03 03:04:23 arch NetworkManager[618]: <info> (lo): link connected
Apr 03 03:04:23 arch NetworkManager[618]: <info> (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1)
Apr 03 03:04:29 arch NetworkManager[618]: <info> startup complete
Apr 03 03:05:05 arch NetworkManager[618]: <info> (wlan0): driver does not support SSID scans (scan_capa 0x00).
Apr 03 03:05:05 arch NetworkManager[618]: <info> (wlan0): using WEXT for WiFi device control
Apr 03 03:05:17 arch NetworkManager[618]: <info> (wlan0): driver does not support SSID scans (scan_capa 0x00).
Apr 03 03:05:17 arch NetworkManager[618]: <info> (wlan0): using WEXT for WiFi device control
Apr 03 03:05:30 arch NetworkManager[618]: <info> (wlan0): driver does not support SSID scans (scan_capa 0x00).
Apr 03 03:05:30 arch NetworkManager[618]: <info> (wlan0): using WEXT for WiFi device control
Apr 03 03:05:39 arch NetworkManager[618]: <info> (wlan0): using nl80211 for WiFi device control
Apr 03 03:05:39 arch NetworkManager[618]: <info> (wlan0): driver supports Access Point (AP) mode
Apr 03 03:05:39 arch NetworkManager[618]: <info> (wlan0): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'rt2800usb', ifindex: 7)
Apr 03 03:05:39 arch NetworkManager[618]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.7/4-1.7:1.0/ieee80211/phy0/rfkill0) (driver rt2800usb)
Apr 03 03:05:39 arch NetworkManager[618]: <info> (wlan0): interface index 7 renamed iface from 'wlan0' to 'wlp0s29u1u7'
Apr 03 03:05:39 arch NetworkManager[618]: <info> (wlp0s29u1u7): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 03 03:05:39 arch NetworkManager[618]: <info> wpa_supplicant running
Apr 03 03:05:39 arch NetworkManager[618]: <info> (wlp0s29u1u7): supplicant interface state: init -> starting
Apr 03 03:05:39 arch NetworkManager[618]: <info> (wlp0s29u1u7) supports 4 scan SSIDs
Apr 03 03:05:39 arch NetworkManager[618]: <info> (wlp0s29u1u7): supplicant interface state: starting -> ready
Apr 03 03:05:39 arch NetworkManager[618]: <info> (wlp0s29u1u7): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Apr 03 03:05:40 arch NetworkManager[618]: <info> (wlp0s29u1u7): supplicant interface state: ready -> inactive
Apr 03 03:05:48 arch NetworkManager[618]: <info> (wlp0s29u1u7): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Apr 03 03:05:48 arch NetworkManager[618]: <warn> (wlp0s29u1u7): failed to disable userspace IPv6LL address handling
Apr 03 03:05:48 arch NetworkManager[618]: <info> radio killswitch /sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.7/4-1.7:1.0/ieee80211/phy0/rfkill0 disappeared
Apr 03 03:06:08 arch NetworkManager[618]: <info> (wlan0): driver does not support SSID scans (scan_capa 0x00).
Apr 03 03:06:08 arch NetworkManager[618]: <info> (wlan0): using WEXT for WiFi device control

Last edited by melog (2016-04-03 15:11:28)

bodysativa · 2016-04-03 05:38:59

I just had the same issue. Downgrading also helped for me, thanks for this topic.

32idea · 2016-04-03 05:52:31

me too, x86_64,usb-wifi don't connect，downgrading to 1.0.10-2 it works

lsusb
Bus 002 Device 004: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter

Sorry，my english is not better to describe this question , next time , I don't do this.

Last edited by 32idea (2016-04-03 06:34:22)

jasonwryan · 2016-04-03 06:04:21

So rather than an endless stream of empty "me too" posts, someone could post some relevant information:

Card, driver, journal entries, etc. The sort of thing that might triangulate the issue and lead to a productive outcome, like a bug report...

misiunt · 2016-04-03 12:26:51

OK, I try to deliver some relevant information:
-Software:
KDE-Plasma-Version 5.6.1
KDE-Frameworks-Version 5.20.0
Qt-Version 5.6.0
Kernel-Version 4.4.5-1-ARCH 64-bit
-Hardware:
i5-5200U CPU
8 GiB Memory
WiFi Adapter:
1. PCI WiFi - 03:00.0 Qualcomm Atheros QCA6174 802.11ac - Driver ath10k_pci
2. USB WiFi - Bus 002 Device 003: ID 0b05:17ab ASUSTek Computer, Inc USB-N13 802.11n Network Adapter (rev. B1) [Realtek RTL8192CU] - Driver 8192cu

The PCI-WiFi uses the regular kernel ath10k_pci and has obviously no problems with the new 1.0.12-1 version of networkmanager, but the usb one has.
The question of the driver for the USB-Adapter is sligtly more complex. Since the original kernel driver is broken I use the 8192cu provided by the AUR Package 8192cu-dkms.
The driver is loaded:

# lsmod | grep 8192
8192cu                532480  0
mei                      81920  1 mei_me
usbcore               196608  9 btusb,uvcvideo,rtsx_usb,ehci_hcd,ehci_pci,usbhid,8192cu,xhci_hcd,xhci_pci

but there is a strange (at least for me) message from

# dmesg -w | grep 8192
usbcore: registered new interface driver rtl8192cu                                                                                                                            
rtl8192cu 2-2:1.0 enp0s20u2: renamed from wlan0

It is strange because rtl8192cu is the original broken kernel driver I blacklisted i /etc/modprobe.d.

There are no any further messages regarding neither a *8192* driver nor the enp0s20u2 interface. Networkmanager starts the PCI-WiFi without any issues but the USB-one can only be started via iw link and/or wifi-menu. After I started it with wifi-menue and restarted networkmanager the nm-applet shows the enp0s20u2 interface but it is impossible to connect to it. A dialog generated by KDED5 /KDEINIT5] pops up and requires a passwort to access the wifi-network. You can enter whatever you want. Nothing is accepted and the messages "no password has been entered" and "interface enp0s20u2 will be deactivated" appear.
Thats the story :(
The only workaround I found was to downgrade networkmanager to the previous version.

mard · 2016-04-03 12:48:41

Hello. I have the same problem with NetworkManager and I can confirm that downgrade to 1.0.10 worked for me.

I am rather beginner Linux user but perhaps I can help with providing the logs.

Device: Realtek RTL8192CUS 802.11 b/g/n WLAN Adapter
Driver: rtl8192cu

journalctl -u NetworkManager entries before and after downgrade. Pasting the parts where logs start to differ:

NetworkManager 1.0.12-1: (doesn't work)

kwi 03 13:59:13 sunjammer NetworkManager[89]: <info>  (wlan0): driver supports SSID scans (scan_capa 0x3F).
kwi 03 13:59:13 sunjammer NetworkManager[89]: <info>  (wlan0): using WEXT for WiFi device control
kwi 03 13:59:13 sunjammer NetworkManager[89]: <info>  startup complete
(then empty)

NetworkManager 1.0.10-2: (works)

kwi 03 14:02:04 sunjammer NetworkManager[201]: <info>  (wlan0): driver supports SSID scans (scan_capa 0x3F).
kwi 03 14:02:04 sunjammer NetworkManager[201]: <info>  (wlan0): using WEXT for WiFi device control
kwi 03 14:02:04 sunjammer NetworkManager[201]: <info>  (wlan0): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'rtl8192cu', ifindex: 2)
kwi 03 14:02:04 sunjammer NetworkManager[201]: <info>  (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
kwi 03 14:02:05 sunjammer NetworkManager[201]: <info>  wpa_supplicant running
kwi 03 14:02:05 sunjammer NetworkManager[201]: <info>  (wlan0) supports 1 scan SSIDs
kwi 03 14:02:05 sunjammer NetworkManager[201]: <info>  (wlan0): supplicant interface state: starting -> ready
kwi 03 14:02:05 sunjammer NetworkManager[201]: <info>  startup complete
kwi 03 14:02:05 sunjammer NetworkManager[201]: <info>  (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
kwi 03 14:02:07 sunjammer NetworkManager[201]: <info>  (wlan0): supplicant interface state: ready -> inactive
(then logs connecting to my known network, then empty)

Last edited by mard (2016-04-03 13:11:08)

promarbler14 · 2016-04-03 15:10:55

I have the same issue as everyone else above. Downgrading NetworkManager and libnm-glib fixed it.

(Driver is r8712u, as seen in the second text spew.)

It should be noted that I have to reload NM and the driver after every time I suspend...

lsusb -v :

Bus 005 Device 005: ID 050d:945a Belkin Components F7D1101 v1 Basic Wireless Adapter [Realtek RTL8188SU]
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x050d Belkin Components
  idProduct          0x945a F7D1101 v1 Basic Wireless Adapter [Realtek RTL8188SU]
  bcdDevice            2.00
  iManufacturer           1 Manufacturer Realtek 
  iProduct                2 Basic Wireless USB Adapter
  iSerial                 3 00e04c000001
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           46
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           4
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x0d  EP 13 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0000
  (Bus Powered)

lshw (relevant portion) :

              *-usb
                   description: Wireless interface
                   product: Basic Wireless USB Adapter
                   vendor: Manufacturer Realtek
                   physical id: 3
                   bus info: usb@5:3
                   logical name: wlp0s29f7u3
                   version: 2.00
                   serial: [REMOVED]
                   capabilities: usb-2.00 ethernet physical wireless
                   configuration: broadcast=yes driver=r8712u ip=[REMOVED] maxpower=500mA multicast=yes speed=480Mbit/s wireless=IEEE 802.11bgn

(edit)

Here is what happens if you try to start it from the cmd-line:

# nmcli c up e4ad7d74-3100-4e4a-bf52-cf00c1a35632
Error: Connection activation failed: No suitable device found for this connection.

The nm-applet doesn't even acknowledge the existence of any wireless devices; it proceeds to assume it's connecting to ethernet.

Last edited by promarbler14 (2016-04-03 15:19:43)

jpcima · 2016-04-03 15:33:23

Same problem, and same logs, except my wifi hardware is 8086:0085 running with the iwlagn driver.
Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)

I am on MATE and using nm-applet. Downgrading to 1.0.10 has also solved my problem.
I temporarily uploaded packages for downgrading if interested:
https://lx.cimalando.eu/arch/temp/libnm … pkg.tar.xz
https://lx.cimalando.eu/arch/temp/netwo … pkg.tar.xz

WorMzy · 2016-04-03 16:05:17

jpcima, don't take this the wrong way, but why should anyone trust those packages? The packages are available on the Arch Linux Archive, so there's no need to redistribute them yourself.

jpcima · 2016-04-03 19:35:36

WorMzy wrote:

jpcima, don't take this the wrong way, but why should anyone trust those packages? The packages are available on the Arch Linux Archive, so there's no need to redistribute them yourself.

I ignored something like this existed, so something new has been learnt today.
There is no malicious intent behind this, I share with others things that are useful to me. Since I suppose it is useless, I will remove it.

phireis · 2016-04-05 12:30:40

My wifi stopped working after updating networkmanager to 1.0.12-1 too, with the USB wifi adapter:
0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter
Driver: r8712u.
Downgrading from networkmanager-1.0.12-1 to 1.0.10-2 solved here too.
4.4.5-1-ARCH x86_64

Last edited by phireis (2016-04-05 12:52:00)

V1del · 2016-04-05 13:02:17

As most of you are running on staging and/or out-of-tree drivers, chances are that they don't really behave in a way networkmanager expects them to. The most likely culprit IMO would be https://cgit.freedesktop.org/NetworkMan … 7e4a0ce3f7 I think the drivers don't really put the devices into the correct management state. Take this with a grain of salt, as I haven't had to use my r8712u device in a while and didn't do extensive testing

Last edited by V1del (2016-04-05 13:16:05)

dicaiopolis · 2016-04-06 13:53:48

Hi there,

Downagrading to 1.0.10-2 didn't work for me. I've downgraded both networkmanager and libnm-glib, but I still get the same error and no wifi connection:

dmesg | grep r8188eu
[   23.260211] r8188eu: module is from the staging directory, the quality is unknown, you have been warned.
[   23.293107] usbcore: registered new interface driver r8188eu
[   23.496895] Error: Driver 'r8188eu' is already registered, aborting...

iwconfig
eth0      no wireless extensions.

wlan0     unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Auto  Frequency=2.412 GHz  Access Point: Not-Associated   
          Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

sudo ip link set wlan0 up
RTNETLINK answers: Operation not permitted

Any ideas about what's going on? Any tips?

Thanks a lot.

Nordicruler · 2016-04-07 03:36:29

Same issue here. Downgrading to networkmanager-1.0.10 and it works again
Realtek driver 8188eu from here https://github.com/lwfinger/rtl8188eu

I use this driver in several other dists and always works good.

ttll · 2016-04-12 20:45:11

reporting in from archlinuxarm on raspberry pi 2

my device

Bus 001 Device 004: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter

worked fine initially, but after upgrade to networkmanager 1.0.12-1 the device was not listed in nmcli/nmtui

[root@alarmpi ~]# journalctl -b -3 | grep -i wlan
Apr 12 20:01:56 alarmpi NetworkManager[203]: <info>  (wlan0): driver supports SSID scans (scan_capa 0x3F).
Apr 12 20:01:56 alarmpi NetworkManager[203]: <info>  (wlan0): using WEXT for WiFi device control

after downgrade to 1.0.10-2 everything works fine again

Apr 12 20:26:49 alarmpi NetworkManager[195]: <info>  (wlan0): using WEXT for WiFi device control
Apr 12 20:26:49 alarmpi NetworkManager[195]: <info>  (wlan0): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'r8712u', ifindex: 3)
Apr 12 20:26:49 alarmpi NetworkManager[195]: <info>  (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 12 20:26:49 alarmpi kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 12 20:26:50 alarmpi kernel: r8712u 1-1.4:1.0 wlan0: 1 RCR=0x153f00e
Apr 12 20:26:50 alarmpi kernel: r8712u 1-1.4:1.0 wlan0: 2 RCR=0x553f00e
Apr 12 20:26:50 alarmpi kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 12 20:26:50 alarmpi kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 12 20:26:51 alarmpi wpa_supplicant[234]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Apr 12 20:26:51 alarmpi NetworkManager[195]: <info>  (wlan0) supports 1 scan SSIDs
Apr 12 20:26:51 alarmpi NetworkManager[195]: <info>  (wlan0): supplicant interface state: starting -> ready
Apr 12 20:26:51 alarmpi NetworkManager[195]: <info>  (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Apr 12 20:26:51 alarmpi kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 12 20:26:54 alarmpi wpa_supplicant[234]: wlan0: Reject scan trigger since one is already pending
Apr 12 20:27:01 alarmpi NetworkManager[195]: <info>  (wlan0): supplicant interface state: ready -> inactive
Apr 12 20:27:01 alarmpi NetworkManager[195]: <info>  (wlan0): Activation: starting connection (obscured)

STUART · 2016-04-13 20:28:16

I'm having the same problem with my wifi adapter, which is using the rtl8812au-dkms-git driver.

Here are the corresponding bugs I've filed upstream:

https://github.com/lwfinger/rtl8188eu/issues/171
https://github.com/gnab/rtl8812au/issues/81

For users of the rtl8188eu-git driver, the upstream maintainer has suggested using the v4.1.8_9499 branch of the repo, which may address the issue potentially introduced by the patch V1del highlighted above.

Last edited by STUART (2016-04-13 20:29:14)

melog · 2016-04-21 12:38:31

Did anybody test the new Networkmanager in testing ? Is the bug fixed?

Thanks for filing the bugreports btw

Blitz67 · 2016-04-22 16:40:33

melog wrote:

Did anybody test the new Networkmanager in testing ? Is the bug fixed?

I have installed this version, in my case it works well.

Device:

RTL8191S WLAN Adapter

dmesg | grep -i rtl

[ 14.346640] r8712u: register rtl8712_netdev_ops to netdev_ops
[ 15.030101] usb 4-3: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"

systemctl status NetworkManager.service

● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
Active: active (running) since Пт 2016-04-22 19:27:05 MSK; 10min ago
Main PID: 355 (NetworkManager)
Tasks: 4 (limit: 512)
CGroup: /system.slice/NetworkManager.service
├─355 /usr/bin/NetworkManager --no-daemon
└─487 /usr/bin/dhclient -d -q -sf /usr/lib/networkmanager/nm-dhcp-helper -pf /var/run/dhclient-wlp0s18f2u3.pid -lf /var/lib/NetworkManager/dhclient-4
63ba15b-51ee-4c0f-a875-ec30ffc69124-wlp0s18f2u3.lease -cf /var/lib/NetworkManager/dhclient-wlp0s18f2u3.conf wlp0s18f2u3
апр 22 19:27:26 mini-pc NetworkManager[355]: <info> [1461342446.4102] dhcp4 (wlp0s18f2u3): state changed unknown -> bound
апр 22 19:27:26 mini-pc NetworkManager[355]: <info> [1461342446.4140] device (wlp0s18f2u3): state change: ip-config -> ip-check (reason 'none') [70 80 0]
апр 22 19:27:26 mini-pc NetworkManager[355]: <info> [1461342446.4154] device (wlp0s18f2u3): state change: ip-check -> secondaries (reason 'none') [80 90 0]
апр 22 19:27:26 mini-pc NetworkManager[355]: <info> [1461342446.4170] device (wlp0s18f2u3): state change: secondaries -> activated (reason 'none') [90 100 0]
апр 22 19:27:26 mini-pc NetworkManager[355]: <info> [1461342446.4175] manager: NetworkManager state is now CONNECTED_LOCAL
апр 22 19:27:31 mini-pc dhclient[487]: bound to 192.168.0.233 -- renewal in 34690 seconds.
апр 22 19:27:31 mini-pc NetworkManager[355]: <info> [1461342451.5647] manager: NetworkManager state is now CONNECTED_GLOBAL
апр 22 19:27:31 mini-pc NetworkManager[355]: <info> [1461342451.5651] policy: set 'Homenet' (wlp0s18f2u3) as default for IPv4 routing and DNS
апр 22 19:27:31 mini-pc NetworkManager[355]: <info> [1461342451.5654] dns-mgr: Writing DNS information to /usr/bin/resolvconf
апр 22 19:27:37 mini-pc NetworkManager[355]: <info> [1461342457.3974] device (wlp0s18f2u3): Activation: successful, device activated.

Last edited by Blitz67 (2016-04-22 16:53:29)

egeus · 2016-04-26 11:57:41

Same for me. I just did an upgrade to the testing version 1.2.0-2 with

sudo pacman -U networkmanager-1.2.0-2-x86_64.pkg.tar.xz

and a restart of NetworkManager and it worked fine.

apastuszak · 2016-04-30 04:47:50

I am having the same problem on NetworkManager 1.2.0-3. The Wireless NIC is showing up as a wired NIC and doesn't get a connection. The downgrade to 1.0.10-2 restores wireless.

I'm on a ThinkPad T440 with Intel Wireless. Has anyone found a fix? I'll post logs in the morning.

bonsairoot · 2016-04-30 12:51:17

apastuszak wrote:

I am having the same problem on NetworkManager 1.2.0-3. The Wireless NIC is showing up as a wired NIC and doesn't get a connection. The downgrade to 1.0.10-2 restores wireless.
I'm on a ThinkPad T440 with Intel Wireless. Has anyone found a fix? I'll post logs in the morning.

Same here. I downgraded as well.
I'm on a xps 13 9350 (late 2015 edition). Broadcom wireless.

Arch Linux

#1 2016-04-02 14:20:49

Networkmanager 1.0.12-1 -> no Wireless connection

#2 2016-04-02 14:43:54

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#3 2016-04-02 18:38:50

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#4 2016-04-02 19:44:45

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#5 2016-04-03 02:05:03

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#6 2016-04-03 05:38:59

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#7 2016-04-03 05:52:31

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#8 2016-04-03 06:04:21

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#9 2016-04-03 12:26:51

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#10 2016-04-03 12:48:41

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#11 2016-04-03 15:10:55

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#12 2016-04-03 15:33:23

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#13 2016-04-03 16:05:17

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#14 2016-04-03 19:35:36

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#15 2016-04-05 12:30:40

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#16 2016-04-05 13:02:17

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#17 2016-04-06 13:53:48

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#18 2016-04-07 03:36:29

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#19 2016-04-12 20:45:11

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#20 2016-04-13 20:28:16

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#21 2016-04-21 12:38:31

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#22 2016-04-22 16:40:33

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#23 2016-04-26 11:57:41

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#24 2016-04-30 04:47:50

Re: Networkmanager 1.0.12-1 -> no Wireless connection

#25 2016-04-30 12:51:17

Re: Networkmanager 1.0.12-1 -> no Wireless connection

Board footer