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

Apollo Lake Platform Validation #364

Open
8 of 18 tasks
reynhout opened this issue May 30, 2017 · 252 comments
Open
8 of 18 tasks

Apollo Lake Platform Validation #364

reynhout opened this issue May 30, 2017 · 252 comments

Comments

@reynhout
Copy link
Member

reynhout commented May 30, 2017

Tracking validation tests and bug reports for GalliumOS support on Apollo Lake models.

Please add observations for any Apollo Lake model in comments!

Current Apollo Lake status

  • galliumos-apollolake package created
  • Firmware available
  • Boots from USB ISO
  • Boots from internal storage (eMMC)
  • Internal keyboard
  • Touchpad
  • Touchscreen (if equipped)
  • Internal audio
    • speakers/headphone jack
    • microphone
    • jack detection
  • WiFi
  • Bluetooth
  • Media keys
    • Volume control
    • LCD backlight control
    • Keyboard backlight control (if equipped)
  • Suspend/resume

Apollo Lake is the successor to Braswell, so that is likely to be the best starting point for testing.

@MrChromebox
Copy link

MrChromebox commented Dec 1, 2017

On Acer Chromebook 15 (SAND) with chrx / kernel 4.8.17-galliumos, 4.12.0-galliumos (testing repo)

  • galliumos-apollolake package created
  • Firmware available (in testing)
  • Boots from USB ISO
  • Boots from internal storage (eMMC)
  • Internal keyboard
  • Touchpad
  • Touchscreen (needs Radium driver - works on Ubuntu 17.10 live USB)
  • Internal audio (needs driver)
    • speakers/headphone jack
    • microphone
    • jack detection
  • WiFi
  • Bluetooth
  • Media keys
    • Volume control
    • LCD backlight control
    • Keyboard backlight control (if equipped)
  • Suspend/resume (boots to ChromeOS recovery)

@perphilip
Copy link

perphilip commented Dec 16, 2017

I have one of these as well, am currently trying to get Write Protect disabled so I have unscrewed the indicated one but still no go, any hints?

Have run the RW_LEGACY flash from MrChromebox and will hopefully try to boot Live GalliumOS tomorrow.

@Mz0rZ
Copy link

Mz0rZ commented Dec 25, 2017

@perphilip Hi there i have just purchased one of these as well.

Model Specific (CB515-1HT-C1W7)

Could you tell me where this particular screw is located on this device>?

Thanks in advance merry x-mas & best regards from the Netherlands.

@MrChromebox
Copy link

The firmware hardware write protect on ApolloLake devices is controlled by the battery sense pin, so to disable WP, simply boot the device without the battery connected (obv. AC power is required). Note that it may take a few extra seconds to power on/boot in this config.

@Mz0rZ
Copy link

Mz0rZ commented Dec 25, 2017

@mattdevo Thank you very much for this useful reply, i'm really grateful for the information.

This is the first ever Chromebook i have purchased so i´m kind of new to this system, so after doing some basic research i can conclude that for now on the (Apollolake) i can only boot Linux via Crouton or using the LegacyUSB method, i have updated the firmware to allow LegacyUSB support and i booted various Distro´s with many problems facing, however after i booted Gallium (Braswell optimized image) from the USB-Drive, it worked pretty well, however the only problem i faced is that i cannot get any sound output to work... Would be absolutely awesome if i could get the sound to output.

@mattdevo Firmware available (in testing)

Does this mean that a full fw is in testing?

Keep up the great work!

Thank you god bless you and Happy holidays!

@YaKillaCJ
Copy link

Signed up to say thanks in advance.

I'm new to github and not familiar with writing code but would like to contribute somehow. Best I can think of is being a guinea pig and beta test. I kno my way around linux at least from the user perspective. Or if theirs any other way I can contribute, let me know.

@perphilip
Copy link

perphilip commented Jan 3, 2018

Took a bit of a break for the holidays but here are my findings so far.

On Acer Chromebook 15 (2017) (SAND) (CB515-1HT-P39B) with updated RW_LEGACY support from MrChromebox / using the GalliumOS install for SkyLake and kernel 4.12.0-galliumos from the testing repo:

  • Boots from USB ISO
  • Boots from internal storage (eMMC)
  • Internal keyboard
  • Touchpad
  • Touchscreen
  • Internal audio (only HDMI show up)
    • speakers/headphone jack
    • microphone
    • jack detection
  • WiFi
  • Bluetooth
  • Media keys
    • Volume control
    • LCD backlight control
    • Keyboard backlight control (Not Available On This Keyboard?)
  • Suspend/resume (Reboots to ChromeOS Recovery mode and sometimes clears the DeveloperMode-flags.)

If I run Ubuntu 17.10 (Budgie) or 18.04LTS I get:

  • Boots from USB ISO
  • Boots from internal storage (eMMC) (Not Tested Yet)
  • Internal keyboard
  • Touchpad
  • Touchscreen
  • Internal audio (only HDMI show up)
    • speakers/headphone jack
    • microphone
    • jack detection
  • WiFi
  • Bluetooth
  • Media keys (Normal Fn-functions instead)
    • Volume control
    • LCD backlight control
    • Keyboard backlight control (Not Available On This Keyboard?)
  • Suspend/resume (Reboots to ChromeOS Recovery mode and sometimes clears the DeveloperMode-flags.)

It turns out there is no screw, as stated above, I have however not had any luck in getting my CB too boot with the battery unplugged, it starts up and blinks a couple of times but nothing happens.

To get past the issue of the missing DeveloperMode-flags I created a bootable usb-drive using
this guide.

Is there anything else I can try that would be helpful?

@davidthewatson
Copy link

@perphilip When you booted without the battery connected and it blinks a couple of times did you try pressing Ctrl-D? It wasn't clear to me if you were getting to developer mode or not.

@perphilip
Copy link

@davidthewatson I can´t remember clearly. I am fairly sure I did but will have to try again to verify. As far as I can remember the whole machine was completely unresponsive and then shut down.

Does anyone have any idea what is needed to enable sound on this one, is it "just" a missing driver?

@kitambi
Copy link

kitambi commented Feb 27, 2018

I'm pretty sure that the missing driver is the SSP clock driver, which appears to be hitting the mainline kernel in 4.16. I've attempted to build 4.16-rc3 after applying the patches from the 4.14.14 galliumos directory (with some modifications to fix the build) and using the 4.14.14 config, but end up with a black screen when trying to boot it. The module is snd_skl_ssp_clk which you can see if you run "lsmod" in ChromeOS, but which is missing from GalliumOS. I do know that the clock driver is required for sound to work on my (REEF) hardware.

@IceAmaura
Copy link

IceAmaura commented Mar 6, 2018

Running Lubuntu with mainline 4.16 kernel via chrx does allow for more functionality beyond the normal kernel for 17.10 such as touchpad, some function keys, and touchscreen but sound is still not showing up in PulseAudio. This is on the Acer Chromebook 15 SAND

@ghost
Copy link

ghost commented Mar 12, 2018

Is there any way to get the sound working?

@IceAmaura
Copy link

@beli3ver I've been using a pair of Bluetooth headphones as Bluetooth is functional on Apollo Lake. You could probably also see if a USB adapter would work.

@ghost
Copy link

ghost commented Mar 12, 2018

Do you use GalliumOS or did you use a other distro with the bluetooth headphones.

@IceAmaura
Copy link

@beli3ver I use GalliumOS with testing and prerelease enabled. Bluetooth drivers for PulseAudio are already installed. If you use Ubuntu or variants you need to install an add-on for PulseAudio to allow it to use Bluetooth.

@reynhout
Copy link
Member Author

@beli3ver USB and Bluetooth audio are the workarounds for now on Apollo Lake. Both should work without any problems.

@IceAmaura We will have 4.15 kernel packages very soon. 4.16 is currently at rc5, and will be released in a few more weeks. I haven't tried porting the GalliumOS patches to the 4.16 RC's, but if there aren't any major problems, we can have packages shortly thereafter.

@ghost
Copy link

ghost commented Mar 12, 2018

Which Version fom GOS is the best for SAND?

@reynhout
Copy link
Member Author

reynhout commented Mar 12, 2018

@beli3ver It probably doesn't matter much but I would use the Braswell or Skylake ISO (or chrx, if dual-booting). There's a nightly Braswell ISO in https://galliumos.org/releases/nightly that has a more recent kernel (and enables the testing pkg repo), so I would use that. You can manually enable the testing repo and update from any 2.1 ISO though.

