Arch Linux

ruddy32

Member

Registered: 2016-02-29

Posts: 27

[Wifi] wpa_supplicant could not read interface p2p-dev-wlp4s0 (solved)

Hi,

After configuring wifi acces point in wpa configuration, wpa_supplicant show this information

wpa_supplicant : could not read interface p2p-dev-wlp4s0 flags: no such device

The system is configured with NetworkManager.

This ticket is relative to the same problem with netctl.

How to fix interface name with P2P ? or disable P2P ?

Journal logs :

# journalctl -b --no-pager|grep iwlwifi
Mar 14 19:06:47 lt002 kernel: iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
Mar 14 19:06:47 lt002 kernel: iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
Mar 14 19:06:47 lt002 kernel: iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
Mar 14 19:06:47 lt002 kernel: iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
Mar 14 19:06:47 lt002 kernel: iwlwifi 0000:04:00.0: Unsupported splx structure
Mar 14 19:06:47 lt002 kernel: iwlwifi 0000:04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm
Mar 14 19:06:48 lt002 kernel: iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
Mar 14 19:06:48 lt002 kernel: iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
Mar 14 19:06:48 lt002 kernel: iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
Mar 14 19:06:48 lt002 kernel: iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
Mar 14 19:06:48 lt002 kernel: iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0
Mar 14 19:06:51 lt002 kernel: iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
Mar 14 19:06:51 lt002 kernel: iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
Mar 14 19:06:51 lt002 kernel: iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
Mar 14 19:06:51 lt002 NetworkManager[453]: <info>  rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
Mar 14 19:06:51 lt002 NetworkManager[453]: <info>  (wlp4s0): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'iwlwifi', ifindex: 3)
Mar 14 19:06:51 lt002 kernel: iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
Mar 14 19:06:51 lt002 kernel: iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
Mar 14 19:06:51 lt002 kernel: iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
Mar 14 20:13:33 lt002 kernel: iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
Mar 14 20:13:33 lt002 kernel: iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
Mar 14 20:13:33 lt002 kernel: iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
Mar 14 20:13:33 lt002 kernel: iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
Mar 14 20:13:33 lt002 kernel: iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
Mar 14 20:13:33 lt002 kernel: iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected

wpa_supplicant return :

# wpa_supplicant -B -i wlp4s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
Could not read interface [b]p2p-dev-[/b]wlp4s0 flags: No such device
nl80211: Could not set interface '[b]p2p-dev-[/b]wlp4s0' UP
nl80211: deinit ifname=[b]p2p-dev-[/b]wlp4s0 disabled_11b_rates=0
[b]p2p-dev-[/b]wlp4s0: Failed to initialize driver interface
P2P: Failed to enable P2P Device interface

Where p2p-dev- comes from? Is it a bug from iwlwifi? Or a mistake from configuration files?

A new firmware is available for Intel Wireless 8260 : iwlwifi-8000C-21.ucode. How to make this firmware loaded at boot time? (Currently the system try to load iwlwifi-8000C-19.ucode)

I guess this post match better with kernel & hardware topic.

Last edited by ruddy32 (2016-03-22 08:56:02)

ruddy32

Member

Registered: 2016-02-29

Posts: 27

Re: [Wifi] wpa_supplicant could not read interface p2p-dev-wlp4s0 (solved)

I solve the problem after resetting the dhcp server nd the acces point, and then removing the wireless interface from the laptop.

I don't know what's going wrong. It works evenif I still have the RSA error message in the log.