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

Braswell Platform Validation #270

Closed
reynhout opened this Issue Jul 28, 2016 · 433 comments

Comments

Projects
None yet
@reynhout
Member

reynhout commented Jul 28, 2016

Tracking validation tests and bug reports for GalliumOS support for Braswell models.

Initial testing on CYAN, but please add observations for any Braswell model in comments!

Current Braswell status

  • galliumos-braswell package created
  • Boots from USB ISO
  • Boots from internal storage (eMMC)
  • Touchpad
    • responsiveness issues (CELES, see comments in thread)
    • FIXED 20161022 in 4.7.2-galliumos6, thanks @jonaias
  • Wi-Fi
  • Bluetooth
  • Internal keyboard
    • NG (CYAN), external keyboard OK
    • NG in Ubuntu mainline kernel 4.4.15, 4.6.5
    • reported OK in Fedora 24 (Gnome/Cinnamon/MATE, kernel 4.5.5? 4.5.7? 4.6.5?)
    • reported OK in Ubuntu mainline kernel 4.7
    • FIXED in 4.7.2-galliumos2
  • Media keys
    • Volume control
      • reported OK in Ubuntu mainline kernel 4.7
      • FIXED in 4.7.2-galliumos2
    • LCD backlight control
      • reported OK in Ubuntu mainline kernel 4.7
      • FIXED in 4.7.2-galliumos2
  • Touchscreen
    • NG (CYAN)
    • reported OK in Ubuntu mainline 4.7 after rebuilding with CONFIG_TOUCHSCREEN_ELAN (this is already set in GalliumOS 4.4.6 config)
    • FIXED in 4.7.2-galliumos2
  • Suspend/resume
    • NG on GalliumOS kernel 4.7.2 (CYAN)
      • Freezes before successful suspend
        • Power LEDs are on solidly
        • If screenlock is disabled, LCD backlight stays on
        • No messages in logfiles
    • NG on Ubuntu mainline kernel 4.7
    • OK on GalliumOS kernel 4.4.6 (CYAN, EDGAR)
    • OK on GalliumOS kernel 4.7.2 (EDGAR)
    • reported OK on Fedora 24 kernel 4.5.5-300 (CELES)
    • required for 4.4.6? set tpm_tis.interrupts=0 in GRUB config
      • also possibly required (but not sufficient) for 4.7.2
    • WORKING 20160920 in 4.7.2-galliumos2
  • HDMI output
    • NG (CELES)
    • OK (CELES, IRC nskelsey)
    • Audio/video output working (EDGAR, 4.7.2 kernel) but requires manual enabling from Display Settings, doesn't auto-enable on cable insertion
    • WORKING but does not autoswitch
  • Internal audio out (most models)
    • speakers and headphones
    • WORKING audio 20170116 in 4.9.4-galliumos1
    • jack detection moved to new ticket: #318
  • Internal microphone moved to new ticket: #317, #319
  • Detect mode transition for convertible devices moved to new ticket: #316

Moved to new tickets:

  • Add mode transition detection for convertible devices (CYAN, ...) #316
  • Internal audio does not work on CYAN #317
  • Headphone jack detection fails on Braswell / Realtek ALC5645 #318
  • Internal microphone does not work on Braswell / Realtek ALC5645 #319

IMPORTANT NOTE REGARDING AUDIO

Braswell Chromebooks come with one of two audio chips: Maxim 98090 or Realtek ALC5650/5654. There are several reports of hardware speaker failures on models with the Realtek chip. There is a lot more discussion in the comments below.

  • Models with Maxim 98090
    • Acer Chromebook R11 CYAN
  • Models with Realtek ALC5650/5654
    • Acer Chromebook 14 EDGAR
    • Lenovo N22/N42 Chromebook REKS
    • HP Chromebook 11 G5 SETZER
    • Samsung Chromebook 3 (XE500C13) CELES
    • Acer Chromebook 15 (CB3-532) BANON
    • ASUS Chromebook C202SA TERRA
    • ASUS Chromebook C300SA TERRA
    • CTL NL61 Chromebook RELM
    • Lenovo ThinkPad 11e Chromebook G3 ULTIMA
    • Lenovo ThinkPad Yoga G3 ULTIMA
@MrChromebox

This comment has been minimized.

Show comment
Hide comment
@MrChromebox

MrChromebox Jul 28, 2016

Working:

  • Installation from Baytrail ISO successful
  • Boot from internal storage (emmc)
    +Trackpad
  • WiFi / Bluetooth

Broken:

  • Internal keyboard
  • Internal speakers
  • Internal mic
  • Suspend/resume (kernel 4.4.6-gallium, 4.4.15/4.7-generic: locks up on suspend)

dmesg: http://paste.ubuntu.com/21235464/

MrChromebox commented Jul 28, 2016

Working:

  • Installation from Baytrail ISO successful
  • Boot from internal storage (emmc)
    +Trackpad
  • WiFi / Bluetooth

Broken:

  • Internal keyboard
  • Internal speakers
  • Internal mic
  • Suspend/resume (kernel 4.4.6-gallium, 4.4.15/4.7-generic: locks up on suspend)

dmesg: http://paste.ubuntu.com/21235464/

@IlIlIlIlIlIlIl

This comment has been minimized.

Show comment
Hide comment
@IlIlIlIlIlIlIl

IlIlIlIlIlIlIl Aug 2, 2016

Tested USB BOOT on REKS (Lenovo N22) with identical results (keyboard and sound broken).

IlIlIlIlIlIlIl commented Aug 2, 2016

Tested USB BOOT on REKS (Lenovo N22) with identical results (keyboard and sound broken).

