diff options
Diffstat (limited to 'docs')
53 files changed, 107 insertions, 27 deletions
diff --git a/docs/archive_old.md b/docs/archive_old.md index f8d3f441..54d9c620 100644 --- a/docs/archive_old.md +++ b/docs/archive_old.md @@ -16,6 +16,7 @@ Releases - [r20150518 (18th May 2015)](#release20150518) - [r20150124 (24th January 2015), r20150126 (26th January 2015), r20150208 (8th February 2015)](#release20150124) + - [r20141015 (15th October 2014)](#release20141015) - [r20140911 (6th release)](#release20140911) (11th September 2014 **pre-release, 7th beta**) @@ -422,7 +423,8 @@ Changes for this release (latest changes first, earliest changes last) - build: Only generate the GRUB configurations once (re-use on all images) - Only build 2 GRUB payload executables, re-use on all boards. -- resources/utilities/grub-assemble/gen.txtmode.sh: Use GNU BASH\ +- resources/utilities/grub-assemble/gen.txtmode.sh: Use GNU BASH + resources/utilities/grub-assemble/gen.vesafb.sh: Use GNU BASH - scripts (error handling): Replace exit with exit 1 (make debugging easier) diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md index 9f0d58e0..31d9df17 100644 --- a/docs/bsd/freebsd.md +++ b/docs/bsd/freebsd.md @@ -59,8 +59,10 @@ Prepare the USB drive (in LibertyBSD or OpenBSD) If you downloaded your ISO on a LibertyBSD or OpenBSD system, here is how to create the bootable FreeBSD USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg | tail + Check to confirm which drive it is, for example, if you think its sd3:\ $ disklabel sd3 diff --git a/docs/bsd/index.md b/docs/bsd/index.md index 8f0aad75..7b2aecbe 100644 --- a/docs/bsd/index.md +++ b/docs/bsd/index.md @@ -11,6 +11,7 @@ instructions have yet to be written.** - [How to install NetBSD on a libreboot system](netbsd.html) - [How to install LibertyBSD or OpenBSD on a libreboot system](openbsd.html) + - [How to install FreeBSD on a libreboot system](freebsd.html) diff --git a/docs/bsd/netbsd.md b/docs/bsd/netbsd.md index ff515c40..3046ef00 100644 --- a/docs/bsd/netbsd.md +++ b/docs/bsd/netbsd.md @@ -55,8 +55,10 @@ Prepare the USB drive (in LibertyBSD or NetBSD) If you downloaded your ISO on a LibertyBSD or NetBSD system, here is how to create the bootable NetBSD USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg | tail + Check to confirm which drive it is, for example, if you think its sd3:\ $ disklabel sd3 diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md index 4a7027d3..4440b665 100644 --- a/docs/bsd/openbsd.md +++ b/docs/bsd/openbsd.md @@ -37,8 +37,10 @@ Prepare the USB drive (in LibertyBSD or OpenBSD) If you downloaded your ISO on a LibertyBSD or OpenBSD system, here is how to create the bootable LibertyBSD/OpenBSD USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg | tail + Check to confirm which drive it is, for example, if you think its sd3:\ $ disklabel sd3 diff --git a/docs/depthcharge/index.md b/docs/depthcharge/index.md index 745b5e8b..4828a390 100644 --- a/docs/depthcharge/index.md +++ b/docs/depthcharge/index.md @@ -10,6 +10,7 @@ This section relates to the depthcharge payload used in libreboot. - Booting from different mediums - Showing device information - Warnings + - [Recovery mode screen](#recovery_mode_screen) - [Recovering from a bad state](#recovering_bad_state) - [Enabling developer mode](#enabling_developer_mode) @@ -185,7 +186,8 @@ security of the device. The following parameters can be configured: - Kernels signature verification: - - Enabled with:\ + - Enabled with: + \# **crossystem dev\_boot\_signed\_only=1** - Disabled with:\ \# **crossystem dev\_boot\_signed\_only=0** diff --git a/docs/future/index.md b/docs/future/index.md index 3eacbc92..f15f40a8 100644 --- a/docs/future/index.md +++ b/docs/future/index.md @@ -15,6 +15,7 @@ Table of contents - [i945 VRAM size](#i945_vram_size) - [LCD panels on i945 - fix incompatible panels](#lcd_i945_incompatibility) + - [i945 X60/T60 VBT implementation (experimental: testing)](#i945_vbt) - [IntelVbtTool results](#intelvbttool_results) - [Fallback patches for i945](#fallback_patches) @@ -162,7 +163,8 @@ How to dump EDID: # modprobe i2c-dev Find out the correct ID to use: # i2cdetect -l\ -Example:\ +Example: + # i2cdump -y 2 0x50 Working panel: EDID dump from LG-Philips LP150E05-A2K1: diff --git a/docs/future/old.md b/docs/future/old.md index 8fc4e273..c68c4385 100644 --- a/docs/future/old.md +++ b/docs/future/old.md @@ -12,6 +12,7 @@ Table of contents - [X60 native graphics initialization (backlight controls)](#x60_native_notes) + - [T60 native graphics initialization (backlight controls)](#t60_native_notes) - [i945: 3D fix (based on 5927) for kernel 3.12+ on @@ -43,7 +44,8 @@ That's all! **This has also been backported into libreboot 5th release (line 1233 in src/mainboard/lenovo/x60/i915io.c)**. GNUtoo (Denis Carikli) told me about the register **BLC\_PWM\_CTL** and that you could set it to control backlight. I read that address using devmem2 while -running the VBIOS:\ +running the VBIOS: + # devmem2 0xe4361254 w The change is also included in libreboot 6. diff --git a/docs/git/index.md b/docs/git/index.md index 71faafc1..fe25cecf 100644 --- a/docs/git/index.md +++ b/docs/git/index.md @@ -16,6 +16,7 @@ the git repository. - [Get the full source code from metadata (git clone)](#build_meta) - [How to build "bucts" (for LenovoBIOS X60/X60S/X60T/T60)](#build_bucts) + - [How to build "flashrom"](#build_flashrom) - [How to build the ROM images](#build) @@ -63,7 +64,8 @@ First, [install the build dependencies](#build_dependencies). Since libreboot makes extensive use of git, you need to configure git properly. If you have not yet configured git, then the minimum -requirement is:\ +requirement is: + $ git config --global user.name "Your Name" $ git config --global user.email your@emailaddress.com This is what will also appear in git logs if you ever commit your own diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md index 8a3f4751..1ba9e366 100644 --- a/docs/gnulinux/configuring_parabola.md +++ b/docs/gnulinux/configuring_parabola.md @@ -19,6 +19,7 @@ Table of Contents - [Pacman command equivalents (compared to other package managers)](#pacman_commandequiv) - [your-freedom](#yourfreedom) + - [Add a user account](#useradd) - [System D](#systemd) - [Interesting repositories](#interesting_repos) @@ -126,7 +127,8 @@ Updating Parabola {#pacman_update} ----------------- In the end, I didn't change my configuration for pacman. When you are -updating, resync with the latest package names/versions:\ +updating, resync with the latest package names/versions: + # pacman -Syy (according to the wiki, -Syy is better than Sy because it refreshes the package list even if it appears to be up to date, which can be useful diff --git a/docs/gnulinux/encrypted_debian.md b/docs/gnulinux/encrypted_debian.md index 6dfb1435..9f65baa5 100644 --- a/docs/gnulinux/encrypted_debian.md +++ b/docs/gnulinux/encrypted_debian.md @@ -77,6 +77,7 @@ Choose 'Manual' partitioning: - Encryption key: passphrase - erase data: Yes (only choose 'No' if it's a new drive that doesn't contain your private data) + - Select 'configure encrypted volumes' - Create encrypted volumes - Select your partition diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index 2771bf34..c4e92c16 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -70,6 +70,7 @@ whole article and keep all points in mind, adapting them for this guide. Securely wipe the drive: # dd if=/dev/urandom of=/dev/sda; sync + NOTE: If you have an SSD, only do this the first time. If it was already LUKS-encrypted before, use the info below to wipe the LUKS header. Also, check online for your SSD what the recommended erase block size is. For @@ -82,7 +83,8 @@ header. <https://www.lisenet.com/2013/luks-add-keys-backup-and-restore-volume-header/> showed me how to do this. It recommends doing the first 3MiB. Now, that guide is recommending putting zero there. I'm going to use urandom. Do -this:\ +this: + # head -c 3145728 /dev/urandom > /dev/sda; sync (Wiping the LUKS header is important, since it has hashed passphrases and so on. It's 'secure', but 'potentially' a risk). diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md index 1fd924b1..4609db97 100644 --- a/docs/gnulinux/grub_boot_installer.md +++ b/docs/gnulinux/grub_boot_installer.md @@ -28,8 +28,10 @@ Prepare the USB drive (in GNU+Linux) If you downloaded your ISO on an existing GNU+Linux system, here is how to create the bootable GNU+Linux USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg + Check lsblk to confirm which drive it is:\ $ lsblk diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md index 31192f5a..dbe55206 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -45,6 +45,7 @@ Table of Contents + Introduction ------------ @@ -142,7 +143,8 @@ your current firmware, using flashrom: $ sudo flashrom -p internal -r libreboot.rom # flashrom -p internal -r libreboot.rom If you are told to specify the chip, add the option **-c {your chip}** -to the command, for example:\ +to the command, for example: + # flashrom -c MX25L6405 -p internal -r libreboot.rom [Back to top of page.](#pagetop) diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md index 9c1a819d..81a3452b 100644 --- a/docs/gnulinux/grub_hardening.md +++ b/docs/gnulinux/grub_hardening.md @@ -31,6 +31,7 @@ image: cbfstool my.rom extract -n grubtest.cfg -f my.grubtest.cfg cbfstool my.rom remove -n grubtest.cfg + Helpful links: - [GRUB manual diff --git a/docs/gnulinux/index.md b/docs/gnulinux/index.md index 79983797..49c04dfd 100644 --- a/docs/gnulinux/index.md +++ b/docs/gnulinux/index.md @@ -10,6 +10,7 @@ instructions have yet to be written.** - [How to install GNU+Linux on a libreboot system](grub_boot_installer.html) + - [How to replace the default GRUB configuration file on a libreboot system](grub_cbfs.html) - [Installing Parabola or Arch GNU+Linux-libre with full disk diff --git a/docs/grub/index.md b/docs/grub/index.md index 81e4bd56..0c676da9 100644 --- a/docs/grub/index.md +++ b/docs/grub/index.md @@ -11,6 +11,7 @@ This section relates to the GRUB payload used in libreboot. + Changing the background image in GRUB {#grub_background} ===================================== @@ -47,7 +48,8 @@ like Debian, Devuan or Parabola. $ cd libreboot\_src/grub compile grub (the build scripts info on how to do this)\ -come back out into libreboot\_src/resources/grub:\ +come back out into libreboot\_src/resources/grub: + $ cd ../libreboot\_src/resources/grub/font I took Dejavu Sans Mono from dejavu (included in this version of diff --git a/docs/hardware/dock.md b/docs/hardware/dock.md index f1e86226..079a4e6f 100644 --- a/docs/hardware/dock.md +++ b/docs/hardware/dock.md @@ -8,6 +8,7 @@ Usually when people do full disk encryption, it's not really full disk, instead they still have a /boot in clear. + So an evil maid attack can still be done, in two passes: 1) Clone the hdd, Infect the initramfs or the kernel. 2) Wait for the user to enter its password, recover the password, diff --git a/docs/hardware/index.md b/docs/hardware/index.md index d7262669..f7a119dd 100644 --- a/docs/hardware/index.md +++ b/docs/hardware/index.md @@ -6,6 +6,7 @@ This section relates to hardware maintenance on supported targets. - [ThinkPad X60/X60s/X60T: Change keyboard](x60_keyboard.html) (the procedure on X200/X200S/X200T is almost identical) + - [ThinkPad X60/X60S: change the fan/heatsink](x60_heatsink.html) - [ThinkPad X60/X60s: How to change the LCD panel](x60_lcd_change.html) (incomplete. pics only for now) diff --git a/docs/hardware/t60_heatsink.md b/docs/hardware/t60_heatsink.md index f9fbde2b..a3ff52e3 100644 --- a/docs/hardware/t60_heatsink.md +++ b/docs/hardware/t60_heatsink.md @@ -11,6 +11,7 @@ Hardware requirements {#hardware_requirements} - rubbing alcohol or isopropyl alcohol, and thermal compound for changing CPU heatsink (procedure involves removing heatsink) + - thermal compound/paste (Arctic MX-4 is good. Others are also good.) diff --git a/docs/hardware/t60_security.md b/docs/hardware/t60_security.md index 6103c42d..974f8b43 100644 --- a/docs/hardware/t60_security.md +++ b/docs/hardware/t60_security.md @@ -231,6 +231,7 @@ Not covered yet: - Disable flashing the ethernet firmware - Disable SPI flash writes (can be re-enabled by unsoldering two parts) + - Disable use of xrandr/edid on external monitor (cut 2 pins on VGA) - Disable docking station (might be possible to do it in software, in coreboot upstream as a Kconfig option) @@ -248,7 +249,8 @@ half of the video to see how to do the above. Also not covered yet: --------------------- -- Intrusion detection: randomized seal on screws\ +- Intrusion detection: randomized seal on screws + Just put nail polish with lot of glider on the important screws, take some good pictures. Keep the pictueres and make sure of their integrity. Compare the nail polish with the pictures before powering diff --git a/docs/hardware/x60_heatsink.md b/docs/hardware/x60_heatsink.md index 35a9c48b..4493f954 100644 --- a/docs/hardware/x60_heatsink.md +++ b/docs/hardware/x60_heatsink.md @@ -22,6 +22,7 @@ Hardware requirements {#hardware_requirements} - your new fan and/or heatsink - CPU thermal compound (some say Arctic MX-4 is good, others are also 'ok') + - Something to spread the paste with diff --git a/docs/hardware/x60_security.md b/docs/hardware/x60_security.md index 1e9479ac..23dba9d0 100644 --- a/docs/hardware/x60_security.md +++ b/docs/hardware/x60_security.md @@ -137,6 +137,7 @@ Not covered yet: - Disable flashing the ethernet firmware - Disable SPI flash writes (can be re-enabled by unsoldering two parts) + - Disable use of xrandr/edid on external monitor (cut 2 pins on VGA) - Disable docking station (might be possible to do it in software, in coreboot upstream as a Kconfig option) @@ -152,7 +153,8 @@ half of the video to see how to do the above. Also not covered yet: --------------------- -- Intrusion detection: randomized seal on screws\ +- Intrusion detection: randomized seal on screws + Just put nail polish with lot of glider on the important screws, take some good pictures. Keep the pictueres and make sure of their integrity. Compare the nail polish with the pictures before powering diff --git a/docs/hcl/c201.md b/docs/hcl/c201.md index b04fb525..ddf293ee 100644 --- a/docs/hcl/c201.md +++ b/docs/hcl/c201.md @@ -22,6 +22,7 @@ Flashing instructions can be found at - [Considerations about ChromeOS and free operating systems](#os) - [Caution: Video acceleration requires a non-free blob, software rendering can be used instead.](#videoblobs) + - [Caution: WiFi requires a non-free blob, a USB dongle can be used instead.](#wifiblobs) - [EC firmware is free software!](#ec) diff --git a/docs/hcl/d945gclf.md b/docs/hcl/d945gclf.md index b2ef3cd0..7b2f95d9 100644 --- a/docs/hcl/d945gclf.md +++ b/docs/hcl/d945gclf.md @@ -33,6 +33,7 @@ Remarks about vendor bios: vendor bios is very bad. It cannot boot from any HDD wether it is connected to the SATA port or USB. With libreboot it works just fine. + - The vendor bios write protects the flash so it requires external flashing to install libreboot on this device. Once libreboot is flashed there is no problem to update the firmware internally diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md index c10c892e..485bf731 100644 --- a/docs/hcl/gm45_remove_me.md +++ b/docs/hcl/gm45_remove_me.md @@ -40,6 +40,7 @@ ich9gen executables can be found under ./ich9deblob/ statically compiled in libreboot\_util. If you are using src or git, build ich9gen from source with: $ ./oldbuild module ich9deblob + The executable will appear under resources/utilities/ich9deblob/ Run: @@ -68,7 +69,8 @@ the little sticker on the bottom/base of the laptop. On GM45 laptops that use flash descriptors, the MAC address or the onboard ethernet chipset is flashed (inside the ROM image). You should generate a descriptor+gbe image with your own MAC address inside (with -the Gbe checksum updated to match). Run:\ +the Gbe checksum updated to match). Run: + $ ./ich9gen --macaddress XX:XX:XX:XX:XX:XX (replace the XX chars with the hexadecimal chars in the MAC address that you want) diff --git a/docs/hcl/index.md b/docs/hcl/index.md index 8adb7fc4..6eb810ef 100644 --- a/docs/hcl/index.md +++ b/docs/hcl/index.md @@ -7,6 +7,7 @@ This sections relates to known hardware compatibility in libreboot. - [Servers/workstations](#supported_workstations_x86amd) - [Laptops (ARM)](#supported_laptops_arm) - [Laptops (Intel, x86)](#supported_laptops_x86intel) + - NOTES: - [Updating the EC firmware on i945 and GM45 (recommended)](#ecupdate) @@ -436,7 +437,8 @@ Referenced below are copies (up to date at the time of writing, the macbook2,1. They are included here in case the main site goes down for whatever reason, since they include a lot of useful information. -Backups created using wget:\ +Backups created using wget: + $ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/ **\$ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/coreboot/**\ diff --git a/docs/hcl/kcma-d8.md b/docs/hcl/kcma-d8.md index 901f190e..f8dab9c1 100644 --- a/docs/hcl/kcma-d8.md +++ b/docs/hcl/kcma-d8.md @@ -91,6 +91,7 @@ Current issues {#issues} can put a kernel in CBFS or on SATA and use that to boot GNU, which can be on a SAS drive. The linux kernel can use those SAS drives (via PIKE module) without an option ROM). + - IPMI iKVM module (optional add-on card) uses proprietary firmware. Since it's for remote out-of-band management, it's theoretically a backdoor similar to the Intel Management Engine. Fortunately, unlike diff --git a/docs/hcl/kfsn4-dre.md b/docs/hcl/kfsn4-dre.md index 34804c0f..84b8d455 100644 --- a/docs/hcl/kfsn4-dre.md +++ b/docs/hcl/kfsn4-dre.md @@ -70,6 +70,7 @@ Current issues {#issues} person says that they will look into it. [This config](http://review.coreboot.org/gitweb?p=board-status.git;a=blob;f=asus/kfsn4-dre/4.0-10101-g039edeb/2015-06-27T03:59:16Z/config.txt;h=4742905c185a93fbda8eb14322dd82c70641aef0;hb=055f5df4e000a97453dfad6c91c2d06ea22b8545) doesn't have the issue. + - Text-mode is a bit jittery (but still usable). (the jitter disappears if using KMS, once the kernel starts. The jitter will remain, if booting the kernel in text-mode). diff --git a/docs/hcl/kgpe-d16.md b/docs/hcl/kgpe-d16.md index 97a87a4b..b0490edc 100644 --- a/docs/hcl/kgpe-d16.md +++ b/docs/hcl/kgpe-d16.md @@ -92,6 +92,7 @@ Current issues {#issues} can put a kernel in CBFS or on SATA and use that to boot GNU, which can be on a SAS drive. The linux kernel can use those SAS drives (via PIKE module) without an option ROM). + - IPMI iKVM module (optional add-on card) uses proprietary firmware. Since it's for remote out-of-band management, it's theoretically a backdoor similar to the Intel Management Engine. Fortunately, unlike diff --git a/docs/hcl/t400.md b/docs/hcl/t400.md index c3e0d9d3..e3355f57 100644 --- a/docs/hcl/t400.md +++ b/docs/hcl/t400.md @@ -79,6 +79,7 @@ outputs from the T400: - T400 with **Winbond W25X64** flash chip (8MiB, SOIC-16) and Lenovo BIOS 2.02 (EC firmware 1.01): - [../future/dumps/logs-t400-bios2.02-ec1.01/](../future/dumps/logs-t400-bios2.02-ec1.01/) + - Version of flashrom used for the external flashing/reading logs is the one that libreboot git revision c164960 uses. diff --git a/docs/hcl/t500.md b/docs/hcl/t500.md index a17a6fc1..2b187e54 100644 --- a/docs/hcl/t500.md +++ b/docs/hcl/t500.md @@ -83,6 +83,7 @@ were something like: $ diff -u t500gbe x200gbe $ diff -u t500descriptor x200descriptor + ME VSCC table is in a different place and a different size on the T500. Libreboot disables and removes the ME anyway, so it doesn't matter. diff --git a/docs/hcl/x200.md b/docs/hcl/x200.md index deb212a9..4ab38cba 100644 --- a/docs/hcl/x200.md +++ b/docs/hcl/x200.md @@ -171,6 +171,7 @@ just simply remove the digitizer). - BOE-Hydis HV121WX4-120, HV121WX4-110 or HV121WX4-100 - cheap-ish, might be hard to find + - Samsung LTN121AP02-001 - common to find, cheap **If your X200 has an LED backlit panel in it, then you also need to get diff --git a/docs/index.md b/docs/index.md index d44b58e7..7b0280d7 100644 --- a/docs/index.md +++ b/docs/index.md @@ -32,6 +32,7 @@ Installing operating systems - [List of recommended GNU+Linux distributions for libreboot](distros/) + - [How to install GNU+Linux on a libreboot system](gnulinux/) - [How to install BSD on a libreboot system](bsd/) @@ -101,7 +102,8 @@ The libreboot project has three main goals: - ***Make coreboot easy to use***. Coreboot is notoriously difficult to install, due to an overall lack of user-focussed documentation and support. Most people will simply give up before attempting to - install coreboot.\ + install coreboot. + \ Libreboot attempts to bridge this divide, making sure that everything from building to installing coreboot is automated, as diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md index 4211777e..a52ea103 100644 --- a/docs/install/bbb_setup.md +++ b/docs/install/bbb_setup.md @@ -46,6 +46,7 @@ Shopping list (pictures of this hardware is shown later): 'Purchase'). We recommend this product because we know that it works well for our purposes and doesn't require any non-free software. + - Electrical/insulative tape: cover the entire bottom surface of the BBB (the part that rests on a surface). This is important, when placing the BBB on top of a board so that nothing shorts. Most @@ -208,7 +209,8 @@ contents of this file with: Run **apt-get update** and **apt-get upgrade** then reboot the BBB, before continuing. -Check that the firmware exists:\ +Check that the firmware exists: + # ls /lib/firmware/BB-SPI0-01-00A0.\* Output: diff --git a/docs/install/c201.md b/docs/install/c201.md index 23cbf1bc..1b15c284 100644 --- a/docs/install/c201.md +++ b/docs/install/c201.md @@ -37,6 +37,7 @@ root shell. parameters](#configuring_verified_boot_parameters) - [Removing the write protect screw](#removing_write_protect_screw) + - [Installing Libreboot to the SPI flash]() - [Installing Libreboot internally, from the device](#installing_libreboot_internally) @@ -153,7 +154,8 @@ The SPI flash has to be read first: **Note: it might be a good idea to copy the produced flash.img file at this point and store it outside of the device for backup purposes.** -Then, the **cros-flash-replace** script has to be executed as such:\ +Then, the **cros-flash-replace** script has to be executed as such: + # ./cros-flash-replace flash.img coreboot ro-frid If any error is shown, it is definitely a bad idea to go further than this point. diff --git a/docs/install/d510mo.md b/docs/install/d510mo.md index 572e7224..3a34bdbe 100644 --- a/docs/install/d510mo.md +++ b/docs/install/d510mo.md @@ -12,6 +12,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + [Back to top of page.](#pagetop) diff --git a/docs/install/ga-g41m-es2l.md b/docs/install/ga-g41m-es2l.md index c254d675..ba6a9a30 100644 --- a/docs/install/ga-g41m-es2l.md +++ b/docs/install/ga-g41m-es2l.md @@ -12,6 +12,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + [Back to top of page.](#pagetop) diff --git a/docs/install/index.md b/docs/install/index.md index c03237cf..55fbbe50 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -30,6 +30,7 @@ Setting up programmers, for external flashing via hardware method - [How to program an SPI flash chip with the BeagleBone Black](bbb_setup.html) + - [How to program an SPI flash chip with the Raspberry Pi](rpi_setup.html) @@ -278,7 +279,8 @@ How to update the flash chip contents: Ocassionally, coreboot changes the name of a given board. If flashrom complains about a board mismatch, but you are sure that you chose the -correct ROM image, then run this alternative command:\ +correct ROM image, then run this alternative command: + $ sudo ./flash forceupdate [yourrom.rom](#rom) diff --git a/docs/install/kcma-d8.md b/docs/install/kcma-d8.md index 7789c1c8..0e78b274 100644 --- a/docs/install/kcma-d8.md +++ b/docs/install/kcma-d8.md @@ -17,6 +17,7 @@ TODO: show photos here, and other info. - [kcma-d8 boards (and full systems) with libreboot preinstalled](#preinstall) + - [External programmer](#programmer) diff --git a/docs/install/kgpe-d16.md b/docs/install/kgpe-d16.md index f9751f14..ed470a15 100644 --- a/docs/install/kgpe-d16.md +++ b/docs/install/kgpe-d16.md @@ -17,6 +17,7 @@ TODO: show photos here, and other info. - [KGPE-D16 boards (and full systems) with libreboot preinstalled](#preinstall) + - [External programmer](#programmer) diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md index 7f2e7c2c..40e49415 100644 --- a/docs/install/r400_external.md +++ b/docs/install/r400_external.md @@ -73,6 +73,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + [Back to top of page.](#pagetop) @@ -252,7 +253,8 @@ factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* have been removed.\ -Now compare the 3 images:\ +Now compare the 3 images: + # sha512sum factory\*.rom If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md index 01cab733..9240038c 100644 --- a/docs/install/rpi_setup.md +++ b/docs/install/rpi_setup.md @@ -43,6 +43,7 @@ Guide](http://libreboot.org/docs/install/t60_unbrick.html). - On the X60, the BIOS chip is on the bottom of the motherboard, under a layer of protective black tape. + - On the T60, the BIOS chip is just under the palmrest, but blocked by a magnesium frame (which you will have to remove). diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md index 2f8c424f..4ddb6793 100644 --- a/docs/install/t400_external.md +++ b/docs/install/t400_external.md @@ -78,6 +78,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + [Back to top of page.](#pagetop) @@ -258,7 +259,8 @@ factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* have been removed.\ -Now compare the 3 images:\ +Now compare the 3 images: + # sha512sum factory\*.rom If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md index 05e4c112..2c350081 100644 --- a/docs/install/t500_external.md +++ b/docs/install/t500_external.md @@ -68,6 +68,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + [Back to top of page.](#pagetop) @@ -263,7 +264,8 @@ factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* have been removed.\ -Now compare the 3 images:\ +Now compare the 3 images: + # sha512sum factory\*.rom If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This diff --git a/docs/install/t60_unbrick.md b/docs/install/t60_unbrick.md index fc7a557f..309385b4 100644 --- a/docs/install/t60_unbrick.md +++ b/docs/install/t60_unbrick.md @@ -17,6 +17,7 @@ Table of Contents + Brick type 1: bucts not reset. {#bucts_brick} ============================== diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md index ac199b2a..78048867 100644 --- a/docs/install/x200_external.md +++ b/docs/install/x200_external.md @@ -36,6 +36,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + The X200S and X200 Tablet will use a WSON-8 flash chip, on the bottom of the motherboard (this requires removal of the motherboard). **Not all X200S/X200T are supported; see @@ -192,7 +193,8 @@ factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* have been removed.\ -Now compare the 3 images:\ +Now compare the 3 images: + # sha512sum factory\*.rom If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md index 33a4fef3..b6710a99 100644 --- a/docs/install/x60_unbrick.md +++ b/docs/install/x60_unbrick.md @@ -17,6 +17,7 @@ Table of Contents + Brick type 1: bucts not reset. {#bucts_brick} ============================== diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md index cc62ecaf..0a1801b1 100644 --- a/docs/install/x60tablet_unbrick.md +++ b/docs/install/x60tablet_unbrick.md @@ -17,6 +17,7 @@ Table of Contents + Brick type 1: bucts not reset. {#bucts_brick} ============================== diff --git a/docs/misc/bbb_ehci.md b/docs/misc/bbb_ehci.md index 4833ff93..51fd40df 100644 --- a/docs/misc/bbb_ehci.md +++ b/docs/misc/bbb_ehci.md @@ -9,6 +9,7 @@ EHCI debugging 1. [Find USB port on the target that supports EHCI debug](#FindUSBportonthetargetthatsupportsEHCIdebug) + 2. [Initial setup of BBB to act as EHCI debug dongle](#InitialsetupofBBBtoactasEHCIdebugdongle) 3. [Patch BBB's `g_dbgp` module (optional, but highly diff --git a/docs/misc/index.md b/docs/misc/index.md index 7d73569b..afffbbeb 100644 --- a/docs/misc/index.md +++ b/docs/misc/index.md @@ -3,6 +3,7 @@ - [High Pitched Whining Noise on Idle (how to remove in Debian or Devuan)](#debian_powertop) + - [High Pitched Whining Noise on Idle (how to remove in Parabola)](#high_pitch_parabola) - [X60/T60: Serial port - how to use (for dock owners)](#serial) @@ -57,7 +58,8 @@ On the X60 with coreboot or libreboot, there is a high pitched sound when idle. So far we have use processor.max\_cstate=2 or idle=halt in GRUB. These consume power. Stop using them! -Be root\ +Be root + $ su - Installed powertop:\ diff --git a/docs/misc/patch.md b/docs/misc/patch.md index 9f22f776..a8dffc92 100644 --- a/docs/misc/patch.md +++ b/docs/misc/patch.md @@ -9,9 +9,11 @@ This is just a quick guide for reference, use 'man' to know more. Apply a patch ============= -To apply a patch to a single file, do that in it's directory:\ +To apply a patch to a single file, do that in it's directory: + $ patch < foo.patch + Assuming that the patch is distributed in unified format identifying the file the patch should be applied to, the above will work. Otherwise:\ $ patch foo.txt < bar.patch diff --git a/docs/release.md b/docs/release.md index bb7266a0..5476a63a 100644 --- a/docs/release.md +++ b/docs/release.md @@ -30,6 +30,7 @@ Other bugfixes: - re-added "unset superusers" to the grub.cfg, which was needed for some users depending on the distros that they used + Libreboot 20160902 {#release20160922} ================== |