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] [day] [month] [year] [list]
Message-ID: <CAKb7Uvi_w8Yia6FzGVzCYY8h+p8v6VHS8Xtyd9R=r_c_NTbQ8A@mail.gmail.com>
Date:   Mon, 31 Oct 2016 08:51:57 -0400
From:   Ilia Mirkin <imirkin@...m.mit.edu>
To:     Alexandre Courbot <gnurou@...il.com>
Cc:     Alexandre Courbot <acourbot@...dia.com>,
        Ben Skeggs <bskeggs@...hat.com>,
        Dave Airlie <airlied@...hat.com>,
        "nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>
Subject: Re: [Nouveau] Nouveau regression since kernel 4.3: loading NVIDIA's
 firwmare files

On Mon, Oct 31, 2016 at 2:31 AM, Alexandre Courbot <gnurou@...il.com> wrote:
> On Mon, Oct 31, 2016 at 1:34 AM, Ilia Mirkin <imirkin@...m.mit.edu> wrote:
>> Hi Alex,
>>
>> As you're well-aware, your commit
>> 8539b37acef73949861a16808b60cb8b5b9b3bab (drm/nouveau/gr: use
>> NVIDIA-provided external firmwares) broke tons of existing setups for
>> people who were using extracted firmware files (stored in the
>> "nouveau" firmware directory) as a result of nouveau's ctxsw fw being
>> ... lacking. This is especially common on GK106's for some reason.
>>
>> The arguments for doing this at the time was that (a) all the bugs in
>> nouveau's fw have been fixed and thus those people don't need to be
>> using those extracted firmware files and (b) NVIDIA was going to
>> release firmware and so things would Just Work (tm) since the new
>> files would be at the new locations.
>>
>> Neither of these have come to fruition. Plenty of people still have
>> GK106's that don't work well with nouveau's fw. NVIDIA has shown no
>> interest in releasing firmware in a redistributable fashion.
>>
>> Can you please create a patch to fix this up so that it still tries to
>> load files from the previous location with the previous names so that
>> people's previously-working setups can keep on working?
>
> Certainly. Actually my first version of 8539b37acef7 did fall back to
> the original paths for loading firmware, but Ben suggested that we
> just replace the paths entirely, hence the version currently merged:
>
> https://lists.freedesktop.org/archives/dri-devel/2015-June/084914.html
>
> Ben, do you agree with falling back to the old "nouveau/nvxx_fucxxxx"
> firmware names so people don't need to move their firmware files
> around?

The theory was that the nouveau fw was going to be sufficient for
pre-GM200 chips. Practice hasn't lived up to that - a ton of people
with a GTX 660's have issues with the nouveau fw being unstable, whose
issues are fixed by the extracted firmware from the blob.

  -ilia

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