similar to: GM108GLM?

Actually GM108 is not one of the recognized chips. Someone needs to go through and check that its goldens didn't change. Nobody's done that. See https://bugs.freedesktop.org/show_bug.cgi?id=89558 On Thu, Mar 31, 2016 at 4:57 PM, Pierre Moreau <pierre.morrow at free.fr> wrote: > Hello, > > Acceleration support for GM107 was merged in kernel 4.1, and modesetting > support

Is there anything I can do in this regard? /smo On 2016-03-31 23:12, Pierre Moreau wrote: > Oh, hum, GM108 is NV118 and not NV108 which is Gk208… My bad! > > SMF from the bug report seemed to have some working setup, and since he didn't > pinged back, I guess it's working nicely. But some more checking might still be > needed? > > On 04:59 PM - Mar 31 2016, Ilia

Hello, A patch was merged yesterday to recognise GM108 (see https://github.com/skeggsb/nouveau/commit/3da1f2a19e5e8dc8d68a4400d9cca01c64ecd59e). I guess it will make it into 4.7. Pierre On 12:14 PM - Apr 18 2016, Sune Mølgaard wrote: > Is there anything I can do in this regard? > > /smo > > On 2016-03-31 23:12, Pierre Moreau wrote: > > Oh, hum, GM108 is NV118 and not

Hello, Acceleration support for GM107 was merged in kernel 4.1, and modesetting support was added to 3.15. Which kernel version did you try? The GM108 chipset seems to be recognised since at least 2015/08/20. Regards, Pierre Moreau On 02:55 PM - Mar 29 2016, Sune Mølgaard wrote: > Hiya, > > Is there any change for Quadro K620M support at some point in time, and > what can I do to

Oh, hum, GM108 is NV118 and not NV108 which is Gk208… My bad! SMF from the bug report seemed to have some working setup, and since he didn't pinged back, I guess it's working nicely. But some more checking might still be needed? On 04:59 PM - Mar 31 2016, Ilia Mirkin wrote: > Actually GM108 is not one of the recognized chips. Someone needs to go > through and check that its goldens

Aha! That seems to do it. If I interpret correctly, it doesn't set it quite to full power, though, but it's certainly an improvement: 07: core 405 MHz memory 810 MHz 0a: core 270-1124 MHz memory 1600 MHz 0f: core 270-1124 MHz memory 2002 MHz AC DC * AC: core 1012 MHz memory 2002 MHz A short run of glmark2 shows aver 100% improvement to ~550 FPS. Interestingly, it's still nowhere

Hi, With drm-next from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/2016-12-08/ I don't get the error messages, but I still get a soft cpu lockup. What info would you need from me to get it working? Best regards, Sune Mølgaard On 2016-12-08 08:10, Karol Herbst wrote: > hi, > > give the drm-next kernel tree a try. Sadly the reclocking improvements didn't land with

Hi, It would seem like it (attachments are from 4.9-rc1, btw), but it doesn't look like there is any support in the Xorg driver. How can I help with that? Best regards, Sune Mølgaard Translucent ApS On 2016-04-22 09:33, Pierre Moreau wrote: > Hello, > > A patch was merged yesterday to recognise GM108 (see >

Hi again, It works :-) Reclocking, however, is another kettle of fish. Trying #echo 0f > /sys/kernel/debug/dri/0/pstate hangs X. Trying the same with no X running reveals: Dec 7 10:08:42 dell-smo kernel: [ 728.831020] nouveau 0000:08:00.0: clk: unable to find matching pll values a number of time as then soft lockup. Very much akin to

you can boot with nouveau.config=NvBoost=2 to enable higher clocks, but that won't fill in the difference compared to Intel. For this there are some changes needed on the mesa side regarding scheduling. Also keep in mind, that PCIe is an important bottleneck here, because the GPU can't push frames fast enough through the bus, that's why any "high FPS" benchmark will be in

also you can't change the clocks when there is nothing running on the GPU. I have some patches pending for this in another series, but maybe I may be able toe extract those fixes. Changing the clocks while something is running shouldn't cause any troubles. Alternatively if you don't care about power consumption, you can boot with nouveau.runpm=0 so that the gpu is always on.

hi, give the drm-next kernel tree a try. Sadly the reclocking improvements didn't land with 4.9, so 4.10 is required. Greetings. On 7 December 2016 10:26:44 a.m. GMT+01:00, "Sune Mølgaard" <smo at translucent.dk> wrote: >Hi again, > >It works :-) > >Reclocking, however, is another kettle of fish. > >Trying #echo 0f > /sys/kernel/debug/dri/0/pstate

Hello, The idea was to use the modesetting DDX instead of Nouveau’s one for Maxwell+ as EXA was [broken][1]. But you can give a try at Ilia’s [patches][2], which fix the Nouveau DDX for GM10x and GM20x (I don’t think it has been tested on a GM108 yet). Best regards, Pierre Moreau [1]: https://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=3e2e0faa2ee1cce9c1bb5c7ad80d0592460f3edc

Hiya, I sent the enclosed email to linux-kernel before realizing that it would, perhaps, be more proper to send it here, which I hereby do. I shall be happy to try out any and all patches. Best regards, Sune M?lgaard -------- Original Message -------- Subject: [bisected] nouveau failure with 3.9-rc1 and ongoing Date: Tue, 12 Mar 2013 19:57:55 +0100 From: Sune M?lgaard <sune at

https://bugs.freedesktop.org/show_bug.cgi?id=62351 Priority: medium Bug ID: 62351 Assignee: nouveau at lists.freedesktop.org Summary: Segfault in nouveau_dri.so Severity: major Classification: Unclassified OS: Linux (All) Reporter: sune at molgaard.org Hardware: x86-64 (AMD64) Status: NEW

Just wondering... Would it be possible for the list software to set the reply-to: field to compiz@lists.freedesktop.org? Best regards, Sune M?lgaard -- I can resist everything except temptation. - Oscar Wilde (1854-1900)

On 18.05.2015 01:46, Ilia Mirkin wrote: > Your errors are most likely due to: > > [ 2.421428] nouveau [ PFB][0000:01:00.0] RAM size: 1975398418 MiB > > I'm guessing you don't *actually* have 1.9PB of VRAM. At least one > other person with a GM108 was seeing a similar issue. You're getting a > bunch of other failed reads, looks like we're somehow not

I got a new laptop as my old one died: an HP Probook 470 G4.? I installed Centos 7 1511. The laptop has a Kaby Lake i5 CPU and an? 01:00.0 3D controller: NVIDIA Corporation Device 134e (rev a2).? Fedora recognizes it as a GM108M/930MX. This may give some hints, but it is not that the standard kernel does not support it, this output comes from the 4.8.7 mainline kernel which should support this

Hi Ben, David and Daniel , First of all happy new year. Based on advice of Greg K-H herewith a mail about a number of Nouveau issues with my laptop. I installed various Kali linux versions up to Linux 4.20.0-rc7 (downloaded, compiled and installed) on a Samsung NP900X5N laptop and have an issue with the driver after loading. My configuration: - i7 7500 - 16 gb / 256 gb ssd - nvidia 940MX

https://bugs.freedesktop.org/show_bug.cgi?id=89558 Bug ID: 89558 Summary: Unknown chipset error for GeForce 840M Product: xorg Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at