lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 3 Apr 2020 14:30:56 -0400
From:   Ilia Mirkin <imirkin@...m.mit.edu>
To:     Zeno Davatz <zdavatz@...il.com>
Cc:     Ben Skeggs <bskeggs@...hat.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        nouveau <nouveau@...ts.freedesktop.org>
Subject: Re: acr: failed to load firmware with Kernel 5.6. Kernel 5.5 works
 just fine.

On Fri, Apr 3, 2020 at 1:59 PM Zeno Davatz <zdavatz@...il.com> wrote:
>
> On Fri, Apr 3, 2020 at 7:23 PM Ilia Mirkin <imirkin@...m.mit.edu> wrote:
> >
> > On Fri, Apr 3, 2020 at 1:21 PM Zeno Davatz <zdavatz@...il.com> wrote:
> > >
> > > On Fri, Apr 3, 2020 at 6:59 PM Ilia Mirkin <imirkin@...m.mit.edu> wrote:
> > > >
> > > > Ben -- probably the ACR changes in 5.6 don't fall back nicely anymore
> > > > when there's no firmware? The load shouldn't be failed, just GR
> > > > disabled...
> > > >
> > > > Zeno -- if you grab linux-firmware, it should be all better. Not sure
> > > > if you're missing it on purpose or by accident.
> > >
> > > Thank you, Ilia
> > >
> > > I will try that on my Gentoo/Funtoo machine now. So far linux-firmware
> > > was not needed with Kernel 5.5, so it was not installed on my machine.
> >
> > It was needed on 5.5 as well. It's just that it fell back gracefully
> > without firmware, and you didn't get any acceleration features.
>
> Do I need any of these enabled for linux-firmware to load properly in
> Kernel 5.6?
>
>  -*- Firmware loading facility
>   │ │                                      ()    Build named firmware
> blobs into the kernel binary
>   │ │                                      [ ]   Enable the firmware
> sysfs fallback mechanism
>   │ │                                      [ ]   Enable compressed
> firmware support

Depends on distro specifics. Also the firmware has to be available at
the time that nouveau loads. The corollary to this is:

If it's built into the kernel, then the firmware must also be included
in the kernel (since this happens before any FS stuff)
If it's loaded as a module from initrd, then initrd must contain the firmware

If you need help including firmware in the right place, a distro
support channel is probably your best shot.

Cheers,

  -ilia

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