Created attachment 940183 [details] alsa-info of 3.17rc kernel (monitor detection fails) On my Lenovo W520 audio over display port to hdmi tv has worked for example in kernel 3.16.1. After upgrading to kernel 3.17-rc2 alsa can no longer get the eld monitor information and thus pulseaudio will not allow sound over the display port. Even in 3.17rc I can still get sound if I kill pulseaudio and manually just use alsa audio from command line forcing the specific display port connector to be used. Thus the bug is that either nouveau or some more generic display/audio component has changed so that the monitor eld information no longer flows into alsa. The bug is still present in 3.17-rc2 to 3.17-rc5. I have not tried rc1. I'll attach the alsa-info of working and non-working configurations. The eld of /proc/asound/NVidia/eld#1.0 on non-working 3.17 kernel is: monitor_present 0 eld_valid 0 vs the working 3.16 kernel shows: monitor_present 1 eld_valid 1 monitor_name Philips FTV connection_type HDMI eld_version [0x2] CEA-861D or below edid_version [0x3] CEA-861-B, C or D manufacture_id 0xc41 product_id 0x0 port_id 0x0 support_hdcp 0 support_ai 0 audio_sync_delay 0 speakers [0x1] FL/FR sad_count 2 sad0_coding_type [0x1] LPCM sad0_channels 2 sad0_rates [0x6e0] 32000 44100 48000 88200 96000 sad0_bits [0xe0000] 16 20 24 sad1_coding_type [0x2] AC-3 sad1_channels 6 sad1_rates [0xe0] 32000 44100 48000 sad1_max_bitrate 640000
Created attachment 940184 [details] alsa-info of 3.16.1 kernel (monitor detection works)
Please attach the output of dmesg for both 3.16.1 and whatever 3.17 kernel you're running.
The alsa-info has collected alsa related parts from the dmesg at the bottom of each attachemnt. Is that enough? I'll try to figure how I can extract from the journal old boot logs. They are there somewhere...
Created attachment 941675 [details] dmesg of 3.16.3 (working example)
Created attachment 941676 [details] dmesg of 3.17rc6 (failing example)
With 3.18.0-0.rc0.git9.2.fc22.1.x86_64 kernel sound works again with pulseaudio. Now the only problem is that compared to previous info most of the filds returned are broken (just endless repeating of byte 0x10). monitor_present 1 eld_valid 1 monitor_name connection_type HDMI eld_version [0x2] CEA-861D or below edid_version [0x0] no CEA EDID Timing Extension block present manufacture_id 0x1010 product_id 0x1010 port_id 0x1010101010101010 support_hdcp 0 support_ai 0 audio_sync_delay 32 speakers [0x10] RC sad_count 1 sad0_coding_type [0x2] AC-3 sad0_channels 1 sad0_rates [0x400] 96000 sad0_max_bitrate 128000
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.