Bug 1867118 - Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope
Summary: Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscree...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-lib
Version: 32
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: 2020-08-07 11:45 UTC by JohnC
Modified: 2021-05-25 16:37 UTC (History)
23 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 16:37:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dsmeg output (69.90 KB, text/plain)
2020-08-07 11:45 UTC, JohnC
no flags Details
dmesg new for 5.8 (64.47 KB, text/plain)
2020-10-21 09:22 UTC, JohnC
no flags Details

Description JohnC 2020-08-07 11:45:54 UTC
Created attachment 1710789 [details]
dsmeg output

Description of problem:
Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope

Version-Release number of selected component (if applicable):
I don't know

How reproducible:

Steps to Reproduce:
1. Install Fedora 32 on Lenovo Yoga Chromebook C630
2. Sound, microphone, touchscreen and gyroscope don't work
3.

Actual results:
sound, microphone, touchscreen and gyroscope do not work

Expected results:
That they work 

Additional info:
I filed a Linux Kernel request and was told that the change has to come from the distribution https://bugzilla.kernel.org/show_bug.cgi?id=207509

Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope. It appears there are no drivers for them in an version of the kernel. 

This is a readout of lspci

00:00.0 Host bridge: Intel Corporation Device 5914 (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Device 5917 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Device 1903 (rev 08)
00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Device 9d2f (rev 21)
00:14.2 Signal processing controller: Intel Corporation Device 9d31 (rev 21)
00:15.0 Signal processing controller: Intel Corporation Device 9d60 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Device 9d61 (rev 21)
00:15.2 Signal processing controller: Intel Corporation Device 9d62 (rev 21)
00:15.3 Signal processing controller: Intel Corporation Device 9d63 (rev 21)
00:19.0 Signal processing controller: Intel Corporation Device 9d66 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d13 (rev f1)
00:1e.0 Signal processing controller: Intel Corporation Device 9d27 (rev 21)
00:1e.2 Signal processing controller: Intel Corporation Device 9d29 (rev 21)
00:1e.3 Signal processing controller: Intel Corporation Device 9d2a (rev 21)
00:1e.4 SD Host controller: Intel Corporation Device 9d2b (rev 21)
00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
00:1f.2 Memory controller: Intel Corporation Device 9d21 (rev 21)
00:1f.3 Multimedia audio controller: Intel Corporation Device 9d71 (rev 21)
00:1f.4 SMBus: Intel Corporation Device 9d23 (rev 21)
00:1f.5 Non-VGA unclassified device: Intel Corporation Device 9d24 (rev 21)
01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 61)

I'm sorry if this is formatted in the wrong way or in the wrong place, this is my first bug.

Comment 2 JohnC 2020-10-21 09:22:06 UTC
Created attachment 1723120 [details]
dmesg new for 5.8

Comment 3 JohnC 2020-11-04 16:07:02 UTC
To update this is not resolved in Fedora 33, have also asked on the Linux Kernel bug tracker and they have said the fix should come from the distro 

https://bugzilla.kernel.org/show_bug.cgi?id=207509

Comment 4 JohnC 2020-11-09 18:43:18 UTC
Note: I have also report the same issue on the Ubuntu bug tracker as I get the same issue, as part of it I provided quite a few logs which may help diagnosis 

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217

Comment 5 JohnC 2020-11-17 11:17:57 UTC
It seems as though a Lenovo employee has been able to offer a solution, please could this fix be implemented? 

https://forums.lenovo.com/t5/Fedora/How-can-I-get-support-for-missing-drivers-for-my-laptop/m-p/5048544?page=1#5185031

