Devices having only a Nvidia GPU are not supported.Intel hardware (CPU and GPU) starting from 1st generation "Nehalem" (refer to ),.x86_64 computers with UEFI boot support (BIOS/MBR devices have limited support through a specific procedure detailled in "Limited support for MBR/BIOS devices" section),.As such only Linux supported hardware will work and the same specific kernel command line options recommended for your device should be passed through the Grub bootloader (see "Modify the Grub bootloader" section). Hardware support is highly dependent on the general Linux kernel hardware compatibility. It is therefore highly recommended to only use this framework on a device which does not contain any sensitive data and to keep non-sensitive data synced with a cloud service. By installing Brunch you agree to take those risks and I cannot be held responsible for anything bad that would happen to your device including data loss. Also, ChromeOS recovery images include device firmware updates that a close enough device might potentially accept and get flashed with the wrong firmware. Warning: As Brunch is not the intended way for ChromeOS to work, at some point a ChromeOS script could potentially behave badly with Brunch and delete data unexpectedly (even on non-ChromeOS partitions). To do so, it uses a 1GB ROOTC partition (containing a custom kernel, an initramfs, the swtpm binaries, userspace patches and config files) and a specific EFI partition to boot from it. The purpose of the Brunch framework is to create a generic x86_64 ChromeOS image from an official recovery image. First of all, thanks goes to project Croissant, the swtpm maintainer and the Chromebrew framework for their work which was actively used when creating this project.
0 kommentar(er)
