archive mirror
 help / color / mirror / Atom feed
From: David Goodenough <>
Subject: Re: Intel 8265/8275 microcode
Date: Sun, 16 Jul 2017 09:58:15 +0100	[thread overview]
Message-ID: <2178837.BdKxmf7zyZ@stargate> (raw)
In-Reply-To: <>

You are right, it was working all along, I just had another config error which
meant that it did not seem to be working.

I followed by usual problem solving which is to look for the first error
message.  Should have looked further. 

thanks for your help


On Saturday, 15 July 2017 23:58:56 BST Luca Coelho wrote:
> On Sat, 2017-07-15 at 10:03 +0100, David Goodenough wrote:
> > I have a laptop which reports the wifi adapter to be an 8265/8275 rev 78
> > and the driver complains that it can not find:-
> > 
> > iwlwifi-8265-23.ucode
> > iwlwifi-8265-24.ucode
> > iwlwifi-8265-25.ucode
> > iwlwifi-8265-26.ucode
> > iwlwifi-8265-27.ucode
> > iwlwifi-8265-28.ucode
> > 
> > and they not appear to be in the github.  Where do I find
> > them and could they be added to github?
> Does your wifi card work? The driver tries to find one of the supported
> versions, starting from highest and going down to the lowest.  It seems
> that you have -22.ucode and, if that's the case, everything should be
> fine and you can ignore these messages.
> It is an old known problem that there is no way to try to load a
> firmware without getting an error message.  People are working on
> solving this, but until then, just ignore this messages and everything
> should be fine. :)
> --
> Cheers,
> Luca.

  reply	other threads:[~2017-07-16  8:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-15  9:03 Intel 8265/8275 microcode David Goodenough
2017-07-15 20:58 ` Luca Coelho
2017-07-16  8:58   ` David Goodenough [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-07-14 13:15 David Goodenough

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2178837.BdKxmf7zyZ@stargate \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).