Fedora Account System
Red Hat Associate
Red Hat Customer
The network service fails to configure wireless specifics on wireless interfaces after upgrade to kernel 3.6. The network service configures wireless specifics on the condition that it detects that a device is wireless based on presence of wireless under sysfs. wireless is no longer present in sysfs under kernel 3.6 so this condition fails: [root@localhost ~]# uname -a Linux localhost.localdomain 3.4.11-1.fc16.i686 #1 SMP Sun Sep 16 14:41:18 UTC 2012 i686 i686 i386 GNU/Linux [root@localhost ~]# ls -1d /sys/class/net/*/wireless /sys/class/net/eth0/wireless /sys/class/net/wifi0/wireless [root@localhost ~]# uname -a Linux localhost.localdomain 3.6.6-1.fc16.i686 #1 SMP Mon Nov 5 17:16:32 UTC 2012 i686 i686 i386 GNU/Linux [root@localhost ~]# ls -1d /sys/class/net/*/wireless ls: cannot access /sys/class/net/*/wireless: No such file or directory The sysfs based check was added in this initscripts commit: http://git.fedorahosted.org/cgit/initscripts.git/diff/?id=af401fb40f6dd5139e8468dfe1bd3dafe40e8e93 If I revert that commit manually, the network service configures wireless specifics again for me under kernel 3.6. Version-Release number of selected component (if applicable): [root@localhost ~]# rpm -q initscripts kernel initscripts-9.34.3-1.fc16.i686 kernel-3.4.11-1.fc16.i686 kernel-3.6.6-1.fc16.i686 How reproducible: Always Steps to Reproduce: 1. Configure wireless devices to start under the network service 2. Upgrade to kernel 3.6 3. Boot Actual results: Wireless interfaces are not configured with wireless specifics at boot. Expected results: Wireless interfaces shoudl be cofnigured with wireless specifcs at boot as they were with kernel 3.4.
I think wireless extensions in sysfs were removed in this kernel commit in 3.6: https://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=35b2a113cb0298d4f9a1263338b456094a414057
initscripts-9.42-1.fc18.2 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/initscripts-9.42-1.fc18.2
Package initscripts-9.42-1.fc18.2: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing initscripts-9.42-1.fc18.2' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-18100/initscripts-9.42-1.fc18.2 then log in and leave karma (feedback).
initscripts-9.37.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/initscripts-9.37.2-1.fc17
initscripts-9.34.4-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/initscripts-9.34.4-1.fc16
initscripts-9.34.4-1.fc16 in updates-testing fixes this for me. Thanks!
initscripts-9.37.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
initscripts-9.34.4-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
initscripts-9.42-1.fc18.2 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
initscripts-9.42.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/initscripts-9.42.1-1.fc18
initscripts-9.42.1-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.