linux-kernel

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: <efc6d5e8abc1da3cac754cb760fff08a1887013b.camel@gmail.com>
Date:   Wed, 30 Dec 2020 19:10:16 +0100
From:   Christian Labisch <clnetbox@...il.com>
To:     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>
Subject: sound

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
>