From: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
To: Christian Labisch <clnetbox@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
Akemi Yagi <toracat@elrepo.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Greg Kroah-Hartman <stable@vger.kernel.org>,
Greg Kroah-Hartman <linux-kernel@vger.kernel.org>,
Justin Forbes <jforbes@redhat.com>
Subject: Re: Haswell audio no longer working with new Catpt driver
Date: Thu, 31 Dec 2020 12:20:42 +0100 [thread overview]
Message-ID: <4c5b8a03-6508-541f-2a72-39cb3052b4f1@linux.intel.com> (raw)
In-Reply-To: <267863e8ca1464e4e433d83c5506ed871e3899b2.camel@gmail.com>
On 12/31/2020 11:50 AM, Christian Labisch wrote:
> Hi Lars-Peter,
>
> Thank you, please find attached the requested information from both kernels.
> I freshly installed the fedora kernel 5.10.4 to give you the latest results.
>
> 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>
>>
>>
Hi,
from reading provided files it seems that you use snd_intel_hda driver,
it should be possible to git bisect it between 5.9 and 5.10 as it wasn't
replaced.
Catpt driver is used on machines using DSP.
Amadeusz
WARNING: multiple messages have this Message-ID (diff)
From: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
To: Christian Labisch <clnetbox@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Akemi Yagi <toracat@elrepo.org>,
Cezary Rojewski <cezary.rojewski@intel.com>,
Greg Kroah-Hartman <stable@vger.kernel.org>,
Greg Kroah-Hartman <linux-kernel@vger.kernel.org>,
Justin Forbes <jforbes@redhat.com>
Subject: Re: Haswell audio no longer working with new Catpt driver
Date: Thu, 31 Dec 2020 12:20:42 +0100 [thread overview]
Message-ID: <4c5b8a03-6508-541f-2a72-39cb3052b4f1@linux.intel.com> (raw)
In-Reply-To: <267863e8ca1464e4e433d83c5506ed871e3899b2.camel@gmail.com>
On 12/31/2020 11:50 AM, Christian Labisch wrote:
> Hi Lars-Peter,
>
> Thank you, please find attached the requested information from both kernels.
> I freshly installed the fedora kernel 5.10.4 to give you the latest results.
>
> 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>
>>
>>
Hi,
from reading provided files it seems that you use snd_intel_hda driver,
it should be possible to git bisect it between 5.9 and 5.10 as it wasn't
replaced.
Catpt driver is used on machines using DSP.
Amadeusz
next prev parent reply other threads:[~2020-12-31 11:22 UTC|newest]
Thread overview: 24+ 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:04 ` Lars-Peter Clausen
2020-12-31 10:50 ` Christian Labisch
2020-12-31 10:50 ` Christian Labisch
2020-12-31 11:20 ` Amadeusz Sławiński [this message]
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:31 ` Christian Labisch
[not found] ` <1ad341b1b0e0eefb83d157ac24d162eaad53ab32.camel@gmail.com>
2020-12-31 15:30 ` Lars-Peter Clausen
2021-01-01 11:10 ` Christian Labisch
2021-01-01 12:09 ` Takashi Iwai
2021-01-01 13:25 ` Christian Labisch
2021-01-01 13:29 ` Lars-Peter Clausen
2021-01-01 13:40 ` Christian Labisch
2021-01-01 17:24 ` Takashi Iwai
2021-01-02 11:50 ` Christian Labisch
2021-01-02 12:16 ` Greg KH
2020-12-31 11:10 ` Haswell audio no longer working with new Catpt driver (was: sound) Christian Labisch
2020-12-31 11:10 ` 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=4c5b8a03-6508-541f-2a72-39cb3052b4f1@linux.intel.com \
--to=amadeuszx.slawinski@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=cezary.rojewski@intel.com \
--cc=clnetbox@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.