MrChromebox

@LufyCZ it's on our to do list, chill. This isn't our FT job, nor our #1 priority even for GalliumOS. @moookino unfortunately the (much older) ChromeOS kernel and mailline Linux...

On Acer Chromebook 15 (SAND) with chrx / kernel 4.8.17-galliumos, 4.12.0-galliumos (testing repo) - [ ] `galliumos-apollolake` package created - [x] Firmware available (in testing) - [x] Boots from USB...

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

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

this is a known issue with CR50 devices running stock firmware. On resume from S3/suspend, Google's verified boot code is looking to the TPM to confirm the previous boot was...

@elthariel not implying, definitively stating. CR50 devices running my UEFI firmware do not have this issue. the TPM boot status is part of the vb2 security data, IIRC. I've not...

@maccaches the X2's detachable keyboard has broken firmware, identifies as a touchscreen. I'm not sure how to work around that currently

@maccaches only if it's not already in the mainline Linux (or GalliumOS) kernel -- would need to check on that

> These are the only options I could find that weren't enabled, but they didn't have the KBL in them: > > SND_SOC_MT8183_DA7219_MAX98357A > SND_SOC_MT8183_MT6358_TS3A227E_MAX98357A as indicated in the name,...

@empathicqubit no, I'm saying that the MT8183 drivers are completely not applicable. Your Kabylake device has one of the 3 setups I listed, and is likely all 3 drivers are...