Bug 218959 - Matebook 2022 with AMD 5 RYZEN 5500U still no sound from speakers with kernel > 6.8.4
Summary: Matebook 2022 with AMD 5 RYZEN 5500U still no sound from speakers with kernel...
Status: RESOLVED ANSWERED
Alias: None
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA) (show other bugs)
Hardware: AMD Linux
: P3 high
Assignee: Jaroslav Kysela
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-13 20:19 UTC by Thorsten
Modified: 2024-06-17 21:47 UTC (History)
1 user (show)

See Also:
Kernel Version: 6.8.9 and up / 6.9.x
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Thorsten 2024-06-13 20:19:33 UTC
I refer to Bug 215119 that has been marked "resolved implemented".
I find that hardware detection only works with upstream-kernel 6.8 version lower than 6.8.9. In fact I am running 6.8.4 and have found that with 6.8.9 and higher soundcard detection fails again. Kernel 6.9 does not work for me either.

My system:
System Information
Manufacturer: HUAWEI
Product Name: KLVL-WXXW
Version: M1010
Serial Number: PRJBB22224800650
UUID: 20220226-a497-b115-3069-a497b115306a
Wake-up Type: Power Switch
SKU Number: C100
Family: MateBook 14 

Any idea what is happening here? Anyone else facing this problem? The bug does not appear to be solved yet - at least not for my hardware.

Any help is greatly appreciated!!
Comment 1 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-06-15 15:39:39 UTC
(In reply to Thorsten from comment #0)

> I find that hardware detection only works with upstream-kernel 6.8 version
> lower than 6.8.9. In fact I am running 6.8.4

It would be great if you could check if mainline is affected (e.g. 6.10-rc3 or (in about 30 hours -rc4). And if it is, bisect the problem. Narrowing down the range (e.g. is 6.8.8 really fine) could help, too.

Please ideally do so with vanilla kernels.
Comment 2 Thorsten 2024-06-16 09:24:51 UTC
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #1)
> (In reply to Thorsten from comment #0)

> It would be great if you could check if mainline is affected (e.g. 6.10-rc3
> or (in about 30 hours -rc4). And if it is, bisect the problem. Narrowing
> down the range (e.g. is 6.8.8 really fine) could help, too.
> 
> Please ideally do so with vanilla kernels.

Thanks for your reply! Will do so and try to narrow the versions down. I am doing my testing on vanilla kernels only (anyway) and will post results here.
Comment 3 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-06-16 09:34:04 UTC
(In reply to Thorsten from comment #2)
> I am doing my testing on vanilla kernels only (anyway)

In the other bug it sounded like you were using zfs -- some people would not call this vanilla. For say an mm bug I guess that would be considered a problem, for this bug it might not.

https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/
Comment 4 Thorsten 2024-06-16 09:43:24 UTC
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #3)
> (In reply to Thorsten from comment #2)
> > I am doing my testing on vanilla kernels only (anyway)
> 
> In the other bug it sounded like you were using zfs -- some people would not
> call this vanilla. For say an mm bug I guess that would be considered a
> problem, for this bug it might not.
> 
> https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-
> kernel-bug-reports-are-ignored/

It's my everyday-working-laptop and I am running it on zfs all right. But I tested on second installation running on ext4 without any extra module as well in the past and will do so now.

But thank you for that reminder! I'll surely consider it ;-)
Comment 5 Thorsten 2024-06-16 19:55:12 UTC
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #1)
> (In reply to Thorsten from comment #0)

> It would be great if you could check if mainline is affected (e.g. 6.10-rc3
> or (in about 30 hours -rc4). And if it is, bisect the problem. Narrowing
> down the range (e.g. is 6.8.8 really fine) could help, too.
> 
> Please ideally do so with vanilla kernels.

So I did some testing just now and found out that it really does not make a difference whether it's vanilla or the distro's version (or with zfs-module loaded). They all behave alike in terms of working sound or having the bug.

Most important (and new to me): mainline does not seem to be affected (at least true for 6.10-rc3)! Sound works! Will try rc4 next.

Concerning the older versions: 6.9.x does not recognize my sound-hw at all. 6.8.x works exactly up to version 6.8.4. From 6.8.5 on it obviously "loses" its ability to detect sound-hw - from a users point of view ;-)
Comment 6 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-06-17 04:48:08 UTC
Sounds like something that broke was included in 6.9 and backported to 6.8.5 -- and later fixed for 6.10, but the fix was not backported (yet) to 6.9.

A git bisection between 6.8.4 and 6.8.5 could help to find the culprit -- or a bisection between 6.9 and 6.10-rc3 what fixed things. But with a bit of luck that fix is alredy heading towards 6.9.y anyway (might be worth trying 6.9.5 if you haven't yet)
Comment 7 Thorsten 2024-06-17 21:46:59 UTC
Well, you are absolutely right! 6.10-rc4 works as well as 6.9.5 does!! Thank you very much for your expertise and the brief insight into the ways of the kernel code ;-)

I greatly appreciate it and mark this thread "solved".

Note You need to log in before you can comment on or make changes to this bug.