Skip to content
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

Closed
reynhout opened this issue Nov 12, 2015 · 98 comments
Closed

No sound on Bay Trail (SWANKY, GNAWTY) #66

reynhout opened this issue Nov 12, 2015 · 98 comments

Comments

@reynhout
Copy link
Member

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.

@hugegreenbug
Copy link
Member

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.

@hugegreenbug
Copy link
Member

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.

@Ravoz
Copy link

Ravoz commented Nov 12, 2015

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.

@ghost
Copy link

ghost commented Nov 12, 2015

I suppose now we should start looking for potential missing kernel modules....

@reynhout
Copy link
Member Author

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: (CONFIG_SND_SOC_INTEL_BAYTRAIL=m and CONFIG_SND_SOC_INTEL_BYT_MAX98090_MACH=m), so the problem might be at a higher layer.

@reynhout reynhout changed the title No sound on Toshiba CB35 Chromebook 2 (SWANKY, Bay Trail) No sound on Bay Trail (SWANKY, GNAWTY) Nov 13, 2015
@hugegreenbug
Copy link
Member

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.

@ghost
Copy link

ghost commented Nov 13, 2015

[Apparently] This works [OOB] on Ubuntu 15.10.

Update: After some further research, there are quite a few mixed reports on this.

@Ravoz
Copy link

Ravoz commented Nov 14, 2015

@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.

@ghost
Copy link

ghost commented Nov 14, 2015

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

@hugegreenbug
Copy link
Member

@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.

@c0nsaw
Copy link

c0nsaw commented Nov 14, 2015

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
John Lewis ROM

@hugegreenbug
Copy link
Member

@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?

@Ravoz
Copy link

Ravoz commented Nov 14, 2015

@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.

@ghost
Copy link

ghost commented Nov 14, 2015

@Ravoz You can probably recover your existing install by using a vt to login and undo whatever you did to break it.

@c0nsaw
Copy link

c0nsaw commented Nov 14, 2015

@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 :)

@hugegreenbug
Copy link
Member

@c0nsaw Is there anything in dmesg related to the sound?

@ghost ghost removed the baytrail label Nov 16, 2015
@drghuser
Copy link

I just installed Beta 1 Haswell ISO on my Toshiba Chromebook 2 (baytrail, swanky) and I have no sound.

Things done so far:

  1. I tried replacing the state file with the one from James Fu (https://plus.google.com/+JamesFuBEEFCAKE/posts/Tf4Pc5Z8reH), and I confirm that the file gets overwritten during boot (also tried using restore command to force it to use my new sound state file - didn't work).
  2. I modified the settings file /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf to address the reported issue (when you DO get sound working) with headphones:
    [Element Speaker]
    switch = mute
    volume = zero
  3. I ran dmesg and saw these errors relating to the sound:

[ 4.593709] byt-max98090 byt-max98090: ASoC: CPU DAI baytrail-pcm-audio not registered
[ 4.593716] byt-max98090 byt-max98090: snd_soc_register_card failed -517

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)

@ghost
Copy link

ghost commented Nov 24, 2015

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.

@hugegreenbug
Copy link
Member

@drghuser
Copy link

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.

@drghuser
Copy link

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.

@drghuser
Copy link

I just checked dmesg and that error is gone, so I'm going to try doing the state file.
[ 4.691389] max98090 i2c-193C9890:00: MAX98090 REVID=0x43
[ 4.699544] byt-max98090 byt-max98090: HiFi <-> baytrail-pcm-audio mapping ok
[ 4.702793] input: byt-max98090 Headset as /devices/platform/80860F28:00/byt-max98090/sound/card1/input10

@drghuser
Copy link

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
[ 4.593109] byt-max98090 byt-max98090: snd_soc_register_card failed -517

before the good entries:

[ 4.693548] max98090 i2c-193C9890:00: MAX98090 REVID=0x43
[ 4.701953] byt-max98090 byt-max98090: HiFi <-> baytrail-pcm-audio mapping ok
[ 4.704858] input: byt-max98090 Headset as /devices/platform/80860F28:00/byt-max98090/sound/card1/input10

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.

@drsn0w
Copy link

drsn0w commented Dec 9, 2015

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

@drsn0w
Copy link

drsn0w commented Dec 9, 2015

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:
(I ran cat config-x86-generic-fedora | grep SND > config-x86-generic-fedora-snd and cat linux-config-gallium | grep SND > linux-config-gallium-snd to filter out the sound related options)

