Sound on Skylake #379
Comments
|
@simonheb You only have HDMI devices listed there, so the driver is not loaded properly. If my notes are correct, CAVE should have a Maxim 98357A codec, driver The first thing to check is which kernel you're running ( To enable the testing repo: You should get a 4.10.5 kernel package, which might be an improvement. But it'll be more interesting to test on a 4.11 or 4.12 kernel. Currently only 4.12.0 is available in the repo: If you still have only HDMI devices in |
|
@reynhout, thanks for your comments. The output in the previous post was indeed produced on an 4.8.17 kernel. Now I followed your steps and booted into the 4.12.0 kernel. Now aplay -l lists more, but apparently all still hdmi devices: dmesg is rather quiet on sound/audio, giving more or less the same messages as on the other kernel (just one more hdmi line). Is there something I should look at via the shell in ChromeOS, e.g. to figure out which driver is needed? In the post where volfyd got it working on Caroline, he mentioned some files he added to the system, which he seems to have gotten from ChromeOS. I assume the equivalent for CAVE would bet getting:
? Other posts mentioning blackinsting snd-hda-intel. Anything to try there? |
|
@simonheb You can check the logs in ChromeOS, but the driver name might be different. I'm not sure if copying files over will help -- I think you should see some noise in the logs well before those files become useful...though they might be needed for later stages of progress of course. Still, worth a try. Re: blacklisting. It's possible there's a conflict, but I would expect to see some relevant log entries. Can't hurt to try either, although it will likely disable the HDMI devices, of course. |
|
Ok, thanks again @reynhout for the comments. Blacklisting snd-hda-intel seems to bring the issue to light: w/ blacklisting snd-hda-intel: I also copied the aforementioned files from ChromeOS and ran called alsaucm As you suspected earlier this didn't really yield anything new. When booting after the files were copied into the system, dmesg contains: |
|
I made some very mild progress on this, not sure whether this is good though as what is described below only works on the 4.10.5 kernel, even though @reynhout suggested to try the 4.12.0. After reading that the hardware is similar on SENTRY, I went ahead and used the topology binary provided in #274 (comment) and placed it in /lib/firmware/dfw_sst.bin. This got me a little further. More specifically, dmesg shows: aplay -l now gives me these: And I was able to hear a humming/beeping sound on my headphones when unmuting codec1_out in alsamixer (i hope i didn't break anything). I'm not sure if i moved closer to or further from solving the issue for CAVE, any input on what to try next? Update: I just booted into ChromeOS to confirm that I didn't break anything and it seems sound is still working fine from the hardware side. Update 2: On the 4.9.4-galliumos-braswell kernel it works as on the 4.10.5 kernel, i.e. the drivers seems to get loaded, but other than humming/beeping on the headphones i get no sound. |
|
On a ThinkPad (SENTRY) with 2.1, I had messed around before trying to get sound to work (such as blacklisting snd_hda_intel) and implemented the steps @volfyd listed on #274, except trying to replace "adi" with "max", although I'm not even sure that would work or is the right chipset for this Chromebook. I admittedly don't know much of what I'm doing when it comes to kernel stuff. Here's my log: |
|
Got exactly the same output as @usfbrian on LARS |
|
I tried @volfyd's instructions to LARS running Arch, and things went very wrong. Please do not try to reproduce if you don't want to damage your hardware. What I did:
I could now play audio, but it seems the hardware output was maxed out, regardless of my settings (in kde or alsa-mixer). Lowering software audio just made the sound very compressed, but still very loud. As it turns out, it seems, on LARS at least, that the sound card was maxed out or something, and it was literally burning. I don't have Chrome OS installed right now to assess whether or not the sound card still works. I am baffled that it is possible to (potentially?) destroy hardware like that using software. The sound card should have shut down by the point I could smell it... |
|
I've got a CHELL, m7. If anyone needs me to do an experiment on my hardware, i'd be glad to help. Preferably not whatever @azertyfun did and literally burn my sound card. I'm not knowledgeable enough to do any good on my own, but I can follow directions. I'll be following this thread. |
|
@azertyfun how come that I am getting an error on Gallium when using your tut ? The output is on #274 |
|
That's weird. Only thing I can think of is a missing HiFi.conf somewhere? |
|
@azertyfun: Could you please try to locate all HiFi.conf files on your system ? |
|
Mhm, I deleted them after I (probably) fried my sound card, but I'm pretty sure I had two unmodified HiFi.conf files at |
|
Well I tried that, didn't work |
|
Anyone make progress? I tried updating to newest linux kernel since I saw some release notes citing skylake audio driver compatibility but no dice. |
|
@RiverCambria Nope, everybody that is / would be able to do something is silent. I can't do anything without somebody pointing me into the right direction. |
|
is it possible somehow to use audio settings from ChromeOS? |
|
@LufyCZ it's on our to do list, chill. This isn't our FT job, nor our #1 priority even for GalliumOS. @moookino unfortunately the (much older) ChromeOS kernel and mailline Linux kernel are sufficiently different to where we can't simply move the drivers/settings/etc directly from ChromeOS to GalliumOS. If we could, we would have done that a long time ago :) |
|
What's the best way to support GalliumOS? I don't have the knowledge to do anything about the Skylake audio issue, but I love GalliumOS and the doors it opens for me on my Chromebook. Should I buy GalliumOS stickers? Lol. TELL ME HOW TO BE USEFUL |
|
@LufyCZ I bought a Sabrent USB audio adapter from Amazon for $8. It was plug and play with GalliumOS. It's going to be very useful until a fix is developed. |
|
Just tried out @azertyfun 's instructions, ready to turn off my CB as soon as I heard something (to not get my speakers damaged). After the reboot, I ran a test "alsaucm -c sklnau8825max set _verb HiFi", and I got the same exact output as he did (that the conf file Acer-Lars.... wasn't found). When I was typing the command to make the Acer-Lars... directory, I (by mistake) pressed backspace on an empty line. That normally makes a sound. Howewer, I just heard a very loud static-like sound, and almost jumped up with my heartbeat at double the normal speed. The files seem to do something, but I wasn't brave enough to continue testing. The speakers work fine in ChromeOS. This was tested on arch. |
|
Yes, I used my chromebook recently, and I think some kernel update or other enabled the speakers — I didn't do anything since last time, but the speakers seem to "work" (emphasis on the quotes). It looks like the sound would be fine on maximum volume (aside from bursting your eardrums), and reducing the volume only compresses the sound (acceptable volume is at 2%, at which point it is nearly unrecognizable). The good news is that means my sound card wasn't damaged from last time, which is good. If I find the time, I'll investigate; my guess is that the Caroline soundcard and LARS soundcard differ slightly, and finding the right ones would make everything work. |
|
Well we could try the LARS files from ChromeOS. Here are the files. Could you please test them out @azertyfun ? |
|
I GOT AUDIO TO WORK!!!!! Just copy over the files, reboot, and voilá :) Edit: Just found out that at 100% it is the high static noise @azertyfun talked about, and when it is low it is highly compressed. It looks like that 20% = 100% in ChromeOS. When going lower it gets compressed. When higher, the sound goes from not-understandeable to high static. I tested it by manually setting the % in terminal and then using Gnomes built-in "speaker test" |
|
@LufyCZ, can u provide details about distribution, kernel, etc? |
|
@moookino I tested it on Arch. Kernel version is 4.12.10-1. |
|
This process works for CAVE as well, don't think I've seen anyone post a success for that yet. I have CAVE working with the same files from #274, renamed things to sklnau8825max as others have mentioned. There is definitely an issue with the audio gain that I still haven't figured out how to fix. Output is far too loud. Can't have volume up more than a couple notches. |
|
@LufyCZ I copied the files you posted but I get the following when trying to initialize: I have no sound devices now listed under volume control. Any suggestions? |
|
@RiverCambria are you on Gallium or on Arch ? |
|
Has anyone gotten sound to work on Manjaro (uefi)? |
|
Can anyone help get audio working on the Samsung Chromebook Pro with Fedora 36 or Ubuntu 22.04? |
|
As distros move to newer kernels I think we might see more breakage. I haven't been able to get sound to work with any kernel 5.13 and newer. I've tried the latest ChromeOS firmwares and such with no luck. Edit to add I'm using an ASUS C302 CAVE. I'm still running the 5.10 kernel in Arch Linux because of this. If anyone has it working on a new kernel I would like to hear about it. |
|
It's 2022 and Intel still hasn't provided proper kernel support for
built-in audio?
pon., 11 kwi 2022, 01:58 użytkownik Chris Osgood ***@***.***>
napisał:
… As distros move to newer kernels I think we might see more breakage. I
haven't been able to get sound to work with any kernel 5.13 and newer. I've
tried the latest ChromeOS firmwares and such with no luck.
I'm still running the 5.10 kernel in Arch Linux because of this.
If anyone has it working on a new kernel I would like to hear about it.
—
Reply to this email directly, view it on GitHub
<#379 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGZZWB4ZICHQFZNZ72UUCBTVENTKVANCNFSM4DVZJLGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
As far as my testing, kernel 5.13 on Ubuntu 21.10 and 5.14 on Fedora 35 are the last ones to work with this workaround on an HP Chromebook 13 G1 CHELL. |
|
If anyone has time and interest in getting audio working on Skylake again. Go here: https://github.com/cb-linux/breath/issues?q=is%3Aissue+is%3Aopen+label%3A%22KBL%2FSKL+without+SOF%22 and let this developer know. |
|
Hi, everyone! It is so nice to use Linux instead of ChromeOS (which has no as much customization). So, trying to solve the Sound Issue, I faced the problem that many of the suggestions have already expired and links are no longer available. Besides some people suggested to use native firmware. I wonder who is going to support that? For now sound is present in Galliumos out of the box with weird noise adjusting the volume. Who can explain to the newbie what is going on. Some people are trying new kernels, some utilize proprietary blobs. |
|
@c302chromebook sound pops occur when the card powers off to power save, that can be disabled but it will still pop when going out of sleep mode. Though you genuinely should not be using GalliumOS nowadays as it's heavily outdated. Use Ubuntu 20.04 and use https://github.com/carchrae/c302ca/tree/patch-1#fixing-sound (Starting from Step 8) to fix the sound, it will work perfectly, no pops whatsoever but it will not work on 22.04 |
|
There is a weird short noise when power off or launching You Tube or media files and there is no proper regulation of sound level - it is overwhelmed already at 20% or so! I am not using though I have installation media just in case. By the way, is there a complete list of hardware improvements to apply to another distro? Thanks. I will try if this issue is not going to be solved in the near future. |
this is good to know re 22.04. fwiw, i did try newer kernels with 20.04 hoping that it might be fixed there, but had no luck. @GlazedBelmont did you get it to work without the steps before 8? i used unsigned kernel that was built (lazy way) by @devendor |
|
I didn't even need to do the steps before 8 |
|
Hello family, I would like to fix the sound issue with my Asus chromebook C436FA. I have no sound so far. Motherboard is Helios and Architecture intel 10th gen CometLake. Many thanks in advance! |
|
Hello everyone, my cb is ASUS C302C. My sound card can work normally in the newest version of Gallium OS. But I can hear some weird sound from my speaker sometimes (like "boom"), is anybody have the same issue? |
|
@barryblueice hi there, I'll start by saying that galliumOS has been dead for years, you really shouldn't be using it. Not something you can fix unfortunately, it'll always pop randomly and even wake itself from sleep. I'd suggest to go to something that's more recent like Fedora, Arch or OpenSUSE because audio is WIP, really just waiting on a couple things |
|
The skylake driver is dead, use AVS instead. |
|
|
OK, I decide to give up my sound card and turn to use Ubuntu 20.10, thanks. :-) |
|
@barryblueice - i have had it working with ubuntu 20.04 and this fix: #379 (comment) however, if you ever update the kernel it will likely break the sound again. eventually i gave up doing this as my kid now has bluetooth headphones that are used most of the time anyway. |
|
and at least upgrade to a LTS/stable version, 20.04 or 22.04. 20.10 isn't supported anymore. |
|
yeah if you update further than 20.04/20.10, stuff will break @carchrae. @WeirdTreeThing is working on getting it working on mainline, they have my c302. They've already got most of the other generations working |
I think I could use a Bluetooth headset instead of a sound card |
|
USB/BT will work, definitely my go-to recommend in that case |
|
On mainline 6.2 everything works with the new AVS driver. There is a chance that your speakers can get damaged though. |
|
I remembered I saw a strange product on the AliExpress. It looks like a wireless card, but it integrates both a wireless card and a sound card in order to fix the sound card issue, and the card very expensive. |
We need new topology that includes DSP controls to prevent that, right? |
Only the ssm4567 and dmic topology have DSP control currently. |
|
You will have more luck using the AVS driver instead of the skylake driver. |
|
https://github.com/eupnea-linux/audio-scripts this will get AVS working. |
|
Link above is broken, but this one works: https://github.com/WeirdTreeThing/chromebook-linux-audio Also thanks for that info. took like 10 seconds and a reboot and sound is good to go on CHELL for me on Tumbleweed. |
and others
This is to concentrate efforts and document progress on the sound issues related to skylake and GalliumOS. All other skylake users are asked to also contribute their logs and use this issue to document progress towards finding a solution.
I am runnning a plain GalliumOS 2.1 via chrx on a CAVE model (Asus C302CA).
Right after the install, the system looks as follows:
My first step is trying out he solution @volfyd suggested for Caroline (#274 (comment)), I will post the result here.
The text was updated successfully, but these errors were encountered: