Bug 112981
Summary: | Intel 8260 fails to load at boot | ||
---|---|---|---|
Product: | Drivers | Reporter: | digimer (digimer) |
Component: | network-wireless | Assignee: | DO NOT USE - assign "network-wireless-intel" component instead (linuxwifi) |
Status: | CLOSED INVALID | ||
Severity: | normal | CC: | linuxwifi, linville, toracat |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 4.4.2 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
digimer
2016-02-23 17:51:08 UTC
You should really get -16.ucode. I wonder why it takes 60 seconds to fallback to older firmwares. > You should really get -16.ucode.
Should I file a bug for RHEL then?
what do you have in /lib/firmware/iwlwifi-8000C* ? # ls -lah /lib/firmware/iwlwifi-8000C* -rw-r--r--. 1 root root 1.7M Nov 20 01:22 /lib/firmware/iwlwifi-8000C-13.ucode I downloaded iwlwifi-8000C-16.ucode from https://github.com/OpenELEC/iwlwifi-firmware/blob/master/firmware/iwlwifi-8000C-16.ucode, set the ownership and mode: # ls -lah /lib/firmware/iwlwifi-8000C* -rw-r--r--. 1 root root 1.7M Nov 20 01:22 /lib/firmware/iwlwifi-8000C-13.ucode -rw-r--r--. 1 root root 2.3M Feb 24 10:02 /lib/firmware/iwlwifi-8000C-16.ucode And rebooted. It still is exhibiting the same behaviour. ==== # dmesg |grep iwlwifi [ 4.340292] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002) [ 4.354269] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2 [ 4.354984] iwlwifi 0000:04:00.0: Falling back to user helper [ 64.183747] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2 [ 64.183759] iwlwifi 0000:04:00.0: Falling back to user helper [ 124.185127] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2 [ 124.185138] iwlwifi 0000:04:00.0: Falling back to user helper [ 184.188493] iwlwifi 0000:04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 184.223830] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 [ 184.224130] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled [ 184.225121] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled [ 184.226445] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected [ 184.399727] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0 [ 184.418313] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled [ 184.418760] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled [ 184.419711] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected [ 184.565105] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled [ 184.565788] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled [ 184.567191] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected ==== Here are the sums: ==== # md5sum /lib/firmware/iwlwifi-8000C* fd0ac79f34b10ce98d58100b509be73f /lib/firmware/iwlwifi-8000C-13.ucode 2d2b06c5644c9d718e7c0495aafa215b /lib/firmware/iwlwifi-8000C-16.ucode ==== I don't understand why it takes 60 seconds to fail. I'll try to find out. Is iwlwifi compiled in the kernel or as a loadable module? # lsmod |grep iwlwifi iwlwifi 131072 1 iwlmvm cfg80211 557056 3 iwlwifi,mac80211,iwlmvm So it looks like it's a module. If there is anything you would like me to try, this machine is not in use at this time. I am happy to test anything for you as there is no concern with reinstalling if needed. Are sure you have udev running properly? This looks like a distro issue. The user space isn't responding to the kernel's request. For sure, this is not a wifi bug. Closing as I can't do much with this. Please contact your distribution. According to https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release , iwlwifi-8000C-16.ucode (Core13) is marked EOL. Maybe the latest (-21.ucode) should be tried. Or at least -19.ucode as a minimum. I don't remember what machine I was having this problem on. It hasn't been an issue on anything I'm running for a while now. So consider it resolved and close the bug. :) Your article: https://alteeve.ca/w/Thinkpad_P70 :-) Oh riiiiight! OK, I will reinstall when Fedora 24 comes out. If I hit the issue then, I'll try the newer driver. If not, I'll update that to remove the notes about the drivers. Thanks! |