icefish332 ~/gallium-linux $ diff linux-config-gallium-snd config-x86-generic-fedora-snd 
1,163d0
< CONFIG_SND=m
< CONFIG_SND_TIMER=m
< CONFIG_SND_PCM=m
< CONFIG_SND_DMAENGINE_PCM=m
< CONFIG_SND_HWDEP=m
< CONFIG_SND_RAWMIDI=m
< CONFIG_SND_COMPRESS_OFFLOAD=m
< CONFIG_SND_JACK=y
< CONFIG_SND_SEQUENCER=m
< CONFIG_SND_SEQ_DUMMY=m
< CONFIG_SND_OSSEMUL=y
< CONFIG_SND_MIXER_OSS=m
< CONFIG_SND_PCM_OSS=m
< CONFIG_SND_PCM_OSS_PLUGINS=y
< # CONFIG_SND_SEQUENCER_OSS is not set
< CONFIG_SND_HRTIMER=m
< CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
< CONFIG_SND_DYNAMIC_MINORS=y
< CONFIG_SND_MAX_CARDS=32
< CONFIG_SND_SUPPORT_OLD_API=y
< CONFIG_SND_VERBOSE_PROCFS=y
< # CONFIG_SND_VERBOSE_PRINTK is not set
< # CONFIG_SND_DEBUG is not set
< CONFIG_SND_VMASTER=y
< CONFIG_SND_KCTL_JACK=y
< CONFIG_SND_DMA_SGBUF=y
< CONFIG_SND_RAWMIDI_SEQ=m
< # CONFIG_SND_OPL3_LIB_SEQ is not set
< # CONFIG_SND_OPL4_LIB_SEQ is not set
< # CONFIG_SND_SBAWE_SEQ is not set
< # CONFIG_SND_EMU10K1_SEQ is not set
< CONFIG_SND_MPU401_UART=m
< CONFIG_SND_AC97_CODEC=m
< CONFIG_SND_DRIVERS=y
< CONFIG_SND_PCSP=m
< CONFIG_SND_DUMMY=m
< CONFIG_SND_ALOOP=m
< CONFIG_SND_VIRMIDI=m
< CONFIG_SND_MTPAV=m
< CONFIG_SND_SERIAL_U16550=m
< CONFIG_SND_MPU401=m
< CONFIG_SND_AC97_POWER_SAVE=y
< CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0
< CONFIG_SND_PCI=y
< # CONFIG_SND_AD1889 is not set
< # CONFIG_SND_ALS300 is not set
< # CONFIG_SND_ALS4000 is not set
< # CONFIG_SND_ALI5451 is not set
< # CONFIG_SND_ASIHPI is not set
< # CONFIG_SND_ATIIXP is not set
< # CONFIG_SND_ATIIXP_MODEM is not set
< # CONFIG_SND_AU8810 is not set
< # CONFIG_SND_AU8820 is not set
< # CONFIG_SND_AU8830 is not set
< # CONFIG_SND_AW2 is not set
< # CONFIG_SND_AZT3328 is not set
< # CONFIG_SND_BT87X is not set
< # CONFIG_SND_CA0106 is not set
< # CONFIG_SND_CMIPCI is not set
< # CONFIG_SND_OXYGEN is not set
< # CONFIG_SND_CS4281 is not set
< # CONFIG_SND_CS46XX is not set
< # CONFIG_SND_CTXFI is not set
< # CONFIG_SND_DARLA20 is not set
< # CONFIG_SND_GINA20 is not set
< # CONFIG_SND_LAYLA20 is not set
< # CONFIG_SND_DARLA24 is not set
< # CONFIG_SND_GINA24 is not set
< # CONFIG_SND_LAYLA24 is not set
< # CONFIG_SND_MONA is not set
< # CONFIG_SND_MIA is not set
< # CONFIG_SND_ECHO3G is not set
< # CONFIG_SND_INDIGO is not set
< # CONFIG_SND_INDIGOIO is not set
< # CONFIG_SND_INDIGODJ is not set
< # CONFIG_SND_INDIGOIOX is not set
< # CONFIG_SND_INDIGODJX is not set
< # CONFIG_SND_EMU10K1 is not set
< # CONFIG_SND_EMU10K1X is not set
< # CONFIG_SND_ENS1370 is not set
< # CONFIG_SND_ENS1371 is not set
< # CONFIG_SND_ES1938 is not set
< # CONFIG_SND_ES1968 is not set
< # CONFIG_SND_FM801 is not set
< # CONFIG_SND_HDSP is not set
< # CONFIG_SND_HDSPM is not set
< # CONFIG_SND_ICE1712 is not set
< # CONFIG_SND_ICE1724 is not set
< CONFIG_SND_INTEL8X0=m
< CONFIG_SND_INTEL8X0M=m
< # CONFIG_SND_KORG1212 is not set
< # CONFIG_SND_LOLA is not set
< # CONFIG_SND_LX6464ES is not set
< # CONFIG_SND_MAESTRO3 is not set
< # CONFIG_SND_MIXART is not set
< # CONFIG_SND_NM256 is not set
< # CONFIG_SND_PCXHR is not set
< # CONFIG_SND_RIPTIDE is not set
< # CONFIG_SND_RME32 is not set
< # CONFIG_SND_RME96 is not set
< # CONFIG_SND_RME9652 is not set
< # CONFIG_SND_SE6X is not set
< # CONFIG_SND_SONICVIBES is not set
< # CONFIG_SND_TRIDENT is not set
< # CONFIG_SND_VIA82XX is not set
< # CONFIG_SND_VIA82XX_MODEM is not set
< # CONFIG_SND_VIRTUOSO is not set
< # CONFIG_SND_VX222 is not set
< # CONFIG_SND_YMFPCI is not set
< CONFIG_SND_HDA=m
< CONFIG_SND_HDA_INTEL=m
< CONFIG_SND_HDA_DSP_LOADER=y
< CONFIG_SND_HDA_PREALLOC_SIZE=64
< CONFIG_SND_HDA_HWDEP=y
< CONFIG_SND_HDA_RECONFIG=y
< CONFIG_SND_HDA_INPUT_BEEP=y
< CONFIG_SND_HDA_INPUT_BEEP_MODE=0
< CONFIG_SND_HDA_INPUT_JACK=y
< CONFIG_SND_HDA_PATCH_LOADER=y
< CONFIG_SND_HDA_CODEC_REALTEK=m
< CONFIG_SND_HDA_CODEC_ANALOG=m
< CONFIG_SND_HDA_CODEC_SIGMATEL=m
< CONFIG_SND_HDA_CODEC_VIA=m
< CONFIG_SND_HDA_CODEC_HDMI=m
< CONFIG_SND_HDA_I915=y
< CONFIG_SND_HDA_CODEC_CIRRUS=m
< CONFIG_SND_HDA_CODEC_CONEXANT=m
< CONFIG_SND_HDA_CODEC_CA0110=m
< CONFIG_SND_HDA_CODEC_CA0132=m
< CONFIG_SND_HDA_CODEC_CA0132_DSP=y
< CONFIG_SND_HDA_CODEC_CMEDIA=m
< CONFIG_SND_HDA_CODEC_SI3054=m
< CONFIG_SND_HDA_GENERIC=m
< CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
< CONFIG_SND_HDA_CORE=m
< CONFIG_SND_USB=y
< CONFIG_SND_USB_AUDIO=m
< CONFIG_SND_USB_UA101=m
< CONFIG_SND_USB_USX2Y=m
< CONFIG_SND_USB_CAIAQ=m
< CONFIG_SND_USB_CAIAQ_INPUT=y
< CONFIG_SND_USB_US122L=m
< CONFIG_SND_USB_6FIRE=m
< CONFIG_SND_USB_HIFACE=m
< CONFIG_SND_BCD2000=m
< # CONFIG_SND_USB_POD is not set
< # CONFIG_SND_USB_PODHD is not set
< # CONFIG_SND_USB_TONEPORT is not set
< # CONFIG_SND_USB_VARIAX is not set
< # CONFIG_SND_PCMCIA is not set
< CONFIG_SND_SOC=m
< CONFIG_SND_SOC_GENERIC_DMAENGINE_PCM=y
< CONFIG_SND_ATMEL_SOC=m
< CONFIG_SND_DESIGNWARE_I2S=m
< CONFIG_SND_SOC_FSL_ASRC=m
< CONFIG_SND_SOC_FSL_SAI=m
< CONFIG_SND_SOC_FSL_SSI=m
< CONFIG_SND_SOC_FSL_SPDIF=m
< CONFIG_SND_SOC_FSL_ESAI=m
< CONFIG_SND_SOC_IMX_AUDMUX=m
< CONFIG_SND_SST_MFLD_PLATFORM=m
< CONFIG_SND_SST_IPC=m
< CONFIG_SND_SST_IPC_ACPI=m
166,167d2
< CONFIG_SND_SOC_INTEL_HASWELL=m
< CONFIG_SND_SOC_INTEL_BAYTRAIL=m
168a4,5
> CONFIG_SND_SOC_INTEL_BROADWELL_MACH=m
> CONFIG_SND_SOC_INTEL_BAYTRAIL=m
171d7
< CONFIG_SND_SOC_INTEL_BROADWELL_MACH=m
174,241c10,15
< # CONFIG_SND_SOC_INTEL_CHT_BSW_RT5645_MACH is not set
< # CONFIG_SND_SOC_QCOM is not set
< # CONFIG_SND_SOC_XTFPGA_I2S is not set
< CONFIG_SND_SOC_I2C_AND_SPI=m
< CONFIG_SND_SOC_ADAU1701=m
< CONFIG_SND_SOC_AK4554=m
< CONFIG_SND_SOC_AK4642=m
< CONFIG_SND_SOC_AK5386=m
< CONFIG_SND_SOC_ALC5623=m
< CONFIG_SND_SOC_CS35L32=m
< CONFIG_SND_SOC_CS42L51=m
< CONFIG_SND_SOC_CS42L51_I2C=m
< CONFIG_SND_SOC_CS42L52=m
< CONFIG_SND_SOC_CS42L56=m
< CONFIG_SND_SOC_CS42L73=m
< CONFIG_SND_SOC_CS4265=m
< CONFIG_SND_SOC_CS4270=m
< CONFIG_SND_SOC_CS4271=m
< CONFIG_SND_SOC_CS4271_I2C=m
< CONFIG_SND_SOC_CS42XX8=m
< CONFIG_SND_SOC_CS42XX8_I2C=m
< CONFIG_SND_SOC_HDMI_CODEC=m
< CONFIG_SND_SOC_ES8328=m
< CONFIG_SND_SOC_MAX98090=m
< CONFIG_SND_SOC_PCM1681=m
< CONFIG_SND_SOC_PCM512x=m
< CONFIG_SND_SOC_PCM512x_I2C=m
< CONFIG_SND_SOC_RL6231=m
< CONFIG_SND_SOC_RT286=m
< CONFIG_SND_SOC_RT5631=m
< CONFIG_SND_SOC_RT5640=m
< CONFIG_SND_SOC_RT5670=m
< # CONFIG_SND_SOC_RT5677_SPI is not set
< CONFIG_SND_SOC_SGTL5000=m
< CONFIG_SND_SOC_SIGMADSP=m
< CONFIG_SND_SOC_SIGMADSP_I2C=m
< CONFIG_SND_SOC_SIRF_AUDIO_CODEC=m
< CONFIG_SND_SOC_SPDIF=m
< CONFIG_SND_SOC_SSM2602=m
< CONFIG_SND_SOC_SSM2602_I2C=m
< CONFIG_SND_SOC_SSM4567=m
< # CONFIG_SND_SOC_STA32X is not set
< CONFIG_SND_SOC_STA350=m
< CONFIG_SND_SOC_TAS2552=m
< CONFIG_SND_SOC_TAS5086=m
< CONFIG_SND_SOC_TFA9879=m
< CONFIG_SND_SOC_TLV320AIC23=m
< CONFIG_SND_SOC_TLV320AIC23_I2C=m
< CONFIG_SND_SOC_TLV320AIC31XX=m
< CONFIG_SND_SOC_TLV320AIC3X=m
< CONFIG_SND_SOC_TS3A227E=m
< CONFIG_SND_SOC_WM8510=m
< CONFIG_SND_SOC_WM8523=m
< CONFIG_SND_SOC_WM8580=m
< CONFIG_SND_SOC_WM8711=m
< CONFIG_SND_SOC_WM8728=m
< CONFIG_SND_SOC_WM8731=m
< CONFIG_SND_SOC_WM8737=m
< CONFIG_SND_SOC_WM8741=m
< CONFIG_SND_SOC_WM8750=m
< CONFIG_SND_SOC_WM8753=m
< CONFIG_SND_SOC_WM8776=m
< # CONFIG_SND_SOC_WM8804_I2C is not set
< CONFIG_SND_SOC_WM8903=m
< CONFIG_SND_SOC_WM8962=m
< CONFIG_SND_SOC_WM8978=m
< CONFIG_SND_SOC_TPA6130A2=m
< CONFIG_SND_SIMPLE_CARD=m
---
> CONFIG_SND_SOC_INTEL_CHT_BSW_RT5645_MACH=m
> CONFIG_SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH=m
> CONFIG_SND_SOC_INTEL_SKL_RT286_MACH=m
> CONFIG_SND_SOC_AC97_CODEC=m
> # CONFIG_SND_SOC_TAS571X is not set
> # CONFIG_SND_SUN4I_CODEC is not set

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.

