site/contact.md

@@ -28,7 +28,7 @@ IRC.
 Webchat:
 <https://web.libera.chat/#libreboot>
 
-Libera is one of the largest IRC networks, used for Free Software projects.
+Libera is one of the largest IRC networks, used for Libre Software projects.
 Find more about them here: <https://libera.chat/>
 
 If you wish to connect using your preferred client (such as weechat or irssi),
@@ -55,17 +55,14 @@ Social media
 
 libreboot exists officially on many places.
 
-Twitter and Mastodon
---------------------
+Mastodon
+--------
 
-News announcements: <https://twitter.com/libreboot/>
+The founder and lead developer, Leah Rowe, is on Mastodon:
 
-The founder and lead developer, Leah Rowe, is also on Twitter and Mastodon:
-
-* <https://twitter.com/n4of7> (use nitter to avoid non-free JavaScript)
 * <https://mas.to/@libreleah>
 
-Leah can also be contacted by her email address:
+Leah can also be contacted by this email address:
 [leah@libreboot.org](mailto:leah@libreboot.org)
 
 Reddit

site/contrib.md

@@ -180,7 +180,7 @@ that, the solution was clear:
 
 A project needed to exist, providing a fully free version of coreboot, without
 any binary blobs. At the time (and this is still true today), coreboot was not
-entirely free software and shipped with binary blobs by default. In particular,
+entirely libre software and shipped with binary blobs by default. In particular,
 CPU microcode updates were included by default, on all x86 machines. Working
 with Joshua who reviewed my work, I created a fully free version of coreboot.
 At first, it wasn't called Libreboot, and the work was purely intended for my
@@ -251,7 +251,7 @@ and forth with Lisa around mid 2016, mostly raminit patches, to get the board
 running at the FSF offices. This work ultimately lead to a most wonderful
 achievement:
 
-The <https://www.gnu.org/> and <https://www.fsf.org/> websites now run on
+The FSF and GNU websites now run on
 Librebooted ASUS KGPE-D16 based servers, on a fully free GNU+Linux distro. This
 means that the FSF now has full software freedom for their hosting infrastructure.
 

site/docs/bsd/index.md

@@ -37,6 +37,26 @@ If you don't plan to set up Xorg/Wayland, then that's all you really need to
 do. For example, you might want to run a headless server, in which case you
 probably don't mind running in text mode all the time.
 
+OpenBSD and corebootfb
+----------------------
+
+It's still recommended to use SeaBIOS in text mode, but OpenBSD specifically
+can work with SeaBIOS booting in a coreboot framebuffer, with SeaVGABIOS. In
+Libreboot ROM images, this would be SeaBIOS images with `corebootfb` in the
+file name.
+
+Make sure to select MBR-style partitioning on the installer, and it will
+Just Work.
+
+If you're using the GRUB payload but SeaBIOS is available in the boot menu,
+you can just select SeaBIOS at said menu, and OpenBSD will work fine.
+
+FreeBSD and corebootfb
+----------------------
+
+Assumed broken, so please ensure that you boot with SeaBIOS payload in text
+mode (lbmk ROM images with `txtmode` in the file name, not `corebootfb`).
+
 Warnings for X11 users
 ----------------------
 
@@ -110,6 +130,13 @@ documentation.
 If you're flashing a ROM for a machine where `seabios_withgrub`
 and `seabios_grubfirst` ROMs are available, choose `seabios_withgrub`.
 
+DO NOT USE ROM IMAGES WITH `seabios_grubfirst` IN THE FILE NAME! These were
+present in older Libreboot releases, and supported in previous revisions
+of the build system, but they did not work for the intended purpose. More
+info is written on the [Libreboot installation guide](../install/). ROM
+images with `seabios_grubfirst` in the filename will NOT be included in
+future Libreboot releases.
+
 Dubious mention: Tianocore
 --------------------------
 

site/docs/gnulinux/index.md

@@ -11,13 +11,8 @@ If you're using SeaBIOS, the boot process will work similarly to traditional
 BIOS systems; refer to the SeaBIOS documentation
 on <https://seabios.org/SeaBIOS>
 
