<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [NVE7] Unable to use nouveau"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87942#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [NVE7] Unable to use nouveau"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87942">bug 87942</a>
from <span class="vcard"><a class="email" href="mailto:bruno.pagani@ens-lyon.org" title="bruno.pagani@ens-lyon.org">bruno.pagani@ens-lyon.org</a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=111625" name="attach_111625" title="Xorg.0.log">attachment 111625</a> <a href="attachment.cgi?id=111625&action=edit" title="Xorg.0.log">[details]</a></span>
Xorg.0.log
(In reply to Ilia Mirkin from <a href="show_bug.cgi?id=87942#c9">comment #9</a>)
<span class="quote">> The GPU's graph unit, responsible for all acceleration, is having trouble
> initializing. You would still be able to use reverse-prime though, I think.
> (i.e. use the intel gpu to render to screens attached to the nvidia gpu --
> sometimes HDMI/etc are that way).</span >
OK, but that’s pointless here, I’ve choose this laptop after being sure that
HDMI and mini-DP were wired to the Intel GPU.
<span class="quote">> > > X has to start after nouveau loads, otherwise it doesn't know about the
> > > nouveau adapter. (This may no longer be the case with DRI3-based offloading
> > > actually...)
> >
> > Then, is there a way to force nouveau to load at boot, and else, is
> > restarting X after loading nouveau supposed to work (for the record, tried
> > that, and it doesn’t work either, but I’m not sure if it is supposed to work
> > since it looks like I’m indeed affected by the issue you’ve linked).
>
> Depends on the "it" that you're talking about. You should be seeing
> NOUVEAU(GPU-0) messages in your xorg log if you start X after nouveau has
> loaded. Do you not?</span >
I was talking of restarting X after loading nouveau, since I know no way to
force nouveau to load at boot. I wasn’t seeing those lines, but I’ve figured
out it was because of this section of the multiple xorg.conf files:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "Backlight" "intel_backlight"
EndSection
Since I’m currently not needing it (because in my actual configuration it has
no effect, but that’s another story), I commented this out, and it does “work”,
in the sense that I get the attached Xorg.0.log, and obviously the following
lines in dmesg:
[ 6509.306972] nouveau E[ PBUS][0000:02:00.0] MMIO write of 0x00000000 FAULT
at 0x418880 [ IBUS ]
[ 6509.307022] nouveau E[ PIBUS][0000:02:00.0] GPC0: 0x419eb4 0xbadf1000
(0x3800820c)
[ 6509.307071] nouveau E[ PBUS][0000:02:00.0] MMIO write of 0x3f800000 FAULT
at 0x405804 [ IBUS ]
[ 6509.307263] nouveau E[ PIBUS][0000:02:00.0] HUB0: 0x404170 0x00000012
(0x0e008201)
[ 6511.309246] nouveau E[ PGRAPH][0000:02:00.0] HUB_INIT timed out
[ 6511.309254] nouveau E[ PGRAPH][0000:02:00.0] 409000 - done 0x00000204
[ 6511.309263] nouveau E[ PGRAPH][0000:02:00.0] 409000 - stat 0x00000000
0x00000000 0x00000000 0x00000000
[ 6511.309273] nouveau E[ PGRAPH][0000:02:00.0] 409000 - stat 0x00000000
0x00000000 0x00000002 0x00000009
[ 6511.309276] nouveau E[ PGRAPH][0000:02:00.0] 502000 - done 0x00000300
[ 6511.309281] nouveau E[ PGRAPH][0000:02:00.0] 502000 - stat 0x00000000
0x00000000 0x00000000 0x00000000
[ 6511.309285] nouveau E[ PGRAPH][0000:02:00.0] 502000 - stat 0x00000000
0x00000000 0x00000000 0x00000000
[ 6511.309287] nouveau E[ PGRAPH][0000:02:00.0] init failed, -16
Also:
xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x69 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs:
4 outputs: 6 associated providers: 0 name:Intel
Provider 1: id: 0x3f cap: 0x5, Source Output, Source Offload crtcs: 0 outputs:
0 associated providers: 0 name:nouveau
But after “xrandr --setprovideroffloadsink nouveau Intel”, “DRI_PRIME=1
glxinfo” results in X.org crashing with:
[ 7519.419] (EE)
[ 7519.419] (EE) Backtrace:
[ 7519.419] (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x56) [0x594276]
[ 7519.419] (EE) 1: /usr/bin/Xorg.bin (0x400000+0x1983c9) [0x5983c9]
[ 7519.419] (EE) 2: /usr/lib/libc.so.6 (0x7f51e163a000+0x33b20)
[0x7f51e166db20]
[ 7519.419] (EE) 3: /usr/bin/Xorg.bin (0x400000+0x1632a4) [0x5632a4]
[ 7519.419] (EE) 4: /usr/bin/Xorg.bin (0x400000+0x1632dd) [0x5632dd]
[ 7519.419] (EE) 5: /usr/bin/Xorg.bin (DRI2Connect+0x3d) [0x56537d]
[ 7519.419] (EE) 6: /usr/bin/Xorg.bin (0x400000+0x16611a) [0x56611a]
[ 7519.419] (EE) 7: /usr/bin/Xorg.bin (0x400000+0x37807) [0x437807]
[ 7519.419] (EE) 8: /usr/bin/Xorg.bin (0x400000+0x3b9a6) [0x43b9a6]
[ 7519.419] (EE) 9: /usr/lib/libc.so.6 (__libc_start_main+0xf0)
[0x7f51e165a040]
[ 7519.419] (EE) 10: /usr/bin/Xorg.bin (0x400000+0x25dce) [0x425dce]
[ 7519.419] (EE)
[ 7519.419] (EE) Segmentation fault at address 0x28
[ 7519.420] (EE)
Fatal server error:
[ 7519.420] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 7519.420] (EE)
[ 7519.420] (EE)
Please consult the The X.Org Foundation support
at <a href="http://wiki.x.org">http://wiki.x.org</a>
for help.
[ 7519.420] (EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
[ 7519.420] (EE)
[ 7519.420] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 7519.435] (EE) Server terminated with error (1). Closing log file.
So I suppose that now this can be closed and that I should follow on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [NVE6,NVE7] HUB_INIT timeout on graph init, blob fw doesn't help"
href="show_bug.cgi?id=70354">bug 70354</a>.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>