Hello,
I have an Acer Chromebook 11 CB3-111 and I’m trying to flash the “Install/Update UEFI (Full ROM) Firmware” using the script available on your website. Everything seems to go smoothly, and I receive a message that the operation was successful. After restarting and waiting for a few minutes, the screen lights up, but nothing is displayed. I performed a reset using Refresh + Power, but there was no change.
So, I downloaded the coreboot_edk2-gnawty-mrchromebox_20240615.rom from your website and flashed it to the Winbond W25Q64 chip. The flashing process completed without errors, but after reassembling the Chromebook, it still won’t boot. The screen lights up, but nothing is displayed.
Next, I downloaded shellball.gnawty.bin and flashed it as mentioned above. After that, the computer booted into Chrome OS. I tried flashing the Full ROM again, but the result was the same as before – the screen lights up, but nothing is displayed.
I would like to install Linux on this Chromebook. Is there anything that can be done to fix this issue?
Best regards,
Maciek
GNAWTY uses the edk2 GOP driver currently, but it doesn’t seem to work for 100% of the display panels. Might need to build using the VBIOS for display init instead and see if that works
Thank you for the quick response!
Could you please provide instructions on how to build the ROM using VBIOS? Specifically, I would appreciate guidance on where to download the source code for the build and which options need to be configured during the compilation process.
Best regards,
Maciek
when you get to the make changes step, overwrite the file configs/byt/config.gnawty.uefi with the contents below:
CONFIG_VENDOR_GOOGLE=y
CONFIG_VGA_BIOS=y
CONFIG_PCIEXP_L1_SUB_STATE=y
CONFIG_IFD_BIN_PATH="3rdparty/blobs/soc/intel/byt/book/flashdescriptor.bin"
CONFIG_ME_BIN_PATH="3rdparty/blobs/soc/intel/byt/me.bin"
CONFIG_BOARD_GOOGLE_GNAWTY=y
CONFIG_VGA_BIOS_FILE="3rdparty/blobs/mainboard/google/rambi/gnawty/vgabios.bin"
CONFIG_HAVE_IFD_BIN=y
CONFIG_HAVE_MRC=y
CONFIG_MRC_FILE="3rdparty/blobs/soc/intel/byt/mrc.elf"
CONFIG_CPU_MICROCODE_CBFS_EXTERNAL_BINS=y
CONFIG_CPU_UCODE_BINARIES="3rdparty/blobs/soc/intel/byt/cpu_microcode_blob.bin"
CONFIG_EC_GOOGLE_CHROMEEC_FIRMWARE_EXTERNAL=y
CONFIG_EC_GOOGLE_CHROMEEC_FIRMWARE_FILE="3rdparty/blobs/mainboard/google/rambi/gnawty/ec.RW.flat"
CONFIG_HAVE_ME_BIN=y
CONFIG_DO_NOT_TOUCH_DESCRIPTOR_REGION=y
CONFIG_FRAMEBUFFER_SET_VESA_MODE=y
save/close the file, then run:
./build-uefi.sh gnawty
and flash the resulting ROM
Thanks again for the response. The ROM coreboot_edk2-gnawty-mrchromebox_20240812.rom is ready. I will flash it tomorrow. Best regards.
1 Like
Hi. I flashed coreboot_edk2-gnawty-mrchromebox_20240812.rom built according to the instructions and it works. Thank you for your invaluable help. Regards Maciek
great, I will make that change for the next release
1 Like
HI
During the startup of EndeavourOS, I receive the following message:
I’d be more concerned with the preceding kernel panic
that’s all dmesg Untitled - Pastebin.com, after adding nofb, the system starts, previously the startup stopped with an error message
looks like Linux is incorrectly trying to create both a coreboot framebuffer and a simple EFI one from the same memory location.
it’s a clean install of endevour os, can I do something with it, can I leave it without any worries,
