-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Audio issues on some Bay Trail models with custom RW_LEGACY firmware #180
Comments
dmesg output
lspci output
|
adding similar dmesg grep from the device running chromeos
|
Could you try a newer kernel that I'm working on for 2.0?: http://galliumos.org/apt/pool/main/l/linux-source-4.3.6galliumos/ . Note, that won't be the final kernel. I hope to move to 4.5 before we release 2.0. |
Seeing more or less the same as with current (also on ubuntu 15.10, fedora 23, archlinux, etc). |
https://www.reddit.com/r/linuxquestions/comments/3zxrki/no_sound_with_ubuntu_1510_on_dell_chromebook_11/cyq3rwe someone was able to get the audio working out of the box with 15.10 after tweaking/replacing the ALSA state. I'm not able to reproduce this though. I'm going to see if I can get more information about what they did. |
I also have the same problem with the exact same dmesg output. Found a guide online for installing debian on a dell candy (https://www.reddit.com/r/linux/comments/4aj29c/howto_debian_on_dell_chromebook_113120_candy2015/), I followed the guide and the firmware that the writer said to install for sound didn't fix the issue for me. |
I think this thread ( https://www.reddit.com/r/linux/comments/4aj29c/howto_debian_on_dell_chromebook_113120_candy2015/d1ex0mk ) is worth a read, establishing that between users the main difference seems to be RW_LEGACY vs BOOT_STUB, and it seems to result in significantly different behavior in the boot process, possibly starting with the 'CITY'/'Calgary' BIOS detection, however MattDevo and JohnLewis both suggest that this shouldn't be a significant factor ( https://plus.google.com/115072581063115222604/posts/YqTf7XSzabW ) |
https://www.reddit.com/r/linux/comments/4aj29c/howto_debian_on_dell_chromebook_113120_candy2015/d1lk7gk this confirms this is some problem caused by a difference between BOOT_STUB and RW_LEGACY |
@hugegreenbug The current LTS kernel is 4.4... We should probably use that one if we don't want to do porting work every couple months. |
@mattdevo will know the current state of things, but we should keep this open for tracking and reference. |
so with RW_LEGACY, the ChromeOS payload (depthcharge) is still run, in order to show the developer mode boot screen. Depthcharge does some hardware initialization on the audio device (and eMMC), which apparently causes some issues when running (non-ChromeOS) Linux. When using a modified BOOT_STUB, depthcharge is replaced with SeaBIOS, so that extra init never happens, and the kernel is happy. As an example of what's going on, see: |
@mattdevo Any ideas on how we could try to get this working from inside the OS? It does seem to work on some models(?) @ColtonDRG reports working audio on GNAWTY... |
IRC Marvin reports no audio problems on SWANKY with RW_LEGACY from MattDevo. |
No sound on my Lenovo 100s with MattDevo RW_LEGACY running GalliumOS 1.0. Doesn't really bother me but I'm happy to provide any useful debugging information requested. |
I have an ORCO chromebook (Lenovo 100s) with MattDevo's RW_legacy, and I had this problem with both GalliumOS and lubuntu. I haven't tried other OS's, but I would assume they would have the same problem. |
IRC
Which would suggest at least partially successful hardware init. |
Toshiba Chromebook 2 CB30-B-103 (SWANKY, Bay Trail), RW_Legacy and John Lewis firmware This problem does effect at least some SWANKY models |
Some more info from IRC
This really sounds like a PulseAudio (or ALSA) configuration problem. If anyone with appropriate hardware can spend some time digging, I think this should be simple to resolve. For those who need a quick fix (and who are not dual-booting), MrChromebox BOOT_STUB firmware seems to be it. |
Some observations from our test GNAWTY:
When initially installed, I had perfect audio playback. Started looking at input, and saw that the level meter in I was able to restore audio by deleting Have not been able to repro the initial failure ( For those affected and still on RW_LEGACY firmware. Maybe try |
Toshiba CB30-B-104, Linux Swanky 4.7.2. When viewing movie in VLC after plug/unplug headphones: no sound. Removing .config/pulse has no effect. Edit: Sorry. Muting microphone via alsamixer doesn't have any effect on speakers. |
@hvdwolf Thanks for the report. Some thoughts:
Just thinking aloud, and capturing info in one place. |
Updated to Linux Swanky 4.8.17-galliumos beta on my Toshiba CB30-B-104, MrChromebox BOOT_STUB installed Sound is working from both speakers and headphones. |
Update from RW_Legacy to BOOT_STUB and Full ROM, no changes! ASUS C300 Chromebook - #367 |
I had this issue on my Toshiba Chromebook 2 for a long time under Arch Linux. Switching to https://aur.archlinux.org/packages/linux-max98090/ seemed to fix it. Not super relevant since it's a different distro, but might provide some hints. |
It's seems very promising! Now I have to find a the driver for GalliumOS.
|
I'm having similar issues on:
The sound works at first (both internal speakers and headphones), but after a while (especially when opening CPU-intensive webpages in Firefox) gets very choppy. Pulseaudio's CPU usage gets to around 50% and stays there until I close the application that uses audio (I'm assuming this is what causes the choppiness). Neither killing Getting the following
|
Installed GalliumOS 3.0alpha2, the issue persists. The kernel version is 4.16.13. Not getting the above
Also the maximum volume on 3.0alpha2 is much quieter. |
The maximum volume with GalliumOS 3.0 (kernel 4.16.18-galliumos) is too quiet on Acer Chromebook 11 (CB3-131), GNAWTY, 2016, Intel Bay Trail with MrChromebox RW_LEGACY firmware. This works fine with GalliumOS 2.1. |
This fixed both my internal mic & distorted audio problems - Gallium OS 3.1 on SWANKY |
I just realized I haven't had any audio problems in a while on my GNAWTY. I can suspend, unsuspend, plug in headphones, pull them out, put them in again, it all works. Before it would work (usually) until I put it to sleep or plugged in headphones, and after that it would stutter to an unusuable degree; sometimes plugging in headphones a second time would reset something and fix it temporarily, but then sometimes it would start stuttering again in a bit anyway. But no more! I thought I would have to wait for Gallium 4.0 to have this fixed but maybe something happened in Ubuntu that inadvertently fixed the audio glitches. Here's versions:
|
Ah nevermind I jinxed it. My sound is all glitchy right now. I'm sure a reboot will bring it back. |
Initial report was on kernel 4.1.14-galliumos.
Reported on IRC:
Reported problems on:
Reported no problems on:
UPDATES
The text was updated successfully, but these errors were encountered: