[Nouveau] Should I expect nouveau on 4.6 to work on a GM206?
On Sun, Jun 26, 2016 at 2:04 PM, Andy Lutomirski wrote: > Eeek! My desire to hack on EXA is pretty low. If there was some Well, the EXA hacking was all done a long time ago. You'd just need to add support for sticking 4 vertices into a buffer. (Maxwell killed direct vertex submit, which was incredibly convenient for the DDX.) > straightforward way I could try to figure out why GLAMOR was so slow, > maybe I could fiddle with that a bit. Upgrade mesa & pray. I think that X11 can end up being pretty glReadPixels-heavy, which in a UMA system is ~free, but much more expensive when the FB is in VRAM. Recently some changes were committed to cache the entire texture in a staging texture if someone does a lot of readpixels on it. Could help. Or could be totally unrelated. You could do an apitrace of the X server (github.com/apitrace/apitrace) and then analyze what all it's doing. > > FWIW, my i915-based laptop uses the modesetting driver and GLAMOR as > well, and it's plenty fast, so I don't think the problem is that > GLAMOR is inherently terrible at legacy X11 operations. Different workloads, I suppose. I had to use GLAMOR on a SKL while the regular ddx was still lacking support for it, and my favorite screensaver was unbearably slow on it (xlock -mode wator, in case you're curious). [And regular usage was also not great, but not to the point of frustration.] It runs plenty fast with the SNA backend though. -ilia
[Nouveau] Should I expect nouveau on 4.6 to work on a GM206?
On Sun, Jun 26, 2016 at 1:49 PM, Andy Lutomirski wrote: > On Sun, May 29, 2016 at 12:27 PM, Andy Lutomirski wrote: >> On Sun, May 29, 2016 at 12:22 PM, Ilia Mirkin >> wrote: >>> On Sun, May 29, 2016 at 3:07 PM, Andy Lutomirski wrote: On Sat, May 28, 2016 at 5:48 PM, Ilia Mirkin wrote: > Do you have mesa 11.2 or later? GM20x support was only added in mesa 11.2. > I just upgraded to 11.2. I'm getting errors like this in the log: [ 5383.723240] nouveau :09:00.0: fifo: read fault at 011000 engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 [007f9ed000 unknown] [ 5398.722676] nouveau :09:00.0: systemd-logind[30778]: failed to idle channel 2 [systemd-logind[30778]] [ 5413.722853] nouveau :09:00.0: systemd-logind[30778]: failed to idle channel 2 [systemd-logind[30778]] and the display output in general is unreliable enough that I'm having trouble telling whether the performance is remotely reasonable. >>> >>> If you're having trouble telling, that means it's not :) The error you >>> pasted is quite odd. Was there anything in the log before those >>> messages? If there's no channel associated, that means that it's the >>> background copying between vram and sysmem? Not sure. >> >> Don't get too excited yet. In the process of upgrading mesa, I >> managed to boot 4.5 without noticing. I'll post back later today with >> actual valid test results. >> > > I replaced the monitor (turns out that my monitor had a known DP > problem), and now the screen lights up reliably. I still get Great to hear! > occasional log lines like this: > > [Jun26 09:25] nouveau :09:00.0: fifo: FB_FLUSH_TIMEOUT > [Jun26 09:30] nouveau :09:00.0: fifo: FB_FLUSH_TIMEOUT > [Jun26 09:32] nouveau :09:00.0: fifo: CHSW_ERROR 0004 > [ +0.000162] nouveau :09:00.0: fifo: CHSW_ERROR 0005 These don't sound good at all! > [Jun26 09:46] nouveau :09:00.0: disp: outp 04:0006:0f44: link > training failed > [ +0.107894] nouveau :09:00.0: disp: outp 04:0006:0f44: link > training failed These are surprising if your monitor is working. Usually it means "couldn't establish link with the monitor". Perhaps something forces it to retry and it eventually succeeds. > > but they aren't causing an obvious problem. > >>> >>> Note that with maxwell we have yet to add EXA support to >>> xf86-video-nouveau, so you're ending up with GLAMOR (and Ben and I >>> disagree on whether EXA support should be added in the first place). >>> There was also an issue that glamor was hitting with nouveau which >>> appears to have dissipated, either due to a change in nouveau or a >>> change in glamor. So you might consider upgrading to Xorg 1.18.3 (as >>> glamor is part of X). > > I do have a serious performance issue, though: when I scroll in > Firefox (default configuration), the whole system drops to ~1fps or > less and, if I scroll enough (even putting the mouse over a simple > page like start.fedoraproject.org and flicking the wheel up and down a > few times), the entire desktop will become unusable for several > seconds. I seem to have this problem under X and under Wayland. > > For better or for worse, forcing Firefox's layers acceleration on > fixes the problem and scrolling is fast. > > I have no idea whether this is an X problem, a gnome-shell problem, a > mesa problem, a kernel problem, or something else. I believe the issue is with GLAMOR, but I'm not sure - in my experience, GLAMOR is slow as molasses for actual X11 ops that aren't "take this composited image and stick it on the screen", and the fact that you are on the lowest perf level of your GPU isn't helping your cause. Turning on acceleration in firefox probably makes it use more optimized GL paths than having some X11 -> GL translation layer. If you're interested, I've a 95% (percentage made up) completed EXA backend for maxwell, but I don't have the hw, or, to be frank, the interest in completing it (as a result of NVIDIA's creation of these locked down, actively anti-open source GPUs). However you're welcome to hack on it if you like - https://github.com/imirkin/xf86-video-nouveau/commit/abf0933a236b6069f42f86ad5b0bf5bbab28e0d6 - if you ask in #nouveau on irc.freenode.net, would be happy to talk about what all needs finishing. -ilia
[Nouveau] Should I expect nouveau on 4.6 to work on a GM206?
On Sun, Jun 26, 2016 at 10:59 AM, Ilia Mirkin wrote: > On Sun, Jun 26, 2016 at 1:49 PM, Andy Lutomirski > wrote: >> On Sun, May 29, 2016 at 12:27 PM, Andy Lutomirski wrote: >>> On Sun, May 29, 2016 at 12:22 PM, Ilia Mirkin >>> wrote: On Sun, May 29, 2016 at 3:07 PM, Andy Lutomirski wrote: > On Sat, May 28, 2016 at 5:48 PM, Ilia Mirkin > wrote: >> Do you have mesa 11.2 or later? GM20x support was only added in mesa >> 11.2. >> > > I just upgraded to 11.2. I'm getting errors like this in the log: > > [ 5383.723240] nouveau :09:00.0: fifo: read fault at 011000 > engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 > [007f9ed000 unknown] > [ 5398.722676] nouveau :09:00.0: systemd-logind[30778]: failed to > idle channel 2 [systemd-logind[30778]] > [ 5413.722853] nouveau :09:00.0: systemd-logind[30778]: failed to > idle channel 2 [systemd-logind[30778]] > > and the display output in general is unreliable enough that I'm having > trouble telling whether the performance is remotely reasonable. If you're having trouble telling, that means it's not :) The error you pasted is quite odd. Was there anything in the log before those messages? If there's no channel associated, that means that it's the background copying between vram and sysmem? Not sure. >>> >>> Don't get too excited yet. In the process of upgrading mesa, I >>> managed to boot 4.5 without noticing. I'll post back later today with >>> actual valid test results. >>> >> >> I replaced the monitor (turns out that my monitor had a known DP >> problem), and now the screen lights up reliably. I still get > > Great to hear! > >> occasional log lines like this: >> >> [Jun26 09:25] nouveau :09:00.0: fifo: FB_FLUSH_TIMEOUT >> [Jun26 09:30] nouveau :09:00.0: fifo: FB_FLUSH_TIMEOUT >> [Jun26 09:32] nouveau :09:00.0: fifo: CHSW_ERROR 0004 >> [ +0.000162] nouveau :09:00.0: fifo: CHSW_ERROR 0005 > > These don't sound good at all! > >> [Jun26 09:46] nouveau :09:00.0: disp: outp 04:0006:0f44: link >> training failed >> [ +0.107894] nouveau :09:00.0: disp: outp 04:0006:0f44: link >> training failed > > These are surprising if your monitor is working. Usually it means > "couldn't establish link with the monitor". Perhaps something forces > it to retry and it eventually succeeds. Given the timing, I'm guessing that it tries a couple of times and eventually works. Given that the monitor is a newer, "fixed" revision of a known-seriously-broken Dell monitor, it wouldn't shock me if what's actually happening is that the monitor uses buggy DP hardware and the "fixed" firmware A03 actually works by forcing several retries when link training fails (as opposed to what A00 - A02 did, which seemed to involve failing a few times and then crashing, sometimes hard enough that even the monitor power button stopped working). > >> >> but they aren't causing an obvious problem. >> Note that with maxwell we have yet to add EXA support to xf86-video-nouveau, so you're ending up with GLAMOR (and Ben and I disagree on whether EXA support should be added in the first place). There was also an issue that glamor was hitting with nouveau which appears to have dissipated, either due to a change in nouveau or a change in glamor. So you might consider upgrading to Xorg 1.18.3 (as glamor is part of X). >> >> I do have a serious performance issue, though: when I scroll in >> Firefox (default configuration), the whole system drops to ~1fps or >> less and, if I scroll enough (even putting the mouse over a simple >> page like start.fedoraproject.org and flicking the wheel up and down a >> few times), the entire desktop will become unusable for several >> seconds. I seem to have this problem under X and under Wayland. >> >> For better or for worse, forcing Firefox's layers acceleration on >> fixes the problem and scrolling is fast. >> >> I have no idea whether this is an X problem, a gnome-shell problem, a >> mesa problem, a kernel problem, or something else. > > I believe the issue is with GLAMOR, but I'm not sure - in my > experience, GLAMOR is slow as molasses for actual X11 ops that aren't > "take this composited image and stick it on the screen", and the fact > that you are on the lowest perf level of your GPU isn't helping your > cause. Turning on acceleration in firefox probably makes it use more > optimized GL paths than having some X11 -> GL translation layer. > > If you're interested, I've a 95% (percentage made up) completed EXA > backend for maxwell, but I don't have the hw, or, to be frank, the > interest in completing it (as a result of NVIDIA's creation of these > locked down, actively anti-open source GPUs). However you're welcome > to hack on it if you like - > https://github.com/imirkin/xf86-video-nouveau/commit/abf0933a236b6069f42f86ad5b0bf5bbab28e0d6 > - if you ask
[Nouveau] Should I expect nouveau on 4.6 to work on a GM206?
On Sun, May 29, 2016 at 12:27 PM, Andy Lutomirski wrote: > On Sun, May 29, 2016 at 12:22 PM, Ilia Mirkin wrote: >> On Sun, May 29, 2016 at 3:07 PM, Andy Lutomirski wrote: >>> On Sat, May 28, 2016 at 5:48 PM, Ilia Mirkin >>> wrote: Do you have mesa 11.2 or later? GM20x support was only added in mesa 11.2. >>> >>> I just upgraded to 11.2. I'm getting errors like this in the log: >>> >>> [ 5383.723240] nouveau :09:00.0: fifo: read fault at 011000 >>> engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 >>> [007f9ed000 unknown] >>> [ 5398.722676] nouveau :09:00.0: systemd-logind[30778]: failed to >>> idle channel 2 [systemd-logind[30778]] >>> [ 5413.722853] nouveau :09:00.0: systemd-logind[30778]: failed to >>> idle channel 2 [systemd-logind[30778]] >>> >>> and the display output in general is unreliable enough that I'm having >>> trouble telling whether the performance is remotely reasonable. >> >> If you're having trouble telling, that means it's not :) The error you >> pasted is quite odd. Was there anything in the log before those >> messages? If there's no channel associated, that means that it's the >> background copying between vram and sysmem? Not sure. > > Don't get too excited yet. In the process of upgrading mesa, I > managed to boot 4.5 without noticing. I'll post back later today with > actual valid test results. > I replaced the monitor (turns out that my monitor had a known DP problem), and now the screen lights up reliably. I still get occasional log lines like this: [Jun26 09:25] nouveau :09:00.0: fifo: FB_FLUSH_TIMEOUT [Jun26 09:30] nouveau :09:00.0: fifo: FB_FLUSH_TIMEOUT [Jun26 09:32] nouveau :09:00.0: fifo: CHSW_ERROR 0004 [ +0.000162] nouveau :09:00.0: fifo: CHSW_ERROR 0005 [Jun26 09:46] nouveau :09:00.0: disp: outp 04:0006:0f44: link training failed [ +0.107894] nouveau :09:00.0: disp: outp 04:0006:0f44: link training failed but they aren't causing an obvious problem. >> >> Note that with maxwell we have yet to add EXA support to >> xf86-video-nouveau, so you're ending up with GLAMOR (and Ben and I >> disagree on whether EXA support should be added in the first place). >> There was also an issue that glamor was hitting with nouveau which >> appears to have dissipated, either due to a change in nouveau or a >> change in glamor. So you might consider upgrading to Xorg 1.18.3 (as >> glamor is part of X). I do have a serious performance issue, though: when I scroll in Firefox (default configuration), the whole system drops to ~1fps or less and, if I scroll enough (even putting the mouse over a simple page like start.fedoraproject.org and flicking the wheel up and down a few times), the entire desktop will become unusable for several seconds. I seem to have this problem under X and under Wayland. For better or for worse, forcing Firefox's layers acceleration on fixes the problem and scrolling is fast. I have no idea whether this is an X problem, a gnome-shell problem, a mesa problem, a kernel problem, or something else.
[Nouveau] Should I expect nouveau on 4.6 to work on a GM206?
On Sun, May 29, 2016 at 3:07 PM, Andy Lutomirski wrote: > On Sat, May 28, 2016 at 5:48 PM, Ilia Mirkin wrote: >> Do you have mesa 11.2 or later? GM20x support was only added in mesa 11.2. >> > > I just upgraded to 11.2. I'm getting errors like this in the log: > > [ 5383.723240] nouveau :09:00.0: fifo: read fault at 011000 > engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 > [007f9ed000 unknown] > [ 5398.722676] nouveau :09:00.0: systemd-logind[30778]: failed to > idle channel 2 [systemd-logind[30778]] > [ 5413.722853] nouveau :09:00.0: systemd-logind[30778]: failed to > idle channel 2 [systemd-logind[30778]] > > and the display output in general is unreliable enough that I'm having > trouble telling whether the performance is remotely reasonable. If you're having trouble telling, that means it's not :) The error you pasted is quite odd. Was there anything in the log before those messages? If there's no channel associated, that means that it's the background copying between vram and sysmem? Not sure. Note that with maxwell we have yet to add EXA support to xf86-video-nouveau, so you're ending up with GLAMOR (and Ben and I disagree on whether EXA support should be added in the first place). There was also an issue that glamor was hitting with nouveau which appears to have dissipated, either due to a change in nouveau or a change in glamor. So you might consider upgrading to Xorg 1.18.3 (as glamor is part of X). FWIW a few other people have been using GM20x without incident, but this can all be very sensitive to your desktop/etc. Lots of things like to use GL nowadays - I stick to a more classic desktop - no compositor, simple window manager, etc. -ilia
[Nouveau] Should I expect nouveau on 4.6 to work on a GM206?
On Sun, May 29, 2016 at 12:22 PM, Ilia Mirkin wrote: > On Sun, May 29, 2016 at 3:07 PM, Andy Lutomirski wrote: >> On Sat, May 28, 2016 at 5:48 PM, Ilia Mirkin wrote: >>> Do you have mesa 11.2 or later? GM20x support was only added in mesa 11.2. >>> >> >> I just upgraded to 11.2. I'm getting errors like this in the log: >> >> [ 5383.723240] nouveau :09:00.0: fifo: read fault at 011000 >> engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 >> [007f9ed000 unknown] >> [ 5398.722676] nouveau :09:00.0: systemd-logind[30778]: failed to >> idle channel 2 [systemd-logind[30778]] >> [ 5413.722853] nouveau :09:00.0: systemd-logind[30778]: failed to >> idle channel 2 [systemd-logind[30778]] >> >> and the display output in general is unreliable enough that I'm having >> trouble telling whether the performance is remotely reasonable. > > If you're having trouble telling, that means it's not :) The error you > pasted is quite odd. Was there anything in the log before those > messages? If there's no channel associated, that means that it's the > background copying between vram and sysmem? Not sure. Don't get too excited yet. In the process of upgrading mesa, I managed to boot 4.5 without noticing. I'll post back later today with actual valid test results. > > Note that with maxwell we have yet to add EXA support to > xf86-video-nouveau, so you're ending up with GLAMOR (and Ben and I > disagree on whether EXA support should be added in the first place). > There was also an issue that glamor was hitting with nouveau which > appears to have dissipated, either due to a change in nouveau or a > change in glamor. So you might consider upgrading to Xorg 1.18.3 (as > glamor is part of X). > > FWIW a few other people have been using GM20x without incident, but > this can all be very sensitive to your desktop/etc. Lots of things > like to use GL nowadays - I stick to a more classic desktop - no > compositor, simple window manager, etc. This is GNOME 3 on Fedora 24 Beta. --Andy
[Nouveau] Should I expect nouveau on 4.6 to work on a GM206?
On Sat, May 28, 2016 at 5:48 PM, Ilia Mirkin wrote: > Do you have mesa 11.2 or later? GM20x support was only added in mesa 11.2. > I just upgraded to 11.2. I'm getting errors like this in the log: [ 5383.723240] nouveau :09:00.0: fifo: read fault at 011000 engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 [007f9ed000 unknown] [ 5398.722676] nouveau :09:00.0: systemd-logind[30778]: failed to idle channel 2 [systemd-logind[30778]] [ 5413.722853] nouveau :09:00.0: systemd-logind[30778]: failed to idle channel 2 [systemd-logind[30778]] and the display output in general is unreliable enough that I'm having trouble telling whether the performance is remotely reasonable. --Andy > Cheers, > > -ilia > > On Sat, May 28, 2016 at 4:51 PM, Andy Lutomirski wrote: >> I have the signed firmware (I think) and I'm running a fresh 4.6 >> kernel. I got an image to show up briefly, rendering the Fedora >> sign-in screen at something like one frame per ten seconds. But then >> I got all kinds of garbage, and I see: >> >> [ 719.300820] nouveau :09:00.0: disp: outp 04:0006:0f44: link >> training failed >> >> dmesg |grep nouveau says: >> >> [ 10.053162] fb: switching to nouveaufb from EFI VGA >> [ 10.053349] nouveau :09:00.0: NVIDIA GM206 (126010a1) >> [ 10.174033] nouveau :09:00.0: bios: version 84.06.0d.00.01 >> [ 10.174854] nouveau :09:00.0: disp: dcb 15 type 8 unknown >> [ 10.178375] nouveau :09:00.0: fb: 2048 MiB GDDR5 >> [ 10.202108] nouveau :09:00.0: DRM: VRAM: 2048 MiB >> [ 10.202109] nouveau :09:00.0: DRM: GART: 1048576 MiB >> [ 10.202113] nouveau :09:00.0: DRM: TMDS table version 2.0 >> [ 10.202114] nouveau :09:00.0: DRM: DCB version 4.1 >> [ 10.202116] nouveau :09:00.0: DRM: DCB outp 00: 01000f02 00020030 >> [ 10.202117] nouveau :09:00.0: DRM: DCB outp 01: 02000f00 >> [ 10.202118] nouveau :09:00.0: DRM: DCB outp 02: 02811f76 04400020 >> [ 10.202120] nouveau :09:00.0: DRM: DCB outp 03: 02011f72 00020020 >> [ 10.202121] nouveau :09:00.0: DRM: DCB outp 04: 04822f86 04400010 >> [ 10.202122] nouveau :09:00.0: DRM: DCB outp 05: 04022f82 00020010 >> [ 10.202123] nouveau :09:00.0: DRM: DCB outp 06: 04833f96 04400020 >> [ 10.202124] nouveau :09:00.0: DRM: DCB outp 07: 04033f92 00020020 >> [ 10.202125] nouveau :09:00.0: DRM: DCB outp 08: 02044f62 00020010 >> [ 10.202126] nouveau :09:00.0: DRM: DCB outp 15: 01df5ff8 >> [ 10.202127] nouveau :09:00.0: DRM: DCB conn 00: 1030 >> [ 10.202128] nouveau :09:00.0: DRM: DCB conn 01: 00020146 >> [ 10.202129] nouveau :09:00.0: DRM: DCB conn 02: 01000246 >> [ 10.202130] nouveau :09:00.0: DRM: DCB conn 03: 02000346 >> [ 10.202131] nouveau :09:00.0: DRM: DCB conn 04: 00010461 >> [ 10.202132] nouveau :09:00.0: DRM: DCB conn 05: 0570 >> [ 10.202134] nouveau :09:00.0: DRM: Pointer to flat panel table invalid >> [ 10.214683] nouveau :09:00.0: DRM: unknown connector type 70 >> [ 10.214728] nouveau :09:00.0: DRM: failed to create encoder 1/8/0: -19 >> [ 10.214730] nouveau :09:00.0: DRM: Unknown-1 has no encoders, removing >> [ 10.369691] nouveau :09:00.0: DRM: MM: using COPY for buffer copies >> [ 10.478561] nouveau :09:00.0: priv: GPC0: 419df4 (1e40820e) >> [ 10.478578] nouveau :09:00.0: priv: GPC1: 419df4 (1e40820e) >> [ 10.607100] nouveau :09:00.0: DRM: allocated 3840x2160 fb: >> 0x6, bo 88044aad7400 >> [ 10.607276] fbcon: nouveaufb (fb0) is primary device >> [ 10.607576] nouveau :09:00.0: fb0: nouveaufb frame buffer device >> [ 10.617064] [drm] Initialized nouveau 1.3.1 20120801 for >> :09:00.0 on minor 0 >> [ 719.282184] nouveau :09:00.0: disp: outp 04:0006:0f44: link >> training failed >> [ 719.300820] nouveau :09:00.0: disp: outp 04:0006:0f44: link >> training failed >> >> >> >> Thanks, >> Andy >> ___ >> Nouveau mailing list >> Nouveau at lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] Should I expect nouveau on 4.6 to work on a GM206?
Do you have mesa 11.2 or later? GM20x support was only added in mesa 11.2. Cheers, -ilia On Sat, May 28, 2016 at 4:51 PM, Andy Lutomirski wrote: > I have the signed firmware (I think) and I'm running a fresh 4.6 > kernel. I got an image to show up briefly, rendering the Fedora > sign-in screen at something like one frame per ten seconds. But then > I got all kinds of garbage, and I see: > > [ 719.300820] nouveau :09:00.0: disp: outp 04:0006:0f44: link > training failed > > dmesg |grep nouveau says: > > [ 10.053162] fb: switching to nouveaufb from EFI VGA > [ 10.053349] nouveau :09:00.0: NVIDIA GM206 (126010a1) > [ 10.174033] nouveau :09:00.0: bios: version 84.06.0d.00.01 > [ 10.174854] nouveau :09:00.0: disp: dcb 15 type 8 unknown > [ 10.178375] nouveau :09:00.0: fb: 2048 MiB GDDR5 > [ 10.202108] nouveau :09:00.0: DRM: VRAM: 2048 MiB > [ 10.202109] nouveau :09:00.0: DRM: GART: 1048576 MiB > [ 10.202113] nouveau :09:00.0: DRM: TMDS table version 2.0 > [ 10.202114] nouveau :09:00.0: DRM: DCB version 4.1 > [ 10.202116] nouveau :09:00.0: DRM: DCB outp 00: 01000f02 00020030 > [ 10.202117] nouveau :09:00.0: DRM: DCB outp 01: 02000f00 > [ 10.202118] nouveau :09:00.0: DRM: DCB outp 02: 02811f76 04400020 > [ 10.202120] nouveau :09:00.0: DRM: DCB outp 03: 02011f72 00020020 > [ 10.202121] nouveau :09:00.0: DRM: DCB outp 04: 04822f86 04400010 > [ 10.202122] nouveau :09:00.0: DRM: DCB outp 05: 04022f82 00020010 > [ 10.202123] nouveau :09:00.0: DRM: DCB outp 06: 04833f96 04400020 > [ 10.202124] nouveau :09:00.0: DRM: DCB outp 07: 04033f92 00020020 > [ 10.202125] nouveau :09:00.0: DRM: DCB outp 08: 02044f62 00020010 > [ 10.202126] nouveau :09:00.0: DRM: DCB outp 15: 01df5ff8 > [ 10.202127] nouveau :09:00.0: DRM: DCB conn 00: 1030 > [ 10.202128] nouveau :09:00.0: DRM: DCB conn 01: 00020146 > [ 10.202129] nouveau :09:00.0: DRM: DCB conn 02: 01000246 > [ 10.202130] nouveau :09:00.0: DRM: DCB conn 03: 02000346 > [ 10.202131] nouveau :09:00.0: DRM: DCB conn 04: 00010461 > [ 10.202132] nouveau :09:00.0: DRM: DCB conn 05: 0570 > [ 10.202134] nouveau :09:00.0: DRM: Pointer to flat panel table invalid > [ 10.214683] nouveau :09:00.0: DRM: unknown connector type 70 > [ 10.214728] nouveau :09:00.0: DRM: failed to create encoder 1/8/0: -19 > [ 10.214730] nouveau :09:00.0: DRM: Unknown-1 has no encoders, removing > [ 10.369691] nouveau :09:00.0: DRM: MM: using COPY for buffer copies > [ 10.478561] nouveau :09:00.0: priv: GPC0: 419df4 (1e40820e) > [ 10.478578] nouveau :09:00.0: priv: GPC1: 419df4 (1e40820e) > [ 10.607100] nouveau :09:00.0: DRM: allocated 3840x2160 fb: > 0x6, bo 88044aad7400 > [ 10.607276] fbcon: nouveaufb (fb0) is primary device > [ 10.607576] nouveau :09:00.0: fb0: nouveaufb frame buffer device > [ 10.617064] [drm] Initialized nouveau 1.3.1 20120801 for > :09:00.0 on minor 0 > [ 719.282184] nouveau :09:00.0: disp: outp 04:0006:0f44: link > training failed > [ 719.300820] nouveau :09:00.0: disp: outp 04:0006:0f44: link > training failed > > > > Thanks, > Andy > ___ > Nouveau mailing list > Nouveau at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/nouveau
Should I expect nouveau on 4.6 to work on a GM206?
I have the signed firmware (I think) and I'm running a fresh 4.6 kernel. I got an image to show up briefly, rendering the Fedora sign-in screen at something like one frame per ten seconds. But then I got all kinds of garbage, and I see: [ 719.300820] nouveau :09:00.0: disp: outp 04:0006:0f44: link training failed dmesg |grep nouveau says: [ 10.053162] fb: switching to nouveaufb from EFI VGA [ 10.053349] nouveau :09:00.0: NVIDIA GM206 (126010a1) [ 10.174033] nouveau :09:00.0: bios: version 84.06.0d.00.01 [ 10.174854] nouveau :09:00.0: disp: dcb 15 type 8 unknown [ 10.178375] nouveau :09:00.0: fb: 2048 MiB GDDR5 [ 10.202108] nouveau :09:00.0: DRM: VRAM: 2048 MiB [ 10.202109] nouveau :09:00.0: DRM: GART: 1048576 MiB [ 10.202113] nouveau :09:00.0: DRM: TMDS table version 2.0 [ 10.202114] nouveau :09:00.0: DRM: DCB version 4.1 [ 10.202116] nouveau :09:00.0: DRM: DCB outp 00: 01000f02 00020030 [ 10.202117] nouveau :09:00.0: DRM: DCB outp 01: 02000f00 [ 10.202118] nouveau :09:00.0: DRM: DCB outp 02: 02811f76 04400020 [ 10.202120] nouveau :09:00.0: DRM: DCB outp 03: 02011f72 00020020 [ 10.202121] nouveau :09:00.0: DRM: DCB outp 04: 04822f86 04400010 [ 10.202122] nouveau :09:00.0: DRM: DCB outp 05: 04022f82 00020010 [ 10.202123] nouveau :09:00.0: DRM: DCB outp 06: 04833f96 04400020 [ 10.202124] nouveau :09:00.0: DRM: DCB outp 07: 04033f92 00020020 [ 10.202125] nouveau :09:00.0: DRM: DCB outp 08: 02044f62 00020010 [ 10.202126] nouveau :09:00.0: DRM: DCB outp 15: 01df5ff8 [ 10.202127] nouveau :09:00.0: DRM: DCB conn 00: 1030 [ 10.202128] nouveau :09:00.0: DRM: DCB conn 01: 00020146 [ 10.202129] nouveau :09:00.0: DRM: DCB conn 02: 01000246 [ 10.202130] nouveau :09:00.0: DRM: DCB conn 03: 02000346 [ 10.202131] nouveau :09:00.0: DRM: DCB conn 04: 00010461 [ 10.202132] nouveau :09:00.0: DRM: DCB conn 05: 0570 [ 10.202134] nouveau :09:00.0: DRM: Pointer to flat panel table invalid [ 10.214683] nouveau :09:00.0: DRM: unknown connector type 70 [ 10.214728] nouveau :09:00.0: DRM: failed to create encoder 1/8/0: -19 [ 10.214730] nouveau :09:00.0: DRM: Unknown-1 has no encoders, removing [ 10.369691] nouveau :09:00.0: DRM: MM: using COPY for buffer copies [ 10.478561] nouveau :09:00.0: priv: GPC0: 419df4 (1e40820e) [ 10.478578] nouveau :09:00.0: priv: GPC1: 419df4 (1e40820e) [ 10.607100] nouveau :09:00.0: DRM: allocated 3840x2160 fb: 0x6, bo 88044aad7400 [ 10.607276] fbcon: nouveaufb (fb0) is primary device [ 10.607576] nouveau :09:00.0: fb0: nouveaufb frame buffer device [ 10.617064] [drm] Initialized nouveau 1.3.1 20120801 for :09:00.0 on minor 0 [ 719.282184] nouveau :09:00.0: disp: outp 04:0006:0f44: link training failed [ 719.300820] nouveau :09:00.0: disp: outp 04:0006:0f44: link training failed Thanks, Andy
