linux-kernel - Re: Haswell audio no longer working with new Catpt driver (was: sound)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d6c5e253849a56b5b04ab4441c9dc0622d0083c7.camel@gmail.com>
Date:   Thu, 31 Dec 2020 12:10:17 +0100
From:   Christian Labisch <clnetbox@...il.com>
To:     Lars-Peter Clausen <lars@...afoo.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Greg Kroah-Hartman <stable@...r.kernel.org>,
        Greg Kroah-Hartman <linux-kernel@...r.kernel.org>,
        Akemi Yagi <toracat@...epo.org>,
        Justin Forbes <jforbes@...hat.com>,
        "alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
        Cezary Rojewski <cezary.rojewski@...el.com>
Subject: Re: Haswell audio no longer working with new Catpt driver (was:
 sound)

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>
> 
>