Comment 6 Hans de Goede 2020-11-17 11:41:23 UTC
(In reply to JohnC from comment #5)
> It seems as though a Lenovo employee has been able to offer a solution,
> please could this fix be implemented? 
> 
> https://forums.lenovo.com/t5/Fedora/How-can-I-get-support-for-missing-drivers-for-my-laptop/m-p/5048544?page=1#5185031

Thank you for this info. I'm re-assigning this to alsa-lib so that the Fedora sound-maintainer is made aware of this.

Jaroslav, it looks like Lenovo has provided an UCM profile for the Chromebook Yoga C630 in the link above, it would be nice if we can get this integrated upstream and in Fedora.

Comment 7 Jaroslav Kysela 2020-11-17 16:05:05 UTC
Please, attach 'alsa-info.sh --no-upload' text file using the latest Fedora kernel (5.9). The UCM config is horrible and it's for the Google audio server in chromebooks.

Make sure that the firmware file from Chromebook is installed:

[    6.070791] snd_soc_skl 0000:00:1f.3: Direct firmware load for 9d71-GOOGLE-NAMIMAX-0-tplg.bin failed with error -2
[    6.070795] snd_soc_skl 0000:00:1f.3: tplg fw 9d71-GOOGLE-NAMIMAX-0-tplg.bin load failed with -2, trying alternative tplg name kbl_da7219_max98357a-tplg.bin
[    6.070827] snd_soc_skl 0000:00:1f.3: Direct firmware load for kbl_da7219_max98357a-tplg.bin failed with error -2
[    6.070830] snd_soc_skl 0000:00:1f.3: tplg kbl_da7219_max98357a-tplg.bin failed with -2, falling back to dfw_sst.bin
[    6.070853] snd_soc_skl 0000:00:1f.3: Direct firmware load for dfw_sst.bin failed with error -2
[    6.070856] snd_soc_skl 0000:00:1f.3: Fallback tplg fw dfw_sst.bin load failed with -2
[    6.070857] snd_soc_skl 0000:00:1f.3: Failed to init topology!
[    6.070859] snd_soc_skl 0000:00:1f.3: ASoC: failed to probe component -2
[    6.070883] kbl_da7219_max98357a kbl_da7219_max98357a: ASoC: failed to instantiate card -2
[    6.071006] kbl_da7219_max98357a: probe of kbl_da7219_max98357a failed with error -2

I am not sure, if we can distribute this firmware file. You should ask Lenovo / Google.

Comment 8 JohnC 2020-11-17 20:51:07 UTC
@Jaroslav_Kysela and @Hans_de_Goede thanks very much for your replies, I don't have enough technical knowledge be able to install the firmware file myself, I've asked Dave Ober to reply here with information on distributing the firmware file.

https://forums.lenovo.com/t5/Fedora/How-can-I-get-support-for-missing-drivers-for-my-laptop/m-p/5048544?page=1#5185554

Is there anything I can do with my limited technical knowledge to help move this along? 

Thanks again

Comment 9 JohnC 2020-11-17 20:52:11 UTC
(In reply to Jaroslav Kysela from comment #7)
> Please, attach 'alsa-info.sh --no-upload' text file using the latest Fedora
> kernel (5.9). The UCM config is horrible and it's for the Google audio
> server in chromebooks.
> 
> Make sure that the firmware file from Chromebook is installed:
> 
> [    6.070791] snd_soc_skl 0000:00:1f.3: Direct firmware load for
> 9d71-GOOGLE-NAMIMAX-0-tplg.bin failed with error -2
> [    6.070795] snd_soc_skl 0000:00:1f.3: tplg fw
> 9d71-GOOGLE-NAMIMAX-0-tplg.bin load failed with -2, trying alternative tplg
> name kbl_da7219_max98357a-tplg.bin
> [    6.070827] snd_soc_skl 0000:00:1f.3: Direct firmware load for
> kbl_da7219_max98357a-tplg.bin failed with error -2
> [    6.070830] snd_soc_skl 0000:00:1f.3: tplg kbl_da7219_max98357a-tplg.bin
> failed with -2, falling back to dfw_sst.bin
> [    6.070853] snd_soc_skl 0000:00:1f.3: Direct firmware load for
> dfw_sst.bin failed with error -2
> [    6.070856] snd_soc_skl 0000:00:1f.3: Fallback tplg fw dfw_sst.bin load
> failed with -2
> [    6.070857] snd_soc_skl 0000:00:1f.3: Failed to init topology!
> [    6.070859] snd_soc_skl 0000:00:1f.3: ASoC: failed to probe component -2
> [    6.070883] kbl_da7219_max98357a kbl_da7219_max98357a: ASoC: failed to
> instantiate card -2
> [    6.071006] kbl_da7219_max98357a: probe of kbl_da7219_max98357a failed
> with error -2
> 
> I am not sure, if we can distribute this firmware file. You should ask
> Lenovo / Google.

See above for reply, just doing a direct reply to make sure you get a notification

Comment 10 Jaroslav Kysela 2020-11-18 07:45:33 UTC
Please, provide 'alsa-info.sh --no-upload' output (attach the file to this bug) with the firmware file installed, as I requested in comment#7. Thank you.

Comment 11 JohnC 2020-11-18 09:12:37 UTC
Hi Jaroslav

I'm not able to install the firmware file, its too technical for me. 

Thanks

Comment 12 Fedora Program Management 2021-04-29 16:35:15 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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 13 Ben Cotton 2021-05-25 16:37:46 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.