Enable IWD to be used as back-end in network selection #4025
+32
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR should solve a lot of issues for Intel users among other legacy hardware.
Issue originally from user: Coda_Phi : On a surface pro 7 (Notoriously Intel contributes to IWD dev, and has bad support with default wpa_supplicant default backend) This notably results in "No networks" in desktops.
So I tested a little on a
Intel AX211similar to user'sAX201It follows https://wiki.archlinux.org/title/NetworkManager#Using_iwd_as_the_Wi-Fi_backend
And https://wiki.archlinux.org/title/NetworkManager#iwd_support_for_captive_portal_support_on_legacy_hardware
By setting enable services to
Falsethen enabling onlyNetworkManagerand writing the necessary config file to use IWD as back-end. It also still copies from ISO re-using existing definitions too.Simply makes it so that you configure in ISO env before or during archinstall => Still works in DE