-GNU+Linux is the operating system of choice, for libreboot development. It is
-highly recommended over any other operating system, precisely because it consists
-of [Free Software](https://www.gnu.org/philosophy/free-sw.html) (free as in
-freedom). There *are* other free operating systems, such as BSD, but most of
-the software in a typical GNU+Linux system is also *copylefted*. To learn more
-about the importance of copyleft, read this page on the GNU website:
-<https://www.gnu.org/licenses/copyleft.html>
+Linux is generally assumed, especially for Libreboot development, but Libreboot
+also works quite nicely with [BSD systems](../bsd/).
 
 Useful links
 ============

site/docs/grub/index.md

@@ -6,13 +6,13 @@ x-toc-enable: true
 TODO: this guide should be reviewed and updated. Some info might be out of
 date.
 
-[GNU GRUB](https://www.gnu.org/software/grub/) already has excellent
+[GRUB](https://www.gnu.org/software/grub/) already has excellent
 documentation, but there are aspects of libreboot that deserve special
 treatment. libreboot provides the option to boot GNU GRUB directly, running on
 bare metal (instead of using BIOS or UEFI services).
 
-[The GNU+Linux section](../gnulinux/) also has libreboot-specific guides for
-dealing with GNU+Linux distributions when using GNU GRUB directly, in this
+[The Linux section](../gnulinux/) also has libreboot-specific guides for
+dealing with Linux distributions when using GRUB directly, in this
 setup. [A similar section exists for BSD operating systems](../bsd/)
 
 GRUB keyboard layouts

site/docs/hardware/ga-g41m-es2l.md

@@ -44,7 +44,7 @@ P*: Partially works with blobs
 
 | ***Payloads supported***  |       |
 |---------------------------|-------|
-| **GNU GRUB**              | Works |
+| **GNU GRUB**              | Slow! |
 | **SeaBIOS**               | Works |
 | **SeaBIOS with GNU GRUB** | Works |
 </div>
@@ -52,27 +52,9 @@ This is a desktop board using intel hardware (circa \~2009, ICH7
 southbridge, similar performance-wise to the ThinkPad X200. It can make
 for quite a nifty desktop. Powered by libreboot.
 
-NOTE: As of January 4th, 2021, video initialization is broken on this machine.
-It is advisable to use Libreboot 20160907, for the time being. You can build a
-ROM image from libreboot, and extract the CPU microcode updates to then insert in
-the Libreboot 20160907 ROM image, like so (using cbfstool):
-
-    cbfstool libreboot.rom extract -n cpu_microcode_blob.bin -f cpu_microcode_blob.bin
-    cbfstool libreboot.rom add -n cpu_microcode_blob.bin -f cpu_microcode_blob.bin -t microcode
-
-With this, you will then have a Libreboot ROM image, but with improved stability
-due to microcode updates. The code in coreboot that checks for this file, in
-CBFS, is present in every Libreboot release; Libreboot merely excludes the blob
-itself, but does not delete the code for loading it. The Libreboot 20160907
-release is reliable, on this board (but has a few issues, for example the PCI
-express slots don't work).
-
-The advice above is only useful for the onboard graphics chipset (the Intel
-one). If you're using an add-on graphics card (PCI express), you can simply
-use libreboot, and it will work. If you're doing *that*, please use one of the
-ROM images with the *SeaBIOS* payload, booting in text mode. SeaBIOS will
-automatically execute the option ROM on your graphics card, implementing VBE
-(Video BIOS extension).
+As of Libreboot release 20221214, only SeaBIOS payload is provided in ROMs
+for this board. According to user reports, they work quite well. GRUB was
+always buggy on this board, so it was removed from lbmk.
 
 IDE on the board is untested, but it might be possible to use a SATA HDD
 using an IDE SATA adapter. The SATA ports do work, but it's IDE emulation. The
@@ -114,4 +96,4 @@ Kingston 8 GiB Kit  KVR800D2N6/8G with Elpida Chips E2108ABSE-8G-E
 this is a 2x4GB setup and these work quite well, according to a user on IRC.
 
 Many other modules will probably work just fine, but raminit is very picky on
-this board.
+this board. Your mileage *will* fluctuate, wildly.

site/docs/hardware/index.md

@@ -4,15 +4,6 @@ x-toc-enable: true
 ...
 
 This sections relates to known hardware compatibility in libreboot.
-**Osboot merged with and became part of Libreboot on November 15th, 2022. As
-of this day, November 16th, many new boards have been added as a result, but
-some may not be documented or even listed at all (on this page). If any are
-missing, please tell us on IRC.**
-
-**If a target doesn't yet have ROM images in the release (ones present as a
-result of the osboot merge), please know that the Libreboot 20220710 release
-was conducted before the merge. The next release after Libreboot 20220710 shall
-contain ROM images for these additional boards.**
 
 For installation instructions, refer to [../install/](../install/).
 
@@ -77,6 +68,9 @@ libreboot currently supports the following systems in this release:
 -   ASUS Chromebook Flip C101 (google/gru)
 -   Samsung Chromebook Plus (v1) (google/gru)
 
+NOTE: the above list may be incomplete. For example, `gru_kevin`
+is also present in lbmk. This needs to be tidied up.
+
 NOTE: ARM hardware is currently undocumented in Libreboot, both for
 installation of Libreboot and the installation of an operating system. If you
 have one of these machines configured with Libreboot, you should consult
@@ -85,6 +79,20 @@ Libera IRC, who ported these boards to Libreboot. Extensive work was
 performed, to make u-boot work correctly. **TODO: installation instructions
 must be added to documentation!**
 
+NOTE: As of 11 December 2022, building of u-boot images has been tested on
+Debian Linux. Make sure you have the latest lbmk from the Git repository, and
+the build dependencies are installed like so, from `lbmk/` as root:
+
+    ./build dependencies debian
+
+This installs everything needed for cross-compiling, and part of the build
+process makes use of coreboot's own cross-compile toolchain.
+
+### Emulation
+
+-   [Qemu x86](../misc/emulation.md)
+
+
 TODO: More hardware is supported. See `resources/coreboot/` in lbmk. Update
 the above list!
 

site/docs/hardware/macbook21.md

@@ -35,17 +35,14 @@ P+: Partially works;
 P*: Partially works with blobs
 ```
 
-| ***Features*** |                                       | Notes |
-|----------------|---------------------------------------|-------|
-| **Internal flashing with original boot firmware** | W+ | MacBook1,1 does 
-                                                not support this |
-| **Display**                                       | W+ |       |
-| **Audio**                                         | W+ | Audio quality is 
-                                     better when using Libreboot |
-| **RAM Init**                                      | W+ |       |
-| **External output**                               | W+ |       |
-| **Display brightness**                            | P+ | [Finetune backlight 
-control](../misc/#finetune-backlight-control-on-intel-gpus)      |
+| ***Features*** |                                       |
+|----------------|---------------------------------------|
+| **Internal flashing with original boot firmware** | W+ |
+| **Display**                                       | W+ |
+| **Audio**                                         | W+ |
+| **RAM Init**                                      | W+ |
+| **External output**                               | W+ |
+| **Display brightness**                            | P+ |
 
 | ***Payloads supported***  |           |
 |---------------------------|-----------|
@@ -53,17 +50,14 @@ control](../misc/#finetune-backlight-control-on-intel-gpus)      |
 | **SeaBIOS**               | Works     |
 | **SeaBIOS with GNU GRUB** | Works     |
 </div>
-There is an Apple laptop called the macbook1,1 from 2006 which uses the
-same i945 chipset as the ThinkPad X60/T60. A developer (Mono Moosbart) ported
-the Macbook2,1 to coreboot, working alongside Vladimir Serbinenko. The ROM
-images also work on the macbook1,1.
+The MacBook1,1 and MacBook2,1 are very similar to the 
+ThinkPad X60. It shares some hardware with the X60 such as the chipset.
 
-Some macbook2,1 models are late 2006, others are early 2007.
 You do not need to use external flashing equipment when flashing the MacBook2,1
 but the MacBook1,1 requires external flashing equipment while running Apple EFI
 firmware.
 
-Macbook2,1 laptops come with Core 2 Duo processors
+MacBook2,1 laptops come with Core 2 Duo processors
 which support 64-bit operating systems (and 32-bit). The MacBook1,1
 uses Core Duo processors (supports 32-bit OS but not 64-bit), and it is
 believed that this is the only difference.
@@ -79,13 +73,13 @@ The following pages list many models of MacBook1,1 and MacBook2,1:
 Models
 ------
 
-Specifically (Order No. / Model No. / CPU) for macbook 1,1:
+Specifically (Order No. / Model No. / CPU) for the MacBook1,1:
 
 * MA255LL/A / A1181 (EMC 2092) / Core Duo T2500 *(tested - working)*
 * MA254LL/A / A1181 (EMC 2092) / Core Duo T2400 *(tested - working)*
 * MA472LL/A / A1181 (EMC 2092) / Core Duo T2500 (untested)
 
-For macbook 2,1:
+For the MacBook2,1:
 
 * MA699LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T5600 *(tested -
     working)*
@@ -94,25 +88,31 @@ For macbook 2,1:
 * MB061LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7200 (untested)
 * MA700LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 *(tested -
     working)*
-* MB063LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 (works)
+* MB063LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 *(tested - working)*
 * MB062LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 *(tested -
     working)*
 
+It's believed that all MacBook2,1 and MacBook1,1 models work fine with 
+Libreboot. If there's a model not in the list or not confirmed working 
+here and you happen to have that model and that model works with Libreboot 
+then don't forget to [send a patch](../../git.md), confirming that it 
+actually works!
+
 Internal flashing
 =================
 
-Macbook2,1 can always be flashed internally, even if running Apple firmware:
+MacBook2,1 can always be flashed internally, even if running Apple firmware:
 
     sudo flashrom -p internal:laptop=force_I_want_a_brick,boardmismatch=force -w your.rom
 
-Macbook1,1 same as above, but if running Apple firmware see below for
-external flashing.
+The MacBook1,1 can't be flashed internally if running the Apple EFI firmware. 
+You must flash externally.
 
 External flashing
 =================
 
-macbook1,1 requires external flashing, if running the default Apple firmware.
-macbook2,1 can be flashed internally, regardless.
+MacBook1,1 requires external flashing, if running the default Apple firmware.
+MacBook2,1 can be flashed internally, regardless.
 If running coreboot or libreboot you can already internally re-flash.
 
 [This page shows disassembly
@@ -128,25 +128,84 @@ motherboard](https://www.ifixit.com/Guide/MacBook+Core+2+Duo+PRAM+Battery+Replac
 Refer to the following guide:\
 [Externally rewrite 25xx NOR flash via SPI protocol](../install/spi.md)
 
-You need to replace OS X with GNU+Linux before flashing libreboot. (OSX
-won't run at all in libreboot), if you wish to internally flash on a macbook21.
-libreboot won't boot OSX either (well, maybe with Tianocore it would, but that's
-untested and OSX is inferior to GNU+Linux). In general you should think of
-your Macbook like a regular laptop, for the purposes of anything coreboot.
+OSes using Linux on Apple EFI firmware
+======================================
+
+You have 2 choices for booting up OSes using Linux as their kernel 
+on the MacBook:
+
+* Boot via USB ;
+
+* Boot via a CD or DVD.
+
+Boot via a CD or DVD
+--------------------
+
+The Apple EFI firmware contains a PC BIOS emulation layer for booting 
+Microsoft Windows on CDs and DVDs. That emulation layer **only** works 
+if booting from a CD/DVD or from the hard drive. The MacBook will **not** 
+boot MBR bootloaders from USB, which is why booting from a CD or DVD is 
+easier than booting from a USB.
+
+* First, burn your ISO to a CD or DVD ;
+
+* Reboot and while rebooting, hold down the Alt/Control key, a boot menu 
+should pop up, requesting you to choose which device to boot from ;
+
+* Select the CD/DVD icon with 'Windows' as the label (the Apple EFI firmware 
+elways recognises CDs/DVDs using MBR as 'Windows', because the emulation 
+layer was made specifically for booting Microsoft Windows as part of 
+BootCamp, a tool which allowed dual-booting Windows and OS X) ;
+
+* Install it like you normally would (If there's an OS X installation then 
+it's highly recommended to save all your data and wipe it. Libreboot isn't 
+able and will never be able to boot OS X) ;
+
+* While rebooting, hold Alt/Control once again, and select the hard disk 
+icon with the 'Windows' label, after each subsequent boot, the Apple EFI 
+should boot up properly automatically.
+
+*If you installed your OS alongside OS X then you won't be able to boot 
+to it using GRUB, despite the fact that it does sometimes show up. You 
+also won't be able to boot it up when using Libreboot.*
+
+Boot via USB
+------------
+
+This method is harder than booting from a CD/DVD and may soft-brick your 
+MacBook but it's the only way to boot up successfully from a USB.
+
+The PC BIOS emulation layer found in the Apple EFI firmware doesn't work 
+when booting up from a USB stick. Despite the fact that the 
+MacBook2,1 does use a 64-Bit processor, the firmware only supports booting 
+32-Bit EFI devices, meaning you're stuck with 32-Bit OSes and rare 
+64-Bit OSes which have ISOs that still support booting from 32-Bit EFI. 
+Meanwhile, GRUB fully supports booting up 64-Bit OSes on 32-Bit EFI.
+
+* First, search for an ISO that supports 32-Bit EFI while being 64-Bit or 
+a normal 32-Bit ISO and put it in your USB stick ;
+
+* Reboot and while rebooting, hold down the Alt/Control key, a boot menu 
+should pop up, requesting you to choose which device to boot from ;
+
+* Select the USB icon ;
+
+* Install it like you normally would (If there's an OS X installation then 
+it's highly recommended to save all your data and wipe it. Libreboot isn't 
+able and will never be able to boot OS X) ;
 
-If it's a macbook2,1 with the core2duo processors, you can run
-a 64-bit distro. For macbook 1,1 the CPU probably only has 32-bit support.
+* Reboot. It should boot up to your newly-installed system if you wiped OS X, 
+else, hold Alt/Control and select the correct boot device ;
 
-GNU+Linux on Apple EFI firmware
-===============================
+* Flash Libreboot. DO NOT REBOOT AGAIN BEFORE FLASHING. Sometimes the 
+firmware can get confused, because Apple never intended to boot other 
+EFI OSes other than OS X, as such there's a chance that your MacBook can 
+become [soft-bricked](https://apple.stackexchange.com/questions/408104/late-2006-macbook-doesnt-turn-on-fan-spinning-but-no-chime/409754). 
+If that is the case then dissassemble it and remove 
+the CMOS/PRAM battery, wait a few minutes, and put it back in.
 
-How to boot an ISO: burn it to a CD (like you would normally) and hold
-down the Alt/Control key while booting. The bootloader will detect the
-GNU+Linux CD as 'Windows' (because Apple doesn't think GNU+Linux
-exists). Install it like you normally would. When you boot up again,
-hold Alt/Control once more. The installation (on the HDD) will once
-again be seen as 'Windows'. (it's not actually Windows, but Apple
-likes to think that Apple and Microsoft are all that exist.)
+*If you want to install Libreboot with the SeaBIOS payload then be sure 
+to reconfigure GRUB2 correctly, else your system won't boot.*
 
 Coreboot wiki page
 ==================
@@ -159,10 +218,9 @@ Issues and solutions/workarounds
 ================================
 
 There is one mouse button only, however multiple finger tapping
-works. Battery life is poor compared to X60/T60. The Apple logo on the
+works. The Apple logo on the
 back is a hole, exposing the backlight, which means that it glows. You
 should [cover it up](http://cweiske.de/tagebuch/tuxbook.htm).
-The MacBook2,1 consumes more power with libreboot than with the Apple EFI firmware, which means it overheats a lot.
 
 *The MacBook2,1 comes with a webcam which does not work with free
 software. Webcams are a privacy and security risk; cover it up! Or

site/docs/install/index.md

@@ -21,6 +21,22 @@ If you're already running libre firmware on your board, you should decide for
 sure whether you wish to risk it. See changelogs on
 the [release announcements via the news page](/news/) and decide for yourself.
 
+Haswell/Ivybridge/Sandybridge machines
+======================================
+
+BLOBS MISSING IN RELEASE ROMs
+-----------------------------
+
+E.g. ThinkPad X220, X230, T440p, W541.
+
+The lbmk build system automatically fetches required blobs for these
+boards, when building, and sets them up properly, e.g. `me_cleaner`
+is used. The same process is also available in a script, which can
+insert them into ROM images.
+
+**If you're using release ROMs, these blobs are missing, and must be
+added. See: [ivy_has_common.md](ivy_has_common.md).**
+
 About ROM image file names
 ==========================
 
@@ -109,14 +125,41 @@ an option in the boot menu.
 ROM images that have `seabios_withgrub` in the file name start with SeaBIOS
 first, but also have GNU GRUB available in the boot menu when you press ESC.
 
-### seabios\_grubfirst
+### seabios\_grubfirst (DEFUNCT, WAS INTENDED ONLY FOR DESKTOPS)
+
+**DEFUNCT**
+
+This build option is obsolete, and should not be used. It was deleted
+in lbmk revision `e1bbdadc9584291cf062660d67128e9f17ab788e`.
+
+It was believed, in earlier theory, that VGA ROM initialisation could
+be used in SeaBIOS and then SeaBIOS boots into a GRUB payload (built
+for coreboot), where the initialisation would continue to be used, but
+it didn't work that way.
+
+It's best to use PC GRUB (normal BIOS GRUB), but compile it into a floppy
+image to insert inside CBFS, to then be executed by SeaBIOS. This is referred
+to as SeaGRUB by the Libreboot project, and it would be quite useful
+for desktop users, but it's largely irrelevant on laptops where
+coreboot's own `libgfxinit` is usually available (or the option ROM is
+easy to extract from vendor firmware and insert).
+
+Where direct bare metal GRUB is desired, but you use a desktop system with
+an add-on graphics card, you must extract the VGA ROM for your card and
+insert it into the coreboot ROM, for coreboot itself to execute. This will
+require custom configuration on your part, and it is thus beyond the scope
+of the Libreboot project, in context of lbmk (automated build system).
+
+Some older Libreboot releases included ROM images built using this option,
+and those specific ROM images (`seabios_grubfirst` ones) should not be
+used; you should only use `seabios_grubfirst` or `seabios`, in most
+scenarios, if SeaBIOS is required.
 
-ROM images that have `seabios_grubfirst` in the file name start with SeaBIOS,
-but SeaBIOS is configured via special `bootorder` file in CBFS so as to ONLY
-load GNU GRUB. This setup would be most useful on desktops, where you wish to
-only have GNU GRUB available, but want to use an add-on GPU while also having
-the option to use libgfxinit, if a supported GPU/framebuffer chip is present
-on your board.
+For most desktop users, if running an external graphics card, it's easier
+to simply boot in text mode with a SeaBIOS payload and use only that. This
+will Just Work with almost all graphics cards, allowing you to use an
+operating system with a full display and (drivers permitting) full 2D/3D
+acceleration.
 
 Which systems are supported?
 ============================
@@ -585,11 +628,32 @@ TARGET: Lenovo ThinkPad R500 laptop
 Refer to the following laptop:\
 [ThinkPad R500](../hardware/r500.md)
 
+sandybridge/ivybridge/haswell
+=================
+
+**If using release ROMs, neutered ME must be inserted. Refer to the info
+below.**
+
+TARGET: ThinkPad X220/T420/T420s
+--------------------------------
+
+Similar to X230 but there's only 1 flash. Intel ME image must be inserted
+if using release ROMs. See: [guide](ivy_has_common.md) (says ivy/haswell but
+the insert script for ME works with sandybridge aswell).
+
+**If using release ROMs, neutered ME must be inserted. Refer to the above
+guide.**
+
 TARGET: Thinkpad X230
 ---------------------
 
+NOTE: Internal flashing is also possible, on this machine, from vendor firmware,
+but it's still recommended to use a clip and a SPI flasher. However, follow
+[internal X230 flashing from Lenovo firmware](ivy_internal.md) if you wish.
+
 Refer to the [ivybridge/haswell common guide.](ivy_has_common.md) for how to
-make the rom image usable for external flashing.
+make the rom image usable for external flashing (with a clip). **If using
+release ROMs, you must insert the neutered ME. Look at the info on that page.**
 
 Read [board documentation](/docs/install/x230_external.html) for disassembly.
 
@@ -603,6 +667,9 @@ Read [board documentation](/docs/install/x230_external.html) for disassembly.
 (same instructions as X230, for this purpose of external flashing, but
 full disassembly will differ slightly)
 
+**If using release ROMs, neutered ME must be inserted. Refer to the above
+guide.**
+
 TARGET: Thinkpad t440p
 ---------------------
 
@@ -610,3 +677,6 @@ Refer to the [ivybridge/haswell common guide.](ivy_has_common.md) for how to
 make the rom image usable for external flashing.
 
 Read [board documentation](/docs/install/t440p_external.html) for disassembly.
+
+**If using release ROMs, neutered ME must be inserted. Refer to the above
+guide.**