@drghuser
Copy link

drghuser commented Dec 9, 2015

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.

@reynhout
Copy link
Member Author

@ghost
Copy link

ghost commented Dec 11, 2015

https://www.youtube.com/watch?v=7WBueo144T8
https://www.youtube.com/watch?v=0YaM09UpgfI

Those were made using Linux 4.3 from Ubuntu's mainline kernel PPA.
The first one works on Linux 4.1.6-galliumos, the second one doesn't.
More details coming soon.

@drghuser
Copy link

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! :-)

@ghost
Copy link

ghost commented Dec 11, 2015

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. ;)

@drghuser
Copy link

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.

@drghuser
Copy link

@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)

@ghost
Copy link

ghost commented Dec 11, 2015

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.

@drghuser
Copy link

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:
apt-get remove galliumos-haswell galliumos-broadwell galliumos-device-c710 galliumos-sandy
apt-get install galliumos-baytrail

@ghost
Copy link

ghost commented Dec 11, 2015

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.

@drghuser
Copy link

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.

@ghost
Copy link

ghost commented Dec 11, 2015

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.

@ghost
Copy link

ghost commented Dec 11, 2015

Okay, I'm ready for someone to test now...

Please download this file
https://cdn.coltondrg.com/galliumos-baytrail-0.1.1.deb
and install it with dpkg -i. It should remove the old haswell/broadwell/sandy packages automatically, but you should remove them manually beforehand, just in case. The command for that is sudo apt-get remove galliumos-haswell galliumos-broadwell galliumos-device-c710

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 byt-max98090). You can use pavucontrol for this.

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 sudo apt-get install galliumos-laptop.