@MrChromebox

This comment has been minimized.

Show comment
Hide comment
@MrChromebox

MrChromebox Aug 5, 2016

CYAN user on G+ running Ubuntu 16.10 (a2?) reports that the keyboard is fixed with kernel 4.7

MrChromebox commented Aug 5, 2016

CYAN user on G+ running Ubuntu 16.10 (a2?) reports that the keyboard is fixed with kernel 4.7

@MrChromebox

This comment has been minimized.

Show comment
Hide comment
@MrChromebox

MrChromebox Aug 6, 2016

same user as above reports CYAN touchscreen works fine w/Ubuntu 4.7 when CONFIG_ELAN_TOUCHSCREEN is added

MrChromebox commented Aug 6, 2016

same user as above reports CYAN touchscreen works fine w/Ubuntu 4.7 when CONFIG_ELAN_TOUCHSCREEN is added

@lispykid

This comment has been minimized.

Show comment
Hide comment
@lispykid

lispykid Aug 19, 2016

Confirm: Kernel 4.7 brings the keyboard to life. Installed from Ubuntu, though.

lispykid commented Aug 19, 2016

Confirm: Kernel 4.7 brings the keyboard to life. Installed from Ubuntu, though.

@lispykid

This comment has been minimized.

Show comment
Hide comment
@lispykid

lispykid Aug 19, 2016

Can anyone point me to the compile flags for Gallium kernel? Then I could build one with the CONFIG_ELAN_TOUCHSCREEN flag and test the screen, too.

lispykid commented Aug 19, 2016

Can anyone point me to the compile flags for Gallium kernel? Then I could build one with the CONFIG_ELAN_TOUCHSCREEN flag and test the screen, too.

@MilitaryRiotLab

This comment has been minimized.

Show comment
Hide comment
@MilitaryRiotLab

MilitaryRiotLab commented Aug 19, 2016

@lispykid https://github.com/GalliumOS/linux/blob/master/.config I am a noob, please don't be harsh if it is wrong
EDIT: https://github.com/GalliumOS/linux/blob/baytrail/.config for baytrail (GalliumOS 4.4.6)

@lispykid

This comment has been minimized.

Show comment
Hide comment
@lispykid

lispykid Aug 22, 2016

My tiny script to rotate screen on the Acer R11. Useful for tentmode: /\

#!/bin/bash
STATE=`xrandr | grep eDP  | awk '{print $4}'`

if [[ $STATE == *"inverted"* ]]
then 
    xrandr -o normal    
else
    xrandr -o inverted
fi

lispykid commented Aug 22, 2016

My tiny script to rotate screen on the Acer R11. Useful for tentmode: /\

#!/bin/bash
STATE=`xrandr | grep eDP  | awk '{print $4}'`

if [[ $STATE == *"inverted"* ]]
then 
    xrandr -o normal    
else
    xrandr -o inverted
fi
@lispykid

This comment has been minimized.

Show comment
Hide comment
@lispykid

lispykid Aug 22, 2016

Volume and Brightness Keys are working in Ubuntu mainline kernel 4.7, btw.

lispykid commented Aug 22, 2016

Volume and Brightness Keys are working in Ubuntu mainline kernel 4.7, btw.

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Aug 22, 2016

Member

@lispykid Thanks, and I'll update the checklist.

Our WIP 4.7.0 kernel config is here: http://paste.ubuntu.com/23078327/

The touchscreen doesn't work yet -- it must require something more than CONFIG_TOUCHSCREEN_ELAN. I've gone through the diffs between Ubuntu and mainline and GalliumOS looking for something missing, but haven't found it yet.

Member

reynhout commented Aug 22, 2016

@lispykid Thanks, and I'll update the checklist.

Our WIP 4.7.0 kernel config is here: http://paste.ubuntu.com/23078327/

The touchscreen doesn't work yet -- it must require something more than CONFIG_TOUCHSCREEN_ELAN. I've gone through the diffs between Ubuntu and mainline and GalliumOS looking for something missing, but haven't found it yet.

@lispykid

This comment has been minimized.

Show comment
Hide comment
@lispykid

lispykid Aug 23, 2016

You tried: modprobe elants_i2c?

lispykid commented Aug 23, 2016

You tried: modprobe elants_i2c?

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Aug 23, 2016

Member

@lispykid No, I don't think so (I don't have the test device)...the driver should load automatically, shouldn't it?

Member

reynhout commented Aug 23, 2016

@lispykid No, I don't think so (I don't have the test device)...the driver should load automatically, shouldn't it?

@MrChromebox

This comment has been minimized.

Show comment
Hide comment
@MrChromebox

MrChromebox Aug 23, 2016

@lispykid there's a dmesg error on boot:
elants_i2c: error while waiting for calibration to complete: -110
full dmesg: https://paste.ubuntu.com/23082714

sudo modprobe elants_i2c returns normally.

MrChromebox commented Aug 23, 2016

@lispykid there's a dmesg error on boot:
elants_i2c: error while waiting for calibration to complete: -110
full dmesg: https://paste.ubuntu.com/23082714

sudo modprobe elants_i2c returns normally.

@MrChromebox

This comment has been minimized.

Show comment
Hide comment
@MrChromebox

MrChromebox Aug 23, 2016

also, for the keyboard working in 4.7.0-040700-generic (ubuntu) vs not in 4.7.0-galliumos we have:

i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 182
i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
i8042: Warning: Keylock active
i8042: probe of i8042 failed with error -22
vs
i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 182
i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
i8042: Warning: Keylock active
serio: i8042 KBD port at 0x60,0x64 irq 182
fwiw

