public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sound on Raptor Lake-P/U/H cAVS
Date: Mon, 07 Jul 2025 09:42:44 +0100	[thread overview]
Message-ID: <4664857.LvFx2qVVIh@rogueboard> (raw)
In-Reply-To: <CAC_tCmpYn=6-UWfm=0toO0SqSrJy6q-FSsOwT_wvNu-8pob-9w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]

On Sunday, 6 July 2025 21:57:59 British Summer Time John Blinka wrote:
> Javier and Michael,
> 
> Sorry to have gone silent for a while. Had houseguests and didn’t want to
> ignore them while burying myself in kernel configuration.
> 
> However, your combined suggestions have borne fruit. I turned on many
> things in Gentoo’s 6.12 kernel  that were present in Ubuntu’s 6.14 kernel,
> and now sound works in Gentoo.
> 
> “Many things” is quite vague, I know. I did a diffconfig between Gentoo and
> Ubuntu and mindlessly made Gentoo more like Ubuntu. Until the sheer tedium
> made me quit, compile a kernel, and reboot. It worked, but right now I have
> no idea why. I will gradually pare down the differences between my new
> working Gentoo 6.12 kernel configuration and the old nonworking Gentoo
> kernel config until I’ve identified the changes that brought sound to life.
> And I’ll report back then.
> 
> I very much appreciate both of your suggestions and your willingness to
> help!!
> 
> John Blinka

Glad you got your sound going.  It is usually a matter of enabling the modules 
in the kernel necessary for your hardware and perhaps adding any firmware, 
setting the order of the desired audio card to be used as the default if you 
have more than one card and unmuting it.  When comparing kernel configs check 
what's build in the kernel and what is set as a module.  Using 'alsactl init' 
flags up anything amiss as it tries to load needed modules, but I haven't had 
to use this for years now because the drives are less buggy than what they 
used to be.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-07-07  8:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 15:34 [gentoo-user] sound on Raptor Lake-P/U/H cAVS John Blinka
2025-07-03 15:40 ` Javier Martinez
2025-07-03 16:56 ` Michael
2025-07-04 13:44   ` John Blinka
2025-07-04 13:57     ` Javier Martinez
2025-07-04 14:10     ` Javier Martinez
2025-07-04 14:20     ` Michael
2025-07-04 14:22       ` Michael
2025-07-06 20:57         ` John Blinka
2025-07-07  8:42           ` Michael [this message]
2025-07-07 17:28           ` Javier Martinez
2025-07-29 10:49             ` [gentoo-user] sound on Raptor Lake-P/U/H cAVS [SOLVED] John Blinka

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=4664857.LvFx2qVVIh@rogueboard \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.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