Comment 278 for bug 1958019
Revision history for this message
|
|
#278 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
It definitely is. What's missing a sequence of HDA verbs specific to
your model of laptop to get the speakers going. This probably sets the
speaker amplifier chips.
Can you share your alsa-info? Skimming through the bug, I wasn't able to
find for you.
Have you tried the verb work around (without the S3 workaround)? How
well does that work for you?
On 6/23/21 12:56 AM, <email address hidden> wrote:
> https:/
>
> --- Comment #257 from DavidLenovo (<email address hidden>) ---
> (In reply to Roland from comment #192)
>> (In reply to DavidLenovo from comment #191)
>>> I think it is normal, this patch is for Lenovo Yoga 7i, and it depend on
>> the
>>> hardware, so don't have the same :(.
>> It's easy to port this patch to Dell, but that's not the point: iasl fails
>> even without applying the patch, which should not happen ;-) But I think I
>> have to ask the iasl people why this fails.
>>
>>> The S3 problem can be resolve by a BIOS option, Lenovo put a locked BIOS so
>>> we can't. But if Dell is better on this you could try to find an option S3,
>>> or energy, ACPI, it disable for Windows compatibility.
>> It's a similar issue on Dell. S3 in BIOS is enabled, but:
>>
>> $ cat /sys/power/
>> [s2idle]
>> $ sudo dmesg |grep ACPI|grep supports
>> [ 0.201665] ACPI: (supports S0 S4 S5)
>>
>>> You have try this 5.11.5 kernel, to be sure, it is not a kernel bug ?
>> Kernel 5.11 is even worse because it doesn't even recognize the sound card.
>> With 5.13rc5 at least the headphone jack and the microphone is working. But
>> basically I think it's either this problem or the problem reported in
>> #213159...
> You sure it is the ALC287 ?
> For me it make no sens the driver work for us and not for you.
> In case of your computer recognize the sound card but the speaker don't work,
> it seem to be logic, but don't recognized, with a working kernel for us, I'm
> surprised.
> For me after 5.11.5 it stop working. I write 5.11.5 cause of that point. Do
> you
> have try 5.11.5 or older ?
>