hexdump0815
Working on Jacuzzi (HP Chromebook 11MK G9 EE) using Kukui images for Jammy
I can confirm that jammy works on jacuzzi on both usb and internal storage with all drivers working, with the only issues being related to X11, along with a weird audio bug where a loud high pitch noise starts to play and doesn't stop until the chromebook is shut down. Wayland works great and has no issues whatsoever.
thanks for the success report, i have added it to the readme: https://github.com/hexdump0815/imagebuilder/commit/b8ebe14763708416a97b20654cc8cb8cd5738024 - the high pitch noise is a known problem, see: https://github.com/hexdump0815/imagebuilder/issues/65 - suspend/resume might also help to get rid of it and i did not hear it again yet with a v6.6 kernel (see info in the github issue)
thanks for the success report, i have added it to the readme: b8ebe14 - the high pitch noise is a known problem, see: #65 - suspend/resume might also help to get rid of it and i did not hear it again yet with a v6.6 kernel (see info in the github issue)
I'd just like to quickly note that this Chromebook isn't burnet and is actually esche, and it's named HP Chromebook 11MK G9 EE, not x360 11MK G9 EE. Although maybe you could change it to say HP Chromebook x360 11MK G3 EE/11MK G9 EE (burnet/esche) because the hardware is pretty much the exact same.
@EnterTheVoid-x86 - which dtb is it using? the output of "cat /proc/device-tree/model" would be interesting ... so far there is no dts for esche, so i guess that it really is burnet in the end then maybe? does it say esche at the dev mode bootscreen too?
@EnterTheVoid-x86 - which dtb is it using? the output of "cat /proc/device-tree/model" would be interesting ... so far there is no dts for esche, so i guess that it really is burnet in the end then maybe? does it say esche at the dev mode bootscreen too?
Yes, it does say esche at the devmode screen. However, ChromeOS firmware says Google-Burnet, and neofetch/proc/device-tree/model say "Google burnet board".
thanks for checking and the update - i have fixed it in the readme now: https://github.com/hexdump0815/imagebuilder/commit/365159765669408c529a7396190157d21a77454c