You definitely want the newest kernel (4.14 presently) which requires the testing repo, for now.

@ghost
Copy link

ghost commented Mar 12, 2018

Thanks for that

@K1ish
Copy link

K1ish commented May 22, 2018

Is it possible to get audio working? what exactly is causing an audio issue. It shows up in lspci and lsusb.

@ghost
Copy link

ghost commented May 23, 2018

That would be amazing

@K1ish
Copy link

K1ish commented Jun 17, 2018

Could I just literally copy the drivers from chromeos into galliumos?

@IceAmaura
Copy link

4.18 has merged some fixes for broxton sound. I'll give it a shot and see if it has fixed anything

@ghost
Copy link

ghost commented Aug 14, 2018

@IceAmaura any news?

@IceAmaura
Copy link

No dice with 4.18. 4.19 also has a Broxton related fix, but it only shrinks the name of the module to conform to standards... I'm wondering if this has to do more with it being exposed from SeaBIOS/UEFI? Also, the diff between the Chrome OS and Upstream broxton board sound module has some pretty big differences but I can't get the module to compile with the newest kernel (probably due to it being built on 4.4). Might try just pulling 4.4 from google's repo with the sound module in it and see if it works...

@MrChromebox
Copy link

I'm wondering if this has to do more with it being exposed from SeaBIOS/UEFI?

exposed from? The firmware payload booting the OS doesn't expose or not expose the audio hardware. This is simply an issue of the drivers from Google's chromium kernel tree being upstreamed to the mainline kernel, and getting them to work on actual hardware

@K1ish
Copy link

K1ish commented Aug 18, 2018 via email

@IceAmaura
Copy link

exposed from? The firmware payload booting the OS doesn't expose or not expose the audio hardware.

Sorry about that, I had the wrong idea of how that worked. :S great work btw on the legacy bios to make all this work in the first place

What is chromeos using for SAND sound drivers?

It's using an i2c module I linked above. The upstream module and the chromeos module are different. I am not an experienced kernel developer (wish I was, would make a lot of things easier) so I can't rewrite the module merging the differences while retaining compatibility for the new kernel unfortunately. Kind of just hoping the upstream developers figure it out or whatnot...I've spent my fair share of time troubleshooting the issue and it just seems like something is missing upstream that chromeos has fixed.

@Tykymba
Copy link

Tykymba commented Feb 24, 2022

@skiwarz HP Chromebook 11 g6 EE, Endeavour Arch based distro

https://pastebin.com/5RkXgCRY

@RodBarnes
Copy link

RodBarnes commented Feb 24, 2022

@skiwarz Since my output was different than @Tykymba , this is from Acer CB515-1HT w GalliumOS:
aplay -l
aplay -L
arecord -l
arecord -L

@Meganium97
Copy link

Meganium97 commented Mar 4, 2022

Either lenovo 100e is unsupported, or debian is unsupported. I can check this easily but debian doesnt have a linux-firmware package, instead having a firmware-linux package. Not sure if that affects it but I'm gonna try installing another OS.
Edit: Probably because I'm using a newer method that emlommers is suggesting I take. I will try the pervious method that works.

@MrChromebox
Copy link

MrChromebox commented Mar 5, 2022

Apollolake on Manjaro 21.x with UEFI test firmware

  • Firmware available (available soon)
  • Boots from USB ISO
  • Boots from internal storage (eMMC)
  • Internal keyboard
  • Touchpad
  • Touchscreen (Elan at least)
  • Internal audio (requires 5.15+ kernel, updated SOF topology, driver param. volume scaling needs work)
    • internal speakers
    • headphone jack
    • microphone
    • jack detection
  • WiFi
  • Bluetooth
  • Media keys (works OOTB on any 5.10+ kernel)
    • Volume control
    • LCD backlight control
    • Keyboard backlight control (if equipped)
  • Suspend/resume

look for UEFI Full ROM firmware available for (almost) all APL and GLK devices in the coming weeks. No additional testers needed at this time.

@epitaxial1
Copy link

Any details on the settings for getting audio to work?

