You (and I) could only try to learn from what was said in the kernel bugzilla comments.
I am closing this since it is not a bug on the wifi side and there is a solution to keep your use case working: not using hostapd, but rather using p2p_group_add command in wpa_supplicant.
somehow using something else
hostapd vs. wpa_supplicant
to achieve the desired result …
I have no idea or knowledge or recommendation.
As usual I’d simply use what works.
In above comment Wifi bridge (kernel 6.11 breaks linux-wifi-hotspot wireless bridge) - #12 by linux-aarhus - I created a working hotspot andd connected a phone, and was able to load Manjaro forum from phone.
I deduced it from the messages printed when launched from terminal.
Neither do I - I could only make the app work by adding the mentioned arguments to my kernel cmdline.
I have apparmor installed because it is a dependency of snapd - which I don’t use either but our tools depend on for building ISO.
You say a kernel makes your app stop working - it could be that those kernels requires the activation - and the app requires apparmor - and this change requires you to reconfigure your kernel.
When you use the app - it is quite possible the developer work with Ubuntu which makes a lot more use of apparmor.
If you cannot make it work - it is time to the approach laid out for my. success
Have fun children…
@linux-aarhus Thank you for your effort! Do you have your linux machine connected to your router via wifi? If yes, can you please post iw list? Or a better command to know whether it’s a capability of the interface or something different.
I had another go on wifi-p2p and i finally got a connection, but it closed after about thirty seconds. So still not usable.
/home/user/wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
device_name=My-pc
device_type=1-0050F204-1
driver_param=use_p2p_group_interface=1
nmcli radio wifi off
rfkill unblock wlan
sudo dnsmasq
sudo wpa_supplicant -Dnl80211 -iwlp3s0 -c/home/user/wpa_supplicant.conf
sudo wpa_cli
> p2p_find
> p2p_peers
> p2p_connect mac:aa:of:phone 45629034 display persistent
sudo ip addr add 192.168.12.1/24 dev p2p-wlp3s0-0
wpa_supplicant output:
Successfully initialized wpa_supplicant
P2P-DEVICE-FOUND mac:aa:of:phone p2p_dev_addr=mac:aa:of:phone pri_dev_type=10-0050F204-5 name='Tab S9 FE von Jessica' config_methods=0x188 dev_capab=0x25 group_capab=0x0 vendor_elems=1 new=1
P2P-FIND-STOPPED
P2P-GO-NEG-SUCCESS role=GO freq=2462 ht40=0 peer_dev=mac:aa:of:phone peer_iface=mac:bb:of:phone wps_method=Display
p2p-wlp3s0-0: interface state UNINITIALIZED->ENABLED
p2p-wlp3s0-0: AP-ENABLED
p2p-wlp3s0-0: CTRL-EVENT-CONNECTED - Connection to mac:aa:of:laptop completed [id=0 id_str=]
p2p-wlp3s0-0: CTRL-EVENT-EAP-STARTED mac:bb:of:phone
p2p-wlp3s0-0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1
p2p-wlp3s0-0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=14122 method=254
p2p-wlp3s0-0: WPS-REG-SUCCESS mac:bb:of:phone cac98c51-fd7c-5417-a0cf-0488d15d0f59
P2P-GROUP-FORMATION-SUCCESS
P2P-GROUP-STARTED p2p-wlp3s0-0 GO ssid="DIRECT-m8" freq=2462 go_dev_addr=mac:bb:of:laptop [PERSISTENT]
p2p-wlp3s0-0: WPS-SUCCESS
p2p-wlp3s0-0: CTRL-EVENT-EAP-FAILURE mac:bb:of:phone
p2p-wlp3s0-0: AP-STA-CONNECTED mac:bb:of:phone p2p_dev_addr=mac:aa:of:phone
AP-STA-CONNECTED mac:bb:of:phone p2p_dev_addr=mac:aa:of:phone
p2p-wlp3s0-0: EAPOL-4WAY-HS-COMPLETED mac:bb:of:phone
p2p-wlp3s0-0: AP-STA-DISCONNECTED mac:bb:of:phone p2p_dev_addr=mac:aa:of:phone
AP-STA-DISCONNECTED mac:bb:of:phone p2p_dev_addr=mac:aa:of:phone
Because I read it between the lines that you are unsure about this: the wifi bridge works on this machine A) on windows B) on linux66 with linux-wifi-hotspot. It doesn’t work on linux611 nor linux612. So yes, my wifi-card is capable of virtual interfaces and i checked that it is capable of P2P via iw list. It is only a change in software.
As linux-wifi-hotspot works on linux66 in wifi-bridge and on linux612 as simple hotspot and i don’t have apparmor installed, would it still be usefull to install apparmor for testing on linux612? I fear it breaks other programs
Your statement kernel 6.11 breaks linux-wifi-hotspot wireless bridge has been tested.
With the above mentioned adjustments to my system the custom AUR package linux-wifi-hotspot work as advertised.
The wlan card in my ThinkPad X13 is Qualcomm Technologies, Inc QCNFA76.
No issues on Linux 6.12.10 on Manjaro edge (unstable branch)
So I my opinion - it is a matter of configuration of the system at hand.
I have made it no secret - this is the first time ever - I have created a wireless hotspot on a laptop.
I added the app using git clone and makepkg to build.
As my intent was to troubleshoot the app - I started the app by entering wihotspot-gui manually in a terminal - watching the output.
From there I could see, if I didn’t have dnsmasq installed - I couldn’t create a hotspot.
So I added dnsmasq. Although it is stated as an optional dependency, I couldn’t start the hotspot without it being present.
After adding dnsmasq I could start the hotspot but couldn’t connect - a message about apparmor compat 2.4 missing.
So I checked the arch wiki to find mention of it - didn’t immediately - but I found the mentioned kernel arguments as the first thing described to use apparmor.
So I added the kernel args, rebuild init and rebooted.
I could still not connect - I got the thought that firewalld might be blocking - so I stopped firewalld - end the thing worked.
I could successfully connect my phone to the hotspot - I could browse the internet, both from laptop and phone.
I will not argue that your don’t have an issue - obvious you have - but I am not able to reproduce your issue on my system - on contrary - on my system it work as advertised.
But I have no clue why your system does not work - especially as it has been functional.
My only suggestion is to remove the app and rebuild using git clone and makepkg.
sudo pacman -Rns linux-wifi-hotspot
git clone https://aur.archlinux.org/linux-wifi-hotspot
makepkg -i
Add the mentioned load entries for apparmor (as described with Arch Wiki) and rebuild your grub and init.
sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo mkinitcpio -P
Note: I didn’t update my grub - as I boot using a single - custom signed - efi loader with Secure Boot.
Thank you very much for your elaborate post and keeping up with me! This gives me a little hope, even if it seems to contradict a kernel dev. My gut feeling still is that this is a difference in either hardware or driver. Do you know which command output to compare?
iw list returns the following on my machine:
Wiphy phy0
wiphy index: 0
max # scan SSIDs: 20
max scan IEs length: 416 bytes
max # sched scan SSIDs: 20
max # match sets: 11
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0x1 RX 0x1
Configured Antennas: TX 0x1 RX 0x1
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x116e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
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: 150 Mbps
HT TX/RX MCS rate indexes supported: 0-7
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.0 MHz [1] (20.0 dBm)
* 2417.0 MHz [2] (20.0 dBm)
* 2422.0 MHz [3] (20.0 dBm)
* 2427.0 MHz [4] (20.0 dBm)
* 2432.0 MHz [5] (20.0 dBm)
* 2437.0 MHz [6] (20.0 dBm)
* 2442.0 MHz [7] (20.0 dBm)
* 2447.0 MHz [8] (20.0 dBm)
* 2452.0 MHz [9] (20.0 dBm)
* 2457.0 MHz [10] (20.0 dBm)
* 2462.0 MHz [11] (20.0 dBm)
* 2467.0 MHz [12] (20.0 dBm) (no IR)
* 2472.0 MHz [13] (20.0 dBm) (no IR)
Band 2:
Capabilities: 0x116e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
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: 150 Mbps
HT TX/RX MCS rate indexes supported: 0-7
VHT Capabilities (0x33807120):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
short GI (80 MHz)
SU Beamformee
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: not supported
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: not supported
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
VHT extended NSS: supported
Bitrates (non-HT):
* 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:
* 5180.0 MHz [36] (22.0 dBm) (no IR)
* 5200.0 MHz [40] (22.0 dBm) (no IR)
* 5220.0 MHz [44] (22.0 dBm) (no IR)
* 5240.0 MHz [48] (22.0 dBm) (no IR)
* 5260.0 MHz [52] (20.0 dBm) (no IR, radar detection)
* 5280.0 MHz [56] (20.0 dBm) (no IR, radar detection)
* 5300.0 MHz [60] (20.0 dBm) (no IR, radar detection)
* 5320.0 MHz [64] (20.0 dBm) (no IR, radar detection)
* 5500.0 MHz [100] (22.0 dBm) (no IR, radar detection)
* 5520.0 MHz [104] (22.0 dBm) (no IR, radar detection)
* 5540.0 MHz [108] (22.0 dBm) (no IR, radar detection)
* 5560.0 MHz [112] (22.0 dBm) (no IR, radar detection)
* 5580.0 MHz [116] (22.0 dBm) (no IR, radar detection)
* 5600.0 MHz [120] (22.0 dBm) (no IR, radar detection)
* 5620.0 MHz [124] (22.0 dBm) (no IR, radar detection)
* 5640.0 MHz [128] (22.0 dBm) (no IR, radar detection)
* 5660.0 MHz [132] (22.0 dBm) (no IR, radar detection)
* 5680.0 MHz [136] (22.0 dBm) (no IR, radar detection)
* 5700.0 MHz [140] (22.0 dBm) (no IR, radar detection)
* 5720.0 MHz [144] (13.0 dBm) (no IR, radar detection)
* 5745.0 MHz [149] (13.0 dBm) (no IR)
* 5765.0 MHz [153] (13.0 dBm) (no IR)
* 5785.0 MHz [157] (13.0 dBm) (no IR)
* 5805.0 MHz [161] (13.0 dBm) (no IR)
* 5825.0 MHz [165] (13.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
* start_sched_scan
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* connect
* disconnect
* channel_switch
* set_qos_map
* add_tx_ts
* 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 4-way handshake
* wake up on rfkill release
* wake up on network detection, up to 11 match sets
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 1, #{ P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
total <= 3, #channels <= 2
* #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
total <= 3, #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 low priority scan.
Device supports scan flush.
Device supports per-vif TX power setting
P2P GO supports CT window setting
P2P GO supports opportunistic powersave setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
Device supports static SMPS
Device supports dynamic SMPS
Device supports WMM-AC admission (TSPECs)
Device supports configuring vdev MAC-addr on create.
Device supports randomizing MAC-addr in scans.
Device supports randomizing MAC-addr in sched scans.
Device supports randomizing MAC-addr in net-detect scans.
max # scan plans: 2
max scan plan interval: 65535
max scan plan iterations: 254
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:
* [ VHT_IBSS ]: VHT-IBSS
* [ RRM ]: RRM
* [ BEACON_RATE_LEGACY ]: legacy beacon rate setting
* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
* [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans
* [ 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
* [ PROT_RANGE_NEGO_AND_MEASURE ]: support for MFP in range measurement negotiation/procedure
* [ POWERED_ADDR_CHANGE ]: can change MAC address while up
Well, I followed your steps and installed linux-wifi-hotspot manually. Then I installed apparmor (even if i didn’t receive any errors about apparmor before when running wihotspot in terminal). I inserted the lines for apparmor into GRUB_CMDLINE_LINUX_DEFAULT= in /etc/default/grub, activated via sudo update-grub, rebooted and confirmed via cat /proc/cmdline. After that I still got the same output as before from wihotspot:
# I disconnected from my wifi network, so the card is idle
pkexec --user root create_ap wlp3s0 wlp3s0 'MyAccessPoint' '12345678' --mkconfig /etc/create_ap.conf --freq-band 2.4
Config options written to '/etc/create_ap.conf'
# now I can connect with my phone to the network, then stopping in the gui
Trying to kill create_ap instance associated with 5172...
# now I connect to my home network and try to start the hotspot again
pkexec --user root create_ap wlp3s0 wlp3s0 'MyAccessPoint' '12345678' --mkconfig /etc/create_ap.conf --freq-band 2.4
Config options written to '/etc/create_ap.conf'
Error: Failed to run hostapd, maybe a program is interfering.
If an error like 'n80211: Could not configure driver mode' was thrown
try running the following before starting create_ap:
nmcli r wifi off
rfkill unblock wlan
Command not found or exited with error status
# if I do the above cmds, the hotspot works, but we knew that already from the above, I want to have a wifi bridge/repeater
I think this is the important part from iw list. As I got access to another PC with manjaro, I tried to run my setup, but it didn’t work and that wifi card shows an empty list of valid combinations. @linux-aarhus can you please post inxi -n? I would guess your card uses the ath11k driver or similar and not the iwlwifi which the kernel issue is about.
My inxi -n is
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: enp2s0f1 state: down mac: f0:76:1c:72:9f:cf
Device-2: Intel Wireless 3160 driver: iwlwifi
IF: wlp3s0 state: up mac: 34:de:1a:7c:09:c5
You are welcome to reference my findings upstream…
I have only focused on the OOB experience and thus not tested any manually applied commands
| Working | Subject | Kernel | Mfg | Version | Driver | AppArmor |
|---|---|---|---|---|---|---|
 |
@gamert | Intel | 3160 | iwlwifi | no | |
 |
A | 6.12.10 | Qualcomm Atheros | QCNFA765 | ath11k_pci | yes |
|
B | 6.12.10 | Intel | Raptor Lake | iwlwifi | no |
|
B | 6.13.0 | Intel | Raptor Lake | iwlwifi | no |
|
C | 6.12.10 | Intel | AC 9x6x [Thunder Peak] | iwlwifi | no |
The current evidence points to either a regression or a deliberate change within the iwlwifi driver
ThinkPad X13 AMD (Ryzen 7 7840 APU)
System has apparmor installed
$ uname -R
6.12.10-1-MANJARO
$ lspci
...
01:00.0 Network controller: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter (rev 01)
...
$ inxi -Nxxx
Network:
Device-1: Qualcomm QCNFA765 Wireless Network Adapter vendor: Lenovo
driver: ath11k_pci v: kernel pcie: speed: 8 GT/s lanes: 1 bus-ID: 01:00.0
chip-ID: 17cb:1103 class-ID: 0280
$ iw list
...
Supported interface modes:
* managed
* AP
* P2P-client
* P2P-GO
* P2P-device
...
$ lshw -c network -sanitize
WARNING: you should run this program as super-user.
*-network
description: Wireless interface
product: QCNFA765 Wireless Network Adapter
vendor: Qualcomm Technologies, Inc
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlp1s0
version: 01
serial: [REMOVED]
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ath11k_pci driverversion=6.12.10-1-MANJARO firmware=N/A ip=[REMOVED] latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:109 memory:90600000-907fffff
Tuxedo Infinitibook Pro 14 (i7-13700H)
System does not have apparmor installed
initial launch of GUI, create hotspot fails.
executing the commands listed and restarting GUI allows to create hotspot, but connecting to the hotspot fails.
$ uname -R
6.12.10-1-MANJARO
$ lspci
...
00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi WiFi (rev 01)
...
$ inxi -Nxxx
Network:
Device-1: Intel Raptor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:51f1 class-ID: 0280
$ iw list
...
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
* P2P-device
...
$ sudo lshw -c network -sanitize
*-network
description: Wireless interface
product: Raptor Lake PCH CNVi WiFi
vendor: Intel Corporation
physical id: 14.3
bus info: pci@0000:00:14.3
logical name: wlo1
version: 01
serial: [REMOVED]
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=6.12.10-1-MANJARO firmware=89.6b44fa0b.0 so-a0-hr-b0-89.uc ip=[REMOVED] latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: iomemory:600-5ff irq:16 memory:601d174000-601d177fff
Error: Failed to run hostapd, maybe a program is interfering.
If an error like 'n80211: Could not configure driver mode' was thrown
try running the following before starting create_ap:
nmcli r wifi off
rfkill unblock wlan
Command not found or exited with error status
Executing the referenced commands does not result in being able to create the hotspot bridge.
Laptop Clevo N14xWU
ISO-boot manjaro-xfce-25.01-development-unstable-minimal-250117-linux612.iso
ISO comes with apparmor installed (snapd support)
$ uname -r
6.12.9-1-MANJARO
$ lspci
3b:00.0 Network controller: Intel Corporation Wi-Fi 5(802.11ac) Wireless-AC 9x6x [Thunder Peak] (rev 29)
$ iw list
...
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
* P2P-device
...
$ inxi -Nxxx
...
Device-2: Intel Wi-Fi 5 Wireless-AC 9x6x [Thunder Peak] driver: iwlwifi
v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 3b:00.0 chip-ID: 8086:2526
class-ID: 0280
$ lshw -c network -sanitize
...
*-network
description: Wireless interface
product: Wi-Fi 5(802.11ac) Wireless-AC 9x6x [Thunder Peak]
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:3b:00.0
logical name: wlp59s0
version: 29
serial: [REMOVED]
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=6.12.9-1-MANJARO firmware=46.7e3e4b69.0 9260-th-b0-jf-b0- ip=[REMOVED] latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:125 memory:dc100000-dc103fff
Error: Failed to run hostapd, maybe a program is interfering.
If an error like 'n80211: Could not configure driver mode' was thrown
try running the following before starting create_ap:
nmcli r wifi off
rfkill unblock wlan
Command not found or exited with error status
Executing the referenced commands does not result in being able to create the hotspot bridge.
Thank you for this very thorough testing! I wrote in the kernel bugzilla and will also write in the linux-wifi-hotspot issue. I hope I found good words and now I have to wait on the devs.