stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasa Ostrouska <casaxa@gmail.com>
To: Jason Montleon <jmontleo@redhat.com>
Cc: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
	"Cezary Rojewski" <cezary.rojewski@intel.com>,
	"Linux regressions mailing list" <regressions@lists.linux.dev>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	lma@semihalf.com,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	stable@vger.kernel.org, "Takashi Iwai" <tiwai@suse.de>
Subject: Re: Google Pixelbook EVE, no sound in kernel 6.1.x
Date: Mon, 6 Feb 2023 22:15:34 +0100	[thread overview]
Message-ID: <CALFERdwqwEzw7Wc_mTuM94+oscQ6iLFwcXS30pXioYpvmZ+2kA@mail.gmail.com> (raw)
In-Reply-To: <CAJD_bPJfT5DA8EdN+timzXa3-itnPD5epq552S=NQ6Spr7iTUw@mail.gmail.com>

On Mon, Feb 6, 2023 at 8:57 PM Jason Montleon <jmontleo@redhat.com> wrote:
>
> On Mon, Feb 6, 2023 at 8:51 AM Jason Montleon <jmontleo@redhat.com> wrote:
> >
> > On Mon, Feb 6, 2023 at 4:04 AM Amadeusz Sławiński
> > <amadeuszx.slawinski@linux.intel.com> wrote:
> > >
> > > On 2/4/2023 4:16 PM, Jason Montleon wrote:
> > > > I have built kernels for 6.0.19 (I don't think anyone confirmed
> > > > whether or not it worked), plus every 6.1 tag from 6.1-rc1 up to
> > > > 6.1.7. 6.0.19 worked. No 6.1 kernels worked. For rc1 to rc5 I built
> > > > with and without the legacy dai renaming patch added in rc6 that I
> > > > believe would be necessary, but it made no difference either way.
> > >
> > > Hi,
> > >
> > > thank you for trying to narrow it down, if I understand correctly -rc1
> > > doesn't work, which means that problem was introduced somewhere between
> > > 6.0 and 6.1-rc1 (just for the sake of being sure, can you test 6.0
> > > instead of 6.0.19?) There is one commit which I'm bit suspicious about:
> > > ef6f5494faf6a37c74990689a3bb3cee76d2544c it changes how HDMI are
> > > assigned and as a machine board present on EVE makes use of HDMI, it may
> > > potentially cause some problems. Can you try reverting it?
> > > (If reverting on top of v6.1.8 you need to revert both
> > > f9aafff5448b1d8d457052271cd9a11b24e4d0bd and
> > > ef6f5494faf6a37c74990689a3bb3cee76d2544c which has minor conflict,
> > > easily resolved with just adding both lines.
> > >
> >
> > Yes, happy to give that a shot and will report back.
> >
>
> Removing f9aafff5448b1d8d457052271cd9a11b24e4d0bd and
> ef6f5494faf6a37c74990689a3bb3cee76d2544c did not make things work.
>
> You may be onto something with pulseaudio and/or HDMI, however.
> When setting up Slackware I saw an interesting aplay hang.
> Normally aplay -l will list like this with working audio:
> $ aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: kblr55145663max [kbl-r5514-5663-max], device 0: Audio (*) []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: kblr55145663max [kbl-r5514-5663-max], device 2: Headset Audio (*) []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: kblr55145663max [kbl-r5514-5663-max], device 6: Hdmi1 (*) []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: kblr55145663max [kbl-r5514-5663-max], device 7: Hdmi2 (*) []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
>
> Both on Slackware and Fedora with broken audio it hangs like so
> (haven't tried on Arch):
> $ aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: kblr55145663max [kbl-r5514-5663-max], device 0: Audio (*) []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: kblr55145663max [kbl-r5514-5663-max], device 2: Headset Audio (*) []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: kblr55145663max [kbl-r5514-5663-max], device 6: Hdmi1 (*) []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
>
> If I remove or disable pulseaudio it lists without hanging, but it's
> difficult for me to tell whether it's working since aplay, etc. seem
> to want pulseaudio to play anything. Shutdown hangs persist
> regardless.
>
> Also, Slackware with 6.1.9 behaves as badly for me as everything else.
> If Sasa has working audio I do not know how he has managed to
> configure it. On each distro, as soon as I add topology and firmware
> files everything goes bad, regardless of whether I add ucm
> configuration or not, etc.
>
As already said, Jason, my slackware install still have a working
audio after all updates.
I have installed slackware the common way, makeing it use BTRFS,
installed by booting
it , run setup on slackware64-15.0 installed all packages except KDE
as I use XCFE or GNOME.
Since gnome is not part of Slackware I am on XFCE right now. After I
installed slackware64-15.0
I boot into it, and then followed the steps in your AUDIO section from
step 1 to step 5.
So basically copied firmware into /lib/firmware, /lib/firmware/intel
and opt/google/dsm
After that I have reboot and sound was working already on kernel 5.15.80 .
Then I run slackpkg update and upgrade-all to update everything to
slackware64-current,
which at the time had a 6.1.8 kernel.
Slackware usually ships an unpatched kernel supplied as it is from Linus tree.

Thats it, and initially I know sound was hanging sometimes. But today
I do not experience any hangs
anymore.

Only thing I had to do was to enable the kbl-r5514-5663-max profile in
pavucontrol. As by default it was at
off position.

But if needed any file or log from Slackware instsall let me know.

Rgds
Sasa

  reply	other threads:[~2023-02-06 21:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 17:09 Google Pixelbook EVE, no sound in kernel 6.1.x Jason Montleon
2023-01-28 17:52 ` Greg KH
2023-01-29  0:23   ` Jason Montleon
2023-01-30  6:33     ` Jason Montleon
2023-01-30 11:27       ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-30 12:15         ` Cezary Rojewski
2023-01-30 12:22           ` Sasa Ostrouska
2023-01-31 12:36             ` Cezary Rojewski
2023-01-31 14:58               ` Sasa Ostrouska
2023-01-31 15:48                 ` Cezary Rojewski
2023-01-31 16:02                   ` Sasa Ostrouska
2023-01-31 15:16               ` Jason Montleon
2023-01-31 15:46                 ` Cezary Rojewski
2023-02-01 11:05                 ` Amadeusz Sławiński
2023-02-01 14:33                   ` Jason Montleon
2023-02-04 15:16                     ` Jason Montleon
2023-02-06  9:03                       ` Amadeusz Sławiński
2023-02-06 13:51                         ` Jason Montleon
2023-02-06 19:57                           ` Jason Montleon
2023-02-06 21:15                             ` Sasa Ostrouska [this message]
2023-02-09 16:13                             ` Jason Montleon
2023-02-09 19:22                               ` Jason Montleon
2023-02-10 13:09                               ` Cezary Rojewski
2023-02-10 14:56                                 ` Jason Montleon
2023-02-10 17:15                                   ` Sasa Ostrouska
2023-01-30 11:23 ` Linux kernel regression tracking (#update)
  -- strict thread matches above, loose matches on Subject: below --
2023-01-23 20:44 Sasa Ostrouska
2023-01-24  5:09 ` Greg KH
2023-01-24 10:18   ` Lukasz Majczak
2023-01-24 11:34     ` Sasa Ostrouska
2023-01-24 12:11       ` Lukasz Majczak
2023-01-24 14:31         ` Sasa Ostrouska
2023-01-24 21:38           ` Sasa Ostrouska
2023-01-25 15:48             ` Lukasz Majczak
2023-01-24 11:30   ` Sasa Ostrouska
2023-01-26 12:59 ` Linux kernel regression tracking (#adding)
2023-01-27 10:06   ` Sasa Ostrouska
2023-02-09 14:11     ` Sasa Ostrouska
2023-02-24  1:10       ` Sasa Ostrouska
2023-02-24 20:43         ` Sasa Ostrouska

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=CALFERdwqwEzw7Wc_mTuM94+oscQ6iLFwcXS30pXioYpvmZ+2kA@mail.gmail.com \
    --to=casaxa@gmail.com \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=cezary.rojewski@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jmontleo@redhat.com \
    --cc=lma@semihalf.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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).