-
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
No sound on Bay Trail (SWANKY, GNAWTY) #66
Comments
This is the solution according to John Leiws: https://johnlewis.ie/procedure-to-get-sound-working-in-fedora-22-on-asus-c300-chromebook/ . We are using a new enough kernel for this to work. If someone could follow the instructions in the link above, save the state with: sudo alsactl store, then send us /var/lib/alsa/sound.state, we could include it. |
This is a better fix: https://plus.google.com/+JamesFuBEEFCAKE/posts/Tf4Pc5Z8reH . It includes the alsa state file from ChromeOS and a fix to mute the speakers when the headphones are plugged in. |
I switched out the alsa state file, however, sound playback was still not working on my swanky. I then also installed an intel firmware that worked for me in 14.04.3 Trusty, but again sound did not work. |
I suppose now we should start looking for potential missing kernel modules.... |
Same problem reported on GNAWTY, so I'll update the title of the issue. I think the GalliumOS kernel includes support for Bay Trail sound as a module: ( |
The alsa state file needs to be replaced, but it could be overwritten by the alsa-store service which runs before rebooting. @Ravoz can you verify that the alsa state file is the same as the downloaded one once you reboot? I think you need to either the disable the alsa-store service and then re-enable it after you reboot with the new state file, or copy the state file and then run the alsa-restore service. |
[Apparently] This works [OOB] on Ubuntu 15.10. Update: After some further research, there are quite a few mixed reports on this. |
@hugegreenbug , I'm away on a business trip this weekend, but I'll see if I can take a look at it. But it may be Monday. @ColtonDRG , for me at least on Swanky, with 15.10, to get sound working still requires replacing the asound.state file. 15.10 did fix automatic headphone muting though. |
Hm, well, other users claimed that it worked OOB on other Bay Trail models. Whatever happens, we'll get it fixed, hopefully before 1.0. Hopefully we'll get our hands on a Bay Trail model before then as well. :D |
@Ravoz Ok, whenever you have time. I also realized that I have a sound fix for the other models that is probably messing things up here. Could you also try to move /etc/modprobe.d/snd-hda-intel.conf out of the way and reboot? Thanks. |
Hi folks, Toshiba CB2 user here also, I have successfully installed GalliumOS via usb. Everything looks pretty good, but no sound either, I have tried the various methods above also. Willing to help out if I can. Toshiba CB2 CB30-B-104 |
@c0nsaw Did you move the file: /etc/modprobe.d/snd-hda-intel.conf out of the way? Did you try the asound.state file and if you did, did you verify that it was the same file you copied over after you rebooted? |
@hugegreenbug , I moved /ect/modprobe.dsnd-hda-intel.conf out of the way, however, after rebooting I get "failed login command"? I will have to wait until Monday to make a new live usb and try again. I'll also confirm that the asound.state isn't being overwritten. |
@Ravoz You can probably recover your existing install by using a vt to login and undo whatever you did to break it. |
@hugegreenbug Hi, I renamed /etc/modprobe.d/snd-hda-intel.conf to snd-hda-intel.conf.old , but left in same location. Yes I did try the asound.state file, but no I did not verify the file was the same after reboot. I will do again, and report back to you. Thanks :) |
@c0nsaw Is there anything in dmesg related to the sound? |
I just installed Beta 1 Haswell ISO on my Toshiba Chromebook 2 (baytrail, swanky) and I have no sound. Things done so far:
[ 4.593709] byt-max98090 byt-max98090: ASoC: CPU DAI baytrail-pcm-audio not registered I did see some posts about 15.10 resolving some audio issues for these models. Hope this info helps - everything seems to be good (some rough spots like Chrome/Chromium - don't see way to switch to Chrome/icon errors, and some other UI oddities but seems mostly stable) |
I am getting a GNAWTY from Google to work on during the month of December. I hope to get the issue (and any other issues) worked out during my time with it. |
@drghuser could you try this: |
I remember seeing this in my research - let me try it and I'll post results. FYI - Power management seems to be working very well (getting perhaps better battery life than ChromeOS). Chromium is definitely slower than stock ChromeOS with Chrome - not sure if there is room for improvement in future builds or not, but thought I'd mention it. |
Not getting the results described by the person in that post - quote from his post: "uninstall linux-firmware, and be sure there is nothing remaining in /lib/firmware/intel. Finally copy the contents of the chromium repo (click tgz to download) to /lib/firmware/intel. You should see an audio device on next boot." and for the repo is referring to "https://chromium.googlesource.com/chromiumos/third_party/linux-firmware/+/refs/heads/stabilize-5339.B/intel/" I tried uninstalling and just copying, and I also tried reinstalling and copying over; neither had positive results. Uninstalling and just copying resulted in no wireless, no sound, etc. I will try to follow up with that person and see if maybe there was more to it, though the article is about a year old. |
I just checked dmesg and that error is gone, so I'm going to try doing the state file. |
OK, so maybe there was no progress - I read more through dmesg and I found: [ 4.593101] byt-max98090 byt-max98090: ASoC: CPU DAI baytrail-pcm-audio not registered before the good entries: [ 4.693548] max98090 i2c-193C9890:00: MAX98090 REVID=0x43 Also, I just recopied (and did a alsactl restore) to try to get it to keep the asound.state file. In the end, no change; In fact, in some combinations of these changes the volume up key does nothing but mute and volume down work, and in other combinations of various fixes I believe volume up and down worked but I'm not sure about mute. Let me know if you have other ideas - I will continue re-reading the various posts from the past year or two with people installing linux on baytrail devices. |
Welp, I excitedly installed GalliumOS w/o grabbing the kernel config from the boot partition of my C300's Debian. Digging through my build machine now, hopefully it's around here somewhere. I'll also take a look at Fedora's default kernel configurations, as I know sound works on them with aforementioned steps |
Looking at a diff between your kernel config and Fedora's kernel config doesn't tell me much. Granted, diff output gives me a headache, and the Fedora kernel config is 4.4 whereas yours is 4.1. From what I can tell, there aren't any options in Fedora that aren't enabled on Gallium's Linux. Here's the diff output if anyone wants to take a look:
UPDATE: About to run kernel build. Unfortunately I have to build it on a crappy 5th-gen mobile i3 tonight so it'll take all night. I'll report results tomorrow afternoon. |
Several things I have read led me to believe that the issue was at the kernel level, that the successful installations of various iterations of linux that had working sound were all newer kernel releases. |
GNAWTY reported fixed here: (parent of) https://www.reddit.com/r/GalliumOS/comments/3to9lj/toshiba_chromebook_2_no_sound/cxuqvcy |
https://www.youtube.com/watch?v=7WBueo144T8 Those were made using Linux 4.3 from Ubuntu's mainline kernel PPA. |
Interesting @reynhout - the steps in the script mentioned in that post seem to be the exact same things I have been doing manually, though I have been using James Fu's asound.state file. I will run this script tonight/tomorrow and post my results. The video from @ColtonDRG gives me hope! :-) |
I didn't use that script. I used good old fashioned research and elbow grease. Remember I have to make this happen by default in the galliumos-baytrail package. ;) |
Well my research and elbow grease haven't worked yet, and like I said that script appears to be exactly what I have found to be supposedly working for others (just automated) and not yet succesful for me. He just replaced the firmware and the asound.state and made sure the speakers are unmuted. |
@ColtonDRG Let me know if you have something you want me to burn to a flashdrive and try booting from in my Toshiba Chromebook 2 CB35 3330 (swanky/baytrail) |
I don't plan on building any isos just yet, but I will ask you to remove whatever device package you have and install galliumos-baytrail from the testing repo whenever I have it ready. |
Can I just liveboot from USB (when it's ready) just to make sure it's OK before making the changes to the installed copy? Also, when it is ready and looks good from live USB boot I would do the following to remove the package like you requested above: |
I don't know. I'll try it once I have the package ready. I'll inquire about getting nightlies built as well. Yes. Those are the correct commands for removing, but you'll have to install galliumos-base-dev first to get the testing repository. |
The haswell iso ran fine (other than no sound) from USB, that is what convinced me to dive in and install it to the internal drive. |
I think the broadwell is actually closer to being correct, but on this kip it doesn't seem to make any difference no matter what galliumos-device package is installed, or even if none are. |
Okay, I'm ready for someone to test now... Please download this file You should start hearing audio as soon as the package is installed, but if you don't, reboot. If you still don't hear audio after a reboot, check to make sure the default sink is set correctly in PulseAudio (it should be I eagerly await anyone's results. This worked for me on Kip. We need it tested on as many Bay Trails as possible. P.S. You may need to manually reinstall galliumos-laptop afterwards with |
I did the manual remove (per suggestion) and then installed the package and rebooted. Everything worked without needing to change default device (though I I think I did that earlier when testing other fixes). I also checked the package manager and galliumos-laptop was listed as installed and everything seems to be good so far. Sound!!! Thank you @ColtonDRG !! |
I have a second Toshiba Chromebook 2 on it's way to me. I like this one (the one I'm building for a gift) so much that I bought one for myself. Refurb new from Toshiba $160 on eBay (they have several if anyone wants one) |
It's done.... Audio works perfectly on kip. https://youtu.be/CsQrxTrALb4 To achieve the proper switching between headphones and speakers, we stole the entire ALSA system from kernel 4.2.7. The new kernel is here. This should be uploaded to the testing repos soon, but you can download it straight from here if you can't wait. https://cdn.coltondrg.com/linux-image-4.1.14-galliumos_6_amd64.deb And in case you missed it before, the galliumos-baytrail package is here. https://cdn.coltondrg.com/galliumos-baytrail-0.1.1.deb You can install both of these packages with After installing both of those and rebooting, you should have perfect audio. I won't close the issue until we have more testing results in, but it's hereby fixed! |
Just got done installing everything, and I can confirm it works on the Gnawty. Thank you all very much for all your efforts!! |
Good work!! Thank you, glad you got it working :D |
If someone finds some device that's not working, let me know. I'll reopen. |
Wow, this is an old issue. Someone on the subreddit reported speakers not working, wonder if this could have anything to do with that. It was a Bay Trail, Asus 300C. https://www.reddit.com/r/GalliumOS/comments/4ac0c5/i_messed_up_my_audio_settings_badly_can_i/ |
It could be related, but I don't know. Unless that device has something different that's the key, it seems unlikely that it's directly related. Audio is pretty much good on Bay Trail now. (there are a couple bugs) |
I have no sound on GNAWTY with latest kernel =(
but with that kernel suspend does not work :-)
dmesg output: https://gist.github.com/gmykhailiuta/6cd967d42caa159621581fd0af5e8c7f |
@gmykhailiuta this is a new issue, I will open a new ticket. EDIT: #258 |
Cool! Thank you a lot, @reynhout ! |
I'm going to lock this, since it's long dead. Any future Bay Trail sound issues should be in new tickets, thanks. :) |
Reported by Bergauk via IRC.
Initial report on Toshiba CB35 Chromebook 2
Toshiba CB2 CB35-B3340
John Lewis ROM
Otherwise, install went well and initial testing is positive.
The text was updated successfully, but these errors were encountered: