Since NetworkManager's wifi functionality was split into a subpackage, boot.iso builds have no longer had wifi support. I confirmed this with today's boot.iso from the mirrors; 'ifconfig' sees my wireless interface, but anaconda's network configuration spoke does not. Manual inspection confirms that the sole file from the NetworkManager-wifi package - /usr/lib64/NetworkManager/libnm-device-plugin-wifi.so - does not exist in anaconda's environment. I believe anaconda-core (probably?) should have a dependency on NetworkManager-wifi to bring back wifi support to dedicated installer images. It's also notable that various other bits of NetworkManager hardware support are in subpackages the installer does not currently bring in: NetworkManager-adsl (certain types of ADSL modem connected directly to the PC) NetworkManager-wwan (cellular data adapters) NetworkManager-openvpn, NetworkManager-vpnc, NetworkManager-openconnect (various types of VPN) I don't know whether we're interested in supporting installs from VPN or via cellular data adapters or directly-connected ADSL modems, and whether simply including the subpackages would be enough or whether we'd need to adjust the anaconda GUI to support some/all of those methods, but it's something to bear in mind. Proposing as an Alpha blocker as a conditional violation of https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria#Remote_package_sources : "When using the dedicated installer images, the installer must be able to use either HTTP or FTP repositories (or both) as package sources." - this is violated in the case that you're trying to access such a repo over a wifi connection.
http://wiki.sugarlabs.org/go/Fedora_21#log_of_install_kernel_3.16-0.0_f21 adds Wifi to f21 installs in 3.16-0-0
(In reply to Adam Williamson from comment #0) > Since NetworkManager's wifi functionality was split into a subpackage, > boot.iso builds have no longer had wifi support. I confirmed this with > today's boot.iso from the mirrors; 'ifconfig' sees my wireless interface, > but anaconda's network configuration spoke does not. Manual inspection > confirms that the sole file from the NetworkManager-wifi package - > /usr/lib64/NetworkManager/libnm-device-plugin-wifi.so - does not exist in > anaconda's environment. > > I believe anaconda-core (probably?) should have a dependency on > NetworkManager-wifi to bring back wifi support to dedicated installer images. Anaconda currently only supports WiFi configuration in the GUI, so I guess it might make sense to make it a dependency of a the anaconda-gui package. > > It's also notable that various other bits of NetworkManager hardware support > are in subpackages the installer does not currently bring in: > > NetworkManager-adsl (certain types of ADSL modem connected directly to the > PC) > NetworkManager-wwan (cellular data adapters) > NetworkManager-openvpn, NetworkManager-vpnc, NetworkManager-openconnect > (various types of VPN) > > I don't know whether we're interested in supporting installs from VPN or via > cellular data adapters or directly-connected ADSL modems, and whether simply > including the subpackages would be enough or whether we'd need to adjust the > anaconda GUI to support some/all of those methods, but it's something to > bear in mind. I've been thinking about taking a closer look on the state of our support of using cellular data/3G modems for installation. People seem to be using this type of Internet connectivity more and more so it would be good to check if it actually works for the installation. :) > > Proposing as an Alpha blocker as a conditional violation of > https://fedoraproject.org/wiki/ > Fedora_21_Alpha_Release_Criteria#Remote_package_sources : "When using the > dedicated installer images, the installer must be able to use either HTTP or > FTP repositories (or both) as package sources." - this is violated in the > case that you're trying to access such a repo over a wifi connection.
"Anaconda currently only supports WiFi configuration in the GUI, so I guess it might make sense to make it a dependency of a the anaconda-gui package." That makes sense. So I just went and did it. Next anaconda build should include the fix.
apparently the anaconda spec file is a special special flower that cannot be touched by the hands of dirty outsiders. so. can someone please do this? i've had enough of this damn subpackage split already.
Discussed at the 2014-07-09 Fedora 21 alpha blocker review meeting. Accepted as a blocker for Fedora 21 alpha due to violation of the following alpha release criteria [1]: When using the dedicated installer images, the installer must be able to use either HTTP or FTP repositories (or both) as package sources. The network install image must default to a valid publicly-accessible package source. [1] https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria#Remote_package_sources
Patch adding the NetworkManager-wifi dependency for the Anaconda GUI subpackage has been posted for review.
21.48 was built on 07-18 so this is likely fixed already. We should verify with a recent boot.iso.
Fix confirmed in 2014-07-25 F21 boot.iso nightly.
Here's another thing to consider, completely aside from anaconda: If you update an F20 system's NetworkManager suite to F21, you'll lose WiFi unless you know about the package split. A rash upgrade to do, you may say, but isn't the package split going to come to F20 someday?
"If you update an F20 system's NetworkManager suite to F21, you'll lose WiFi unless you know about the package split." No, you won't. We have a convention that handles this. All the subpackages obsolete the pre-split versions of NetworkManager; yum (and, since a recent build, dnf) interprets this in the way we want it to: when you upgrade from a pre-split to a post-split version of NetworkManager, you get all the subpackages installed. "isn't the package split going to come to F20 someday?" I don't think so, no. This kind of disruptive change wouldn't generally be shipped as a stable release update.