Bug 207509
Summary: | Lenovo Yoga Chromebook C630 missing support for sound, microphone, touchscreen and gyroscope | ||
---|---|---|---|
Product: | Platform Specific/Hardware | Reporter: | John Cummings (mrjohncummings) |
Component: | x86-64 | Assignee: | platform_x86_64 (platform_x86_64) |
Status: | NEW --- | ||
Severity: | normal | CC: | bp, erdichen, tiwai, waownn |
Priority: | P1 | ||
Hardware: | Intel | ||
OS: | Linux | ||
Kernel Version: | 5.4 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
dmesg output
dmesg output new for 5.8 |
Description
John Cummings
2020-04-29 11:00:26 UTC
For clarity internal sound, microphone and touchscreen simply don't work at all, the gyroscope appears to work but it always sets the screen upside down Also for clarity this is the C630, not the C630WOS, they are completely different machines, one Intel, one ARM, I think they're even released on different years (not sure why they have the same model number) Thanks very much Can you try with the latest kernel 5.7 ? Also, pls update full dmesg from it. Takashi, can you do something about the sound? > Also, pls update full dmesg from it.
I mean, "upload".
Thx.
Thank you very much for your reply, I can confirm the issue is still there with kernel version 5.7.11-200.fc32.x86_64 I have attached the full dmesg text Created attachment 290787 [details]
dmesg output
(In reply to Borislav Petkov from comment #3) > Can you try with the latest kernel 5.7 ? > > Also, pls update full dmesg from it. > > Takashi, can you do something about the sound? Replying to make sure you see the messages above, thanks again for your help with this (In reply to Borislav Petkov from comment #3) > Can you try with the latest kernel 5.7 ? > > Also, pls update full dmesg from it. > > Takashi, can you do something about the sound? Yes the sound and microphone are much more important to me at least, saves attaching an external USB speaker and microphone which is a real faff. Since it is a Chromebook I assume there are open source drivers within ChromeOS, let me know if I should run dmesg or anything else in ChromeOS for you. Thanks again Did you try the latest 5.8 kernel? You'd need the SOF firmware as well for the recent ASoC Intel SOF driver as well as the UCMv2 profiles (and the recent version of alsa-lib that supports UCMv2), too. (In reply to Takashi Iwai from comment #9) > Did you try the latest 5.8 kernel? You'd need the SOF firmware as well for > the recent ASoC Intel SOF driver as well as the UCMv2 profiles (and the > recent version of alsa-lib that supports UCMv2), too. I'm afraid I only understand about half of the words in that sentence :) I'm not a developer, are you saying that Kernel 5.8 will have the drivers I need in and it should fix the issues I'm having? Thanks I can't say whether it'd work because you didn't give any detailed hardware information. The lspci output is only a tip of iceberg. You'd just need to try it out. And ask your distro for providing the latest set of user-space stuff for supporting ASoC SOF driver. (In reply to Takashi Iwai from comment #11) > I can't say whether it'd work because you didn't give any detailed hardware > information. The lspci output is only a tip of iceberg. > > You'd just need to try it out. And ask your distro for providing the latest > set of user-space stuff for supporting ASoC SOF driver. OK, thanks, is the dmesg output not enough? Happy to provide other if I'm told what is needed. Thanks I'll ask them Note that the dmesg is just an information to see whether the lowest fundamental piece is loaded / works. Most of other stuff needed are user-space, hence you need to ask your distro in anyway. (In reply to Takashi Iwai from comment #13) > Note that the dmesg is just an information to see whether the lowest > fundamental piece is loaded / works. Most of other stuff needed are > user-space, hence you need to ask your distro in anyway. OK, thanks, so what should I do to fix this issue? Ask the people working on the distro to look at this bug? Yes, it should have been other way round: you'd better to report the issue to the distro at first, then move on to the upstream kernel bugzilla for each kernel bug. OK, thanks, the reason that I came here is I went through that process and couldn't find a way to request the fix and was told that the support needed to be included in the kernel. In that case, it'd be helpful if you give the link to the original report to distro bug tracker, too. In anyway, give the fresh 5.8 kernel a try, and report back with the dmesg output. If the audio still doesn't show up, run alsa-info.sh script with --no-upload option, and attach the output to Bugzilla. (In reply to Takashi Iwai from comment #17) > In that case, it'd be helpful if you give the link to the original report to > distro bug tracker, too. > > In anyway, give the fresh 5.8 kernel a try, and report back with the dmesg > output. If the audio still doesn't show up, run alsa-info.sh script with > --no-upload option, and attach the output to Bugzilla. Also to confirm 5.8 does not fix the issue, specifically I'm using Fedora so its 5.8.14-200.fc32.x86_64 (In reply to Takashi Iwai from comment #17) > In that case, it'd be helpful if you give the link to the original report to > distro bug tracker, too. > > In anyway, give the fresh 5.8 kernel a try, and report back with the dmesg > output. If the audio still doesn't show up, run alsa-info.sh script with > --no-upload option, and attach the output to Bugzilla. I also contacted them via the forum, that's where I got the reply that it should be requested here (can't find the message now though). Please let me know if there's anything I can do to help Created attachment 293117 [details]
dmesg output new for 5.8
(In reply to Takashi Iwai from comment #17) > In that case, it'd be helpful if you give the link to the original report to > distro bug tracker, too. > > In anyway, give the fresh 5.8 kernel a try, and report back with the dmesg > output. If the audio still doesn't show up, run alsa-info.sh script with > --no-upload option, and attach the output to Bugzilla. Also please see new attached dmesg output (In reply to Takashi Iwai from comment #17) > In that case, it'd be helpful if you give the link to the original report to > distro bug tracker, too. > > In anyway, give the fresh 5.8 kernel a try, and report back with the dmesg > output. If the audio still doesn't show up, run alsa-info.sh script with > --no-upload option, and attach the output to Bugzilla. Have updated to Fedora 33 which is 5.8.17-300.fc33.x86_64, still the same issues Also same problem in Ubuntu, have filed a bug with them which includes lots of output files https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903217 (In reply to Takashi Iwai from comment #17) > In that case, it'd be helpful if you give the link to the original report to > distro bug tracker, too. > > In anyway, give the fresh 5.8 kernel a try, and report back with the dmesg > output. If the audio still doesn't show up, run alsa-info.sh script with > --no-upload option, and attach the output to Bugzilla. It seems that a solution has been found by a Lenovo employee, please could this be implemented in the kernel? Thanks very much indeed https://forums.lenovo.com/t5/Fedora/How-can-I-get-support-for-missing-drivers-for-my-laptop/m-p/5048544?page=1#5185031 please support Lenovo Yoga Chromebook C630 i7 for sound, microphone, touchscreen and gyroscope. I am using OpenSUSE tumbleweed The Nami board has multiple possible touchscreen controllers so the kernel needs a patch to probe for the present device: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/11cd1bd03f75afb7051f180ba468307736c367d9 |