@MrChromebox
Copy link

Any details on the settings for getting audio to work?

audio on APL works under mainline Linux with my UEFI firmware, a 5.15 kernel and the fix on my FAQ. Fix isn't needed on 5.18+ I believe.

@Tykymba
Copy link

Tykymba commented Jun 8, 2022

My audio start working and stopped after updates. Dont know why. Fresh install - no effect after FAQ fix.
Arch based distro

@walterav1984
Copy link

@MrChromebox is HDMI audio output also functioning besides video output?

@MrChromebox
Copy link

@MrChromebox is HDMI audio output also functioning besides video output?

I've not tested it TBH, the chrultrabook subreddit or Discord server would be a good place to ask

@AaronJH
Copy link

AaronJH commented Jun 14, 2022

My audio start working and stopped after updates. Dont know why. Fresh install - no effect after FAQ fix. Arch based distro

I've also noticed that audio fails to work with any Arch kernel packages in the 5.18 series (on an ASUS C213N running vanilla Arch). Downgrading to 5.17.9 fixes it, as does booting with linux-lts instead, which uses 5.15.46.

As soon as I get a few spare hours, I'll dig into it in more detail to see if I can identify precisely what is going on.

@MrChromebox
Copy link

@Tykymba @AaronJH plenty of info on Arch forums that 5.18 has audio bugs on APL/GLK and should be avoided

@Mollie2000
Copy link

Mollie2000 commented Sep 1, 2022

Looks like Linux 5.19 could solve the audio issues: https://www.phoronix.com/news/Linux-5.19-Sound

@lilkidsuave
Copy link

5.19 is already out, it just isnt shipped by default on distros yet

@1000001101000
Copy link

I’m guessing it’s not that easy, but I’m going to try building the current 5.19 from kernel.org and see what happens

@1000001101000
Copy link

it recognized my audio devices, though now that I think of it so did the old driver. For my Debian install at least I think it's a lack of alsa/etc config rather than kernel drivers/firmware.

To be honest I never really understood all of that.

root@chrome:~# uname -a
Linux chrome 5.19.6 #1 SMP PREEMPT_DYNAMIC Thu Sep 1 19:08:03 CDT 2022 x86_64 GNU/Linux
root@chrome:~# dmesg | grep -i snd
[    4.081868] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    4.081880] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SST driver
[    4.555671] snd_soc_skl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    4.555683] snd_soc_skl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SST driver
[    4.692532] snd_soc_skl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

@TLMcNulty
Copy link

TLMcNulty commented Sep 29, 2022

I bricked one of my DUTs so I decided to wipe and test 5.19.

DUT:

Acer CB515-H (Sand)

Conclusions:

With the stock kernel no devices showed up.

I altered configs according to @whyiscassieongithub EMLommers/Apollolake_Audio changes, and after reboot a bunch of devices on the Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster PCI device are now listed, however I can't get audio out of the system speakers

Pavucontrol is also displaying the device.
image

I had to mess with it to get bluetooth to start working again, and unless the N3350/N4200/E3900 profile is set to to Off, bluetooth is basically unusable, it's chopping or not reassembling slices correctly. It's jumbled audio but the stuff that is reassembled is reassembled at the higher A2DP bitrate. Attempting HSP is even worse, lower quality as you'd expect but I'm not even hearing slices of the test media.

I've also got some messages about screen locks failing to run and the the system seems to wake up while the lid is closed. If I set it to suspend and close the lid and walk away, I'll come back to it and open it up and it hasn't locked and chewed through 70% of the battery. I was messing with the audio but I'll probably switch to suspend now.

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu Kinetic Kudu (development branch)
Release:	22.10
Codename:	kinetic

