Nouveau - Oct 2015 - [Bug 92274] New: nouveau black screen and errors with two monitors attached

https://bugs.freedesktop.org/show_bug.cgi?id=92274

            Bug ID: 92274
           Summary: nouveau black screen and errors with two monitors
                    attached
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: joseph-thommes at gmx.de
        QA Contact: xorg-team at lists.x.org

Hello,
I switched from the proprietary nvidia-drivers to nouveau under Gentoo.
I use a Dual-Monitor Setup: one is connected to the DVI-I and the other one to
the HDMI output of my Nvidia GTX 770.
Under my Manjaro installation I use the proprietary driver and everything
works;
under Gentoo everything was fine with the nvidia-drivers, too.
Now I can boot without errors into Gentoo when only one of the monitors is
connected, no matter which one.
However, when both monitors are attached to the graphics card,
I cannot access a tty or my graphical login manger:
the screens turn off showing "no input signal".
Me not being able to access my Gentoo installation by booting into it when the
error happens,
I chrooted into it and used cat /var/log/dmesg.
I know that this is not what the nouveau reporting guide suggests for obtaining
a kernel log,
but if I run dmesg from my chrooted environment I obviously get the kernel log
of my Manjaro boot.
If there is another better way for obtaining the kernel log, please let me
know.

VBIOS is following in a few minutes.

If there is anything else missing, let me know.

lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 770]
(rev a1)

kernel version: x86-64 4.0.5-linux-gentoo
nouveau version: x11-drivers/xf86-video-nouveau-1.0.11
libdrm version: x11-libs/libdrm-2.4.59
mesa version: media-libs/mesa-10.3.7-r1
X server: x11-base/xorg-server-1.16.4

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151004/6bbd08b8/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #1 from joseph-thommes at gmx.de ---
Created attachment 118654
  --> https://bugs.freedesktop.org/attachment.cgi?id=118654&action=edit
dmesg from /var/log/dmesg

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151004/b91c6afb/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #2 from joseph-thommes at gmx.de ---
Created attachment 118655
  --> https://bugs.freedesktop.org/attachment.cgi?id=118655&action=edit
VBIOS

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151004/fc809af0/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #3 from joseph-thommes at gmx.de ---
Not sure if important, but the vbios is from Gentoo when only one monitor was
connected.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151004/d2d1ab09/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #4 from joseph-thommes at gmx.de ---
Created attachment 118677
  --> https://bugs.freedesktop.org/attachment.cgi?id=118677&action=edit
/var/log/dmesg with kernel command line added drm.debug=14 log_buf_len=16M

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151005/ee5edfcc/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #5 from joseph-thommes at gmx.de ---
Having in mind that this could also be a Gennto-specific Bug or could be a
badly configured kernel, do you have any suggestions for my kernel config?
I think I followed all instructions to get nouveau to work also due to it
working with only one monitor connected, but there's also the possibility
that I forgot something, so feel free to ask or suggest something that helps
solving this.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151005/0dc34bf5/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> ---
In your first dmesg, you have:

video=HDMI-0:e video=DVI-I-1:e

Are these required for something? Force-enabling this stuff just leads to
trouble down the line.

Interesting....

[    8.872612] nouveau E[    PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT
at 0x690400 [ IBUS ]
[    8.872781] nouveau E[    PBUS][0000:01:00.0] MMIO write of 0xbadf1001 FAULT
at 0x690400 [ IBUS ]
[    8.872869] nouveau E[    PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT
at 0x6904c0 [ IBUS ]
[    8.873043] nouveau E[    PBUS][0000:01:00.0] MMIO write of 0xbadf1001 FAULT
at 0x6904c0 [ IBUS ]

in drm/nouveau/nvkm/engine/disp/hdmigk104.c:

        /* AVI InfoFrame */
        nvkm_mask(device, 0x690000 + hdmi, 0x00000001, 0x00000000);
        nvkm_wr32(device, 0x690008 + hdmi, 0x000d0282);
        nvkm_wr32(device, 0x69000c + hdmi, 0x0000006f);
        nvkm_wr32(device, 0x690010 + hdmi, 0x00000000);
        nvkm_wr32(device, 0x690014 + hdmi, 0x00000000);
        nvkm_wr32(device, 0x690018 + hdmi, 0x00000000);
        nvkm_mask(device, 0x690000 + hdmi, 0x00000001, 0x00000001);

        /* ??? InfoFrame? */
        nvkm_mask(device, 0x6900c0 + hdmi, 0x00000001, 0x00000000);
        nvkm_wr32(device, 0x6900cc + hdmi, 0x00000010);
        nvkm_mask(device, 0x6900c0 + hdmi, 0x00000001, 0x00000001);

690000 + hdmi / 6900c0 + hdmi each get 2 reads/writes, but you only see one
error, both times on the enable. I wonder if this code doesn't need to be
more
like

u32 foo = nvkm_rd32(device, 0x690000 + hdmi);
nvkm_wr32(device, 0x690000 + hdmi, foo & ~1);
...
nvkm_wr32(device, 0x690000 + hdmi, foo | 1);

and same sort of thing for the second section. Are comfortable enough with code
to try this on your own, or do you need patches?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151005/296e62ec/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #7 from joseph-thommes at gmx.de ---
Oh these two video options were for testing and did not show any effect.
I accidently took this kernel log, but the other ones without these options
looked the same.
I'm not that into compiling everything on my own (except for some of the
easy
or
self written parts; or when gentoo does it for me ;)), but I'm willing to
learn
and been always looking for a good reason to get myself doing something like
this
and not thinking that others will do it or that it does not have enough
advantages.

So just that I got it right:
I get the source code from the nouveau git repository,
change the affected code parts, follow the instructions in the readme etc.
and compile nouveau as a module to load it.

Is it enough that I just download a snapshot and do a out-of-tree compilation?
Is it compatible with my kernel?
(because it says it contains the 3.x versions and my version is 4)
Which settings do I need to enable in my kernel that are not trivial?

Sorry for so many questions, but I'd really like to get this done.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151005/dfad2f23/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #8 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to joseph-thommes from comment #7)
> Oh these two video options were for testing and did not show any effect.
> I accidently took this kernel log, but the other ones without these options
> looked the same.
> I'm not that into compiling everything on my own (except for some of
the
> easy or
> self written parts; or when gentoo does it for me ;)), but I'm willing
to
> learn
> and been always looking for a good reason to get myself doing something
like
> this
> and not thinking that others will do it or that it does not have enough
> advantages.
> 
> So just that I got it right:
> I get the source code from the nouveau git repository,
> change the affected code parts, follow the instructions in the readme etc.
> and compile nouveau as a module to load it.
> 
> Is it enough that I just download a snapshot and do a out-of-tree
> compilation?
> Is it compatible with my kernel?
> (because it says it contains the 3.x versions and my version is 4)
> Which settings do I need to enable in my kernel that are not trivial?
> 
> Sorry for so many questions, but I'd really like to get this done.
Doesn't matter what code you grab, it should basically be the same for the
past
many kernel versions. Nouveau got a bit of a rewrite in 4.3, so the code might
look a bit different if you use an older kernel, but it's the same idea.

