Comment # 7 on bug 1000482 from
Sorry for that long text paste, I don't see a way of adding more than one
attachment.

--"Judging from hwinfo output and dmesg output, the iwlwifi driver on TW kernel
seems already working.  What doesn't work on your machine?"

Huh?? From the subject of this bug: The install of Leap 42.2 Beta 1 & 2 fails.


HWINFO of the current installed 42.1 might just give clues:
  <6>[    7.418817] cfg80211: Calling CRDA to update world regulatory domain
  <6>[    7.421439] Intel(R) Wireless WiFi driver for Linux
  <6>[    7.421444] Copyright(c) 2003- 2015 Intel Corporation
  <6>[    7.421822] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
  <3>[    7.425421] iwlwifi 0000:02:00.0: Unsupported splx structure
  <6>[    7.426325] iwlwifi 0000:02:00.0: loaded firmware version 25.30.13.0
op_mode iwlmvm
  <6>[    7.431815] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless
AC 8260, REV=0x208
  <6>[    7.432032] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
  <6>[    7.433064] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
  <6>[    7.433675] iwlwifi 0000:02:00.0: can't access the RSA semaphore it is
write protected


Here is what someone else said for Ubuntu:
http://askubuntu.com/questions/751504/intel-wireless-controller-8260-unclaimed-ubuntu-15-10

What will be the same routine in openSUSE as per this article? I mean which
binary from here -
https://github.com/OpenELEC/iwlwifi-firmware/tree/master/firmware


--"It's unclear whether we can add the support of this chip to openSUSE-42.2
kernel.  I can try to provide a test kernel with a couple of simple backports. 
If it works, it's fine.  If not, it'll be WONTFIX, unfortunately."

This chip came out 1.5 years ago -
http://ark.intel.com/products/86068/Intel-Dual-Band-Wireless-AC-8260

I do not understand the lingo/buswords you are using. Sorry I'm not so involved
with Kernel stuff. To whom will you provide a kernel and what does simple
backports mean for Kernel stuff? What does WONTFIX mean and what does this mean
for Tumbleweed that have the exact same install problem?


You are receiving this mail because: