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>
Subject: Re: Haswell audio no longer working with new Catpt driver (was: sound)
Date: Thu, 31 Dec 2020 12:10:17 +0100 [thread overview]
Message-ID: <d6c5e253849a56b5b04ab4441c9dc0622d0083c7.camel@gmail.com> (raw)
In-Reply-To: <a194639e-f444-da95-095d-38e07e34f72f@metafoo.de>
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>
>
>
prev parent reply other threads:[~2020-12-31 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 15:26 sound Christian Labisch
2020-12-30 15:36 ` sound Greg KH
2020-12-30 15:45 ` sound Christian Labisch
2020-12-30 18:10 ` sound Christian Labisch
2020-12-31 8:33 ` sound Greg Kroah-Hartman
2020-12-31 10:04 ` Haswell audio no longer working with new Catpt driver (was: sound) Lars-Peter Clausen
2020-12-31 10:50 ` Christian Labisch
2020-12-31 11:20 ` Haswell audio no longer working with new Catpt driver Amadeusz Sławiński
2020-12-31 11:31 ` Christian Labisch
2020-12-31 11:10 ` Christian Labisch [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6c5e253849a56b5b04ab4441c9dc0622d0083c7.camel@gmail.com \
--to=clnetbox@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=cezary.rojewski@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jforbes@redhat.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=toracat@elrepo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).