MrChromebox commented Aug 23, 2016

also, for the keyboard working in 4.7.0-040700-generic (ubuntu) vs not in 4.7.0-galliumos we have:

i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 182
i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
i8042: Warning: Keylock active
i8042: probe of i8042 failed with error -22
vs
i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 182
i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
i8042: Warning: Keylock active
serio: i8042 KBD port at 0x60,0x64 irq 182
fwiw

@lispykid

This comment has been minimized.

Show comment
Hide comment
@lispykid

lispykid Aug 24, 2016

Ok, I played with pulseaudio yesterday but had no luck with the headphonejack. Will try wether the HDMI output works, at least the mixer looks like.

I wish I could be more helpful. I reinstalled my R11 yesterday with GalliumOS Testing and Gallium Kernel 4.7 but I don't know what more I could help. It's some years since I last built my own kernel. Maybe I should give it a try again. Can you point me in a good direction for starts?

lispykid commented Aug 24, 2016

Ok, I played with pulseaudio yesterday but had no luck with the headphonejack. Will try wether the HDMI output works, at least the mixer looks like.

I wish I could be more helpful. I reinstalled my R11 yesterday with GalliumOS Testing and Gallium Kernel 4.7 but I don't know what more I could help. It's some years since I last built my own kernel. Maybe I should give it a try again. Can you point me in a good direction for starts?

@MrChromebox

This comment has been minimized.

Show comment
Hide comment
@MrChromebox

MrChromebox Aug 24, 2016

@lispykid kb/touchpad/touchscreen all work in the Ubuntu 4.7 kernel (recompiled w/CONFIG_ELAN_TOUCHSCREEN=m), so now it's just determining what in the GalliumOS config is breaking things. Audio is a separate issue entirely though

MrChromebox commented Aug 24, 2016

@lispykid kb/touchpad/touchscreen all work in the Ubuntu 4.7 kernel (recompiled w/CONFIG_ELAN_TOUCHSCREEN=m), so now it's just determining what in the GalliumOS config is breaking things. Audio is a separate issue entirely though

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Sep 8, 2016

Member

Internal audio log messages (nonworking), extracted from MrChromebox's dmesg output on Ubuntu 4.7.0 mainline kernel:

[    6.523916] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    6.682138] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[    6.682313] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[    6.682459] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[    6.789370] cht-bsw-max98090 cht-bsw-max98090: ASoC: i2c-104C227E:00 not registered
[    6.789381] cht-bsw-max98090 cht-bsw-max98090: snd_soc_register_card failed -517
Member

reynhout commented Sep 8, 2016

Internal audio log messages (nonworking), extracted from MrChromebox's dmesg output on Ubuntu 4.7.0 mainline kernel:

[    6.523916] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    6.682138] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[    6.682313] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[    6.682459] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[    6.789370] cht-bsw-max98090 cht-bsw-max98090: ASoC: i2c-104C227E:00 not registered
[    6.789381] cht-bsw-max98090 cht-bsw-max98090: snd_soc_register_card failed -517
@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Sep 8, 2016

Member

4.7.2 kernel parms

  • SND_SOC_INTEL_BYT_MAX98090_MACH
  • SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH

(which enable the Maxim MAX98090 audio chip for Bay Trail and Cherry Trail/Braswell, respectively) appear to be mutually exclusive in Kconfig.

We might need to build separate kernels for Bay Trail and Braswell models.

Member

reynhout commented Sep 8, 2016

4.7.2 kernel parms

  • SND_SOC_INTEL_BYT_MAX98090_MACH
  • SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH

(which enable the Maxim MAX98090 audio chip for Bay Trail and Cherry Trail/Braswell, respectively) appear to be mutually exclusive in Kconfig.

We might need to build separate kernels for Bay Trail and Braswell models.

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Sep 10, 2016

Member

GalliumOS kernel 4.7.2-galliumos2 includes the following fixes for Braswell models:

  • Touchscreen
  • Internal keyboard
  • Media keys

Tested on CYAN (Many thanks to @MattDevo!)

If you are having suspend/resume issues, try setting tpm_tis.interrupts=0 in your GRUB kernel config. This will be already be set if you installed from ISO. Some configs might also (or instead) include tpm_tis.force=1, which should be equivalent, but it looks like we'll be preferring tpm_tis.interrupts=0 in future images.

This kernel does not include fixes for Braswell audio.

The new kernel package is currently in the galliumos-testing repodist only. To enable and install:

sudo galliumos-repodist --enable testing
galliumos-update
Member

reynhout commented Sep 10, 2016

GalliumOS kernel 4.7.2-galliumos2 includes the following fixes for Braswell models:

  • Touchscreen
  • Internal keyboard
  • Media keys

Tested on CYAN (Many thanks to @MattDevo!)

If you are having suspend/resume issues, try setting tpm_tis.interrupts=0 in your GRUB kernel config. This will be already be set if you installed from ISO. Some configs might also (or instead) include tpm_tis.force=1, which should be equivalent, but it looks like we'll be preferring tpm_tis.interrupts=0 in future images.

This kernel does not include fixes for Braswell audio.

The new kernel package is currently in the galliumos-testing repodist only. To enable and install:

sudo galliumos-repodist --enable testing
galliumos-update
@dh34751

This comment has been minimized.

Show comment
Hide comment
@dh34751

dh34751 Sep 10, 2016

Successfully tested on EDGAR.
galliumos-upgrade command was not found, tried galliumos-update instead and that seemed to work.

dh34751 commented Sep 10, 2016

