public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Javier Martinez <tazok.id0@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sound on Raptor Lake-P/U/H cAVS
Date: Mon, 7 Jul 2025 19:28:51 +0200	[thread overview]
Message-ID: <a5877144-dec7-4e66-b00a-e5876ee9aa96@gmail.com> (raw)
In-Reply-To: <CAC_tCmpYn=6-UWfm=0toO0SqSrJy6q-FSsOwT_wvNu-8pob-9w@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2055 bytes --]

El 6/7/25 a las 22:57, John Blinka escribió:
> 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

This usually happens, mantainers could decide to split one kernel driver 
into two or more to make maintenance easier. Is something like b43 
legacy drivers from broadcom and b43 standard.

In the future probably you will see this again with a driver splitted to 
support arrow lake or whatever intel "code name" that arrives.


This has happened to me recently, with a rockpi4c+. The rock pi 4c+ 
brings one realtek 8211T that "should be" supported by Realtek_phy 
(CONFIG_REALTEK_PHY) but not. I had also to enable CONFIG_STMMAC_ETH to 
make it works enabling also STMicroelectronics net adapter :-/

So, a lot of times you will find surprises as this, So test error and 
recompile (in a rock pi 4c+ it takes around 8 hours a full compilation)

Now I'm trying to enable the broadcom 43455 sdio that its shipped with 
it (the cause is the damned dtb or lack of support of the correct kernel 
option, (I already actived CONFIG_B43_SDIO and BRCMFMAC_SDIO....) or 
firmware, what will be... will be....)

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3145 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  parent reply	other threads:[~2025-07-07 17:30 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
2025-07-07 17:28           ` Javier Martinez [this message]
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=a5877144-dec7-4e66-b00a-e5876ee9aa96@gmail.com \
    --to=tazok.id0@gmail.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