similar to: Nouveau regression since kernel 4.3: loading NVIDIA's firwmare files

On Mon, Oct 31, 2016 at 1:34 AM, Ilia Mirkin <imirkin at alum.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)

https://bugs.freedesktop.org/show_bug.cgi?id=111724 Bug ID: 111724 Summary: NVE6 (GK106) memory re-clocking breaks GpuTest plot3d benchmark Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: not set

Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path if they cannot be found in the new, "official" path. User setups were broken by the switch, which is bad. There are only 4 firmware files we may want to look up that way, so hardcode them into the lookup function. All new firmware files should use the standard "nvidia/<chip>/gr/" path.

There were fixes in 3.17 that were supposed to help this, but apparently they didn't help enough. See https://bugs.freedesktop.org/show_bug.cgi?id=72180 -- basically some sort of card setup failure on our part is causing our ctxsw to die, but nvidia's appears to be more resilient to the screwups. On Fri, Dec 5, 2014 at 1:16 PM, Rob Jansen <rob.g.jansen at nrl.navy.mil> wrote: >

Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path if they cannot be found in the new, "official" path. User setups were broken by the switch, which is bad. There are only 4 firmware files we may want to look up that way, so hardcode them into the lookup function. All new firmware files should use the standard "nvidia/<chip>/gr/" path.

On 11/02/2016 02:07 PM, Ilia Mirkin wrote: > On Wed, Nov 2, 2016 at 12:54 AM, Alexandre Courbot <acourbot at nvidia.com> wrote: >> Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path >> if they cannot be found in the new, "official" path. User setups were >> broken by the switch, which is bad. >> >> There are only 4

Some firmware images may be large (64K), so using kmalloc memory is inappropriate for them. Use vmalloc instead, to avoid high-order allocation failures. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: stable at vger.kernel.org --- Couldn't get video decoding started on a long-running system due to high-order allocation failures. This seems like a fine use-case for vmalloc.

Hi, Using 3 monitors on the GeForce GTX 650 Ti card (2 DVI and 1 VGA) works great out of the box on Fedora 20. However, every couple of days the graphics driver seems to crash. The same thing used to happen when 2 monitors were in use, but that has pretty much stabilized as of late. Does anyone have a stable setup with this card using 3 monitors? Will 3 monitors be supported? Thanks, Rob $

Hi ! Kenrel 2.6.21 (kernel.org) Patch lguest-2.6.21-254.patch Distro Slackware 11.0 GCC 3.4.6 GLIBC 2.3.6 HW model name : AMD Duron(tm) procu{s{ Module Size Used by tun 7680 0 lg 54600 0 just started playing with lguest - patching, compiling and booting the host-kernel goes ok - compiling lguest is ok as well after

Hi ! Kenrel 2.6.21 (kernel.org) Patch lguest-2.6.21-254.patch Distro Slackware 11.0 GCC 3.4.6 GLIBC 2.3.6 HW model name : AMD Duron(tm) procu{s{ Module Size Used by tun 7680 0 lg 54600 0 just started playing with lguest - patching, compiling and booting the host-kernel goes ok - compiling lguest is ok as well after

On 12 May 2015 at 19:04, Alexandre Courbot <gnurou at gmail.com> wrote: > Hi Ben, > > On Fri, May 1, 2015 at 8:01 AM, Ben Skeggs <skeggsb at gmail.com> wrote: >> On 13 April 2015 at 20:42, Alexandre Courbot <acourbot at nvidia.com> wrote: >>> Ben, I guess our main remaining concern with this patch is how it should >>> integrate wrt. the existing

Hi Guys, So creating a forums application seems like something that rails can handle easily and well, and whatever implementation that came to fruition would be head and shoulders above existing products like vBulliten and phpBB. Even the existing rails forums are using php-based forum products! An insult if you ask me. So my question -- is there any current development of a rails-based

On 2017/11/14 15:12, Wanpeng Li wrote: > 2017-11-14 15:02 GMT+08:00 Quan Xu <quan.xu0 at gmail.com>: >> >> On 2017/11/13 18:53, Juergen Gross wrote: >>> On 13/11/17 11:06, Quan Xu wrote: >>>> From: Quan Xu <quan.xu0 at gmail.com> >>>> >>>> So far, pv_idle_ops.poll is the only ops for pv_idle. .poll is called >>>>

On 2017/11/14 15:12, Wanpeng Li wrote: > 2017-11-14 15:02 GMT+08:00 Quan Xu <quan.xu0 at gmail.com>: >> >> On 2017/11/13 18:53, Juergen Gross wrote: >>> On 13/11/17 11:06, Quan Xu wrote: >>>> From: Quan Xu <quan.xu0 at gmail.com> >>>> >>>> So far, pv_idle_ops.poll is the only ops for pv_idle. .poll is called >>>>

On Thu, 2019-02-14 at 18:43 -0600, Bjorn Helgaas wrote: > Hi Lyude, > > On Tue, Feb 12, 2019 at 05:02:30PM -0500, Lyude Paul wrote: > > On a very specific subset of ThinkPad P50 SKUs, particularly ones that > > come with a Quadro M1000M chip instead of the M2000M variant, the BIOS > > seems to have a very nasty habit of not always resetting the secondary > >

On Tue, 2019-05-21 at 17:44 +0100, Rowland penny via samba wrote: > There was some talk of this happening automatically, but this seems > to > have not come to fruition yet. It has. See the bootstrap/ system in master. This hasn't been backported to Samba 4.10 however. The files in generated-dists are intended to be linkable from the wiki as the definitive list of packages for a

Hello r users, I have to deal with int8 data with R. AFAIK R does only handle int4 with `as.integer` function [1]. I wonder: 1. what is the better approach to handle int8 ? `as.character` ? `as.numeric` ? 2. is there any plan to handle int8 in the future ? As you might know, int4 is to small to deal with earth population right now. Thanks for you ideas, int8 eg: human_id

https://bugs.freedesktop.org/show_bug.cgi?id=90626 Bug ID: 90626 Summary: HP ZBook 15 nouveau driver hangup for kernel >= 3.19 Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: critical Priority: medium Component: Driver/nouveau Assignee:

Hi, With help from Oleg we got the right patches applied and NFS working well. Maximum performance was about 60 MB/sec. Last week that dropped to about 12.5 MB/sec and I cannot find a reason. Lustre clients all obtain 100+ MB/sec on GigE. Each OST is good for 270 MB/sec. When mounting the client on one of the OSSs I get 230 MB/sec. Seems the speed is there. How can NFS and Lustre be tuned

On 01-12-15, Samuel Pitoiset wrote: >>> Ok, here is a MMT trace of vectorAdd: >>> >>> https://fedorapeople.org/~jwrdegoede/vectorAdd.log.gz >> >> Hi Hans, >> >> Thanks a lot. > > Well, I didn't know but Martin has a GK208... > I just tested the compute support on his card and ... it works without > any changes. :-)