Successfully tested on EDGAR.
galliumos-upgrade command was not found, tried galliumos-update instead and that seemed to work.

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Sep 10, 2016

Member

@dh34751 Sorry, typo! fixed. Thanks for testing!

Member

reynhout commented Sep 10, 2016

@dh34751 Sorry, typo! fixed. Thanks for testing!

@mschmortte

This comment has been minimized.

Show comment
Hide comment
@mschmortte

mschmortte Sep 13, 2016

@dh34751 How did you manage to install GalliumOS on EDGAR? Using chrx I installed GalliumOS but the keyboard isn't working. So I cannot login and upgrade/update. How did you do this?

mschmortte commented Sep 13, 2016

@dh34751 How did you manage to install GalliumOS on EDGAR? Using chrx I installed GalliumOS but the keyboard isn't working. So I cannot login and upgrade/update. How did you do this?

@MilitaryRiotLab

This comment has been minimized.

Show comment
Hide comment
@MilitaryRiotLab

MilitaryRiotLab Sep 13, 2016

@mschmortte I am also using EDGAR (Chromebook 14 CB3-431-C5FM). You need to use an external keyboard to upgrade the kernel

Working:

  • Suspend/resume

MilitaryRiotLab commented Sep 13, 2016

@mschmortte I am also using EDGAR (Chromebook 14 CB3-431-C5FM). You need to use an external keyboard to upgrade the kernel

Working:

  • Suspend/resume
@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Sep 13, 2016

Member

@mschmortte Good point. An external keyboard is still needed until we get the updated kernel into a nightly image build. Chrx will install the latest nightly build if it's run with -r nightly. (but again, the "latest" nightly build is still pre-kernel fix. I'll update this when we have a newer build pushed)

EDIT: Nightly images now include the keyboard config and all other patches for Braswell. Audio is still WIP.

@shamkoonyu Awesome. Thanks for the report!

Member

reynhout commented Sep 13, 2016

@mschmortte Good point. An external keyboard is still needed until we get the updated kernel into a nightly image build. Chrx will install the latest nightly build if it's run with -r nightly. (but again, the "latest" nightly build is still pre-kernel fix. I'll update this when we have a newer build pushed)

EDIT: Nightly images now include the keyboard config and all other patches for Braswell. Audio is still WIP.

@shamkoonyu Awesome. Thanks for the report!

@IlIlIlIlIlIlIl

This comment has been minimized.

Show comment
Hide comment
@IlIlIlIlIlIlIl

IlIlIlIlIlIlIl Sep 13, 2016

tested chrx install with REKS. Same behaviour as with other devices:

  • keyboard works with the new testing kernel
  • sound doesn't work (it sees the HDMI out as sound device, so it might work)

IlIlIlIlIlIlIl commented Sep 13, 2016

tested chrx install with REKS. Same behaviour as with other devices:

  • keyboard works with the new testing kernel
  • sound doesn't work (it sees the HDMI out as sound device, so it might work)
@mildred

This comment has been minimized.

Show comment
Hide comment
@mildred

mildred Sep 14, 2016

Audio initialization seems to be done in the firmware, see kernel bug #151521:

From the discussion over there it sounds to me that Coreboot itself does no sound initialization, but the 'depthcharge' payload started from Coreboot when booting to ChromeOS does do a codec init.

However SeaBIOS payload doesn't do anything sound initialization related so it'd be wished that the kernel would do that instead if it wasn't done by the Coreboot and its payload.

Wouldn't it be possible to use the same boot mechanism as Chromium OS so we get the same initialized state, and stop booting from SeaBIOS?

I'm running some tests in that direction (packing the fedora kernel + initramfs in the kernel signed partition) but I didn't manage to boot yet.

By the way, I'm running Fedora 24 on CYAN, and everything works well except audio and suspend.

mildred commented Sep 14, 2016

Audio initialization seems to be done in the firmware, see kernel bug #151521:

From the discussion over there it sounds to me that Coreboot itself does no sound initialization, but the 'depthcharge' payload started from Coreboot when booting to ChromeOS does do a codec init.

However SeaBIOS payload doesn't do anything sound initialization related so it'd be wished that the kernel would do that instead if it wasn't done by the Coreboot and its payload.

Wouldn't it be possible to use the same boot mechanism as Chromium OS so we get the same initialized state, and stop booting from SeaBIOS?

I'm running some tests in that direction (packing the fedora kernel + initramfs in the kernel signed partition) but I didn't manage to boot yet.

By the way, I'm running Fedora 24 on CYAN, and everything works well except audio and suspend.

@MrChromebox

This comment has been minimized.

Show comment
Hide comment
@MrChromebox

MrChromebox Sep 14, 2016

Wouldn't it be possible to use the same boot mechanism as Chromium OS so we get the same initialized state, and stop booting from SeaBIOS?

you're misunderstanding the issue; you're getting the "Same initialized state" now regardless of whether you boot ChromeOS via depthcharge or Linux via SeaBIOS. The BSW/CHT drivers in the mainline Linux kernels (4.5+) likely aren't (fully) resetting the codec/DSP properly as part of init, whereas the drivers in the ChromeOS kernel (3.1x) do. Changing the payload isn't going to help - you either need to cut out the init depthcharge is doing (eg, replace the payload like we do with the BOOT_STUB firmware on Baytrail) or fix the mainline kernel drivers.

MrChromebox commented Sep 14, 2016

Wouldn't it be possible to use the same boot mechanism as Chromium OS so we get the same initialized state, and stop booting from SeaBIOS?

