On Tue, May 12, 2015 at 10:26:24AM -0500, Mario Limonciello wrote:
On 05/12/2015 05:12 AM, Mark Brown wrote:
On Mon, May 11, 2015 at 08:26:58PM +0200, Dominik Brodowski wrote:
Please fix your mail client to word wrap within paragraphs and leave blank lines between paragraphs. Your current mail client is doing neither which makes your mails hard to read.
Also CCing Matthew who came up with the original version of the version change and Liam who is one of Intel's audio experts.
According to an off-list discussion, the sound breakage (and not just some jack detection issue) seems to be caused due to alsa-lib being too old.
Right, it needs the userspace configuration files installing.
Is it just configuration files? With 4.1-rc3 I've not been able to get sound working mucking with any mixers.
You need PulseAudio 6.0 but otherwise yes, it works for me.
The matter is further complicated by the issue that the driver asks for some firmware blob intel/IntcPP01.bin which (at least) I cannot find anywhere.
As previously advised that firmware is optional.
The errors in dmesg make it seem like that was related to the firmware missing, but that is a red herring it sounds like.
Yes, it is.
Does this also affect other behaviour of the system? I'd be pretty unhappy if it introduce power regressions for example, I mostly don't use audio on my laptops but I care a lot about how long it'll run disconnected. It *is* quite a new laptop and my experience installing was very much that it was in bringup (though quite a bit of this was userspace).
I just tried it with 4.1-rc3 from Ubuntu's mainline PPA and an Ubuntu 15.04 userspace. It does affect the behavior of the system. See all the PCM errors in dmesg:
That wasn't my question. I'm asking what else the firmware is changing based on detecting Linux, we don't want to just move onto a different set of bugs somewhere else.
At least with BIOS A03 (latest), Ubuntu 15.04 (3.19ish and modern userspace) or with 4.0 and recent userspace the experience shouldn't be bringup.
I'm not seeing any of the hw_params() issues with v4.1 - are you perhaps using an old linux-firmware? I don't know how up to date Ubuntu is there.