Created attachment 1688530 [details] journalctl --no-hostname -k 1. Please describe the problem: With sound set to HDMI, the system gives no sound under nouveau but rebooting to the NVIDIA driver gives sound without any other change. There isn't any visible error when under nouveau, it just doesn't make any sound. 2. What is the Version-Release number of the kernel: `uname -s -r -v -m -p -i -o` Linux 5.6.11-300.fc32.x86_64 #1 SMP Wed May 6 19:12:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux `lspci -v | grep -i audio` 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) 01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1) `cat /proc/asound/cards` 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf7310000 irq 34 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf7080000 irq 17 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : I believe it has been broken for every F32 kernel I've tried. Under F31, it made sound, but was had pops and glitches. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Try to play a sound using any means. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: I haven't tried rawhide. 6. Are you running any modules that not shipped with directly Fedora's kernel?: I want to run stock Fedora, but sound only works with the NVIDIA driver. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
Created attachment 1688531 [details] alsa-info.sh --no-upload
Revisiting 3. I just reproduced the bug with the most recent rawhide. `uname -s -r -v -m -p -i -o` Linux 5.7.0-0.rc5.1.fc33.x86_64 #1 SMP Mon May 11 14:55:14 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
(In reply to Aaron Schlaegel from comment #2) > Revisiting 3. > > I just reproduced the bug with the most recent rawhide. > > `uname -s -r -v -m -p -i -o` > Linux 5.7.0-0.rc5.1.fc33.x86_64 #1 SMP Mon May 11 14:55:14 UTC 2020 x86_64 > x86_64 x86_64 GNU/Linux That's 5, not 3. (5. Does this problem occur with the latest Rawhide kernel?)
I just retest hdmi sound with the new F32 kernel and still have no sound. `uname -s -r -v -m -p -i -o` Linux 5.6.13-300.fc32.x86_64 #1 SMP Thu May 14 22:51:37 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Last Monday I backported some nouveau patches to the 5.7-rc6 kernel to (hopefully) fix HDMI audio on the Lenovo P1 Gen 2. I think these might help in your case too. I have done a test-build of the 5.7 kernel with the backported patches added here: https://koji.fedoraproject.org/koji/taskinfo?taskID=44650399 See here for some generic instructions for directly installing a kernel from koji: https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt Note since this is not an official build you need to disable secure-boot to boot it. If you can give this kernel a test run and let me know it fixes HDMI audio for you then that would be great.
With that test kernel, I get sound again. It is the same glitchy, crackly, stuttery sound that I got with F31, but there is sound. `uname -s -r -v -m -p -i -o` Linux 5.7.0-0.rc6.20200518gitc7c95c838059.0.test.fc32.x86_64 #1 SMP Mon May 18 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux See new attached `journalctl --no-hostname -k` and `alsa-info.sh --no-upload`
Created attachment 1691337 [details] journalctl.Linux 5.7.0-0.rc6.20200518gitc7c95c838059.0.test.txt
Created attachment 1691338 [details] alsa-info.Linux 5.7.0-0.rc6.20200518gitc7c95c838059.0.test.txt
So, I guess you fixed this bug if that patch goes live. I need to file another bug about the glitches and pops in nouveau, since those also go away when using the NVIDIA driver.
I've created a merge-request to get these added to the Fedora 5.7 kernel. Once this is merged these patches will be part of the next F33/rawhide kernel build: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/384
Sound worked briefly for one or more released F32 kernel updates, and then regressed and no longer works again with the last few current F32 kernels. `uname -s -r -v -m -p -i -o` Linux 5.6.19-300.fc32.x86_64 #1 SMP Wed Jun 17 16:10:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.