Gnome Network displays No Wif P2P Adapter

Gnome network display can find a Wi-Fi P2P adapter. How do I install a Wi-Fi P2P adapter?

1 Like

First of all you need WiFi running on your device.

Second you will need a device in your network who knows miracast. Just then you will get a list of available video sinks.

Important:
This is an experimental implementation of Wi-Fi Display (aka Miracast).

2 Likes

Thanks

  1. I’m typing this on the laptop I want to use, so I guess wifi is working :smiley:
  2. There is no list of devices (as there is o p2p driver
  3. on Microsoft Windows 10 I can connect to the TV without a hitch
    output from nmcli device:
    nmcli device
    DEVICE TYPE STATE CONNECTION
    wlp3s0 wifi connected MittlereGasse1
    virbr0 bridge connected (externally) virbr0
    enp0s25 ethernet unavailable –
    cdc-wdm1 gsm unavailable –
    lo loopback unmanaged –
    virbr0-nic tun unmanaged –

not sure what I should do with gitlab repo. I have gnome-network-displays installed.

It says

Please verify that Wi-Fi is enabled (check) and Wi-Fi P2P operations are available in both NetworkManager and wpa_supplicant.

I have neither created nor touched those files so Iḿ unclear what is expected of me here.

I am joining this thread as I have:

  • a ChromeCastUlltra at home
  • a Notebook with “Intel Corporation Centrino Wireless-N 1030 [Rainbow Peak] (rev 34)”
lspci -v

9:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 [Rainbow Peak] (rev 34)
Subsystem: Intel Corporation Centrino Wireless-N 1030 BGN
Flags: bus master, fast devsel, latency 0, IRQ 40
Memory at f7a00000 (64-bit, non-prefetchable) [size=8K]
Capabilities:
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

Before doing anything, iw gives:

iw dev

$iw dev
Interface wlp9s0
ifindex 3
wdev 0x1
addr 58:91:cf:48:d4:d3
ssid homewifi
type managed
channel 11 (2462 MHz), width: 20 MHz, center1: 2462 MHz
txpower 15.00 dBm

iw phy

Wiphy phy0
wiphy index: 0
max # scan SSIDs: 20
max scan IEs length: 195 bytes
max # sched scan SSIDs: 0
max # match sets: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CCMP-256 (00-0f-ac:10)
* GCMP-128 (00-0f-ac:8)
* GCMP-256 (00-0f-ac:9)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
Band 1:
Capabilities: 0x107e
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT Max RX data rate: 300 Mbps
HT RX MCS rate indexes supported: 0-15
TX unequal modulation not supported
HT TX Max spatial streams: 1
HT TX MCS rate indexes supported may differ
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (15.0 dBm)
* 2417 MHz [2] (15.0 dBm)
* 2422 MHz [3] (15.0 dBm)
* 2427 MHz [4] (15.0 dBm)
* 2432 MHz [5] (15.0 dBm)
* 2437 MHz [6] (15.0 dBm)
* 2442 MHz [7] (15.0 dBm)
* 2447 MHz [8] (15.0 dBm)
* 2452 MHz [9] (15.0 dBm)
* 2457 MHz [10] (15.0 dBm)
* 2462 MHz [11] (15.0 dBm)
* 2467 MHz [12] (15.0 dBm) (no IR)
* 2472 MHz [13] (15.0 dBm) (no IR)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* connect
* disconnect
* set_qos_map
* set_multicast_to_unicast
WoWLAN support:
* wake up on disconnect
* wake up on magic packet
* wake up on pattern match, up to 20 patterns of 16-128 bytes,
maximum packet offset 0 bytes
* can do GTK rekeying
* wake up on GTK rekey failure
* wake up on EAP identity request
* wake up on rfkill release
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 1, #{ AP } <= 1,
total <= 2, #channels <= 1, STA/AP BI must match
* #{ managed } <= 2,
total <= 2, #channels <= 1
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports scan flush.
Device supports per-vif TX power setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Device supports static SMPS
Device supports dynamic SMPS
Device supports configuring vdev MAC-addr on create.
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xb0 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
Supported extended features:
* [ RRM ]: RRM
* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ EXT_KEY_ID ]: Extended Key ID support
* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
* [ DEL_IBSS_STA ]: deletion of IBSS station support
* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support

Only after discover this topic, I do sudo dnf install gnome-network-display, then I also got the same error message from gnome-network-display.

Then after some Google Search, I got:
https://gitlab.gnome.org/GNOME/gnome-network-displays/-/issues/64

This command from the above link iw <dev> interface add p2p0 type managed give me a extra p2p0 device as managed.

$ iw dev
phy#0
	Interface p2p0
		ifindex 5
		wdev 0x2
		addr 96:73:8e:4f:d2:00
		type managed
		txpower 15.00 dBm
	Interface wlp9s0
		ifindex 3
		wdev 0x1
		addr 58:91:cf:48:d4:d3
		ssid homewifi
		type managed
		channel 11 (2462 MHz), width: 20 MHz, center1: 2462 MHz
		txpower 15.00 dBm

Then I don’t know how to proceed further.

I am now studying this topic:
https://discussion.fedoraproject.org/t/cannot-start-miracast-mirroring-via-wifi/68165

And will report back any progress here.

1 Like

I did post the gitlab repo first to show that there is a patch:

Link to patch

NOTE: A common issue is that wpa_supplicant requires this patch: https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benjamin@sipsolutions.net/

And second, if you need more details about the application, you can also look direct with Gnome.
Did you have a look, if your device is, one of the checked one?

@SampsonF thanks for joining. Unfortunately i do not have a device where i could check it.

I swapped the mini-PCI wifi adaptor of my Notebook.

Immediately, it do not complaint lack of P2P adapter.

Now it is showing an empty choices in “Available Video Sinks”.

My new Wifi is Intel 7260:
09:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260
Flags: bus master, fast devsel, latency 0, IRQ 40
Memory at f7a00000 (64-bit, non-prefetchable) [size=8K]
Capabilities:
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

So far i got too … just missing a device to display there. If you have a device who should work look that it is in the same network/sub-net. Look that name resolution is working and that you can ping or traceroute to it over the device name.