you're misunderstanding the issue; you're getting the "Same initialized state" now regardless of whether you boot ChromeOS via depthcharge or Linux via SeaBIOS. The BSW/CHT drivers in the mainline Linux kernels (4.5+) likely aren't (fully) resetting the codec/DSP properly as part of init, whereas the drivers in the ChromeOS kernel (3.1x) do. Changing the payload isn't going to help - you either need to cut out the init depthcharge is doing (eg, replace the payload like we do with the BOOT_STUB firmware on Baytrail) or fix the mainline kernel drivers.

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Sep 14, 2016

Member

@mildred Setting tpm_tis.interrupts=0 in GRUB config has been reported to help with suspend/resume.

Member

reynhout commented Sep 14, 2016

@mildred Setting tpm_tis.interrupts=0 in GRUB config has been reported to help with suspend/resume.

@IlIlIlIlIlIlIl

This comment has been minimized.

Show comment
Hide comment
@IlIlIlIlIlIlIl

IlIlIlIlIlIlIl Sep 14, 2016

Most likely it's unrelated, but I just had a massive hardware failure with my REKS / Lenovo N22. Something badly overheated in laptop bag when using GalliumOS and lid suspend, parts of the plastic actually melted. Battery's the likely candidate. Computer works still, but obviously I cannot continue using this fire hazard :)

I'm returning this one and getting another model (Edgar most likely).

IlIlIlIlIlIlIl commented Sep 14, 2016

Most likely it's unrelated, but I just had a massive hardware failure with my REKS / Lenovo N22. Something badly overheated in laptop bag when using GalliumOS and lid suspend, parts of the plastic actually melted. Battery's the likely candidate. Computer works still, but obviously I cannot continue using this fire hazard :)

I'm returning this one and getting another model (Edgar most likely).

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Sep 14, 2016

Member

@IlIlIlIlIlIlIl Yikes! Well, EDGAR has less plastic to melt if you get another bad battery :)

Member

reynhout commented Sep 14, 2016

@IlIlIlIlIlIlIl Yikes! Well, EDGAR has less plastic to melt if you get another bad battery :)

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Jan 18, 2017

Member

This ticket is substantially complete!

Since the remaining issues are relatively minor, and/or don't affect all models, I'm going to move the remaining items to their own new issues, and close this epic ticket.

Open issues:

  • Add mode transition detection for convertible devices (CYAN, ...) #316
  • Internal audio does not work on CYAN #317
  • Headphone jack detection fails on Braswell / Realtek ALC5645 #318
  • Internal microphone does not work on Braswell / Realtek ALC5645 #319

Be sure to follow any of the new tickets of special interest to you.

Thanks for your help and patience.

Member

reynhout commented Jan 18, 2017

This ticket is substantially complete!

Since the remaining issues are relatively minor, and/or don't affect all models, I'm going to move the remaining items to their own new issues, and close this epic ticket.

Open issues:

  • Add mode transition detection for convertible devices (CYAN, ...) #316
  • Internal audio does not work on CYAN #317
  • Headphone jack detection fails on Braswell / Realtek ALC5645 #318
  • Internal microphone does not work on Braswell / Realtek ALC5645 #319

Be sure to follow any of the new tickets of special interest to you.

Thanks for your help and patience.

@reynhout reynhout closed this Jan 18, 2017

@wiredin

This comment has been minimized.

Show comment
Hide comment
@wiredin

wiredin Jan 28, 2017

