Bug 1786723 - No sound control on Lenovo MIIX 2 10
Summary: No sound control on Lenovo MIIX 2 10
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-lib
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Kysela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-27 13:45 UTC by 5152
Modified: 2020-11-24 16:49 UTC (History)
18 users (show)

Fixed In Version: alsa-lib-1.2.2-2.fc32 alsa-lib-1.2.2-2.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 16:49:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
output of dmesg (55.12 KB, text/plain)
2020-01-10 15:09 UTC, 5152
no flags Details
output of dmesg (59.43 KB, text/plain)
2020-05-01 15:15 UTC, 5152
no flags Details
FEDORA-2020-499d0da833 dmesg (59.06 KB, text/plain)
2020-05-01 15:47 UTC, 5152
no flags Details

Description 5152 2019-12-27 13:45:34 UTC
With last update the sound started working, but it is too loud and distorted. Volume regulation doesn't influence it at all, except of 0 value.

Comment 1 Hans de Goede 2020-01-08 08:56:31 UTC
We have had some issues with ALSA UCM profiles for Bay and Cherry Trail based devices, which were fixed in recent updates.

Can you please try the following:

1. Save all your works and close all your apps
2. From a terminal run the following 2 commands:

sudo rm /var/lib/alsa/asound.state
sudo reboot --force

This will reset your (possibly bad) mixer settings from the previous issues and will hopefully fix this.

Comment 2 5152 2020-01-08 22:03:27 UTC
Thank you, Hans, for your proposal. Anyway, as it could be solution on Lenovo Miix 320, it doesn't change anything on Lenovo Miix 2 10 and the issue persists.

Comment 3 Hans de Goede 2020-01-09 18:36:43 UTC
Ok, can you please do:

dmesg > dmesg

And attach the generated dmesg file here?

And also please run:

alsa-info.sh 

And attach the file it generates here.

Comment 5 Justin M. Forbes 2020-03-03 16:30:16 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs.

Fedora 31 has now been rebased to 5.5.7-200.fc31.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32.

If you experience different issues, please open a new bug report for those.

Comment 6 Justin M. Forbes 2020-03-25 22:25:39 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 7 Hans de Goede 2020-04-05 18:35:07 UTC
I have reproduced this problem on a Lenovo Thinkpad8 devices which also uses the cht-bsw-rt5672 machine driver.

This is a problem with the recent conversion of the UCM profiles to the UCM2 format. I've prepared a patch fixing this and I have just submitted this upstream.

Jaroslav, the alsa-ucm-conf patch-series which I just send out also contains some other bug-fixes, any chance we can get an update Fedora package with these fixes?

Comment 8 Fedora Update System 2020-04-06 16:42:57 UTC
FEDORA-2020-499d0da833 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-499d0da833

Comment 9 Fedora Update System 2020-04-06 17:06:02 UTC
FEDORA-2020-c4518d2d81 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c4518d2d81

Comment 10 Fedora Update System 2020-04-07 02:28:03 UTC
FEDORA-2020-c4518d2d81 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c4518d2d81`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c4518d2d81

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2020-04-07 03:10:12 UTC
FEDORA-2020-499d0da833 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-499d0da833`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-499d0da833

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2020-04-08 02:53:39 UTC
FEDORA-2020-c4518d2d81 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2020-04-18 00:07:12 UTC
FEDORA-2020-499d0da833 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 5152 2020-05-01 15:15:45 UTC
Created attachment 1683712 [details]
output of dmesg

Still buggy, nothing was improved after updating Fedora today and the sound still not working.

http://alsa-project.org/db/?f=8d6044205ef0877798f58507ae4a3e579bee76ea

Comment 15 5152 2020-05-01 15:47:01 UTC
Created attachment 1683726 [details]
FEDORA-2020-499d0da833 dmesg

output of dmesg

http://alsa-project.org/db/?f=3199b5cec12ce6497ae22cb89a4801d18697fdd6

Nothing improved regarding to sound probem during testing FEDORA-2020-499d0da833

Comment 16 5152 2020-05-05 16:54:49 UTC
The sound started working without any noise, but it is very silent. The maximum 100% corresponds to 50% of volume level. It should be rescalled.

Comment 17 5152 2020-05-05 17:04:30 UTC
I noticed it is only working from small built-in speaker, not from main speakers at the keyboard. There is still the same defect of loudy noice as before.

And what neither works are volume buttons on the corner of tablet.

Comment 18 Hans de Goede 2020-05-06 09:08:35 UTC
(In reply to 5152 from comment #17)
> I noticed it is only working from small built-in speaker, not from main
> speakers at the keyboard. There is still the same defect of loudy noice as
> before.
> 
> And what neither works are volume buttons on the corner of tablet.

So I did some googling and it seems that there are extra speakers inside the keyboard-dock. That is a somewhat exotic solution. I'm afraid I cannot really help with surporting that until I manage to get my hands on one of these devices myself. I will keep a look out for one of these devices on the second-hand market.

Comment 19 Hans de Goede 2020-06-30 14:11:32 UTC
(In reply to Hans de Goede from comment #18)
> So I did some googling and it seems that there are extra speakers inside the
> keyboard-dock. That is a somewhat exotic solution. I'm afraid I cannot
> really help with surporting that until I manage to get my hands on one of
> these devices myself. I will keep a look out for one of these devices on the
> second-hand market.

I've managed to get my hands on one of these devices; and although it was quite a bit of work to get to the bottom of this, I've figured out how the extra speakers work and wrote a kernel patch fixing this.

I've submitted the patch upstream and it is on its way to be included as a fix for the 5.8-rc# kernels:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?h=for-5.8&id=0ceb8a36d023d4bb4ffca3474a452fb1dfaa0ef2

5152 are you still trying to use this tablet + dock with Fedora?

If so then let me know, then I will submit a merge-req to add the patch to the Fedora 5.7 kernels which should hit updates-testing soon.

Comment 20 5152 2020-09-09 17:12:13 UTC
Thanks for solving that issue. The problem persists on external speakers when I start Fedora with Kernels 5.6.16 or 5.7.8, while with Kernel 5.8.6 the sound is understandable. It only has lower quality than on Windows, but sound control works.

Comment 21 Ben Cotton 2020-11-03 16:03:59 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 22 Ben Cotton 2020-11-24 16:49:48 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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