Just briefly relating my installation of fatdog on Acer 714 Chromebook.
This Acer 714 i3 is all aluminium, slim, long battery life, touchscreen, backlit keyboard, lightweight laptop, with fullhd screen.
Firstly I installed the firmware from Mrchromebox while runnig chromeos which is installed on the mmcblk internal device. Basically you put the device into developer mode, following mrchromebox guides. Then using the main underlying terminal, not the emulated one, you download a script which installs the firmware updater through a menu. After rebooting you can select a boot device. There are two options for firmware, one is the full efi firmware which replaces chromeos and requires unlocking hardwre protection. Or using the cutdown firmware which is kind of temporary but allows dual booting with chromeos. Which is what I have, and it's fine.
I dual boot with linux using syslinux installed via cli to the first partition which is fat32 of a usb-c ssd. I now know that syslinux can be installed to linux partitions also, which i will try at some point. I like the simple syslinux.conf way of organising boot options, in my case I have three different custom kernels for fatdog, plus fossadog and fossapup distros frugally installed on the ssd.
The kernel I am presently using is 5.2.21-rt which I compiled in sukk on the chromebook in fatdog. I also have available 5.13.3 and 5.16.2.
So in the beginning I didn't have sound working. hdmi was available but I never tried it. I had to update UCM, and blacklist snd_hda_intel to get the internal audio working. To date I only have the internal speakers working, not the headphone socket or mic. But that maybe a matter of getting the settings right on the kblda7219max intel skylake soundcard.
The webcam works perfectly and is great. Backlit keyboard worked with sending level directly to /sys/leds/* with a yad script. Screen backlight is the same. Volume also. Wifi worked from the get go. Booting from usb-c and usb 3 is fine. I can run a portable fullhd display from one of the two usb-c sockets, but I have not yet heard sound when selecting hdmi 1, 2 or 3 through the speakers of the ext. display.
Last night I had another go at touchscreen. After boot running dmesg i see elan_i2c touchpad, and raydium_i2c devices. The raydium is the touchscreen which works on chromeos of course but didn't on linux. It seem to not get power during boot. After lots of research and trial and error, including recompiling kernels and stealing firmware from chromeos, searching endless forums and trying out various solutions, I finally got it working, and all I needed to do was blacklist elants_i2c, which was my own solution after thinking there are too many possible modules loaded for one device. Running google-chrome browser, which handles touch directly I have pinch to zoom and right click menu. In openbox I cannot force the wacom driver to be adopted so there is no two finger right click, but two finger operation is there as I can keep one finger controlling cursor, and also touch the menu which opens without cursor moving. So maybe another windowmanager will be ok. Otherwise I will try to implement Tazoc's long press for right-click from Lighthouse64.
There is a problem with suspend when closing the lid it simply reboots. But I will figure that out eventually.
So, I highly recommend this budget friendly premium feel Acer 714. Long battery life, stable wifi and bluetooth, excellent camera, thin side bezels, and superb backlit keyboard, incredbile glass multi-touchpad with three buttons.
stemsee