My right speaker stopped working (edgar) in both gallium OS and Chrome OS after updating :-( I have Acer Chromebook 14 CB3-431-C7M1

wiredin commented Jan 28, 2017

My right speaker stopped working (edgar) in both gallium OS and Chrome OS after updating :-( I have Acer Chromebook 14 CB3-431-C7M1

@chiguireitor

This comment has been minimized.

Show comment
Hide comment
@chiguireitor

chiguireitor Jan 28, 2017

Did it overheat? try to get smell, if it smells as burnt, it's done for good. Also, try the dev-mode boot screen to make it beep, if it does beep loudly, it's just a driver problem.

chiguireitor commented Jan 28, 2017

Did it overheat? try to get smell, if it smells as burnt, it's done for good. Also, try the dev-mode boot screen to make it beep, if it does beep loudly, it's just a driver problem.

@wiredin

This comment has been minimized.

Show comment
Hide comment
@wiredin

wiredin Jan 28, 2017

@chiguireitor Thanks for the tips, there was no smell of heat. Just stopped working. It does not beep in dev-mode boot, only left speaker :-/

wiredin commented Jan 28, 2017

@chiguireitor Thanks for the tips, there was no smell of heat. Just stopped working. It does not beep in dev-mode boot, only left speaker :-/

@chiguireitor

This comment has been minimized.

Show comment
Hide comment
@chiguireitor

chiguireitor Jan 28, 2017

Yup, borked... my left one has very low and garbled sound, the right one just low.... so prolly you have to change as i've to do

chiguireitor commented Jan 28, 2017

Yup, borked... my left one has very low and garbled sound, the right one just low.... so prolly you have to change as i've to do

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Jan 28, 2017

Member

@wiredin how long ago did you update? There's nothing in the update process (or after it) that should make the problem more likely to occur -- but we don't know yet whether it makes it less likely.

The window will always exist where the machine is not-fully-booted (hardware initialized by ChromeOS bootloader only), which definitely does seem to be a higher risk state.

It's also possible that affected machines will "accumulate" minor damages over time (spending several seconds or a minute in the high risk state), which eventually lead to speaker failure.

I have no good suggestions. I still think that "fail fast, and be prepared to exchange defective hardware inside the convenient return period" is the best approach. Better than the other options, at least. :(

Member

reynhout commented Jan 28, 2017

@wiredin how long ago did you update? There's nothing in the update process (or after it) that should make the problem more likely to occur -- but we don't know yet whether it makes it less likely.

The window will always exist where the machine is not-fully-booted (hardware initialized by ChromeOS bootloader only), which definitely does seem to be a higher risk state.

It's also possible that affected machines will "accumulate" minor damages over time (spending several seconds or a minute in the high risk state), which eventually lead to speaker failure.

I have no good suggestions. I still think that "fail fast, and be prepared to exchange defective hardware inside the convenient return period" is the best approach. Better than the other options, at least. :(

@wiredin

This comment has been minimized.

Show comment
Hide comment
@wiredin

wiredin Jan 28, 2017

@reynhout this morning I did an update. I did.

sudo galliumos-repodist --enable testing
sudo galliumos-update

plus added the files @evan-a-a worked on
https://gist.github.com/evan-a-a/86b2a698708074530e2d0ee7c6498767

I will try exchanging my hardware.

wiredin commented Jan 28, 2017

@reynhout this morning I did an update. I did.

sudo galliumos-repodist --enable testing
sudo galliumos-update

plus added the files @evan-a-a worked on
https://gist.github.com/evan-a-a/86b2a698708074530e2d0ee7c6498767

I will try exchanging my hardware.

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Jan 28, 2017

Member

@wiredin OK, thank you for the info. Again, nothing in the update process should have been a trigger, but the issue has been ongoing. Were both speakers working directly before the update?

By the way, those files from @evan-a-a should be included in the package updates. Saves a step.

Member

reynhout commented Jan 28, 2017

@wiredin OK, thank you for the info. Again, nothing in the update process should have been a trigger, but the issue has been ongoing. Were both speakers working directly before the update?

By the way, those files from @evan-a-a should be included in the package updates. Saves a step.

@wiredin

This comment has been minimized.

Show comment
Hide comment
@wiredin

wiredin Jan 28, 2017

@reynhout yes both speakers were working, it was likely a coincidence that is when the problem occurred. I added the files manually because after galliumos-update and reboot the drivers did not appear. Should I have done apt-get update aswell?

wiredin commented Jan 28, 2017

@reynhout yes both speakers were working, it was likely a coincidence that is when the problem occurred. I added the files manually because after galliumos-update and reboot the drivers did not appear. Should I have done apt-get update aswell?

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Jan 28, 2017

Member

@wiredin No, galliumos-update runs apt update, so that should have picked everything up automatically. Curious.

Member

reynhout commented Jan 28, 2017

@wiredin No, galliumos-update runs apt update, so that should have picked everything up automatically. Curious.

@chharris88

This comment has been minimized.

Show comment
Hide comment
@chharris88

chharris88 Feb 1, 2017

Galliumos rocks. Thanks guys.

I'm on an Edgar Acer 14 on kernel 4.9.4, and I figured I'd mention that audio on the speakers was not working even after enabling prerelease and testing and running sudo apt-get dist-upgrade. Turns out there were two packages being held back: galliumos-baytrail and galliumos-braswell, since there was a dependency on the galliumos-baytrail (4.0.0 iirc) package that was currently installed. I forced the update with sudo apt-get install galliumos-braswell which I believe was 4.0.4, rebooted and found speakers to be working.

I don't exactly understand what happened there, but it worked for me.

chharris88 commented Feb 1, 2017

Galliumos rocks. Thanks guys.

I'm on an Edgar Acer 14 on kernel 4.9.4, and I figured I'd mention that audio on the speakers was not working even after enabling prerelease and testing and running sudo apt-get dist-upgrade. Turns out there were two packages being held back: galliumos-baytrail and galliumos-braswell, since there was a dependency on the galliumos-baytrail (4.0.0 iirc) package that was currently installed. I forced the update with sudo apt-get install galliumos-braswell which I believe was 4.0.4, rebooted and found speakers to be working.

I don't exactly understand what happened there, but it worked for me.

@bhjohnp1

This comment has been minimized.

Show comment
Hide comment
@bhjohnp1

bhjohnp1 Feb 3, 2017

I can confirm thatsudo apt-get install galliumos-braswell was needed to fix internal audio issues on my machine as well. (CELES) Thanks @chharris88 !!

bhjohnp1 commented Feb 3, 2017

I can confirm thatsudo apt-get install galliumos-braswell was needed to fix internal audio issues on my machine as well. (CELES) Thanks @chharris88 !!

@thecodingbandit

This comment has been minimized.

Show comment
Hide comment
@thecodingbandit

thecodingbandit Feb 4, 2017

Just installed galliumOS on my Acer 14 Edgar and couldn't get sound to work. Did hear a very weird noise coming from right speaker and also a bad burning smell. I quickly rebooted and the speakers do still seem to be working okay on chromiumOS but I'm kind of worried about them now. Any advice?

thecodingbandit commented Feb 4, 2017

Just installed galliumOS on my Acer 14 Edgar and couldn't get sound to work. Did hear a very weird noise coming from right speaker and also a bad burning smell. I quickly rebooted and the speakers do still seem to be working okay on chromiumOS but I'm kind of worried about them now. Any advice?

@rtreffer

This comment has been minimized.

Show comment
Hide comment
@rtreffer

rtreffer Feb 4, 2017

rtreffer commented Feb 4, 2017

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Feb 4, 2017

Member

@thecodingbandit Which version of, and how, did you install GalliumOS? There's a summary of the current status at https://wiki.galliumos.org/Support/Braswell .

So far there have been no reports of issues (while booted into GalliumOS) now that we load driver code for the audio chip.

Member

reynhout commented Feb 4, 2017

@thecodingbandit Which version of, and how, did you install GalliumOS? There's a summary of the current status at https://wiki.galliumos.org/Support/Braswell .

So far there have been no reports of issues (while booted into GalliumOS) now that we load driver code for the audio chip.

@thecodingbandit

This comment has been minimized.

Show comment
Hide comment
@thecodingbandit

thecodingbandit Feb 4, 2017

@reynhout I'm not sure which version (I installed using chrx as per: https://wiki.galliumos.org/Installing )
I used the firmware update script from MrChromebox (The first option, RW_LEGACY - I'm not entirely sure what exactly this does, however).

I ran a couple of update commands but nothing was downloaded (I think I have the most recent version)

thecodingbandit commented Feb 4, 2017

@reynhout I'm not sure which version (I installed using chrx as per: https://wiki.galliumos.org/Installing )
I used the firmware update script from MrChromebox (The first option, RW_LEGACY - I'm not entirely sure what exactly this does, however).

I ran a couple of update commands but nothing was downloaded (I think I have the most recent version)

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Feb 4, 2017

Member

@thecodingbandit The updates for Braswell audio still in the "prerelease" repository. The easy way to get them with a chrx install is to use the -r nightly option. Without that, you would have only been running with ChromeOS/depthcharge audio hardware init, which will not work (and appears to be the trigger for the problem with the Realtek chips).

Since you've already installed, you can update with:

sudo galliumos-repodist --enable prerelease
galliumos-update
sudo reboot

How long were you running GalliumOS after install before you noticed the sound/heat issue? If we're correct that the ChromeOS/depthcharge init is inadequate/problematic for affected machines, the issue might be mitigated by the audio init we've added to GalliumOS, but it will not be possible to eliminate without an update to ChromeOS firmware, as there will always be the time window between power on and full GalliumOS boot.

Member

reynhout commented Feb 4, 2017

@thecodingbandit The updates for Braswell audio still in the "prerelease" repository. The easy way to get them with a chrx install is to use the -r nightly option. Without that, you would have only been running with ChromeOS/depthcharge audio hardware init, which will not work (and appears to be the trigger for the problem with the Realtek chips).

Since you've already installed, you can update with:

sudo galliumos-repodist --enable prerelease
galliumos-update
sudo reboot

How long were you running GalliumOS after install before you noticed the sound/heat issue? If we're correct that the ChromeOS/depthcharge init is inadequate/problematic for affected machines, the issue might be mitigated by the audio init we've added to GalliumOS, but it will not be possible to eliminate without an update to ChromeOS firmware, as there will always be the time window between power on and full GalliumOS boot.

@thecodingbandit

This comment has been minimized.

Show comment
Hide comment
@thecodingbandit

thecodingbandit Feb 4, 2017

I had been using it for about two hours, it was only when I was troubleshooting the audio problems that the problem occurred.

I've updated to the prerelease version as above but it's still not picking up an audio device apart from the HDMI output.

thecodingbandit commented Feb 4, 2017

I had been using it for about two hours, it was only when I was troubleshooting the audio problems that the problem occurred.

I've updated to the prerelease version as above but it's still not picking up an audio device apart from the HDMI output.

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Feb 4, 2017

Member

@thecodingbandit Did you get any messages about packages being "held back" in galliumos-update? If so, run sudo apt install galliumos-braswell to resolve.

You should have galliumos-braswell package version 2.0.4 or later. Check with dpkg -l galliumos-braswell.

Member

reynhout commented Feb 4, 2017

@thecodingbandit Did you get any messages about packages being "held back" in galliumos-update? If so, run sudo apt install galliumos-braswell to resolve.

You should have galliumos-braswell package version 2.0.4 or later. Check with dpkg -l galliumos-braswell.

@thecodingbandit

This comment has been minimized.

Show comment
Hide comment
@thecodingbandit

thecodingbandit Feb 4, 2017

@reynhout That's got the audio working, thanks for your help. I'll definitely opt for the fail-fast testing process re: the speakers.

thecodingbandit commented Feb 4, 2017

@reynhout That's got the audio working, thanks for your help. I'll definitely opt for the fail-fast testing process re: the speakers.

@chharris88

This comment has been minimized.

Show comment
Hide comment
@chharris88

chharris88 Feb 6, 2017

Sorry to keep posting in a closed thread, but it does seem to be the only applicable issue..

I've been running the nightly updates on my Acer chromebook 14 Edgar for about a week now, and I thought it worthwhile to mention that one time, while in Galliumos 4.9.4, I experienced the speakers producing a squelching/distortion/static noise while not playing any audio. A reboot got this noise to subside, and the speakers appear to still be ok when subsequently playing audio, but I have taken to leaving them muted whenever they're not in use (not sure if that'll actually help) for fear of hardware failure. I understand issues arising during the boot sequence before Gallium is running, but this one got me a little worried. Anything I can do to assist testing @reynhout ?

chharris88 commented Feb 6, 2017

Sorry to keep posting in a closed thread, but it does seem to be the only applicable issue..

I've been running the nightly updates on my Acer chromebook 14 Edgar for about a week now, and I thought it worthwhile to mention that one time, while in Galliumos 4.9.4, I experienced the speakers producing a squelching/distortion/static noise while not playing any audio. A reboot got this noise to subside, and the speakers appear to still be ok when subsequently playing audio, but I have taken to leaving them muted whenever they're not in use (not sure if that'll actually help) for fear of hardware failure. I understand issues arising during the boot sequence before Gallium is running, but this one got me a little worried. Anything I can do to assist testing @reynhout ?

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Feb 6, 2017

Member

Re: headphone jack detection: Please update to galliumos-braswell 2.0.5 and reboot. This ticket is closed, so please post any related comments to ticket #318.

Member

reynhout commented Feb 6, 2017

Re: headphone jack detection: Please update to galliumos-braswell 2.0.5 and reboot. This ticket is closed, so please post any related comments to ticket #318.

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Feb 6, 2017

Member

@chharris88 Thanks for the info. Noise is not necessarily indicative of a problem state (aside from the existence of the noise itself), but the problem state does sometimes make noise. Not very insightful, I realize, but that's all we know at this point.

Unfortunately, the only way we'll know for certain is if we hear a report of speaker damage in a fully updated OS. If there have been no reports for a long enough time, we can probably guess that the additional init helps.

And again, the pre-boot window of risk will always exist (unless Google updates ChromeOS firmware to resolve).

Member

reynhout commented Feb 6, 2017

@chharris88 Thanks for the info. Noise is not necessarily indicative of a problem state (aside from the existence of the noise itself), but the problem state does sometimes make noise. Not very insightful, I realize, but that's all we know at this point.

Unfortunately, the only way we'll know for certain is if we hear a report of speaker damage in a fully updated OS. If there have been no reports for a long enough time, we can probably guess that the additional init helps.

And again, the pre-boot window of risk will always exist (unless Google updates ChromeOS firmware to resolve).

@tjyrinki

This comment has been minimized.

Show comment
Hide comment
@tjyrinki

tjyrinki Feb 8, 2017

There is a suggested fix to enabling sound on CYAN at https://bugzilla.kernel.org/show_bug.cgi?id=151521 now.

As another note it's been a long time but some may be interested in that Ubuntu kernels now finally have "Fix Committed" to re-enable touch screen and internal keyboard like GalliumOS has had for a long time. The fix should be published to 16.04, 16.10 and 17.04 in the next kernel updates. https://launchpad.net/bugs/1630238 for more information. I filed the bug in October when it regressed after having worked for some time.

tjyrinki commented Feb 8, 2017

There is a suggested fix to enabling sound on CYAN at https://bugzilla.kernel.org/show_bug.cgi?id=151521 now.

As another note it's been a long time but some may be interested in that Ubuntu kernels now finally have "Fix Committed" to re-enable touch screen and internal keyboard like GalliumOS has had for a long time. The fix should be published to 16.04, 16.10 and 17.04 in the next kernel updates. https://launchpad.net/bugs/1630238 for more information. I filed the bug in October when it regressed after having worked for some time.

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Feb 8, 2017

Member

@tjyrinki Thanks for the links, I will test the CYAN patch. @mildred has posted on this thread a few months ago, so I'll update here (on ticket #317), and on bugzilla.kernel.org with any news.

I haven't been able to find the patch which fixes the second issue. And I'm curious to see how they avoided the bug in 4.9 which broke keyboard/touchpad/touchscreen all over again. I'd like to merge an upstream patch instead of maintaining our own, if possible.

Member

reynhout commented Feb 8, 2017

@tjyrinki Thanks for the links, I will test the CYAN patch. @mildred has posted on this thread a few months ago, so I'll update here (on ticket #317), and on bugzilla.kernel.org with any news.

I haven't been able to find the patch which fixes the second issue. And I'm curious to see how they avoided the bug in 4.9 which broke keyboard/touchpad/touchscreen all over again. I'd like to merge an upstream patch instead of maintaining our own, if possible.

@hissingshark

This comment has been minimized.

Show comment
Hide comment
@hissingshark

hissingshark Feb 14, 2017

@reynhout
With respect to Google applying a fix to the firmware - closing that window - have they actually been made aware of the issue/hazard? Is it under discussion?

hissingshark commented Feb 14, 2017

@reynhout
With respect to Google applying a fix to the firmware - closing that window - have they actually been made aware of the issue/hazard? Is it under discussion?

@thatguy21212121

This comment has been minimized.

Show comment
Hide comment
@thatguy21212121

thatguy21212121 Feb 18, 2017

hallo nice people,

can someone please tell me which kernel version from " http://kernel.ubuntu.com/~kernel-ppa/mainline/ " I need to pick for the audio to start working? ( EDGAR - model )

thx

thatguy21212121 commented Feb 18, 2017

hallo nice people,

can someone please tell me which kernel version from " http://kernel.ubuntu.com/~kernel-ppa/mainline/ " I need to pick for the audio to start working? ( EDGAR - model )

thx

@reynhout

This comment has been minimized.

Show comment
Hide comment
@reynhout

reynhout Feb 18, 2017

Member

@thatguy2121212 No mainline kernel versions will have working audio for Braswell, and as far as I know no other distro kernels will either. You need to either patch a kernel yourself, or use the GalliumOS kernel until the fixes are released in a mainline version.

This ticket is closed, but has many subscribers. I'm going to lock this thread to prevent future notifications. Further support questions should go to Reddit; issue reports to new GitHub tickets (but check for dupes first). Thank you!

Member

reynhout commented Feb 18, 2017

@thatguy2121212 No mainline kernel versions will have working audio for Braswell, and as far as I know no other distro kernels will either. You need to either patch a kernel yourself, or use the GalliumOS kernel until the fixes are released in a mainline version.

This ticket is closed, but has many subscribers. I'm going to lock this thread to prevent future notifications. Further support questions should go to Reddit; issue reports to new GitHub tickets (but check for dupes first). Thank you!

@GalliumOS GalliumOS locked and limited conversation to collaborators Feb 18, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.