libreboot

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README

commit a62fe03d3e84150e6186f57f53029d5a9abe3d7b
parent 07da8fb0c7d513bc73470b69be99f1add0cb95e5
Author: Alyssa Rosenzweig <alyssa@rosenzweig.io>
Date:   Mon, 20 Mar 2017 20:26:48 -0700

undo breakages

Diffstat:
docs/archive_old.md | 166++++++++++++++++++++++++++++++++++++++++++++-----------------------------------
docs/bsd/freebsd.md | 86+++++++++++++++++++++++++++++++++++++++++++++++++------------------------------
docs/bsd/index.md | 9++++++---
docs/bsd/netbsd.md | 95+++++++++++++++++++++++++++++++++++++++++++++++--------------------------------
docs/bsd/openbsd.md | 95+++++++++++++++++++++++++++++++++++++++++++++++--------------------------------
docs/depthcharge/index.md | 107++++++++++++++++++++++++++++++++++++++++++++-----------------------------------
docs/distros/index.md | 132+++++++++++++++++++++++++++++++++++++++++++------------------------------------
docs/fsf-distros/index.md | 12++++++++++--
docs/future/index.md | 225+++++++++++++++++++++++++++++++++++++++----------------------------------------
docs/future/old.md | 52+++++++++++++++++++++++++++++++++++-----------------
docs/git/index.md | 145+++++++++++++++++++++++++++++++++++++++----------------------------------------
docs/global.css | 38--------------------------------------
docs/gnulinux/configuring_parabola.md | 415+++++++++++++++++++++++++++++++++++++------------------------------------------
docs/gnulinux/encrypted_debian.md | 83+++++++++++++++++++++++++++++++++++++++++++++++--------------------------------
docs/gnulinux/encrypted_parabola.md | 525+++++++++++++++++++++++++++++++++++--------------------------------------------
docs/gnulinux/grub_boot_installer.md | 147++++++++++++++++++++++++++++++++++++++++---------------------------------------
docs/gnulinux/grub_cbfs.md | 109+++++++++++++++++++++++++++++++++++++++++++------------------------------------
docs/gnulinux/grub_hardening.md | 25+++++++++++++++++--------
docs/gnulinux/index.md | 9++++++---
docs/grub/index.md | 58+++++++++++++++++++++++++++++++++++-----------------------
docs/hardware/dock.md | 11+++++++++--
docs/hardware/index.md | 7+++++--
docs/hardware/t60_heatsink.md | 52++++++++++++++++++++++++----------------------------
docs/hardware/t60_lcd_15.md | 35++++++++++++++++-------------------
docs/hardware/t60_security.md | 182+++++++++++++++++++++++++++++++++++--------------------------------------------
docs/hardware/x60_heatsink.md | 67+++++++++++++++++++++++++++++++------------------------------------
docs/hardware/x60_keyboard.md | 21+++++++++++----------
docs/hardware/x60_lcd_change.md | 9+++++++--
docs/hardware/x60_security.md | 123+++++++++++++++++++++++++++++++++++++------------------------------------------
docs/hcl/c201.md | 37+++++++++++++++++++++++++++++++++----
docs/hcl/d510mo.md | 7+++++--
docs/hcl/d945gclf.md | 64+++++++++++++++++++++++++---------------------------------------
docs/hcl/ga-g41m-es2l.md | 12+++++++-----
docs/hcl/gm45_remove_me.md | 105++++++++++++++++++++++++++++++++++++++++++++-----------------------------------
docs/hcl/imac52.md | 7+++++--
docs/hcl/index.md | 112+++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------
docs/hcl/kcma-d8.md | 27+++++++++++++++++++++++----
docs/hcl/kfsn4-dre.md | 23++++++++++++++++++++---
docs/hcl/kgpe-d16.md | 35+++++++++++++++++++++++++++--------
docs/hcl/r400.md | 17++++++++++++++---
docs/hcl/t400.md | 19++++++++++++++++---
docs/hcl/t500.md | 26++++++++++++++++++++------
docs/hcl/x200.md | 49++++++++++++++++++++++++++++++++++++++-----------
docs/index.md | 46+++++++++++++++++++++++-----------------------
docs/install/bbb_setup.md | 93+++++++++++++++++++++++++++++++++++++++++--------------------------------------
docs/install/c201.md | 87++++++++++++++++++++++++++++++++++++++++++++-----------------------------------
docs/install/d510mo.md | 20+++++++++++++-------
docs/install/d945gclf.md | 13+++++++++----
docs/install/ga-g41m-es2l.md | 26+++++++++++++++-----------
docs/install/index.md | 105++++++++++++++++++++++++++++++++++++++++++++++++++-----------------------------
docs/install/kcma-d8.md | 10++++++++--
docs/install/kgpe-d16.md | 12++++++++++--
docs/install/r400_external.md | 167+++++++++++++++++++++++++++++++++++++------------------------------------------
docs/install/rpi_setup.md | 30++++++++++++++++--------------
docs/install/t400_external.md | 155++++++++++++++++++++++++++++++++++++++-----------------------------------------
docs/install/t500_external.md | 170+++++++++++++++++++++++++++++++++++++------------------------------------------
docs/install/t60_unbrick.md | 152+++++++++++++++++++++++++++++++------------------------------------------------
docs/install/x200_external.md | 125++++++++++++++++++++++++++++++++++++++++---------------------------------------
docs/install/x60_unbrick.md | 173+++++++++++++++++++++++++++++++------------------------------------------------
docs/install/x60tablet_unbrick.md | 86+++++++++++++++++++++++++++++++++++--------------------------------------------
docs/misc/bbb_ehci.md | 44++++++++++++++++++++++----------------------
docs/misc/index.md | 87+++++++++++++++++++++++++++++++++++++++++++++++--------------------------------
docs/misc/patch.md | 81++++++++++++++++++++++++++++++++++++++-----------------------------------------
docs/publish.sh | 10----------
docs/release.md | 27+++++++++++++++++----------
65 files changed, 2753 insertions(+), 2546 deletions(-)

diff --git a/docs/archive_old.md b/docs/archive_old.md @@ -1,10 +1,16 @@ -% Libreboot release information (old) + +Libreboot release information (old) +=================================== Information for this release can be found at [release.html](release.html). Updated versions of libreboot can be found at [libreboot.org](http://libreboot.org/). -**This page is *obsolete*, provided for historical purposes.** + +**This page is \*obsolete\*, provided for historical purposes.** + + + Releases -------- @@ -22,13 +28,15 @@ Releases - [r20131213 (2nd release)](#release20131213) (13th December 2013) - [r20131212 (1st release)](#release20131212) (12th December 2013) + + Release 20150518 {#release20150518} ================ Release date: 18th May 2015. Installation instructions can be found at ***docs/install/***. Building -instructions (for source code) can be found at ***docs/git/#build***. +instructions (for source code) can be found at ***docs/git/\#build***. Machines supported in this release: ----------------------------------- @@ -39,22 +47,22 @@ Machines supported in this release: also fit inside an X60/X60s. - **ThinkPad X60 Tablet** (1024x768 and 1400x1050) with digitizer support - - See ***docs/hcl/#supported\_x60t\_list*** for list of supported + - See ***docs/hcl/\#supported\_x60t\_list*** for list of supported LCD panels - It is unknown whether an X61 Tablet can have it's mainboard replaced with an X60 Tablet motherboard. - **ThinkPad T60** (Intel GPU) (there are issues; see below): - See notes below for exceptions, and - ***docs/hcl/#supported\_t60\_list*** for known working LCD + ***docs/hcl/\#supported\_t60\_list*** for known working LCD panels. - It is unknown whether a T61 can have it's mainboard replaced with a T60 motherboard. - - See ***docs/future/#t60\_cpu\_microcode***. + - See ***docs/future/\#t60\_cpu\_microcode***. - T60P (and T60 laptops with ATI GPU) will likely never be - supported: ***docs/hcl/#t60\_ati\_intel*** + supported: ***docs/hcl/\#t60\_ati\_intel*** - **ThinkPad X200** - X200S and X200 Tablet are also supported, conditionally; see - ***docs/hcl/x200.html#x200s*** + ***docs/hcl/x200.html\#x200s*** - **ME/AMT**: libreboot removes this, permanently. ***docs/hcl/gm45\_remove\_me.html*** - **ThinkPad R400** @@ -70,10 +78,10 @@ Machines supported in this release: - **ME/AMT**: libreboot removes this, permanently. ***docs/hcl/gm45\_remove\_me.html*** - **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) - - See ***docs/hcl/#macbook11***. + - See ***docs/hcl/\#macbook11***. - **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - - See ***docs/hcl/#macbook21***. + - See ***docs/hcl/\#macbook21***. Changes for this release, relative to r20150208 (earliest changes last, recent changes first) --------------------------------------------------------------------------------------------- @@ -94,7 +102,7 @@ Changes for this release, relative to r20150208 (earliest changes last, recent c again in the next release) - coreboot-libre: delete unused code (reduce size of src archive) - Flashing guides: make them more friendly to colourblind people -- docs/gnulinux/encrypted\_*.html: Remove mention of password +- docs/gnulinux/encrypted\_\*.html: Remove mention of password length - it was arbitrary and pointless. - docs/maintain/: Finish the guide - scripts/download/coreboot: use diffs included in libreboot, not @@ -117,7 +125,7 @@ Changes for this release, relative to r20150208 (earliest changes last, recent c - demefactory (new utility): create GM45 factory.rom without the ME - ich9deblob: re-factor descriptor.c functions - docs/hcl/t500.html: add hardware logs -- docs/gnulinux/encrypted\_*.html: No password for default entry +- docs/gnulinux/encrypted\_\*.html: No password for default entry - docs/git/: Add more details about BUC.TS - grub.cfg: Also scan for grub2/grub.cfg, not just grub/grub.cfg - docs/maintain/ (new section. WIP!): Maintaining libreboot @@ -125,7 +133,7 @@ Changes for this release, relative to r20150208 (earliest changes last, recent c - docs/tasks.html: Better categorization between intel/amd/arm - docs/install/bbb\_setup.html: notes about SPI flashing stability - docs/install/bbb\_setup.html: more names for the 0.1" cables -- docs/install/*\_external.html: add disclaimer about thermal paste +- docs/install/\*\_external.html: add disclaimer about thermal paste - docs/install/bbb\_setup.html: Fix broken links - docs/install/bbb\_setup.html: preliminary notes about EHCI debug - docs/hcl/gm45\_remove\_me.html: Link to websites talking about the @@ -156,7 +164,7 @@ Changes for this release, relative to r20150208 (earliest changes last, recent c included (merged upstream) - coreboot-libre: don't list vortex86ex kbd firmware as microcode (list it separately) -- coreboot-libre: don't rm */early\_setup\_ss.h (these are not +- coreboot-libre: don't rm \*/early\_setup\_ss.h (these are not blobs) - coreboot-libre: add GPLv3 license to the findblobs script - coreboot-libreboot: don't rm raminit\_tables (nahelem/sandybridge) @@ -247,6 +255,8 @@ Changes for this release, relative to r20150208 (earliest changes last, recent c - **New board:** ThinkPad R400 support added to libreboot. - bbb\_setup.html: tell user to use libreboot's own flashrom + + Release 20150124, 20150126 and 20150208 {#release20150124} ======================================= @@ -261,32 +271,32 @@ Machines supported in this release: also fit inside an X60/X60s. - **Lenovo ThinkPad X60 Tablet** (1024x768 and 1400x1050) with digitizer support - - See **hcl/#supported\_x60t\_list** for list of supported LCD + - See **hcl/\#supported\_x60t\_list** for list of supported LCD panels - It is unknown whether an X61 Tablet can have it's mainboard replaced with an X60 Tablet motherboard. - **Lenovo ThinkPad T60** (Intel GPU) (there are issuesinstall/x200\_external.html; see below): - See notes below for exceptions, and - **hcl/#supported\_t60\_list** for known working LCD panels. + **hcl/\#supported\_t60\_list** for known working LCD panels. - It is unknown whether a T61 can have it's mainboard replaced with a T60 motherboard. - - See **future/#t60\_cpu\_microcode**. + - See **future/\#t60\_cpu\_microcode**. - T60P (and T60 laptops with ATI GPU) will likely never be - supported: **hcl/#t60\_ati\_intel** + supported: **hcl/\#t60\_ati\_intel** - **Lenovo ThinkPad X200** - X200S and X200 Tablet are also supported, conditionally; see - **hcl/x200.html#x200s** + **hcl/x200.html\#x200s** - **ME/AMT**: libreboot removes this, permanently. **hcl/gm45\_remove\_me.html** - **Lenovo ThinkPad R400** (r20150208 and later, only) - **ME/AMT**: libreboot removes this, permanently. **hcl/gm45\_remove\_me.html** - **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) - - See **hcl/#macbook11**. + - See **hcl/\#macbook11**. - **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - - See **hcl/#macbook21**. + - See **hcl/\#macbook21**. Revisions for r20150208 (relative to r20150126) ----------------------------------------------- @@ -364,10 +374,10 @@ Changes for this release (latest changes first, earliest changes last) completely. - Enabled cstates 1 and 2 on macbook21. This reduces idle heat / power consumption. -- buildrom-withgrub: disabled creation of *txtmode*.rom for X200 +- buildrom-withgrub: disabled creation of \*txtmode\*.rom for X200 (only framebuffer graphics work) - Updated SeaBIOS (again) -- docs/install/#flashrom\_x200: improve instructions +- docs/install/\#flashrom\_x200: improve instructions - Updated flashrom (again) - patches updated - Updated GRUB (again) - Updated coreboot (again) @@ -414,8 +424,7 @@ 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) @@ -459,6 +468,8 @@ Changes for this release (latest changes first, earliest changes last) html errors - Documentation (macbook21 related): clean up + + Release 20141015 {#release20141015} ================ @@ -471,23 +482,23 @@ Machines supported in this release: also fit inside an X60/X60s. - **Lenovo ThinkPad X60 Tablet** (1024x768 and 1400x1050) with digitizer support - - See **hcl/#supported\_x60t\_list** for list of supported LCD + - See **hcl/\#supported\_x60t\_list** for list of supported LCD panels - It is unknown whether an X61 Tablet can have its mainboard replaced with an X60 Tablet motherboard. - **Lenovo ThinkPad T60** (Intel GPU) (there are issues; see below): - See notes below for exceptions, and - **hcl/#supported\_t60\_list** for known working LCD panels. + **hcl/\#supported\_t60\_list** for known working LCD panels. - It is unknown whether a T61 can have its mainboard replaced with a T60 motherboard. - - See **future/#t60\_cpu\_microcode**. + - See **future/\#t60\_cpu\_microcode**. - T60P (and T60s with ATI GPU) will likely never be supported: - **hcl/#t60\_ati\_intel** + **hcl/\#t60\_ati\_intel** - **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) - - See **hcl/#macbook11**. + - See **hcl/\#macbook11**. - **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - - See **hcl/#macbook21**. + - See **hcl/\#macbook21**. Changes for this release (latest changes first, earliest changes last) ---------------------------------------------------------------------- @@ -529,6 +540,8 @@ Changes for this release (latest changes first, earliest changes last) [Back to top of page.](#pagetop) + + 6th release (pre-release, 7th beta) {#release20140911} =================================== @@ -553,22 +566,22 @@ New systems supported in this release: - **Lenovo ThinkPad X60 Tablet** (1024x768 and 1400x1050) with digitizer support - - See **hcl/#supported\_x60t\_list** for list of supported LCD + - See **hcl/\#supported\_x60t\_list** for list of supported LCD panels - It is unknown whether an X61 Tablet can have its mainboard replaced with an X60 Tablet motherboard. - **Lenovo ThinkPad T60** (Intel GPU) (there are issues; see below) - See notes below for exceptions, and - **hcl/#supported\_t60\_list** for known working LCD panels. + **hcl/\#supported\_t60\_list** for known working LCD panels. - It is unknown whether a T61 can have its mainboard replaced with a T60 motherboard. - T60P (and T60s with ATI GPU) will likely never be supported: - **hcl/#t60\_ati\_intel** + **hcl/\#t60\_ati\_intel** - **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) - - See **hcl/#macbook11**. + - See **hcl/\#macbook11**. - **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - - See **hcl/#macbook21**. + - See **hcl/\#macbook21**. Machines no longer supported (compared to previous release): ------------------------------------------------------------ @@ -600,22 +613,21 @@ Revisions for r20140911 (7th beta) (11th September 2014) Revisions for r20140903 (6th beta) (3rd September 2014) ------------------------------------------------------- -- Added modified builddeb* scripts for Parabola GNU+Linux-libre: +- Added modified builddeb\* scripts for Parabola GNU+Linux-libre: buildpac, buildpac-flashrom, buildpac-bucts (courtesy of Noah Vesely) - Documentation: updated all relevant areas to mention use of - buildpac* scripts for Parabola users. + buildpac\* scripts for Parabola users. - Documentation: added information showing how to enable or disable bluetooth on the X60 -- MacBook1,1 tested! See **hcl/#macbook11** -- Documentation: fixed typo in #get\_edid\_panelname (get-edit +- MacBook1,1 tested! See **hcl/\#macbook11** +- Documentation: fixed typo in \#get\_edid\_panelname (get-edit changed to get-edid) - Documentation: added images/x60\_lcd\_change/ (pics only for now) - Added gcry\_serpent and gcry\_whirlpool to the GRUB module list in the 'build' script (for luks users) - **Libreboot is now based on a new coreboot version from August 23rd, - 2014: - + 2014:\ Merged commits (relates to boards that were already supported in libreboot):** - <http://review.coreboot.org/#/c/6697/> @@ -645,10 +657,10 @@ Revisions for r20140903 (6th beta) (3rd September 2014) - Updated getcb script and DEBLOB script. - Updated configuration files under resources/libreboot/config/ to accomodate new coreboot version. -- Removed grub\_serial*.cfg and libreboot\_serial*.rom, all +- Removed grub\_serial\*.cfg and libreboot\_serial\*.rom, all configs/rom files are now unified (containing same configuration as serial rom files from before). - - Documentation: updated #rom to reflect the above. + - Documentation: updated \#rom to reflect the above. - Updated GRUB to new version from August 14th, 2014. - Unified all grub configurations for all systems to a single grub.cfg under resources/grub/config/ @@ -683,19 +695,19 @@ Revisions for r20140903 (6th beta) (3rd September 2014) manifests (not needed, since release tarballs are GPG-signed) - 'build' script: removed the parts that generated libreboot\_meta directory (not needed anymore, since \_meta will be hosted in git) - - Updated #build\_meta (and other parts of documentation) to + - Updated \#build\_meta (and other parts of documentation) to accomodate this change. -- Documentation: simplified (refactored) the notes in #rom +- Documentation: simplified (refactored) the notes in \#rom - 'build' script: removed the parts that generated libreboot\_bin and added them to a new script: 'build-release' - - Documentation: #build updated to reflect the above. -- ~~Added all gcry\_* modules to grub (luks/cryptomount): + - Documentation: \#build updated to reflect the above. +- ~~Added all gcry\_\* modules to grub (luks/cryptomount): gcry\_arcfour gcry\_camellia gcry\_crc gcry\_dsa gcry\_md4 gcry\_rfc2268 gcry\_rmd160 gcry\_seed gcry\_sha1 gcry\_sha512 gcry\_twofish gcry\_blowfish gcry\_cast5 gcry\_des gcry\_idea gcry\_md5 gcry\_rijndael gcry\_rsa gcry\_serpent gcry\_sha256 gcry\_tiger gcry\_whirlpool~~ -- Added GNUtoo's list of GRUB modules (includes all of the gcry\_* +- Added GNUtoo's list of GRUB modules (includes all of the gcry\_\* modules above), cryptomount should be working now. - Removed builddeb-bucts and builddeb-flashrom, merged them with builddeb ( updated accordingly) @@ -703,7 +715,7 @@ Revisions for r20140903 (6th beta) (3rd September 2014) buildpac ( updated accordingly) - Renamed buildpac to deps-parabola ( updated accordingly) - Documentation: removed all parts talking about build dependencies, - replaced them with links to #build\_dependencies + replaced them with links to \#build\_dependencies - Documentation: emphasized more strongly on the documentation, the need to re-build bucts and/or flashrom before flashing a ROM image. - build-release: flashrom, nvramtool, cbfstool and bucts are no longer @@ -719,9 +731,9 @@ Revisions for r20140903 (6th beta) (3rd September 2014) - Removed all unused fonts from dejavu-fonts-ttf-2.34/ directory - 'buildrom-withgrub' script: updated it to create 2 sets of ROMs for each system: one with text-mode, one with coreboot framebuffer. -- Documentation: updated #rom to reflect the above +- Documentation: updated \#rom to reflect the above - Deleted unused README and COPYING file from main directory -- Removed some rm -Rf .git* instructions from the get* scripts and +- Removed some rm -Rf .git\* instructions from the get\* scripts and moved them to build-release script - Split up default grub.cfg into 6 parts: extra/{common.cfg,txtmode.cfg,vesafb.cfg} and @@ -736,13 +748,10 @@ Revisions for r20140903 (6th beta) (3rd September 2014) ohci, uhci, usb, usbserial\_pl2303, usbserial\_ftdi, usbserial\_usbdebug - set prefix=(memdisk)/boot/grub - - For native graphics (recommended by coreboot wiki): - - gfxpayload=keep - + - For native graphics (recommended by coreboot wiki):\ + gfxpayload=keep\ terminal\_output \--append gfxterm - - Play a beep on startup: - + - Play a beep on startup:\ play 480 440 1 - Documentation: updated gnulinux/grub\_cbfs.html to make it safer (and easier) to follow. @@ -780,7 +789,7 @@ Revisions for r20140811 (5th beta) (11th August 2014) - Documentation: added preliminary information about preventing/mitigating cold-boot attack in x60\_security.html and t60\_security.html -- Documentation: added info to #macbook21 warning about issues with +- Documentation: added info to \#macbook21 warning about issues with macbook21 - Documentation: X60/T60: added information about checking custom ROMs using dd to see whether or not the top 64K region is duplicated @@ -819,7 +828,7 @@ Revisions for r20140729 (4th beta) (29th July 2014) needed. Removing it reduces the size of the archive. flashrom development should be upstream. - Added ROMs with Qwerty (Italian) layout in GRUB - (libreboot*itqwerty.rom) + (libreboot\*itqwerty.rom) - Added resources/utilities/i945gpu/intel-regs.py for debugging issues related to LCD panel compatibility on X60 Tablet and T60. (courtesy of [Michał Masłowski](http://mtjm.eu)) @@ -851,7 +860,7 @@ Revisions for r20140720 (3rd beta) (20th July 2014) coreboot\_usqwerty.rom and coreboot\_serial\_usqwerty.rom - coreboot\_dvorak and coreboot\_serial\_dvorak.rom renamed to coreboot\_usdvorak.rom and coreboot\_serial\_usdvorak.rom - - Renamed coreboot*rom to libreboot*rom + - Renamed coreboot\*rom to libreboot\*rom - Made flash, lenovobios\_firstflash and lenovobios\_secondflash scripts fail if the specified file does not exist. - Updated all relevant parts of the documentation to reflect the @@ -861,11 +870,11 @@ Revisions for r20140720 (3rd beta) (20th July 2014) - Updated buildrom-withgrub to use background.jpg instead of background.png - Updated buildrom-withgrub to use gnulove.jpg aswell -- Updated resources/grub/config/macbook21/grub*cfg to use gnulove.jpg +- Updated resources/grub/config/macbook21/grub\*cfg to use gnulove.jpg background. -- Updated resources/grub/config/{x60,t60,x60t}/grub*cfg to use +- Updated resources/grub/config/{x60,t60,x60t}/grub\*cfg to use background.jpg background. -- Documentation: updated docs/#grub\_custom\_keyboard to be more +- Documentation: updated docs/\#grub\_custom\_keyboard to be more generally useful. - nvramtool: - Updated builddeps-coreboot script to build it @@ -909,17 +918,17 @@ Revisions for r20140711 (1st beta) (11th July 2014) (macbook21 does not need bucts when flashing libreboot while Apple EFI firmware is running) - Documentation: Added macbook21 ROMs to the list of ROMs in - docs/#rom + docs/\#rom - Documentation: Write documentation linking to Mono Moosbart's macbook21 and parabola page (and include a copy) - Documentation: added a copy of Mono's Parabola install guide (for macbook21 with Apple EFI firmware) and linked in in main index. - Documentation: added a copy of Mono's Coreboot page (for macbook21) and linked it in main index. -- T60: Copy CD option from the grub.cfg files for T60 *serial*.rom +- T60: Copy CD option from the grub.cfg files for T60 \*serial\*.rom images into the grub configs for non-serial images. (T60s have CD/DVD drive on main laptop) -- macbook21: remove options in build-macbook21 for *serial*.rom +- macbook21: remove options in build-macbook21 for \*serial\*.rom (there is no dock or serial port available for macbook21) - Added patches for backlight controls on X60 and T60 with help from Denis Carikli (see ./resources/libreboot/patch/gitdiff and ./getcb @@ -951,8 +960,8 @@ Revisions for r20140711 (1st beta) (11th July 2014) 'dmidecode') - Added 'build-x60t' script - Updated 'build' script to use 'build-x60t' - - Documentation: added to #config section the section - #config\_x60t (libreboot configuration and dmidecode info) + - Documentation: added to \#config section the section + \#config\_x60t (libreboot configuration and dmidecode info) - Documentation: added x60t ROMs to the list of ROMs - Tidied up the 'builddeps' script (easier to read) - Tidied up the 'cleandeps' script (easier to read) @@ -1060,7 +1069,7 @@ Revisions for r20140711 (1st beta) (11th July 2014) libreboot\_bin - Documentation: made docs/gnulinux/grub\_cbfs.html slightly easier to follow. -- Annotate the 'build*' scripts with 'echo' commands, to help the +- Annotate the 'build\*' scripts with 'echo' commands, to help the user understand what it actually happening during the build process. - Documentation: added information about how 'dmidecode' data was put in the coreboot configs @@ -1104,10 +1113,12 @@ Revisions for r20140711 (1st beta) (11th July 2014) - Deleted the RELEASE and BACKPORT files (no longer needed) - Documentation: added information about X60/T60 dock (ultrabase x6 and advanced mini dock) to relevant sections. - - Added to docs/#serial + - Added to docs/\#serial [Back to top of page.](#pagetop) + + Release 20140622 (5th release) {#release20140622} ============================== @@ -1226,6 +1237,8 @@ Development notes [Back to top of page.](#pagetop) + + Release 20140221 (4th release) {#release20140221} ============================== @@ -1256,10 +1269,12 @@ Development notes The "Parse" options read ./isolinux/isolinux.cfg on a CD or USB, and automatically converts it to a grub config and switches to the boot menu -of that distro. This makes booting ISOs *much* easier than before. +of that distro. This makes booting ISOs \*much\* easier than before. [Back to top of page.](#pagetop) + + r20131214 (3rd release) {#release20131214} ======================= @@ -1279,6 +1294,8 @@ Development notes [Back to top of page.](#pagetop) + + r20131213 (2nd release) {#release20131213} ======================= @@ -1300,6 +1317,8 @@ Development notes [Back to top of page.](#pagetop) + + r20131212 (1st release) {#release20131212} ======================= @@ -1319,8 +1338,9 @@ Development notes [Back to top of page.](#pagetop) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md @@ -1,4 +1,6 @@ -% How to install FreeBSD on a libreboot system + +How to install FreeBSD on a libreboot system +============================================ This section relates to preparing, booting and installing FreeBSD on your libreboot system, using nothing more than a USB flash drive (and @@ -26,10 +28,14 @@ with libreboot. [Back to previous index](./) + + **This section is only for the GRUB payload. For depthcharge (used on CrOS devices in libreboot), instructions have yet to be written in the libreboot documentation.** + + freebsd.img is the installation image for FreeBSD. Adapt the filename accordingly, for whatever FreeBSD version you use. @@ -55,81 +61,95 @@ 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: - - $ dmesg | tail -Check to confirm which drive it is, for example, if you think its sd3: - - $ disklabel sd3 +Connect the USB drive. Check dmesg:\ +**\$ dmesg | tail**\ +Check to confirm which drive it is, for example, if you think its sd3:\ +**\$ disklabel sd3** Check that it wasn't automatically mounted. If it was, unmount it. For -example: - - $ doas umount /dev/sd3i +example:\ +**\$ doas umount /dev/sd3i**\ dmesg told you what device it is. Overwrite the drive, writing the -FreeBSD installer to it with dd. For example: - - $ doas dd if=freebsd.img of=/dev/rsdXc bs=1M; sync +FreeBSD installer to it with dd. For example:\ +**\$ doas dd if=freebsd.img of=/dev/rsdXc bs=1M; sync**\ You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. +[Back to top of page](#pagetop). + Prepare the USB drive (in GNU+Linux) ------------------------------------ If you downloaded your ISO on a GNU+Linux system, here is how to create the bootable FreeBSD USB drive: -Connect the USB drive. Check dmesg: - - $ dmesg -Check lsblk to confirm which drive it is: - - $ lsblk +Connect the USB drive. Check dmesg:\ +**\$ dmesg**\ +Check lsblk to confirm which drive it is:\ +**\$ lsblk** Check that it wasn't automatically mounted. If it was, unmount it. For -example: - - $ sudo umount /dev/sdX* - # umount /dev/sdX* +example:\ +**\$ sudo umount /dev/sdX\***\ +**\# umount /dev/sdX\*** dmesg told you what device it is. Overwrite the drive, writing your -distro ISO to it with dd. For example: - - $ sudo dd if=freebsd.img of=/dev/sdX bs=8M; sync - # dd if=freebsd.img of=/dev/sdX bs=8M; sync +distro ISO to it with dd. For example:\ +**\$ sudo dd if=freebsd.img of=/dev/sdX bs=8M; sync**\ +**\# dd if=freebsd.img of=/dev/sdX bs=8M; sync** You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. +[Back to top of page](#pagetop). + + + Installing FreeBSD without full disk encryption ----------------------------------------------- Press C in GRUB to access the command line: -grub> kfreebsd (usb0,gpt3)/boot/kernel/kernel -grub> set FreeBSD.vfs.mountfrom=ufs:/dev/da1p3 +grub> **kfreebsd (usb0,gpt3)/boot/kernel/kernel**\ +grub> **set FreeBSD.vfs.mountfrom=ufs:/dev/da1p3**\ grub> **boot** It will start booting into the FreeBSD installer. Follow the normal process for installing FreeBSD. +[Back to top of page](#pagetop). + + + Installing FreeBSD with full disk encryption -------------------------------------------- TODO +[Back to top of page](#pagetop). + + + Booting ------- TODO +[Back to top of page](#pagetop). + + + Configuring Grub ---------------- TODO +[Back to top of page](#pagetop). + + + Troubleshooting =============== @@ -142,16 +162,18 @@ because it doesn't exist. In most cases, you should use the vesafb ROM images. Example filename: libreboot\_ukdvorak\_vesafb.rom. -won't boot...something about file not found +won't boot\...something about file not found --------------------------------------------- Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and numbers may differ. Use TAB completion. -Copyright © 2016 Leah Rowe <info@minifree.org> +[Back to top of page](#pagetop). + -Copyright © 2016 Scott Bonds <scott@ggr.com> +Copyright © 2016 Leah Rowe <info@minifree.org>\ +Copyright © 2016 Scott Bonds <scott@ggr.com>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/bsd/index.md b/docs/bsd/index.md @@ -1,9 +1,11 @@ -% BSD projects + +BSD projects +============ This section relates to dealing with BSD projects: preparing bootable USB drives, changing the default GRUB menu and so on. -**This section is only for the *GRUB* payload. For depthcharge, +**This section is only for the \*GRUB\* payload. For depthcharge, instructions have yet to be written.** [Back to previous index](../). @@ -13,8 +15,9 @@ instructions have yet to be written.** system](openbsd.html) - [How to install FreeBSD on a libreboot system](freebsd.html) -Copyright © 2016 Scott Bonds <scott@ggr.com> + +Copyright © 2016 Scott Bonds <scott@ggr.com>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/bsd/netbsd.md b/docs/bsd/netbsd.md @@ -1,4 +1,6 @@ -% How to install NetBSD on a libreboot system + +How to install NetBSD on a libreboot system +=========================================== This section relates to preparing, booting and installing NetBSD on your libreboot system, using nothing more than a USB flash drive (and *dd*). @@ -21,10 +23,14 @@ for the initial instructions. [Back to previous index](./) + + **This section is only for the GRUB payload. For depthcharge (used on CrOS devices in libreboot), instructions have yet to be written in the libreboot documentation.** + + netbsd.iso is the installation image for NetBSD. Adapt the filename accordingly, for your version of NetBSD. @@ -51,81 +57,91 @@ 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: - - $ dmesg | tail -Check to confirm which drive it is, for example, if you think its sd3: - - $ disklabel sd3 +Connect the USB drive. Check dmesg:\ +**\$ dmesg | tail**\ +Check to confirm which drive it is, for example, if you think its sd3:\ +**\$ disklabel sd3** Check that it wasn't automatically mounted. If it was, unmount it. For -example: - - $ doas umount /dev/sd3i +example:\ +**\$ doas umount /dev/sd3i**\ dmesg told you what device it is. Overwrite the drive, writing the -NetBSD installer to it with dd. For example: - - $ doas netbsd.iso of=/dev/rsdXc bs=1M; sync +NetBSD installer to it with dd. For example:\ +**\$ doas netbsd.iso of=/dev/rsdXc bs=1M; sync**\ You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. +[Back to top of page](#pagetop). + Prepare the USB drive (in GNU+Linux) ------------------------------------ If you downloaded your ISO on a GNU+Linux system, here is how to create the bootable NetBSD USB drive: -Connect the USB drive. Check dmesg: - - $ dmesg -Check lsblk to confirm which drive it is: - - $ lsblk +Connect the USB drive. Check dmesg:\ +**\$ dmesg**\ +Check lsblk to confirm which drive it is:\ +**\$ lsblk** Check that it wasn't automatically mounted. If it was, unmount it. For -example: - - $ sudo umount /dev/sdX* - # umount /dev/sdX* +example:\ +**\$ sudo umount /dev/sdX\***\ +**\# umount /dev/sdX\*** dmesg told you what device it is. Overwrite the drive, writing your -distro ISO to it with dd. For example: - - $ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync - # dd if=netbsd.iso of=/dev/sdX bs=8M; sync +distro ISO to it with dd. For example:\ +**\$ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync**\ +**\# dd if=netbsd.iso of=/dev/sdX bs=8M; sync** You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. +[Back to top of page](#pagetop). + + + Installing NetBSD without full disk encryption ---------------------------------------------- You might have to use an external USB keyboard during the installation. Press C to access the GRUB terminal. -grub> knetbsd -r sd0a (usb0,netbsd1)/netbsd +grub> **knetbsd -r sd0a (usb0,netbsd1)/netbsd**\ grub> **boot** It will start booting into the NetBSD installer. Follow the normal process for installing NetBSD. +[Back to top of page](#pagetop). + + + Installing NetBSD with full disk encryption ------------------------------------------- TODO +[Back to top of page](#pagetop). + + + Booting ------- Press C in GRUB to access the command line: -grub> knetbsd -r wd0a (ahci0,netbsd1)/netbsd +grub> **knetbsd -r wd0a (ahci0,netbsd1)/netbsd**\ grub> **boot** NetBSD will start booting. Yay! +[Back to top of page](#pagetop). + + + Configuring Grub ---------------- @@ -138,18 +154,19 @@ On your NetBSD root partition, create the **/grub** directory and add the file **libreboot\_grub.cfg** to it. Inside the **libreboot\_grub.cfg** add these lines: -**default=0 timeout=3 menuentry "NetBSD" { - -    knetbsd -r wd0a (ahci0,netbsd1)/netbsd - -} - +**default=0 timeout=3 menuentry "NetBSD" {\ +    knetbsd -r wd0a (ahci0,netbsd1)/netbsd\ +}\ ** The next time you boot, you'll see the old Grub menu for a few seconds, then you'll see the a new menu with only NetBSD on the list. After 3 seconds NetBSD will boot, or you can hit enter to boot. +[Back to top of page](#pagetop). + + + Troubleshooting =============== @@ -162,16 +179,18 @@ because it doesn't exist. In most cases, you should use the vesafb ROM images. Example filename: libreboot\_ukdvorak\_vesafb.rom. -won't boot...something about file not found +won't boot\...something about file not found --------------------------------------------- Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and numbers may differ. Use TAB completion. -Copyright © 2016 Leah Rowe <info@minifree.org> +[Back to top of page](#pagetop). + -Copyright © 2016 Scott Bonds <scott@ggr.com> +Copyright © 2016 Leah Rowe <info@minifree.org>\ +Copyright © 2016 Scott Bonds <scott@ggr.com>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md @@ -1,4 +1,6 @@ -% How to install LibertyBSD or OpenBSD on a libreboot system + +How to install LibertyBSD or OpenBSD on a libreboot system +========================================================== NOTE: This guide was written for OpenBSD by the person who contributed it, but the libreboot project recommends LibertyBSD. LibertyBSD is a @@ -20,10 +22,14 @@ your libreboot system, using nothing more than a USB flash drive (and [Back to previous index](./) + + **This section is only for the GRUB payload. For depthcharge (used on CrOS devices in libreboot), instructions have yet to be written in the libreboot documentation.** + + install60.fs is the installation image for OpenBSD 6.0. Adapt the filename accordingly, for a different OpenBSD version or LibertyBSD. @@ -33,26 +39,24 @@ 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: - - $ dmesg | tail -Check to confirm which drive it is, for example, if you think its sd3: - - $ disklabel sd3 +Connect the USB drive. Check dmesg:\ +**\$ dmesg | tail**\ +Check to confirm which drive it is, for example, if you think its sd3:\ +**\$ disklabel sd3** Check that it wasn't automatically mounted. If it was, unmount it. For -example: - - $ doas umount /dev/sd3i +example:\ +**\$ doas umount /dev/sd3i**\ dmesg told you what device it is. Overwrite the drive, writing the -OpenBSD installer to it with dd. For example: - - $ doas dd if=install60.fs of=/dev/rsdXc bs=1M; sync +OpenBSD installer to it with dd. For example:\ +**\$ doas dd if=install60.fs of=/dev/rsdXc bs=1M; sync**\ You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. +[Back to top of page](#pagetop). + Prepare the USB drive (in NetBSD) --------------------------------- @@ -76,39 +80,43 @@ Prepare the USB drive (in GNU+Linux) If you downloaded your ISO on a GNU+Linux system, here is how to create the bootable OpenBSD USB drive: -Connect the USB drive. Check dmesg: - - $ dmesg -Check lsblk to confirm which drive it is: - - $ lsblk +Connect the USB drive. Check dmesg:\ +**\$ dmesg**\ +Check lsblk to confirm which drive it is:\ +**\$ lsblk** Check that it wasn't automatically mounted. If it was, unmount it. For -example: - - $ sudo umount /dev/sdX* - # umount /dev/sdX* +example:\ +**\$ sudo umount /dev/sdX\***\ +**\# umount /dev/sdX\*** dmesg told you what device it is. Overwrite the drive, writing your -distro ISO to it with dd. For example: - - $ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync - # dd if=install60.fs of=/dev/sdX bs=8M; sync +distro ISO to it with dd. For example:\ +**\$ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync**\ +**\# dd if=install60.fs of=/dev/sdX bs=8M; sync** You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. +[Back to top of page](#pagetop). + + + Installing OpenBSD without full disk encryption ----------------------------------------------- Press C in GRUB to access the command line: -grub> kopenbsd (usb0,openbsd1)/6.0/amd64/bsd.rd +grub> **kopenbsd (usb0,openbsd1)/6.0/amd64/bsd.rd**\ grub> **boot** It will start booting into the OpenBSD installer. Follow the normal process for installing OpenBSD. +[Back to top of page](#pagetop). + + + Installing OpenBSD with full disk encryption -------------------------------------------- @@ -137,16 +145,24 @@ installations would be possible, but probably not feasible; it's an alien codebase to the OpenBSD project, not tightly integrated and the OpenBSD bootloader already works. +[Back to top of page](#pagetop). + + + Booting ------- Press C in GRUB to access the command line: -grub> kopenbsd -r sd0a (ahci0,openbsd1)/bsd +grub> **kopenbsd -r sd0a (ahci0,openbsd1)/bsd**\ grub> **boot** OpenBSD will start booting. Yay! +[Back to top of page](#pagetop). + + + Configuring Grub ---------------- @@ -159,18 +175,19 @@ On your OpenBSD root partition, create the **/grub** directory and add the file **libreboot\_grub.cfg** to it. Inside the **libreboot\_grub.cfg** add these lines: -**default=0 timeout=3 menuentry "OpenBSD" { - -    kopenbsd -r sd0a (ahci0,openbsd1)/bsd - -} - +**default=0 timeout=3 menuentry "OpenBSD" {\ +    kopenbsd -r sd0a (ahci0,openbsd1)/bsd\ +}\ ** The next time you boot, you'll see the old Grub menu for a few seconds, then you'll see the a new menu with only OpenBSD on the list. After 3 seconds OpenBSD will boot, or you can hit enter to boot. +[Back to top of page](#pagetop). + + + Troubleshooting =============== @@ -183,16 +200,18 @@ because it doesn't exist. In most cases, you should use the vesafb ROM images. Example filename: libreboot\_ukdvorak\_vesafb.rom. -won't boot...something about file not found +won't boot\...something about file not found --------------------------------------------- Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and numbers may differ. Use TAB completion. -Copyright © 2016 Scott Bonds <scott@ggr.com> +[Back to top of page](#pagetop). + -Copyright © 2016 Leah Rowe <info@minifree.org> +Copyright © 2016 Scott Bonds <scott@ggr.com>\ +Copyright © 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/depthcharge/index.md b/docs/depthcharge/index.md @@ -1,7 +1,10 @@ -% Depthcharge payload + +Depthcharge payload +=================== This section relates to the depthcharge payload used in libreboot. + - [CrOS security model](#cros_security_model) - [Developer mode screen](#developer_mode_screen) - Holding the developer mode screen @@ -15,6 +18,8 @@ This section relates to the depthcharge payload used in libreboot. - [Configuring verified boot parameters](#configuring_verified_boot_parameters) + + CrOS security model {#cros_security_model} =================== @@ -24,17 +29,20 @@ compromised, that is implemented as the verified boot (vboot) reference, most of which is executed within depthcharge. A detailed overview of the CrOS security model is available on the dedicated page. + In spite of the CrOS security model, depthcharge won't allow booting kernels without verifying their signature and booting from external media or legacy payload unless explicitly allowed: see [configuring verified boot parameters](#configuring_verified_boot_parameters). + + + Developer mode screen {#developer_mode_screen} ===================== The developer mode screen can be accessed in depthcharge when developer -mode is enabled. - +mode is enabled.\ Developer mode can be enabled from the [recovery mode screen](#recovery_mode_screen). @@ -43,6 +51,7 @@ external media (when enabled), booting from legacy payload (when enabled), showing information about the device and disabling developer mode. + Holding the developer mode screen {#holding_developer_mode_screen} --------------------------------- @@ -50,23 +59,25 @@ As instructed on the developer mode screen, the screen can be held by pressing **Ctrl + H** in the first 3 seconds after the screen is shown. After that delay, depthcharge will resume booting normally. + + Booting normally {#booting_normally} ---------------- As instructed on the developer mode screen, a regular boot will happen -after **3 seconds** (if developer mode screen is not held). - +after **3 seconds** (if developer mode screen is not held).\ The default boot medium (internal storage, external media, legacy payload) is shown on screen. + + Booting from different mediums {#booting_different_mediums} ------------------------------ Depthcharge allows booting from different mediums, when they are allowed (see [configuring verified boot parameters](#configuring_verified_boot_parameters) to enable or disable -boot mediums). - +boot mediums).\ As instructed on the developer mode screen, booting from various mediums can be triggered by pressing various key combinations: @@ -74,14 +85,17 @@ can be triggered by pressing various key combinations: - External media: **Ctrl + U** (when enabled) - Legacy payload: **Ctrl + L** (when enabled) + + Showing device information {#showing_device_information} -------------------------- As instructed on the developer mode screen, showing device information -can be triggered by pressing **Ctrl + I** or **Tab**. - +can be triggered by pressing **Ctrl + I** or **Tab**.\ Various information is shown, including vboot non-volatile data, TPM -status, GBB flags and key hashes. +status, GBB flags and key hashes.\ + + Warnings -------- @@ -92,6 +106,9 @@ The developer mode screen will show warnings when: - Booting from external media is enabled - Booting legacy payloads is enabled + + + Recovery mode screen {#recovery_mode_screen} ==================== @@ -102,27 +119,25 @@ It allows recovering the device from a bad state by booting from a trusted recovery media. When accessed with the device in a good state, it also allows enabling developer mode. + Recovering from a bad state {#recovering_bad_state} --------------------------- When the device fails to verify the signature of a piece of the boot software or when an error occurs, it is considered to be in a bad state -and will instruct the user to reboot to recovery mode. - +and will instruct the user to reboot to recovery mode.\ Recovery mode boots using only software located in write-protected memory, that is considered to be trusted and safe. Recovery mode then allows recovering the device by booting from a trusted recovery media, that is automatically detected when recovery mode starts. When no external media is found or when the recovery media -is invalid, instructions are shown on screen. - +is invalid, instructions are shown on screen.\ Trusted recovery media are external media (USB drives, SD cards, etc) that hold a kernel signed with the recovery key. Google provides images of such recovery media for Chrome OS (which are -not advised to users as they contain proprietary software). - +not advised to users as they contain proprietary software).\ They are signed with Google's recovery keys, that are pre-installed on the device when it ships. @@ -131,22 +146,25 @@ replaced. When the recovery private key is available (e.g. when using self-generated keys), it can be used to sign a kernel for recovery purposes. + + Enabling developer mode {#enabling_developer_mode} ----------------------- As instructed on the recovery mode screen, developer mode can be enabled -by pressing **Ctrl + D**. - +by pressing **Ctrl + D**.\ Instructions to confirm enabling developer mode are then shown on screen. + + + Configuring verified boot parameters {#configuring_verified_boot_parameters} ==================================== Depthcharge's behavior relies on the verified boot (vboot) reference implementation, that can be configured with parameters stored in the -verified boot non-volatile storage. - +verified boot non-volatile storage.\ These parameters can be modified with the **crossystem** tool, that requires sufficient privileges to access the verified boot non-volatile storage. @@ -156,8 +174,7 @@ boot non-volatile storage on some devices. **crossystem** and **mosys** are both free software and their source code is made available by Google: [crossystem](https://chromium.googlesource.com/chromiumos/platform/vboot_reference/). -[mosys](https://chromium.googlesource.com/chromiumos/platform/mosys/). - +[mosys](https://chromium.googlesource.com/chromiumos/platform/mosys/).\ These tools are not distributed along with Libreboot yet. However, they are preinstalled on the device, with ChromeOS. @@ -166,42 +183,36 @@ of the device**. In particular, disabling kernels signature verification, external media boot and legacy payload boot can weaken the security of the device. + The following parameters can be configured: - Kernels signature verification: - - Enabled with: - - # **crossystem dev\_boot\_signed\_only=1** - - Disabled with: - - # **crossystem dev\_boot\_signed\_only=0** + - Enabled with:\ + \# **crossystem dev\_boot\_signed\_only=1** + - Disabled with:\ + \# **crossystem dev\_boot\_signed\_only=0** - External media boot: - - Enabled with: - - # **crossystem dev\_boot\_usb=1** - - Disabled with: - - # **crossystem dev\_boot\_usb=0** + - Enabled with:\ + \# **crossystem dev\_boot\_usb=1** + - Disabled with:\ + \# **crossystem dev\_boot\_usb=0** - Legacy payload boot: - - Enabled with: - - # **crossystem dev\_boot\_legacy=1** - - Disabled with: - - # **crossystem dev\_boot\_legacy=0** + - Enabled with:\ + \# **crossystem dev\_boot\_legacy=1** + - Disabled with:\ + \# **crossystem dev\_boot\_legacy=0** - Default boot medium: - - Internal storage: - - # **crossystem dev\_default\_boot=disk** - - External media: + - Internal storage:\ + \# **crossystem dev\_default\_boot=disk** + - External media:\ + \# **crossystem dev\_default\_boot=usb** + - Legacy payload:\ + \# **crossystem dev\_default\_boot=legacy** - # **crossystem dev\_default\_boot=usb** - - Legacy payload: - # **crossystem dev\_default\_boot=legacy** -Copyright © 2015 Paul Kocialkowski <contact@paulk.fr> +Copyright © 2015 Paul Kocialkowski <contact@paulk.fr>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/distros/index.md b/docs/distros/index.md @@ -1,39 +1,47 @@ -% List of recommended GNU+Linux distributions for libreboot -Any distribution should work, so long as it uses kernel mode setting for -graphics. We recommend using distributions that are entirely free software; -most distros out there have proprietary software in them, but the ones that we -recommend do not have proprietary software by default. +List of recommended GNU+Linux distributions for libreboot +========================================================= -Note: we are not the Free Software Foundation. The recommendations here consist -of both FSF-endorsed and non-FSF-endorsed distros. Some of these distributions -wrongly call the whole system *Linux*. Despite libreboot's [stance against the -GNU project](../../gnu/), we still agree with the free software philosophy and -we still want you to call the whole system *GNU+Linux*, since this is the -technically correct name for the system. +Any distribution should work, so long as it uses kernel mode setting for +graphics. We recommend using distributions that are entirely free +software; most distros out there have proprietary software in them, but +the ones that we recommend do not have proprietary software by default. + +Note: we are not the Free Software Foundation. The recommendations here +consist of both FSF-endorsed and non-FSF-endorsed distros. Some of these +distributions wrongly call the whole system *Linux*. Despite +libreboot's [stance against the GNU project](../../gnu/), we still +agree with the free software philosophy and we still want you to call +the whole system *GNU+Linux*, since this is the technically correct name +for the system. FSF-endorsed distros -------------------- -Many FSF-endorsed GNU+Linux distributions are considered unfit for general use -by the libreboot project. You can read about their problems here: - -[Why we can't endorse many FSF-endorsed distributions](../fsf-distros/). +Many FSF-endorsed GNU+Linux distributions are considered unfit for +general use by the libreboot project. You can read about their problems +here:\ +[Why we can't endorse many FSF-endorsed +distributions](../fsf-distros/). [How to install GNU+Linux on a libreboot system](../gnulinux/grub_boot_installer.html) + + + Debian ------ Most of the developers use it (Leah Rowe always uses testing releases of -Debian). We recommend Debian stable releases for most users. If you want to do -development, e.g. libreboot development, then you should use the testing -release of Debian. +Debian). We recommend Debian stable releases for most users. If you want +to do development, e.g. libreboot development, then you should use the +testing release of Debian. -Debian by default comes without non-free software in the default installation -or repos. There is a non-free repo that's not added by default. Just avoid -adding this, and you should have a fully free system. +Debian by default comes without non-free software in the default +installation or repos. There is a non-free repo that's not added by +default. Just avoid adding this, and you should have a fully free +system. [Visit the Debian website](https://www.debian.org/) @@ -42,8 +50,8 @@ We recommend using the *MATE* desktop. Devuan ------ -Devuan is a fork of Debian that does not use the controversial *systemd* init -system. +Devuan is a fork of Debian that does not use the controversial *systemd* +init system. See: <https://www.devuan.org/os/init-freedom/>. @@ -55,15 +63,15 @@ Qubes ----- Security-focussed distribution. It makes heavy use of IOMMU and hardware -virtualization to separate running applications, along with other security -features. Provides a full hypervisor for running applications. +virtualization to separate running applications, along with other +security features. Provides a full hypervisor for running applications. Also heavily in favour of adoption of both Libreboot and Coreboot. -**Of all available Libreboot systems, Qubes is currently only known to be -compatible with the ASUS KGPE-D16 and KCMA-D8, due to the hardware -virtualization requirement (and even on those boards, only certain CPUs have -fully functional virtualization in Libreboot).** +**Of all available Libreboot systems, Qubes is currently only known to +be compatible with the ASUS KGPE-D16 and KCMA-D8, due to the hardware +virtualization requirement (and even on those boards, only certain CPUs +have fully functional virtualization in Libreboot).** [Visit the Qubes website](https://www.qubes-os.org/) @@ -71,16 +79,17 @@ Dragora ------- Fully free distribution, with a focus on simple package management and -configuration. Experienced users might like this distro. It also has native -support for multiple languages. +configuration. Experienced users might like this distro. It also has +native support for multiple languages. [Visit the Dragora website](https://dragora.org/) Parabola -------- -Fully free bleeding edge distribution, based on the *Arch* distribution. Good -for saavy users and developers in general (some libreboot developers use this). +Fully free bleeding edge distribution, based on the *Arch* distribution. +Good for saavy users and developers in general (some libreboot +developers use this). Arch users, refer to the [Parabola migration guide](https://wiki.parabola.nu/Migration_from_the_GNU+Linux_distribution_of_Arch). @@ -89,36 +98,39 @@ guide](https://wiki.parabola.nu/Migration_from_the_GNU+Linux_distribution_of_Arc We recommend using the *MATE* desktop. -Copyright © 2016 Leah Rowe <info@minifree.org> -Permission is granted to copy, distribute and/or modify this document under the -terms of the Creative Commons Attribution-ShareAlike 4.0 International license -or any later version published by Creative Commons; A copy of the license can -be found at [../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Copyright © 2016 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) Updated versions of the license (when available) can be found at <https://creativecommons.org/licenses/by-sa/4.0/legalcode> -UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT POSSIBLE, -THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND AS-AVAILABLE, AND MAKES NO -REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE LICENSED MATERIAL, -WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT -LIMITATION, WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR -PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE -PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE -DISCLAIMERS OF WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER -MAY NOT APPLY TO YOU. - -TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU ON ANY -LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR OTHERWISE FOR ANY -DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR -OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR -USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF -LIABILITY IS NOT ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO -YOU. - -The disclaimer of warranties and limitation of liability provided above shall -be interpreted in a manner that, to the extent possible, most closely -approximates an absolute disclaimer and waiver of all liability. +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. diff --git a/docs/fsf-distros/index.md b/docs/fsf-distros/index.md @@ -1,4 +1,6 @@ -% Explaining Why We Don't Endorse FSF-endorsed Systems + +Explaining Why We Don't Endorse FSF-endorsed Systems +===================================================== We are asked why we don't endorse most FSF-endorsed distributions, usually well-known within the FSF community. @@ -7,6 +9,9 @@ To learn more about the GNU+Linux systems that we do endorse, check out our list of [free GNU+Linux distributions](../distros/). The *only* FSF-endorsed distribution that we endorse there is *Parabola*. + + + Blag ---- @@ -66,8 +71,11 @@ Ututo It's a dead project. -Copyright © 2016 Leah Rowe <info@minifree.org> +[Back to top of page](#pagetop) + + +Copyright © 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/future/index.md b/docs/future/index.md @@ -1,10 +1,14 @@ -% Development notes + +Development notes +================= These are development notes, for future use. For old (obselete) notes, see [old.html](old.html). Or go [back to main task list](../tasks.html). + + Table of contents ================= @@ -17,6 +21,8 @@ Table of contents - [IntelVbtTool results](#intelvbttool_results) - [Fallback patches for i945](#fallback_patches) + + standard test {#standard_test} ============= @@ -41,6 +47,8 @@ on i945 (X60 and T60). [Back to top of page.](#pagetop) + + T60 cpu microcode {#t60_cpu_microcode} ================= @@ -57,73 +65,56 @@ Every other T7200 tested so far has worked without microcode updates. [Back to top of page.](#pagetop) + + i945 VRAM size {#i945_vram_size} ============== Apparently, only 8MB VRAM is available on i945 GPUs (though it could do -64MB): - +64MB):\ phcoder: No. Hardware default is 8 MiB. When I wanted to make it configurable, I saw that docs mention only one other alternative: 1MiB. Later isn't event enough for 1024x768 at 24bpp without any acceleration or double buffering. It's possible that there are undocumented values. Which options do you have in vendor BIOS? How to find out how much vram -you have: - -phcoder: TOM - BSM - -phcoder: check what vendor BIOS offers as options - -vimuser: I thought it could do 64MB usually - -phcoder: not accorging to doc. - -phcoder: see mobile-945-express-chipset-datasheet page 93 - +you have:\ +phcoder: TOM - BSM\ +phcoder: check what vendor BIOS offers as options\ +vimuser: I thought it could do 64MB usually\ +phcoder: not accorging to doc.\ +phcoder: see mobile-945-express-chipset-datasheet page 93\ phcoder: see also -src/northbridge/intel/i945/{early\_init,northbridge,gma}.c - -vimuser: "011 = DVMT (UMA) mode, 8 MB of memory pre-allocated for - -vimuser: frame buffer." - -vimuser: "Others - reserved" - +src/northbridge/intel/i945/{early\_init,northbridge,gma}.c\ +vimuser: "011 = DVMT (UMA) mode, 8 MB of memory pre-allocated for\ +vimuser: frame buffer."\ +vimuser: "Others - reserved"\ phcoder: the easiest way is a loop at this position which tries -different values and reads (and prints) BSM with them - +different values and reads (and prints) BSM with them\ stefanct: vimuser: they suggest that you change the value and look how -BSM reacts to that - -stefanct: as they pointed out earlier vram size = TOM - BSM - -stefanct: different values of GMS - -stefanct: phcoder: hm... this could be a hint. look at the text -description of TOLUD at page 103 - -stefanct: it mentions 64 MB in the text about BSM as well - -stefanct: table 18... - +BSM reacts to that\ +stefanct: as they pointed out earlier vram size = TOM - BSM\ +stefanct: different values of GMS\ +stefanct: phcoder: hm\... this could be a hint. look at the text +description of TOLUD at page 103\ +stefanct: it mentions 64 MB in the text about BSM as well\ +stefanct: table 18\...\ phcoder: stefanct: I have a guess which value make is 64 but I will not -tell to avoid skewing test results - -stefanct: phcoder: sure... i assumed you were not sure if it supports -it at all. testing it properly is of course a good idea :) - +tell to avoid skewing test results\ +stefanct: phcoder: sure\... i assumed you were not sure if it supports +it at all. testing it properly is of course a good idea :)\ stefanct: test the various possible (but reserved) values of GMS and see -what the resulting VRAM size is - +what the resulting VRAM size is\ vimuser: so, TOM - BSM [Back to top of page.](#pagetop) + + LCD panels on i945 - fix incompatible panels {#lcd_i945_incompatibility} ============================================ Fix T60 issues (see incompatible panels listed at -[../hcl/#supported\_t60\_list](../hcl/#supported_t60_list)). +[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list)). Run that tool (resources/utilities/i945gpu/intel-regs.py) as root on systems with the offending panels in: @@ -155,8 +146,7 @@ Original getregs.py script can be found at <http://hg.mtjm.eu/scripts/file/tip/intel-regs.py> written by Michał Masłowski. -About fixing remaining LCD panels on 5345: - +About fixing remaining LCD panels on 5345:\ 'polarity' is mentioned in coreboot log (cbmem -c). compare output (with working and non-working panel). (and see the other notes in docs/future/) @@ -170,14 +160,12 @@ working and nonworking panels. How to dump EDID: - # apt-get install i2c-tools - # modprobe i2c-dev -Find out the correct ID to use: - - # i2cdetect -l -Example: - -# **i2cdump -y 2 0x50** +\# **apt-get install i2c-tools**\ +\# **modprobe i2c-dev**\ +Find out the correct ID to use:\ +\# **i2cdetect -l**\ +Example:\ +\# **i2cdump -y 2 0x50** Working panel: EDID dump from LG-Philips LP150E05-A2K1: @@ -245,6 +233,8 @@ LTN141XA-L01: revert to libreboot git commit c943281 to see this [Back to top of page.](#pagetop) + + i945 gfx: X60/T60 VBT implementation (experimental: testing) {#i945_vbt} ============================================================ @@ -270,42 +260,46 @@ You are supposed to: With each boot, make notes about what you see and get logs using the [standard test](#standard_test). You will need the files from -[#intelvbttool\_results](#intelvbttool_results) for each system. +[\#intelvbttool\_results](#intelvbttool_results) for each system. -Results (# means untested): +Results (\# means untested): - **X60/X60s:** - - TMD-Toshiba LTD121ECHB: # - - CMO N121X5-L06: # - - Samsung LTN121XJ-L07: # - - BOE-Hydis HT121X01-101: # + - TMD-Toshiba LTD121ECHB: \# + - CMO N121X5-L06: \# + - Samsung LTN121XJ-L07: \# + - BOE-Hydis HT121X01-101: \# - **X60T XGA:** - - BOE-Hydis HV121X03-100: # + - BOE-Hydis HV121X03-100: \# - **X60T SXGA+:** - - BOE-Hydis HV121P01-100: # + - BOE-Hydis HV121P01-100: \# - **T60 14" XGA:** - - Samsung LTN141XA-L01: # - - CMO N141XC: # - - BOE-Hydis HT14X14: # - - TMD-Toshiba LTD141ECMB: # + - Samsung LTN141XA-L01: \# + - CMO N141XC: \# + - BOE-Hydis HT14X14: \# + - TMD-Toshiba LTD141ECMB: \# - **T60 14" SXGA+** - - TMD-Toshiba LTD141EN9B: # - - Samsung LTN141P4-L02: # - - Boe-Hydis HT14P12: # + - TMD-Toshiba LTD141EN9B: \# + - Samsung LTN141P4-L02: \# + - Boe-Hydis HT14P12: \# - **T60 15" XGA** - - Samsung LTN150XG-L08: # - - LG-Philips LP150X09: # - - 13N7068 (IDtech): # - - 13N7069 (CMO): # + - Samsung LTN150XG-L08: \# + - LG-Philips LP150X09: \# + - 13N7068 (IDtech): \# + - 13N7069 (CMO): \# - **T60 15" SXGA+** - - LG-Philips LP150E05-A2K1: # - - BOE-Hydis HV150P01-100: # + - LG-Philips LP150E05-A2K1: \# + - BOE-Hydis HV150P01-100: \# - **T60 15" UXGA** - - BOE-Hydis HV150UX1-100: # - - IDTech N150U3-L01: # - - BOE-Hydis HV150UX1-102: # + - BOE-Hydis HV150UX1-100: \# + - IDTech N150U3-L01: \# + - BOE-Hydis HV150UX1-102: \# - **T50 15" QXGA** - - IDtech IAQX10N: # - - IDtech IAQX10S: # + - IDtech IAQX10N: \# + - IDtech IAQX10S: \# + +[Back to top of page](#pagetop) + + intelvbttool test results (VGA ROM dumps) {#intelvbttool_results} ========================================= @@ -331,56 +325,56 @@ Get intelvbttool here: <http://review.coreboot.org/#/c/5842> (util/intelvbttool). Now dump a copy of the running VGA BIOS: **\$ sudo dd if=/dev/mem bs=64k -of=runningvga.bin skip=12 count=1** - -Then do (and record the output): - - $ ./intelvbttool runningvga.bin > intelvbttool\_out +of=runningvga.bin skip=12 count=1**\ +Then do (and record the output):\ +**\$ ./intelvbttool runningvga.bin > intelvbttool\_out** Backup both files (runningvga.bin and intelvbttool\_out), renaming them to match the system and LCD panel used. -[../misc/#get\_edid\_panelname](../misc/#get_edid_panelname) will show +[../misc/\#get\_edid\_panelname](../misc/#get_edid_panelname) will show you how to get the name (model) of the LCD panel used. -Test results (# means untested and all had docks, unless noted). +Test results (\# means untested and all had docks, unless noted). ----------------------------------------------------------------- - **X60/X60s:** - - TMD-Toshiba LTD121ECHB: # - - CMO N121X5-L06: # - - Samsung LTN121XJ-L07: # - - BOE-Hydis HT121X01-101: # + - TMD-Toshiba LTD121ECHB: \# + - CMO N121X5-L06: \# + - Samsung LTN121XJ-L07: \# + - BOE-Hydis HT121X01-101: \# - **X60T XGA (1024x768):** - - BOE-Hydis HV121X03-100: # + - BOE-Hydis HV121X03-100: \# - **X60T SXGA+ (1400x1050):** - - BOE-Hydis HV121P01-100: # + - BOE-Hydis HV121P01-100: \# - **T60 14" XGA (1024x768):** - - Samsung LTN141XA-L01: # - - CMO N141XC: # - - BOE-Hydis HT14X14: # - - TMD-Toshiba LTD141ECMB: # + - Samsung LTN141XA-L01: \# + - CMO N141XC: \# + - BOE-Hydis HT14X14: \# + - TMD-Toshiba LTD141ECMB: \# - **T60 14" SXGA+ (1400x1050):** - - TMD-Toshiba LTD141EN9B: # - - Samsung LTN141P4-L02: # - - Boe-Hydis HT14P12: # + - TMD-Toshiba LTD141EN9B: \# + - Samsung LTN141P4-L02: \# + - Boe-Hydis HT14P12: \# - **T60 15" XGA (1024x768):** - - Samsung LTN150XG-L08: # - - LG-Philips LP150X09: # - - 13N7068 (IDtech): # - - 13N7069 (CMO): # + - Samsung LTN150XG-L08: \# + - LG-Philips LP150X09: \# + - 13N7068 (IDtech): \# + - 13N7069 (CMO): \# - **T60 15" SXGA+ (1400x1050):** - - LG-Philips LP150E05-A2K1: # - - BOE-Hydis HV150P01-100: # + - LG-Philips LP150E05-A2K1: \# + - BOE-Hydis HV150P01-100: \# - **T60 15" UXGA (1600x1200):** - - BOE-Hydis HV150UX1-100: # - - IDTech N150U3-L01: # - - BOE-Hydis HV150UX1-102: # + - BOE-Hydis HV150UX1-100: \# + - IDTech N150U3-L01: \# + - BOE-Hydis HV150UX1-102: \# - **T60 15" QXGA (2048x1536):** - - IDtech IAQX10N: # - - IDtech IAQX10S: # + - IDtech IAQX10N: \# + - IDtech IAQX10S: \# [Back to top of page.](#pagetop) + + Fallback patches {#fallback_patches} ================ @@ -390,6 +384,8 @@ Fallback patches {#fallback_patches} [Back to top of page.](#pagetop) + + Other - unlisted (low priority) {#other} =============================== @@ -409,8 +405,9 @@ Other - unlisted (low priority) {#other} [Back to top of page.](#pagetop) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/future/old.md b/docs/future/old.md @@ -1,10 +1,14 @@ -% Development notes (old/obsolete notes) + +Development notes (old/obsolete notes) +====================================== For current notes, see [](./). These are old (obsolete) notes that mare kept because they might become useful again in the future. + + Table of contents ================= @@ -17,13 +21,15 @@ Table of contents - [i945/x60: coreboot 5927 testing (3D fix for kernel 3.12+ on replay code)](#x60_cb5927_testing) + + X60 native graphics initialization (with backlight controls) {#x60_native_notes} ============================================================ **This is now obsolete. A better way was found (included in libreboot): <http://review.coreboot.org/#/c/6731/>** -***Also check [#5320\_kernel312fix](#5320_kernel312fix) (to fix 3D on +***Also check [\#5320\_kernel312fix](#5320_kernel312fix) (to fix 3D on kernel 3.12/higher)*** **The fix below was done on 5320/6 (from review.coreboot.org) but should @@ -39,15 +45,14 @@ 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: - - # devmem2 0xe4361254 w +running the VBIOS:\ +**\# devmem2 0xe4361254 w** The change is also included in libreboot 6. When doing this, it gave back that value. The same trick was used to get backlight controls for T60 (see -[#t60\_native\_notes](#t60_native_notes)). +[\#t60\_native\_notes](#t60_native_notes)). Further notes ------------- @@ -86,19 +91,23 @@ to calculate it without hardcoded laptop-specific values. Therefore, I am supposed to find out the 'display core frequency' (mtjm says there might be a register for it; also, it might be in 5320 or the replay code) and the PWM modulation frequency. -https://en.wikipedia.org/wiki/Backlight#Flicker\_due\_to\_backlight\_dimming +https://en.wikipedia.org/wiki/Backlight\#Flicker\_due\_to\_backlight\_dimming phcoder (Vladimir Serbinenko) who is author of 5320 (review.coreboot.org) talks about 'duty cycle limit' and 'flickering frequency'. +[Back to top of page](#pagetop) + + + T60 native graphics initialization (with backlight controls) {#t60_native_notes} ============================================================ **This is now obsolete. A better way was found (included in libreboot): <http://review.coreboot.org/#/c/6731/>** -***Also check [#5320\_kernel312fix](#5320_kernel312fix) (to fix 3D on +***Also check [\#5320\_kernel312fix](#5320_kernel312fix) (to fix 3D on kernel 3.12/higher)*** **The fix below was done on an earlier version of 5345 changeset @@ -109,15 +118,19 @@ included in libreboot 6** change **gpu\_backlight** to **0x58BF58BE** Hold on! Check -[../misc/#get\_edid\_panelname](../misc/#get_edid_panelname) to know +[../misc/\#get\_edid\_panelname](../misc/#get_edid_panelname) to know what LCD panel you have. This is important for the next step! Supported panels ---------------- -[../hcl/#supported\_t60\_list](../hcl/#supported_t60_list). +[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list). + +See [\#lcd\_i945\_incompatibility](./#lcd_i945_incompatibility). + +[Back to top of page](#pagetop) + -See [#lcd\_i945\_incompatibility](./#lcd_i945_incompatibility). i945: 3D fix (based on 5927) for kernel 3.12+ on 5320 {#5320_kernel312fix} ===================================================== @@ -133,7 +146,7 @@ is also now included in libreboot 6 (using the proper way, not the now obsolete. This needs to be re-done for the latest version of 5320. The fix below is (in practise) only for reference, therefore.** -See [#x60\_cb5927\_testing](#x60_cb5927_testing) for the original (and +See [\#x60\_cb5927\_testing](#x60_cb5927_testing) for the original (and current) fix, for the replay code. Now we want to implement that on top of <http://review.coreboot.org/#/c/5320> which is the current code for native graphics initialization on i945. @@ -160,6 +173,10 @@ apt-get repositories) using tool "intel\_gtt": - with coreboot (no vbios or native init): <http://paste.debian.net/104341> +[Back to top of page](#pagetop) + + + i945/X60: Coreboot 5927 testing (3D fix for kernel 3.12+ on replay code) {#x60_cb5927_testing} ======================================================================== @@ -186,10 +203,8 @@ For historical purposes, here is a collection of IRC logs that once existed on this page, related to the issue: [kernel312\_irc](dumps/kernel312_irc). -PGETBL\_CTL differs between VBIOS (-) and native graphics init (+). - -- PGETBL\_CTL: 0x3ffc0001 - +PGETBL\_CTL differs between VBIOS (-) and native graphics init (+).\ +- PGETBL\_CTL: 0x3ffc0001\ + PGETBL\_CTL: 0x3f800001 GTT (graphics translation table) size is PGETBL\_save, max 256 KiB. BSM @@ -210,8 +225,11 @@ GTT (graphics translation table) size is PGETBL\_save, max 256 KiB. BSM - [/sys/class/drm/card0/error](dumps/5927_crashdump) - [.config](dumps/5927_config) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> +[Back to top of page](#pagetop) + + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/git/index.md b/docs/git/index.md @@ -3,12 +3,15 @@ Depthcharge is currently not documented, since it is in the new build system. Instructions for how to build boards that have depthcharge are included in the BUILD\_HOWTO file in libreboot.git or \_src. + + Building libreboot from source ============================== This section relates to building libreboot from source, and working with the git repository. + - [Install build dependencies](#build_dependencies) - [Get the full source code from metadata (git clone)](#build_meta) - [How to build "bucts" (for LenovoBIOS @@ -16,6 +19,8 @@ the git repository. - [How to build "flashrom"](#build_flashrom) - [How to build the ROM images](#build) + + Install build dependencies {#build_dependencies} ========================== @@ -25,21 +30,24 @@ libreboot\_src.tar.xz or git. **If you are using libreboot\_util.tar.xz (binary archive) then you can ignore this, because ROM images and statically compiled executables for the utilities are included.** -For Debian Stretch (may also work on Debian Jessie), you can run the -following command: - $ sudo ./oldbuild dependencies debian +For Debian Stretch (may also work on Debian Jessie), you can run the +following command:\ +\$ **sudo ./oldbuild dependencies debian**\ (this will also work in Devuan) -For Parabola, you can run the following command: - - $ sudo ./oldbuild dependencies parabola -or: +For Parabola, you can run the following command:\ +\$ **sudo ./oldbuild dependencies parabola**\ +or:\ +\# **./oldbuild dependencies parabola** -# **./oldbuild dependencies parabola** For other GNU+Linux distributions, you can adapt the existing scripts. +[Back to top of page](#pagetop) + + + Get the full source code from metadata (git clone) {#build_meta} ================================================== @@ -55,34 +63,33 @@ 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: - - $ git config \--global user.name "Your Name" - $ git config \--global user.email your@emailaddress.com +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 changes to a given repository. For more information, see <http://git-scm.com/doc>. -Another nice config for you (optional, but recommended): - - $ git config \--global core.editor nano - $ git config \--global color.status auto - $ git config \--global color.branch auto - $ git config \--global color.interactive auto +Another nice config for you (optional, but recommended):\ +\$ **git config \--global core.editor nano**\ +\$ **git config \--global color.status auto**\ +\$ **git config \--global color.branch auto**\ +\$ **git config \--global color.interactive auto**\ \$ **git config \--global color.diff auto** -After that, run the script: - +After that, run the script:\ \$ **./download all** What this did was download everything (grub, coreboot, memtest86+, bucts, flashrom) at the versions last tested for this release, and patch them. Read the script in a text editor to learn more. -To build the ROM images, see [#build](#build). +To build the ROM images, see [\#build](#build). [Back to top of page.](#pagetop) + + How to build "bucts" (for LenovoBIOS X60/X60S/X60T/T60) {#build_bucts} ========================================================= @@ -95,17 +102,17 @@ a register in the chipset on some Intel systems. Bucts is needed when flashing in software the X60/X60S/X60T/T60 ROM while Lenovo BIOS is running; external flashing will be safe regardless. Each ROM contains identical data inside the two final 64K region in the -file*. This corresponds to the final two 64K regions in the flash chip. +file\*. This corresponds to the final two 64K regions in the flash chip. Lenovo BIOS will prevent you from writing the final one, so running "**bucts 1**" will set the system to boot from the other block instead (which is writeable along with everything beneath it when using a -patched flashrom. see [#build\_flashrom](#build_flashrom)). After +patched flashrom. see [\#build\_flashrom](#build_flashrom)). After shutting down and booting up after the first flash of libreboot, the final 64K block is writeable so you flash the ROM again with an unpatched flashrom and run "**bucts 0**" to make the system boot from the normal (highest) block again. -*Libreboot ROM images have identical data in those two 64KiB regions +\*Libreboot ROM images have identical data in those two 64KiB regions because dd is used to do that, by the build system. If you're building from upstream (coreboot), you have to do it manually. @@ -116,9 +123,8 @@ the mainboard. Removing that battery removes power to BUC.TS, resetting the bit back to 0 (if you previously set it to 1). BUC.TS utility is included in libreboot\_src.tar.xz and -libreboot\_util.tar.xz. - -**If you downloaded from git, follow [#build\_meta](#build_meta) before +libreboot\_util.tar.xz.\ +**If you downloaded from git, follow [\#build\_meta](#build_meta) before you proceed.** "BUC" means "**B**ack**u**p **C**ontrol" (it's a register) and @@ -130,12 +136,10 @@ If you have the binary release archive, you'll find executables under First, [install the build dependencies](#build_dependencies). -To build bucts, do this in the main directory: - +To build bucts, do this in the main directory:\ \$ **./oldbuild module bucts** -To statically compile it, do this: - +To statically compile it, do this:\ \$ **./oldbuild module bucts static** The "builddeps" script in libreboot\_src also makes use of @@ -143,6 +147,8 @@ builddeps-bucts. [Back to top of page.](#pagetop) + + How to build "flashrom" {#build_flashrom} ========================= @@ -150,9 +156,8 @@ Flashrom is the utility for flashing/dumping ROM images. This is what you will use to install libreboot. Flashrom source code is included in libreboot\_src.tar.xz and -libreboot\_util.tar.xz. - -**If you downloaded from git, follow [#build\_meta](#build_meta) before +libreboot\_util.tar.xz.\ +**If you downloaded from git, follow [\#build\_meta](#build_meta) before you proceed.** If you are using the binary release archive, then there are already @@ -162,12 +167,10 @@ flashrom from source, continue reading. First, [install the build dependencies](#build_dependencies). -To build it, do the following in the main directory: - +To build it, do the following in the main directory:\ \$ **./oldbuild module flashrom** -To statically compile it, do the following in the main directory: - +To statically compile it, do the following in the main directory:\ \$ **./oldbuild module flashrom static** After you've done that, under ./flashrom/ you will find the following @@ -187,6 +190,8 @@ builddeps-flashrom. [Back to top of page.](#pagetop) + + How to build the ROM images {#build} =========================== @@ -207,42 +212,38 @@ MacBook1,1 laptops are all 32-bit only. First, [install the build dependencies](#build_dependencies). If you downloaded libreboot from git, refer to -[#build\_meta](#build_meta). - -Build all of the components used in libreboot: +[\#build\_meta](#build_meta). +Build all of the components used in libreboot:\ \$ **./oldbuild module all** You can also build each modules separately, using *./oldbuild module -modulename*. To see the possible values for *modulename*, use: - +modulename*. To see the possible values for *modulename*, use:\ \$ **./oldbuild module list** -After that, build the ROM images (for all boards): - - $ ./oldbuild roms withgrub +After that, build the ROM images (for all boards):\ +\$ **./oldbuild roms withgrub**\ Alternatively, you can build for a specific board or set of boards. For -example: - - $ ./oldbuild roms withgrub x60 - $ ./oldbuild roms withgrub x200\_8mb - $ ./oldbuild roms withgrub x60 x200\_8mb +example:\ +\$ **./oldbuild roms withgrub x60**\ +\$ **./oldbuild roms withgrub x200\_8mb**\ +\$ **./oldbuild roms withgrub x60 x200\_8mb**\ The list of board options can be found by looking at the directory names in **resources/libreboot/config/grub/**. -To clean (reverse) everything, do the following: - +To clean (reverse) everything, do the following:\ \$ **./oldbuild clean all** The ROM images will be stored under **bin/*payload*/**, where *payload* could be *grub*, *seabios*, or whatever other payload those images were built for. + Preparing release archives (optional) ------------------------------------- **This is only confirmed to work (tested) in Debian Stretch. Parabola -*fails* at this stage (for now). For all other distros, YMMV. This +\*fails\* at this stage (for now). For all other distros, YMMV. This will also work in Devuan.** This is mainly intended for use with the git repository. These commands @@ -258,29 +259,23 @@ Tag the current commit, and that version will appear in both the in the file names of the archives. Otherwise, whatever git uses for *git describe \--tags HEAD* will be used. -Utilities (static executables): - +Utilities (static executables):\ \$ **./oldbuild release util** -Archive containing flashrom and bucts source code: - +Archive containing flashrom and bucts source code:\ \$ **./oldbuild release tobuild** Documentation archive (**does not work on \_src release archive, only -git**): - +git**):\ \$ **./oldbuild release docs** -ROM image archives: - +ROM image archives:\ \$ **./oldbuild release roms** -Source code archive: - +Source code archive:\ \$ **./oldbuild release src** -SHA512 sums of all other release archives that have been generated: - +SHA512 sums of all other release archives that have been generated:\ \$ **./oldbuild release sha512sums** If you are building on an i686 host, this will build statically linked @@ -288,7 +283,7 @@ If you are building on an i686 host, this will build statically linked **nvramtool, cbfstool, ich9deblob, cbmem**. If you are building on an x86\_64 host, this will build statically -linked 32- *and* 64-bit binaries for **cbmem**, **ich9deblob**, +linked 32- \*and\* 64-bit binaries for **cbmem**, **ich9deblob**, **cbfstool** and **nvramtool**. **To include statically linked i686 and x86\_64 binaries for bucts and @@ -309,9 +304,8 @@ libreboot\_util, for: - flashrom If you are building binaries on a live system or chroot (for -flashrom/bucts), you can use the following to statically link them: - - $ ./oldbuild module flashrom static +flashrom/bucts), you can use the following to statically link them:\ +\$ **./oldbuild module flashrom static**\ \$ **./oldbuild module bucts static** The same conditions as above apply for ARM (except, building bucts on @@ -321,9 +315,8 @@ an X60/T60 while lenovo bios is present, working around the security restrictions). The command that you used for generating the release archives will also -run the following command: - - $ ./oldbuild release tobuild +run the following command:\ +\$ **./oldbuild release tobuild**\ The archive **tobuild.tar.xz** will have been created under **release/oldbuildsystem/**, containing bucts, flashrom and all other required resources for building them. @@ -335,8 +328,12 @@ libreboot\_src.tar.xz have been created, under The ROM images will be stored in separate archives for each system, under **release/oldbuildsystem/rom/**. -Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org> +[Back to top of page](#pagetop) + + + +Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/global.css b/docs/global.css @@ -1,38 +0,0 @@ -html { - background-color: #eee; -} - -body { - background-color: #fff; - margin: 0 auto; - max-width: 60em; - padding: 0.2em 1em; - box-shadow: 0 0 6px; -} - -body { - line-height: 1.6; - font-family: Cantarell, sans-serif; - font-size: 1.1em; - - color: #222; -} - -h1 { - font-size: 2.0em; - text-align: center; -} - -#logo { - width: 25%; - float: right; -} - -a { - text-decoration: none; - color: #22D; -} - -a:hover { - color: #008; -} diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md @@ -1,4 +1,6 @@ -% Configuring Parabola (post-install) + +Configuring Parabola (post-install) +=================================== Post-installation configuration steps for Parabola GNU+Linux-libre. Parabola is extremely flexible; this is just an example. This example @@ -7,6 +9,8 @@ uses LXDE because it's lightweight, but we recommend the *MATE* desktop [Back to previous index](./) + + Table of Contents ================= @@ -38,6 +42,8 @@ Table of Contents - [LXDE - battery monitor](#lxde_battery) - [LXDE - network manager](#lxde_network) + + While not strictly related to the libreboot project, this guide is intended to be useful for those interested in installing Parabola on their libreboot system. @@ -53,6 +59,8 @@ will be made to maintain it. to be made at the present date, please get in touch with the libreboot project!** + + You do not necessarily have to follow this guide word-for-word; *parabola* is extremely flexible. The aim here is to provide a common setup that most users will be happy with. While Parabola can seem @@ -65,6 +73,8 @@ Paradoxically, as you get more advanced Parabola can actually become compared to what most distributions provide. You will find over time that other distributions tend to *get in your way*. + + **This guide assumes that you already have Parabola installed. If you have not yet installed Parabola, then [this guide](encrypted_parabola.html) is highly recommended!** @@ -83,18 +93,19 @@ system Linux, using the term open-source (or closed-source), and it will sometimes recommend the use of proprietary software. You need to be careful about this when reading anything on the Arch wiki. -Some of these steps require internet access. I'll go into networking -later but for now, I just connected my system to a switch and did: - # systemctl start dhcpcd.service -You can stop it later by running: - # systemctl stop dhcpcd.service +Some of these steps require internet access. I'll go into networking +later but for now, I just connected my system to a switch and did:\ +\# **systemctl start dhcpcd.service**\ +You can stop it later by running:\ +\# **systemctl stop dhcpcd.service**\ For most people this should be enough, but if you don't have DHCP on -your network then you should setup your network connection first: - +your network then you should setup your network connection first:\ [Setup network connection in Parabola](#network) + + Configure pacman {#pacman_configure} ---------------- @@ -111,20 +122,19 @@ sure to read and understand this, it's very important) and [Back to top of page.](#pagetop) + + 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: - - # pacman -Syy +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 -when switching to another mirror). - -Then, update the system: - -# **pacman -Syu** +when switching to another mirror).\ +Then, update the system:\ +\# **pacman -Syu** **Before installing packages with 'pacman -S', always update first, using the notes above.** @@ -146,7 +156,7 @@ work. The Arch forum can also be useful, if others have the same issue as you (if you encounter issues, that is). The *Parabola* IRC channel -(#parabola on freenode) can also help you. +(\#parabola on freenode) can also help you. Due to this and the volatile nature of Parabola/Arch, you should only update when you have at least a couple hours of spare time in case of @@ -164,6 +174,8 @@ event that they do occur. [Back to top of page.](#pagetop) + + Maintaining Parabola {#pacman_maintain} -------------------- @@ -179,17 +191,15 @@ re-install it or install the distro on another computer, for example). ### Cleaning the package cache {#pacman_cacheclean} **The following is very important as you continue to use, update and -maintain your Parabola system: - +maintain your Parabola system:\ <https://wiki.archlinux.org/index.php/Pacman#Cleaning_the_package_cache>. Essentially, this guide talks about a directory that has to be cleaned once in a while, to prevent it from growing too big (it's a cache of old package information, updated automatically when you do anything in pacman).** -To clean out all old packages that are cached: - -# **pacman -Sc** +To clean out all old packages that are cached:\ +\# **pacman -Sc** The wiki cautions that this should be used with care. For example, since older packages are deleted from the repo, if you encounter issues and @@ -197,9 +207,8 @@ want to revert back to an older package then it's useful to have the caches available. Only do this if you are sure that you won't need it. The wiki also mentions this method for removing everything from the -cache, including currently installed packages that are cached: - - # pacman -Scc +cache, including currently installed packages that are cached:\ +\# **pacman -Scc**\ This is inadvisable, since it means re-downloading the package again if you wanted to quickly re-install it. This should only be used when disk space is at a premium. @@ -209,12 +218,13 @@ space is at a premium. ### pacman command equivalents {#pacman_commandequiv} The following table lists other distro package manager commands, and -their equivalent in pacman: - +their equivalent in pacman:\ <https://wiki.archlinux.org/index.php/Pacman_Rosetta> [Back to top of page.](#pagetop) + + your-freedom {#yourfreedom} ------------ @@ -229,6 +239,8 @@ continue installing *your-freedom*. [Back to top of page.](#pagetop) + + Add a user {#useradd} ---------- @@ -241,16 +253,18 @@ access to the entire operating system. Read the entire document linked to above, and then continue. -Add your user: - - # useradd -m -G wheel -s /bin/bash *yourusername* -Set a password: - -# **passwd *yourusername*** +Add your user:\ +\# **useradd -m -G wheel -s /bin/bash *yourusername***\ +Set a password:\ +\# **passwd *yourusername*** Use of the *diceware method* is recommended, for generating secure passphrases (instead of passwords). +[Back to top of page](#pagetop) + + + systemd ------- @@ -268,9 +282,8 @@ sshd (openssh), dhcp, etc. There are countless others. the background behind the decision by Arch (Parabola's upstream supplier) to use systemd. -The manpage should also help: - - # man systemd +The manpage should also help:\ +\# **man systemd**\ The section on 'unit types' is especially useful. According to the wiki, systemd 'journal' keeps logs of a size up to @@ -280,36 +293,30 @@ implications later when the log gets too big. Based on instructions from the wiki, I will reduce the total size of the journal to 50MiB (the wiki recommends 50MiB). -Open /etc/systemd/journald.conf and find the line that says: - -*#SystemMaxUse=* - -Change it to say: - +Open /etc/systemd/journald.conf and find the line that says:\ +*\#SystemMaxUse=*\ +Change it to say:\ *SystemMaxUse=50M* The wiki also recommended a method for forwarding journal output to TTY 12 (accessible by pressing ctrl+alt+f12, and you use ctrl+alt+\[F1-F12\] to switch between terminals). I decided not to enable it. -Restart journald: - -# **systemctl restart systemd-journald** +Restart journald:\ +\# **systemctl restart systemd-journald** The wiki recommends that if the journal gets too large, you can also -simply delete (rm -Rf) everything inside /var/log/journald/* but +simply delete (rm -Rf) everything inside /var/log/journald/\* but recommends backing it up. This shouldn't be necessary, since you already set the size limit above and systemd will automatically start to delete older records when the journal size reaches it's limit (according to systemd developers). Finally, the wiki mentions 'temporary' files and the utility for -managing them. - - # man systemd-tmpfiles -The command for 'clean' is: - - # systemd-tmpfiles \--clean +managing them.\ +\# **man systemd-tmpfiles**\ +The command for 'clean' is:\ +\# **systemd-tmpfiles \--clean**\ According to the manpage, this *"cleans all files and directories with an age parameter"*. According to the Arch wiki, this reads information in /etc/tmpfiles.d/ and /usr/lib/tmpfiles.d/ to know what actions to @@ -318,14 +325,17 @@ locations to get a better understanding. I looked in /etc/tmpfiles.d/ and found that it was empty on my system. However, /usr/lib/tmpfiles.d/ contained some files. The first one was -etc.conf, containing information and a reference to this manpage: - - # man tmpfiles.d +etc.conf, containing information and a reference to this manpage:\ +\# **man tmpfiles.d**\ Read that manpage, and then continue studying all the files. The systemd developers tell me that it isn't usually necessary to touch the systemd-tmpfiles utility manually at all. +[Back to top of page](#pagetop) + + + Interesting repositories {#interesting_repos} ------------------------ @@ -336,25 +346,23 @@ default base. It might be worth looking into what is available there, depending on your use case. I enabled it on my system, to see what was in it. Edit /etc/pacman.conf -and below the 'extra' section add: - -*\[kernels\] - +and below the 'extra' section add:\ +*\[kernels\]\ Include = /etc/pacman.d/mirrorlist* -Now sync with the repository: +Now sync with the repository:\ +\# **pacman -Syy** -# **pacman -Syy** - -List all available packages in this repository: - -# **pacman -Sl kernels** +List all available packages in this repository:\ +\# **pacman -Sl kernels** In the end, I decided not to install anything from it but I kept the repository enabled regardless. [Back to top of page.](#pagetop) + + Setup a network connection in Parabola {#network} -------------------------------------- @@ -366,20 +374,16 @@ Read <https://wiki.archlinux.org/index.php/Configuring_Network>. This should be the same as the hostname that you set in /etc/hostname when installing Parabola. You can also do it with systemd (do so now, if -you like): - - # hostnamectl set-hostname *yourhostname* +you like):\ +\# **hostnamectl set-hostname *yourhostname***\ This writes the specified hostname to /etc/hostname. More information -can be found in these manpages: - - # man hostname - # info hostname -# **man hostnamectl** - -Add the same hostname to /etc/hosts, on each line. Example: - -*127.0.0.1 localhost.localdomain localhost myhostname +can be found in these manpages:\ +\# **man hostname**\ +\# **info hostname**\ +\# **man hostnamectl** +Add the same hostname to /etc/hosts, on each line. Example:\ +*127.0.0.1 localhost.localdomain localhost myhostname\ ::1 localhost.localdomain localhost myhostname* You'll note that I set both lines; the 2nd line is for IPv6. More and @@ -397,21 +401,17 @@ According to the Arch wiki, [udev](https://wiki.archlinux.org/index.php/Udev) should already detect the ethernet chipset and load the driver for it automatically at boot time. You can check this in the *"Ethernet controller"* section when -running this command: - -# **lspci -v** +running this command:\ +\# **lspci -v** Look at the remaining sections *'Kernel driver in use'* and *'Kernel -modules'*. In my case it was as follows: - -*Kernel driver in use: e1000e - +modules'*. In my case it was as follows:\ +*Kernel driver in use: e1000e\ Kernel modules: e1000e* Check that the driver was loaded by issuing *dmesg | grep module\_name*. -In my case, I did: - -# **dmesg | grep e1000e** +In my case, I did:\ +\# **dmesg | grep e1000e** ### Network device names {#network_devicenames} @@ -432,12 +432,10 @@ instructions in [grub\_cbfs.html](grub_cbfs.html)). For background information, read [Predictable Network Interface Names](http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/) -Show device names: - -# **ls /sys/class/net** - -Changing the device names is possible (I chose not to do it): +Show device names:\ +\# **ls /sys/class/net** +Changing the device names is possible (I chose not to do it):\ <https://wiki.archlinux.org/index.php/Configuring_Network#Change_device_name> [Back to top of page.](#pagetop) @@ -446,8 +444,7 @@ Changing the device names is possible (I chose not to do it): I actually chose to ignore most of Networking section on the wiki. Instead, I plan to set up LXDE desktop with the graphical -network-manager client. Here is a list of network managers: - +network-manager client. Here is a list of network managers:\ <https://wiki.archlinux.org/index.php/List_of_applications/Internet#Network_managers>. If you need to, set a static IP address (temporarily) using the networking guide and the Arch wiki, or start the dhcpcd service in @@ -455,6 +452,8 @@ systemd. NetworkManager will be setup later, after installing LXDE. [Back to top of page.](#pagetop) + + System Maintenance {#system_maintain} ------------------ @@ -465,14 +464,15 @@ is important, so make sure to read them!** Install smartmontools (it can be used to check smart data. HDDs use non-free firmware inside, but it's transparent to you but the smart -data comes from it. Therefore, don't rely on it too much): - - # pacman -S smartmontools +data comes from it. Therefore, don't rely on it too much):\ +\# **pacman -S smartmontools**\ Read <https://wiki.archlinux.org/index.php/S.M.A.R.T.> to learn how to use it. [Back to top of page.](#pagetop) + + Configuring the desktop {#desktop} ----------------------- @@ -484,57 +484,49 @@ provide LXDE by default. [Back to top of page.](#pagetop) + ### Installing Xorg {#desktop_xorg} Based on <https://wiki.archlinux.org/index.php/Xorg>. -Firstly, install it! - - # pacman -S xorg-server +Firstly, install it!\ +\# **pacman -S xorg-server**\ I also recommend installing this (contains lots of useful tools, -including *xrandr*): - -# **pacman -S xorg-server-utils** +including *xrandr*):\ +\# **pacman -S xorg-server-utils** Install the driver. For me this was *xf86-video-intel* on the ThinkPad -X60. T60 and macbook11/21 should be the same. - - # pacman -S xf86-video-intel -For other systems you can try: - - # pacman -Ss xf86-video- | less +X60. T60 and macbook11/21 should be the same.\ +\# **pacman -S xf86-video-intel**\ +For other systems you can try:\ +\# **pacman -Ss xf86-video- | less**\ Combined with looking at your *lspci* output, you can determine which driver is needed. By default, Xorg will revert to xf86-video-vesa which is a generic driver and doesn't provide true hardware acceleration. Other drivers (not just video) can be found by looking at the -*xorg-drivers* group: - - # pacman -Sg xorg-drivers +*xorg-drivers* group:\ +\# **pacman -Sg xorg-drivers**\ Mostly you will rely on a display manager, but in case you ever want to -start X without one: - -# **pacman -S xorg-xinit** - -<optional> - -   Arch wiki recommends installing these, for testing that X works: - -    # pacman -S xorg-twm xorg-xclock xterm -   Refer to <https://wiki.archlinux.org/index.php/Xinitrc>. and test X: - -    # startx +start X without one:\ +\# **pacman -S xorg-xinit** + +<optional>\ +   Arch wiki recommends installing these, for testing that X works:\ +   \# **pacman -S xorg-twm xorg-xclock xterm**\ +   Refer to <https://wiki.archlinux.org/index.php/Xinitrc>. and test X:\ +   \# **startx**\    When you are satisfied, type ***exit*** in xterm, inside the X -session. - -   Uninstall them (clutter. eww): # **pacman -S xorg-xinit xorg-twm -xorg-xclock xterm** - +session.\ +   Uninstall them (clutter. eww): \# **pacman -S xorg-xinit xorg-twm +xorg-xclock xterm**\ </optional> [Back to top of page.](#pagetop) + + ### Xorg keyboard layout {#desktop_kblayout} Refer to @@ -545,9 +537,8 @@ will notice that the layout you set in /etc/vconsole.conf earlier might not actually be the same in X. To see what layout you currently use, try this on a terminal emulator in -X: - -# **setxkbmap -print -verbose 10** +X:\ +\# **setxkbmap -print -verbose 10** In my case, I wanted to use the Dvorak (UK) keyboard which is quite different from Xorg's default Qwerty (US) layout. @@ -560,30 +551,20 @@ X60, with a 105-key UK keyboard). If you use an American keyboard *dvorak*. The Arch wiki recommends two different methods for setting the keyboard -layout: - +layout:\ <https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_X_configuration_files> -and - +and\ <https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_localectl>. -In my case, I chose to use the *configuration file* method: - +In my case, I chose to use the *configuration file* method:\ Create the file /etc/X11/xorg.conf.d/10-keyboard.conf and put this -inside: - -*Section "InputClass" - -        Identifier "system-keyboard" - -        MatchIsKeyboard "on" - -        Option "XkbLayout" "gb" - -        Option "XkbModel" "pc105" - -        Option "XkbVariant" "dvorak" - +inside:\ +*Section "InputClass"\ +        Identifier "system-keyboard"\ +        MatchIsKeyboard "on"\ +        Option "XkbLayout" "gb"\ +        Option "XkbModel" "pc105"\ +        Option "XkbVariant" "dvorak"\ EndSection* For you, the steps above may differ if you have a different layout. If @@ -592,6 +573,8 @@ you use a US Qwerty keyboard, then you don't even need to do anything [Back to top of page.](#pagetop) + + ### Install LXDE {#desktop_lxde} Desktop choice isn't that important to me, so for simplicity I decided @@ -601,65 +584,52 @@ would like to try something different, refer to Refer to <https://wiki.archlinux.org/index.php/LXDE>. -Install it, choosing 'all' when asked for the default package list: - -# **pacman -S lxde obconf** - -I didn't want the following, so I removed them: - -# **pacman -R lxmusic lxtask** +Install it, choosing 'all' when asked for the default package list:\ +\# **pacman -S lxde obconf** -I also lazily installed all fonts: +I didn't want the following, so I removed them:\ +\# **pacman -R lxmusic lxtask** -# **pacman -S \$(pacman -Ssq ttf-)** +I also lazily installed all fonts:\ +\# **pacman -S \$(pacman -Ssq ttf-)** -And a mail client: - -# **pacman -S icedove** +And a mail client:\ +\# **pacman -S icedove** In IceCat, go to *Preferences :: Advanced* and disable *GNU IceCat Health Report*. -I also like to install these: - -# **pacman -S xsensors stress htop** - -Enable LXDM (the default display manager, providing a graphical login): - - # systemctl enable lxdm.service -It will start when you boot up the system. To start it now, do: +I also like to install these:\ +\# **pacman -S xsensors stress htop** -# **systemctl start lxdm.service** +Enable LXDM (the default display manager, providing a graphical login):\ +\# **systemctl enable lxdm.service**\ +It will start when you boot up the system. To start it now, do:\ +\# **systemctl start lxdm.service** Log in with your standard (non-root) user that you created earlier. It is advisable to also create an xinitrc rule in case you ever want to start lxde without lxdm. Read <https://wiki.archlinux.org/index.php/Xinitrc>. -Open LXterminal: - - $ cp /etc/skel/.xinitrc \~ +Open LXterminal:\ +\$ **cp /etc/skel/.xinitrc \~**\ Open .xinitrc and add the following plus a line break at the bottom of -the file. - -*# Probably not needed. The same locale info that we set before - -# Based on advice from the LXDE wiki export LC\_ALL=en\_GB.UTF-8 - -export LANGUAGE=en\_GB.UTF-8 - -export LANG=en\_GB.UTF-8 - -# Start lxde desktop - -exec startlxde - -* Now make sure that it is executable: - +the file.\ +*\# Probably not needed. The same locale info that we set before\ +\# Based on advice from the LXDE wiki export LC\_ALL=en\_GB.UTF-8\ +export LANGUAGE=en\_GB.UTF-8\ +export LANG=en\_GB.UTF-8\ +\ +\# Start lxde desktop\ +exec startlxde\ +* Now make sure that it is executable:\ \$ **chmod +x .xinitrc** [Back to top of page.](#pagetop) + + ### LXDE - clock {#lxde_clock} In **Digital Clock Settings** (right click the clock) I set the Clock @@ -667,17 +637,20 @@ Format to *%Y/%m/%d %H:%M:%S* [Back to top of page.](#pagetop) + + ### LXDE - font {#lxde_font} NOTE TO SELF: come back to this later. [Back to top of page.](#pagetop) -### LXDE - screenlock {#lxde_screenlock} -Arch wiki recommends to use *xscreensaver*: -# **pacman -S xscreensaver** +### LXDE - screenlock {#lxde_screenlock} + +Arch wiki recommends to use *xscreensaver*:\ +\# **pacman -S xscreensaver** Under *Preferences :: Screensaver* in the LXDE menu, I chose *Mode: Blank Screen Only*, setting *Blank After*, *Cycle After* and *Lock @@ -688,6 +661,8 @@ menu. [Back to top of page.](#pagetop) + + ### LXDE - automounting {#lxde_automount} Refer to @@ -697,6 +672,8 @@ I chose to ignore this for now. NOTE TO SELF: come back to this later. [Back to top of page.](#pagetop) + + ### LXDE - disable suspend {#lxde_suspend} When closing the laptop lid, the system suspends. This is annoying at @@ -704,6 +681,8 @@ least to me. NOTE TO SELF: disable it, then document the steps here. [Back to top of page.](#pagetop) + + ### LXDE - battery monitor {#lxde_battery} Right click lxde panel and *Add/Remove Panel Items*. Click *Add* and @@ -714,44 +693,38 @@ cursor over it, it'll show information about the battery. [Back to top of page.](#pagetop) + + ### LXDE - Network Manager {#lxde_network} Refer to <https://wiki.archlinux.org/index.php/LXDE#Network_Management>. Then I read: <https://wiki.archlinux.org/index.php/NetworkManager>. -Install Network Manager: - -# **pacman -S networkmanager** - -You will also want the graphical applet: +Install Network Manager:\ +\# **pacman -S networkmanager** - # pacman -S network-manager-applet +You will also want the graphical applet:\ +\# **pacman -S network-manager-applet**\ Arch wiki says that an autostart rule will be written at */etc/xdg/autostart/nm-applet.desktop* I want to be able to use a VPN at some point, so the wiki tells me to -do: - -# **pacman -S networkmanager-openvpn** - -LXDE uses openbox, so I refer to: +do:\ +\# **pacman -S networkmanager-openvpn** +LXDE uses openbox, so I refer to:\ <https://wiki.archlinux.org/index.php/NetworkManager#Openbox>. -It tells me for the applet I need: - - # pacman -S xfce4-notifyd gnome-icon-theme -Also, for storing authentication details (wifi) I need: - -# **pacman -S gnome-keyring** +It tells me for the applet I need:\ +\# **pacman -S xfce4-notifyd gnome-icon-theme**\ +Also, for storing authentication details (wifi) I need:\ +\# **pacman -S gnome-keyring** -I wanted to quickly enable networkmanager: - - # systemctl stop dhcpcd - # systemctl start NetworkManager -Enable NetworkManager at boot time: - -# **systemctl enable NetworkManager** +I wanted to quickly enable networkmanager:\ +\# **systemctl stop dhcpcd**\ +\# **systemctl start NetworkManager**\ +Enable NetworkManager at boot time:\ +\# **systemctl enable NetworkManager** Restart LXDE (log out, and then log back in). @@ -761,8 +734,10 @@ theme, in *lxappearance*. [Back to top of page.](#pagetop) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/gnulinux/encrypted_debian.md b/docs/gnulinux/encrypted_debian.md @@ -1,4 +1,6 @@ -% Installing Debian or Devuan GNU+Linux with full disk encryption (including /boot) + +Installing Debian or Devuan GNU+Linux with full disk encryption (including /boot) +================================================================================= This guide is written for the Debian distribution, but it should also work for Devuan with the net installer. @@ -20,30 +22,21 @@ tampering by someone with physical access to the system. This guide is written for Debian net installer. You can download the ISO from the homepage on [debian.org](https://www.debian.org/). Use this on -the GRUB terminal to boot it from USB (for 64-bit Intel or AMD): - -**set root='usb0' - -linux /install.amd/vmlinuz - -initrd /install.amd/initrd.gz - -boot - -** If you are on a 32-bit system (e.g. X60): - -**set root='usb0' - -linux /install.386/vmlinuz - -initrd /install.386/initrd.gz - +the GRUB terminal to boot it from USB (for 64-bit Intel or AMD):\ +**set root='usb0'\ +linux /install.amd/vmlinuz\ +initrd /install.amd/initrd.gz\ +boot\ +** If you are on a 32-bit system (e.g. X60):\ +**set root='usb0'\ +linux /install.386/vmlinuz\ +initrd /install.386/initrd.gz\ boot** [This guide](grub_boot_installer.html) shows how to create a boot USB drive with the Debian ISO image. -**This guide is *only* for the GRUB payload. If you use the +**This guide is \*only\* for the GRUB payload. If you use the depthcharge payload, ignore this section entirely.** Note: on some thinkpads, a faulty DVD drive can cause the cryptomount -a @@ -52,6 +45,8 @@ drive. [Back to previous index](./) + + Set a strong user password (lots of lowercase/uppercase, numbers and symbols). @@ -68,6 +63,8 @@ therefore optional, and not recommended. Choose 'no'.** you will set later on. Your LUKS password should, like the user password, be secure.** + + Partitioning ============ @@ -107,6 +104,8 @@ Choose 'Manual' partitioning: - name: **swap** (user this exact name) - size: press enter + + Further partitioning ==================== @@ -122,12 +121,16 @@ mountpoints and filesystems to use. - done setting up partition - Now you select 'Finished partitioning and write changes to disk'. + + Kernel ====== Installation will ask what kernel you want to use. linux-generic is fine. + + Tasksel ======= @@ -148,12 +151,16 @@ instead, which contains the most up to date versions of the Linux kernel. These kernels are also deblobbed, like Debian's kernels, so you can be sure that no binary blobs are present. + + Postfix configuration ===================== If asked, choose *"No Configuration"* here (or maybe you want to select something else. It's up to you.) + + Install the GRUB boot loader to the master boot record ====================================================== @@ -164,35 +171,38 @@ Choice is irrelevant here. *You do not need to install GRUB at all, since in libreboot you are using the GRUB payload (for libreboot) to boot your system directly.* + + Clock UTC ========= Just say 'Yes'. + + Booting your system =================== At this point, you will have finished the installation. At your GRUB payload, press C to get to the command line. -Do that: - -grub> cryptomount -a -grub> set root='lvm/matrix-rootvol' +Do that:\ +grub> **cryptomount -a**\ +grub> **set root='lvm/matrix-rootvol'**\ grub> **linux /vmlinuz root=/dev/mapper/matrix-rootvol -cryptdevice=/dev/mapper/matrix-rootvol:root** - -grub> initrd /initrd.img +cryptdevice=/dev/mapper/matrix-rootvol:root**\ +grub> **initrd /initrd.img**\ grub> **boot** + + ecryptfs ======== If you didn't encrypt your home directory, then you can safely ignore this section. -Immediately after logging in, do that: - +Immediately after logging in, do that:\ \$ **sudo ecryptfs-unwrap-passphrase** This will be needed in the future if you ever need to recover your home @@ -200,6 +210,8 @@ directory from another system, so write it down and keep the note somewhere secret. Ideally, you should memorize it and then burn the note (or not even write it down, and memorize it still)> + + Modify grub.cfg (CBFS) ====================== @@ -210,11 +222,10 @@ Modify your grub.cfg (in the firmware) [using this tutorial](grub_cbfs.html); just change the default menu entry 'Load Operating System' to say this inside: - cryptomount -a - set root='lvm/matrix-rootvol' +**cryptomount -a**\ +**set root='lvm/matrix-rootvol'**\ **linux /vmlinuz root=/dev/mapper/matrix-rootvol -cryptdevice=/dev/mapper/matrix-rootvol:root** - +cryptdevice=/dev/mapper/matrix-rootvol:root**\ **initrd /initrd.img** Without specifying a device, the *-a* parameter tries to unlock all @@ -225,6 +236,8 @@ hardening your GRUB configuration, for security purposes. Flash the modified ROM using [this tutorial](../install/#flashrom). + + Troubleshooting =============== @@ -236,6 +249,7 @@ station. Further investigation revealed that it was the DVD drive causing problems. Removing that worked around the issue. + "sudo wodim -prcap" shows information about the drive: Device was not specified. Trying to find an appropriate drive... Detected CD-R drive: /dev/sr0 @@ -312,8 +326,9 @@ problems. Removing that worked around the issue. Does write ultra high speed CD-RW media Does not write ultra high speed+ CD-RW media -Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md @@ -1,4 +1,6 @@ -% Installing Parabola or Arch GNU+Linux with full disk encryption (including /boot) + +Installing Parabola or Arch GNU+Linux with full disk encryption (including /boot) +================================================================================= Libreboot on x86 uses the GRUB [payload](http://www.coreboot.org/Payloads#GRUB_2) by default, which @@ -15,7 +17,7 @@ volume. Not so with libreboot! Since GRUB is already included directly as a payload, even /boot can be encrypted. This protects /boot from tampering by someone with physical access to the system. -**This guide is *only* for the GRUB payload. If you use the +**This guide is \*only\* for the GRUB payload. If you use the depthcharge payload, ignore this section entirely.** This guide is intended for the Parabola distribution, but it should also @@ -32,6 +34,8 @@ drive. [Back to previous index](./) + + Boot Parabola's install environment. [How to boot a GNU+Linux installer](grub_boot_installer.html). @@ -47,6 +51,8 @@ to the Parabola wiki at a later date. For up to date Parabola install guide, go to the Parabola wiki. This guide essentially cherry picks the useful information (valid at the time of writing: 2015-08-25). + + This section deals with wiping the storage device on which you plan to install Parabola GNU+Linux. Follow these steps, but if you use an SSD, also: @@ -64,15 +70,13 @@ article](https://wiki.archlinux.org/index.php/Solid_State_Drives). Edit /etc/fstab later on when chrooted into your install. Also, read the 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 +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 -example if it was 2MiB: - -# **dd if=/dev/urandom of=/dev/sda bs=2M; sync** +example if it was 2MiB:\ +\# **dd if=/dev/urandom of=/dev/sda bs=2M; sync** If your drive was already LUKS encrypted (maybe you are re-installing your distro) then it is already 'wiped'. You should just wipe the LUKS @@ -80,22 +84,24 @@ 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: - - # head -c 3145728 /dev/urandom > /dev/sda; sync +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). + + Change keyboard layout ---------------------- Parabola live shell assumes US Qwerty. If you have something different, -list the available keymaps and use yours: - - # localectl list-keymaps - # loadkeys LAYOUT +list the available keymaps and use yours:\ +\# **localectl list-keymaps**\ +\# **loadkeys LAYOUT**\ For me, LAYOUT would have been dvorak-uk. + + Establish an internet connection -------------------------------- @@ -103,6 +109,8 @@ Refer to [this guide](https://wiki.parabola.nu/Beginners%27_guide#Establish_an_internet_connection). Wired is recommended, but wireless is also explained there. + + Getting started --------------- @@ -110,13 +118,14 @@ The beginning is based on <https://wiki.parabolagnulinux.org/Installation_Guide>. Then I referred to <https://wiki.archlinux.org/index.php/Partitioning> at first. + + dm-mod ------ device-mapper will be used - a lot. Make sure that the kernel module is -loaded: - -# **modprobe dm-mod** +loaded:\ +\# **modprobe dm-mod** Create LUKS partition --------------------- @@ -129,35 +138,29 @@ prepared cryptsetup command below. Note that the iteration time is for security purposes (mitigates brute force attacks), so anything lower than 5 seconds is probably not ok. -I am using MBR partitioning, so I use cfdisk: - -# **cfdisk /dev/sda** +I am using MBR partitioning, so I use cfdisk:\ +\# **cfdisk /dev/sda** I create a single large sda1 filling the whole drive, leaving it as the default type 'Linux' (83). Now I refer to -<https://wiki.archlinux.org/index.php/Dm-crypt/Drive_preparation#Partitioning>: - +<https://wiki.archlinux.org/index.php/Dm-crypt/Drive_preparation#Partitioning>:\ I am then directed to <https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption>. Parabola forces you to RTFM. Do that. -It tells me to run: - -# **cryptsetup benchmark** (for making sure the list below is -populated) - -Then: - - # cat /proc/crypto +It tells me to run:\ +\# **cryptsetup benchmark** (for making sure the list below is +populated)\ +Then:\ +\# **cat /proc/crypto**\ This gives me crypto options that I can use. It also provides a representation of the best way to set up LUKS (in this case, security is a priority; speed, a distant second). To gain a better understanding, I -am also reading: - -# **man cryptsetup** +am also reading:\ +\# **man cryptsetup** Following that page, based on my requirements, I do the following based on @@ -165,9 +168,8 @@ on Reading through, it seems like Serpent (encryption) and Whirlpool (hash) is the best option. -I am initializing LUKS with the following: - -# **cryptsetup -v \--cipher serpent-xts-plain64 \--key-size 512 \--hash +I am initializing LUKS with the following:\ +\# **cryptsetup -v \--cipher serpent-xts-plain64 \--key-size 512 \--hash whirlpool \--iter-time 500 \--use-random \--verify-passphrase luksFormat /dev/sda1** Choose a **secure** passphrase here. Ideally lots of lowercase/uppercase numbers, letters, symbols etc all in a random @@ -177,45 +179,38 @@ without writing it down or storing it anywhere. Use of the *diceware method* is recommended, for generating secure passphrases (instead of passwords). + + Create LVM ---------- Now I refer to <https://wiki.archlinux.org/index.php/LVM>. -Open the LUKS partition: - - # cryptsetup luksOpen /dev/sda1 lvm +Open the LUKS partition:\ +\# **cryptsetup luksOpen /dev/sda1 lvm**\ (it will be available at /dev/mapper/lvm) -Create LVM partition: - - # pvcreate /dev/mapper/lvm -Show that you just created it: - -# **pvdisplay** +Create LVM partition:\ +\# **pvcreate /dev/mapper/lvm**\ +Show that you just created it:\ +\# **pvdisplay** Now I create the volume group, inside of which the logical volumes will -be created: - - # vgcreate matrix /dev/mapper/lvm +be created:\ +\# **vgcreate matrix /dev/mapper/lvm**\ (volume group name is 'matrix' - choose your own name, if you like) -Show that you created it: - -# **vgdisplay** - -Now create the logical volumes: - -# **lvcreate -L 2G matrix -n swapvol** (2G swap partition, named -swapvol) +Show that you created it:\ +\# **vgdisplay** +Now create the logical volumes:\ +\# **lvcreate -L 2G matrix -n swapvol** (2G swap partition, named +swapvol)\ Again, choose your own name if you like. Also, make sure to choose a swap size of your own needs. It basically depends on how much RAM you have installed. I refer to -<http://www.linux.com/news/software/applications/8208-all-about-linux-swap-space>. - -# **lvcreate -l +100%FREE matrix -n root** (single large partition in -the rest of the space, named root) - +<http://www.linux.com/news/software/applications/8208-all-about-linux-swap-space>.\ +\# **lvcreate -l +100%FREE matrix -n root** (single large partition in +the rest of the space, named root)\ You can also be flexible here, for example you can specify a /boot, a /, a /home, a /var, a /usr, etc. For example, if you will be running a web/mail server then you want /var in its own partition (so that if it @@ -223,27 +218,26 @@ fills up with logs, it won't crash your system). For a home/laptop system (typical use case), a root and a swap will do (really). Verify that the logical volumes were created, using the following -command: +command:\ +\# **lvdisplay** + -# **lvdisplay** Create / and swap partitions, and mount --------------------------------------- -For the swapvol LV I use: +For the swapvol LV I use:\ +\# **mkswap /dev/mapper/matrix-swapvol**\ +Activate swap:\ +\# **swapon /dev/matrix/swapvol** - # mkswap /dev/mapper/matrix-swapvol -Activate swap: +For the root LV I use:\ +\# **mkfs.btrfs /dev/mapper/matrix-root** -# **swapon /dev/matrix/swapvol** +Mount the root (/) partition:\ +\# **mount /dev/matrix/root /mnt** -For the root LV I use: -# **mkfs.btrfs /dev/mapper/matrix-root** - -Mount the root (/) partition: - -# **mount /dev/matrix/root /mnt** Continue with Parabola installation ----------------------------------- @@ -255,150 +249,121 @@ Now I am following the rest of <https://wiki.parabolagnulinux.org/Installation_Guide>. I also cross referenced <https://wiki.archlinux.org/index.php/Installation_guide>. -Create /home and /boot on root mountpoint: - - # mkdir -p /mnt/home -# **mkdir -p /mnt/boot** +Create /home and /boot on root mountpoint:\ +\# **mkdir -p /mnt/home**\ +\# **mkdir -p /mnt/boot** Once all the remaining partitions, if any, have been mounted, the devices are ready to install Parabola. In **/etc/pacman.d/mirrorlist**, comment out all lines except the Server line closest to where you are (I chose the UK Parabola server (main -server)) and then did: - - # pacman -Syy - # pacman -Syu -# **pacman -Sy pacman** (and then I did the other 2 steps above, -again) - +server)) and then did:\ +\# **pacman -Syy**\ +\# **pacman -Syu**\ +\# **pacman -Sy pacman** (and then I did the other 2 steps above, +again)\ In my case I did the steps in the next paragraph, and followed the steps in this paragraph again. -<troubleshooting> - +<troubleshooting>\    The following is based on 'Verification of package signatures' in -the Parabola install guide. - -   Check there first to see if steps differ by now. - +the Parabola install guide.\ +   Check there first to see if steps differ by now.\    Now you have to update the default Parabola keyring. This is used for -signing and verifying packages: - -    # pacman -Sy parabola-keyring +signing and verifying packages:\ +   \# **pacman -Sy parabola-keyring**\    It says that if you get GPG errors, then it's probably an expired -key and, therefore, you should do: - -    # pacman-key \--populate parabola -    # pacman-key \--refresh-keys -    # pacman -Sy parabola-keyring +key and, therefore, you should do:\ +   \# **pacman-key \--populate parabola**\ +   \# **pacman-key \--refresh-keys**\ +   \# **pacman -Sy parabola-keyring**\    To be honest, you should do the above anyway. Parabola has a lot of -maintainers, and a lot of keys. Really! - -   If you get an error mentioning dirmngr, do: - -    # dirmngr </dev/null +maintainers, and a lot of keys. Really!\ +   If you get an error mentioning dirmngr, do:\ +   \# **dirmngr </dev/null**\    Also, it says that if the clock is set incorrectly then you have to -manually set the correct time - -   (if keys are listed as expired because of it): - -    # date MMDDhhmm\[\[CC\]YY\]\[.ss\] -   I also had to install: - -    # pacman -S archlinux-keyring -    # pacman-key \--populate archlinux +manually set the correct time\ +   (if keys are listed as expired because of it):\ +   \# **date MMDDhhmm\[\[CC\]YY\]\[.ss\]**\ +   I also had to install:\ +   \# **pacman -S archlinux-keyring**\ +   \# **pacman-key \--populate archlinux**\    In my case I saw some conflicting files reported in pacman, stopping -me from using it. - +me from using it.\    I deleted the files that it mentioned and then it worked. -Specifically, I had this error: - -   *licenses: /usr/share/licenses/common/MPS exists in filesystem* - +Specifically, I had this error:\ +   *licenses: /usr/share/licenses/common/MPS exists in filesystem*\    I rm -Rf'd the file and then pacman worked. I'm told that the -following would have also made it work: - -    # pacman -Sf licenses -</troubleshooting> +following would have also made it work:\ +   \# **pacman -Sf licenses**\ +</troubleshooting>\ I also like to install other packages (base-devel, compilers and so on) and wpa\_supplicant/dialog/iw/wpa\_actiond are needed for wireless after -the install: - -# **pacstrap /mnt base base-devel wpa\_supplicant dialog iw +the install:\ +\# **pacstrap /mnt base base-devel wpa\_supplicant dialog iw wpa\_actiond** + + Configure the system -------------------- Generate an fstab - UUIDs are used because they have certain advantages (see <https://wiki.parabola.nu/Fstab#Identifying_filesystems>. If you -prefer labels instead, replace the -U option with -L): - - # genfstab -U -p /mnt >> /mnt/etc/fstab -Check the created file: - - # cat /mnt/etc/fstab +prefer labels instead, replace the -U option with -L):\ +\# **genfstab -U -p /mnt >> /mnt/etc/fstab**\ +Check the created file:\ +\# **cat /mnt/etc/fstab**\ (If there are any errors, edit the file. Do **NOT** run the genfstab command again!) -Chroot into new system: +Chroot into new system:\ +\# **arch-chroot /mnt /bin/bash** -# **arch-chroot /mnt /bin/bash** - -It's a good idea to have this installed: - -# **pacman -S linux-libre-lts** +It's a good idea to have this installed:\ +\# **pacman -S linux-libre-lts** It was also suggested that you should install this kernel (read up on -what GRSEC is): - -# **pacman -S linux-libre-grsec** +what GRSEC is):\ +\# **pacman -S linux-libre-grsec** This is another kernel that sits inside /boot, which you can use. LTS means 'long-term support'. These are so-called 'stable' kernels that can be used as a fallback during updates, if a bad kernel causes issues for you. -Parabola does not have wget. This is sinister. Install it: - -# **pacman -S wget** +Parabola does not have wget. This is sinister. Install it:\ +\# **pacman -S wget** -Locale: - - # vi /etc/locale.gen +Locale:\ +\# **vi /etc/locale.gen**\ Uncomment your needed localisations. For example en\_GB.UTF-8 (UTF-8 is -highly recommended over other options). - - # locale-gen - # echo LANG=en\_GB.UTF-8 > /etc/locale.conf -# **export LANG=en\_GB.UTF-8** +highly recommended over other options).\ +\# **locale-gen**\ +\# **echo LANG=en\_GB.UTF-8 > /etc/locale.conf**\ +\# **export LANG=en\_GB.UTF-8** -Console font and keymap: - - # vi /etc/vconsole.conf +Console font and keymap:\ +\# **vi /etc/vconsole.conf**\ In my case: KEYMAP=dvorak-uk FONT=lat9w-16 -Time zone: - - # ln -s /usr/share/zoneinfo/Europe/London /etc/localtime +Time zone:\ +\# **ln -s /usr/share/zoneinfo/Europe/London /etc/localtime**\ (Replace Zone and Subzone to your liking. See /usr/share/zoneinfo) -Hardware clock: - -# **hwclock \--systohc \--utc** +Hardware clock:\ +\# **hwclock \--systohc \--utc** Hostname: Write your hostname to /etc/hostname. For example, if your -hostname is parabola: - - # echo parabola > /etc/hostname -Add the same hostname to /etc/hosts: - - # vi /etc/hosts +hostname is parabola:\ +\# **echo parabola > /etc/hostname**\ +Add the same hostname to /etc/hosts:\ +\# **vi /etc/hosts**\ #<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost parabola @@ -410,10 +375,9 @@ Configure the network: Refer to Mkinitcpio: Configure /etc/mkinitcpio.conf as needed (see <https://wiki.parabola.nu/Mkinitcpio>). Runtime modules can be found in /usr/lib/initcpio/hooks, and build hooks can be found in -/usr/lib/initcpio/install. (# **mkinitcpio -H hookname** gives -information about each hook.) Specifically, for this use case: - - # vi /etc/mkinitcpio.conf +/usr/lib/initcpio/install. (\# **mkinitcpio -H hookname** gives +information about each hook.) Specifically, for this use case:\ +\# **vi /etc/mkinitcpio.conf**\ Then modify the file like so: - MODULES="i915" @@ -437,54 +401,44 @@ Then modify the file like so: Now using mkinitcpio, you can create the kernel and ramdisk for booting with (this is different from Arch, specifying linux-libre instead of -linux): - - # mkinitcpio -p linux-libre -Also do it for linux-libre-lts: - - # mkinitcpio -p linux-libre-lts -Also do it for linux-libre-grsec: - -# **mkinitcpio -p linux-libre-grsec** +linux):\ +\# **mkinitcpio -p linux-libre**\ +Also do it for linux-libre-lts:\ +\# **mkinitcpio -p linux-libre-lts**\ +Also do it for linux-libre-grsec:\ +\# **mkinitcpio -p linux-libre-grsec** Set the root password: At the time of writing, Parabola used SHA512 by default for its password hashing. I referred to -<https://wiki.archlinux.org/index.php/SHA_password_hashes>. - - # vi /etc/pam.d/passwd -Add rounds=65536 at the end of the uncommented 'password' line. - - # passwd root +<https://wiki.archlinux.org/index.php/SHA_password_hashes>.\ +\# **vi /etc/pam.d/passwd**\ +Add rounds=65536 at the end of the uncommented 'password' line.\ +\# **passwd root**\ Make sure to set a secure password! Also, it must never be the same as your LUKS password. Use of the *diceware method* is recommended, for generating secure passphrases (instead of passwords). + + Extra security tweaks --------------------- Based on <https://wiki.archlinux.org/index.php/Security>. -Restrict access to important directories: - -# **chmod 700 /boot /etc/{iptables,arptables}** - -Lockout user after three failed login attempts: - -Edit the file /etc/pam.d/system-login and comment out that line: - -*# auth required pam\_tally.so onerr=succeed file=/var/log/faillog* - -Or just delete it. Above it, put: +Restrict access to important directories:\ +\# **chmod 700 /boot /etc/{iptables,arptables}** +Lockout user after three failed login attempts:\ +Edit the file /etc/pam.d/system-login and comment out that line:\ +*\# auth required pam\_tally.so onerr=succeed file=/var/log/faillog*\ +Or just delete it. Above it, put:\ *auth required pam\_tally.so deny=2 unlock\_time=600 onerr=succeed -file=/var/log/faillog* - +file=/var/log/faillog*\ To unlock a user manually (if a password attempt is failed 3 times), -do: - -# **pam\_tally \--user *theusername* \--reset** What the above +do:\ +\# **pam\_tally \--user *theusername* \--reset** What the above configuration does is lock the user out for 10 minutes, if they make 3 failed login attempts. @@ -492,29 +446,29 @@ Configure sudo - not covered here. Will be covered post-installation in another tutorial, at a later date. If this is a single-user system, you don't really need sudo. -Unmount, reboot! ----------------- -Exit from chroot: -# **exit** +Unmount, reboot! +---------------- -unmount: +Exit from chroot:\ +\# **exit** - # umount -R /mnt -# **swapoff -a** +unmount:\ +\# **umount -R /mnt**\ +\# **swapoff -a** -deactivate the lvm lv's: +deactivate the lvm lv's:\ +\# **lvchange -an /dev/matrix/root**\ +\# **lvchange -an /dev/matrix/swapvol**\ - # lvchange -an /dev/matrix/root - # lvchange -an /dev/matrix/swapvol +Lock the encrypted partition (close it):\ +\# **cryptsetup luksClose lvm** -Lock the encrypted partition (close it): +\# **shutdown -h now**\ +Remove the installation media, then boot up again. -# **cryptsetup luksClose lvm** - # shutdown -h now -Remove the installation media, then boot up again. Booting from GRUB ----------------- @@ -523,17 +477,18 @@ Initially you will have to boot manually. Press C to get to the GRUB command line. The underlined parts are optional (using those 2 underlines will boot lts kernel instead of normal). -grub> cryptomount -a -grub> set root='lvm/matrix-root' +grub> **cryptomount -a**\ +grub> **set root='lvm/matrix-root'**\ grub> **linux /boot/vmlinuz-linux-libre-lts root=/dev/matrix/root -cryptdevice=/dev/sda1:root** - -grub> initrd /boot/initramfs-linux-libre-lts.img -grub> boot +cryptdevice=/dev/sda1:root**\ +grub> **initrd /boot/initramfs-linux-libre-lts.img**\ +grub> **boot**\ You could also make it load /boot/vmlinuz-linux-libre-grsec and /boot/initramfs-linux-libre-grsec.img + + Follow-up tutorial: configuring Parabola ---------------------------------------- @@ -549,6 +504,8 @@ means that you are in control. For more information, read [The Arch Way](https://wiki.archlinux.org/index.php/The_Arch_Way) (Parabola also follows it). + + Modify grub.cfg inside the ROM ------------------------------ @@ -563,21 +520,16 @@ possibility of bricking your device! I will go for the re-flash option here. Firstly, cd to the libreboot\_util/cbfstool/{armv7l i686 x86\_64} directory. Dump the current firmware - where *libreboot.rom* is an example: make sure to -adapt: - - # flashrom -p internal -r libreboot.rom +adapt:\ +\# **flashrom -p internal -r libreboot.rom**\ If flashrom complains about multiple flash chips detected, add a *-c* -option at the end, with the name of your chosen chip is quotes. - +option at the end, with the name of your chosen chip is quotes.\ You can check if everything is in there (*grub.cfg* and *grubtest.cfg* -would be really nice): - - $ ./cbfstool libreboot.rom print -Extract grubtest.cfg: - - $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg -And modify: - +would be really nice):\ +\$ **./cbfstool libreboot.rom print**\ +Extract grubtest.cfg:\ +\$ **./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg**\ +And modify:\ \$ **vi grubtest.cfg** In grubtest.cfg, inside the 'Load Operating System' menu entry, change @@ -606,24 +558,20 @@ detected LUKS volumes. You can also specify -u UUID or -a (device). hardening your GRUB configuration, for security purposes. Save your changes in grubtest.cfg, then delete the unmodified config -from the ROM image: - - $ ./cbfstool libreboot.rom remove -n grubtest.cfg -and insert the modified grubtest.cfg: - +from the ROM image:\ +\$ **./cbfstool libreboot.rom remove -n grubtest.cfg**\ +and insert the modified grubtest.cfg:\ \$ **./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t -raw** +raw**\ Now refer to <http://libreboot.org/docs/install/#flashrom>. Cd (up) to -the libreboot\_util directory and update the flash chip contents: - - # ./flash update libreboot.rom +the libreboot\_util directory and update the flash chip contents:\ +\# **./flash update libreboot.rom**\ 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: - - # ./flash forceupdate libreboot.rom -You should see "Verifying flash... VERIFIED." written at the end of +correct ROM image, then run this alternative command:\ +\# **./flash forceupdate libreboot.rom**\ +You should see "Verifying flash\... VERIFIED." written at the end of the flashrom output. With this new configuration, Parabola can boot automatically and you @@ -636,7 +584,7 @@ LUKS passphrase and login as root/your user. All went well? Great! If it does not work like you want it to, if you are unsure or sceptical in any way, don't despair: you have been wise and did not brick your device! Reboot and login the default way, and then modify your -grubtest.cfg until you get it right! **Do *not* proceed past this +grubtest.cfg until you get it right! **Do \*not\* proceed past this point unless you are 100% sure that your new configuration is safe (or desirable) to use.** @@ -648,37 +596,35 @@ the main config still links (in the menu) to grubtest.cfg, so that you don't have to manually switch to it, in case you ever want to follow this guide again in the future (modifying the already modified config). Inside libreboot\_util/cbfstool/{armv7l i686 x86\_64}, we can do this -with the following command: - +with the following command:\ \$ **sed -e 's:(cbfsdisk)/grub.cfg:(cbfsdisk)/grubtest.cfg:g' -e 's:Switch to grub.cfg:Switch to grubtest.cfg:g' < grubtest.cfg > -grub.cfg** - -Delete the grub.cfg that remained inside the ROM: - - $ ./cbfstool libreboot.rom remove -n grub.cfg -Add the modified version that you just made: - - $ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw +grub.cfg**\ +Delete the grub.cfg that remained inside the ROM:\ +\$ **./cbfstool libreboot.rom remove -n grub.cfg**\ +Add the modified version that you just made:\ +\$ **./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw**\ Now you have a modified ROM. Once more, refer to <http://libreboot.org/docs/install/#flashrom>. Cd to the libreboot\_util -directory and update the flash chip contents: - - # ./flash update libreboot.rom -And wait for the "Verifying flash... VERIFIED." Once you have done +directory and update the flash chip contents:\ +\# **./flash update libreboot.rom**\ +And wait for the "Verifying flash\... VERIFIED." Once you have done that, shut down and then boot up with your new configuration. When done, delete GRUB (remember, we only needed it for the *grub-mkpasswd-pbkdf2* utility; GRUB is already part of libreboot, -flashed alongside it as a *payload*): +flashed alongside it as a *payload*):\ +\# **pacman -R grub** + -# **pacman -R grub** If you followed all that correctly, you should now have a fully encrypted Parabola installation. Refer to the wiki for how to do the rest. + + Bonus: Using a key file to unlock /boot/ ---------------------------------------- @@ -689,40 +635,36 @@ fact that it is being loaded from an encrypted volume. Therefore, you will be asked to enter your passphrase a second time. A workaround is to put a keyfile inside initramfs, with instructions for the kernel to use it when booting. This is safe, because /boot/ is encrypted (otherwise, -putting a keyfile inside initramfs would be a bad idea). - -Boot up and login as root or your user. Then generate the key file: - -# **dd bs=512 count=4 if=/dev/urandom of=/etc/mykeyfile -iflag=fullblock** - -Insert it into the luks volume: - - # cryptsetup luksAddKey /dev/sdX /etc/mykeyfile +putting a keyfile inside initramfs would be a bad idea).\ +Boot up and login as root or your user. Then generate the key file:\ +\# **dd bs=512 count=4 if=/dev/urandom of=/etc/mykeyfile +iflag=fullblock**\ +Insert it into the luks volume:\ +\# **cryptsetup luksAddKey /dev/sdX /etc/mykeyfile**\ and enter your LUKS passphrase when prompted. Add the keyfile to the -initramfs by adding it to FILES in /etc/mkinitcpio.conf. For example: - - # FILES="/etc/mykeyfile" -Create the initramfs image from scratch: - - # mkinitcpio -p linux-libre - # mkinitcpio -p linux-libre-lts - # mkinitcpio -p linux-libre-grsec +initramfs by adding it to FILES in /etc/mkinitcpio.conf. For example:\ +\# **FILES="/etc/mykeyfile"**\ +Create the initramfs image from scratch:\ +\# **mkinitcpio -p linux-libre**\ +\# **mkinitcpio -p linux-libre-lts**\ +\# **mkinitcpio -p linux-libre-grsec**\ Add the following to your grub.cfg - you are now able to do that, see -above! -, or add it in the kernel command line for GRUB: - - # cryptkey=rootfs:/etc/mykeyfile - +above! -, or add it in the kernel command line for GRUB:\ +\# **cryptkey=rootfs:/etc/mykeyfile**\ +\ You can also place this inside the grub.cfg that exists in CBFS: [grub\_cbfs.html](grub_cbfs.html). + + Further security tips --------------------- -<https://wiki.archlinux.org/index.php/Security>. - +<https://wiki.archlinux.org/index.php/Security>.\ <https://wiki.parabolagnulinux.org/User:GNUtoo/laptop> + + Troubleshooting =============== @@ -734,6 +676,7 @@ station. Further investigation revealed that it was the DVD drive causing problems. Removing that worked around the issue. + "sudo wodim -prcap" shows information about the drive: Device was not specified. Trying to find an appropriate drive... Detected CD-R drive: /dev/sr0 @@ -810,10 +753,10 @@ problems. Removing that worked around the issue. Does write ultra high speed CD-RW media Does not write ultra high speed+ CD-RW media -Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org> -Copyright © 2015 Jeroen Quint <jezza@diplomail.ch> +Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\ +Copyright © 2015 Jeroen Quint <jezza@diplomail.ch>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md @@ -1,4 +1,6 @@ -% How to install GNU+Linux on a libreboot system + +How to install GNU+Linux on a libreboot system +============================================== This section relates to preparing, booting and installing a GNU+Linux distribution on your libreboot system, using nothing more than a USB @@ -14,38 +16,40 @@ flash drive (and *dd*). [Back to previous index](./) + + **This section is only for the GRUB payload. For depthcharge (used on CrOS devices in libreboot), instructions have yet to be written in the libreboot documentation.** + + 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: - - $ dmesg -Check lsblk to confirm which drive it is: - - $ lsblk +Connect the USB drive. Check dmesg:\ +**\$ dmesg**\ +Check lsblk to confirm which drive it is:\ +**\$ lsblk** Check that it wasn't automatically mounted. If it was, unmount it. For -example: - - $ sudo umount /dev/sdX* - # umount /dev/sdX* +example:\ +**\$ sudo umount /dev/sdX\***\ +**\# umount /dev/sdX\*** dmesg told you what device it is. Overwrite the drive, writing your -distro ISO to it with dd. For example: - - $ sudo dd if=gnulinux.iso of=/dev/sdX bs=8M; sync - # dd if=gnulinux.iso of=/dev/sdX bs=8M; sync +distro ISO to it with dd. For example:\ +**\$ sudo dd if=gnulinux.iso of=/dev/sdX bs=8M; sync**\ +**\# dd if=gnulinux.iso of=/dev/sdX bs=8M; sync** You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. +[Back to top of page](#pagetop). + Prepare the USB drive (in NetBSD) --------------------------------- @@ -69,26 +73,26 @@ 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 GNU+Linux USB drive: -Connect the USB drive. Check dmesg: - - $ dmesg | tail -Check to confirm which drive it is, for example, if you think its sd3: - - $ disklabel sd3 +Connect the USB drive. Check dmesg:\ +**\$ dmesg | tail**\ +Check to confirm which drive it is, for example, if you think its sd3:\ +**\$ disklabel sd3** Check that it wasn't automatically mounted. If it was, unmount it. For -example: - - $ doas umount /dev/sd3i +example:\ +**\$ doas umount /dev/sd3i**\ dmesg told you what device it is. Overwrite the drive, writing the -OpenBSD installer to it with dd. For example: - - $ doas dd if=gnulinux.iso of=/dev/rsdXc bs=1M; sync +OpenBSD installer to it with dd. For example:\ +**\$ doas dd if=gnulinux.iso of=/dev/rsdXc bs=1M; sync**\ You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. +[Back to top of page](#pagetop). + + + Installing GNU+Linux with full disk encryption ---------------------------------------------- @@ -97,33 +101,31 @@ Installing GNU+Linux with full disk encryption - [Installing Parabola GNU+Linux with full disk encryption (including /boot)](encrypted_parabola.html) +[Back to top of page](#pagetop). + + + Debian or Devuan net install? ----------------------------- Download the Debian or Devuan net installer. You can download the ISO from the homepage on [debian.org](https://www.debian.org/), or [the Devuan homepage](https://www.devuan.org/) for Devuan. Use this on the -GRUB terminal to boot it from USB (for 64-bit Intel or AMD): - -**set root='usb0' - -linux /install.amd/vmlinuz - -initrd /install.amd/initrd.gz - -boot - -** If you are on a 32-bit system (e.g. X60): - -**set root='usb0' - -linux /install.386/vmlinuz +GRUB terminal to boot it from USB (for 64-bit Intel or AMD):\ +**set root='usb0'\ +linux /install.amd/vmlinuz\ +initrd /install.amd/initrd.gz\ +boot\ +** If you are on a 32-bit system (e.g. X60):\ +**set root='usb0'\ +linux /install.386/vmlinuz\ +initrd /install.386/initrd.gz\ +boot**\ +We recommend using the *MATE* desktop. -initrd /install.386/initrd.gz +[Back to top of page](#pagetop). -boot** -We recommend using the *MATE* desktop. Booting ISOLINUX images (automatic method) ------------------------------------------ @@ -133,6 +135,10 @@ menu should appear in GRUB, showing the boot options for that distro; this is a GRUB menu, converted from the usual ISOLINUX menu provided by that distro. +[Back to top of page](#pagetop). + + + Booting ISOLINUX images (manual method) --------------------------------------- @@ -141,18 +147,14 @@ distribution. You must adapt them appropriately, for whatever GNU+Linux distribution it is that you are trying to install.* If the ISOLINUX parser or *Search for GRUB configuration* options won't -work, then press C in GRUB to access the command line. - -grub> ls -Get the device from above output, eg (usb0). Example: - -grub> cat (usb0)/isolinux/isolinux.cfg +work, then press C in GRUB to access the command line.\ +grub> **ls**\ +Get the device from above output, eg (usb0). Example:\ +grub> **cat (usb0)/isolinux/isolinux.cfg**\ Either this will show the ISOLINUX menuentries for that ISO, or link to -other .cfg files, for example /isolinux/foo.cfg. - -If it did that, then you do: - -grub> cat (usb0)/isolinux/foo.cfg +other .cfg files, for example /isolinux/foo.cfg.\ +If it did that, then you do:\ +grub> **cat (usb0)/isolinux/foo.cfg**\ And so on, until you find the correct menuentries for ISOLINUX. **The file */isolinux/foo.cfg* is a fictional example. Do not actually use this example, unless you actually have that file, if it is @@ -168,24 +170,24 @@ options in txt.cfg. This is important if you want 64-bit booting on your system. Devuan versions based on Debian 8.x may also have the same issue. -Now look at the ISOLINUX menuentry. It'll look like: - -**kernel /path/to/kernel - -append PARAMETERS initrd=/path/to/initrd MAYBE\_MORE\_PARAMETERS - +Now look at the ISOLINUX menuentry. It'll look like:\ +**kernel /path/to/kernel\ +append PARAMETERS initrd=/path/to/initrd MAYBE\_MORE\_PARAMETERS\ ** GRUB works the same way, but in it's own way. Example GRUB -commands: - -grub> set root='usb0' -grub> linux /path/to/kernel PARAMETERS MAYBE\_MORE\_PARAMETERS -grub> initrd /path/to/initrd -grub> boot +commands:\ +grub> **set root='usb0'**\ +grub> **linux /path/to/kernel PARAMETERS MAYBE\_MORE\_PARAMETERS**\ +grub> **initrd /path/to/initrd**\ +grub> **boot**\ Note: *usb0* may be incorrect. Check the output of the *ls* command in GRUB, to see a list of USB devices/partitions. Of course this will vary from distro to distro. If you did all of that correctly, then it should now be booting your USB drive in the way that you specified. +[Back to top of page](#pagetop). + + + Troubleshooting =============== @@ -211,8 +213,7 @@ When using the ROM images that use coreboot's "text mode" instead of the coreboot framebuffer, booting the Debian or Devuan net installer results in graphical corruption because it is trying to switch to a framebuffer which doesn't exist. Use that kernel parameter on the -'linux' line when booting it: - +'linux' line when booting it:\ **vga=normal fb=false** This forces debian-installer to start in text-mode, instead of trying to @@ -227,10 +228,12 @@ This workaround was found on the page: also work for Debian, Devuan and any other apt-get distro that provides debian-installer (text mode) net install method. -Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org> +[Back to top of page](#pagetop). + -Copyright © 2016 Scott Bonds <scott@ggr.com> +Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\ +Copyright © 2016 Scott Bonds <scott@ggr.com>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md @@ -1,4 +1,6 @@ -% How to replace the default GRUB configuration file on a libreboot system + +How to replace the default GRUB configuration file on a libreboot system +======================================================================== Libreboot on x86 uses the GRUB [payload](http://www.coreboot.org/Payloads#GRUB_2) by default, which @@ -22,11 +24,13 @@ the libreboot GRUB payload will automatically search for. Here is an excellent writeup about CBFS (coreboot filesystem): <http://lennartb.home.xs4all.nl/coreboot/col5.html>. -**This guide is *only* for the GRUB payload. If you use the +**This guide is \*only\* for the GRUB payload. If you use the depthcharge payload, ignore this section entirely.** [Back to previous index](./) + + Table of Contents ================= @@ -41,13 +45,14 @@ Table of Contents - [Testing](#testing) - [Final steps](#final_steps) + + Introduction ------------ -Download the latest release from <http://libreboot.org/> - +Download the latest release from <http://libreboot.org/>\ **If you downloaded from git, refer to -[../git/#build\_meta](../git/#build_meta) before continuing.** +[../git/\#build\_meta](../git/#build_meta) before continuing.** [Back to top of page.](#pagetop) @@ -61,6 +66,8 @@ If you aren't up to that then don't worry; it is possible to use a custom GRUB menu without flashing a new image, by loading a GRUB configuration from a partition on the main storage instead. + + 1st option: don't re-flash {#option1_dont_reflash} --------------------------- @@ -87,8 +94,8 @@ coreboot payload) that is located in a partition on the main storage. If you want to adapt a copy of the existing *libreboot* GRUB configuration and use that for the libreboot\_grub.cfg file, then follow -[#tools](#tools), [\#rom](#rom) and -[#extract\_testconfig](#extract_testconfig) to get the +[\#tools](#tools), [\#rom](#rom) and +[\#extract\_testconfig](#extract_testconfig) to get the ***grubtest.cfg***. Rename ***grubtest.cfg*** to ***libreboot\_grub.cfg*** and save it to ***/boot/grub/*** on the running system where it is intended to be used. Modify the file at that @@ -99,6 +106,8 @@ for libreboot\_grub.cfg otherwise it will loop.**. [Back to top of page.](#pagetop) + + 2nd option: re-flash {#option2_reflash} -------------------- @@ -107,18 +116,21 @@ on to find out how. [Back to top of page.](#pagetop) + + Acquire the necessary utilities {#tools} ------------------------------- Use ***cbfstool*** and ***flashrom***. There are available in the *libreboot\_util* release archive, or they can be compiled (see -[../git/#build\_flashrom](../git/#build_flashrom)). Flashrom is also -available from the repositories: - -# **pacman -S flashrom** +[../git/\#build\_flashrom](../git/#build_flashrom)). Flashrom is also +available from the repositories:\ +\# **pacman -S flashrom** [Back to top of page.](#pagetop) + + Acquiring the correct ROM image {#rom} ------------------------------- @@ -128,23 +140,22 @@ flashed. For the purpose of this tutorial it is assumed that your ROM image file is named *libreboot.rom*, so please make sure to adapt. ROM images are included pre-compiled in libreboot. You can also dump -your current firmware, using flashrom: - - $ sudo flashrom -p internal -r libreboot.rom - # flashrom -p internal -r libreboot.rom +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: - -# **flashrom -c MX25L6405 -p internal -r libreboot.rom** +to the command, for example:\ +\# **flashrom -c MX25L6405 -p internal -r libreboot.rom** [Back to top of page.](#pagetop) + + Extract grubtest.cfg from the ROM image {#extract_testconfig} --------------------------------------- -You can check the contents of the ROM image, inside CBFS: - - $ cd .../libreboot\_util/cbfstool** \$ ./cbfstool libreboot.rom +You can check the contents of the ROM image, inside CBFS:\ +**\$ cd \.../libreboot\_util/cbfstool** **\$ ./cbfstool libreboot.rom print** The files *grub.cfg* and *grubtest.cfg* should be present. grub.cfg is @@ -152,43 +163,42 @@ loaded by default, with a menuentry for switching to grubtest.cfg. In this tutorial, you will first modify and test *grubtest.cfg*. This is to reduce the possibility of bricking your device, so DO NOT SKIP THIS! -Extract grubtest.cfg from the ROM image: - - $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg +Extract grubtest.cfg from the ROM image:\ +**\$ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg** Modify the grubtest.cfg accordingly. [Back to top of page.](#pagetop) + + Re-insert the modified grubtest.cfg into the ROM image {#reinsert_modified_testconfig} ------------------------------------------------------ Once your grubtest.cfg is modified and saved, delete the unmodified -config from the ROM image: - - $ ./cbfstool libreboot.rom remove -n grubtest.cfg - -Next, insert the modified version: +config from the ROM image:\ +**\$ ./cbfstool libreboot.rom remove -n grubtest.cfg** +Next, insert the modified version:\ **\$ ./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t raw** [Back to top of page.](#pagetop) + + Testing ------- **Now you have a modified ROM. Refer back to -[../install/#flashrom](../install/#flashrom) for information on how to -flash it. - - $ cd /libreboot\_util** # **./flash update libreboot.rom +[../install/\#flashrom](../install/#flashrom) for information on how to +flash it.\ +\$ **cd /libreboot\_util** \# **./flash update libreboot.rom**\ 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: - - # ./flash forceupdate libreboot.rom -You should see **"Verifying flash... VERIFIED."** written at the end +correct ROM image, then run this alternative command:\ +\# **./flash forceupdate libreboot.rom**\ +You should see **"Verifying flash\... VERIFIED."** written at the end of the flashrom output. Once you have done that, shut down and then boot up with your new test configuration.** @@ -197,11 +207,13 @@ works, then your config is safe and you can continue below. **If it does not work like you want it to, if you are unsure or sceptical in any way, then re-do the steps above until you get it right! -Do *not* proceed past this point unless you are 100% sure that your +Do \*not\* proceed past this point unless you are 100% sure that your new configuration is safe (or desirable) to use.** [Back to top of page.](#pagetop) + + Final steps {#final_steps} ----------- @@ -212,31 +224,28 @@ difference: the menuentry 'Switch to grub.cfg' will be changed to grubtest.cfg. This is so that the main config still links (in the menu) to grubtest.cfg, so that you don't have to manually switch to it, in case you ever want to follow this guide again in the future (modifying -the already modified config). From /libreboot\_util/cbfstool, do: - +the already modified config). From /libreboot\_util/cbfstool, do:\ \$ **sed -e 's:(cbfsdisk)/grub.cfg:(cbfsdisk)/grubtest.cfg:g' -e 's:Switch to grub.cfg:Switch to grubtest.cfg:g' < grubtest.cfg > -grub.cfg** - -Delete the grub.cfg that remained inside the ROM: - - $ ./cbfstool libreboot.rom remove -n grub.cfg +grub.cfg**\ -Add the modified version that you just made: +Delete the grub.cfg that remained inside the ROM:\ +**\$ ./cbfstool libreboot.rom remove -n grub.cfg** - $ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw +Add the modified version that you just made:\ +**\$ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw** **Now you have a modified ROM. Again, refer back to -[../install/#flashrom](../install/#flashrom) for information on how to +[../install/\#flashrom](../install/#flashrom) for information on how to flash it. It's the same method as you used before. Shut down and then boot up with your new configuration.** [Back to top of page.](#pagetop) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> -Copyright © 2015 Jeroen Quint <jezza@diplomail.ch> +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ +Copyright © 2015 Jeroen Quint <jezza@diplomail.ch>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md @@ -1,4 +1,6 @@ -% GRUB hardening + +GRUB hardening +============== This guide deals with various ways in which you can harden your GRUB configuration, for security purposes. These steps are optional, but @@ -6,6 +8,8 @@ highly recommended by the Libreboot project. [Back to previous index](./) + + GRUB secure boot with GPG ========================= @@ -32,7 +36,7 @@ image: Helpful links: - [GRUB manual - #security](https://www.gnu.org/software/grub/manual/html_node/Security.html#Security) + \#security](https://www.gnu.org/software/grub/manual/html_node/Security.html#Security) - [GRUB info pages](http://git.savannah.gnu.org/cgit/grub.git/tree/docs/grub.texi) - [SATA connected storage considered dangerous until proven @@ -40,6 +44,8 @@ Helpful links: - [Coreboot GRUB security howto](https://www.coreboot.org/GRUB2#Security) + + GRUB Password ============= @@ -111,12 +117,12 @@ configurations, is to remove (or comment out) **unset superusers** in function try\_user\_config: function try_user_config { - set root="\${1}" + set root="${1}" for dir in boot grub grub2 boot/grub boot/grub2; do for name in '' autoboot_ libreboot_ coreboot_; do - if [ -f /"\${dir}"/"\${name}"grub.cfg ]; then + if [ -f /"${dir}"/"${name}"grub.cfg ]; then #unset superusers - configfile /"\${dir}"/"\${name}"grub.cfg + configfile /"${dir}"/"${name}"grub.cfg fi done done @@ -131,6 +137,8 @@ an attacker wants is then just a few GRUB commands away. As far as basic password setup is concerned we are done and we can now move on to signing. + + GPG keys ======== @@ -138,7 +146,7 @@ First generate a GPG keypair to use for signing. Option RSA (sign only) is ok. **Warning:** GRUB does not read ASCII armored keys. When attempting to -trust ... a key filename it will print error: bad signature +trust \... a key filename it will print error: bad signature mkdir --mode 0700 keys gpg --homedir keys --gen-key @@ -176,10 +184,11 @@ What remains now is to include the modifications into the image (rom): cbfstool my.rom add -n grubtest.cfg -f my.grubtest.cfg -t raw cbfstool my.rom add -n grubtest.cfg.sig -f my.grubtest.cfg.sig -t raw -... and flashing it. +\... and flashing it. + -Copyright © 2017 Fedja Beader <fedja@protonmail.ch> +Copyright © 2017 Fedja Beader <fedja@protonmail.ch>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/gnulinux/index.md b/docs/gnulinux/index.md @@ -1,9 +1,11 @@ -% GNU+Linux distributions + +GNU+Linux distributions +======================= This section relates to dealing with GNU+Linux distributions: preparing bootable USB drives, changing the default GRUB menu and so on. -**This section is only for the *GRUB* payload. For depthcharge, +**This section is only for the \*GRUB\* payload. For depthcharge, instructions have yet to be written.** [Back to previous index](../). @@ -21,8 +23,9 @@ instructions have yet to be written.** - [How to harden your GRUB configuration, for security](grub_hardening.html) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/grub/index.md b/docs/grub/index.md @@ -1,26 +1,32 @@ -% GRUB payload + +GRUB payload +============ This section relates to the GRUB payload used in libreboot. + - [Changing the background image in GRUB](#grub_background) - [Setting font in GRUB](#grub_font) - [GRUB keyboard layouts](#grub_keyboard) - [Custom keyboard layout in GRUB](#grub_custom_keyboard) - [UK Dvorak keyboard layout in GRUB](#grub_ukdvorak_keyboard) + + Changing the background image in GRUB {#grub_background} ===================================== Use cbfstool from libreboot\_util, or libreboot\_src/coreboot/util/cbfstool/ if you want to build from source. -./cbfstool yourrom.rom remove background.png -n background.png - +./cbfstool yourrom.rom remove background.png -n background.png\ ./cbfstool yourrom.rom add -f background.png -n background.png -t raw When you've done this, re-flash your ROM and you should have a new background at boot time. + + Setting font in GRUB (for reference) {#grub_font} ==================================== @@ -41,42 +47,40 @@ one](http://sourceforge.net/projects/dejavu/files/dejavu/2.34/dejavu-fonts-ttf-2 This is a free font that is also contained in GNU+Linux distributions 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: - - $ cd ../libreboot\_src/resources/grub/font +**\$ cd libreboot\_src/grub**\ +compile grub (the build scripts info on how to do this)\ +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 -libreboot) and did: - +libreboot) and did:\ **\$ ../../../grub/grub-mkfont -o dejavusansmono.pf2 dejavu-fonts-ttf-2.34/ttf/DejaVuSansMono.ttf** I then added the instructions to 'gen.sh' script in grub-assemble to include resources/grub/dejavusansmono.pf2 in all of the ROM images, at -the root of the GRUB memdisk. - +the root of the GRUB memdisk.\ I then added that instructions to the grub.cfg files (to load the -font): - +font):\ **loadfont (memdisk)/dejavusansmono.pf2** +[Back to top of page](#pagetop) + + + GRUB keyboard layouts (for reference) {#grub_keyboard} ===================================== + Custom keyboard layout in GRUB (for reference) {#grub_custom_keyboard} ---------------------------------------------- Keymaps are stored in resources/utilities/grub-assemble/keymap/. -Example (French Azerty): - - $ ckbcomp fr > frazerty - -Go in grub directory: - +Example (French Azerty):\ +**\$ ckbcomp fr > frazerty**\ +\ +Go in grub directory:\ **cat frazerty | ./grub/grub-mklayout -o frazerty.gkb** You must make sure that the files are named keymap and keymap.gkb (where @@ -91,6 +95,10 @@ The build scripts will automatically see this, and automatically build ROM images with your custom layout (given the name) and include them under bin. Example: **libreboot\_frazerty.rom**. +[Back to top of page](#pagetop) + + + UK Dvorak keyboard layout in GRUB (for reference) {#grub_ukdvorak_keyboard} ------------------------------------------------- @@ -98,10 +106,14 @@ ukdvorak had to be created manually, based on usdvorak. diff them (under resources/utilities/grub-assemble/keymap/original) to see how ukdvorak file was created - $ cat ukdvorak | ./grub/grub-mklayout -o ukdvorak.gkb +**\$ cat ukdvorak | ./grub/grub-mklayout -o ukdvorak.gkb** + +[Back to top of page](#pagetop) + + -Copyright © 2014 Leah Rowe <info@minifree.org> +Copyright © 2014 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hardware/dock.md b/docs/hardware/dock.md @@ -1,4 +1,9 @@ -% Notes about DMA and the docking station (X60/T60) + +Notes about DMA and the docking station (X60/T60) +================================================= + + + Use case: --------- @@ -61,6 +66,7 @@ | ICH7 | |_______________________| + The code: --------- Now if I look at the existing code, there is some superio drivers, like @@ -115,8 +121,9 @@ > The dock autodetection is tried only if it is also enabled > trough nvram. -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hardware/index.md b/docs/hardware/index.md @@ -1,4 +1,6 @@ -% Hardware modifications + +Hardware modifications +====================== This section relates to hardware maintenance on supported targets. @@ -14,8 +16,9 @@ This section relates to hardware maintenance on supported targets. - [ThinkPad X60/X60S: hardware security](x60_security.html) - [ThinkPad T60: hardware security](t60_security.html) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hardware/t60_heatsink.md b/docs/hardware/t60_heatsink.md @@ -1,9 +1,13 @@ -% Changing heatsink (or CPU) on the ThinkPad T60 + +Changing heatsink (or CPU) on the ThinkPad T60 +============================================== Using this guide you can also change/upgrade the CPU. [Back to previous index](./) + + Hardware requirements {#hardware_requirements} ===================== @@ -11,35 +15,34 @@ Hardware requirements {#hardware_requirements} changing CPU heatsink (procedure involves removing heatsink) - thermal compound/paste (Arctic MX-4 is good. Others are also good.) + + Software requirements {#software_requirements} ===================== - xsensors - stress + + Disassembly {#recovery} =========== -Remove those screws and remove the HDD: - +Remove those screws and remove the HDD:\ ![](../images/t60_dev/0001.JPG) ![](../images/t60_dev/0002.JPG) -Lift off the palm rest: - +Lift off the palm rest:\ ![](../images/t60_dev/0003.JPG) Lift up the keyboard, pull it back a bit, flip it over like that and -then disconnect it from the board: - +then disconnect it from the board:\ ![](../images/t60_dev/0004.JPG) ![](../images/t60_dev/0005.JPG) ![](../images/t60_dev/0006.JPG) -Gently wedge both sides loose: - +Gently wedge both sides loose:\ ![](../images/t60_dev/0007.JPG) ![](../images/t60_dev/0008.JPG) -Remove that cable from the position: - +Remove that cable from the position:\ ![](../images/t60_dev/0009.JPG) ![](../images/t60_dev/0010.JPG) Remove the bezel (sorry forgot to take pics). @@ -47,8 +50,7 @@ Remove the bezel (sorry forgot to take pics). On the CPU (and there is another chip south-east to it, sorry forgot to take pic) clean off the old thermal paste (with the alcohol) and apply new (Artic Silver 5 is good, others are good too) you should also clean -the heatsink the same way - +the heatsink the same way\ ![](../images/t60_dev/0051.JPG) This is also an opportunity to change the CPU to another one. For @@ -57,39 +59,33 @@ processor (higher speed, 64-bit support). A Core 2 Duo T7600 was installed here. Attach the heatsink and install the screws (also, make sure to install -the AC jack as highlighted): - +the AC jack as highlighted):\ ![](../images/t60_dev/0052.JPG) -Reinstall that upper bezel: - +Reinstall that upper bezel:\ ![](../images/t60_dev/0053.JPG) -Do that: - +Do that:\ ![](../images/t60_dev/0054.JPG) ![](../images/t60_dev/0055.JPG) -Attach keyboard: - +Attach keyboard:\ ![](../images/t60_dev/0056.JPG) Place keyboard and (sorry, forgot to take pics) reinstall the palmrest -and insert screws on the underside: - +and insert screws on the underside:\ ![](../images/t60_dev/0058.JPG) -It lives! - +It lives!\ ![](../images/t60_dev/0071.JPG) ![](../images/t60_dev/0072.JPG) ![](../images/t60_dev/0073.JPG) Always stress test ('stress -c 2' and xsensors. below 90C is ok) when -replacing cpu paste/heatsink: - +replacing cpu paste/heatsink:\ ![](../images/t60_dev/0074.JPG) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hardware/t60_lcd_15.md b/docs/hardware/t60_lcd_15.md @@ -1,4 +1,6 @@ -% Changing the LCD panel on a 15.1" T60 + +Changing the LCD panel on a 15.1" T60 +====================================== This is for the 15.1" T60. If you have another size then the procedure will differ; for example, on 14.1" you have to remove the hinges and @@ -6,54 +8,49 @@ the procedure is a bit more involved than on 15.1". [Back to previous index](./) + + Disassembly {#recovery} =========== -Remove those covers and unscrew: - +Remove those covers and unscrew:\ ![](../images/t60_dev/0059.JPG) ![](../images/t60_dev/0060.JPG) ![](../images/t60_dev/0061.JPG) Gently pry off the front bezel. -Remove inverter board: - +Remove inverter board:\ ![](../images/t60_dev/0064.JPG) -Disconnect LCD cable: - +Disconnect LCD cable:\ ![](../images/t60_dev/0065.JPG) -Remove the panel: - +Remove the panel:\ ![](../images/t60_dev/0066.JPG) Move the rails (left and right side) from the old panel to the new one -and then attach LCD cable: - +and then attach LCD cable:\ ![](../images/t60_dev/0068.JPG) Insert panel (this one is an LG-Philips LP150E05-A2K1, and there are others. See -[../hcl/#supported\_t60\_list](../hcl/#supported_t60_list)): - +[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list)):\ ![](../images/t60_dev/0069.JPG) Insert new inverter board (see -[../hcl/#supported\_t60\_list](../hcl/#supported_t60_list) for what is -recommended on your LCD panel): - +[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list) for what is +recommended on your LCD panel):\ ![](../images/t60_dev/0070.JPG) Now re-attach the front bezel and put all the screws in. -It lives! - +It lives!\ ![](../images/t60_dev/0071.JPG) ![](../images/t60_dev/0072.JPG) ![](../images/t60_dev/0073.JPG) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hardware/t60_security.md b/docs/hardware/t60_security.md @@ -1,10 +1,14 @@ -% Security on the ThinkPad T60 + +Security on the ThinkPad T60 +============================ Hardware modifications to enhance security on the ThinkPad T60. This tutorial is **incomplete** at the time of writing. [Back to previous index](./) + + Table of Contents ================= @@ -26,6 +30,8 @@ Software requirements {#software_requirements} - none (at least in the scope of the article as-is) - You probably want to encrypt your GNU+Linux install using LUKS + + Rationale ========= @@ -37,39 +43,33 @@ memory access that could communicate with inputs/outputs that could be used to remotely command the system (or leak data). All of this is purely theoretical for the time being. + + Disassembly {#procedure} =========== -Remove those screws and remove the HDD: - +Remove those screws and remove the HDD:\ ![](../images/t60_dev/0001.JPG) ![](../images/t60_dev/0002.JPG) -Lift off the palm rest: - +Lift off the palm rest:\ ![](../images/t60_dev/0003.JPG) Lift up the keyboard, pull it back a bit, flip it over like that and -then disconnect it from the board: - +then disconnect it from the board:\ ![](../images/t60_dev/0004.JPG) ![](../images/t60_dev/0005.JPG) ![](../images/t60_dev/0006.JPG) -Gently wedge both sides loose: - +Gently wedge both sides loose:\ ![](../images/t60_dev/0007.JPG) ![](../images/t60_dev/0008.JPG) -Remove that cable from the position: - +Remove that cable from the position:\ ![](../images/t60_dev/0009.JPG) ![](../images/t60_dev/0010.JPG) Now remove that bezel. Remove wifi, nvram battery and speaker connector -(also remove 56k modem, on the left of wifi): - -![](../images/t60_dev/0011.JPG) - +(also remove 56k modem, on the left of wifi):\ +![](../images/t60_dev/0011.JPG)\ Reason: has direct (and very fast) memory access, and could -(theoretically) leak data over a side-channel. - +(theoretically) leak data over a side-channel.\ **Wifi:** The ath5k/ath9k cards might not have firmware at all. They might safe but could have access to the computer's RAM trough DMA. If people have an intel card(most T60 laptops come with Intel wifi by @@ -77,53 +77,41 @@ default, until you change it),then that card runs a non-free firwamre and has access to the computer's RAM trough DMA! So the risk-level is very high. -Remove those screws: - +Remove those screws:\ ![](../images/t60_dev/0012.JPG) -Disconnect the power jack: - +Disconnect the power jack:\ ![](../images/t60_dev/0013.JPG) -Remove nvram battery (we will put it back later): - +Remove nvram battery (we will put it back later):\ ![](../images/t60_dev/0014.JPG) -Disconnect cable (for 56k modem) and disconnect the other cable: - +Disconnect cable (for 56k modem) and disconnect the other cable:\ ![](../images/t60_dev/0015.JPG) ![](../images/t60_dev/0016.JPG) -Disconnect speaker cable: - +Disconnect speaker cable:\ ![](../images/t60_dev/0017.JPG) -Disconnect the other end of the 56k modem cable: - +Disconnect the other end of the 56k modem cable:\ ![](../images/t60_dev/0018.JPG) -Make sure you removed it: - +Make sure you removed it:\ ![](../images/t60_dev/0019.JPG) -Unscrew those: - +Unscrew those:\ ![](../images/t60_dev/0020.JPG) -Make sure you removed those: - +Make sure you removed those:\ ![](../images/t60_dev/0021.JPG) -Disconnect LCD cable from board: - +Disconnect LCD cable from board:\ ![](../images/t60_dev/0022.JPG) -Remove those screws then remove the LCD assembly: - +Remove those screws then remove the LCD assembly:\ ![](../images/t60_dev/0023.JPG) ![](../images/t60_dev/0024.JPG) ![](../images/t60_dev/0025.JPG) -Once again, make sure you removed those: - +Once again, make sure you removed those:\ ![](../images/t60_dev/0026.JPG) Remove the shielding containing the motherboard, then flip it over. @@ -131,18 +119,15 @@ Remove these screws, placing them on a steady surface in the same layout as they were in before you removed them. Also, you should mark each screw hole after removing the screw (a permanent marker pen will do), this is so that you have a point of reference when re-assembling the -system: - +system:\ ![](../images/t60_dev/0027.JPG) ![](../images/t60_dev/0028.JPG) ![](../images/t60_dev/0029.JPG) ![](../images/t60_dev/0031.JPG) ![](../images/t60_dev/0032.JPG) ![](../images/t60_dev/0033.JPG) Remove microphone (soldering iron not needed. Just wedge it out -gently): - -![](../images/t60_dev/0039.JPG) - - Rationale: +gently):\ +![](../images/t60_dev/0039.JPG)\ +**Rationale:**\ Another reason to remove the microphone: If your computer gets[\[1\]](#ref1) compromised, it can record what you say, and use it to receive data from nearby devices if they're compromised too. Also, @@ -151,120 +136,97 @@ could theoretically be programmed to accept remote commands from some speaker somewhere (remote security hole). **In other words, the system could already be compromised from the factory.** -Remove infrared: - +Remove infrared:\ ![](../images/t60_dev/0040.JPG) ![](../images/t60_dev/0042.JPG) Remove cardbus (it's in a socket, no need to disable. Just remove the -port itself): - -![](../images/t60_dev/0041.JPG) - - Rationale: +port itself):\ +![](../images/t60_dev/0041.JPG)\ +**Rationale:**\ It has direct memory access and can be used to extract sensitive details (such as LUKS keys). See 'GoodBIOS' video linked at the end (speaker is Peter Stuge, a coreboot hacker). The video covers X60 but the same topics apply to T60. -Before re-installing the upper chassis, remove the speaker: - -![](../images/t60_dev/0043.JPG) ![](../images/t60_dev/0044.JPG) - +Before re-installing the upper chassis, remove the speaker:\ +![](../images/t60_dev/0043.JPG) ![](../images/t60_dev/0044.JPG)\ Reason: combined with the microphone issue, this could be used to leak -data. - +data.\ If your computer gets[\[1\]](#ref1) compromised, it can be used to transmit data to nearby compromised devices. It's unknown if it can be -turned into a microphone[\[2\]](#ref2). - +turned into a microphone[\[2\]](#ref2).\ Replacement: headphones/speakers (line-out) or external DAC (USB). -Remove the wwan: - -![](../images/t60_dev/0045.JPG) - +Remove the wwan:\ +![](../images/t60_dev/0045.JPG)\ **Wwan (3g modem):** They run proprietary software! It's like AMT but -over the GSM network which is probably even worse. - +over the GSM network which is probably even worse.\ Replacement: external USB wifi dongle. (or USB wwan/3g dongle; note, this has all the same privacy issues as mobile phones. wwan not recommended). This is where the simcard connector is soldered. See notes above about wwan. Remove simcard by removing battery and then it's accessible (so, -remember to do this when you re-assemble. or you could do it now?) - +remember to do this when you re-assemble. or you could do it now?)\ ![](../images/t60_dev/0046.JPG) -Put those screws back: - +Put those screws back:\ ![](../images/t60_dev/0047.JPG) -Put it back into lower chassis: - +Put it back into lower chassis:\ ![](../images/t60_dev/0048.JPG) -Attach LCD and insert screws (also, attach the lcd cable to the board): - +Attach LCD and insert screws (also, attach the lcd cable to the board):\ ![](../images/t60_dev/0049.JPG) -Insert those screws: - +Insert those screws:\ ![](../images/t60_dev/0050.JPG) On the CPU (and there is another chip south-east to it, sorry forgot to take pic) clean off the old thermal paste (with the alcohol) and apply new (Artic Silver 5 is good, others are good too) you should also clean -the heatsink the same way - +the heatsink the same way\ ![](../images/t60_dev/0051.JPG) Attach the heatsink and install the screws (also, make sure to install -the AC jack as highlighted): - +the AC jack as highlighted):\ ![](../images/t60_dev/0052.JPG) -Reinstall that upper bezel: - +Reinstall that upper bezel:\ ![](../images/t60_dev/0053.JPG) -Do that: - +Do that:\ ![](../images/t60_dev/0054.JPG) ![](../images/t60_dev/0055.JPG) -Attach keyboard and install nvram battery: - +Attach keyboard and install nvram battery:\ ![](../images/t60_dev/0056.JPG) ![](../images/t60_dev/0057.JPG) Place keyboard and (sorry, forgot to take pics) reinstall the palmrest -and insert screws on the underside: - +and insert screws on the underside:\ ![](../images/t60_dev/0058.JPG) -Remove those covers and unscrew: - +Remove those covers and unscrew:\ ![](../images/t60_dev/0059.JPG) ![](../images/t60_dev/0060.JPG) ![](../images/t60_dev/0061.JPG) Gently pry off the front bezel (sorry, forgot to take pics). -Remove bluetooth module: - +Remove bluetooth module:\ ![](../images/t60_dev/0062.JPG) ![](../images/t60_dev/0063.JPG) Re-attach the front bezel and re-insert the screws (sorry, forgot to take pics). -It lives! - +It lives!\ ![](../images/t60_dev/0071.JPG) ![](../images/t60_dev/0072.JPG) ![](../images/t60_dev/0073.JPG) Always stress test ('stress -c 2' and xsensors. below 90C is ok) when -replacing cpu paste/heatsink: - +replacing cpu paste/heatsink:\ ![](../images/t60_dev/0074.JPG) + + Not covered yet: ---------------- @@ -283,11 +245,12 @@ or directly to the video: A lot of this tutorial is based on that video. Look towards the second 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 @@ -304,6 +267,8 @@ Also not covered yet: - <https://en.wikipedia.org/wiki/Tempest_%28codename%29> - https://gitorious.org/gnutoo-for-coreboot/grub-assemble/source/a61f636797777a742f65f4c9c58032aa6a9b23c3: + + Extra notes =========== @@ -321,6 +286,7 @@ with the help of an SDR and some directional antennas[\[3\]](#ref3). controller](http://www.coreboot.org/Intel_82573_Ethernet_controller) on the X60 seems safe, according to Denis. + Risk level ---------- @@ -331,6 +297,9 @@ Risk level - Speakers: only problematic if the computer gets compromised. - EC: can be mitigated if following the guide on software security. + + + Further reading material (software security) ============================================ @@ -340,9 +309,12 @@ Further reading material (software security) /boot)](../gnulinux/encrypted_parabola.html) - [Notes about DMA access and the docking station](dock.html) + + References ========== + \[1\] physical access {#ref1} --------------------- @@ -355,6 +327,8 @@ to 400000\$, some other websites had prices 10 times lower but that but it was probably a typo. So if people increase their security it makes it more risky and more costly to attack people. + + \[2\] microphone {#ref2} ---------------- @@ -365,6 +339,8 @@ microphone jack can now become a headphone plug, that's called retasking. There is some support for it in GNU+Linux but it's not very well known. + + \[3\] Video (CCC) {#ref3} ----------------- @@ -373,8 +349,10 @@ their demo is experimental(their hardware also got damaged during the transport), the spies probably already have that since a long time. <http://berlin.ftp.media.ccc.de/congress/2013/webm/30c3-5356-en-Firmware_Fat_Camp_webm.webm> -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hardware/x60_heatsink.md b/docs/hardware/x60_heatsink.md @@ -1,8 +1,13 @@ -% Changing the fan/heatsink on the ThinkPad X60 + +Changing the fan/heatsink on the ThinkPad X60 +============================================= This guide will teach you how to replace the fan and heatsink on your ThinkPad X60. + + + Table of Contents ================= @@ -10,6 +15,8 @@ Table of Contents - [Software Requirements](#software_requirements) - [Disassembly](#procedure) + + Hardware requirements {#hardware_requirements} ===================== @@ -19,88 +26,75 @@ Hardware requirements {#hardware_requirements} 'ok') - Something to spread the paste with + + Software requirements (for CPU stress testing) {#software_requirements} ============================================== - xsensors utility - stress utility + + Disassembly {#procedure} =========== -Remove those screws: - +Remove those screws:\ ![](../images/x60_heatsink/0000.jpg) -Push the keyboard forward (carefully): - +Push the keyboard forward (carefully):\ ![](../images/x60_heatsink/0001.jpg) -Lift the keyboard up and disconnect it from the board: - +Lift the keyboard up and disconnect it from the board:\ ![](../images/x60_heatsink/0002.jpg) Grab the right-hand side of the chassis and force it off (gently) and -pry up the rest of the chassis: - +pry up the rest of the chassis:\ ![](../images/x60_heatsink/0003.jpg) -You should now have this: - +You should now have this:\ ![](../images/x60_heatsink/0004.jpg) -Disconnect the wifi antenna cables, the modem cable and the speaker: - +Disconnect the wifi antenna cables, the modem cable and the speaker:\ ![](../images/x60_heatsink/0005.jpg) Unroute the cables along their path, carefully lifting the tape that holds them in place. Then, disconnect the modem cable (other end) and power connection and unroute all the cables so that they dangle by the -monitor hinge on the right-hand side: - +monitor hinge on the right-hand side:\ ![](../images/x60_heatsink/0006.jpg) Disconnect the monitor from the motherboard, and unroute the grey -antenna cable, carefully lifting the tape that holds it into place: - +antenna cable, carefully lifting the tape that holds it into place:\ ![](../images/x60_heatsink/0008.jpg) Carefully lift the remaining tape and unroute the left antenna cable so -that it is loose: - +that it is loose:\ ![](../images/x60_heatsink/0009.jpg) -Remove those screws: - +Remove those screws:\ ![](../images/x60_heatsink/0011.jpg) -Remove those screws: - +Remove those screws:\ ![](../images/x60_heatsink/0012.jpg) -Carefully remove the plate, like so: - +Carefully remove the plate, like so:\ ![](../images/x60_heatsink/0013.jpg) -Remove the SATA connector: - +Remove the SATA connector:\ ![](../images/x60_heatsink/0014.jpg) -Now remove the motherboard (gently) and cast the lcd/chassis aside: - +Now remove the motherboard (gently) and cast the lcd/chassis aside:\ ![](../images/x60_heatsink/0015.jpg) -Look at that black tape above the heatsink, remove it: - +Look at that black tape above the heatsink, remove it:\ ![](../images/x60_heatsink/0016.jpg) -Now you have removed it: - +Now you have removed it:\ ![](../images/x60_heatsink/0017.jpg) Disconnect the fan and remove all the screws, heatsink will easily come -off: - +off:\ ![](../images/x60_heatsink/0018.jpg) Remove the old paste with a cloth (from the CPU and heatsink) and then @@ -113,8 +107,9 @@ the heatsink, reversing previous steps. **xsensors** (or **watch sensors** command) can be used to monitor heat. Below 90C is ok. -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hardware/x60_keyboard.md b/docs/hardware/x60_keyboard.md @@ -1,4 +1,6 @@ -% Thinkpad X60/X60s/X60t: Change keyboard + +Thinkpad X60/X60s/X60t: Change keyboard +======================================= Use this guide to replace the keyboard on your ThinkPad X60. Also works for X60s and X60 Tablet. @@ -9,21 +11,20 @@ same place, and it's the same procedure. [Back to previous index](./) -Just follow these steps, and then reverse {#recovery} -========================================= - -![](../images/x60_keyboard/1.JPG) -![](../images/x60_keyboard/2.JPG) -![](../images/x60_keyboard/3.JPG) - -![](../images/x60_keyboard/4.JPG) +Just follow these steps, and then reverse {#recovery} +========================================= +![](../images/x60_keyboard/1.JPG)\ +![](../images/x60_keyboard/2.JPG)\ +![](../images/x60_keyboard/3.JPG)\ +![](../images/x60_keyboard/4.JPG)\ ![](../images/x60_keyboard/5.JPG) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hardware/x60_lcd_change.md b/docs/hardware/x60_lcd_change.md @@ -1,9 +1,13 @@ -% Changing the LCD panel on X60 + +Changing the LCD panel on X60 +============================= This tutorial is incomplete, and only pictures for now. [Back to previous index](./) + + ![](../images/x60_lcd_change/0001.JPG) ![](../images/x60_lcd_change/0002.JPG) ![](../images/x60_lcd_change/0003.JPG) @@ -12,8 +16,9 @@ This tutorial is incomplete, and only pictures for now. ![](../images/x60_lcd_change/0006.JPG) ![](../images/x60_lcd_change/0007.JPG) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hardware/x60_security.md b/docs/hardware/x60_security.md @@ -1,10 +1,14 @@ -% Security on the ThinkPad X60 + +Security on the ThinkPad X60 +============================ Hardware modifications to enhance security on the ThinkPad X60. This tutorial is **incomplete** at the time of writing. [Back to previous index](./) + + Table of Contents ================= @@ -12,6 +16,8 @@ Table of Contents - [Software Requirements](#software_requirements) - [The procedure](#procedure) + + Hardware requirements {#hardware_requirements} ===================== @@ -25,6 +31,8 @@ Software requirements {#software_requirements} - none (at least in the scope of the article as-is) - You probably want to encrypt your GNU+Linux install using LUKS + + Rationale ========= @@ -39,58 +47,42 @@ purely theoretical for the time being. Disassembly {#procedure} =========== -Firstly remove the bluetooth (if your X60 has this): - +Firstly remove the bluetooth (if your X60 has this):\ The marked screws are underneath those stickers (marked in those 3 -locations at the bottom of the LCD assembly): - -![](../images/x60_security/0000_bluetooth0.jpg) - +locations at the bottom of the LCD assembly):\ +![](../images/x60_security/0000_bluetooth0.jpg)\ Now gently pry off the bottom part of the front bezel, and the bluetooth -module is on the left (easily removable): - -![](../images/x60_security/0000_bluetooth.jpg) - -If your model was WWAN, remove the simcard (check anyway): - -Uncover those 2 screws at the bottom: - -![](../images/x60_security/0000_simcard0.jpg) - -SIM card (not present in the picture) is in the marked location: - -![](../images/x60_security/0000_simcard1.jpg) - +module is on the left (easily removable):\ +![](../images/x60_security/0000_bluetooth.jpg)\ + +If your model was WWAN, remove the simcard (check anyway):\ +Uncover those 2 screws at the bottom:\ +![](../images/x60_security/0000_simcard0.jpg)\ +SIM card (not present in the picture) is in the marked location:\ +![](../images/x60_security/0000_simcard1.jpg)\ Replacement: USB dongle. Now get into the motherboard. -Remove those screws: - +Remove those screws:\ ![](../images/x60_security/0000.jpg) -Push the keyboard forward (carefully): - +Push the keyboard forward (carefully):\ ![](../images/x60_security/0001.jpg) -Lift the keyboard up and disconnect it from the board: - +Lift the keyboard up and disconnect it from the board:\ ![](../images/x60_security/0002.jpg) Grab the right-hand side of the chassis and force it off (gently) and -pry up the rest of the chassis: - +pry up the rest of the chassis:\ ![](../images/x60_security/0003.jpg) -You should now have this: - +You should now have this:\ ![](../images/x60_security/0004.jpg) The following is a summary of what you will remove (already done to this -system): - -![](../images/x60_security/0001_overview.jpg) - +system):\ +![](../images/x60_security/0001_overview.jpg)\ Note: the blue lines represent antenna cables and modem cables. You don't need to remove these, but you can if you want (to make it tidier after removing other parts). I removed the antenna wires, the modem @@ -99,11 +91,9 @@ part where the wwan antenna goes (wasn't sure what it was, but I knew it wasn't needed). **This is optional** Remove the microphone (can desolder it, but you can also easily pull it -off with you hands). Already removed here: - -![](../images/x60_security/0001_microphone.jpg) - - Rationale: +off with you hands). Already removed here:\ +![](../images/x60_security/0001_microphone.jpg)\ +**Rationale:**\ Another reason to remove the microphone: If your computer gets[\[1\]](#ref1) compromised, it can record what you say, and use it to receive data from nearby devices if they're compromised too. Also, @@ -112,42 +102,31 @@ could theoretically be programmed to accept remote commands from some speaker somewhere (remote security hole). **In other words, the system could already be compromised from the factory.** -Remove the modem: - -![](../images/x60_security/0001_modem.jpg) - +Remove the modem:\ +![](../images/x60_security/0001_modem.jpg)\ (useless, obsolete device) -Remove the speaker: - -![](../images/x60_security/0001_speaker.jpg) - +Remove the speaker:\ +![](../images/x60_security/0001_speaker.jpg)\ Reason: combined with the microphone issue, this could be used to leak -data. - +data.\ If your computer gets[\[1\]](#ref1) compromised, it can be used to transmit data to nearby compromised devices. It's unknown if it can be -turned into a microphone[\[2\]](#ref2). - +turned into a microphone[\[2\]](#ref2).\ Replacement: headphones/speakers (line-out) or external DAC (USB). -Remove the wlan (also remove wwan if you have it): - -![](../images/x60_security/0001_wlan_wwan.jpg) - +Remove the wlan (also remove wwan if you have it):\ +![](../images/x60_security/0001_wlan_wwan.jpg)\ Reason: has direct (and very fast) memory access, and could -(theoretically) leak data over a side-channel. - +(theoretically) leak data over a side-channel.\ **Wifi:** The ath5k/ath9k cards might not have firmware at all. They might safe but could have access to the computer's RAM trough DMA. If people have an intel card(most X60s come with Intel wifi by default, until you change it),then that card runs a non-free firwamre and has access to the computer's RAM trough DMA! So the risk-level is very -high. - +high.\ **Wwan (3g modem):** They run proprietary software! It's like AMT but -over the GSM network which is probably even worse. - +over the GSM network which is probably even worse.\ Replacement: external USB wifi dongle. (or USB wwan/3g dongle; note, this has all the same privacy issues as mobile phones. wwan not recommended). @@ -175,8 +154,7 @@ 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 @@ -196,6 +174,8 @@ Also not covered yet: - <https://en.wikipedia.org/wiki/Tempest_%28codename%29> - https://gitorious.org/gnutoo-for-coreboot/grub-assemble/source/a61f636797777a742f65f4c9c58032aa6a9b23c3: + + Extra notes =========== @@ -213,6 +193,7 @@ with the help of an SDR and some directional antennas[\[3\]](#ref3). controller](http://www.coreboot.org/Intel_82573_Ethernet_controller) on the X60 seems safe, according to Denis. + Risk level ---------- @@ -223,6 +204,9 @@ Risk level - Speakers: only problematic if the computer gets compromised. - EC: can be mitigated if following the guide on software security. + + + Further reading material (software security) ============================================ @@ -232,9 +216,12 @@ Further reading material (software security) /boot)](../gnulinux/encrypted_parabola.html) - [Notes about DMA access and the docking station](dock.html) + + References ========== + \[1\] physical access {#ref1} --------------------- @@ -247,6 +234,8 @@ to 400000\$, some other websites had prices 10 times lower but that but it was probably a typo. So if people increase their security it makes it more risky and more costly to attack people. + + \[2\] microphone {#ref2} ---------------- @@ -257,6 +246,8 @@ microphone jack can now become a headphone plug, that's called retasking. There is some support for it in GNU+Linux but it's not very well known. + + \[3\] Video (CCC) {#ref3} ----------------- @@ -265,8 +256,10 @@ their demo is experimental(their hardware also got damaged during the transport), the spies probably already have that since a long time. <http://berlin.ftp.media.ccc.de/congress/2013/webm/30c3-5356-en-Firmware_Fat_Camp_webm.webm> -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/c201.md b/docs/hcl/c201.md @@ -1,4 +1,6 @@ -% ASUS Chromebook C201 + +ASUS Chromebook C201 +==================== This is a Chromebook, using the Rockchip RK3288 SoC. It uses an ARM CPU, and has free EC firmware (unlike some other laptops). More RK3288-based @@ -12,10 +14,12 @@ instructions. The board is supported in libreboot, however, and has been confirmed to work.** Flashing instructions can be found at -[../install/#flashrom](../install/#flashrom) +[../install/\#flashrom](../install/#flashrom) [Back to previous index](./). + + - [Google's intent with CrOS devices](#googlesintent) - [Considerations about ChromeOS and free operating systems](#os) - [Caution: Video acceleration requires a non-free blob, software @@ -27,6 +31,8 @@ Flashing instructions can be found at - [Depthcharge payload](#depthcharge) - [Flash chip write protection: the screw](#thescrew) + + Google's intent with CrOS devices {#googlesintent} ================================== @@ -56,6 +62,10 @@ are supported in libreboot. Those laptops are supported, in spite of Apple and Lenovo, companies which are actually *hostile* to the free software movement. +[Back to top of page](#pagetop). + + + Considerations about ChromeOS and free operating systems {#os} ======================================================== @@ -76,6 +86,10 @@ install Debian. TODO: instructions for Devuan +[Back to top of page](#pagetop). + + + Caution: Video acceleration requires a non-free blob, software rendering can be used instead. {#videoblobs} ============================================================================================= @@ -95,6 +109,10 @@ The Tamil developer wrote this blog post, which sheds light on the story: [http://libv.livejournal.com/27461.html,http://libv.livejournal.com/27461.html](http://libv.livejournal.com/27461.html). +[Back to top of page](#pagetop). + + + Caution: WiFi requires a non-free blob, a USB dongle can be used instead. {#wifiblobs} ========================================================================= @@ -103,7 +121,7 @@ require non-free firmware in the Linux kernel in order to work. The libreboot project recommends using an external USB wifi dongle that works with free software. See -[#recommended\_wifi](./#recommended_wifi). +[\#recommended\_wifi](./#recommended_wifi). There are 2 companies (endorsed by Creative Commons, under their *Respects your Freedom* guidelines), that sell USB WiFi dongles @@ -120,6 +138,8 @@ These wifi dongles use the AR9271 (atheros) chipset, supported by the free *ath9k\_htc* driver in the Linux kernel. They work in *linux-libre* too. + + EC firmware is free software! {#ec} ============================= @@ -135,6 +155,8 @@ when using one of these laptops. The libreboot FAQ briefly describes what an *EC* is: <http://libreboot.org/faq/#firmware-ec> + + No microcode! {#microcode} ============= @@ -149,6 +171,10 @@ present), which are proprietary software. On ARM CPUs, the instruction set is implemented in circuitry, without microcode. +[Back to top of page](#pagetop). + + + Depthcharge payload {#depthcharge} =================== @@ -156,6 +182,8 @@ These systems do not use the GRUB payload. Instead, they use a payload called depthcharge, which is common on CrOS devices. This is free software, maintained by Google. + + Flash chip write protection: the screw {#thescrew} ====================================== @@ -179,8 +207,9 @@ firmware-level *evil maid* attack. It's possible to write protect on all current libreboot systems, but CrOS devices make it easy. The screw is such a stupidly simple idea, which all designs should implement. -Copyright © 2015 Leah Rowe <info@minifree.org> + +Copyright © 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/d510mo.md b/docs/hcl/d510mo.md @@ -1,4 +1,6 @@ -% Intel D510MO desktop board + +Intel D510MO desktop board +========================== This is a desktop board using intel hardware (circa \~2009, ICH7 southbridge, similar performance-wise to the Libreboot X200. It can make @@ -11,8 +13,9 @@ This board can however be used for building a headless server. Flashing instructions can be found at [../install/d510mo.html](../install/d510mo.html) -Copyright © 2016 Leah Rowe <info@minifree.org> + +Copyright © 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/d945gclf.md b/docs/hcl/d945gclf.md @@ -1,4 +1,6 @@ -% Intel D945GCLF desktop board + +Intel D945GCLF desktop board +============================ [Back to previous index](https://libreboot.org/docs/hcl/) @@ -37,63 +39,47 @@ Remarks about vendor bios: flashing to install libreboot on this device. Once libreboot is flashed there is no problem to update the firmware internally -Here is an image of the board: - -![](../images/d945gclf/d945gclf.jpg) - -Here is an image of the D945GCLF2 board: - -![](../images/d945gclf/20160923_141521.jpg){width="80%" height="80%"} +Here is an image of the board:\ +![](../images/d945gclf/d945gclf.jpg)\ +Here is an image of the D945GCLF2 board:\ +![](../images/d945gclf/20160923_141521.jpg){width="80%" height="80%"}\ +And SPI SOIC8 flash chip\ +![](../images/d945gclf/20160923_141550.jpg){width="50%" height="50%"} -And SPI SOIC8 flash chip -![](../images/d945gclf/20160923_141550.jpg){width="50%" height="50%"} How to replace thermal paste and fan ------------------------------------ This board comes with very crappy disposable loud fan, that one has no bearings, which can not be repaired or oiled properly, do not waste your -time trying to fix it, just buy one chinese same size fan - +time trying to fix it, just buy one chinese same size fan\ ![](../images/d945gclf/20160923_141620.jpg){width="50%" height="50%"} -![](../images/d945gclf/20160923_141614.jpg){width="50%" height="50%"} - -Make sure that new one has same wiring - -![](../images/d945gclf/20160923_142618.jpg){width="50%" height="50%"} - -This is a new one, with bearing and maintenable - +![](../images/d945gclf/20160923_141614.jpg){width="50%" height="50%"}\ +Make sure that new one has same wiring\ +![](../images/d945gclf/20160923_142618.jpg){width="50%" height="50%"}\ +This is a new one, with bearing and maintenable\ ![](../images/d945gclf/20160923_141738.jpg){width="50%" height="50%"} -![](../images/d945gclf/20160923_141814.jpg){width="50%" height="50%"} - +![](../images/d945gclf/20160923_141814.jpg){width="50%" height="50%"}\ Now remove the both coolers rotating them a bit, slowly, then clean both -silicons and both coolers (removing cmos battery first is recommended) - -![](../images/d945gclf/20160923_141601.jpg){width="50%" height="50%"} - +silicons and both coolers (removing cmos battery first is recommended)\ +![](../images/d945gclf/20160923_141601.jpg){width="50%" height="50%"}\ Put a little bit of non conductive thermal paste on both silicons (only -cpu silicon iis shown on that image) - -![](../images/d945gclf/20160923_142031.jpg){width="50%" height="50%"} +cpu silicon iis shown on that image)\ +![](../images/d945gclf/20160923_142031.jpg){width="50%" height="50%"}\ Before assembling new fan, some need new longer screws, make sure having -these (on the left is original one, too short for new fan) - -![](../images/d945gclf/20160923_141659.jpg){width="50%" height="50%"} - -After that, assemble your new fan into CPU cooler - -![](../images/d945gclf/20160923_141635.jpg){width="50%" height="50%"} - +these (on the left is original one, too short for new fan)\ +![](../images/d945gclf/20160923_141659.jpg){width="50%" height="50%"}\ +After that, assemble your new fan into CPU cooler\ +![](../images/d945gclf/20160923_141635.jpg){width="50%" height="50%"}\ Finally assemle both coolers on both chips, do not forget put in the CPU fan connector back, and you are done. -Copyright © 2016 Arthur Heymans <arthur@aheymans.xyz> -Copyright © 2016 Vitaly Castaño Solana <vita\_cell@hotmail.com> +Copyright © 2016 Arthur Heymans <arthur@aheymans.xyz>\ +Copyright © 2016 Vitaly Castaño Solana <vita\_cell@hotmail.com>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/ga-g41m-es2l.md b/docs/hcl/ga-g41m-es2l.md @@ -1,4 +1,6 @@ -% Gigabyte GA-G41M-ES2L desktop board + +Gigabyte GA-G41M-ES2L desktop board +=================================== This is a desktop board using intel hardware (circa \~2009, ICH7 southbridge, similar performance-wise to the Libreboot X200. It can make @@ -9,15 +11,15 @@ using an IDE SATA adapter. The SATA ports do work. You need to set a custom MAC address in GNU+Linux for the NIC to work. In /etc/network/interfaces on debian-based systems like Debian or -Devuan, this would be in the entry for your NIC: - +Devuan, this would be in the entry for your NIC:\ hwaddress ether macaddressgoeshere Flashing instructions can be found at -[../install/#flashrom](../install/#flashrom) +[../install/\#flashrom](../install/#flashrom) + -Copyright © 2016 Leah Rowe <info@minifree.org> +Copyright © 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md @@ -1,4 +1,6 @@ -% GM45 chipsets: remove the ME (manageability engine) + +GM45 chipsets: remove the ME (manageability engine) +=================================================== This sections relates to disabling and removing the ME (Intel **M**anagement **E**ngine) on GM45. This was originally done on the @@ -26,6 +28,8 @@ Another project recently found: <http://io.smashthestack.org/me/> [Back to previous index](./). + + ICH9 gen utility {#ich9gen} ================ @@ -36,13 +40,11 @@ factory.bin dump. 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 +source with:\ +\$ **./oldbuild module ich9deblob**\ The executable will appear under resources/utilities/ich9deblob/ -Run: - +Run:\ \$ **./ich9gen** Running ich9gen this way (without any arguments) generates a default @@ -68,9 +70,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: - - $ ./ich9gen \--macaddress XX:XX:XX:XX:XX:XX +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) @@ -85,25 +86,19 @@ Two new files will be created: Assuming that your libreboot image is named **libreboot.rom**, copy the file to where **libreboot.rom** is located and then insert the -descriptor+gbe file into the ROM image. - -For 16MiB flash chips: - +descriptor+gbe file into the ROM image.\ +For 16MiB flash chips:\ \$ **dd if=ich9fdgbe\_16m.bin of=libreboot.rom bs=1 count=12k -conv=notrunc** - -For 8MiB flash chips: - +conv=notrunc**\ +For 8MiB flash chips:\ \$ **dd if=ich9fdgbe\_8m.bin of=libreboot.rom bs=1 count=12k -conv=notrunc** - -For 4MiB flash chips: - +conv=notrunc**\ +For 4MiB flash chips:\ \$ **dd if=ich9fdgbe\_4m.bin of=libreboot.rom bs=1 count=12k -conv=notrunc** +conv=notrunc**\ Your libreboot.rom image is now ready to be flashed on the system. Refer -back to [../install/#flashrom](../install/#flashrom) for how to flash +back to [../install/\#flashrom](../install/#flashrom) for how to flash it. Write-protecting the flash chip @@ -130,13 +125,13 @@ for the following lines: NOTE: When you write-protect the flash chip, re-flashing is no longer possible unless you use dedicated external equipment, which also means disassembling the laptop. The same equipment can also be used to remove -the write-protection later on, if you choose to do so. *Only* +the write-protection later on, if you choose to do so. \*Only\* write-protect the chip if you have the right equipment for external flashing later on; for example, see [../install/bbb\_setup.html](../install/bbb_setup.html). Change them all to 0x0, then re-compile ich9gen. After you have done -that, follow the notes in [#ich9gen](#ich9gen) to generate a new +that, follow the notes in [\#ich9gen](#ich9gen) to generate a new descriptor+gbe image and insert that into your ROM image, then flash it. The next time you boot, the flash chip will be read-only in software (hardware re-flashing will still work, which you will need for @@ -150,6 +145,8 @@ brick your laptop. For external flashing guides, refer to [../install/](../install/). + + ICH9 deblob utility {#ich9deblob} =================== @@ -168,9 +165,8 @@ regions for your libreboot ROM image. If you are working with libreboot\_src (or git), you can find the source under resources/utilities/ich9deblob/ and will already be compiled if you ran **./oldbuild module all** or **./oldbuild module ich9deblob** -from the main directory (./), otherwise you can build it like so: - - $ ./oldbuild module ich9deblob +from the main directory (./), otherwise you can build it like so:\ +\$ **./oldbuild module ich9deblob**\ An executable file named **ich9deblob** will now appear under resources/utilities/ich9deblob/ @@ -181,8 +177,7 @@ GNU+Linux) under ./ich9deblob/. Place the factory.rom from your system (can be obtained using the external flashing guides for GM45 targets linked [../install/](../install/)) in the directory where you have your -ich9deblob executable, then run the tool: - +ich9deblob executable, then run the tool:\ \$ **./ich9deblob** A 12kiB file named **deblobbed\_descriptor.bin** will now appear. **Keep @@ -199,8 +194,7 @@ Intel. Only the Intel NICs need a GbE region in the flash chip. Assuming that your libreboot image is named **libreboot.rom**, copy the **deblobbed\_descriptor.bin** file to where **libreboot.rom** is located -and then run: - +and then run:\ \$ **dd if=deblobbed\_descriptor.bin of=libreboot.rom bs=1 count=12k conv=notrunc** @@ -224,9 +218,11 @@ need for a factory.rom dump! You should now have a **libreboot.rom** image containing the correct 4K descriptor and 8K gbe regions, which will then be safe to flash. Refer -back to [../install/#flashrom](../install/#flashrom) for how to flash +back to [../install/\#flashrom](../install/#flashrom) for how to flash it. + + demefactory utility {#demefactory} =================== @@ -237,24 +233,21 @@ The ME interferes with flash read/write in flashrom, and the default descriptor locks some regions. The idea is that doing this will remove all of those restrictions. -Simply run (with factory.rom in the same directory): - +Simply run (with factory.rom in the same directory):\ \$ **./demefactory** It will generate a 4KiB descriptor file (only the descriptor, no GbE). Insert that into a factory.rom image (NOTE: do this on a copy of it. -Keep the original factory.rom stored safely somewhere): - +Keep the original factory.rom stored safely somewhere):\ \$ **dd if=demefactory\_4kdescriptor.bin of=factory\_nome.rom bs=1 count=4k conv=notrunc** -TODO: test this. - +TODO: test this.\ TODO: lenovobios (GM45 thinkpads) still write-protects parts of the flash. Modify the assembly code inside. Note: the factory.rom (BIOS region) from lenovobios is in a compressed format, which you have to extract. bios\_extract upstream won't work, but the following was said -in #coreboot on freenode IRC: +in \#coreboot on freenode IRC: <roxfan> vimuser: try bios_extract with ffv patch http://patchwork.coreboot.org/patch/3444/ <roxfan> or https://github.com/coreboot/bios_extract/blob/master/phoenix_extract.py @@ -271,11 +264,14 @@ disassemble and re-flash externally unless you brick the device. demefactory is part of the ich9deblob src, found at *resources/utilities/ich9deblob/* + + The sections below are adapted from (mostly) IRC logs related to early development getting the ME removed on GM45. They are useful for background information. This could not have been done without sgsit's help. + Early notes {#early_notes} ----------- @@ -298,6 +294,10 @@ Early notes {#early_notes} what the X201 uses: <http://www.intel.co.uk/content/dam/www/public/us/en/documents/datasheets/6-chipset-c200-chipset-datasheet.pdf> + + + + Flash chips {#flashchips} ----------- @@ -305,8 +305,7 @@ Flash chips {#flashchips} <http://pdf.datasheetarchive.com/indexerfiles/Datasheets-USER/DSAUPLD00006075.pdf> **~~- Page 20 and page 9 refer to SDA\_HDO or SDA\_HDOUT~~** only on series 6 or higher chipsets. ICH9-M (X200) does it with a strap - connected to GPIO33 pin (see IRC notes below) - + connected to GPIO33 pin (see IRC notes below)\ - According to page 29, the X200 can have any of the following flash chips: - ATMEL AT26DF321-SU 72.26321.A01 - this is a 32Mb (4MiB) chip @@ -322,9 +321,13 @@ Flash chips {#flashchips} - Schematics for X200s laptop: <http://pdf.datasheetarchive.com/indexerfiles/Datasheets-USER/DSAUPLD00006104.pdf>. + + + Early development notes {#early_development_notes} ----------------------- + Start (hex) End (hex) Length (hex) Area Name ----------- --------- ------------ --------- 00000000 003FFFFF 00400000 Flash Image @@ -392,6 +395,8 @@ X200. End justified means, and the utility is no longer needed since the ich9deblob utility (documented on this page) can now be used to create deblobbed descriptors. + + GBE (gigabit ethernet) region in SPI flash {#gbe_region} ------------------------------------------ @@ -401,6 +406,7 @@ documented in this public datasheet: The only actual content found was: + 00 1F 1F 1F 1F 1F 00 08 FF FF 83 10 FF FF FF FF 08 10 FF FF C3 10 EE 20 AA 17 F5 10 86 80 00 00 01 0D 00 00 00 00 05 06 20 30 00 0A 00 00 8B 8D @@ -417,12 +423,13 @@ The first part is the MAC address set to all 0x1F. It's repeated haly way through the 8K area, and the rest is all 0xFF. This is all documented in the datasheet. -The GBe region starts at 0x20A000 bytes from the *end* of a factory +The GBe region starts at 0x20A000 bytes from the \*end\* of a factory image and is 0x2000 bytes long. In libreboot (deblobbed) the descriptor is set to put gbe directly after the initial 4K flash descriptor. So the first 4K of the ROM is the descriptor, and then the next 8K is the gbe region. + ### GBE region: change MAC address {#gbe_region_changemacaddress} According to the datasheet, it's supposed to add up to 0xBABA but can @@ -433,7 +440,7 @@ actually be others on the X200. 0xBABA"* In honour of the song *Baba O'Reilly* by *The Who* apparently. We're -not making this stuff up... +not making this stuff up\... 0x3ABA, 0x34BA, 0x40BA and more have been observed in the main Gbe regions on the X200 factory.rom dumps. The checksums of the backup @@ -442,7 +449,7 @@ regions match BABA, however. By default, the X200 (as shipped by Lenovo) actually has an invalid main gbe checksum. The backup gbe region is correct, and is what these systems default to. Basically, you should do what you need on the -*backup* gbe region, and then correct the main one by copying from the +\*backup\* gbe region, and then correct the main one by copying from the backup. Look at resources/utilities/ich9deblob/ich9deblob.c. @@ -452,6 +459,9 @@ Look at resources/utilities/ich9deblob/ich9deblob.c. to 0xBABA. In other words, the checksum is 0xBABA minus the total of the first 0x3E 16bit numbers (unsigned), ignoring any overflow. + + + Flash descriptor region {#flash_descriptor_region} ----------------------- @@ -515,6 +525,8 @@ So, *x << 12 = address* If it's in descriptor mode, then the first 4 bytes will be 5A A5 F0 0F. + + platform data partition in boot flash (factory.rom / lenovo bios) {#platform_data_region} ----------------------------------------------------------------- @@ -526,8 +538,9 @@ This is a 32K region from the factory image. It could be data It has only a 448 byte fragment different from 0x00 or 0xFF. -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/imac52.md b/docs/hcl/imac52.md @@ -1,9 +1,12 @@ -% Apple iMac 5,2 + +Apple iMac 5,2 +============== Information to be written soon, but this board is merged in libreboot. -Copyright © 2016 Leah Rowe <info@minifree.org> + +Copyright © 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/index.md b/docs/hcl/index.md @@ -1,4 +1,6 @@ -% Hardware compatibility list + +Hardware compatibility list +=========================== This sections relates to known hardware compatibility in libreboot. @@ -15,6 +17,8 @@ This sections relates to known hardware compatibility in libreboot. [Back to previous index](../). + + List of supported hardware {#supported_list} -------------------------- @@ -58,6 +62,10 @@ working). There may be exceptions; in other words, this is a list of It is also possible to build ROM images (from source) for other systems (and virtual systems, e.g. QEMU). +[Back to top of page](#pagetop) + + + EC update on i945 (X60, T60) and GM45 (X200, T400, T500, R400) {#ecupdate} ============================================================== @@ -77,20 +85,26 @@ only replaces the BIOS firmware, not EC. Updated EC firmware has several advantages e.g. bettery battery handling. +[Back to top of page](#pagetop) + + + How to find what EC version you have (i945/GM45) {#ecversion} ================================================ -In GNU+Linux, you can try this: - +In GNU+Linux, you can try this:\ **grep 'at EC' /proc/asound/cards** -Sample output: - +Sample output:\ **ThinkPad Console Audio Control at EC reg 0x30, fw 7WHT19WW-3.6** 7WHT19WW is the version in different notation, use search engine to find out regular version - in this case it's a 1.06 for x200 tablet +[Back to top of page](#pagetop) + + + Recommended wifi chipsets {#recommended_wifi} ------------------------- @@ -109,6 +123,10 @@ project if these work with linux-libre kernel (TODO: test): - \[0200\]: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) \[168c:001c\] +[Back to top of page](#pagetop) + + + List of supported ThinkPad X60s {#supported_x60_list} ------------------------------- @@ -118,12 +136,12 @@ BIOS](https://en.wikipedia.org/wiki/Video_BIOS)' or 'VBIOS'), all known LCD panels are currently compatible: To find what LCD panel you have, see: -[../misc/#get\_edid\_panelname](../misc/#get_edid_panelname). +[../misc/\#get\_edid\_panelname](../misc/#get_edid_panelname). -- TMD-Toshiba LTD121ECHB: # -- CMO N121X5-L06: # -- Samsung LTN121XJ-L07: # -- BOE-Hydis HT121X01-101: # +- TMD-Toshiba LTD121ECHB: \# +- CMO N121X5-L06: \# +- Samsung LTN121XJ-L07: \# +- BOE-Hydis HT121X01-101: \# You can remove an X61/X61s motherboard from the chassis and install an X60/X60s motherboard in it's place (for flashing libreboot). The @@ -135,10 +153,12 @@ at all without proprietary firmware, and while Lenovo BIOS is running the system will refuse to boot if you replace the card. Fortunately it is very easily replaced; just remove the card and install another one **after** libreboot is installed. See -[#recommended\_wifi](#recommended_wifi) for replacements. +[\#recommended\_wifi](#recommended_wifi) for replacements. [Back to top of page.](#pagetop) + + List of supported ThinkPad X60 Tablets {#supported_x60t_list} -------------------------------------- @@ -147,7 +167,7 @@ proprietary VGA Option ROM ('[Video BIOS](https://en.wikipedia.org/wiki/Video_BIOS)' or 'VBIOS'). To find what LCD panel you have, see: -[../misc/#get\_edid\_panelname](../misc/#get_edid_panelname). +[../misc/\#get\_edid\_panelname](../misc/#get_edid_panelname). There are 5 known LCD panels for the X60 Tablet: @@ -174,7 +194,7 @@ work at all without proprietary firmware, and while Lenovo BIOS is running the system will refuse to boot if you replace the card. Fortunately it is very easily replaced; just remove the card and install another one **after** libreboot is installed. See -[#recommended\_wifi](#recommended_wifi) for replacements. +[\#recommended\_wifi](#recommended_wifi) for replacements. A user with a X60T that has digitizer+finger support, reported that they could get finger input working. They used linuxwacom at git tag @@ -183,7 +203,7 @@ could get finger input working. They used linuxwacom at git tag # Now, for some reason (probably a bug in linuxwacom), # the 'Touch=on' directive gets reset to 'off'. # So you'll need to do - # \$ xsetwacom --set WTouch Touch on + # $ xsetwacom --set WTouch Touch on # # tested with linuxwacom git 42a42b2a8636abc9e105559e5dea467163499de7 @@ -201,16 +221,16 @@ could get finger input working. They used linuxwacom at git tag Identifier "WTouch" Driver "wacom" Option "Device" "/dev/ttyS0" - #Option "DebugLevel" "12" + # Option "DebugLevel" "12" Option "BaudRate" "38400" Option "Type" "touch" Option "Touch" "on" Option "Gesture" "on" Option "ForceDevice" "ISDV4" - #Option "KeepShape" "on" + # Option "KeepShape" "on" Option "Mode" "Absolute" Option "RawSample" "2" - #Option "TPCButton" "off" + # Option "TPCButton" "off" Option "TopX" "17" Option "TopY" "53" Option "BottomX" "961" @@ -225,6 +245,8 @@ could get finger input working. They used linuxwacom at git tag [Back to top of page.](#pagetop) + + Supported T60 list {#supported_t60_list} ------------------ @@ -233,10 +255,10 @@ proprietary VGA Option ROM ('[Video BIOS](https://en.wikipedia.org/wiki/Video_BIOS)' or 'VBIOS'). To find what LCD panel you have, see: -[../misc/#get\_edid\_panelname](../misc/#get_edid_panelname). +[../misc/\#get\_edid\_panelname](../misc/#get_edid_panelname). **Some T60s have ATI GPUs, and all T60P laptops have ATI GPUs These are -incompatible! See [#t60\_ati\_intel](#t60_ati_intel) for how to remedy +incompatible! See [\#t60\_ati\_intel](#t60_ati_intel) for how to remedy this.** Tested LCD panels: **working(compatible)** @@ -253,8 +275,9 @@ Tested LCD panels: **working(compatible)** - BOE-Hydis HV150UX1-100 (15.1" 1600x1200) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board) + Tested LCD panels: **not working yet (incompatible; see -[../future/#lcd\_i945\_incompatibility](../future/#lcd_i945_incompatibility))** +[../future/\#lcd\_i945\_incompatibility](../future/#lcd_i945_incompatibility))** - Samsung LTN141XA-L01 (14.1" 1024x768) - LG-Philips LP150X09 (15.1" 1024x768) @@ -269,6 +292,8 @@ Tested LCD panels: **not working yet (incompatible; see GNU+Linux works) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board) + + *The following LCD panels are **UNTESTED**. If you have one of these panels then please submit a report!*: @@ -300,10 +325,13 @@ at all without proprietary firmware, and while Lenovo BIOS is running the system will refuse to boot if you replace the card. Fortunately it is very easily replaced; just remove the card and install another one **after** libreboot is installed. See -[#recommended\_wifi](#recommended_wifi) for replacements. +[\#recommended\_wifi](#recommended_wifi) for replacements. + [Back to top of page.](#pagetop) + + ThinkPad T60 (ATI GPU) and ThinkPad T60 (Intel GPU) differences. {#t60_ati_intel} ---------------------------------------------------------------- @@ -324,8 +352,8 @@ cannot be used with libreboot under any circumstances. The following T60 motherboard (see area highlighted in white) shows an empty space where the ATI GPU would be (this particular motherboard has -an Intel GPU): - +an Intel GPU):\ +\ ![](../images/t60_dev/t60_unbrick.jpg) The reason that the ATI GPU on T60 is unsupported is due to the VBIOS @@ -335,8 +363,7 @@ work in libreboot. The 'Video BIOS' is what initializes graphics. -See: <https://en.wikipedia.org/wiki/Video_BIOS>. - +See: <https://en.wikipedia.org/wiki/Video_BIOS>.\ In fact, lack of free VBIOS in general is a big problem in coreboot, and is one reason (among others) why many ports for coreboot are unsuitable for libreboot's purpose. @@ -349,6 +376,8 @@ server setup (with serial and/or ssh console as the display). [Back to top of page.](#pagetop) + + Information about the macbook1,1 {#macbook11} -------------------------------- @@ -357,7 +386,7 @@ same i945 chipset as the ThinkPad X60/T60. A developer ported the [MacBook2,1](#macbook21) to coreboot, the ROM images also work on the macbook1,1. -You can refer to [#macbook21](#macbook21) for most of this. Macbook2,1 +You can refer to [\#macbook21](#macbook21) for most of this. 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 @@ -367,6 +396,7 @@ It is believed that all models are compatible, listed here: - <http://www.everymac.com/ultimate-mac-lookup/?search_keywords=MacBook1,1> + ### Compatible models Specifically (Order No. / Model No. / CPU): @@ -375,12 +405,13 @@ Specifically (Order No. / Model No. / CPU): - MA254LL/A / A1181 (EMC 2092) / Core Duo T2400 **(tested - working)** - MA472LL/A / A1181 (EMC 2092) / Core Duo T2500 (untested) + Also of interest: -[../git/#config\_macbook21](../git/#config_macbook21). +[../git/\#config\_macbook21](../git/#config_macbook21). Unbricking: [this page shows disassembly guides](https://www.ifixit.com/Device/MacBook_Core_2_Duo) and mono's -page (see [#macbook21](#macbook21)) shows the location of the SPI flash +page (see [\#macbook21](#macbook21)) shows the location of the SPI flash chip on the motherboard. [How to remove the motherboard](https://www.ifixit.com/Guide/MacBook+Core+2+Duo+PRAM+Battery+Replacement/529). @@ -391,6 +422,8 @@ refer to [../install/bbb\_setup.html](../install/bbb_setup.html). [Back to top of page.](#pagetop) + + Information about the macbook2,1 {#macbook21} -------------------------------- @@ -405,12 +438,10 @@ 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: - - $ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/ +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/** - +http://macbook.donderklumpen.de/coreboot/**\ Use **-e robots=off** if using this trick for other sites and the site restricts using robots.txt @@ -420,6 +451,7 @@ distribute them, but I need to ask this person to tell me what license these works fall under first. Otherwise, the above URLs should be fine. NOTE TO SELF: REMOVE THIS WHEN DONE** + ### Installing GNU+Linux distributions (on Apple EFI firmware) - [Parabola GNU+Linux installation on a macbook2,1 with Apple EFI @@ -433,17 +465,23 @@ 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.) Now to install libreboot, follow -[../install/#flashrom\_macbook21](../install/#flashrom_macbook21). +[../install/\#flashrom\_macbook21](../install/#flashrom_macbook21). + + ### Information about coreboot - [Coreboot on the macbook2,1](#) (this is a copy of Mono's page, see above) + + ### coreboot wiki page - <https://www.coreboot.org/Board:apple/macbook21> + + ### Compatible models It is believed that all models are compatible, listed here: @@ -463,8 +501,9 @@ Specifically (Order No. / Model No. / CPU): - MB062LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 **(tested - working)** + Also of interest: -[../git/#config\_macbook21](../git/#config_macbook21). +[../git/\#config\_macbook21](../git/#config_macbook21). Unbricking: [this page shows disassembly guides](https://www.ifixit.com/Device/MacBook_Core_2_Duo) and mono's @@ -551,8 +590,9 @@ libreboot git repository. [Back to top of page.](#pagetop) -Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/kcma-d8.md b/docs/hcl/kcma-d8.md @@ -1,4 +1,6 @@ -% ASUS KCMA-D8 desktop/workstation board + +ASUS KCMA-D8 desktop/workstation board +====================================== This is a desktop board using AMD hardware (Fam10h **and Fam15h** CPUs available). It can also be used for building a high-powered workstation. @@ -9,7 +11,7 @@ Raptor Engineering Inc. and, working with them, merged into libreboot. recommend avoiding Kingston modules.** Flashing instructions can be found at -[../install/#flashrom](../install/#flashrom) - note that external +[../install/\#flashrom](../install/#flashrom) - note that external flashing is required (e.g. BBB), if the proprietary (ASUS) firmware is currently installed. If you already have libreboot, by default it is possible to re-flash using software running in GNU+Linux on the kcma-d8, @@ -17,6 +19,8 @@ without using external hardware. [Back to previous index](./). + + CPU compatibility ================= @@ -24,11 +28,15 @@ CPU compatibility virt).** 4300 series needs microcode updates, so avoid those CPUs. 4100 series is too old, and mostly untested. + + Board status (compatibility) {#boardstatus} ============================ See <https://raptorengineeringinc.com/coreboot/kcma-d8-status.php>. + + Form factor {#formfactor} =========== @@ -36,6 +44,8 @@ These boards use the SSI EEB 3.61 form factor; make sure that your case supports this. This form factor is similar to E-ATX in that the size is identical, but the position of the screws are different. + + IPMI iKVM module add-on {#ipmi} ======================= @@ -46,6 +56,8 @@ unsigned (possibly to replace) and physically separate from the mainboard since it's on the add-on module, which you don't have to install. + + Flash chips {#flashchips} =========== @@ -62,12 +74,16 @@ flash chip is 2MiB). extractor. These can be found online. See <http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + + Native graphics initialization {#graphics} ============================== Only text-mode is known to work, but linux(kernel) can initialize the framebuffer display (if it has KMS - kernel mode setting). + + Current issues {#issues} ============== @@ -87,15 +103,18 @@ Current issues {#issues} to derive from, for those who want to work on a free replacement. In practise, out-of-band management isn't very useful anyway (or at the very least, it's not a major inconvenience to not have it). -- Graphics: only text-mode works. See [#graphics](#graphics) +- Graphics: only text-mode works. See [\#graphics](#graphics) + + Hardware specifications {#specifications} ----------------------- Check the ASUS website. -Copyright © 2016 Leah Rowe <info@minifree.org> + +Copyright © 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/kfsn4-dre.md b/docs/hcl/kfsn4-dre.md @@ -1,13 +1,17 @@ -% ASUS KFSN4-DRE server/workstation board + +ASUS KFSN4-DRE server/workstation board +======================================= This is a server board using AMD hardware (Fam10h). It can also be used for building a high-powered workstation. Powered by libreboot. Flashing instructions can be found at -[../install/#flashrom](../install/#flashrom) +[../install/\#flashrom](../install/#flashrom) [Back to previous index](./). + + Form factor {#formfactor} =========== @@ -15,6 +19,8 @@ These boards use the SSI EEB 3.61 form factor; make sure that your case supports this. This form factor is similar to E-ATX in that the size is identical, but the position of the screws are different. + + Flash chips {#flashchips} =========== @@ -28,17 +34,23 @@ example of a 2MiB (16Mbits) chip, which might work. It is believed that extractor. These can be found online. See <http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + + Native graphics initialization {#graphics} ============================== Native graphics initialization exists (XGI Z9s) for this board. Framebuffer- and text-mode both work. A serial port is also available. + + Memory ====== DDR2 533/667 Registered ECC. 16 slots. Total capacity up to 64GiB. + + Hex-core CPUs {#hexcore} ============= @@ -47,6 +59,8 @@ number will be printed on the board), because it can use dual hex-core CPUs (Opteron 2400/8400 series). Other revisions are believed to only support dual quad-core CPUs. + + Current issues {#issues} ============== @@ -62,13 +76,16 @@ Current issues {#issues} disappears if using KMS, once the kernel starts. The jitter will remain, if booting the kernel in text-mode). + + Other information ================= [specifications](ftp://ftp.sgi.com/public/Technical%20Support/Pdf%20files/Asus/kfsn4-dre.pdf) -Copyright © 2015 Leah Rowe <info@minifree.org> + +Copyright © 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/kgpe-d16.md b/docs/hcl/kgpe-d16.md @@ -1,4 +1,6 @@ -% ASUS KGPE-D16 server/workstation board + +ASUS KGPE-D16 server/workstation board +====================================== This is a server board using AMD hardware (Fam10h **and Fam15h** CPUs available). It can also be used for building a high-powered workstation. @@ -10,7 +12,7 @@ work), merged into libreboot. recommend avoiding Kingston modules.** Flashing instructions can be found at -[../install/#flashrom](../install/#flashrom) - note that external +[../install/\#flashrom](../install/#flashrom) - note that external flashing is required (e.g. BBB), if the proprietary (ASUS) firmware is currently installed. If you already have libreboot, by default it is possible to re-flash using software running in GNU+Linux on the @@ -18,6 +20,8 @@ KGPE-D16, without using external hardware. [Back to previous index](./). + + CPU compatibility ================= @@ -25,11 +29,15 @@ CPU compatibility virt).** 6300 series needs microcode updates, so avoid those CPUs. 6100 series is too old, and mostly untested. + + Board status (compatibility) {#boardstatus} ============================ See <https://raptorengineeringinc.com/coreboot/kgpe-d16-status.php>. + + Form factor {#formfactor} =========== @@ -37,6 +45,8 @@ These boards use the SSI EEB 3.61 form factor; make sure that your case supports this. This form factor is similar to E-ATX in that the size is identical, but the position of the screws are different. + + IPMI iKVM module add-on {#ipmi} ======================= @@ -47,6 +57,8 @@ unsigned (possibly to replace) and physically separate from the mainboard since it's on the add-on module, which you don't have to install. + + Flash chips {#flashchips} =========== @@ -63,12 +75,16 @@ flash chip is 2MiB). extractor. These can be found online. See <http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + + Native graphics initialization {#graphics} ============================== Only text-mode is known to work, but linux(kernel) can initialize the framebuffer display (if it has KMS - kernel mode setting). + + Current issues {#issues} ============== @@ -88,7 +104,9 @@ Current issues {#issues} to derive from, for those who want to work on a free replacement. In practise, out-of-band management isn't very useful anyway (or at the very least, it's not a major inconvenience to not have it). -- Graphics: only text-mode works. See [#graphics](#graphics) +- Graphics: only text-mode works. See [\#graphics](#graphics) + + Hardware specifications {#specifications} ----------------------- @@ -126,8 +144,8 @@ The information here is adapted, from the ASUS website. - **Total Slots:** 16 (4-channel per CPU, 8 DIMM per CPU), ECC - **Capacity:** Maximum up to 256GB RDIMM - **Memory Type that is compatible:** - - DDR3 1600/1333/1066/800 UDIMM* - - DDR3 1600/1333/1066/800 RDIMM* + - DDR3 1600/1333/1066/800 UDIMM\* + - DDR3 1600/1333/1066/800 RDIMM\* - **Compatible sizes per memory module:** - 16GB, 8GB, 4GB, 3GB, 2GB, 1GB RDIMM - 8GB, 4GB, 2GB, 1GB UDIMM @@ -144,7 +162,7 @@ The information here is adapted, from the ASUS website. - **Slot Location 6:** PCI-E x16 (Gen2 X16 Link), Auto turn off if slot 5 is occupied, For 1U FH/FL Card, MIO supported - **Additional Slot 1:** PIKE slot (for SAS drives. See notes above) -- Follow SSI Location# +- Follow SSI Location\# ### Form factor {#form-factor} @@ -205,11 +223,12 @@ The information here is adapted, from the ASUS website. ### Note: -- * DDR3 1600 can only be supported with AMD Opteron 6300/6200 series +- \* DDR3 1600 can only be supported with AMD Opteron 6300/6200 series processor -Copyright © 2015 Leah Rowe <info@minifree.org> + +Copyright © 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/r400.md b/docs/hcl/r400.md @@ -1,4 +1,6 @@ -% ThinkPad R400 + +ThinkPad R400 +============= It is believed that all or most R400 laptops are compatible. See notes about [CPU @@ -15,10 +17,12 @@ modified descriptor: see [gm45\_remove\_me.html](gm45_remove_me.html)** (contains notes, plus instructions) Flashing instructions can be found at -[../install/#flashrom](../install/#flashrom) +[../install/\#flashrom](../install/#flashrom) [Back to previous index](./). + + EC update {#ecupdate} ========= @@ -38,9 +42,12 @@ only replaces the BIOS firmware, not EC. Updated EC firmware has several advantages e.g. bettery battery handling. + + Compatibility (without blobs) {#compatibility_noblobs} ----------------------------- + ### Hardware virtualization (vt-x) {#hwvirt} The R400, when run without CPU microcode updates in coreboot, currently @@ -55,14 +62,18 @@ On GM45 hardware (with libreboot), make sure that the *kvm* and The following errata datasheet from Intel might help with investigation: <http://download.intel.com/design/mobile/specupdt/320121.pdf> + + + The R400 is almost identical to the X200, code-wise. See [x200.html](x200.html). TODO: put hardware register logs here like on the [X200](x200.html) and [T400](t400.html) page. -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/t400.md b/docs/hcl/t400.md @@ -1,4 +1,6 @@ -% ThinkPad T400 + +ThinkPad T400 +============= It is believed that all or most T400 laptops are compatible. See notes about [CPU @@ -15,10 +17,12 @@ modified descriptor: see [gm45\_remove\_me.html](gm45_remove_me.html)** (contains notes, plus instructions) Flashing instructions can be found at -[../install/#flashrom](../install/#flashrom) +[../install/\#flashrom](../install/#flashrom) [Back to previous index](./). + + EC update {#ecupdate} ========= @@ -38,9 +42,12 @@ only replaces the BIOS firmware, not EC. Updated EC firmware has several advantages e.g. bettery battery handling. + + Compatibility (without blobs) {#compatibility_noblobs} ----------------------------- + ### Hardware virtualization (vt-x) {#hwvirt} The T400, when run without CPU microcode updates in coreboot, currently @@ -55,9 +62,14 @@ On GM45 hardware (with libreboot), make sure that the *kvm* and The following errata datasheet from Intel might help with investigation: <http://download.intel.com/design/mobile/specupdt/320121.pdf> + + + The T400 is almost identical to the X200, code-wise. See [x200.html](x200.html). + + Hardware register dumps {#regdumps} ----------------------- @@ -72,8 +84,9 @@ outputs from the T400: - Version of flashrom used for the external flashing/reading logs is the one that libreboot git revision c164960 uses. -Copyright © 2015 Leah Rowe <info@minifree.org> + +Copyright © 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/t500.md b/docs/hcl/t500.md @@ -1,4 +1,6 @@ -% ThinkPad T500 + +ThinkPad T500 +============= It is believed that all or most T500 laptops are compatible. See notes about [CPU @@ -15,10 +17,12 @@ modified descriptor: see [gm45\_remove\_me.html](gm45_remove_me.html)** (contains notes, plus instructions) Flashing instructions can be found at -[../install/#flashrom](../install/#flashrom) +[../install/\#flashrom](../install/#flashrom) [Back to previous index](./). + + EC update {#ecupdate} ========= @@ -38,9 +42,12 @@ only replaces the BIOS firmware, not EC. Updated EC firmware has several advantages e.g. bettery battery handling. + + Compatibility (without blobs) {#compatibility_noblobs} ----------------------------- + ### Hardware virtualization (vt-x) {#hwvirt} The T500, when run without CPU microcode updates in coreboot, currently @@ -55,9 +62,14 @@ On GM45 hardware (with libreboot), make sure that the *kvm* and The following errata datasheet from Intel might help with investigation: <http://download.intel.com/design/mobile/specupdt/320121.pdf> + + + The T500 is almost identical to the X200, code-wise. See [x200.html](x200.html). + + Descriptor and Gbe differences {#descriptor_difference} ------------------------------ @@ -69,9 +81,8 @@ and The patches above are based on the output from ich9deblob on a factory.rom image dumped from the T500 with a SOIC-8 4MiB flash chip. The patch re-creates the X200 descriptor/gbe source, so the commands -were something like: - - $ diff -u t500gbe x200gbe +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. @@ -81,6 +92,8 @@ The very same descriptor/gbe used on the X200 (generated by [ich9gen](gm45_remove_me.html#ich9gen)) was re-used on the T500, and it still worked. + + Hardware register dumps {#regdumps} ----------------------- @@ -93,8 +106,9 @@ outputs from the T500: Lenovo BIOS 3.13 7VET83WW (EC firmware 1.06): - [../future/dumps/t500log/](../future/dumps/t500log/) -Copyright © 2015 Leah Rowe <info@minifree.org> + +Copyright © 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/hcl/x200.md b/docs/hcl/x200.md @@ -1,9 +1,11 @@ -% ThinkPad X200 + +ThinkPad X200 +============= It is believed that all X200 laptops are compatible. X200S and X200 Tablet will also work, [depending on the configuration](#x200s). -It *might* be possible to put an X200 motherboard in an X201 chassis, +It \*might\* be possible to put an X200 motherboard in an X201 chassis, though this is currently untested by the libreboot project. The same may also apply between X200S and X201S; again, this is untested. **It's most likely true.** @@ -18,10 +20,12 @@ modified descriptor: see [gm45\_remove\_me.html](gm45_remove_me.html)** (contains notes, plus instructions) Flashing instructions can be found at -[../install/#flashrom](../install/#flashrom) +[../install/\#flashrom](../install/#flashrom) [Back to previous index](./). + + EC update {#ecupdate} ========= @@ -41,9 +45,12 @@ only replaces the BIOS firmware, not EC. Updated EC firmware has several advantages e.g. bettery battery handling. + + Compatibility (without blobs) {#compatibility_noblobs} ----------------------------- + ### Hardware virtualization (vt-x) {#hwvirt} The X200, when run without CPU microcode updates in coreboot, currently @@ -62,6 +69,9 @@ Anecdotal reports from at least 1 user suggests that some models with CPU microcode 1067a (on the CPU itself) might work with vt-x in libreboot. + + + X200S and X200 Tablet. {#x200s} ---------------------- @@ -104,6 +114,7 @@ This was then pushed as a patch for coreboot, which can be found at <http://review.coreboot.org/#/c/7786/> (libreboot merges this patch in coreboot-libre now. Check the 'getcb' script in src or git). + ### Proper GS45 raminit {#x200s_raminit} A new northbridge gs45 should be added to coreboot, based on gm45, and a @@ -122,12 +133,17 @@ comparing it with X200 (factory BIOS) and X200 (gm45 raminit code in coreboot), to see what the differences are. Then tweak raminit code based on that. + + + Trouble undocking (button doesn't work) ---------------------------------------- This person seems to have a workaround: <https://github.com/the-unconventional/libreboot-undock> + + LCD compatibility list {#lcd_supported_list} ---------------------- @@ -138,6 +154,7 @@ All LCD panels for the X200, X200S and X200 Tablet are known to work. [Back to top of page.](#pagetop) + ### AFFS/IPS panels {#ips} #### X200 @@ -161,7 +178,7 @@ just simply remove the digitizer). **If your X200 has an LED backlit panel in it, then you also need to get an inverter and harness cable that is compatible with the CCFL panels. To see which panel type you have, see -[#led\_howtotell](#led_howtotell). If you need the inverter/cable, here +[\#led\_howtotell](#led_howtotell). If you need the inverter/cable, here are part numbers: 44C9909 for CCFL LVDS cable with bluetooth and camera connections, and 42W8009 or 42W8010 for the inverter.** @@ -180,14 +197,19 @@ Sources: - [ThinkWiki.de - X200 Displayumbau](http://thinkwiki.de/X200_Displayumbau) + + ### X200S <http://forum.thinkpads.com/viewtopic.php?p=618928#p618928> explains that the X200S screens/assemblies are thinner. You need to replace the whole lid with one from a normal X200/X201. + [Back to top of page.](#pagetop) + + How to tell if it has an LED or CCFL? {#led_howtotell} ------------------------------------- @@ -205,6 +227,8 @@ something different). [Back to top of page.](#pagetop) + + Hardware register dumps {#regdumps} ----------------------- @@ -216,6 +240,8 @@ outputs from the X200: - BIOS 3.15, EC 1.06 - [hwdumps/x200/](hwdumps/x200/) + + RAM, S3 and microcode updates {#ram_s3_microcode} ============================= @@ -231,13 +257,12 @@ be useful for RAM compatibility info (note: coreboot raminit is different, so this page might be BS) pehjota started collecting some steppings for different CPUs on several -X200 laptops. You can get the CPUID by running: - -\$ **dmesg | sed -n 's/\^.* microcode: CPU0 -sig=0x\\(\[\^,\]*\\),.*\$/\\1/p'** +X200 laptops. You can get the CPUID by running:\ +\$ **dmesg | sed -n 's/\^.\* microcode: CPU0 +sig=0x\\(\[\^,\]\*\\),.\*\$/\\1/p'** What pehjota wrote: The laptops that have issues resuming from suspend, -as well as a laptop that (as I mentioned earlier in #libreboot) won't +as well as a laptop that (as I mentioned earlier in \#libreboot) won't boot with any Samsung DIMMs, all have CPUID 0x10676 (stepping M0). What pehjota wrote: Laptops with CPUID 0x167A (stepping R0) resume @@ -258,6 +283,8 @@ available. I'd be curious if you could confirm these results.** It might not be coreboot that's buggy with raminit/S3; it might just be down to the microcode updates. + + Unsorted notes {#unsorted} -------------- @@ -267,10 +294,10 @@ Unsorted notes {#unsorted} <sgsit> you can plug a board in which gives diagnostic codes but i'm wondering whether it is capable of more <sgsit> http://www.endeer.cz/bios.tools/bios.html -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> -Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net> +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ +Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/index.md b/docs/index.md @@ -1,4 +1,6 @@ -% Libreboot documentation + +Libreboot documentation +======================= Information about this release can be found at [release.html](release.html). Always check @@ -9,6 +11,8 @@ Information about this release can be found at [Answers to frequently asked questions about Libreboot](https://libreboot.org/faq/) + + Libreboot is compatible with GNU+Linux and several BSD systems. For GNU+Linux, have a look at our [list of GNU+Linux distributions that @@ -46,6 +50,8 @@ Other information - [Hardware modifications](hardware/) - [Miscellaneous](misc/) + + About the libreboot project =========================== @@ -97,26 +103,20 @@ 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 much as is feasibly possible. Secondly, the project produces documentation aimed at non-technical users. Thirdly, the project attempts to provide excellent user support via mailing lists and - IRC. - - - + IRC.\ + \ Libreboot already comes with a payload (GRUB), flashrom and other needed parts. Everything is fully integrated, in a way where most of the complicated steps that are otherwise required, are instead done - for the user in advance. - - - + for the user in advance.\ + \ You can download ROM images for your libreboot system and install them, without having to build anything from source. The build system is also fully automated, so building from source is easy if you @@ -157,6 +157,8 @@ Libreboot is a 'stable' version of coreboot [Back to top of page.](#pagetop) + + How do I know what version I'm running? ======================================== @@ -164,9 +166,8 @@ If you are at least 127 commits after release 20150518 (commit message *build/roms/helper: add version information to CBFS*) (or you have any **upstream** stable release of libreboot after 20150518), then you can press C at the GRUB console, and use this command to find out what -version of libreboot you have: - - cat (cbfsdisk)/lbversion +version of libreboot you have:\ +**cat (cbfsdisk)/lbversion**\ This will also work on non-release images (the version string is automatically generated, using *git describe \--tags HEAD*), built from the git repository. A file named *version* will also be included in the @@ -175,9 +176,8 @@ archives that you downloaded (if you are using release archives). If it exists, you can also extract this *lbversion* file by using the *cbfstool* utility which libreboot includes, from a ROM image that you either dumped or haven't flashed yet. In your distribution, run -cbfstool on your ROM image (*libreboot.rom*, in this example): - - $ ./cbfstool libreboot.rom extract -n lbversion -f lbversion +cbfstool on your ROM image (*libreboot.rom*, in this example):\ +\$ **./cbfstool libreboot.rom extract -n lbversion -f lbversion**\ You will now have a file, named *lbversion*, which you can read in whatever program it is that you use for reading/writing text files. @@ -187,9 +187,8 @@ For releases on or below 20150518, or snapshots generated from the git repository below 127 commits after 20150518, you can find a file named *commitid* inside the archives. If you are using pre-built ROM images from the libreboot project, you can press C in GRUB for access to the -terminal, and then run this command: - - lscoreboot +terminal, and then run this command:\ +**lscoreboot**\ You may find a date in here, detailing when that ROM image was built. For pre-built images distributed by the libreboot project, this is a rough approximation of what version you have, because the version @@ -213,8 +212,9 @@ libreboot that you are using. Generally speaking, it is advisable to use the latest version of libreboot. -Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md @@ -1,4 +1,6 @@ -% How to program an SPI flash chip with the BeagleBone Black or Teensy 3.1 + +How to program an SPI flash chip with the BeagleBone Black or Teensy 3.1 +======================================================================== This document exists as a guide for reading from or writing to an SPI flash chip with the BeagleBone Black, using the @@ -26,10 +28,12 @@ flashing on the ThinkPad X200, but it should work for other targets. here is a photo of the setup for the teensy: <http://h5ai.swiftgeek.net/IMG_20160601_120855.jpg> -Onto the Beaglebone black... +Onto the Beaglebone black\... [Back to previous index](./) + + Hardware requirements ===================== @@ -100,6 +104,8 @@ Shopping list (pictures of this hardware is shown later): [Back to top of page.](#pagetop) + + Setting up the 3.3V DC PSU ========================== @@ -108,21 +114,21 @@ page](https://en.wikipedia.org/wiki/Power_supply_unit_%28computer%29#Wiring_diag You can use pin 1 or 2 (orange wire) on a 20-pin or 24-pin ATX PSU for 3.3V, and any of the ground/earth sources (black cables) for ground. -Short PS\_ON# / Power on (green wire; pin 16 on 24-pin ATX PSU, or pin +Short PS\_ON\# / Power on (green wire; pin 16 on 24-pin ATX PSU, or pin 14 on a 20-pin ATX PSU) to a ground (black; there is one right next to it) using a wire/paperclip/jumper, then power on the PSU by grounding -PS\_ON# (this is also how an ATX motherboard turns on a PSU). +PS\_ON\# (this is also how an ATX motherboard turns on a PSU). -**DO **NOT** use pin 4, 6, do **NOT** use pin 19 or 20 (on a -20-pin ATX PSU), and DO **NOT** use pin 21, 22 or 23 (on a 24-pin -ATX PSU). Those wires (the red ones) are 5V, and they **WILL** kill -your flash chip. ***NEVER*** supply more than 3.3V to your flash +**DO \*\*NOT\*\* use pin 4, 6, do \*\*NOT\*\* use pin 19 or 20 (on a +20-pin ATX PSU), and DO \*\*NOT\*\* use pin 21, 22 or 23 (on a 24-pin +ATX PSU). Those wires (the red ones) are 5V, and they \*\*WILL\*\* kill +your flash chip. \*\*\*NEVER\*\*\* supply more than 3.3V to your flash chip (that is, if it's a 3.3V flash chip; 5V and 1.8V SPI flash chips do exist, but they are rare. Always check what voltage your chip takes. Most of them take 3.3V).** You only need one 3.3V supply and one ground for the flash chip, after -grounding PS\_ON#. +grounding PS\_ON\#. The male end of a 0.1" or 2.54mm header cable is not thick enough to remain permanently connected to the ATX PSU on its own. When connecting @@ -131,10 +137,11 @@ to a thicker piece of wire (you could use a paper clip), or wedge the male end of the jumper cable into the sides of the hole in the connector, instead of going through the centre. -Here is an example set up: - +Here is an example set up:\ ![](images/x200/psu33.jpg "Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net> see license notice at the end of this document") + + Accessing the operating system on the BBB ========================================= @@ -150,27 +157,26 @@ Alternatives to SSH (in case SSH fails) --------------------------------------- You can also use a serial FTDI debug board with GNU Screen, to access -the serial console. - - # screen /dev/ttyUSB0 115200 -Here are some example photos: - -![](images/x200/ftdi.jpg) ![](images/x200/ftdi_port.jpg) +the serial console.\ +\# **screen /dev/ttyUSB0 115200**\ +Here are some example photos:\ +![](images/x200/ftdi.jpg) ![](images/x200/ftdi_port.jpg)\ You can also connect the USB cable from the BBB to another computer and a new network interface will appear, with its own IP address. This is -directly accessible from SSH, or screen: - -# **screen /dev/ttyACM0 115200** +directly accessible from SSH, or screen:\ +\# **screen /dev/ttyACM0 115200** You can also access the uboot console, using the serial method instead of SSH. + + Setting up spidev on the BBB ============================ Log on as root on the BBB, using either SSH or a serial console as -defined in [#bbb\_access](#bbb_access). Make sure that you have +defined in [\#bbb\_access](#bbb_access). Make sure that you have internet access on your BBB. Follow the instructions at @@ -197,24 +203,22 @@ contents of this file with: # Description: Starts LED aging (whatever that is) ### END INIT INFO - x=\$(/bin/ps -ef | /bin/grep "[l]ed_acc") - if [ ! -n "\$x" -a -x /usr/bin/led_acc ]; then + x=$(/bin/ps -ef | /bin/grep "[l]ed_acc") + if [ ! -n "$x" -a -x /usr/bin/led_acc ]; then /usr/bin/led_acc & fi Run **apt-get update** and **apt-get upgrade** then reboot the BBB, before continuing. -Check that the firmware exists: - - # ls /lib/firmware/BB-SPI0-01-00A0.* +Check that the firmware exists:\ +\# **ls /lib/firmware/BB-SPI0-01-00A0.\***\ Output: /lib/firmware/BB-SPI0-01-00A0.dtbo -Then: - - # echo BB-SPI0-01 > /sys/devices/bone\_capemgr.*/slots - # cat /sys/devices/bone\_capemgr.*/slots +Then:\ +\# **echo BB-SPI0-01 > /sys/devices/bone\_capemgr.\*/slots**\ +\# **cat /sys/devices/bone\_capemgr.\*/slots**\ Output: 0: 54:PF--- @@ -225,16 +229,14 @@ Output: 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPI0-01 -Verify that the spidev device now exists: - - # ls -al /dev/spid* +Verify that the spidev device now exists:\ +\# **ls -al /dev/spid\***\ Output: crw-rw---T 1 root spi 153, 0 Nov 19 21:07 /dev/spidev1.0 Now the BBB is ready to be used for flashing. Make this persist across -reboots: - +reboots:\ In /etc/default/capemgr add **CAPE=BB-SPI0-01** at the end (or change the existing **CAPE=** entry to say that, if an entry already exists. @@ -250,9 +252,8 @@ libreboot\_src, and put the ARM binary for it on your BBB. Finally, get the ROM image that you would like to flash and put that on your BBB. -Now test flashrom: - - # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 +Now test flashrom:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ Output: Calibrating delay loop... OK. @@ -262,6 +263,8 @@ Output: This means that it's working (the clip isn't connected to any flash chip, so the error is fine). + + Connecting the Pomona 5250/5252 =============================== @@ -330,12 +333,13 @@ should.** if you need to extend the 3.3v psu leads, just use the same colour M-F leads, **but** keep all other leads short (10cm or less) -You should now have something that looks like this: - +You should now have something that looks like this:\ ![](images/x200/5252_bbb0.jpg) ![](images/x200/5252_bbb1.jpg) [Back to top of page.](#pagetop) + + Notes about stability {#stability} ===================== @@ -344,7 +348,7 @@ not always. That page has some notes about using resistors to affect stability. Currently, we use spispeed=512 (512kHz) but it is possible to use higher speeds while maintaining stability. -tty0\_ in #libreboot was able to get better flashing speeds with the +tty0\_ in \#libreboot was able to get better flashing speeds with the following configuration: - "coax" with 0.1 mm core and aluminum foley (from my kitchen), add @@ -354,12 +358,11 @@ following configuration: - See this image: <http://i.imgur.com/qHGxKpj.jpg> - He was able to flash at 50MHz (lower speeds are also fine). -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> - -Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net> -Copyright © 2015 Albin Söderqvist +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ +Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net>\ +Copyright © 2015 Albin Söderqvist\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/c201.md b/docs/install/c201.md @@ -1,12 +1,16 @@ -% ASUS Chromebook C201 installation guide + +ASUS Chromebook C201 installation guide +======================================= These instructions are for installing Libreboot to the ASUS Chromebook C201. Since the device ships with Coreboot, the installation instructions are the same before and after flashing Libreboot for the first time. + **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/#build](../git/#build)).** +the sources first (see [../git/\#build](../git/#build)).** + Look at the [list of ROM images](#rom) to see which image is compatible with your device. @@ -19,14 +23,12 @@ flashrom version. **Google's modified version of flashrom** is free software and its source code is made available by Google: -[flashrom](https://chromium.googlesource.com/chromiumos/third_party/flashrom/). - +[flashrom](https://chromium.googlesource.com/chromiumos/third_party/flashrom/).\ It is not distributed along with Libreboot yet. However, it is preinstalled on the device, with ChromeOS. Installing Libreboot internally requires sufficient privileges on the -system installed on the device. - +system installed on the device.\ When the device has ChromeOS installed (as it does initially), it is necessary to gain root privileges in ChromeOS, to be able to access a root shell. @@ -45,11 +47,15 @@ root shell. - [Debian GNU+Linux is recommended for this device](#debian) (TODO: instructions for Devuan) + + + Gaining root privileges on ChromeOS In order to gain root privileges on ChromeOS, developer mode has to be enabled from the recovery mode screen and debugging features have to be enabled in ChromeOS. + Instructions to access the [recovery mode screen](../depthcharge/#recovery_mode_screen) and [enabling developer mode](../depthcharge/#enabling_developer_mode) are available on the page @@ -62,8 +68,7 @@ or by pressing **Ctrl + D** After the system has booted, root access can be enabled by clicking on the **Enable debugging features** link. A confirmation dialog will ask -whether to proceed. - +whether to proceed.\ After confirming by clicking **Proceed**, the device will reboot and ask for the root password to set. Finally, the operation has to be confirmed by clicking **Enable**. @@ -72,11 +77,15 @@ After setting the root password, it becomes possible to log-in as root. A tty prompt can be obtained by pressing **Ctrl + Alt + Next**. The **Next** key is the one on the top left of the keyboard. + + + Preparing the device for the installation Before installing Libreboot on the device, both its software and hardware has to be prepared to allow the installation procedure and to ensure that security features don't get in the way. + Configuring verified boot parameters {#configuring_verified_boot_parameters} ------------------------------------ @@ -91,6 +100,8 @@ parameters](../depthcharge/#configuring_verified_boot_parameters): Those changes can be reverted later, when the device is known to be in a working state. + + Removing the write protect screw {#removing_write_protect_screw} -------------------------------- @@ -113,6 +124,9 @@ screw](images/c201/wp-screw.jpg)](images/c201/wp-screw.jpg) The write protect screw can be put back in place later, when the device is known to be in a working state. + + + Installing Libreboot to the SPI flash {#installing_libreboot_spi_flash} ===================================== @@ -121,6 +135,7 @@ that are used to implement parts of the CrOS security system. Libreboot is installed in the *read-only* coreboot partition, that becomes writable after removing the write-protect screw. + Installing Libreboot internally, from the device {#installing_libreboot_internally} ------------------------------------------------ @@ -132,31 +147,28 @@ transferred to the device. The following operations have to be executed with root privileges on the device (e.g. using the *root* account). In addition, the -**cros-flash-replace** script has to be made executable: +**cros-flash-replace** script has to be made executable:\ +\# **chmod a+x cros-flash-replace**\ - # chmod a+x cros-flash-replace - -The SPI flash has to be read first: - - # flashrom -p host -r flash.img +The SPI flash has to be read first:\ +\# **flashrom -p host -r flash.img**\ **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: - - # ./cros-flash-replace flash.img coreboot ro-frid +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. -The resulting flash image can then be flashed back: +The resulting flash image can then be flashed back:\ +\# **flashrom -p host -w flash.img**\ - # flashrom -p host -w flash.img +You should also see within the output the following:\ +**"Verifying flash\... VERIFIED."** -You should also see within the output the following: +Shut down. The device will now boot to Libreboot. -**"Verifying flash... VERIFIED."** -Shut down. The device will now boot to Libreboot. Installing Libreboot externally, with a SPI flash programmer {#installing_libreboot_externally} ------------------------------------------------------------ @@ -166,7 +178,7 @@ to be opened. The SPI flash is located next to the write protect screw. Its layout is indicated in the picture below. Note that it is not necessary to connect -**WP#** since removing the screw already connects it to ground. Before +**WP\#** since removing the screw already connects it to ground. Before writing to the chip externally, the battery connector has to be detached. It is located under the heat spreader, that has to be unscrewed from the rest of the case. The battery connector is located on @@ -182,33 +194,29 @@ transferred to the host. The following operations have to be executed with root privileges on the host (e.g. using the *root* account). In addition, the -**cros-flash-replace** script has to be made executable: - - # chmod a+x cros-flash-replace +**cros-flash-replace** script has to be made executable:\ +\# **chmod a+x cros-flash-replace**\ -The SPI flash has to be read first (using the right spi programmer): - - # flashrom -p *programmer* -r flash.img +The SPI flash has to be read first (using the right spi programmer):\ +\# **flashrom -p *programmer* -r flash.img**\ **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: - - # ./cros-flash-replace flash.img coreboot ro-frid +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. The resulting flash image can then be flashed back (using the right spi -programmer): +programmer):\ +\# **flashrom -p *programmer* -w flash.img**\ - # flashrom -p *programmer* -w flash.img - -You should also see within the output the following: - -**"Verifying flash... VERIFIED."** +You should also see within the output the following:\ +**"Verifying flash\... VERIFIED."** The device will now boot to Libreboot. + Debian GNU+Linux {#debian} ---------------- @@ -221,8 +229,9 @@ See <https://wiki.debian.org/InstallingDebianOn/Asus/C201>. [Back to top of page.](#pagetop) -Copyright © 2015 Paul Kocialkowski <contact@paulk.fr> + +Copyright © 2015 Paul Kocialkowski <contact@paulk.fr>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/d510mo.md b/docs/install/d510mo.md @@ -1,29 +1,35 @@ -% D510MO flashing tutorial + +D510MO flashing tutorial +======================== This guide is for those who want libreboot on their Intel D510MO motherboard while they still have the original BIOS present. + + + Flash chip size {#flashchips} =============== -Use this to find out: - -# **flashrom -p internal -V** +Use this to find out:\ +\# **flashrom -p internal -V** [Back to top of page.](#pagetop) + + Flashing instructions {#clip} ===================== Refer to [bbb\_setup.html](bbb_setup.html) for how to set up the BBB for flashing. -This is an image of the flash chip, for reference: - +This is an image of the flash chip, for reference:\ ![](../images/d510mo/d510mo.jpg) -Copyright © 2016 Leah Rowe <info@minifree.org> + +Copyright © 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/d945gclf.md b/docs/install/d945gclf.md @@ -1,4 +1,6 @@ -% Intel D945GCLF flashing tutorial + +Intel D945GCLF flashing tutorial +================================ This guide is for those who want libreboot on their Intel D945GCLF motherboard while they still have the original BIOS present. @@ -6,18 +8,21 @@ motherboard while they still have the original BIOS present. For information about this board, go to [../hcl/d945gclf.html](../hcl/d945gclf.html) + + + Flashing instructions {#clip} ===================== Refer to [bbb\_setup.html](bbb_setup.html) for how to set up the BBB for external flashing. -Here is an image of the flash chip: - +Here is an image of the flash chip:\ ![](../images/d945gclf/d945gclf_spi.jpg) -Copyright © 2016 Leah Rowe <info@minifree.org> + +Copyright © 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/ga-g41m-es2l.md b/docs/install/ga-g41m-es2l.md @@ -1,17 +1,23 @@ -% GA-G41M-ES2L flashing tutorial + +GA-G41M-ES2L flashing tutorial +============================== This guide is for those who want libreboot on their Intel GA-G41M-ES2L motherboard while they still have the original BIOS present. + + + Flash chip size {#flashchips} =============== -Use this to find out: - -# **flashrom -p internal -V** +Use this to find out:\ +\# **flashrom -p internal -V** [Back to top of page.](#pagetop) + + Flashing instructions {#clip} ===================== @@ -22,19 +28,16 @@ by connecting 3v3 to /CS of that chip, so you will actually need 2 test clips (you also need to connect GND on the chip that you're disabling).** -Here is an image of the flash chip: - +Here is an image of the flash chip:\ ![](../images/ga-g41m-es2l/ga-g41m-es2l.jpg) Internal flashing is possible. Boot with the proprietary BIOS and GNU+Linux. There are 2 flash chips (one is backup). -Flash the first chip: - +Flash the first chip:\ **./flashrom -p internal:dualbiosindex=0 -w libreboot.rom** -Flash the second chip: - +Flash the second chip:\ **./flashrom -p internal:dualbiosindex=1 -w libreboot.rom** NOTE: you can still boot the system with just the main flash chip @@ -48,8 +51,9 @@ NOTE: due to a bug in the hardware, the MAC address is hardcoded in coreboot-libre. Therefore, you must set your own MAC address in your operating system. -Copyright © 2016 Leah Rowe <info@minifree.org> + +Copyright © 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/index.md b/docs/install/index.md @@ -1,4 +1,6 @@ -% Installing libreboot + +Installing libreboot +==================== This section relates to installing libreboot on supported targets. @@ -9,6 +11,8 @@ that has CONFIG\_STRICT\_DEVMEM not enabled. [Back to previous index](../) + + General information ------------------- @@ -48,6 +52,8 @@ Flashing via hardware methods, on system: - [ThinkPad T400](t400_external.html) - [ThinkPad T500](t500_external.html) + + Information about libreboot ROM images {#rom} ====================================== @@ -71,7 +77,7 @@ as the keymap in GNU+Linux is concerned. Keymaps are named appropriately according to each keyboard layout support in GRUB. To learn how these keymaps are created, see -[../grub/#grub\_keyboard](../grub/#grub_keyboard) +[../grub/\#grub\_keyboard](../grub/#grub_keyboard) QEMU ---- @@ -94,6 +100,8 @@ information. [Back to top of page.](#pagetop) + + How to update or install libreboot (if you are already running libreboot or coreboot) {#flashrom} ===================================================================================== @@ -103,8 +111,10 @@ any dedicated hardware. In other words, you can do everything entirely in software, directly from the OS that is running on your libreboot system. + **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/#build](../git/#build)).** +the sources first (see [../git/\#build](../git/#build)).** + Look at the [list of ROM images](#rom) to see which image is compatible with your device. @@ -117,8 +127,8 @@ coreboot), then the flashing instructions for your system are going to be different. X60/T60 users running the proprietary firmware should refer to -[#flashrom\_lenovobios](#flashrom_lenovobios). MacBook2,1 users running -Apple EFI should refer to [#flashrom\_macbook21](#flashrom_macbook21) +[\#flashrom\_lenovobios](#flashrom_lenovobios). MacBook2,1 users running +Apple EFI should refer to [\#flashrom\_macbook21](#flashrom_macbook21) X200 users, refer to [x200\_external.html](x200_external.html), R400 users refer to [r400\_external.html](r400_external.html), T400 users @@ -221,7 +231,7 @@ onboard ethernet chipset is located inside the flash chip. Libreboot ROM images for these laptops contain a generic MAC address by default, but this is not what you want. *Make sure to change the MAC address inside the ROM image, before flashing it. The instructions on -[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) show how to do this.* It is important that you change the default MAC address, before @@ -243,14 +253,13 @@ ROM image, and it should work.** Flash chip size --------------- -Use this to find out: - -# **flashrom -p internal -V** +Use this to find out:\ +\# **flashrom -p internal -V** All good? --------- -Excellent! Moving on... +Excellent! Moving on\... Download the *libreboot\_util.tar.xz* archive, and extract it. Inside, you will find a directory called *flashrom*. This contains statically @@ -263,56 +272,66 @@ what CPU architecture you have (e.g. i686, x86\_64) and use the appropriate executable. It is also possible for you to build these executables from the libreboot source code archives. -How to update the flash chip contents: +How to update the flash chip contents:\ \$ **sudo ./flash update [yourrom.rom](#rom)** + + 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)** -You should see **"Verifying flash... VERIFIED."** written at the end + + +You should see **"Verifying flash\... VERIFIED."** written at the end of the flashrom output. **Shut down** after you see this, and then boot up again after a few seconds. + +[Back to top of page](#pagetop) + + + ThinkPad X60/T60: Initial installation guide (if running the proprietary firmware) {#flashrom_lenovobios} ================================================================================== **This is for the ThinkPad X60 and T60 while running Lenovo BIOS. If you already have coreboot or libreboot running, then go to -[#flashrom](#flashrom) instead!** +[\#flashrom](#flashrom) instead!** **If you are flashing a Lenovo ThinkPad T60, be sure to read -[../hcl/#supported\_t60\_list](../hcl/#supported_t60_list)** +[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list)** + **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/#build](../git/#build)).** +the sources first (see [../git/\#build](../git/#build)).** + **Warning: this guide will not instruct the user how to backup the original Lenovo BIOS firmware. These backups are tied to each system, and will not work on any other. For that, please refer to <http://www.coreboot.org/Board:lenovo/x60/Installation>.** + **If you're using libreboot 20150518, note that there is a mistake in the flashing script. do this: *rm -f patch && wget -O flash https://notabug.org/vimuser/libreboot/raw/9d850543ad90b72e0e333c98075530b31e5d23f1/flash && chmod +x flash*** -The first half of the procedure is as follows: - +The first half of the procedure is as follows:\ \$ **sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom).** -You should see within the output the following: + +You should see within the output the following:\ **"Updated BUC.TS=1 - 64kb address ranges at 0xFFFE0000 and 0xFFFF0000 are swapped"**. -You should also see within the output the following: - +You should also see within the output the following:\ **"Your flash chip is in an unknown state"**, **"FAILED"** and - "DO NOT REBOOT OR POWEROFF" +**"DO NOT REBOOT OR POWEROFF"**\ Seeing this means that the operation was a **resounding** success! **DON'T PANIC**. @@ -321,65 +340,75 @@ See this link for more details: If the above is what you see, then **SHUT DOWN**. Wait a few seconds, and then boot; libreboot is running, but there is a 2nd procedure -***needed*** (see below). +**\*needed\*** (see below). -When you have booted up again, you must also do this: -\$ **sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom)** -If flashing fails at this stage, try the following: +When you have booted up again, you must also do this:\ +\$ **sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom)** +If flashing fails at this stage, try the following:\ \$ **sudo ./flashrom/i686/flashrom -p internal:laptop=force\_I\_want\_a\_brick -w [yourrom.rom](#rom)** -You should see within the output the following: + +You should see within the output the following:\ **"Updated BUC.TS=0 - 128kb address range 0xFFFE0000-0xFFFFFFFF is untranslated"** -You should also see within the output the following: +You should also see within the output the following:\ +**"Verifying flash\... VERIFIED."** -**"Verifying flash... VERIFIED."** [Back to top of page.](#pagetop) + + MacBook2,1: Initial installation guide (if running the proprietary firmware) {#flashrom_macbook21} ============================================================================ + **If you have a MacBook1,1, refer to -[../hcl/#macbook11](../hcl/#macbook11) for flashing instructions.** +[../hcl/\#macbook11](../hcl/#macbook11) for flashing instructions.** + **This is for the MacBook2,1 while running Apple EFI firmware. If you already have coreboot or libreboot running, then go to -[#flashrom](#flashrom) instead!** +[\#flashrom](#flashrom) instead!** Be sure to read the information in -[../hcl/#macbook21](../hcl/#macbook21). +[../hcl/\#macbook21](../hcl/#macbook21). **Warning: this guide will not instruct the user how to backup the original Apple EFI firmware. For that, please refer to <http://www.coreboot.org/Board:apple/macbook21>.** + **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/#build](../git/#build)).** +the sources first (see [../git/\#build](../git/#build)).** + Look at the [list of ROM images](#rom) to see which image is compatible with your device. -Use this flashing script, to install libreboot: +Use this flashing script, to install libreboot:\ \$ **sudo ./flash i945apple\_firstflash [yourrom.rom](#rom)** -You should also see within the output the following: -**"Verifying flash... VERIFIED."** + +You should also see within the output the following:\ +**"Verifying flash\... VERIFIED."** Shut down. + [Back to top of page.](#pagetop) -Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/kcma-d8.md b/docs/install/kcma-d8.md @@ -1,4 +1,6 @@ -% KCMA-D8 external flashing instructions + +KCMA-D8 external flashing instructions +====================================== Initial flashing instructions for kcma-d8. @@ -19,6 +21,9 @@ TODO: show photos here, and other info. preinstalled](#preinstall) - [External programmer](#programmer) + + + External programmer {#programmer} =================== @@ -30,8 +35,9 @@ motherboard, which you take out and then re-flash with libreboot, using the programmer. **DO NOT** remove the chip with your hands. Use a chip extractor tool. -Copyright © 2016 Leah Rowe <info@minifree.org> + +Copyright © 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/kgpe-d16.md b/docs/install/kgpe-d16.md @@ -1,4 +1,6 @@ -% KGPE-D16 external flashing instructions + +KGPE-D16 external flashing instructions +======================================= Initial flashing instructions for KGPE-D16. @@ -19,6 +21,9 @@ TODO: show photos here, and other info. preinstalled](#preinstall) - [External programmer](#programmer) + + + KGPE-D16 boards (and full systems) with libreboot preinstalled {#preinstall} ============================================================== @@ -28,6 +33,8 @@ GNU+Linux distribution. Check the [suppliers](../../suppliers) page for more information. + + External programmer {#programmer} =================== @@ -39,8 +46,9 @@ motherboard, which you take out and then re-flash with libreboot, using the programmer. **DO NOT** remove the chip with your hands. Use a chip extractor tool. -Copyright © 2015 Leah Rowe <info@minifree.org> + +Copyright © 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md @@ -1,4 +1,6 @@ -% Flashing the R400 with a BeagleBone Black + +Flashing the R400 with a BeagleBone Black +========================================= Initial flashing instructions for R400. @@ -11,12 +13,17 @@ ROM properly first. Although ROM images are provided pre-built in libreboot, there are some modifications that you need to make to the one you chose before flashing. (instructions referenced later in this guide) + + + Libreboot T400 {#t400} ============== You may also be interested in the smaller, more portable [Libreboot T400](t400_external.html). + + Serial port {#serial_port} ----------- @@ -24,6 +31,8 @@ EHCI debug might not be needed. It has been reported that the docking station for this laptop has a serial port, so it might be possible to use that instead. + + A note about CPUs ================= @@ -38,6 +47,8 @@ Quad-core CPUs Incompatible. Do not use. + + A note about GPUs ================= @@ -54,17 +65,20 @@ initialization works all the same. CPU paste required ================== -See [#paste](#paste). +See [\#paste](#paste). + + Flash chip size {#flashchips} =============== -Use this to find out: - - # flashrom -p internal -V +Use this to find out:\ +\# **flashrom -p internal -V**\ [Back to top of page.](#pagetop) + + MAC address {#macaddress} =========== @@ -78,6 +92,8 @@ image before flashing it. It will be written in one of these locations: ![](images/t400/macaddress0.jpg) ![](images/t400/macaddress1.jpg) ![](images/x200/disassembly/0001.jpg) + + Initial BBB configuration ========================= @@ -115,95 +131,73 @@ for SOIC-8 (clip: Pomona 5250): Disassembly ----------- -Remove all screws: - -![](images/r400/0000.jpg) - -Remove the HDD and optical drive: - -![](images/r400/0001.jpg) - -Remove the hinge screws: - +Remove all screws:\ +![](images/r400/0000.jpg)\ +Remove the HDD and optical drive:\ +![](images/r400/0001.jpg)\ +Remove the hinge screws:\ ![](images/r400/0002.jpg) ![](images/r400/0003.jpg) -Remove the palm rest and keyboard: - +Remove the palm rest and keyboard:\ ![](images/r400/0004.jpg) ![](images/r400/0005.jpg) -Remove these screws, and then remove the bezel: - +Remove these screws, and then remove the bezel:\ ![](images/r400/0006.jpg) ![](images/r400/0007.jpg) Remove the speaker screws, but don't remove the speakers yet (just set -them loose): - +them loose):\ ![](images/r400/0008.jpg) ![](images/r400/0009.jpg) ![](images/r400/0010.jpg) -Remove these screws, and then remove the metal plate: - +Remove these screws, and then remove the metal plate:\ ![](images/r400/0011.jpg) ![](images/r400/0012.jpg) ![](images/r400/0013.jpg) -Remove the antennas from the wifi card, and then start unrouting them: - +Remove the antennas from the wifi card, and then start unrouting them:\ ![](images/r400/0014.jpg) ![](images/r400/0015.jpg) ![](images/r400/0016.jpg) ![](images/r400/0017.jpg) ![](images/r400/0018.jpg) ![](images/r400/0019.jpg) -Disconnect the LCD cable from the motherboard: - +Disconnect the LCD cable from the motherboard:\ ![](images/r400/0020.jpg) ![](images/r400/0021.jpg) ![](images/r400/0022.jpg) ![](images/r400/0023.jpg) -Remove the hinge screws, and then remove the LCD panel: - +Remove the hinge screws, and then remove the LCD panel:\ ![](images/r400/0024.jpg) ![](images/r400/0025.jpg) ![](images/r400/0026.jpg) ![](images/r400/0027.jpg) -Remove this: - +Remove this:\ ![](images/r400/0028.jpg) ![](images/r400/0029.jpg) -Remove this long cable (there are 3 connections): - +Remove this long cable (there are 3 connections):\ ![](images/r400/0030.jpg) ![](images/r400/0031.jpg) ![](images/r400/0032.jpg) ![](images/r400/0033.jpg) -Disconnect the speaker cable, and remove the speakers: - +Disconnect the speaker cable, and remove the speakers:\ ![](images/r400/0034.jpg) Remove the heatsink screws, remove the fan and then remove the -heatsink/fan: - +heatsink/fan:\ ![](images/r400/0035.jpg) ![](images/r400/0036.jpg) ![](images/r400/0037.jpg) ![](images/r400/0038.jpg) -Remove the NVRAM battery: - +Remove the NVRAM battery:\ ![](images/r400/0039.jpg) ![](images/r400/0040.jpg) -Remove this screw: - +Remove this screw:\ ![](images/r400/0041.jpg) ![](images/r400/0042.jpg) -Disconnect the AC jack: - +Disconnect the AC jack:\ ![](images/r400/0043.jpg) ![](images/r400/0044.jpg) -Remove this screw and then remove what is under it: - +Remove this screw and then remove what is under it:\ ![](images/r400/0045.jpg) -Remove this: - +Remove this:\ ![](images/r400/0046.jpg) Lift the motherboard (which is still inside the cage) from the side on -the right, removing it completely: - +the right, removing it completely:\ ![](images/r400/0047.jpg) ![](images/r400/0048.jpg) Remove all screws, marking each hole so that you know where to re-insert @@ -212,23 +206,19 @@ that they were in before removal: ![](images/r400/0049.jpg) ![](images/r400/0050.jpg) Remove the motherboard from the cage, and the SPI flash chip will be -next to the memory slots: - +next to the memory slots:\ ![](images/r400/0051.jpg) ![](images/r400/0052.jpg) -Connect your programmer, then connect GND and 3.3V - +Connect your programmer, then connect GND and 3.3V\ ![](images/t400/0065.jpg) ![](images/t400/0066.jpg) ![](images/t400/0067.jpg) ![](images/t400/0069.jpg) ![](images/t400/0070.jpg) ![](images/t400/0071.jpg) A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is -also fine: - +also fine:\ ![](images/t400/0072.jpg) -Of course, make sure to turn on your PSU: - +Of course, make sure to turn on your PSU:\ ![](images/x200/disassembly/0013.jpg) Now, you should be ready to install libreboot. @@ -238,11 +228,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). - -Test that flashrom works: +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). - # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) @@ -255,24 +244,18 @@ In this case, the output was: Please specify which chip definition to use with the -c <chipname> option. How to backup factory.rom (change the -c option as neeed, for your flash -chip): - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory1.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory2.rom** - +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +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: - - # sha512sum factory*.rom +have been removed.\ +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 is useful for reverse engineering work, if there is a desirable @@ -280,20 +263,19 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** -Now flash it: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +Now flash it:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V** ![](images/x200/disassembly/0015.jpg) -You might see errors, but if it says **Verifying flash... VERIFIED** at +You might see errors, but if it says **Verifying flash\... VERIFIED** at the end, then it's flashed and should boot. If you see errors, try again (and again, and again); the message **Chip content is identical to the requested image** is also an indication of a successful @@ -314,6 +296,8 @@ Example output from running the command (see above): [Back to top of page.](#pagetop) + + Thermal paste (IMPORTANT) ========================= @@ -331,13 +315,15 @@ NOTE: the photo above is for illustration purposes only, and does not show how to properly apply the thermal paste. Other guides online detail the proper application procedure. + + Wifi ==== The R400 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). Some R400 laptops might come with an Atheros chipset, but this is 802.11g only. @@ -348,10 +334,11 @@ whitelist of approved chips, and it will refuse to boot if you use an 'unauthorized' wifi card. The following photos show an Atheros AR5B95 being installed, to replace -the Intel chip that this R400 came with: - +the Intel chip that this R400 came with:\ ![](images/t400/0012.jpg) ![](images/t400/ar5b95.jpg) + + WWAN ==== @@ -362,6 +349,8 @@ track your movements. Not to be confused with wifi (wifi is fine). + + Memory ====== @@ -375,10 +364,11 @@ Make sure that the RAM you buy is the 2Rx8 density. be useful for RAM compatibility info (note: coreboot raminit is different, so this page might be BS) -The following photo shows 8GiB (2x4GiB) of RAM installed: - +The following photo shows 8GiB (2x4GiB) of RAM installed:\ ![](images/t400/memory.jpg) + + Boot it! -------- @@ -388,8 +378,9 @@ You should see something like this: Now [install GNU+Linux](../gnulinux/). -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md @@ -1,4 +1,6 @@ -% How to program an SPI flash chip with the Raspberry Pi + +How to program an SPI flash chip with the Raspberry Pi +====================================================== This document exists as a guide for reading from or writing to an SPI flash chip with the Raspberry Pi, using the @@ -11,6 +13,8 @@ SOIC-16). [Back to previous index](../) + + [](#raspberry-pi-thinkpad-x60t60-and-macbook-21){#user-content-raspberry-pi-thinkpad-x60t60-and-macbook-21 .anchor}Raspberry Pi (ThinkPad X60/T60 and Macbook 2,1) ------------------------------------------------------------------------------------------------------------------------------------------------------------------ @@ -53,7 +57,7 @@ B+ with 40 pins, start counting from the right and leave 14 pins): 1234 ~~~ Palmrest (back) ~~ - Pin # SPI Pin Name BP (Seeed) BP (Spkfun) [Beagleboard Black](http://beagleboard.org/Support/bone101#headers) [Raspberry Pi](images/rpi/0000.jpg) + Pin \# SPI Pin Name BP (Seeed) BP (Spkfun) [Beagleboard Black](http://beagleboard.org/Support/bone101#headers) [Raspberry Pi](images/rpi/0000.jpg) -------- -------------- ------------ ------------- --------------------------------------------------------------------- ------------------------------------- 1 CS White Red Pin 17 24 2 MISO Black Brown Pin 21 21 @@ -156,7 +160,7 @@ successfully. If not, just flash again. ### [](#raspberry-pi-pinout-diagrams){#user-content-raspberry-pi-pinout-diagrams .anchor}Raspberry Pi Pinout Diagrams - MCP 3008 Pin Pi GPIO Pin # Pi Pin Name + MCP 3008 Pin Pi GPIO Pin \# Pi Pin Name ----- ---------- ---------------- -------------------- 16 `VDD` 1 `3.3 V` 15 `VREF` 1 `3.3 V` @@ -206,7 +210,7 @@ GPG signature as well. x86# gpg --keyserver prefered.keyserver.org --recv-keys 0x656F212E - x86# for signature in \$(ls *.sig); do gpg --verify \$signature; done + x86# for signature in $(ls *.sig); do gpg --verify $signature; done Extract NOOBS and libreboot. @@ -281,7 +285,7 @@ text. ![](images/rpi/0002.jpg) - Pin # SPI Pin Name Raspberry Pi Pin \# + Pin \# SPI Pin Name Raspberry Pi Pin \# -------- -------------- --------------------- 1 *not used* *not used* 2 3.3V 1 @@ -289,7 +293,7 @@ text. 4 *not used* *not used* 5 *not used* *not used* 6 *not used* *not used* - 7 CS # 24 + 7 CS\# 24 8 S0/SIO1 21 9 *not used* *not used* 10 GND 25 @@ -363,8 +367,8 @@ GPIO Pinouts: ![](images/rpi/0009.png) ![](images/rpi/0010.png) -> *Diagram made by ["Pacman" from Win-Raid -> Forums*](http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html) +> \*Diagram made by ["Pacman" from Win-Raid +> Forums\*](http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html) SOIC Pinouts: @@ -421,14 +425,12 @@ box.](http://www.flashrom.org/RaspberryPi) - [Win-Raid - Recover from Failed BIOS Flashing using Raspberry Pi](http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html) -Copyright © 2014, 2015 Lawrence Wu <sagnessagiel@gmail.com> - -Copyright © 2015 snuffeluffegus <> - -Copyright © 2015 Kevin Keijzer <> -Copyright © 2016 Leah Rowe <info@minifree.org> +Copyright © 2014, 2015 Lawrence Wu <sagnessagiel@gmail.com>\ +Copyright © 2015 snuffeluffegus <>\ +Copyright © 2015 Kevin Keijzer <>\ +Copyright © 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md @@ -1,4 +1,6 @@ -% Flashing the T400 with a BeagleBone Black + +Flashing the T400 with a BeagleBone Black +========================================= Initial flashing instructions for T400. @@ -14,6 +16,9 @@ the screws on page 144 (with title "1130 Keyboard bezel") are swapped and if you follow the HMM you will punch a hole through the bezel in the upper right corner. + + + T400 laptops with libreboot pre-installed {#preinstall} ========================================= @@ -23,6 +28,8 @@ GNU+Linux distribution. Check the [suppliers](../../suppliers) page for more information. + + Serial port {#serial_port} ----------- @@ -30,6 +37,8 @@ EHCI debug might not be needed. It has been reported that the docking station for this laptop has a serial port, so it might be possible to use that instead. + + A note about CPUs ================= @@ -43,6 +52,8 @@ Quad-core CPUs Incompatible. Do not use. + + A note about GPUs ================= @@ -59,17 +70,20 @@ initialization works all the same. CPU paste required ================== -See [#paste](#paste). +See [\#paste](#paste). + + Flash chip size {#flashchips} =============== -Use this to find out: - -# **flashrom -p internal -V** +Use this to find out:\ +\# **flashrom -p internal -V** [Back to top of page.](#pagetop) + + MAC address {#macaddress} =========== @@ -83,6 +97,8 @@ image before flashing it. It will be written in one of these locations: ![](images/t400/macaddress0.jpg) ![](images/t400/macaddress1.jpg) ![](images/x200/disassembly/0001.jpg) + + Initial BBB configuration ========================= @@ -121,90 +137,72 @@ for SOIC-8 (clip: Pomona 5250): The procedure ------------- -Remove *all* screws, placing them in the order that you removed them: - +Remove *all* screws, placing them in the order that you removed them:\ ![](images/t400/0001.jpg) ![](images/t400/0002.jpg) -Remove those three screws then remove the rear bezel: - +Remove those three screws then remove the rear bezel:\ ![](images/t400/0003.jpg) ![](images/t400/0004.jpg) ![](images/t400/0005.jpg) ![](images/t400/0006.jpg) -Remove the speakers: - +Remove the speakers:\ ![](images/t400/0007.jpg) ![](images/t400/0008.jpg) ![](images/t400/0009.jpg) ![](images/t400/0010.jpg) ![](images/t400/0011.jpg) -Remove the wifi: - +Remove the wifi:\ ![](images/t400/0012.jpg) ![](images/t400/0013.jpg) -Remove this cable: - +Remove this cable:\ ![](images/t400/0014.jpg) ![](images/t400/0015.jpg) ![](images/t400/0016.jpg) ![](images/t400/0017.jpg) ![](images/t400/0018.jpg) -Unroute those antenna wires: - +Unroute those antenna wires:\ ![](images/t400/0019.jpg) ![](images/t400/0020.jpg) ![](images/t400/0021.jpg) ![](images/t400/0022.jpg) ![](images/t400/0023.jpg) -Remove the LCD assembly: - +Remove the LCD assembly:\ ![](images/t400/0024.jpg) ![](images/t400/0025.jpg) ![](images/t400/0026.jpg) ![](images/t400/0027.jpg) ![](images/t400/0028.jpg) ![](images/t400/0029.jpg) ![](images/t400/0030.jpg) ![](images/t400/0031.jpg) -Disconnect the NVRAM battery: - +Disconnect the NVRAM battery:\ ![](images/t400/0033.jpg) -Disconnect the fan: - +Disconnect the fan:\ ![](images/t400/0034.jpg) -Unscrew these: - +Unscrew these:\ ![](images/t400/0035.jpg) ![](images/t400/0036.jpg) ![](images/t400/0037.jpg) ![](images/t400/0038.jpg) -Unscrew the heatsink, then lift it off: - +Unscrew the heatsink, then lift it off:\ ![](images/t400/0039.jpg) ![](images/t400/0040.jpg) -Disconnect the power jack: - +Disconnect the power jack:\ ![](images/t400/0041.jpg) ![](images/t400/0042.jpg) -Loosen this: - +Loosen this:\ ![](images/t400/0043.jpg) -Remove this: - +Remove this:\ ![](images/t400/0044.jpg) ![](images/t400/0045.jpg) ![](images/t400/0046.jpg) ![](images/t400/0047.jpg) ![](images/t400/0048.jpg) -Unscrew these: - +Unscrew these:\ ![](images/t400/0049.jpg) ![](images/t400/0050.jpg) -Remove this: - +Remove this:\ ![](images/t400/0051.jpg) ![](images/t400/0052.jpg) -Unscrew this: - +Unscrew this:\ ![](images/t400/0053.jpg) Remove the motherboard (the cage is still attached) from the right hand -side, then lift it out: - +side, then lift it out:\ ![](images/t400/0054.jpg) ![](images/t400/0055.jpg) ![](images/t400/0056.jpg) @@ -214,23 +212,19 @@ later): ![](images/t400/0057.jpg) ![](images/t400/0058.jpg) ![](images/t400/0059.jpg) ![](images/t400/0060.jpg) ![](images/t400/0061.jpg) ![](images/t400/0062.jpg) -Separate the motherboard: - +Separate the motherboard:\ ![](images/t400/0063.jpg) ![](images/t400/0064.jpg) -Connect your programmer, then connect GND and 3.3V - +Connect your programmer, then connect GND and 3.3V\ ![](images/t400/0065.jpg) ![](images/t400/0066.jpg) ![](images/t400/0067.jpg) ![](images/t400/0069.jpg) ![](images/t400/0070.jpg) ![](images/t400/0071.jpg) A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is -also fine: - +also fine:\ ![](images/t400/0072.jpg) -Of course, make sure to turn on your PSU: - +Of course, make sure to turn on your PSU:\ ![](images/x200/disassembly/0013.jpg) Now, you should be ready to install libreboot. @@ -240,11 +234,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). - -Test that flashrom works: +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). - # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) @@ -257,24 +250,18 @@ In this case, the output was: Please specify which chip definition to use with the -c <chipname> option. How to backup factory.rom (change the -c option as neeed, for your flash -chip): - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory1.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory2.rom** - +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +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: - - # sha512sum factory*.rom +have been removed.\ +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 is useful for reverse engineering work, if there is a desirable @@ -282,20 +269,19 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** -Now flash it: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +Now flash it:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V** ![](images/x200/disassembly/0015.jpg) -You might see errors, but if it says **Verifying flash... VERIFIED** at +You might see errors, but if it says **Verifying flash\... VERIFIED** at the end, then it's flashed and should boot. If you see errors, try again (and again, and again); the message **Chip content is identical to the requested image** is also an indication of a successful @@ -316,6 +302,8 @@ Example output from running the command (see above): [Back to top of page.](#pagetop) + + Thermal paste (IMPORTANT) ========================= @@ -333,13 +321,15 @@ NOTE: the photo above is for illustration purposes only, and does not show how to properly apply the thermal paste. Other guides online detail the proper application procedure. + + Wifi ==== The T400 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). Some T400 laptops might come with an Atheros chipset, but this is 802.11g only. @@ -350,10 +340,11 @@ whitelist of approved chips, and it will refuse to boot if you use an 'unauthorized' wifi card. The following photos show an Atheros AR5B95 being installed, to replace -the Intel chip that this T400 came with: - +the Intel chip that this T400 came with:\ ![](images/t400/0012.jpg) ![](images/t400/ar5b95.jpg) + + WWAN ==== @@ -364,6 +355,8 @@ track your movements. Not to be confused with wifi (wifi is fine). + + Memory ====== @@ -377,10 +370,11 @@ Make sure that the RAM you buy is the 2Rx8 density. be useful for RAM compatibility info (note: coreboot raminit is different, so this page might be BS) -The following photo shows 8GiB (2x4GiB) of RAM installed: - +The following photo shows 8GiB (2x4GiB) of RAM installed:\ ![](images/t400/memory.jpg) + + Boot it! -------- @@ -390,8 +384,9 @@ You should see something like this: Now [install GNU+Linux](../gnulinux/). -Copyright © 2015 Leah Rowe <info@minifree.org> + +Copyright © 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md @@ -1,4 +1,6 @@ -% Flashing the T500 with a BeagleBone Black + +Flashing the T500 with a BeagleBone Black +========================================= Initial flashing instructions for T500. @@ -6,12 +8,17 @@ This guide is for those who want libreboot on their ThinkPad T500 while they still have the original Lenovo BIOS present. This guide can also be followed (adapted) if you brick your T500, to know how to recover. + + + Libreboot T400 {#t400} ============== You may also be interested in the smaller, more portable [Libreboot T400](t400_external.html). + + Serial port {#serial_port} ----------- @@ -19,6 +26,8 @@ EHCI debug might not be needed. It has been reported that the docking station for this laptop has a serial port, so it might be possible to use that instead. + + A note about CPUs ================= @@ -33,6 +42,8 @@ Quad-core CPUs Incompatible. Do not use. + + A note about GPUs ================= @@ -49,17 +60,20 @@ initialization works all the same. CPU paste required ================== -See [#paste](#paste). +See [\#paste](#paste). + + Flash chip size {#flashchips} =============== -Use this to find out: - -# **flashrom -p internal -V** +Use this to find out:\ +\# **flashrom -p internal -V** [Back to top of page.](#pagetop) + + MAC address {#macaddress} =========== @@ -73,6 +87,8 @@ image before flashing it. It will be written in one of these locations: ![](images/t400/macaddress0.jpg) ![](images/t400/macaddress1.jpg) ![](images/x200/disassembly/0001.jpg) + + Initial BBB configuration ========================= @@ -111,26 +127,20 @@ for SOIC-8 (clip: Pomona 5250): The procedure ------------- -Remove all screws: - -![](images/t500/0000.jpg) - +Remove all screws:\ +![](images/t500/0000.jpg)\ It is also advisable to, throughout the disassembly, place any screws and/or components that you removed in the same layout or arrangement. -The follow photos demonstrate this: - +The follow photos demonstrate this:\ ![](images/t500/0001.jpg) ![](images/t500/0002.jpg) -Remove the HDD/SSD and optical drive: - +Remove the HDD/SSD and optical drive:\ ![](images/t500/0003.jpg) ![](images/t500/0004.jpg) -Remove the palm rest: - +Remove the palm rest:\ ![](images/t500/0005.jpg) ![](images/t500/0006.jpg) -Remove the keyboard and rear bezel: - +Remove the keyboard and rear bezel:\ ![](images/t500/0007.jpg) ![](images/t500/0008.jpg) ![](images/t500/0009.jpg) ![](images/t500/0010.jpg) ![](images/t500/0011.jpg) ![](images/t500/0012.jpg) @@ -138,109 +148,88 @@ Remove the keyboard and rear bezel: If you have a WWAN/3G card and/or sim card reader, remove them permanently. The WWAN-3G card has proprietary firmware inside; the technology is identical to what is used in mobile phones, so it can also -track your movements: - +track your movements:\ ![](images/t500/0013.jpg) ![](images/t500/0017.jpg) ![](images/t500/0018.jpg) -Remove this frame, and then remove the wifi chip: - +Remove this frame, and then remove the wifi chip:\ ![](images/t500/0014.jpg) ![](images/t500/0015.jpg) ![](images/t500/0016.jpg) -Remove the speakers: - +Remove the speakers:\ ![](images/t500/0019.jpg) ![](images/t500/0020.jpg) ![](images/t500/0021.jpg) ![](images/t500/0022.jpg) ![](images/t500/0023.jpg) ![](images/t500/0024.jpg) ![](images/t500/0025.jpg) -Remove the NVRAM battery (already removed in this photo): - +Remove the NVRAM battery (already removed in this photo):\ ![](images/t500/0026.jpg) When you re-assemble, you will be replacing the wifi chip with another. These two screws don't hold anything together, but they are included in your system because the screw holes for half-height cards are a different size, so use these if you will be installing a half-height -card: - +card:\ ![](images/t500/0027.jpg) -Unroute the antenna wires: - +Unroute the antenna wires:\ ![](images/t500/0028.jpg) ![](images/t500/0029.jpg) ![](images/t500/0030.jpg) ![](images/t500/0031.jpg) -Disconnect the LCD cable from the motherboard: - +Disconnect the LCD cable from the motherboard:\ ![](images/t500/0032.jpg) ![](images/t500/0033.jpg) -Remove the LCD assembly hinge screws, and then remove the LCD assembly: - +Remove the LCD assembly hinge screws, and then remove the LCD assembly:\ ![](images/t500/0034.jpg) ![](images/t500/0035.jpg) ![](images/t500/0036.jpg) -Remove the fan and heatsink: - +Remove the fan and heatsink:\ ![](images/t500/0037.jpg) ![](images/t500/0038.jpg) ![](images/t500/0039.jpg) -Remove this screw: - +Remove this screw:\ ![](images/t500/0040.jpg) Remove these cables, keeping note of how and in what arrangement they -are connected: - +are connected:\ ![](images/t500/0041.jpg) ![](images/t500/0042.jpg) ![](images/t500/0043.jpg) ![](images/t500/0044.jpg) ![](images/t500/0045.jpg) ![](images/t500/0046.jpg) ![](images/t500/0047.jpg) ![](images/t500/0048.jpg) ![](images/t500/0049.jpg) -Disconnect the power jack: - +Disconnect the power jack:\ ![](images/t500/0050.jpg) ![](images/t500/0051.jpg) Remove the motherboard and cage from the base (the marked hole is where -those cables were routed through): - +those cables were routed through):\ ![](images/t500/0052.jpg) ![](images/t500/0053.jpg) Remove all screws, arranging them in the same layout when placing the screws on a surface and marking each screw hole (this is to reduce the -possibility of putting them back in the wrong holes): - +possibility of putting them back in the wrong holes):\ ![](images/t500/0054.jpg) ![](images/t500/0055.jpg) -Also remove this: - +Also remove this:\ ![](images/t500/0056.jpg) ![](images/t500/0057.jpg) -Separate the motherboard from the cage: - +Separate the motherboard from the cage:\ ![](images/t500/0058.jpg) ![](images/t500/0059.jpg) The flash chip is next to the memory slots. On this system, it was a -SOIC-8 (4MiB or 32Mb) flash chip: - +SOIC-8 (4MiB or 32Mb) flash chip:\ ![](images/t500/0060.jpg) -Connect your programmer, then connect GND and 3.3V - -![](images/t500/0061.jpg) - +Connect your programmer, then connect GND and 3.3V\ +![](images/t500/0061.jpg)\ ![](images/t400/0067.jpg) ![](images/t400/0069.jpg) ![](images/t400/0070.jpg) ![](images/t400/0071.jpg) A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is -also fine: - +also fine:\ ![](images/t400/0072.jpg) -Of course, make sure to turn on your PSU: - +Of course, make sure to turn on your PSU:\ ![](images/x200/disassembly/0013.jpg) Now, you should be ready to install libreboot. @@ -250,11 +239,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). - -Test that flashrom works: +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). - # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) @@ -267,24 +255,18 @@ In this case, the output was: Please specify which chip definition to use with the -c <chipname> option. How to backup factory.rom (change the -c option as neeed, for your flash -chip): - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory1.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory2.rom** - +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +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: - - # sha512sum factory*.rom +have been removed.\ +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 is useful for reverse engineering work, if there is a desirable @@ -292,20 +274,19 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** -Now flash it: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +Now flash it:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V** ![](images/x200/disassembly/0015.jpg) -You might see errors, but if it says **Verifying flash... VERIFIED** at +You might see errors, but if it says **Verifying flash\... VERIFIED** at the end, then it's flashed and should boot. If you see errors, try again (and again, and again); the message **Chip content is identical to the requested image** is also an indication of a successful @@ -326,6 +307,8 @@ Example output from running the command (see above): [Back to top of page.](#pagetop) + + Thermal paste (IMPORTANT) ========================= @@ -343,13 +326,15 @@ NOTE: the photo above is for illustration purposes only, and does not show how to properly apply the thermal paste. Other guides online detail the proper application procedure. + + Wifi ==== The T500 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). Some T500 laptops might come with an Atheros chipset, but this is 802.11g only. @@ -360,10 +345,11 @@ whitelist of approved chips, and it will refuse to boot if you use an 'unauthorized' wifi card. The following photos show an Atheros AR5B95 being installed, to replace -the Intel chip that this T500 came with: - +the Intel chip that this T500 came with:\ ![](images/t400/0012.jpg) ![](images/t400/ar5b95.jpg) + + WWAN ==== @@ -374,6 +360,8 @@ also track your movements. Not to be confused with wifi (wifi is fine). + + Memory ====== @@ -387,10 +375,11 @@ Make sure that the RAM you buy is the 2Rx8 density. be useful for RAM compatibility info (note: coreboot raminit is different, so this page might be BS) -The following photo shows 8GiB (2x4GiB) of RAM installed: - +The following photo shows 8GiB (2x4GiB) of RAM installed:\ ![](images/t400/memory.jpg) + + Boot it! -------- @@ -400,8 +389,9 @@ You should see something like this: Now [install GNU+Linux](../gnulinux/). -Copyright © 2015 Leah Rowe <info@minifree.org> + +Copyright © 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/t60_unbrick.md b/docs/install/t60_unbrick.md @@ -1,10 +1,14 @@ -% ThinkPad T60: Recovery guide + +ThinkPad T60: Recovery guide +============================ This section documents how to recover from a bad flash that prevents your ThinkPad T60 from booting. [Back to previous index](./) + + Table of Contents ----------------- @@ -13,37 +17,36 @@ Table of Contents - [Brick type 2: bad rom (or user error), system won't boot](#recovery) + + Brick type 1: bucts not reset. {#bucts_brick} ============================== You still have Lenovo BIOS, or you had libreboot running and you flashed -another ROM; and you had bucts 1 set and the ROM wasn't dd'd.* or if -Lenovo BIOS was present and libreboot wasn't flashed. - +another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if +Lenovo BIOS was present and libreboot wasn't flashed.\ +\ In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or -two: - -![](../images/t60_dev/0006.JPG) - -*Those dd commands should be applied to all newly compiled T60 ROM +two:\ +![](../images/t60_dev/0006.JPG)\ +\ +\*Those dd commands should be applied to all newly compiled T60 ROM images (the ROM images in libreboot binary archives already have this -applied!): - +applied!):\ dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s -coreboot.rom) - 0x10000\] count=64k - +coreboot.rom) - 0x10000\] count=64k\ dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] -count=64k | hexdump - +count=64k | hexdump\ dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s -coreboot.rom) - 0x20000\] count=64k conv=notrunc - +coreboot.rom) - 0x20000\] count=64k conv=notrunc\ (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, using those instructions: <http://www.coreboot.org/Board:lenovo/x60/Installation>. (it says x60, but instructions for t60 are identical) + + bad rom (or user error), system won't boot {#recovery} =========================================== @@ -58,80 +61,62 @@ you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides). -Remove those screws and remove the HDD: - +Remove those screws and remove the HDD:\ ![](../images/t60_dev/0001.JPG) ![](../images/t60_dev/0002.JPG) -Lift off the palm rest: - +Lift off the palm rest:\ ![](../images/t60_dev/0003.JPG) Lift up the keyboard, pull it back a bit, flip it over like that and -then disconnect it from the board: - +then disconnect it from the board:\ ![](../images/t60_dev/0004.JPG) ![](../images/t60_dev/0005.JPG) ![](../images/t60_dev/0006.JPG) -Gently wedge both sides loose: - +Gently wedge both sides loose:\ ![](../images/t60_dev/0007.JPG) ![](../images/t60_dev/0008.JPG) -Remove that cable from the position: - +Remove that cable from the position:\ ![](../images/t60_dev/0009.JPG) ![](../images/t60_dev/0010.JPG) Now remove that bezel. Remove wifi, nvram battery and speaker connector -(also remove 56k modem, on the left of wifi): - +(also remove 56k modem, on the left of wifi):\ ![](../images/t60_dev/0011.JPG) -Remove those screws: - +Remove those screws:\ ![](../images/t60_dev/0012.JPG) -Disconnect the power jack: - +Disconnect the power jack:\ ![](../images/t60_dev/0013.JPG) -Remove nvram battery: - +Remove nvram battery:\ ![](../images/t60_dev/0014.JPG) -Disconnect cable (for 56k modem) and disconnect the other cable: - +Disconnect cable (for 56k modem) and disconnect the other cable:\ ![](../images/t60_dev/0015.JPG) ![](../images/t60_dev/0016.JPG) -Disconnect speaker cable: - +Disconnect speaker cable:\ ![](../images/t60_dev/0017.JPG) -Disconnect the other end of the 56k modem cable: - +Disconnect the other end of the 56k modem cable:\ ![](../images/t60_dev/0018.JPG) -Make sure you removed it: - +Make sure you removed it:\ ![](../images/t60_dev/0019.JPG) -Unscrew those: - +Unscrew those:\ ![](../images/t60_dev/0020.JPG) -Make sure you removed those: - +Make sure you removed those:\ ![](../images/t60_dev/0021.JPG) -Disconnect LCD cable from board: - +Disconnect LCD cable from board:\ ![](../images/t60_dev/0022.JPG) -Remove those screws then remove the LCD assembly: - +Remove those screws then remove the LCD assembly:\ ![](../images/t60_dev/0023.JPG) ![](../images/t60_dev/0024.JPG) ![](../images/t60_dev/0025.JPG) -Once again, make sure you removed those: - +Once again, make sure you removed those:\ ![](../images/t60_dev/0026.JPG) Remove the shielding containing the motherboard, then flip it over. @@ -139,25 +124,20 @@ Remove these screws, placing them on a steady surface in the same layout as they were in before you removed them. Also, you should mark each screw hole after removing the screw (a permanent marker pen will do), this is so that you have a point of reference when re-assembling the -system: - +system:\ ![](../images/t60_dev/0027.JPG) ![](../images/t60_dev/0028.JPG) ![](../images/t60_dev/0029.JPG) ![](../images/t60_dev/0031.JPG) ![](../images/t60_dev/0032.JPG) ![](../images/t60_dev/0033.JPG) -Now wire up the BBB and the Pomona with your PSU. - +Now wire up the BBB and the Pomona with your PSU.\ Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for -flashing. - +flashing.\ **Note, the guide mentions a 3.3v DC PSU but you don't need this on the T60: if you don't have or don't want to use an external PSU, then make sure not to connect the 3.3v leads mentioned in the guide; instead, connect the AC adapter (the one that normally charges your battery) so -that the board has power (but don't boot it up)** - -![](../images/t60_dev/0030.JPG) - +that the board has power (but don't boot it up)**\ +![](../images/t60_dev/0030.JPG)\ Correlate the following with the BBB guide linked above: POMONA 5250: @@ -176,76 +156,64 @@ Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. -SSH'd into the BBB: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +SSH'd into the BBB:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom** -It should be **Verifying flash... VERIFIED** at the end. If flashrom +It should be **Verifying flash\... VERIFIED** at the end. If flashrom complains about multiple flash chip definitions detected, then choose one of them following the instructions in the output. -Put those screws back: - +Put those screws back:\ ![](../images/t60_dev/0047.JPG) -Put it back into lower chassis: - +Put it back into lower chassis:\ ![](../images/t60_dev/0048.JPG) -Attach LCD and insert screws (also, attach the lcd cable to the board): - +Attach LCD and insert screws (also, attach the lcd cable to the board):\ ![](../images/t60_dev/0049.JPG) -Insert those screws: - +Insert those screws:\ ![](../images/t60_dev/0050.JPG) On the CPU (and there is another chip south-east to it, sorry forgot to take pic) clean off the old thermal paste (with the alcohol) and apply new (Artic Silver 5 is good, others are good too) you should also clean -the heatsink the same way - +the heatsink the same way\ ![](../images/t60_dev/0051.JPG) Attach the heatsink and install the screws (also, make sure to install -the AC jack as highlighted): - +the AC jack as highlighted):\ ![](../images/t60_dev/0052.JPG) -Reinstall that upper bezel: - +Reinstall that upper bezel:\ ![](../images/t60_dev/0053.JPG) -Do that: - +Do that:\ ![](../images/t60_dev/0054.JPG) ![](../images/t60_dev/0055.JPG) Re-attach modem, wifi, (wwan?), and all necessary cables. Sorry, forgot to take pics. Look at previous removal steps to see where they go back to. -Attach keyboard and install nvram battery: - +Attach keyboard and install nvram battery:\ ![](../images/t60_dev/0056.JPG) ![](../images/t60_dev/0057.JPG) Place keyboard and (sorry, forgot to take pics) reinstall the palmrest -and insert screws on the underside: - +and insert screws on the underside:\ ![](../images/t60_dev/0058.JPG) -It lives! - +It lives!\ ![](../images/t60_dev/0071.JPG) ![](../images/t60_dev/0072.JPG) ![](../images/t60_dev/0073.JPG) Always stress test ('stress -c 2' and xsensors. below 90C is ok) when -replacing cpu paste/heatsink: - +replacing cpu paste/heatsink:\ ![](../images/t60_dev/0074.JPG) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md @@ -1,4 +1,6 @@ -% Flashing the X200 with a BeagleBone Black + +Flashing the X200 with a BeagleBone Black +========================================= Initial flashing instructions for X200. @@ -16,6 +18,9 @@ followed (adapted) if you brick your X200, to know how to recover. - [Memory](#memory) - [X200S and X200 Tablet users: GPIO33 trick will not work.](#gpio33) + + + X200 laptops with libreboot pre-installed {#preinstall} ========================================= @@ -25,20 +30,23 @@ GNU+Linux distribution. Check the [suppliers](../../suppliers) page for more information. + + Flash chip size {#flashchips} =============== -Use this to find out: - -# **flashrom -p internal -V** +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 -[../hcl/x200.html#x200s](../hcl/x200.html#x200s).** +[../hcl/x200.html\#x200s](../hcl/x200.html#x200s).** [Back to top of page.](#pagetop) + + MAC address {#macaddress} =========== @@ -53,6 +61,8 @@ image before flashing it. It will be written in one of these locations: ![](images/x200/disassembly/0002.jpg) ![](images/x200/disassembly/0001.jpg) + + Initial BBB configuration {#clip} ========================= @@ -91,21 +101,20 @@ header), for SOIC-8 (clip: Pomona 5250): This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. Here is a photo of the SOIC-8 flash chip. The pins are labelled: + + Look at the pads in that photo, on the left and right. Those are for SOIC-16. Would it be possible to remove the SOIC-8 and solder a SOIC-16 chip on those pins? **On the X200S and X200 Tablet the flash chip is underneath the board, in a WSON package. The pinout is very much the same as a SOIC-8, except -you need to solder (there are no clips available). - -The following image shows how this is done:** - -![](images/x200/wson_soldered.jpg "Copyright 2014 Steve Shenton <sgsit@libreboot.org> see license notice at the end of this document") - +you need to solder (there are no clips available).\ +The following image shows how this is done:**\ +![](images/x200/wson_soldered.jpg "Copyright 2014 Steve Shenton <sgsit@libreboot.org> see license notice at the end of this document")\ In this image, a pin header was soldered onto the WSON. Another solution might be to de-solder the WSON-8 chip and put a SOIC-8 there instead. Check the list of SOIC-8 flash chips at -[../hcl/gm45\_remove\_me.html#flashchips](../hcl/gm45_remove_me.html#flashchips) +[../hcl/gm45\_remove\_me.html\#flashchips](../hcl/gm45_remove_me.html#flashchips) but do note that these are only 4MiB (32Mb) chips. The only X200 SPI chips with 8MiB capacity are SOIC-16. For 8MiB capacity in this case, the X201 SOIC-8 flash chip (Macronix 25L6445E) might work. @@ -117,47 +126,39 @@ This section is for the X200. This does not apply to the X200S or X200 Tablet (for those systems, you have to remove the motherboard completely, since the flash chip is on the other side of the board). -Remove these screws: - +Remove these screws:\ ![](images/x200/disassembly/0003.jpg) Push the keyboard forward, gently, then lift it off and disconnect it -from the board: - +from the board:\ ![](images/x200/disassembly/0004.jpg) ![](images/x200/disassembly/0005.jpg) Pull the palm rest off, lifting from the left and right side at the back -of the palm rest: - +of the palm rest:\ ![](images/x200/disassembly/0006.jpg) Lift back the tape that covers a part of the flash chip, and then -connect the clip: - +connect the clip:\ ![](images/x200/disassembly/0007.jpg) ![](images/x200/disassembly/0008.jpg) On pin 2 of the BBB, where you have the ground (GND), connect the ground -to your PSU: - +to your PSU:\ ![](images/x200/disassembly/0009.jpg) ![](images/x200/disassembly/0010.jpg) -Connect the 3.3V supply from your PSU to the flash chip (via the clip): - +Connect the 3.3V supply from your PSU to the flash chip (via the clip):\ ![](images/x200/disassembly/0011.jpg) ![](images/x200/disassembly/0012.jpg) -Of course, make sure that your PSU is also plugged in and turn on: - +Of course, make sure that your PSU is also plugged in and turn on:\ ![](images/x200/disassembly/0013.jpg) This tutorial tells you to use an ATX PSU, for the 3.3V DC supply. The PSU used when taking these photos is actually not an ATX PSU, but a PSU that is designed specifically for providing 3.3V DC (an ATX PSU will -also work): - +also work):\ ![](images/x200/disassembly/0014.jpg) Now, you should be ready to install libreboot. @@ -167,11 +168,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). - -Test that flashrom works: +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). - # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) @@ -184,24 +184,18 @@ In this case, the output was: Please specify which chip definition to use with the -c <chipname> option. How to backup factory.rom (change the -c option as neeed, for your flash -chip): - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory1.rom** - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r -factory2.rom** - +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +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: - - # sha512sum factory*.rom +have been removed.\ +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 is useful for reverse engineering work, if there is a desirable @@ -209,20 +203,19 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** -Now flash it: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +Now flash it:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V** ![](images/x200/disassembly/0015.jpg) -You might see errors, but if it says **Verifying flash... VERIFIED** at +You might see errors, but if it says **Verifying flash\... VERIFIED** at the end, then it's flashed and should boot. If you see errors, try again (and again, and again); the message **Chip content is identical to the requested image** is also an indication of a successful @@ -243,13 +236,15 @@ Example output from running the command (see above): [Back to top of page.](#pagetop) + + Wifi ==== The X200 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). Some X200 laptops come with an Atheros chipset, but this is 802.11g only. @@ -260,11 +255,12 @@ whitelist of approved chips, and it will refuse to boot if you use an 'unauthorized' wifi card. The following photos show an Atheros AR5B95 being installed, to replace -the Intel chip that this X200 came with: - +the Intel chip that this X200 came with:\ ![](images/x200/disassembly/0016.jpg) ![](images/x200/disassembly/0017.jpg) + + WWAN ==== @@ -275,6 +271,8 @@ track your movements. Not to be confused with wifi (wifi is fine). + + Memory ====== @@ -287,10 +285,11 @@ work in some cases. Make sure that the RAM you buy is the 2Rx8 density. -In this photo, 8GiB of RAM (2x4GiB) is installed: - +In this photo, 8GiB of RAM (2x4GiB) is installed:\ ![](images/x200/disassembly/0018.jpg) + + Boot it! {#boot} -------- @@ -300,6 +299,8 @@ You should see something like this: Now [install GNU+Linux](../gnulinux/). + + X200S and X200 Tablet users: GPIO33 trick will not work. {#gpio33} -------------------------------------------------------- @@ -308,8 +309,7 @@ disable the flashing protections by the descriptor and stop the ME from starting (which itself interferes with flashing attempts). The theory was proven correct; however, it is still useless in practise. -Look just above the 7 in TP37 (that's GPIO33): - +Look just above the 7 in TP37 (that's GPIO33):\ ![](../hcl/images/x200/gpio33_location.jpg) By default we would see this in lenovobios, when trying flashrom -p @@ -340,10 +340,11 @@ here: On a related note, libreboot has a utility that could help with investigating this: -[../hcl/gm45\_remove\_me.html#demefactory](../hcl/gm45_remove_me.html#demefactory) +[../hcl/gm45\_remove\_me.html\#demefactory](../hcl/gm45_remove_me.html#demefactory) + -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md @@ -1,10 +1,14 @@ -% ThinkPad X60: Recovery guide + +ThinkPad X60: Recovery guide +============================ This section documents how to recover from a bad flash that prevents your ThinkPad X60 from booting. [Back to previous index](./) + + Table of Contents ================= @@ -13,36 +17,35 @@ Table of Contents - [Brick type 2: bad rom (or user error), system won't boot](#recovery) + + Brick type 1: bucts not reset. {#bucts_brick} ============================== You still have Lenovo BIOS, or you had libreboot running and you flashed -another ROM; and you had bucts 1 set and the ROM wasn't dd'd.* or if -Lenovo BIOS was present and libreboot wasn't flashed. - +another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if +Lenovo BIOS was present and libreboot wasn't flashed.\ +\ In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or -two: - -![](../images/x60_unbrick/0004.jpg) - -*Those dd commands should be applied to all newly compiled X60 ROM +two:\ +![](../images/x60_unbrick/0004.jpg)\ +\ +\*Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this -applied!): - +applied!):\ dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s -coreboot.rom) - 0x10000\] count=64k - +coreboot.rom) - 0x10000\] count=64k\ dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] -count=64k | hexdump - +count=64k | hexdump\ dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s -coreboot.rom) - 0x20000\] count=64k conv=notrunc - +coreboot.rom) - 0x20000\] count=64k conv=notrunc\ (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, using those instructions: <http://www.coreboot.org/Board:lenovo/x60/Installation>. + + bad rom (or user error), system won't boot {#recovery} =========================================== @@ -57,86 +60,68 @@ you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides). -Remove those screws: - +Remove those screws:\ ![](../images/x60_unbrick/0000.jpg) -Push the keyboard forward (carefully): - +Push the keyboard forward (carefully):\ ![](../images/x60_unbrick/0001.jpg) -Lift the keyboard up and disconnect it from the board: - +Lift the keyboard up and disconnect it from the board:\ ![](../images/x60_unbrick/0002.jpg) Grab the right-hand side of the chassis and force it off (gently) and -pry up the rest of the chassis: - +pry up the rest of the chassis:\ ![](../images/x60_unbrick/0003.jpg) -You should now have this: - +You should now have this:\ ![](../images/x60_unbrick/0004.jpg) -Disconnect the wifi antenna cables, the modem cable and the speaker: - +Disconnect the wifi antenna cables, the modem cable and the speaker:\ ![](../images/x60_unbrick/0005.jpg) Unroute the cables along their path, carefully lifting the tape that holds them in place. Then, disconnect the modem cable (other end) and power connection and unroute all the cables so that they dangle by the -monitor hinge on the right-hand side: - +monitor hinge on the right-hand side:\ ![](../images/x60_unbrick/0006.jpg) Disconnect the monitor from the motherboard, and unroute the grey -antenna cable, carefully lifting the tape that holds it into place: - +antenna cable, carefully lifting the tape that holds it into place:\ ![](../images/x60_unbrick/0008.jpg) Carefully lift the remaining tape and unroute the left antenna cable so -that it is loose: - +that it is loose:\ ![](../images/x60_unbrick/0009.jpg) Remove the screw that is highlighted (do NOT remove the other one; it -holds part of the heatsink (other side) into place): - +holds part of the heatsink (other side) into place):\ ![](../images/x60_unbrick/0011.jpg) -Remove those screws: - +Remove those screws:\ ![](../images/x60_unbrick/0012.jpg) -Carefully remove the plate, like so: - +Carefully remove the plate, like so:\ ![](../images/x60_unbrick/0013.jpg) -Remove the SATA connector: - +Remove the SATA connector:\ ![](../images/x60_unbrick/0014.jpg) -Now remove the motherboard (gently) and cast the lcd/chassis aside: - +Now remove the motherboard (gently) and cast the lcd/chassis aside:\ ![](../images/x60_unbrick/0015.jpg) Lift back that tape and hold it with something. Highlighted is the SPI -flash chip: - +flash chip:\ ![](../images/x60_unbrick/0016.jpg) -Now wire up the BBB and the Pomona with your PSU. - +Now wire up the BBB and the Pomona with your PSU.\ Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for -flashing. - +flashing.\ **Note, the guide mentions a 3.3v DC PSU but you don't need this on the X60: if you don't have or don't want to use an external PSU, then make sure not to connect the 3.3v leads mentioned in the guide; instead, connect the AC adapter (the one that normally charges your battery) so that the board has power (but don't boot it up)** -![](../images/x60_unbrick/0017.jpg) - +![](../images/x60_unbrick/0017.jpg)\ Correlate the following with the BBB guide linked above: POMONA 5250: @@ -149,122 +134,98 @@ Correlate the following with the BBB guide linked above: This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. Connecting the BBB and pomona (in this image, an external 3.3v DC PSU -was used): - +was used):\ ![](images/x60/th_bbb_flashing.jpg) Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. -SSH'd into the BBB: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +SSH'd into the BBB:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom** -It should be **Verifying flash... VERIFIED** at the end. If flashrom +It should be **Verifying flash\... VERIFIED** at the end. If flashrom complains about multiple flash chip definitions detected, then choose one of them following the instructions in the output. Remove the programmer and put it away somewhere. Put back the tape and -press firmly over it: - +press firmly over it:\ ![](../images/x60_unbrick/0026.jpg) -Your empty chassis: - +Your empty chassis:\ ![](../images/x60_unbrick/0027.jpg) -Put the motherboard back in: - +Put the motherboard back in:\ ![](../images/x60_unbrick/0028.jpg) -Reconnect SATA: - +Reconnect SATA:\ ![](../images/x60_unbrick/0029.jpg) -Put the plate back and re-insert those screws: - +Put the plate back and re-insert those screws:\ ![](../images/x60_unbrick/0030.jpg) -Re-route that antenna cable around the fan and apply the tape: - +Re-route that antenna cable around the fan and apply the tape:\ ![](../images/x60_unbrick/0031.jpg) Route the cable here and then (not shown, due to error on my part) reconnect the monitor cable to the motherboard and re-insert the -screws: - +screws:\ ![](../images/x60_unbrick/0032.jpg) -Re-insert that screw: - +Re-insert that screw:\ ![](../images/x60_unbrick/0033.jpg) -Route the black antenna cable like so: - +Route the black antenna cable like so:\ ![](../images/x60_unbrick/0034.jpg) -Tuck it in neatly like so: - +Tuck it in neatly like so:\ ![](../images/x60_unbrick/0035.jpg) -Route the modem cable like so: - +Route the modem cable like so:\ ![](../images/x60_unbrick/0036.jpg) -Connect modem cable to board and tuck it in neatly like so: - +Connect modem cable to board and tuck it in neatly like so:\ ![](../images/x60_unbrick/0037.jpg) -Route the power connection and connect it to the board like so: - +Route the power connection and connect it to the board like so:\ ![](../images/x60_unbrick/0038.jpg) -Route the antenna and modem cables neatly like so: - +Route the antenna and modem cables neatly like so:\ ![](../images/x60_unbrick/0039.jpg) Connect the wifi antenna cables. At the start of the tutorial, this system had an Intel wifi chip. Here you see I've replaced it with an -Atheros AR5B95 (supports 802.11n and can be used without blobs): - +Atheros AR5B95 (supports 802.11n and can be used without blobs):\ ![](../images/x60_unbrick/0040.jpg) -Connect the modem cable: - +Connect the modem cable:\ ![](../images/x60_unbrick/0041.jpg) -Connect the speaker: - +Connect the speaker:\ ![](../images/x60_unbrick/0042.jpg) -You should now have this: - +You should now have this:\ ![](../images/x60_unbrick/0043.jpg) -Re-connect the upper chassis: - +Re-connect the upper chassis:\ ![](../images/x60_unbrick/0044.jpg) -Re-connect the keyboard: - +Re-connect the keyboard:\ ![](../images/x60_unbrick/0045.jpg) -Re-insert the screws that you removed earlier: - +Re-insert the screws that you removed earlier:\ ![](../images/x60_unbrick/0046.jpg) -Power on! - +Power on!\ ![](../images/x60_unbrick/0047.jpg) -Operating system: - +Operating system:\ ![](../images/x60_unbrick/0049.jpg) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md @@ -1,10 +1,14 @@ -% ThinkPad X60 Tablet: Recovery guide + +ThinkPad X60 Tablet: Recovery guide +=================================== This section documents how to recover from a bad flash that prevents your ThinkPad X60 Tablet from booting. [Back to previous index](./) + + Table of Contents ----------------- @@ -13,36 +17,35 @@ Table of Contents - [Brick type 2: bad rom (or user error), system won't boot](#recovery) + + Brick type 1: bucts not reset. {#bucts_brick} ============================== You still have Lenovo BIOS, or you had libreboot running and you flashed -another ROM; and you had bucts 1 set and the ROM wasn't dd'd.* or if -Lenovo BIOS was present and libreboot wasn't flashed. - +another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if +Lenovo BIOS was present and libreboot wasn't flashed.\ +\ In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or -two: - -![](../images/x60t_unbrick/0008.JPG) - -*Those dd commands should be applied to all newly compiled X60 ROM +two:\ +![](../images/x60t_unbrick/0008.JPG)\ +\ +\*Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this -applied!): - +applied!):\ dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s -coreboot.rom) - 0x10000\] count=64k - +coreboot.rom) - 0x10000\] count=64k\ dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] -count=64k | hexdump - +count=64k | hexdump\ dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s -coreboot.rom) - 0x20000\] count=64k conv=notrunc - +coreboot.rom) - 0x20000\] count=64k conv=notrunc\ (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, using those instructions: <http://www.coreboot.org/Board:lenovo/x60/Installation>. + + bad rom (or user error), system won't boot {#recovery} =========================================== @@ -59,57 +62,45 @@ flash the SPI chip (where libreboot resides). ![](../images/x60t_unbrick/0000.JPG) -Remove those screws: - +Remove those screws:\ ![](../images/x60t_unbrick/0001.JPG) -Remove the HDD: - +Remove the HDD:\ ![](../images/x60t_unbrick/0002.JPG) -Push keyboard forward to loosen it: - +Push keyboard forward to loosen it:\ ![](../images/x60t_unbrick/0003.JPG) -Lift: - +Lift:\ ![](../images/x60t_unbrick/0004.JPG) -Remove those: - +Remove those:\ ![](../images/x60t_unbrick/0005.JPG) ![](../images/x60t_unbrick/0006.JPG) -Also remove that (marked) and unroute the antenna cables: - +Also remove that (marked) and unroute the antenna cables:\ ![](../images/x60t_unbrick/0007.JPG) -For some X60T laptops, you have to unroute those too: - +For some X60T laptops, you have to unroute those too:\ ![](../images/x60t_unbrick/0010.JPG) Remove the LCD extend board screws. Also remove those screws (see blue -marks) and remove/unroute the cables and remove the metal plate: - +marks) and remove/unroute the cables and remove the metal plate:\ ![](../images/x60t_unbrick/0008.JPG) -Remove that screw and then remove the board: - +Remove that screw and then remove the board:\ ![](../images/x60t_unbrick/0009.JPG) -Now wire up the BBB and the Pomona with your PSU. - +Now wire up the BBB and the Pomona with your PSU.\ Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for -flashing. - +flashing.\ **Note, the guide mentions a 3.3v DC PSU but you don't need this on the X60 Tablet: if you don't have or don't want to use an external PSU, then make sure not to connect the 3.3v leads mentioned in the guide; instead, connect the AC adapter (the one that normally charges your battery) so that the board has power (but don't boot it up)** -![](../images/x60t_unbrick/0011.JPG) - +![](../images/x60t_unbrick/0011.JPG)\ Correlate the following with the BBB guide linked above: POMONA 5250: @@ -122,27 +113,26 @@ Correlate the following with the BBB guide linked above: This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. Connecting the BBB and pomona (in this image, an external 3.3v DC PSU -was used): - +was used):\ ![](images/x60/th_bbb_flashing.jpg) Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. -SSH'd into the BBB: - -# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +SSH'd into the BBB:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom** -It should be **Verifying flash... VERIFIED** at the end. If flashrom +It should be **Verifying flash\... VERIFIED** at the end. If flashrom complains about multiple flash chip definitions detected, then choose one of them following the instructions in the output. Reverse the steps to re-assemble your system. -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/misc/bbb_ehci.md b/docs/misc/bbb_ehci.md @@ -1,7 +1,11 @@ -% EHCI debugging on the BeagleBone Black + +EHCI debugging on the BeagleBone Black +====================================== [Back to previous index](./) + + EHCI debugging ============== @@ -99,7 +103,7 @@ section): ls /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget/g_dbgp.ko -Unload all other g\_* modules: +Unload all other g\_\* modules: # lsmod # rmmod g_multi @@ -122,8 +126,7 @@ next step. ### Patch BBB's g\_dbgp module (optional, but highly recommended) {#PatchBBBsgdbgpmoduleoptionalbuthighlyrecommended} For the reasons why you need this, see: [EHCI Gadget -Debug](http://www.coreboot.org/EHCI_Gadget_Debug). - +Debug](http://www.coreboot.org/EHCI_Gadget_Debug).\ Make sure that you have cross compiling environment for arm-linux-gnueabihf setup on your *host*. @@ -134,10 +137,10 @@ arm-linux-gnueabihf setup on your *host*. <!-- --> - $ cd \$work_dir + $ cd $work_dir $ git clone https://github.com/beagleboard/kernel.git $ cd kernel - $ git checkout \$mav (see above) + $ git checkout $mav (see above) $ ./patch.sh $ wget http://arago-project.org/git/projects/?p=am33x-cm3.git\;a=blob_plain\;f=bin/am335x-pm-firmware.bin\;hb=HEAD -O kernel/firmware/am335x-pm-firmware.bin $ cp configs/beaglebone kernel/arch/arm/configs/beaglebone_defconfig @@ -150,7 +153,7 @@ arm-linux-gnueabihf setup on your *host*. the two different version of the kernel (3.8 and 3.10). I will use 3.8. (If using kernel 3.12 patch\_1 is not needed) - cd kernel (note that this is one more level: you should be in - $work\_dir/kernel/kernel) + \$work\_dir/kernel/kernel) - Apply the patches: <!-- --> @@ -185,18 +188,17 @@ arm-linux-gnueabihf setup on your *host*. - on BBB, backup /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget (i.e. mv /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget - $HOME) + \$HOME) - copy the freshly compiled usb/gadget dir to /lib/modules/3.8.13-bone70/kernel/drivers/usb - restart BBB -- Remove all g\_* modules (rmmod g\_<>) +- Remove all g\_\* modules (rmmod g\_<>) - modprobpe g\_dbgp ### Configure libreboot with EHCI debug {#ConfigurelibrebootwithEHCIdebug} Libreboot(coreboot) should be configured with debug turned on and to -push debug messages to the EHCI debug port. - +push debug messages to the EHCI debug port.\ If you've downloaded the binary distribution, you can check if it is properly configured in the following way: @@ -207,7 +209,7 @@ properly configured in the following way: <!-- --> - ./cbfstool/i686/cbfstool \$img_path extract -n config -f ./my_config + ./cbfstool/i686/cbfstool $img_path extract -n config -f ./my_config - Make sure that the following params in the config are set as following: @@ -232,7 +234,7 @@ documented [here](https://johnlewis.ie/coreboot-ehci-debug-gadget-demonstration/) (also tested/verified). -Then: +Then:\ CONFIG_CONSOLE_USB=y (Console -> USB dongle console output) @@ -253,8 +255,7 @@ refer to the doc(**FIXME: link** about compiling libreboot. #### Selecting HCD Index and USB Debug port {#SelectingHCDIndexandUSBDebugport} This applies (and works) only if the USB controller that supports debug -(found in the first section) is from Intel. - +(found in the first section) is from Intel.\ If the PCI ID of the port you found in the first section is 0000:00:1a.0 or 0000:00:1d.0 , you are ok. Otherwise you have to try without guarantee that will work. @@ -265,12 +266,10 @@ then for CONFIG\_USBDEBUG\_HCD\_INDEX choose 2, otherwise choose 0 . For CONFIG\_USBDEBUG\_DEFAULT\_PORT choose the port from the first section that correspond to the PCI ID -Notes: - +Notes:\ The above is based on the implementation of coreboot/src/southbridge/intel/common/usb\_debug.c : -pci\_ehci\_dbg\_dev() . - +pci\_ehci\_dbg\_dev() .\ This is enough as it applies for the supported GM45/G45 Thinkpads. coreboot support some other contollers too, but they are irellevent for libreboot (for now). @@ -283,7 +282,7 @@ libreboot (for now). - Plug the USB cable in the target's debug port (the one you found in step 1) and BBB's mini-B USB -- Make sure no other then g\_dbgp of the g\_* modules is loaded on +- Make sure no other then g\_dbgp of the g\_\* modules is loaded on your BBB - On the BBB: @@ -296,7 +295,7 @@ libreboot (for now). - You should see debug logs comming on your BBB console Note that this is not permanent on BBB, if you reboot it, you have to -rmmod g\_* and modprobe g\_dbgp +rmmod g\_\* and modprobe g\_dbgp ### Eneble EHCI Debug on the target's kernel (optional, recommended) {#EnebleEHCIDebugonthetargetskerneloptionalrecommended} @@ -355,8 +354,9 @@ Interface](http://cs.usfca.edu/~cruse/cs698s10/) 3. Patch and compule g\_dbgp on BBB instead cross-compile 4. Find a simple way to send debug messages from targets userland -Copyright © 2015 Alex David <opdecirkel@gmail.com> + +Copyright © 2015 Alex David <opdecirkel@gmail.com>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/misc/index.md b/docs/misc/index.md @@ -1,4 +1,7 @@ -% Miscellaneous + +Miscellaneous +============= + - [High Pitched Whining Noise on Idle (how to remove in Debian or Devuan)](#debian_powertop) @@ -14,9 +17,12 @@ Black](bbb_ehci.html) - [e1000e driver trouble shooting (Intel NICs)](#e1000-hang) + + High Pitched Whining Noise on Idle (how to remove in Debian or Devuan) {#debian_powertop} ====================================================================== + Start powertop automatically at boot time {#debian_powertop_autostart} ----------------------------------------- @@ -32,6 +38,11 @@ If powertop doesn't work, another way (reduces battery life slightly) is to add *processor.max\_cstate=2* to the *linux* line in grub.cfg, using [this guide](../gnulinux/grub_cbfs.html). + +[Back to top of page](#pagetop) + + + High Pitched Whining Noise on Idle (how to remove in Parabola) {#high_pitch_parabola} ============================================================== @@ -48,13 +59,11 @@ 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 -** - $ su - - -Installed powertop: - - # pacman -S powertop +Installed powertop:\ +**\# pacman -S powertop** and added the following to /etc/systemd/system/powertop.service : @@ -71,10 +80,9 @@ and added the following to /etc/systemd/system/powertop.service : [Install] WantedBy=multi-user.target -Finally, as root do that: - - # systemctl enable powertop - # systemctl start powertop +Finally, as root do that:\ +**\# systemctl enable powertop**\ +**\# systemctl start powertop** The next time you boot the system, the buzz will be gone. @@ -84,6 +92,10 @@ If powertop doesn't work, another way (reduces battery life slightly) is to add *processor.max\_cstate=2* to the *linux* line in grub.cfg, using [this guide](../gnulinux/grub_cbfs.html). +[Back to top of page](#pagetop) + + + X60/T60: Serial port - how to use (for dock owners) {#serial} =================================================== @@ -97,9 +109,8 @@ included inside the ROM. Connect your null modem cable to the serial port on the dock and connect the other end to a 2nd system using your USB Serial adapter. -On the 2nd system, you can try this (using GNU Screen): - - $ sudo screen /dev/ttyUSB0 115200 +On the 2nd system, you can try this (using GNU Screen):\ +**\$ sudo screen /dev/ttyUSB0 115200** How to quit GNU Screen: Ctrl+A then release and press K, and then press Y. @@ -113,8 +124,7 @@ can also configure your distro so that a terminal (TTY) is accessible from the serial console. The following guide is for Ubuntu, but it should work in Debian and -Devuan, to enable a serial console using GeTTY: - +Devuan, to enable a serial console using GeTTY:\ <https://help.ubuntu.com/community/SerialConsoleHowto> (we DO NOT recommend Ubuntu, because it contains non-free software in the default repos. Use Debian or Devuan) @@ -123,6 +133,10 @@ Note: part of the tutorial above requires changing your grub.cfg. Just change the **linux** line to add instructions for enabling getty. See [../gnulinux/grub\_cbfs.html](../gnulinux/grub_cbfs.html). +[Back to top of page](#pagetop) + + + Finetune backlight control on intel gpu's ========================================= @@ -197,7 +211,7 @@ duty cycle. see <https://review.coreboot.org/#/c/10624/> on bit 16. The cause of this issue is that i945, in contrast with to GM45, is set to work in BLM Legacy Mode. This makes backlight more complicated since the duty cycle is derived from 3 instead of 2 registers using the following -formula: if(BPC\[7:0\] <> xFF) then BPCR\[15:0\] * BPC\[7:0\] +formula: if(BPC\[7:0\] <> xFF) then BPCR\[15:0\] \* BPC\[7:0\] Else BPCR\[15:0\] BPC is LBB - PCI Backlight Control Register, described on <http://www.mouser.com/pdfdocs/945gmedatasheet.pdf> on page 315. BPCR is BLC\_PWM\_CTL described in @@ -205,6 +219,8 @@ is BLC\_PWM\_CTL described in on page 94. More research needs to be done on this target so proceed with care. + + Power Management Beeps on Thinkpads =================================== @@ -213,32 +229,30 @@ battery goes to a critically low charge level, a beep occurs. Nvramtool is included in libreboot, and can be used to enable or disable this behaviour. -Disable or enable beeps when removing/adding the charger: - - $ sudo ./nvramtool -w power\_management\_beeps=Enable +Disable or enable beeps when removing/adding the charger:\ +\$ **sudo ./nvramtool -w power\_management\_beeps=Enable**\ \$ **sudo ./nvramtool -w power\_management\_beeps=Disable** -Disable or enable beeps when battery is low: - - $ sudo ./nvramtool -w low\_battery\_beep=Enable +Disable or enable beeps when battery is low:\ +\$ **sudo ./nvramtool -w low\_battery\_beep=Enable**\ \$ **sudo ./nvramtool -w low\_battery\_beep=Disable** A reboot is required, for these changes to take effect. + + Get EDID: Find out the name (model) of your LCD panel {#get_edid_panelname} ===================================================== -Get the panel name with sudo get-edid | strings +Get the panel name with **sudo get-edid | strings**\ Or look in **/sys/class/drm/card0-LVDS-1/edid** Alternatively you can use i2cdump. In Debian and Devuan, this is in the -package i2c-tools. - - $ sudo modprobe i2c-dev +package i2c-tools.\ +\$ **sudo modprobe i2c-dev**\ \$ **sudo i2cdump -y 5 0x50** (you might have to change the value for --y) - - $ sudo rmmod i2c-dev +-y)\ +\$ **sudo rmmod i2c-dev**\ You'll see the panel name in the output (from the EDID dump). If neither of these options work (or they are unavailable), physically @@ -247,6 +261,8 @@ printed on the back. [Back to top of page.](#pagetop) + + e1000e driver trouble shooting (Intel NICs) {#e1000-hang} =========================================== @@ -255,16 +271,14 @@ needed for cause): e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang -Possible workaround, tested by Nazara: Disable C-STATES. - +Possible workaround, tested by Nazara: Disable C-STATES.\ **NOTE: this also disables power management, because disabling C-States means that your CPU will now be running at full capacity (and therefore using more power) non-stop, which will drain battery life if this is a laptop. If power usage is a concern, then you should not use this. (we're also not sure whether this workaround is appropriate)** -To disable c-states, do this in GNU+Linux: - +To disable c-states, do this in GNU+Linux:\ **for i in /sys/devices/system/cpu/cpu/cpuidle/state/disable; do echo 1 > \$i; done** @@ -274,6 +288,8 @@ across subnets on the same interface (NIC). More information, including logs, can be found on [this page](https://notabug.org/vimuser/libreboot/issues/23). + + USB keyboard wakeup on GM45 laptops {#usb_keyboard_gm45} =================================== @@ -281,8 +297,9 @@ Look at resources/scripts/helpers/misc/libreboot\_usb\_bugfix Put this script in /etc/init.d/ on debian-based systems. -Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/misc/patch.md b/docs/misc/patch.md @@ -1,20 +1,22 @@ -% Diff and patch + +Diff and patch +============== This is just a quick guide for reference, use 'man' to know more. [Back to index](./) + + Apply a patch ============= -To apply a patch to a single file, do that in it's directory: - - $ patch < foo.patch +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 +file the patch should be applied to, the above will work. Otherwise:\ +**\$ patch foo.txt < bar.patch** You can apply a patch to an entire directory, but note the "p level". What this means is that inside patch files will be the files that you @@ -22,46 +24,43 @@ intend to patch, identified by path names that might be different when the files ane located on your own computer instead of on the computer where the patch was created. 'p' level instructs the 'patch' utility to ignore parts of the path name to identify the files correctly. -Usually a p level of 1 will work, so you would use: - - $ patch -p1 < baz.patch +Usually a p level of 1 will work, so you would use:\ +**\$ patch -p1 < baz.patch** Change to the top level directory before running this. If a patch level of 1 cannot identify the files to patch, then inspect the patch file for -file names. For example: - +file names. For example:\ **/home/user/do/not/panic/yet.c** -and you are working in a directory that contains panic/yet.c, use: - - $ patch -p5 < baz.patch +and you are working in a directory that contains panic/yet.c, use:\ +**\$ patch -p5 < baz.patch** You usually count one up for each path separator (forward slash) removed from the beginning of the path, until you are left with a path that exists in the current working directory. The count is the p level. -Removing a patch using the -R flag - - $ patch -p5 -R < baz.patch +Removing a patch using the -R flag\ +**\$ patch -p5 -R < baz.patch** [Back to top of page.](#pagetop) + + Create a patch with diff ======================== -Diff can create a patch for a single file: +Diff can create a patch for a single file:\ +**\$ diff -u original.c new.c > original.patch** - $ diff -u original.c new.c > original.patch +For diff'ing a source tree:\ +**\$ cp -R original new** -For diff'ing a source tree: +Do whatever you want in new/ and then diff it:\ +**\$ diff -rupN original/ new/ > original.patch** - $ cp -R original new - -Do whatever you want in new/ and then diff it: +[Back to top of page.](#pagetop) - $ diff -rupN original/ new/ > original.patch -[Back to top of page.](#pagetop) git diff ======== @@ -70,34 +69,31 @@ git is something special. Note: this won't show new files created. -Just make whatever changes you want to a git clone and then: - - $ git diff > patch.git - -Note the git revision that you did this with: - - $ git log +Just make whatever changes you want to a git clone and then:\ +**\$ git diff > patch.git** -Alternatively (better yet), commit your changes and then use: +Note the git revision that you did this with:\ +**\$ git log** - $ git format-patch -N +Alternatively (better yet), commit your changes and then use:\ +\$ **git format-patch -N**\ Replace N with the number of commits that you want to show. [Back to top of page.](#pagetop) + + git apply ========= it really is. Now to apply that patch in the future, just git clone it again and do -with the git revision you found from above: - - $ git reset \--hard REVISIONNUMBER +with the git revision you found from above:\ +**\$ git reset \--hard REVISIONNUMBER** -Now put patch.git in the git clone directory and do: - - $ git apply patch.git +Now put patch.git in the git clone directory and do:\ +**\$ git apply patch.git** If you use a patch from git format-patch, then use **git am patch.git** instead of **git apply patch.git**. git-am will re-create the commits @@ -105,8 +101,9 @@ aswell, instead of just applying the patch. [Back to top of page.](#pagetop) -Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative diff --git a/docs/publish.sh b/docs/publish.sh @@ -1,10 +0,0 @@ -#!/bin/sh - -# see equivalent script in libreboot-website for more info - -FILE=${1%.md} -echo $FILE -cat $FILE.md > temp.md -sed temp.md -i -e 's/.md\(#[a-z\-]*\)*)/.html\1)/g' -TOC=$(grep -q "^x-toc-enable: true$" temp.md && echo "--toc") -pandoc -t html temp.md -s --css /global.css --section-divs -T Libreboot $TOC > $FILE.html diff --git a/docs/release.md b/docs/release.md @@ -1,14 +1,20 @@ -% Libreboot release information + +Libreboot release information +============================= Updated versions of libreboot can be found at [libreboot.org](http://libreboot.org/). + + Old releases ------------ See [archive\_old.html](archive_old.html) for information about older libreboot releases. + + Libreboot 20160907 {#release20160907} ================== @@ -40,7 +46,7 @@ Libreboot 20160818 {#release20160818} Release date: 18th August 2016. Installation instructions can be found at ***docs/install/***. Building -instructions (for source code) can be found at ***docs/git/#build***. +instructions (for source code) can be found at ***docs/git/\#build***. Machines supported in this release: ----------------------------------- @@ -68,22 +74,22 @@ Machines supported in this release: also fit inside an X60/X60s. - **ThinkPad X60 Tablet** (1024x768 and 1400x1050) with digitizer support - - See ***docs/hcl/#supported\_x60t\_list*** for list of supported + - See ***docs/hcl/\#supported\_x60t\_list*** for list of supported LCD panels - It is unknown whether an X61 Tablet can have it's mainboard replaced with an X60 Tablet motherboard. - **ThinkPad T60** (Intel GPU) (there are issues; see below): - See notes below for exceptions, and - ***docs/hcl/#supported\_t60\_list*** for known working LCD + ***docs/hcl/\#supported\_t60\_list*** for known working LCD panels. - It is unknown whether a T61 can have it's mainboard replaced with a T60 motherboard. - - See ***docs/future/#t60\_cpu\_microcode***. + - See ***docs/future/\#t60\_cpu\_microcode***. - T60P (and T60 laptops with ATI GPU) will likely never be - supported: ***docs/hcl/#t60\_ati\_intel*** + supported: ***docs/hcl/\#t60\_ati\_intel*** - **ThinkPad X200** - X200S and X200 Tablet are also supported, conditionally; see - ***docs/hcl/x200.html#x200s*** + ***docs/hcl/x200.html\#x200s*** - **ME/AMT**: libreboot removes this, permanently. ***docs/hcl/gm45\_remove\_me.html*** - **ThinkPad R400** @@ -99,10 +105,10 @@ Machines supported in this release: - **ME/AMT**: libreboot removes this, permanently. ***docs/hcl/gm45\_remove\_me.html*** - **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) - - See ***docs/hcl/#macbook11***. + - See ***docs/hcl/\#macbook11***. - **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - - See ***docs/hcl/#macbook21***. + - See ***docs/hcl/\#macbook21***. Changes for this release, relative to r20150518 (earliest changes last, recent changes first) --------------------------------------------------------------------------------------------- @@ -202,8 +208,9 @@ Kocialkowski) Various fixes to the ich9gen utility (e.g. flash component density is now set correctly in the descriptor, gbe-less descriptors now supported) -Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org> + +Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\ Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license or any later version published by Creative