Hello all,
Rather than becoming e-waste, I am working on turning a kind of large collection of Chromebooks into a cluster computer. I was wondering if the fullROM option allowed for PXE booting, that way I could use MaaS to help image and deploy the nodes in the cluster. Thanks!
no, but it can be enabled when compiling. But only supports LAN NICs, not WLAN IIRC
Perfect, I’ll read up on the process unless you have some documentation available, I looked but was unable to find anything relating to it. Each once will be bridged over a USB NIC as the chromebooks don’t have ethernet. Provisioning over MaaS I estimate will have a lot of time as compared to imaging each one individually after flashing them.
I think I found the support under coreboot in payloads/edk2 on the repo. Just to confirm, when performing the UEFI Fullrom procedure, I would not have the ability to enable this, but rather I would need to change the value in coreboot before compiling the firmware.
correct, PXE booting is not enabled in the firmware available via the firmware utility script.
you will need to add CONFIG_EDK2_NETWORK_PXE_SUPPORT=y to your board’s config file and rebuild. That will add PXE support for Realtek and ASIX USB NICs.
So using a USB-C to ethernet adapter will work, but not integrated Wi-Fi or a USB Wi-Fi adapter?
I don’t know how you got that from my posts. I said integrated WiFi modules will not work, and that some specific USB NICs should work.
How do you find out which ones should work?
I added this (on Jinlon) and also the HTTP option and nothing changed in the firmware settings screen. Is a PXE option supposed to show up?
haven’t tested it in several versions/rebases. it should if there is a compatible NIC
I didn’t have any USB to ethernet adapter plugged in. Does it only show up if one is plugged in? Does it only show up if it’s plugged in and the ethernet cable is also connected?
it’s not going to add a boot entry for a device that isn’t present. cable connection doesn’t affect device detection
