Re: [Nouveau] GM108GLM?
Hi Karol, Thank you for both the suggestion and for your insight. Best regards, Sune Mølgaard On 2016-12-08 15:32, Karol Herbst wrote: > 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 favour of intel, because Intel doesn't > need to copy all the frames through the bus. > > 2016-12-08 14:46 GMT+01:00 Sune Mølgaard <s...@translucent.dk>: >> 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 near a match for the built-in >> Broadwell-U with i915, which runs at ~1400 - ~1900 FPS. >> >> Thank you very much - I'll keep a look-out for future improvements :-) >> >> Best regards, >> >> Sune Mølgaard >> >> On 2016-12-08 14:14, Karol Herbst wrote: >>> 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. >>> >>> 2016-12-08 13:25 GMT+01:00 Sune Mølgaard <s...@translucent.dk>: >>>> 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 4.9, so 4.10 is required. >>>>> >>>>> Greetings. >>>>> >>>>> On 7 December 2016 10:26:44 a.m. GMT+01:00, "Sune Mølgaard" >>>>> <s...@translucent.dk> wrote: >>>>>> 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 :08:00.0: >>>>>> clk: unable to find matching pll values >>>>>> >>>>>> a number of time as then soft lockup. >>>>>> >>>>>> Very much akin to >>>>>> https://people.freedesktop.org/~cbrill/dri-log/?channel=nouveau=2016-04-14 >>>>>> , actually, so what I gather from that is that I need to provide you >>>>>> guys with some info about the card, so which do you need, and how do I >>>>>> extract them? >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Sune Mølgaard >>>>>> >>>>>> On 2016-10-27 11:06, Pierre Moreau wrote: >>>>>>> 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 >>>>>>
Re: [Nouveau] GM108GLM?
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 near a match for the built-in Broadwell-U with i915, which runs at ~1400 - ~1900 FPS. Thank you very much - I'll keep a look-out for future improvements :-) Best regards, Sune Mølgaard On 2016-12-08 14:14, Karol Herbst wrote: > 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. > > 2016-12-08 13:25 GMT+01:00 Sune Mølgaard <s...@translucent.dk>: >> 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 4.9, so 4.10 is required. >>> >>> Greetings. >>> >>> On 7 December 2016 10:26:44 a.m. GMT+01:00, "Sune Mølgaard" >>> <s...@translucent.dk> wrote: >>>> 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 :08:00.0: >>>> clk: unable to find matching pll values >>>> >>>> a number of time as then soft lockup. >>>> >>>> Very much akin to >>>> https://people.freedesktop.org/~cbrill/dri-log/?channel=nouveau=2016-04-14 >>>> , actually, so what I gather from that is that I need to provide you >>>> guys with some info about the card, so which do you need, and how do I >>>> extract them? >>>> >>>> Best regards, >>>> >>>> Sune Mølgaard >>>> >>>> On 2016-10-27 11:06, Pierre Moreau wrote: >>>>> 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 >>>>> [2]: https://github.com/imirkin/xf86-video-nouveau/ >>>>> >>>>> >>>>> On 11:29 am - Oct 18 2016, Sune Mølgaard wrote: >>>>>> 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 >>>>>>> >>>> https://github.com/skeggsb/nouveau/commit/3da1f2a19e5e8dc8d68a4400d9cca01c64ecd59e). >>>>>>> I guess it will make it into 4.7. >>>>>>> >>>>>>> Pierre >>>>>> >>>>> >>>>>> lspci - >>>>>> 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI >>>&g
Re: [Nouveau] GM108GLM?
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 4.9, so 4.10 is required. > > Greetings. > > On 7 December 2016 10:26:44 a.m. GMT+01:00, "Sune Mølgaard" > <s...@translucent.dk> wrote: >> 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 :08:00.0: >> clk: unable to find matching pll values >> >> a number of time as then soft lockup. >> >> Very much akin to >> https://people.freedesktop.org/~cbrill/dri-log/?channel=nouveau=2016-04-14 >> , actually, so what I gather from that is that I need to provide you >> guys with some info about the card, so which do you need, and how do I >> extract them? >> >> Best regards, >> >> Sune Mølgaard >> >> On 2016-10-27 11:06, Pierre Moreau wrote: >>> 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 >>> [2]: https://github.com/imirkin/xf86-video-nouveau/ >>> >>> >>> On 11:29 am - Oct 18 2016, Sune Mølgaard wrote: >>>> 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 >>>>> >> https://github.com/skeggsb/nouveau/commit/3da1f2a19e5e8dc8d68a4400d9cca01c64ecd59e). >>>>> I guess it will make it into 4.7. >>>>> >>>>> Pierre >>>> >>> >>>> lspci - >>>> 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI >> (rev 09) >>>>Subsystem: Lenovo Broadwell-U Host Bridge -OPI >>>>Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx- >>>>Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- >> SERR- >>>Latency: 0 >>>>Capabilities: >>>>Kernel driver in use: bdw_uncore >>>> >>>> 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U >> Integrated Graphics (rev 09) (prog-if 00 [VGA controller]) >>>>Subsystem: Lenovo Broadwell-U Integrated Graphics >>>>Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx+ >>>>Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- >> SERR- >>>Latency: 0 >>>>Interrupt: pin A routed to IRQ 49 >>>>Region 0: Memory at f200 (64-bit, non-prefetchable) [size=16M] >>>>Region 2: Memory at c000 (64-bit, prefetchable) [size=512M] >>>>Region 4: I/O ports at 4000 [size=64] >>>>[virtual] Expansion ROM at 000c [disabled] [size=128K] >>>>Capabilities: >>>>Kernel driver in use: i915 >>>>Kernel modules: i915 >>>> >>>> 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller >> (rev 09) >>>>Subsystem: Lenovo Broadwell-U Audio Controller >>>>Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx+ >>>>Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- >> SERR- >>>Latency: 0, Cache Line Size: 6
Re: [Nouveau] GM108GLM?
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 :08:00.0: clk: unable to find matching pll values a number of time as then soft lockup. Very much akin to https://people.freedesktop.org/~cbrill/dri-log/?channel=nouveau=2016-04-14 , actually, so what I gather from that is that I need to provide you guys with some info about the card, so which do you need, and how do I extract them? Best regards, Sune Mølgaard On 2016-10-27 11:06, Pierre Moreau wrote: > 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 > [2]: https://github.com/imirkin/xf86-video-nouveau/ > > > On 11:29 am - Oct 18 2016, Sune Mølgaard wrote: >> 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 >>> https://github.com/skeggsb/nouveau/commit/3da1f2a19e5e8dc8d68a4400d9cca01c64ecd59e). >>> I guess it will make it into 4.7. >>> >>> Pierre >> > >> lspci - >> 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) >> Subsystem: Lenovo Broadwell-U Host Bridge -OPI >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- > <MAbort+ >SERR- > Latency: 0 >> Capabilities: >> Kernel driver in use: bdw_uncore >> >> 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated >> Graphics (rev 09) (prog-if 00 [VGA controller]) >> Subsystem: Lenovo Broadwell-U Integrated Graphics >> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx+ >> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- > SERR- > Latency: 0 >> Interrupt: pin A routed to IRQ 49 >> Region 0: Memory at f200 (64-bit, non-prefetchable) [size=16M] >> Region 2: Memory at c000 (64-bit, prefetchable) [size=512M] >> Region 4: I/O ports at 4000 [size=64] >> [virtual] Expansion ROM at 000c [disabled] [size=128K] >> Capabilities: >> Kernel driver in use: i915 >> Kernel modules: i915 >> >> 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) >> Subsystem: Lenovo Broadwell-U Audio Controller >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx+ >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > SERR- > Latency: 0, Cache Line Size: 64 bytes >> Interrupt: pin A routed to IRQ 50 >> Region 0: Memory at f423 (64-bit, non-prefetchable) [size=16K] >> Capabilities: >> Kernel driver in use: snd_hda_intel >> Kernel modules: snd_hda_intel >> >> 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI >> Controller (rev 03) (prog-if 30 [XHCI]) >> Subsystem: Lenovo Wildcat Point-LP USB xHCI Controller >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx+ >> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >> SERR- > Latency: 0 >> Interrupt: pin A routed to IRQ 42 >> Region 0: Memory at f422 (64-bit, non-prefetchable) [size=64K] >> Capabilities: >> Kernel driver in use: xhci_hcd >> >> 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI >> Controller #1 (rev 03) >> Subsystem: Lenovo Wildcat Point-LP MEI Controller >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx+ >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- &
Re: [Nouveau] GM108GLM?
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 > https://github.com/skeggsb/nouveau/commit/3da1f2a19e5e8dc8d68a4400d9cca01c64ecd59e). > I guess it will make it into 4.7. > > Pierre lspci - 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) Subsystem: Lenovo Broadwell-U Host Bridge -OPI Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: bdw_uncore 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) Subsystem: Lenovo Broadwell-U Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) (prog-if 30 [XHCI]) Subsystem: Lenovo Wildcat Point-LP USB xHCI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) Subsystem: Lenovo Wildcat Point-LP MEI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-V (rev 03) Subsystem: Lenovo Ethernet Connection (3) I218-V Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: e1000e Kernel modules: e1000e 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) Subsystem: Lenovo Wildcat Point-LP High Definition Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #6 (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03) (prog-if 20 [EHCI]) Sub
Re: [Nouveau] GM108GLM?
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 Mirkin wrote: >> 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.mor...@free.fr> wrote: >>> 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 help, apart from the info below? >>>> >>>> Best regards, >>>> >>>> Sune Mølgaard >>>> >>>> dmesg |grep -i nouveau >>>> [1.164919] nouveau :08:00.0: unknown chipset (1183a0a2) >>>> [1.164943] nouveau: probe of :08:00.0 failed with error -12 >>>> >>>> lspci|grep -i nvidi >>>> 08:00.0 3D controller: NVIDIA Corporation GM108GLM [Quadro K620M] (rev a2) >>>> ___ >>>> Nouveau mailing list >>>> Nouveau@lists.freedesktop.org >>>> https://lists.freedesktop.org/mailman/listinfo/nouveau >>> >>> ___ >>> Nouveau mailing list >>> Nouveau@lists.freedesktop.org >>> https://lists.freedesktop.org/mailman/listinfo/nouveau >>> >> ___ >> Nouveau mailing list >> Nouveau@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/nouveau signature.asc Description: OpenPGP digital signature ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] GM108GLM?
Hiya, Is there any change for Quadro K620M support at some point in time, and what can I do to help, apart from the info below? Best regards, Sune Mølgaard dmesg |grep -i nouveau [1.164919] nouveau :08:00.0: unknown chipset (1183a0a2) [1.164943] nouveau: probe of :08:00.0 failed with error -12 lspci|grep -i nvidi 08:00.0 3D controller: NVIDIA Corporation GM108GLM [Quadro K620M] (rev a2) ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Fwd: [bisected] nouveau failure with 3.9-rc1 and ongoing
Marcin Slusarz wrote: I think it may be already fixed by commit 94f54f5336aac6801f2a14dcb12467e41b35456a drm/nv50: encoder creation failure doesn't mean full init failure (post 3.9-rc2) With the latest 3.9-rc2+ git, I got past the KMS init blackout and into X, but I got a panic shortly after. Unfortunately, the trace was too lengthy to see in which module, and since it wasn't captured /var/log/syslog, I have no idea whether it has anything to do with nouveau or something else. tl;dr: It would seem that the commit fixes the specific bug I reported, but my system isn't functional. Thank you so far anyway, Sune Mølgaard -- Nothing exists except atoms and empty space; everything else is opinion. - Democritus ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] Fwd: [bisected] nouveau failure with 3.9-rc1 and ongoing
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 s...@molgaard.org To: linux-ker...@vger.kernel.org Hiya, Between 3.8 and 3.9-rc1, the following occurs: Upon boot, when KMS kicks in, I get a blank screen. Keyboard responds correctly to Num Lock on/off, but machine is unreachable on the network. Git bisection says: eb6313add6dddf07ea3e50c4caa33a9c3b2379f1 is the first bad commit commit eb6313add6dddf07ea3e50c4caa33a9c3b2379f1 Author: Ben Skeggs bske...@redhat.com Date: Mon Feb 11 09:52:58 2013 +1000 drm/nv50: initial kms support for off-chip TMDS/DP encoders Signed-off-by: Ben Skeggs bske...@redhat.com :04 04 41f69d26a80082e19d3c76e6556ad5ef9eb2677d 216d501e053e9d05136929593e90259c2e59dff0 M drivers But even though I marked that last bisection kernel good (since it didn't cause a black-out), it does have problems, namely that GTK themes are reset, and xrandr seems non-functional, inasmuch as my left-ward, secondary screen now seems to be treated as being situated to the right. No previous kernel in the bisection exercise caused anything of the like. I'd be happy to try out any and all patches proposed, and as for the physical card, this is the relevant part: 02:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce 9800 GT] (rev a2) Please let me know if there is anything else I can do to help resolve this! Best regards, Sune Mølgaard -- What a gorgeous day. What effulgent sunshine. It was a day of this sort the McGillicuddy brothers murdered their mother with an axe. - W. C. Fields ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
