<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - No nouveau HDMI sound on NVIDIA GT430" href="https://bugs.freedesktop.org/show_bug.cgi?id=67051#c90">Comment # 90</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - No nouveau HDMI sound on NVIDIA GT430" href="https://bugs.freedesktop.org/show_bug.cgi?id=67051">bug 67051</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to <a href="show_bug.cgi?id=67051#c88">comment #88</a>) > Let's worry about X dying later... > it has nothing to do with HDMI video or audio. > > The X comment was just for completeness. > X was lost at that time (so video and/or audio situation would've been > academical, anyway). Not at all. With KMS, X has nothing to do with modesetting, and thus nothing to do with video or hdmi audio besides asking the kernel to configure one mode or another. You should be able to test everything from the console just fine. > ----------------------------------------------------------------------------- > -- > Also, my hdminva3.patch should already be part of 3.11, so I'm surprised you > didn't get a conflict of some sort when applying it. > > Are you talking about my linux "master" (circa 3.11.0-rc1+)? > If so, I'll double check and report on problems with hdminva3.patch (if any). > Please advise. > > Otherwise, there's no "real" 3.11.0 available to me. > I see the latest one for me (the "official") would be 3.10.3. > (I've had and ran 3.10.1 for this bug submission). Right. So the patch is in 3.11-rc1 and 3.10.x (3, I think). So if you're using a version later than that, you should see apply failures with hdminva3.patch -- no need to even try it though. > ----------------------------------------------------------------------------- > -- > Do you have the dmesg from the boot that had my debug[-3] patch applied? > > As aluded to in my <a href="show_bug.cgi?id=67051#c86">Comment 86</a>: > > [~/linux]$ git checkout 8e9e3d2deacc460fbb8a4691140318f6e85e6891 ; echo $? > 0 > [~/linux]$ git checkout drivers/gpu/drm/nouveau ; echo $? > 0 > [~/linux]$ patch -p1 < /home/alex/hdmi-1.patch ; echo $? > patching file drivers/gpu/drm/nouveau/core/engine/disp/hdanva3.c > 0 > [~/linux]$ patch -p1 < /home/alex/hdminva3.patch ; echo $? > patching file drivers/gpu/drm/nouveau/core/engine/disp/hdminva3.c > 0 > [~/linux]$ patch -p1 < /home/alex/hdminva3-4.patch ; echo $? > patching file drivers/gpu/drm/nouveau/core/engine/disp/hdminv84.c > Hunk #1 succeeded at 44 with fuzz 1. > Hunk #2 succeeded at 61 (offset -4 lines). > patching file drivers/gpu/drm/nouveau/core/engine/disp/hdminva3.c > 0 > [~/linux]$ patch -p1 < /home/alex/debug-3.patch ; echo $? > patching file drivers/gpu/drm/nouveau/core/engine/disp/hdminva3.c > patching file drivers/gpu/drm/nouveau/core/engine/disp/sornv50.c > Hunk #2 succeeded at 77 with fuzz 1. > patching file drivers/gpu/drm/nouveau/nv50_display.c > Hunk #1 FAILED at 1657. > Hunk #2 FAILED at 1666. > 2 out of 2 hunks FAILED -- saving rejects to file > drivers/gpu/drm/nouveau/nv50_display.c.rej > 1 > > ------ > Should I go ahead and compile this commit (despite debug-3 failure) > and post the dmesg? > Please advise. No. My debug patch would have to be redone for a kernel that old. Instead, please take a recent kernel and apply my debug patch to it, and boot. The other patches are actually probably not necessary either -- they just change what gets written where, whereas I'm trying to figure out a potential issue with the execution flow. You don't even have to go into X or test anything (but you can) -- I just want to see the dmesg that happens when nouveau loads with that debug patch. (But obviously make sure that your hdmi-audio-capable device is plugged in at the time.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>