$ uname -ar
Linux germsand 5.19.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 2 07:35:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofbxtda7219max [sof-bxtda7219max], device 0: Speakers (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofbxtda7219max [sof-bxtda7219max], device 1: Headset (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofbxtda7219max [sof-bxtda7219max], device 5: HDMI1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofbxtda7219max [sof-bxtda7219max], device 6: HDMI2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofbxtda7219max [sof-bxtda7219max], device 7: HDMI3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Some of dmesg:

[    7.477499] sof-audio-pci-intel-apl 0000:00:0e.0: DSP detected with PCI class/subclass/prog-if 0x040100
[    8.002172] sof-audio-pci-intel-apl 0000:00:0e.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    8.008645] sof-audio-pci-intel-apl 0000:00:0e.0: use msi interrupt mode
[    8.041760] sof-audio-pci-intel-apl 0000:00:0e.0: NHLT_DEVICE_I2S detected, ssp_mask 0x22
[    8.041772] sof-audio-pci-intel-apl 0000:00:0e.0: hda codecs found, mask 4
[    8.045182] sof-audio-pci-intel-apl 0000:00:0e.0: Firmware info: version 2:1:1-3964a
[    8.045232] sof-audio-pci-intel-apl 0000:00:0e.0: Firmware: ABI 3:21:0 Kernel ABI 3:21:0
[    8.045255] sof-audio-pci-intel-apl 0000:00:0e.0: unknown sof_ext_man header type 3 size 0x30
[    8.098873] sof-audio-pci-intel-apl 0000:00:0e.0: Firmware info: version 2:1:1-3964a
[    8.098884] sof-audio-pci-intel-apl 0000:00:0e.0: Firmware: ABI 3:21:0 Kernel ABI 3:21:0
[    8.115372] sof-audio-pci-intel-apl 0000:00:0e.0: Topology: ABI 3:20:0 Kernel ABI 3:21:0
[    8.115736] bxt_da7219_max98357a bxt_da7219_mx98357a: ASoC: Parent card not yet available, widget card binding deferred
[    8.123831] da7219 i2c-DLGS7219:00: supply VDD not found, using dummy regulator
[    8.123941] da7219 i2c-DLGS7219:00: supply VDDMIC not found, using dummy regulator
[    8.123958] da7219 i2c-DLGS7219:00: supply VDDIO not found, using dummy regulator
[    8.123978] da7219 i2c-DLGS7219:00: Invalid VDDIO voltage
[    8.150973] bxt_da7219_max98357a bxt_da7219_mx98357a: ASoC: sink widget DMic overwritten
[    8.151034] bxt_da7219_max98357a bxt_da7219_mx98357a: ASoC: source widget Capture overwritten
[    8.163275] input: sof-bxtda7219max Headset Jack as /devices/pci0000:00/0000:00:0e.0/bxt_da7219_mx98357a/sound/card0/input8
[    8.163402] input: sof-bxtda7219max HDMI/DP,pcm=5 as /devices/pci0000:00/0000:00:0e.0/bxt_da7219_mx98357a/sound/card0/input9
[    8.163574] input: sof-bxtda7219max HDMI/DP,pcm=6 as /devices/pci0000:00/0000:00:0e.0/bxt_da7219_mx98357a/sound/card0/input10
[    8.163659] input: sof-bxtda7219max HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:0e.0/bxt_da7219_mx98357a/sound/card0/input11

@walterav1984
Copy link

walterav1984 commented Oct 1, 2022

Did you boot from "rw_legacy" firmware or did you do a full flash of UEFI replacement firmware from see latest question in FAQ on mrchromebox.tech?

Does your linux distro come with SOF installed and is it correctly setup and running?
https://www.reddit.com/r/chrultrabook/comments/uc0b6i/howto_audio_on_apollolake_devices_under_linux/

@TLMcNulty
Copy link

TLMcNulty commented Oct 7, 2022

Did you boot from "rw_legacy" firmware or did you do a full flash of UEFI replacement firmware from see latest question in FAQ on mrchromebox.tech?

Nailed it. I have a few of these machines, some rw_legacy and some UEFI. Finally got around to flashing the full UEFI on this one and everything fell into place like it was made to. Listening to music at the moment out of sheer novelty. I basically never use the onboard speakers but it's still cool to have.

  • Boots from internal storage (eMMC)
  • Internal keyboard
  • Touchpad
  • Touchscreen (if equipped)
  • Internal audio
    • speakers
    • headphone jack
    • microphone
    • jack detection
  • WiFi
  • Bluetooth
  • Media keys
    • Volume control
    • LCD backlight control
    • Keyboard backlight control (if equipped)
  • Suspend/resume

Messed only with a few of the UI settings for headphones, didn't find anything immediately apparent. Either way no jack detection or headphone output on this device at the moment.

I have volume keys that work but no media keys to test. Software control of LCD backlight operational. Function key backlight control inoperable.

Suspend/resume left blank because I'll need to test it for a bit to be sure.

@walterav1984
Copy link

walterav1984 commented Oct 10, 2022

Good to hear its working for you @TLMcNulty

Did you still have to do the apollolake reddit SOF patches or other patches on top of ubuntu 22.10 for laptop speakers or did it work out of the box after the machine was fully UEFI flashed running the default 5.19 kernel?

As you described that headphone jack detection isn't working yet(expected), is the laptop speaker volume slider only working between 0-10% issue also still in place (labeled as headphone...)?

Do you happen to have a USB-C -> HDMI dongle to check if audio out works?

Still little hesitant to flash this Acer 515HT to full UEFI, since the late linux 5.19 update might cause display damage and also red something about AVS vs SOF might also cause damage on some devices with linux 6.x.

@kovan
Copy link

kovan commented Oct 31, 2022

I am interested in this also.
Does audio work with mrchromebox full UEFI flash + a distro with kernel 5.19, or not?

@AaronJH
Copy link

AaronJH commented Oct 31, 2022

Audio was problematic for me under 5.18 and 5.19 with SOF. It worked fine under 5.17 and 5.15.

However, it's better than ever with the new AVS audio subsystem, including (finally) headphone support. Using the firmware files from the chrultrabook Discord channel, audio is now at a point where it's essentially fully-working for my needs. Although, given there are occasional reports of blown speakers at high volumes when using AVS, I've volume-limited mine to 50% to be safe.

@lilkidsuave
Copy link

How do you install the avs subsystem?

@AaronJH
Copy link

AaronJH commented Oct 31, 2022

How do you install the avs subsystem?

It's included in recent kernels. Whether it is compiled-in to the latest mainline kernels is up to your distro. You'll see the "snd_soc_avs", "snd_soc_avs_max98357a" and "snd_soc_avs_da7219" modules if you have it.

I've been testing with the latest 6.x kernel packages from Arch, and it's been working fine for me.

Once you have a recent kernel with AVS, it's just a matter of setting modprobe to use "option snd_intel_dspcfg dsp_driver=4" (to enable AVS=4 instead of SOF=3), and installing the APL audio firmware using the avs.zip file from the chrultrabook Discord server: https://discord.gg/tkPTk5w.

You'll then see a whole lot of new audio devices present... including, finally, a line-out/headphone one. Just be careful with higher volumes when using the speakers for now.

@perphilip
Copy link

perphilip commented Nov 2, 2022 via email

@YDJSIR-NJU
Copy link

I made it work by following the instructions of the Discord Channel. What I am using is Ubuntu 22.10 with mainline kernel 6.0.7 installed in Acer Chromebook Spin 11 (R751T) , which is equipped with an Intel N3350 Soc, 4GB DDR4-1866 RAM and 32G eMMC storage. The version of my BIOS is 20221027. And these below is what I do:

  1. Install the system as usual.
  2. Use mainline to update the kernel to 6.0.7, then reboot.
  3. Follow the instruction of the Discord Channel (On the top of message history).
  4. Modify /etc/modprobe.d/inteldsp.conf as follows, then restart.
options snd-intel-dspcfg dsp_driver=4

Finally, here we go. HDMI & DP output from USB-C works fine with sound, headset jack with detection work pretty fine too. Howerver, speakers volume limit is about 50%, and for my machine, they can only make sound correctly like buzzing otherwise they simply make noises, which doesn't bother me at all as I don't need them anymore. Sadly, on these circumstances, the screen cannot turn over when the device is bent like a tent.
I sincerely appreciate the contribution of @AaronJH and other people working for this community.

@AaronJH
Copy link

AaronJH commented Nov 5, 2022

Just one question, how do you setup a volume limit

This is very much desktop-dependent. I use XFCE4 and PulseAudio, so the process for me was:

  • Install xfce4-settings-editor if it's not already installed.
  • Open xfce4-settings-editor
  • Navigate to the xfce4-panel channel
  • Go to the pulseaudio plugin entry (under "plugins).
    • It will have a number like "plugin-24" - it can be identified by it having a value of "pulseaudio".
  • Set the "volume-max" property to 50.
  • If the volume-max property doesn't exist, you can create a new Integer property by clicking "Add" and entering "/plugins/plugin-XX/volume-max", where XX is the value of your pulseaudio plugin as seen above. Set the value to 50.
  • You can also set the "volume-step" property (also an Integer value). I set it to "1" so I have fine control with my media keys.

Logout and login, or restart your panel, and test it with the volume up/down keys.

This then stops me from setting the volume above 50% with my media keys, and makes the extreme-right end of the volume slider correspond to 50%.

All thanks for Linux audio working on Chromebooks goes to the hard-working Chrultrabook devs, and, of course, MrChromebox.

@Meganium97
Copy link

I wonder if this means all problems are done? Personally with the old fix I couldn't get the mic working but with the google chrome book layout everything else worked - if we can confirm this is 100% functional this might just be the end of out problems here.

@walterav1984
Copy link

walterav1984 commented Dec 31, 2022

CB515-1HT "sand"

Flashed succesfully to full UEFI Coreboot 4.18.2 using the guest mode on ChromeOS. Just had to use CTRL+ALT+F1 or F2(vs CTRL+ALT+T) for a shell with elevated rights to run MRchromebox tech script and disconnect the battery. Tip for opening the case, start at the side facing your body not the screen when removing the bottom cover.

Running ubuntu mate 22.10 with 5.19 kernel only needs the apollolake FAQ audio reddit link with still the following downsides:
*Internal stereo speakers works (detected as headphone with volume slider max ~5/10%)
*headphone 3.5mm jack not detected nor working
*USB-C displayport/hdmi audio outputs aren't detected nor have audio output(display works)
*Keyboard layout US with Keyboard model "Chromebook" only misses "Screen brightness down" quick key other functions like Audio volume up/down/mute or Screen brightness up are working fine!

*connecting the USB-C power cable while screen is closed and system turned off AUTO turns on and boots the system while you may think its only charging...

upsides:
*battery life is still incredible
*screen brightness can be adjusted much more accurate and darker
*touchscreen only needs "Enable natural scrolling" setting in mouse/touchpad and Firefox browser tweaks see 3.3 all 10 fingers detected.
*the same 1CM edge touchpad deadzone as ChromeOS

Warning!
Before enabling audio, make sure that both in your Desktop Environment and at the Login Window screen the volume slider is set to ~5% and systems sounds are disabled.

@TLMcNulty
Copy link

TLMcNulty commented Mar 8, 2023

Long time between replies but I digress. I'm on 6.2.0 now BTW.

Did you still have to do the [apollolake reddit SOF patches]

Yes. Devices were non-existent as described previously until patched. Having the pro audio profile selected still displays like 9 of them but they work, so whatever.

As you described that headphone jack detection isn't working yet(expected), is the laptop speaker volume slider only working between 0-10% issue also still in place (labeled as headphone...)?

Jack detection still non-functional.

Do you happen to have a USB-C -> HDMI dongle to check if audio out works?

I have a USB-C -> HDMI dongle (which works flawlessly) but unfortunately no way of testing the audio out of it.

Still little hesitant to flash this Acer 515HT to full UEFI, since the late linux 5.19 update might cause display damage and also red something about AVS vs SOF might also cause damage on some devices with linux 6.x.

I read that AVS stuff as well. I'm on the SOF stuff still, yet for some reason the sound out of the speakers is WAY louder. I'm not sure if I'm at risk for blowing them out, so I'm just not using them, but man this thing sounds way better than it ever has. Suspend is working properly, I haven't run tests so I'm not sure which type of sleep it's going into, but it finally has the battery life I'd expect of a system like this. Can't report on display damage but I've switched another of this device over and am really really loving it.

re:

*connecting the USB-C power cable while screen is closed and system turned off AUTO turns on and boots the system while you may think its only charging...

This has tripped me up as well.

I've done A LOT of work to try to get Alt + Screen Brightness Up/Down to do the keyboard brightness and can't get it working. The device is detected and the system is aware of the state, you can echo values into the /sys/class tree and have it take effect, but I haven't gotten an X conf to map Alt + F? to XkdbBrightness.

Regards all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests