<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Nouveau fails to enter KMS with the Gigabyte G1 Gaming GTX970" href="https://bugs.freedesktop.org/show_bug.cgi?id=89664#c29">Comment # 29</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Nouveau fails to enter KMS with the Gigabyte G1 Gaming GTX970" href="https://bugs.freedesktop.org/show_bug.cgi?id=89664">bug 89664</a> from <a class="email" href="mailto:mikolaj.swiatek@gmail.com" title="Mikołaj Świątek <mikolaj.swiatek@gmail.com>"> Mikołaj Świątek</a> <pre>(In reply to Ben Skeggs from <a href="show_bug.cgi?id=89664#c28">comment #28</a>) > (In reply to Mikołaj Świątek from <a href="show_bug.cgi?id=89664#c27">comment #27</a>) > > (In reply to Ben Skeggs from <a href="show_bug.cgi?id=89664#c25">comment #25</a>) > > > (In reply to Mikołaj Świątek from <a href="show_bug.cgi?id=89664#c24">comment #24</a>) > > > > (In reply to Ilia Mirkin from <a href="show_bug.cgi?id=89664#c23">comment #23</a>) > > > > > Have a look at <a class="bz_bug_link bz_status_NEW " title="NEW - gp104 - messy(random green and/or missing pixel lines) then no output at and after boot" href="show_bug.cgi?id=100676">bug #100676</a>. Is it the same issue? (Please test the patches > > > > > that were provided there.) > > > > > > > > I don't *think* it's the exact same issue. The screen photo in that report > > > > is similar to what I see, though my text output is completely > > > > unintelligible, rather than just slightly corrupted. The reason I thought it > > > > was this bug was that the log messages about unknown connectors and failing > > > > to create encoders are identical with Omar's in my case. > > > > > > > > In any event, I've built the kernel module from Ben's tree and it didn't > > > > change anything at all, same behaviour. > > > > > > Can I see your kernel log output from that please? Bonus points if you boot > > > with "log_buf_len=8M nouveau.debug=trace". > > > > Tried to do it that way, but it somehow resulted in so much output that I > > couldn't even see the boot log with journalctl. I guess the kernel ring > > buffer fills up and the beginning gets overwritten before journald can read > > it? Not an expert at debugging kernel modules by any stretch, so let me know > > if I'm missing something obvious here. > > > > In the meantime, uploaded a run with nouveau.debug=debug. > > I can't tell 100% for sure from that, but, there's *strong* evidence there > to suggest that yes, you are indeed seeing the bug Ilia mentioned. You can > probably work around it in the meantime by plugging one of your displays > into another connector, or by trying the tree suggested in the other bug. Well, for <a class="bz_bug_link bz_status_NEW " title="NEW - gp104 - messy(random green and/or missing pixel lines) then no output at and after boot" href="show_bug.cgi?id=100676">bug 100676</a> you suggest using your master branch, which I'm already doing. Still, based on that report, I tried booting with "log_buf_len=8M drm.debug=0x14 nouveau.debug=disp=trace,i2c=trace,bios=trace", which gave legible output, attaching log in the hope that it helps. Can't really use a different connector for reasons, so for the time being I'm stuck using nvidia's driver.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>