Description of problem: Neither kernel nor kernel-modules-extra include support for Intersil Prism chipset. The kernel is compiled without CONFIG_HERMES_PRISM, which disables Prism chipset support in orinoco_cs, orinoco_plx and orinoco_nortel modules and disables orinoco_pci module completely. CONFIG_HOSTAP is also disabled. Version-Release number of selected component (if applicable): 3.15.4-200.fc20 How reproducible: Always Steps to Reproduce: 1. Install a Prism2 or Prism2.5 card 2. Boot Fedora 20 Actual results: The card is not detected by the kernel, no module is loaded Expected results: The card is detected Additional info: I understand that Prism chipset is old, but it was a market leader ten years ago. Not supporting it leave old computers without wireless connectivity. That's the computers that are migrating to Linux because Windows XP is not supported anymore. We should care. Enabling hostap would be a much better choice, as the hostap driver supports WPA and the orinoco (hermes) driver doesn't. But is enabling hostap is ruled out please at least enable CONFIG_HERMES_PRISM. The whole point in having that option is to avoid a conflict with hostap that is not enabled anyway.
Enabled in the next build. Note that this driver is ancient and we really can't support it. If bugs are reported against it we'll direct people upstream and close the bug as UPSTREAM.
kernel-3.15.6-200.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.15.6-200.fc20
Package kernel-3.15.6-200.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.15.6-200.fc20' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-8519/kernel-3.15.6-200.fc20 then log in and leave karma (feedback).
kernel-3.15.6-200.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.