@drghuser
Copy link

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 !!

@drghuser
Copy link

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)

@ghost
Copy link

ghost commented Dec 12, 2015

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
You can remove the old kernel with sudo apt-get remove linux-image-4.1.6-galliumos

And in case you missed it before, the galliumos-baytrail package is here. https://cdn.coltondrg.com/galliumos-baytrail-0.1.1.deb
Again, you can install that and it should remove the old stuff automatically, but just in case it doesn't, you can remove it manually with sudo apt-get remove galliumos-haswell galliumos-broadwell galliumos-device-c710. You may also need to reinstall galliumos-laptop manually after you've done that.

You can install both of these packages with dpkg -i

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!

@rolladude1166
Copy link

Just got done installing everything, and I can confirm it works on the Gnawty. Thank you all very much for all your efforts!!

@drsn0w
Copy link

drsn0w commented Dec 13, 2015

Good work!! Thank you, glad you got it working :D

@ghost
Copy link

ghost commented Dec 21, 2015

If someone finds some device that's not working, let me know. I'll reopen.

@dvdmuckle
Copy link
Member

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/

@ghost
Copy link

ghost commented Mar 15, 2016

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)

@gmykhailiuta
Copy link

I have no sound on GNAWTY with latest kernel =(
In my case, it's not even mentioned in dmesg.
I've tried "https://www.dropbox.com/s/dcg8g5rzha21v96/baytrail.sh?dl=0" with no luck.
Sound works on a bit older kernel:

linux-image-4.4.6-galliumos:
  Installed: 5

but with that kernel suspend does not work :-)
What could I try?

$ lsb_release -a 
No LSB modules are available.
Distributor ID: Ubuntu
Description:    GalliumOS 2.0
Release:    16.04
Codename:   xenial
$ uname -a
Linux cb.gen2.lan 4.5.5-galliumos #2 SMP PREEMPT Thu May 26 11:25:54 MDT 2016 x86_64 x86_64 x86_64 GNU/Linux

dmesg output: https://gist.github.com/gmykhailiuta/6cd967d42caa159621581fd0af5e8c7f

@reynhout
Copy link
Member Author

reynhout commented Jun 24, 2016

@gmykhailiuta this is a new issue, I will open a new ticket.

EDIT: #258

@gmykhailiuta
Copy link

Cool! Thank you a lot, @reynhout !

@ghost
Copy link

ghost commented Jun 27, 2016

I'm going to lock this, since it's long dead. Any future Bay Trail sound issues should be in new tickets, thanks. :)

@ghost ghost locked and limited conversation to collaborators Jun 27, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants