Hello folks,
I am running openSUSE Leap 42.1 (x86_64). Yesterday, I updated to the latest kernel. Since then, wireless does not work any more.
I have the following adapter:
$ /sbin/lspci |grep Wireless
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
$ /sbin/lspci -n |grep 04:00
04:00.0 0280: 8086:24f3 (rev 3a)
dmesg says:
6.890021] Intel(R) Wireless WiFi driver for Linux
6.890022] Copyright(c) 2003- 2015 Intel Corporation
6.903922] ACPI: AC Adapter [AC] (off-line)
6.904486] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-30.ucode failed with error -2
6.904502] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-29.ucode failed with error -2
6.904515] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-28.ucode failed with error -2
6.904526] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-27.ucode failed with error -2
6.904537] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-26.ucode failed with error -2
6.904548] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-25.ucode failed with error -2
6.904559] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-24.ucode failed with error -2
6.904569] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-23.ucode failed with error -2
6.904581] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-22.ucode failed with error -2
Is there an easy way to make it run?
Thanks
Is kernel-firmware installed?
zypper se -si kernel-firmware
PS:
Leap 42.1 is out of support.
Yes, it is:
S | Name | Type | Version | Arch | Repository
–±----------------±--------±-------------±-------±-------------------------
i | kernel-firmware | package | 20160503-3.1 | noarch | openSUSE-Leap-42.1-Update
I know I should upgrade to 42.2, but I don’t have time right now to do that 
Am Tue, 20 Jun 2017 18:46:01 GMT
schrieb checkfrogger <checkfrogger@no-mx.forums.microfocus.com>:
> Hello folks,
>
> I am running openSUSE Leap 42.1 (x86_64). Yesterday, I updated to the
> latest kernel. Since then, wireless does not work any more.
>
> I have the following adapter:
>
>
> Code:
> --------------------
>
> $ /sbin/lspci |grep
> Wireless 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
>
> $ /sbin/lspci -n |grep 04:00
> 04:00.0 0280: 8086:24f3 (rev 3a)
>
> --------------------
>
>
> dmesg says:
>
>
> Code:
> --------------------
>
> 6.890021] Intel(R) Wireless WiFi driver for Linux
> 6.890022] Copyright(c) 2003- 2015 Intel Corporation
> 6.903922] ACPI: AC Adapter [AC] (off-line)
> 6.904486] iwlwifi 0000:04:00.0: Direct firmware load for
> iwlwifi-8000C-30.ucode failed with error -2 6.904502] iwlwifi
> 0000:04:00.0: Direct firmware load for iwlwifi-8000C-29.ucode failed with
> error -2 6.904515] iwlwifi 0000:04:00.0: Direct firmware load for
> iwlwifi-8000C-28.ucode failed with error -2 6.904526] iwlwifi
> 0000:04:00.0: Direct firmware load for iwlwifi-8000C-27.ucode failed with
> error -2 6.904537] iwlwifi 0000:04:00.0: Direct firmware load for
> iwlwifi-8000C-26.ucode failed with error -2 6.904548] iwlwifi
> 0000:04:00.0: Direct firmware load for iwlwifi-8000C-25.ucode failed with
> error -2 6.904559] iwlwifi 0000:04:00.0: Direct firmware load for
> iwlwifi-8000C-24.ucode failed with error -2 6.904569] iwlwifi
> 0000:04:00.0: Direct firmware load for iwlwifi-8000C-23.ucode failed with
> error -2 6.904581] iwlwifi 0000:04:00.0: Direct firmware load for
> iwlwifi-8000C-22.ucode failed with error -2 --------------------
>
>
> Is there an easy way to make it run?
>
> Thanks
>
>
Also show us the next few lines after that output.
The iwlwifi-drivers try to load firmwares in reversed order (=try to find the
latest file first, while in this case the versions from 30-28 don’t even exist
yet in the official firmware tree), so if the next lines look something like
this
10.111066] iwlwifi 0000:3a:00.0: loaded firmware version 21.302800.0 op_mode
iwlmvm 10.139921] iwlwifi 0000:3a:00.0: Detected Intel(R) Dual Band Wireless
AC 8260, REV=0x208 10.141980] iwlwifi 0000:3a:00.0: L1 Enabled - LTR Disabled
10.142632] iwlwifi 0000:3a:00.0: L1 Enabled - LTR Disabled
missing firmware would not be the problem.
OTOH and as said before, 42.1 is out of support, so upgrading to 42.2 should be
at order (even if it does not magically fix the wifi problem).
AK
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
Am Tue, 20 Jun 2017 19:03:30 GMT
schrieb AK <Akoellh@no-mx.forums.microfocus.com>:
> Am Tue, 20 Jun 2017 18:46:01 GMT
> schrieb checkfrogger <checkfrogger@no-mx.forums.microfocus.com>:
>
> > Hello folks,
> >
> > I am running openSUSE Leap 42.1 (x86_64). Yesterday, I updated to the
> > latest kernel. Since then, wireless does not work any more.
Addendum:
What does “updated to the latest kernel” mean?
Post the output of:
uname -r
–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
Post:
zypper se -si kernel
zypper lr -d
/sbin/lspci -nnk | grep -iA3 net
And please use Code Tags. Its the # in the graphical TextEditor of the Forum.
Thanks for all your answers! I respond in the order your replies were posted:
First, the following lines in dmesg:
5.413351] Intel(R) Wireless WiFi driver for Linux
5.413353] Copyright(c) 2003- 2015 Intel Corporation
5.416493] thinkpad_acpi: ThinkPad ACPI Extras v0.25
5.416494] thinkpad_acpi: http://ibm-acpi.sf.net/
5.416496] thinkpad_acpi: ThinkPad BIOS N1CET37W (1.05 ), EC unknown
5.416496] thinkpad_acpi: Lenovo ThinkPad T460s, model 20FAA01100
5.422978] thinkpad_hwmon thinkpad_hwmon: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
5.424320] thinkpad_acpi: radio switch found; radios are enabled
5.424338] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
5.424338] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
5.427596] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
5.430389] usbcore: registered new interface driver btusb
5.431736] AVX2 version of gcm_enc/dec engaged.
5.431737] AES CTR mode by8 optimization enabled
5.432116] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-30.ucode failed with error -2
5.432133] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-29.ucode failed with error -2
5.432145] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-28.ucode failed with error -2
5.432156] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-27.ucode failed with error -2
5.432168] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-26.ucode failed with error -2
5.432180] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-25.ucode failed with error -2
5.432191] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-24.ucode failed with error -2
5.432205] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-23.ucode failed with error -2
5.432216] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-22.ucode failed with error -2
5.432218] iwlwifi 0000:04:00.0: no suitable firmware found!
5.432250] iwlwifi 0000:04:00.0: minimum version required: iwlwifi-8000C-22
5.432281] iwlwifi 0000:04:00.0: maximum version supported: iwlwifi-8000C-30
5.432314] iwlwifi 0000:04:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
Then there was the question about the exact kernel version:
$ uname -r
4.12.0-rc5-1.g270295f-default
The kernel packages (zypper se -si kernel)
i | kernel-default | package | 4.12.rc4-1.1.gf198de4 | x86_64 | (System Packages)
i | kernel-default | package | 4.12.rc5-1.1.g270295f | x86_64 | KOTD
i | kernel-firmware | package | 20160503-3.1 | noarch | openSUSE-Leap-42.1-Update
i | texlive-l3kernel | package | 2013.84.svn_4469svn29409-17.5 | noarch | openSUSE-Leap-42.1-Oss
i | texlive-l3kernel-doc | package | 2013.84.svn_4469svn29409-17.5 | noarch | openSUSE-Leap-42.1-Oss
Then the output of zypper lr -d
$zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+-------------------------------------+-----------------------------------------+---------+-----------+---------+----------+--------+-----------------------------------------------------------------------------------------+--------
1 | KOTD | KOTD | Yes | (r ) Yes | No | 100 | rpm-md | http://download.opensuse.org/repositories/Kernel:/HEAD/standard |
2 | ftp.gwdg.de-suse | Packman Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_42.1/ |
3 | home_DarkPlayer_Pipelight | Pipelight (openSUSE_Factory) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/openSUSE_Factory/ |
4 | http-download.opensuse.org-b0761407 | home:lvader:xfstk | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/lvader:/xfstk/openSUSE_Leap_42.1/ |
5 | http-download.opensuse.org-ecfccd23 | home:awissu:gazebo | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/awissu:/gazebo/openSUSE_Leap_42.1/ |
6 | openSUSE-42.1-0 | openSUSE-42.1-0 | Yes | (r ) Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/usb-TSSTcorp_CDDVDW_SE-208GB_S1BX6YAG7001RP-0:0 |
7 | opensuse-guide.org-repo | Libdvdcss Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/openSUSE_Leap_42.1/ |
8 | repo-debug | openSUSE-Leap-42.1-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.1/repo/oss/ |
9 | repo-debug-non-oss | openSUSE-Leap-42.1-Debug-Non-Oss | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.1/repo/non-oss/ |
10 | repo-debug-update | openSUSE-Leap-42.1-Update-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/update/leap/42.1/oss |
11 | repo-debug-update-non-oss | openSUSE-Leap-42.1-Update-Debug-Non-Oss | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/update/leap/42.1/non-oss/ |
12 | repo-non-oss | openSUSE-Leap-42.1-Non-Oss | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/distribution/leap/42.1/repo/non-oss/ |
13 | repo-oss | openSUSE-Leap-42.1-Oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.1/repo/oss/ |
14 | repo-source | openSUSE-Leap-42.1-Source | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/leap/42.1/repo/oss/ |
15 | repo-update | openSUSE-Leap-42.1-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.1/oss/ |
16 | repo-update-non-oss | openSUSE-Leap-42.1-Update-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.1/non-oss/ |
And finally, lspci
$/sbin/lspci -nnk | grep -iA3 net
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-LM [8086:156f] (rev 21)
Subsystem: Lenovo Device [17aa:2233]
Kernel driver in use: e1000e
Kernel modules: e1000e
--
04:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
Subsystem: Intel Corporation Device [8086:0130]
Kernel modules: iwlwifi
Am Tue, 20 Jun 2017 19:46:02 GMT
schrieb checkfrogger <checkfrogger@no-mx.forums.microfocus.com>:
> 5.432218] iwlwifi 0000:04:00.0: no suitable firmware found!
> 5.432250] iwlwifi 0000:04:00.0: minimum version required:
> iwlwifi-8000C-22 5.432281] iwlwifi 0000:04:00.0: maximum version
> supported: iwlwifi-8000C-30 5.432314] iwlwifi 0000:04:00.0: check
> git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
Well, I think this message is very clear, now isn’t it?
And seriously, Why do you use an unstable kernel?
But even if you think you have to, then you should also use the respective
kernel-firmware packages from the same repo to cover exactly these cases.
And:
Reading logs in full helps.
AK
–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
Alright, thank you. Please excuse my ignorance, I was not even aware my kernel was updated from an unstable repository.
I will have to upgrade to 42.2 now anyway.
You could try to solve it for now by doing
zypper dup --from KOTD
to make sure all kernel packages are from the HEAD:standard repo.
For the record:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/intel/iwlwifi/iwl-8000.c?id=4b87e5af638b6056bd6c20b0954d09a5a58633be
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/intel/iwlwifi?id=15098803d38778070b8edfa5a3d5fc4fef10d0a1
So a typical change which can happen any time during a development cycle and will not happen to an already released version.
Of course, this will land in 4.12 on release date, so people using kernels from kernel:stable repo (or Tumbleweed) will get “hit” by this when 4.12 stable arrives, but in contrast to using unstable kernels, you have at least an idea as a jump from 4.11 to 4.12 can and will make drastic changes while a change from 4.11.X to 4.11.X+1 will not apply changes like that. But during a release cycle a change from rcX to rcX+1 can and most likely will do such things.
In other words, if using a repo with very recent stable kernels, you might get hit ever 2-3 months by something like this and you can expect when this is most likely to happen and when not, but with “rc” (= unstable) kernels, this can happen every day.
If you know, what you are doing and want to test/help out in finding bugs (and if you are able to test those kernels on a machine you don’t need every day), then fine, go bug hunting and report them upstream.
But if you don’t know what you are doing and want to use recent kernels on your production machine, then keep your hands off rc-Kernels or at least have a fall back solution (= second stable kernel to boot into in case something breaks).
AK