Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <d6c5e253849a56b5b04ab4441c9dc0622d0083c7.camel@gmail.com>
Subject: Re: Haswell audio no longer working with new Catpt driver (was:
 sound)
From:   Christian Labisch <clnetbox@gmail.com>
To:     Lars-Peter Clausen <lars@metafoo.de>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc:     Greg Kroah-Hartman <stable@vger.kernel.org>,
        Greg Kroah-Hartman <linux-kernel@vger.kernel.org>,
        Akemi Yagi <toracat@elrepo.org>,
        Justin Forbes <jforbes@redhat.com>,
        "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
        Cezary Rojewski <cezary.rojewski@intel.com>
Date:   Thu, 31 Dec 2020 12:10:17 +0100
In-Reply-To: <a194639e-f444-da95-095d-38e07e34f72f@metafoo.de>
References: <2f0acfa1330ca6b40bff564fd317c8029eb23453.camel@gmail.com>
         <efc6d5e8abc1da3cac754cb760fff08a1887013b.camel@gmail.com>
         <X+2MzJ7bKCQTRCd/@kroah.com>
         <a194639e-f444-da95-095d-38e07e34f72f@metafoo.de>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.38.2 (3.38.2-1.fc33) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi Lars-Peter,

Additional information to what I've sent you already before :
I found out that sound works with headphones (built-in audio)
But sound still does not work with speakers (built-in-audio).

Regards,
Christian

Christian Labisch
Red Hat Accelerator
clnetbox.blogspot.com
access.redhat.com/community
access.redhat.com/accelerators


On Thu, 2020-12-31 at 11:04 +0100, Lars-Peter Clausen wrote:
> On 12/31/20 9:33 AM, Greg Kroah-Hartman wrote:
> > On Wed, Dec 30, 2020 at 07:10:16PM +0100, Christian Labisch wrote:
> > > Update :
> > > 
> > > I've just tested the kernel 5.10.4 from ELRepo.
> > > Unfortunately nothing changed - still no sound.
> > Ah, sad.  Can you run 'git bisect' between 5.9 and 5.10 to determine the
> > commit that caused the problem?
> 
> The problem is that one driver was replaced with another driver. git 
> bisect wont really help to narrow down why the new driver does not work.
> 
> Christian can you run the alsa-info.sh[1] script on your system and send 
> back the result?
> 
> You say sound is not working, can you clarify that a bit? Is no sound 
> card registered? Is it registered but output stays silent?
> 
> - Lars
> 
> [1] https://www.alsa-project.org/wiki/AlsaInfo 
> <https://www.alsa-project.org/wiki/AlsaInfo>
> 
>