About HP Chromebook Plus 15.6 inch model 15anb Board Yaviks cpu Intel Core i3-N305 Alder Lake LPDDR-5 8Gb WiFi-6.
I installed MxLinux-ahs-23.5 xfce version because its light and install every thing. After install updates I immediatelly switch kernel from “liquorix” to “amd64 SMP PREEMPT_DYNAMIC Debian”. The reason is because liquorix gobernor focus on performance and make laptop cpu extremely “hyper” and “hot” about 95 C; instead debian kernel allow you to choose for cpu powersafe gobernor; my machine actually runs fanless set cpu at 8 x 800 MHz and GPU 200-750 MHz at temperature min 43 C and max 55 C on multitask; while on not heavy costume tasks on continue use battery can live up to 14 hours.
The only issue with debian kernel is about USB Type-C port, they are only available if the device is plugged-in from booting time but ports will NOT work if the device is plug-in after boot; it means on linux already running to make usable USB Type-C ports you have to plug-in the device and reboot; I did my best to figure out why it happens but still no solution found.
GOOD NEWS For all of yours getting trouble installing linux on HP Chromebook Plus 15" Yaviks with cpu Intel Core i3-N305 Alder Lake. I am really happy after I fully 100 % succeed and you can do it also; Easy.
The best Linux distro for that Chr-Laptop in particular is Loc-OS ASH for new machines Live version so far, it is a light weight distro, highly optimized, boots at once, install every thing, and USB-TYPE-C ports works perfect, sensor temperature report very good…
After Loc-OS Linux installed you can connect back the battery. I advice to install “TLP” and go to /etc/tlp.conf file to edit it for max powersave efficiency, just use your common sense but if someone need help and is instresting on details how I did let me know.
Before I was using MxLinux but Liquorix Kernel cause extreme cpu heat and otherwise if you switch to PREEMT-DYNAMIC kernel it is unable to access to USB-TYPE-C after boot time; so I try with Loc-OS a V-init kernel distro that proved is costumized for this coreboot BIOS, my modest opinion is that looks like current systemd kernels can NOT control this coreBIOS yet or are in conflict with.