If this is your first time compiling a kernel, then it might get a bit tricky.
First grab a kernel, compile it, make sure you can boot it, and *then* make the
relevant changes.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151005/d10e1d94/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #9 from joseph-thommes at gmx.de ---
Oh I misunderstood something about the kernel sources :D.
Thougt this included more afford ;).
I configured my current kernel by myself and it is bootable except for
the multi-monitor problem.
I'm going to try it now.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151005/7296cacf/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #10 from joseph-thommes at gmx.de ---
Ok I'm sorry to ask again, but I've got no idea what the methods
nvkm_mask,
read, and wr32 are expecting, returning or doing, so I cannot
think by myself what to do...
(By the way in my sources they are just named nv_*.)
So where can I find documentation about it or where are they defined?
I'm familiar with (userspace) C, but not in these dimensions
and I don't know how to locate the definition of a function except for
looking in all included headers recursively...
Did I understand you correctly, that I should make the changes like this:
(again I've got no idea what these functions do, so it might be nonsense)

/* AVI InfoFrame */

        u32 foo = nvkm_rd32(device, 0x690000 + hdmi);
        nvkm_wr32(device, 0x690000 + hdmi, foo & ~1);
        nvkm_wr32(device, 0x69000c + hdmi, 0x0000006f);
        nvkm_wr32(device, 0x690010 + hdmi, 0x00000000);
        nvkm_wr32(device, 0x690014 + hdmi, 0x00000000);
        nvkm_wr32(device, 0x690018 + hdmi, 0x00000000);
        nvkm_wr32(device, 0x690000 + hdmi, foo | 1);

        /* ??? InfoFrame? */
        u32 foo = nvkm_rd32(device, 0x6900c0 + hdmi);        
        nvkm_wr32(device, 0x6900c0 + hdmi, foo & ~1);
        nvkm_wr32(device, 0x6900cc + hdmi, 0x00000010);
        nvkm_wr32(device, 0x6900c0 + hdmi, foo | 1);

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151005/cf7376c9/attachment-0001.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #11 from joseph-thommes at gmx.de ---
And of course I meant effort not afford

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151005/a9542ea7/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #12 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to joseph-thommes from comment #10)
> Ok I'm sorry to ask again, but I've got no idea what the methods
nvkm_mask,
> read, and wr32 are expecting, returning or doing, so I cannot
> think by myself what to do...
> (By the way in my sources they are just named nv_*.)
> So where can I find documentation about it or where are they defined?
> I'm familiar with (userspace) C, but not in these dimensions
> and I don't know how to locate the definition of a function except for
> looking in all included headers recursively...
> Did I understand you correctly, that I should make the changes like this:
> (again I've got no idea what these functions do, so it might be
nonsense)
> 
> /* AVI InfoFrame */
> 
>         u32 foo = nvkm_rd32(device, 0x690000 + hdmi);
>         nvkm_wr32(device, 0x690000 + hdmi, foo & ~1);
>         nvkm_wr32(device, 0x69000c + hdmi, 0x0000006f);
>         nvkm_wr32(device, 0x690010 + hdmi, 0x00000000);
>         nvkm_wr32(device, 0x690014 + hdmi, 0x00000000);
>         nvkm_wr32(device, 0x690018 + hdmi, 0x00000000);
>         nvkm_wr32(device, 0x690000 + hdmi, foo | 1);
> 
>         /* ??? InfoFrame? */
>         u32 foo = nvkm_rd32(device, 0x6900c0 + hdmi);        
>         nvkm_wr32(device, 0x6900c0 + hdmi, foo & ~1);
>         nvkm_wr32(device, 0x6900cc + hdmi, 0x00000010);
>         nvkm_wr32(device, 0x6900c0 + hdmi, foo | 1);
Seems right to me, except of course it won't compile since you have two
variables named "foo" being declared in the same scope. Remove the
second 'u32'
and you should be good to go.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151005/80059474/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #13 from joseph-thommes at gmx.de ---
Ok I changed the file, it compiled fine (with a little C90 standard warning).
On bootup I still get the message at the HDMI Monitor: No input. The DVI
Monitor just stays black, not sure if this is specific to this monitor, but I
think it usually shows such a message, too. So the symtpoms are the same.
In the last post I accidentally removed one line too much, which I did not in
the source code I used to compile it.
The kernel log has changed a bit.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151005/1401fdda/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #14 from joseph-thommes at gmx.de ---
Created attachment 118683
  --> https://bugs.freedesktop.org/attachment.cgi?id=118683&action=edit
/var/log/dmesg after changes in ./drm/.../hdmigk104.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151005/07f14c01/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #15 from joseph-thommes at gmx.de ---
I changed to the nouveau driver in Manjaro and the same issue came up.
Unfortunately I'm not able to obtain a kernel log in a chrooted environment
in
Manjaro, so there is none attached. If someone knows how to do this, please
just answer. (There's no file like dmesg in other distributions in
/var/log/).
Anyway, the symptoms are the same, so it is not a gentooish bug, but really a
bug in nouveau...

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151012/6318a5f5/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #16 from joseph-thommes at gmx.de ---
Just saw this (https://bugs.freedesktop.org/show_bug.cgi?id=91705) thread which
is about the same problem on another card so its not just this card. I don't
know if this helps, but I hope so. (You probably know this already, but just in
case.)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151026/6ac60d76/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #17 from joseph-thommes at gmx.de ---
Just compiled the new gentoo-4.0.9 sources and the problem persists.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151026/4dae474f/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #18 from joseph-thommes at gmx.de ---
When I changed it in Manjaro it was using 4.1.11 I think.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20151026/f6018500/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #19 from Joseph Thommes <joseph-thommes at gmx.de> ---
Created attachment 121229
  --> https://bugs.freedesktop.org/attachment.cgi?id=121229&action=edit
kernel log after upgrade to gentoo-4.1.15-r1

The monitors still turn off and I think it's the exact same thing as before.
Just wanted to keep this up-to-date.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20160123/b3590c88/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #20 from Pierre Moreau <pierre.morrow at free.fr> ---
(In reply to Joseph Thommes from comment #19)
> Created attachment 121229 [details]
> kernel log after upgrade to gentoo-4.1.15-r1
> 
> The monitors still turn off and I think it's the exact same thing as
before.
> Just wanted to keep this up-to-date.
The latest release would be 4.4, which includes the big rewrite from 4.3,
whereas 4.1.15 will only include fixes that were back ported (and Nouveau
doesn't send many fixes to stable version).

Sorry I can't help more than that: I don't have the correct setup and
have no
knowledge about that part of Nouveau.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20160123/6c9c078e/attachment-0001.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #21 from Joseph Thommes <joseph-thommes at gmx.de> ---
I meant the latest kernel release in sys-kernel/gentoo-sources, but I think,
I'll try some more recent sources to find out whether the problem is fixed
or
not and I'll keep this thread up-to-date.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20160125/5bead4a6/attachment-0001.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

Joseph Thommes <joseph-thommes at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #121229|0                           |1
        is obsolete|                            |

--- Comment #22 from Joseph Thommes <joseph-thommes at gmx.de> ---
Created attachment 121284
  --> https://bugs.freedesktop.org/attachment.cgi?id=121284&action=edit
dmesg of the 4.4 kernel from the gentoo sys-kernel/git-sources

I upgraded to the 4.4 release of the kernel today, but still the same error
happens. I think the syntax of the output was slightly changed, but all in all
it's still the same thing.
If you need any other information, tell me.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20160125/8302fe65/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #23 from Joseph Thommes <joseph-thommes at gmx.de> ---
Hi,
I now have both monitors attached via DVI and now the system boots up. However
the monitors now display both the same picture with the same frequency and
resolution - they are mirrored. I haven't really tried to solve this by now
and
I am not sure whether this is a X or a nouveau problem, but my X configuration
is apparently not read at all. On the other hand, this mirroring is also the
case while booting. So I need to figure out what the problem is and let you
know what it was.
This all being the case and me not knowing how the driver is constructed, I
think you can isolate the problem to somewhere, but I don't really know
where.
I hope this somehow helps.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160308/c6a2b5d3/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #24 from Joseph Thommes <joseph-thommes at gmx.de> ---
Ok, the same problem occurs just in the consoles, too.
So it's not a X problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160308/6041497f/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #25 from Pierre Moreau <pierre.morrow at free.fr> ---
AFAIK, the mirrored behaviour in console mode is expected. What happens if you
run `xrandr --output ID_OF_YOUR_RIGHT_SCREEN --right-of
ID_OF_YOUR_LEFT_SCREEN`, with the id being of the form DVI-I-1?

Can you link your Xorg config file here, and tell us where it is placed on your
system?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160308/64c7a3ec/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

--- Comment #26 from Joseph Thommes <joseph-thommes at gmx.de> ---
Ok the fact that the mirroring was also present in console mode made me not
even check for the X configuration. Thanks for this tip. I can calibrate and
configure the monitors now. Sometimes the simplest things can confuse one :D
But the bug concerning the HDMI and DVI combination was still not fixed before
I bought the DVI-cable, so I'm leaving this thread open. :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160309/49abe499/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=92274

Joseph Thommes <joseph-thommes at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #27 from Joseph Thommes <joseph-thommes at gmx.de> ---
I switched back to nouveau (kernel 4.10.1) after a time using the proprietary
nvidia driver and now X and tty work even with three monitors attached. But now
the switching between X and tty does not work properly, so I'll open a new
thread for that.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20170227/a0a666b1/attachment.html>