<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - xorg-server-1.19.3 crashes when trying to enable HDMI output"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101220#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - xorg-server-1.19.3 crashes when trying to enable HDMI output"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101220">bug 101220</a>
from <span class="vcard"><a class="email" href="mailto:pachoramos1@gmail.com" title="Pacho Ramos <pachoramos1@gmail.com>"> <span class="fn">Pacho Ramos</span></a>
</span></b>
<pre>(In reply to Ilia Mirkin from <a href="show_bug.cgi?id=101220#c12">comment #12</a>)
<span class="quote">> (In reply to Pacho Ramos from <a href="show_bug.cgi?id=101220#c11">comment #11</a>)
> > I don't use any initrd... I could rely on CONFIG_EXTRA_FIRMWARE... but I
> > thought I didn't need that as nouveau is compiled as a module and not into
> > the kernel :|
>
> OK, well if modules are loaded off the FS and not initrd, then you're good
> on that front, assuming you really do have the updated linux-firwmare (April
> 4 or later --
> <a href="https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/">https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/</a>
> commit/?id=b14134583c2a15d4404695f72cb523daedb877ab). Lots of people use
> initrd without understanding how it works.</span >
Yeah, my linux-firmware snapshot is the one up to
<a href="https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=df40d15d6ad617e72ce7ea00b91d9117d92dcccc">https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=df40d15d6ad617e72ce7ea00b91d9117d92dcccc</a>
<span class="quote">>
> So there are two issues here...
>
> #1: we should probably disable reverse prime if you don't have acceleration
> (or figure out how to make it work without accel... should just be a very
> slow memcpy away... not great, but better than a non-working screen)
>
> #2: we should figure out what's going on with accel on your GP107 -- looks
> like stuff is just hanging (that's the "timeout" messages you see, we're
> waiting for some condition to become true, and it never does).
>
> I can help with the former, and hopefully Ben Skeggs can investigate the
> latter.</span >
Great, thanks a lot:)</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>