From: Christian Labisch <clnetbox@gmail.com>
To: 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>
Subject: sound
Date: Wed, 30 Dec 2020 19:10:16 +0100 [thread overview]
Message-ID: <efc6d5e8abc1da3cac754cb760fff08a1887013b.camel@gmail.com> (raw)
In-Reply-To: <2f0acfa1330ca6b40bff564fd317c8029eb23453.camel@gmail.com>
Update :
I've just tested the kernel 5.10.4 from ELRepo.
Unfortunately nothing changed - still no sound.
Regards,
Christian
> Thank you Greg,
>
> I am running Fedora 33 with kernel 5.9.16, which works correctly.
> All stable 5.10 versions up to 5.10.3 are having the sound issue.
> Once 5.10.4 will be available on koji I'm gonna test if it works.
>
> Thanks again !
>
> Regards,
> Christian
>
> On Wed, 2020-12-30 at 16:36 +0100, Greg KH wrote:
> > On Wed, Dec 30, 2020 at 04:26:00PM +0100, Christian Labisch wrote:
> > > Hello !
> > >
> > > I could need your help ... I have tested the new kernel 5.10.3 and sound doesn't work with
> > > this
> > > version.
> > > Seems the new Intel audio drivers are the main reason. What can be done ? Do you have any
> > > ideas
> > > ?
> > >
> > > Intel Catpt driver support is new ... This deprecates the previous Haswell SoC audio driver
> > > code
> > > previously providing the audio capabilities.
> > > And I am having a Haswell CPU -> Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
> > > Processor HD Audio Controller (rev 06)
> >
> > Can you try 5.10.4? I think a fix for this is in there as was reported
> > by another user yesterday.
> >
> > If not, can you run 'git bisect' on the kernels between the last good
> > one that worked for you, and the one that doesn't?
> >
> > thanks,
> >
> > greg k-h
>
next prev parent reply other threads:[~2020-12-30 18: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 ` Christian Labisch [this message]
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 ` Haswell audio no longer working with new Catpt driver (was: sound) Christian Labisch
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=efc6d5e8abc1da3cac754cb760fff08a1887013b.camel@gmail.com \
--to=clnetbox@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jforbes@redhat.com \
--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
Powered by JetHome