diff options
126 files changed, 17587 insertions, 21048 deletions
diff --git a/docs/archive_old.html b/docs/archive_old.html deleted file mode 100644 index 061bd309..00000000 --- a/docs/archive_old.html +++ /dev/null @@ -1,1509 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('css/main.css'); - </style> - - <title>Libreboot release information (old)</title> -</head> -<body> - - <div class="section"> - - <h1 id="pagetop">Libreboot release information (old)</h1> - <p> - Information for this release can be found at <a href="release.html">release.html</a>. - Updated versions of libreboot can be found at <a href="http://libreboot.org/">libreboot.org</a>. - </p> - - <div class="important"> - <p> - <b>This page is *obsolete*, provided for historical purposes.</b> - </p> - </div> - - </div> - - <div class="section"> - - <h2>Releases</h2> - <ul> - <li><a href="#release20150518">r20150518 (18th May 2015)</a></li> - <li><a href="#release20150124">r20150124 (24th January 2015), r20150126 (26th January 2015), r20150208 (8th February 2015)</a></li> - <li><a href="#release20141015">r20141015 (15th October 2014)</a></li> - <li><a href="#release20140911">r20140911 (6th release)</a> (11th September 2014 <b>pre-release, 7th beta</b>)</li> - <li><a href="#release20140622">r20140622 (5th release)</a> (7th March 2014, revised 22nd June 2014)</li> - <li><a href="#release20140221">r20140221 (4th release)</a> (21st February 2014)</li> - <li><a href="#release20131214">r20131214 (3rd release)</a> (14th December 2013)</li> - <li><a href="#release20131213">r20131213 (2nd release)</a> (13th December 2013)</li> - <li><a href="#release20131212">r20131212 (1st release)</a> (12th December 2013)</li> - </ul> - - </div> - - <div class="section"> - - <h1 id="release20150518">Release 20150518</h1> - - <p> - Release date: 18th May 2015. - </p> - - <p> - Installation instructions can be found at <b><i>docs/install/</i></b>. - Building instructions (for source code) can be found at <b><i>docs/git/#build</i></b>. - </p> - - <h2>Machines supported in this release:</h2> - <ul> - <li> - <b>ThinkPad X60/X60s</b> - <ul> - <li> - You can also remove the motherboard from an X61/X61s and replace it with an X60/X60s motherboard. - An X60 Tablet motherboard will also fit inside an X60/X60s. - </li> - </ul> - </li> - <li> - <b>ThinkPad X60 Tablet</b> (1024x768 and 1400x1050) with digitizer support - <ul> - <li>See <b><i>docs/hcl/#supported_x60t_list</i></b> for list of supported LCD panels</li> - <li>It is unknown whether an X61 Tablet can have it's mainboard replaced with an X60 Tablet motherboard.</li> - </ul> - </li> - <li> - <b>ThinkPad T60</b> (Intel GPU) (there are issues; see below): - <ul> - <li>See notes below for exceptions, and <b><i>docs/hcl/#supported_t60_list</i></b> for known working LCD panels.</li> - <li>It is unknown whether a T61 can have it's mainboard replaced with a T60 motherboard.</li> - <li>See <b><i>docs/future/#t60_cpu_microcode</i></b>.</li> - <li>T60P (and T60 laptops with ATI GPU) will likely never be supported: <b><i>docs/hcl/#t60_ati_intel</i></b></li> - </ul> - </li> - <li> - <b>ThinkPad X200</b> - <ul> - <li>X200S and X200 Tablet are also supported, conditionally; see <b><i>docs/hcl/x200.html#x200s</i></b></li> - <li><b>ME/AMT</b>: libreboot removes this, permanently. <b><i>docs/hcl/gm45_remove_me.html</i></b></li> - </ul> - </li> - <li> - <b>ThinkPad R400</b> - <ul> - <li>See <b><i>docs/hcl/r400.html</i></b></li> - <li><b>ME/AMT</b>: libreboot removes this, permanently. <b><i>docs/hcl/gm45_remove_me.html</i></b></li> - </ul> - </li> - <li> - <b>ThinkPad T400</b> - <ul> - <li>See <b><i>docs/hcl/t400.html</i></b></li> - <li><b>ME/AMT</b>: libreboot removes this, permanently. <b><i>docs/hcl/gm45_remove_me.html</i></b></li> - </ul> - </li> - <li> - <b>ThinkPad T500</b> - <ul> - <li>See <b><i>docs/hcl/t500.html</i></b></li> - <li><b>ME/AMT</b>: libreboot removes this, permanently. <b><i>docs/hcl/gm45_remove_me.html</i></b></li> - </ul> - </li> - <li> - <b>Apple MacBook1,1</b> (MA255LL/A, MA254LL/A, MA472LL/A) - <ul> - <li>See <b><i>docs/hcl/#macbook11</i></b>.</li> - </ul> - </li> - <li> - <b>Apple MacBook2,1</b> (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - <ul> - <li>See <b><i>docs/hcl/#macbook21</i></b>.</li> - </ul> - </li> - </ul> - - <h2> - Changes for this release, relative to r20150208 (earliest changes last, recent changes first) - </h2> - <ul> - <li>Add a whitelist entry to board_enable.c in flashrom, for the ThinkPad R400, T400 and T500</li> - <li> - Updated flashrom (to SVN revision 1889) - <ul> - <li>X200 whitelist patch removed (merged upstream)</li> - <li>X200 whitelist modified to include X200S and X200 Tablet</li> - </ul> - </li> - <li>libreboot_util: don't include cmos layout files (not needed anymore)</li> - <li><b>coreboot-libre: backport patches for X200 Tablet digitizer support</b></li> - <li>build/release/archives: create SHA512 sum manifest file of the release archives</li> - <li>build/release/archives: separate crossgcc into a new archive</li> - <li>disabled generation of txtmode ROM images for now (they will be back again in the next release)</li> - <li>coreboot-libre: delete unused code (reduce size of src archive)</li> - <li>Flashing guides: make them more friendly to colourblind people</li> - <li> - docs/gnulinux/encrypted_*.html: Remove mention of password length - - it was arbitrary and pointless. - </li> - <li>docs/maintain/: Finish the guide</li> - <li> - scripts/download/coreboot: use diffs included in libreboot, not external gerrit cherry-picks - - review.coreboot.org (gerrit) being down no longer kills - libreboot (backup mirrors of the master repository exist) - </li> - <li>docs/install/bbb_setup.html: Add info about wp/hold and pinouts</li> - <li>docs/: improve the description of libreboot</li> - <li>docs/hcl/gm45_remove_me.html: notes about the demefactory utility</li> - <li>docs/install/bbb_setup.html: EHCI debug: recommend linux-libre</li> - <li>docs/install/bbb_setup.html: EHCI Debug logging setup guide</li> - <li>docs/hcl/t500.html: Add screen compatibility report (TODO: fix incompatible screens)</li> - <li> - Update coreboot(again) + merge GM45 hybrid GPU patches - - means that T400/T500 with the ATI+Intel hybrid GPU setup - will work (ATI disabled, Intel permanently enabled). - power_on_after_fail nvram option added to all GM45 boards, - defaulting to No, so that plugging it AC doesn't boot up - the system against the users will. Net20DC is now the default - debug dongle on all boards (compatible with BBB). - </li> - <li>demefactory (new utility): create GM45 factory.rom without the ME</li> - <li>ich9deblob: re-factor descriptor.c functions</li> - <li>docs/hcl/t500.html: add hardware logs</li> - <li>docs/gnulinux/encrypted_*.html: No password for default entry</li> - <li>docs/git/: Add more details about BUC.TS</li> - <li>grub.cfg: Also scan for grub2/grub.cfg, not just grub/grub.cfg</li> - <li>docs/maintain/ (new section. WIP!): Maintaining libreboot</li> - <li>docs/gnulinux/grub_boot_installer.html: Fix hazardous instruction</li> - <li>docs/tasks.html: Better categorization between intel/amd/arm</li> - <li>docs/install/bbb_setup.html: notes about SPI flashing stability</li> - <li>docs/install/bbb_setup.html: more names for the 0.1" cables</li> - <li>docs/install/*_external.html: add disclaimer about thermal paste</li> - <li>docs/install/bbb_setup.html: Fix broken links</li> - <li>docs/install/bbb_setup.html: preliminary notes about EHCI debug</li> - <li>docs/hcl/gm45_remove_me.html: Link to websites talking about the ME</li> - <li>docs/install/{t400,t500,r400}_external.html: Notes about CPU compatibility</li> - <li>Delete the ich9macchange script. It's useless, and confuses people</li> - <li>docs/hcl/gm45_remove_me.html: prioritize ich9gen executable path</li> - <li>docs/hcl/gm45_remove_me.html: prioritize changing mac address</li> - <li>docs/hcl/gm45_remove_me.html: less confusing notes about ich9gen</li> - <li>build/dependencies/parabola: Add dependencies for x86_64</li> - <li>scripts/dependencies/paraboladependencies: build dependencies (32-bit Parabola)</li> - <li><b>New board</b>: ThinkPad T500</li> - <li>Add diffs for descriptor/gbe differences between T500 and X200</li> - <li>coreboot-libre: provide better blob categorization</li> - <li>docs/hcl/gm45_remove_me.html: add notes about flash write protect</li> - <li><b>New board</b>: ThinkPad T400</li> - <li>GRUB: add partial vesamenu.c32 support (fixes tails ISOLINUX menu)</li> - <li>Update GRUB (to revision fa07d919d1ff868b18d8a42276d094b63a58e299)</li> - <li> - Update coreboot (to revision 83b05eb0a85d7b7ac0837cece67afabbdb46ea65) - <ul> - <li> - Intel CPU microcode (most of it) no longer deleted, - because it was deleted upstream (moved to a 3rd - party repository). - </li> - <li>MacBook2,1 cstate patch is no longer cherry picked (merged upstream)</li> - <li>Patch to disable use of timestamps in coreboot no longer included (merged upstream)</li> - </ul> - </li> - <li>coreboot-libre: don't list vortex86ex kbd firmware as microcode (list it separately)</li> - <li>coreboot-libre: don't rm */early_setup_ss.h (these are not blobs)</li> - <li>coreboot-libre: add GPLv3 license to the findblobs script</li> - <li>coreboot-libreboot: don't rm raminit_tables (nahelem/sandybridge) (they are not blobs)</li> - <li>coreboot-libre: don't delete the .spd.hex files (they are not blobs)</li> - <li>build/release/archives: don't put rmodtool in libreboot_util</li> - <li>docs/install/x200_external.html: recommend installing GNU+Linux at the end</li> - <li>docs/install/x200_external.html: add more photos, improve instructions</li> - <li>build/clean/grub: use distclean instead of clean</li> - <li>grub-assemble: Add the <i>bsd</i> and <i>part_bsd</i> modules</li> - <li>build/roms/withgrub: Only run ich9gen if gm45/gs45 images exist</li> - <li>docs/git/: Add notes about building for specific boards</li> - <li>build/roms/withgrub: Allow building for a custom range of boards</li> - <li>grub-assemble: Disable verbose output</li> - <li>Add documentation on how to unlock root encrypted fs with key in initramfs in Parabola Linux</li> - <li>docs/gnulinux/grub_cbfs.html: Improve structure (easier to use)</li> - <li>grub.cfg: Disable the beep on startup</li> - <li>docs/install/bbb_setup.html: Make the guide easier to use</li> - <li>docs/gnulinux/grub_cbfs.html: Remove redundant instructions</li> - <li>docs/install/x200_external.html: Mark pins in the images</li> - <li>docs/install/bbb_setup.html: Replace 3.3V PSU photo with ATX PSU</li> - <li>docs/hcl/x200.html: Add dumps from 4-MiB X200 with Lenovo BIOS 3.22</li> - <li>docs/hcl/x200.html: Add dumps from 4-MiB X200 with Lenovo BIOS 3.18</li> - <li>grub.cfg: add syslinux_configfile menuentry for ahci0</li> - <li>grub.cfg: Add more paths for syslinux_configfile</li> - <li>docs/future.html: T60: Add EDID dump from LG-Philips LP150E05-A2K1</li> - <li>docs/install/bbb_setup.html: Further clarify which clip is needed</li> - <li>bash scripts: Make script output more user-friendly in general</li> - <li>bash scripts: Only enable verbose output if DEBUG= is used</li> - <li> - build: Support multiple extra options - - now possible to build multiple images for arbitrary - boards (configs), but without building the entire - collection. - </li> - <li> - Deleted the signing archive key - - the finger print and ID is given instead, so that - the user can download it from a key server - </li> - <li> - scripts/helpers/build/release: Move docs to separate archive - - reduces the size of the other archives considerably - </li> - <li>Move DEBLOB to resources/utilities/coreboot-libre/deblob</li> - <li> - scripts/helpers/build/release: Delete DEBLOB from libreboot_src/ - - not needed in libreboot_src (release archive) because it - contains a coreboot revision that has already been deblobbed. - </li> - <li>flash (script): Use <i>build</i> instead of <i>DEBLOB</i> to know if in src</li> - <li>docs/install/r400_external.html: Show images, don't link.</li> - <li>docs/install/x200_external.html: Show images, don't link.</li> - <li>docs/install/bbb_setup.html: Show images, instead of linking</li> - <li>Documentation: optimize all images (reduce file sizes)</li> - <li> - Remove download links from the release page (and the archive page) - - release archives are hosted differently following this release, - which means that the old methods are no longer viable. - </li> - <li>Moved ich9macchange to resources/scripts/misc/ich9macchange</li> - <li> - ich9macchange: assume that the script is being run from _util - (act only on one ROM image, defined by a user-provided path) - </li> - <li>Move grub-background to resources/scripts/misc/grub-background</li> - <li>grub-background: assume that it is being run from libreboot_util</li> - <li>grub-background: change only one ROM image, specified by path</li> - <li>build (release archives): Add the commitid file to release/</li> - <li>build-release: Move the release archives to release/</li> - <li> - Merge all build scripts into a single generic script, - with helpers in resources/scripts/helpers/build/ - </li> - <li> - Replace <i>getall</i> with <i>download</i>, which takes as input an argument - specifying which program the user wants to download. - </li> - <li>Moved the get scripts to resources/scripts/helpers/download/</li> - <li>build-release: Remove the powertop entries</li> - <li>Documentation: general improvements to the flashing instructions</li> - <li>Merged all flashing scripts into a single script</li> - <li>Updated GRUB</li> - <li>bucts: Make it build without git</li> - <li>Moved dejavu-fonts-ttf-2.34/AUTHORS to resources/grub/font/</li> - <li>Deleted GRUB Invaders from libreboot</li> - <li>Deleted SeaBIOS from libreboot</li> - <li>build-release: optimize use of tar (reduced file sizes)</li> - <li>grub.cfg: add another SYSLINUX config location (/syslinux/syslinux.cfg)</li> - <li>build-release: remove the bin/ directory from libreboot_util</li> - <li>cleandeps: delete the bin/ directory</li> - <li>buildrom-withgrub: create the bin directory if it does not exist</li> - <li>coreboot-libre: don't use git for version timestamp</li> - <li>i945-pwm: add clean command to Makefile</li> - <li>i945-pwm: add -lz to Makefile</li> - <li>docs/install/x200_external: Mention GPIO33 non-descriptor mode</li> - <li>docs/hcl/: Remove redundant links</li> - <li>ich9macchange: Add R400</li> - <li>build-release: Separate ROM images into individual archives</li> - <li>build-release: rename libreboot_bin to libreboot_util</li> - <li><b>New board:</b> ThinkPad R400 support added to libreboot.</li> - <li>bbb_setup.html: tell user to use libreboot's own flashrom</li> - </ul> - - </div> - - <div class="section"> - - <h1 id="release20150124">Release 20150124, 20150126 and 20150208</h1> - - <p> - Release date: 24th January 2015. - </p> - - <h2>Machines supported in this release:</h2> - <ul> - <li> - <b>Lenovo ThinkPad X60/X60s</b> - <ul> - <li> - You can also remove the motherboard from an X61/X61s and replace it with an X60/X60s motherboard. - An X60 Tablet motherboard will also fit inside an X60/X60s. - </li> - </ul> - </li> - <li> - <b>Lenovo ThinkPad X60 Tablet</b> (1024x768 and 1400x1050) with digitizer support - <ul> - <li>See <b>hcl/#supported_x60t_list</b> for list of supported LCD panels</li> - <li>It is unknown whether an X61 Tablet can have it's mainboard replaced with an X60 Tablet motherboard.</li> - </ul> - </li> - <li> - <b>Lenovo ThinkPad T60</b> (Intel GPU) (there are issuesinstall/x200_external.html; see below): - <ul> - <li>See notes below for exceptions, and <b>hcl/#supported_t60_list</b> for known working LCD panels.</li> - <li>It is unknown whether a T61 can have it's mainboard replaced with a T60 motherboard.</li> - <li>See <b>future/#t60_cpu_microcode</b>.</li> - <li>T60P (and T60 laptops with ATI GPU) will likely never be supported: <b>hcl/#t60_ati_intel</b></li> - </ul> - </li> - <li> - <b>Lenovo ThinkPad X200</b> - <ul> - <li>X200S and X200 Tablet are also supported, conditionally; see <b>hcl/x200.html#x200s</b></li> - <li><b>ME/AMT</b>: libreboot removes this, permanently. <b>hcl/gm45_remove_me.html</b></li> - </ul> - </li> - <li> - <b>Lenovo ThinkPad R400</b> (r20150208 and later, only) - <ul> - <li><b>ME/AMT</b>: libreboot removes this, permanently. <b>hcl/gm45_remove_me.html</b></li> - </ul> - </li> - <li> - <b>Apple MacBook1,1</b> (MA255LL/A, MA254LL/A, MA472LL/A) - <ul> - <li>See <b>hcl/#macbook11</b>.</li> - </ul> - </li> - <li> - <b>Apple MacBook2,1</b> (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - <ul> - <li>See <b>hcl/#macbook21</b>.</li> - </ul> - </li> - </ul> - - <h2> - Revisions for r20150208 (relative to r20150126) - </h2> - <p> - This is a maintenance release (polishing) based on r20150126. Users who installed r20150126 - don't really need to update to this release. - </p> - <ul> - <li>buildrom-withgrub: use gnulove.jpg background on 16:10 laptops (MacBook2,1 and X200)</li> - <li>build-release: include grub-background script in libreboot_bin</li> - <li>grub-background (new): lets user change GRUB background image</li> - <li>grub-assemble: Add link to original utility.</li> - <li>buildrom-withgrub: Put background.jpg in CBFS, not GRUB memdisk</li> - <li>grub-assemble: merge scripts into a single script gen.sh</li> - <li>Documentation: implement theme, drastically improve readability</li> - <li>docs/hcl/: update list of compatible T60 LCD panels</li> - <li>docs/: more clarification of libreboot's stated purpose.</li> - <li>build-release: include the commitid file in the release archives</li> - <li>docs/: Further emphasize the GNU+Linux requirement.</li> - <li>lenovobios_firstflash: fix BASH errors</li> - <li>lenovobios_secondflash: fix BASH errors</li> - <li>docs/install/x200_external.html: Tell user to switch MAC address.</li> - <li>docs/git/: Add to the list of x86_64 compatible hosts.</li> - <li>docs/install/: Remove old (obsolete) information.</li> - <li>docs/git/: Say that the build dependencies are for src (and not nedeed for libreboot_bin)</li> - <li>build: re-factor the descriptor/gbe generating loop for GM45/ICH9M</li> - <li>X60, X60S and X60 Tablet now the same ROM images.</li> - <li>Add QEMU (q35/ich9) support to libreboot.</li> - <li>Add QEMU (i440fx/piix4) support to libreboot</li> - <li>docs/: Re-write the description of what libreboot is.</li> - <li>docs/release.html: Add notes about how to use GPG.</li> - <li>build-release: delete the commitid file from release archives</li> - <li>build-release: create file named commitid after build-release</li> - </ul> - <h2> - Revisions for r20150126 (relative to r20150124) - </h2> - <p> - This is a bug fix release based on r20150124. It contains a few small changes: - </p> - <ul> - <li>grub.cfg: hardcode the list of partitions to search (speeds up booting considerably. GRUB regexp isn't very well optimized)</li> - <li>Docs (x200.html hcl): Remove incorrect information</li> - <li>Documentation (bbb_setup.html): Fix typos</li> - <li> - build-release: delete ich9fdgbe_{4m,8m}.bin files from ich9gen - <ul> - <li> - These were accidentically included in the r20150124 release. They - are generated from ich9gen so it's ok, but they don't need to be - in the archive. - </li> - </ul> - </li> - <li>Documentation (grub_cbfs.html): Looping in libreboot_grub.cfg (Add notes about it if the user copied from grub.cfg in CBFS.)</li> - </ul> - <h2> - Changes for this release (latest changes first, earliest changes last) - </h2> - <ul> - <li>grub.cfg: Added (ahci1) to list of devices for ISOLINUX parser (CD/DVD) (this is needed for the X200 docking station).</li> - <li>grub.cfg: ISOLINUX parsing is now done on all USB partitions.</li> - <li>grub.cfg: Automatically switched to /boot/grub/libreboot_grub.cfg on a partition, if it exists.</li> - <li>libreboot_bin: added static ARM binaries for flashrom, cbfstool, ich9gen and - ich9deblob (tested on beaglebone black).</li> - <li>Flashrom: removed redundant Macronix flashchip definitions (for X200 owners).</li> - <li>Flashrom: added whitelist for ThinkPad X200.</li> - <li>X200: fixed uneven backlight (at low levels)</li> - <li>ich9macchange (new script, uses ich9gen): for changing the default MAC address on X200 ROM images.</li> - <li>ich9gen: added capability to change the default MAC address (and update the checksum)</li> - <li>ich9deblob: added new utility ich9gen: this can generate a descriptor+gbe image without a factory.rom dump present.</li> - <li>Modified ich9deblob to use a struct for Gbe, documenting everything.</li> - <li>Massively updated the ich9deblob utility: re-factored everything completely.</li> - <li>Enabled cstates 1 and 2 on macbook21. This reduces idle heat / power consumption.</li> - <li>buildrom-withgrub: disabled creation of *txtmode*.rom for X200 (only framebuffer graphics work)</li> - <li>Updated SeaBIOS (again)</li> - <li>docs/install/#flashrom_x200: improve instructions</li> - <li>Updated flashrom (again) - patches updated</li> - <li>Updated GRUB (again)</li> - <li>Updated coreboot (again)</li> - <li>build-release: not all files were copied to libreboot_src. fix that.</li> - <li>build-release: include cbmem (statically compiled) in libreboot_bin</li> - <li>Documentation (X200): added software-based flashing instructions</li> - <li>Documentation: remove all references to the bus pirate (replaced with BBB flashing tutorials)</li> - <li><b>New board:</b> ThinkPad X200S and X200 Tablet support added to libreboot</li> - <li>build: automatically find board names (configs) to build for</li> - <li><b>New board:</b> ThinkPad X200 support added to libreboot</li> - <li>coreboot-libre config (all boards): enable USB dongle log output (for BeagleBone Black)</li> - <li>cleandeps: actually clean grubinvaders</li> - <li>.gitignore: add powertop directory</li> - <li>cleandeps: clean i945-pwm utility</li> - <li>scripts (all): fix typos</li> - <li>Documentation: general cleanup.</li> - <li>builddeps-flashrom: reduce build commands to a single for loop</li> - <li>scripts (all): replace unnecessary rm -Rf with rm -f</li> - <li>docs/release.html: add lenovo g505s to the list of candidates</li> - <li>.gitignore: add libreboot_bin.tar.xz and libreboot_src.tar.xz</li> - <li> - libreboot_bin.tar.xz: Include utils as statically linked binaries - <ul> - <li>This means that the user does not have to install build dependency - or build from source anymore.</li> - </ul> - </li> - <li>deps-parabola (removed) Remove Parabola dependencies script. Will re-add later (properly tested)</li> - <li>grub.cfg: Add more path checks to isolinux parser (more ISOs should work now)</li> - <li>Update SeaBIOS</li> - <li>x60flashfrom5 (new), for X60 users upgrading from 5th/early release</li> - <li>Update flashrom</li> - <li>Update GRUB</li> - <li> - Updated coreboot-libre - <ul> - <li>i945: permanently set tft_brightness to 0xff (fixes bug on X60 where - turning up brightness at max would make it loop back to low brightness)</li> - </ul> - </li> - <li> - getcb: Revert X60/T60 to legacy backlight controls - <ul> - <li>The ACPI brightness patches were abandoned and obsolete.</li> - </ul> - </li> - <li>grub.cfg: Only load initrd.img if it exists. Add rw to linux line (for ProteanOS)</li> - <li>build: Only generate the GRUB configurations once (re-use on all images)</li> - <li>Only build 2 GRUB payload executables, re-use on all boards.</li> - <li> - resources/utilities/grub-assemble/gen.txtmode.sh: Use GNU BASH<br/> - resources/utilities/grub-assemble/gen.vesafb.sh: Use GNU BASH - </li> - <li>scripts (error handling): Replace exit with exit 1 (make debugging easier)</li> - <li> - Move most files in CBFS to GRUB memdisk, except grub.cfg and grubtest.cfg - <ul> - This reduces the space used in CBFS because coreboot compresses - its payloads with LZMA by default. grub.cfg is all that most users - will want to modify, which remains in CBFS. - </ul> - </li> - <li>docs/release.html Add DMP vortex86ex to list of candidates.</li> - <li>docs/release.html Add ThinkPad X201 to list of candidates.</li> - <li>New links added to docs/security/x60_security and docs/security/t60_security</li> - <li>lenovobios_secondflash: Warn if BUCTS is not present. (not a dealbreaker. Can just pull out nvram battery/coin).</li> - <li>lenovobios_firstflash: Fail if BUCTS fails. (anti-bricking precaution)</li> - <li>Removed obnoxious warnings from flashing scripts, improved documentation instead.</li> - <li>scripts (all): add proper error checking (fail fast, fail early. Do not continue if there are errors)</li> - <li>buildrom-withgrub: rename image to boardname_layout_romtype.rom</li> - <li>buildrom-withgrub: don't move cbfstool, execute directly</li> - <li>resources/utilities/grub-assemble: add French Dvorak (BEPO) keyboard layout.</li> - <li>Documentation: add docs/hardware/x60_keyboard.html (show how to replace keyboard on X60/X60T)</li> - <li>Documentation: major cleanup (better structure, easier to find things)</li> - <li> - docs/release.html: Remove Acer CB5 from list of future candidates. - <ul> - <li> - Too many issues. Chromebooks are crippled (soldered RAM/storage/wifi) - and have too many usability issues for the libreboot project. - </li> - </ul> - </li> - <li>docs/gnulinux/grub_cbfs.html Major cleanup. Usability improvements.</li> - <li> - flash (flashrom script): remove boardmismatch=force - <ul> - <li> - This was put there before for users upgrading from libreboot r5 - to r6, but also allows the user to flash the wrong image. For - example, the user could flash a T60 image on an X60, thus - bricking the system. It's almost certain that most people - have upgraded by now, so remove this potentially dangerous - option. - </li> - </ul> - </li> - <li>Documentation: update compatibility list for X60T LCD panels.</li> - <li>docs/release.html: add note about X60 Tablet board in X60/X60s</li> - <li>docs/howtos/grub_boot_installer.html: small corrections</li> - <li>docs/howtos/grub_boot_installer.html: improved readability, fixed html errors</li> - <li>Documentation (macbook21 related): clean up</li> - </ul> - - </div> - - <div class="section"> - - <h1 id="release20141015">Release 20141015</h1> - - <h2>Machines supported in this release:</h2> - <ul> - <li> - <b>Lenovo ThinkPad X60/X60s</b> - <ul> - <li> - You can also remove the motherboard from an X61/X61s and replace it with an X60/X60s motherboard. - An X60 Tablet motherboard will also fit inside an X60/X60s. - </li> - </ul> - </li> - <li> - <b>Lenovo ThinkPad X60 Tablet</b> (1024x768 and 1400x1050) with digitizer support - <ul> - <li>See <b>hcl/#supported_x60t_list</b> for list of supported LCD panels</li> - <li>It is unknown whether an X61 Tablet can have its mainboard replaced with an X60 Tablet motherboard.</li> - </ul> - </li> - <li> - <b>Lenovo ThinkPad T60</b> (Intel GPU) (there are issues; see below): - <ul> - <li>See notes below for exceptions, and <b>hcl/#supported_t60_list</b> for known working LCD panels.</li> - <li>It is unknown whether a T61 can have its mainboard replaced with a T60 motherboard.</li> - <li>See <b>future/#t60_cpu_microcode</b>.</li> - <li>T60P (and T60s with ATI GPU) will likely never be supported: <b>hcl/#t60_ati_intel</b></li> - </ul> - </li> - <li> - <b>Apple MacBook1,1</b> (MA255LL/A, MA254LL/A, MA472LL/A) - <ul> - <li>See <b>hcl/#macbook11</b>.</li> - </ul> - </li> - <li> - <b>Apple MacBook2,1</b> (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - <ul> - <li>See <b>hcl/#macbook21</b>.</li> - </ul> - </li> - </ul> - - <h2> - Changes for this release (latest changes first, earliest changes last) - </h2> - <ul> - <li>Updated coreboot (git commit 8ffc085e1affaabbe3dca8ac6a89346b71dfc02e), the latest at the time of writing.</li> - <li>Updated SeaBIOS (git commit 67d1fbef0f630e1e823f137d1bae7fa5790bcf4e), the latest at the time of writing.</li> - <li>Updated Flashrom (svn revision 1850), the latest at the time of writing.</li> - <li>Updated GRUB (git commit 9a67e1ac8e92cd0b7521c75a734fcaf2e58523ad), the latest at the time of writing.</li> - <li>Cleaned up the documentation, removed unneeded files.</li> - <li>ec/lenovo/h8 (x60/x60s/x60t/t60): Enable wifi/bluetooth/wwan/touchpad/trackpoint by default.</li> - <li>Documentation: Updated list of T60 LCDs (Samsung LTN150XG 15" XGA listed as non-working).</li> - <li>builddeps-coreboot: Don't build libpayload (not needed. This was leftover by mistake, when trying out the TINT payload).</li> - <li>Replaced most diff files (patches) for coreboot with gerrit checkouts (cherry-pick).</li> - <li>Documentation: x60_security.html and t60_security.html: added links to info about the ethernet controller (Intel 82573).</li> - <li>Documentation: x60_security.html and t60_security.html: added notes about DMA and the docking station.</li> - <li> - Documentation: configuring_parabola.html: basic post-install steps for Parabola GNU+Linux - (helpful, since libreboot development is being moved to Parabola at the time of writing). - </li> - <li>builddeps-coreboot: use 'make crossgcc-i386' instead of 'make crossgcc'. Libreboot only targets x86 at the time of writing.</li> - <li>ROM images no longer include SeaBIOS. Instead, the user adds it afterwards. Documentation and scripts updated.</li> - <li>docs/images/encrypted_parabola.html: Notes about linux-libre-grsec</li> - <li>Documentation: encrypted_parabola.html: add tutorial for encrypted Parabola GNU+Linux installation.</li> - <li>Documentation: added more info about wifi chipsets</li> - </ul> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="release20140911">6th release (pre-release, 7th beta)</h1> - - <ul> - <li>Released 11th July 2014 (pre-release) 1st beta</li> - <li>Revised (pre-release, 2nd beta) 16th July 2014</li> - <li>Revised (pre-release, 3rd beta) 20th July 2014</li> - <li>Revised (pre-release, 4th beta) 29th July 2014</li> - <li>Revised (pre-release, 5th beta) 11th August 2014 (corrected 11th August 2014)</li> - <li>Revised (pre-release, 6th beta) 3rd September 2014</li> - <li>Revised (pre-release, 7th beta) 11th September 2014</li> - </ul> - - <h2>Machines still supported (compared to previous release):</h2> - <ul> - <li> - <b>Lenovo ThinkPad X60/X60s</b> - <ul> - <li> - You can also remove the motherboard from an X61/X61s and replace it with an X60/X60s motherboard. - </li> - </ul> - </li> - </ul> - <h2>New systems supported in this release:</h2> - <ul> - <li> - <b>Lenovo ThinkPad X60 Tablet</b> (1024x768 and 1400x1050) with digitizer support - <ul> - <li>See <b>hcl/#supported_x60t_list</b> for list of supported LCD panels</li> - <li>It is unknown whether an X61 Tablet can have its mainboard replaced with an X60 Tablet motherboard.</li> - </ul> - </li> - <li> - <b>Lenovo ThinkPad T60</b> (Intel GPU) (there are issues; see below) - <ul> - <li>See notes below for exceptions, and <b>hcl/#supported_t60_list</b> for known working LCD panels.</li> - <li>It is unknown whether a T61 can have its mainboard replaced with a T60 motherboard.</li> - <li>T60P (and T60s with ATI GPU) will likely never be supported: <b>hcl/#t60_ati_intel</b></li> - </ul> - </li> - <li> - <b>Apple MacBook1,1</b> (MA255LL/A, MA254LL/A, MA472LL/A) - <ul> - <li>See <b>hcl/#macbook11</b>.</li> - </ul> - </li> - <li> - <b>Apple MacBook2,1</b> (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - <ul> - <li>See <b>hcl/#macbook21</b>.</li> - </ul> - </li> - </ul> - <h2>Machines no longer supported (compared to previous release):</h2> - <ul> - <li><b>All previous systems still supported!</b></li> - </ul> - - <h2> - Revisions for r20140911 (7th beta) (11th September 2014) - </h2> - <ul> - <li>The changes below were made in a git repository, unlike in previous releases. Descriptions below are copied from 'git log'.</li> - <li>Update .gitignore for new dependencies.</li> - <li>Use a submodule for i945-pwm.</li> - <li>Don't clean packages that fail or don't need cleaning.</li> - <li>Don't clean i945-pwm, it's not needed.</li> - <li>Regression fix: Parabola live ISO boot issues</li> - <li>Re-enable background images in ISOLINUX/SYSLINUX GRUB parser menus</li> - <li>Regression fix: Re-add CD-ROM (ata0) in GRUB</li> - <li>Documentation: add notes about performance penalty when using ecryptfs.</li> - <li>Documentation: Fixed spelling and grammatical errors.</li> - <li>Documentation: macbook21: add new system as tested</li> - <li>Documentation: macbook21: add info about improving touchpad sensitivity</li> - <li>Documentation: X60 Tablet: add more information about finger input</li> - <li>Documentation: release.html: Add information about recently merged commit in coreboot</li> - </ul> - - <h2> - Revisions for r20140903 (6th beta) (3rd September 2014) - </h2> - <ul> - <li>Added modified builddeb* scripts for Parabola GNU+Linux-libre: buildpac, buildpac-flashrom, buildpac-bucts (courtesy of Noah Vesely)</li> - <li>Documentation: updated all relevant areas to mention use of buildpac* scripts for Parabola users.</li> - <li>Documentation: added information showing how to enable or disable bluetooth on the X60</li> - <li>MacBook1,1 tested! See <b>hcl/#macbook11</b></li> - <li>Documentation: fixed typo in #get_edid_panelname (get-edit changed to get-edid)</li> - <li>Documentation: added images/x60_lcd_change/ (pics only for now)</li> - <li>Added gcry_serpent and gcry_whirlpool to the GRUB module list in the 'build' script (for luks users)</li> - <li> - <b>Libreboot is now based on a new coreboot version from August 23rd, 2014:<br/> - Merged commits (relates to boards that were already supported in libreboot):</b> - <ul> - <li><a href="http://review.coreboot.org/#/c/6697/">http://review.coreboot.org/#/c/6697/</a></li> - <li><a href="http://review.coreboot.org/#/c/6698/">http://review.coreboot.org/#/c/6698/</a> (merged already)</li> - <li><a href="http://review.coreboot.org/#/c/6699/">http://review.coreboot.org/#/c/6699/</a> (merged already)</li> - <li><a href="http://review.coreboot.org/#/c/6696/">http://review.coreboot.org/#/c/6696/</a> (merged already)</li> - <li><a href="http://review.coreboot.org/#/c/6695/">http://review.coreboot.org/#/c/6695/</a> (merged already)</li> - <li><b><a href="http://review.coreboot.org/#/c/5927/">http://review.coreboot.org/#/c/5927/</a> (merged already)</b></li> - <li><a href="http://review.coreboot.org/#/c/6717/">http://review.coreboot.org/#/c/6717/</a> (merged already)</li> - <li><a href="http://review.coreboot.org/#/c/6718/">http://review.coreboot.org/#/c/6718/</a> (merged already)</li> - <li> - <a href="http://review.coreboot.org/#/c/6723/">http://review.coreboot.org/#/c/6723/</a> (merged already) - (text-mode patch, might enable memtest. macbook21) - </li> - <li> - <a href="http://review.coreboot.org/#/c/6732/">http://review.coreboot.org/#/c/6732/</a> (MERGED) - (remove useless ps/2 keyboard delay from macbook21. already merged) - </li> - </ul> - </li> - <li> - These were also merged in coreboot (relates to boards that libreboot already supported): - <ul> - <li><a href="http://review.coreboot.org/#/c/5320/">http://review.coreboot.org/#/c/5320/</a> (merged)</li> - <li><a href="http://review.coreboot.org/#/c/5321/">http://review.coreboot.org/#/c/5321/</a> (merged)</li> - <li><a href="http://review.coreboot.org/#/c/5323/">http://review.coreboot.org/#/c/5323/</a> (merged)</li> - <li><a href="http://review.coreboot.org/#/c/6693/">http://review.coreboot.org/#/c/6693/</a> (merged)</li> - <li><a href="http://review.coreboot.org/#/c/6694/">http://review.coreboot.org/#/c/6694/</a> (merged)</li> - <li><a href="http://review.coreboot.org/#/c/5324/">http://review.coreboot.org/#/c/5324/</a> (merged)</li> - </ul> - </li> - <li>Documentation: removed the section about tft_brightness on X60 (new code makes it obsolete)</li> - <li>Removed all patches from resources/libreboot/patch/ and added new patch: 0000_t60_textmode.git.diff</li> - <li>Updated getcb script and DEBLOB script.</li> - <li>Updated configuration files under resources/libreboot/config/ to accomodate new coreboot version.</li> - <li> - Removed grub_serial*.cfg and libreboot_serial*.rom, all configs/rom files are now unified (containing same configuration as serial rom files from before). - <ul> - <li>Documentation: updated #rom to reflect the above.</li> - </ul> - </li> - <li>Updated GRUB to new version from August 14th, 2014.</li> - <li>Unified all grub configurations for all systems to a single grub.cfg under resources/grub/config/</li> - <li>Updated flashrom to new version from August 20th, 2014</li> - <li> - Added getseabios and builddeps-seabios (builddeps and getall were also updated) - <ul> - <li> - Added instructions to 'buildrom-withgrub' to include bios.bin.elf and vgaroms/vgabios.bin from SeaBIOS inside the ROM. - </li> - </ul> - </li> - <li>Added seabios (and sgavgabios) to grub as payload option in menu</li> - <li> - Disabled serial output in Memtest86+ (no longer needed) to speed up tests. - <ul> - <li>MemTest86+ now works properly, it can output on the laptop screen (no serial port needed anymore).</li> - </ul> - </li> - <li> - Added getgrubinvaders, builddeps-grubinvaders scripts. Added these to getall and builddeps. - <ul> - <li> - Added <a href="http://www.coreboot.org/GRUB_invaders">GRUB Invaders</a> menu entry in resources/grub/config/grub.cfg - </li> - </ul> - </li> - <li>Added rules to builddeps-coreboot to build libpayload with TinyCurses. (added appropriate instructions to cleandeps script).</li> - <li>Commented out lines in resources/grub/config/grub.cfg for loading font/background (not useful anymore, now that GRUB is in text-mode).</li> - <li>Commented out lines in buildrom-withgrub that included backgrounds/fonts (not useful anymore, now that GRUB is in text-mode).</li> - <li> - Added resources/utilities/i945-pwm/ (from git://git.mtjm.eu/i945-pwm), for debugging acpi brightness on i945 systems. - <ul> - <li>Added instructions for it in builddeps, builddeps-i945pwm, builddeb and cleandeps</li> - </ul> - </li> - <li>'build' script: removed the parts that generated sha512sum manifests (not needed, since release tarballs are GPG-signed)</li> - <li> - 'build' script: removed the parts that generated libreboot_meta directory (not needed anymore, since _meta will be hosted in git) - <ul> - <li>Updated #build_meta (and other parts of documentation) to accomodate this change.</li> - </ul> - </li> - <li>Documentation: simplified (refactored) the notes in #rom</li> - <li> - 'build' script: removed the parts that generated libreboot_bin and added them to a new script: 'build-release' - <ul> - <li>Documentation: #build updated to reflect the above.</li> - </ul> - </li> - <li><s>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</s></li> - <li>Added GNUtoo's list of GRUB modules (includes all of the gcry_* modules above), cryptomount should be working now.</li> - <li>Removed builddeb-bucts and builddeb-flashrom, merged them with builddeb ( updated accordingly)</li> - <li>Removed buildpac-bucts and buildpac-flashrom, merged them with buildpac ( updated accordingly)</li> - <li>Renamed buildpac to deps-parabola ( updated accordingly)</li> - <li>Documentation: removed all parts talking about build dependencies, replaced them with links to #build_dependencies</li> - <li>Documentation: emphasized more strongly on the documentation, the need to re-build bucts and/or flashrom before flashing a ROM image.</li> - <li>build-release: flashrom, nvramtool, cbfstool and bucts are no longer provided pre-compiled in binary archives, and are now in source form only. (to maximize distro compatibility).</li> - <li>'build' script: replaced grub.elf assembly instructons, it is now handled by a utility added under resources/utilities/grub-assemble</li> - <li>Moved resources/grub/keymap to resources/utilities/grub-assemble/keymap, and updated that utility to use it</li> - <li>Documentation: removed useless links to pictures of keyboard layouts and unmodified layouts.</li> - <li>Removed all unused fonts from dejavu-fonts-ttf-2.34/ directory</li> - <li>'buildrom-withgrub' script: updated it to create 2 sets of ROMs for each system: one with text-mode, one with coreboot framebuffer.</li> - <li>Documentation: updated #rom to reflect the above</li> - <li>Deleted unused README and COPYING file from main directory</li> - <li>Removed some rm -Rf .git* instructions from the get* scripts and moved them to build-release script</li> - <li> - Split up default grub.cfg into 6 parts: extra/{common.cfg,txtmode.cfg,vesafb.cfg} and menuentries/{common.cfg,txtmode.cfg,vesafb.cfg} - <ul> - <li>buildrom-withgrub script uses these to generate the correct grub.cfg for each type of configuration.</li> - </ul> - </li> - <li>grub_memdisk.cfg (used inside grub.elf) now only loads grub.cfg from cbfs. It no longer enables serial output or sets prefix. (menuentries/common.cfg does instead)</li> - <li> - resources/grub/config/extra/common.cfg, added: - <ul> - <li>insmod instructions to load those modules: nativedisk, ehci, ohci, uhci, usb, usbserial_pl2303, usbserial_ftdi, usbserial_usbdebug</li> - <li>set prefix=(memdisk)/boot/grub</li> - <li> - For native graphics (recommended by coreboot wiki):<br/> - gfxpayload=keep<br/> - terminal_output --append gfxterm - </li> - <li> - Play a beep on startup:<br/> - play 480 440 1 - </li> - </ul> - </li> - <li> - Documentation: updated gnulinux/grub_cbfs.html to make it safer (and easier) to follow. - </li> - </ul> - - <h2> - Corrections to r20140811 (5th beta) (11th August 2014) - </h2> - <ul> - <li>Fixed typo where revision list for 5th beta was listed as March 11th 2014, when in fact it was August 11th 2014</li> - <li>Fixed incorrect grub.cfg that was actually placed in resources/grub/config/x60/grub_usqwerty.cfg which broke the default GRUB menu entry on X60</li> - </ul> - - <h2> - Revisions for r20140811 (5th beta) (11th August 2014) - </h2> - <ul> - <li>build: added 'luks', 'lvm', 'cmosdump' and 'cmostest' to the list of modules for grub.elf</li> - <li>Documentation: added pics showing T60 unbricking (still need to write a tutorial)</li> - <li>build: include cmos.layout (coreboot/src/mainboard/manufacturer/model/cmos.layout) files in libreboot_bin</li> - <li>Documentation: added <b>install/x60tablet_unbrick.html</b></li> - <li>Documentation: added <b>install/t60_unbrick.html</b></li> - <li>Documentation: added <b>install/t60_lcd_15.html</b></li> - <li>Documentation: added <b>install/t60_security.html</b></li> - <li>Documentation: added <b>install/t60_heatsink.html</b></li> - <li>Documentation: Renamed RELEASE.html to release.html</li> - <li>Documentation: removed pcmcia reference in x60_security.html (it's cardbus)</li> - <li>Documentation: added preliminary information about randomized seal (for physical intrusion detection) in x60_security.html and t60_security.html</li> - <li>Documentation: added preliminary information about preventing/mitigating cold-boot attack in x60_security.html and t60_security.html</li> - <li>Documentation: added info to #macbook21 warning about issues with macbook21</li> - <li> - Documentation: X60/T60: added information about checking custom ROMs using dd to see whether or not the top 64K - region is duplicated below top or not. Advise caution about this in the tutorial that deals with flashing on top - of Lenovo BIOS, citing the correct dd commands necessary if it is confirmed that the ROM has not been applied with - dd yet. (in the case that the user compiled their own ROMs from libreboot, without using the build scripts, or if they forgot to use dd, etc). - </li> - <li> - Split resources/libreboot/patch/gitdiff into separate patch files (getcb script updated to accomodate this change). - </li> - <li>Re-added .git files to bucts</li> - <li>Fixed the oversight where macbook21_firstflash wasn't included in binary archives</li> - <li>Release archives are now compressed using .tar.xz for better compression</li> - </ul> - - <h2> - Revisions for r20140729 (4th beta) (29th July 2014) - </h2> - <ul> - <li>Documentation: improved (more explanations, background info) in docs/security/x60_security.html (courtesy of Denis Carikli)</li> - <li>MacBook2,1 tested (confirmed)</li> - <li>macbook21: Added script 'macbook21_firstflash' for flashing libreboot while Apple EFI firmware is running.</li> - <li>Documentation: macbook21: added software-based flashing instructions for flashing libreboot while Apple EFI firmware is running.</li> - <li> - Reduced size of libreboot_src.tar.gz: - <ul> - <li> - Removed .git and .gitignore from grub directory (libreboot_src); not needed. - Removing them reduces the size of the archive (by a lot). GRUB development should be upstream. - </li> - <li> - Removed .git and .gitignore from bucts directory (libreboot_src); not needed. - Removing them reduces the size of the archive. bucts development should be upstream. - </li> - <li> - Removed .svn from flashrom directory (libreboot_src); not needed. - Removing it reduces the size of the archive. flashrom development should be upstream. - </li> - </ul> - </li> - <li> - Added ROMs with Qwerty (Italian) layout in GRUB (libreboot*itqwerty.rom) - </li> - <li> - Added resources/utilities/i945gpu/intel-regs.py for debugging issues related to LCD panel compatibility on X60 Tablet and T60. (courtesy of <a href="http://mtjm.eu">Michał Masłowski</a>) - </li> - </ul> - - <h2> - Revisions for r20140720 (3rd beta) (20th July 2014) - </h2> - <ul> - <li> - Fixed typo that existed in 2nd beta where the release date of the 2nd beta was listed as being in year 2016, when in actual fact it was 2014. - </li> - <li> - Documentation: added (preliminary) details about (rare) buggy CPUs on the ThinkPad T60 that were found to fail (instability, kernel panics, etc) - without the microcode updates. - </li> - <li>Documentation: added docs/hardware/x60_heatsink.html for showing how to change the heatsink on the Thinkpad X60</li> - <li>Added ROM images for Azerty (French) keyboard layout in GRUB (courtesy of Olivier Mondoloni)</li> - <li> - Tidied up some scripts: - <ul> - <li><s>Re-factored those scripts (made easier to read/maintain): build-x60, build-x60t, build-t60, build-macbook21</s></li> - <li><s>Reduced the number of grub configs to 2 (or 1, for macbook21), the build scripts now generate the other configs at build time.</s></li> - <li>Deleted build-x60, build-x60t, build-t60, build-macbook21 and replaced with intelligent (generic) buildrom-withgrub script</li> - <li>Updated build to use buildrom-withgrub script for building the ROM images.</li> - <li>coreboot.rom and coreboot_serial.rom renamed to coreboot_usqwerty.rom and coreboot_serial_usqwerty.rom</li> - <li>coreboot_dvorak and coreboot_serial_dvorak.rom renamed to coreboot_usdvorak.rom and coreboot_serial_usdvorak.rom</li> - <li>Renamed coreboot*rom to libreboot*rom</li> - <li>Made flash, lenovobios_firstflash and lenovobios_secondflash scripts fail if the specified file does not exist.</li> - <li>Updated all relevant parts of the documentation to reflect the above.</li> - </ul> - </li> - <li>Replaced background.png with background.jpg. added gnulove.jpg. (resources/grub/background/)</li> - <li>Updated buildrom-withgrub to use background.jpg instead of background.png</li> - <li>Updated buildrom-withgrub to use gnulove.jpg aswell</li> - <li>Updated resources/grub/config/macbook21/grub*cfg to use gnulove.jpg background.</li> - <li>Updated resources/grub/config/{x60,t60,x60t}/grub*cfg to use background.jpg background.</li> - <li>Documentation: updated docs/#grub_custom_keyboard to be more generally useful.</li> - <li> - nvramtool: - <ul> - <li>Updated builddeps-coreboot script to build it</li> - <li>Updated build script to include it in libreboot_bin</li> - </ul> - </li> - <li> - Documentation: added docs/security/x60_security.html (security hardening for X60) - </li> - </ul> - - <h2> - Revisions for r20140716 (2nd beta) (16th July 2014) - </h2> - <ul> - <li> - Deleted all git-related files from the coreboot directory. This was necessary because - with those it is possible to run 'git diff' which shows the changes made in the form - of a patch (diff format); this includes the blobs that were deleted during deblobbing. - </li> - </ul> - - <h2> - Revisions for r20140711 (1st beta) (11th July 2014) - </h2> - <ul> - <li>Initial release (new coreboot base, dated 1st June 2014. See 'getcb' script for reference)</li> - <li>DEBLOBBED coreboot</li> - <li>Removed the part from memtest86+ 'make' where it tried to connect to some scp server while compiling. (commented out line 24 in the Makefile)</li> - <li>X60 now uses a single .config (for coreboot)</li> - <li>X60 now uses a single grub.cfg (for grub memdisk)</li> - <li>X60 now uses a single grub.elf (payload)</li> - <li>Added new native graphics code for X60 (replaces the old 'replay' code) from Vladimir Serbinenko: 5320/9 from review.coreboot.org</li> - <li>T60 is now supported, with native graphics. (5345/4 from review.coreboot.org, cherry-picked on top of 5320/9 checkout)</li> - <li> - Added macbook2,1 support (from Mono Moosbart and Vladimir Serbinenko) from review.coreboot.org (see 'getcb' script to know how that was done) - <ul> - <li>Documentation: added information linking to correct page and talking about which models are supported.</li> - <li>Added resources/libreboot/config/macbook21config</li> - <li>macbook21: Added 'build-macbook21' script and linked to it in 'build' (ROMs included under bin/macbook21/)</li> - <li>macbook21: Removed dd instructions from build-macbook21 script (macbook21 does not need bucts when flashing libreboot while Apple EFI firmware is running)</li> - <li>Documentation: Added macbook21 ROMs to the list of ROMs in docs/#rom</li> - <li>Documentation: Write documentation linking to Mono Moosbart's macbook21 and parabola page (and include a copy)</li> - </ul> - </li> - <li>Documentation: added a copy of Mono's Parabola install guide (for macbook21 with Apple EFI firmware) and linked in in main index.</li> - <li>Documentation: added a copy of Mono's Coreboot page (for macbook21) and linked it in main index.</li> - <li>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)</li> - <li>macbook21: remove options in build-macbook21 for *serial*.rom (there is no dock or serial port available for macbook21)</li> - <li> - Added patches for backlight controls on X60 and T60 with help from Denis Carikli (see ./resources/libreboot/patch/gitdiff and ./getcb and docs/i945_backlight.html) - <ul> - <li>Documentation: added docs/i945_backlight.html showing how backlight controls were made to work on X60/T60</li> - </ul> - </li> - <li> - Documentation: Added info about getting LCD panel name based on EDID data. - <ul> - <li>Documentation: Added a link to this from the list of supported T60s and LCD panels for T60 (so that the user can check what LCD panel they have).</li> - </ul> - </li> - <li> - X60/T60: Merged patches for 3D fix (from Paul Menzel) when using kernel 3.12 or higher (see ./resources/libreboot/patch/gitdiff and ./getcb) - <ul> - <li>based on 5927/11 and 5932/5 from review.coreboot.org</li> - </ul> - </li> - <li> - Improved thinkpad_acpi support (from coreboot ): xsensors shows more information. - <ul> - <li>From 4650/29 in review.coreboot.org (merged in coreboot 'master' on June 1st 2014)</li> - </ul> - </li> - <li> - Merged changes for digitizer (X60 Tablet) and IR (X60 and T60) based on 5243/17, 5242/17 and 5239/19 from review.coreboot.org - <ul> - <li>(see ./resources/libreboot/patch/gitdiff and ./getcb)</li> - </ul> - </li> - <li>Documentation: added information about building flashrom using 'builddeps-flashrom' script.</li> - <li>Re-created resources/libreboot/config/x60config</li> - <li>Re-created resources/libreboot/config/t60config</li> - <li> - Added 'x60tconfig' in resources/libreboot/config (because X60 Tablet has different information about serial/model/version in 'dmidecode') - <ul> - <li>Added 'build-x60t' script</li> - <li>Updated 'build' script to use 'build-x60t'</li> - <li>Documentation: added to #config section the section #config_x60t (libreboot configuration and dmidecode info)</li> - <li>Documentation: added x60t ROMs to the list of ROMs</li> - </ul> - </li> - <li>Tidied up the 'builddeps' script (easier to read)</li> - <li>Tidied up the 'cleandeps' script (easier to read)</li> - <li>Annotated the 'buildall' script</li> - <li>Added 'getcb' script for getting coreboot revision used from git, and patching it.</li> - <li>Added 'getgrub' script for getting the GRUB revision used from git, and patching it.</li> - <li>Added 'getmt86' script for getting the memtest86+ version used, and patching it.</li> - <li>Added 'getbucts' script for getting the bucts version used.</li> - <li>Added 'getflashrom' script for getting the flashrom version used, and patching it</li> - <li>Added 'getall' script which runs all of the other 'get' scripts.</li> - <li> - Add instructions to the 'build' script to prepare libreboot_meta.tar.gz - <ul> - <li>New archive: libreboot_meta.tar.gz - minimal archive, using the 'get' scripts to download all the dependencies (coreboot, memtest, grub and so on).</li> - </ul> - </li> - <li>Documentation: added information about where 'build' script prepares the libreboot_meta.tar.gz archive.</li> - <li> - Documentation: added information about how to use the 'get' scripts in libreboot_meta.tar.gz (to generate libreboot_src.tar.gz) - <ul> - <li>Documentation: mention that meta doesn't create libreboot_src/ directory, but that libreboot_meta itself becomes the same.</li> - <li>Documentation: advise to rename libreboot_meta to libreboot_src after running 'getall'.</li> - </ul> - </li> - <li>Annotated the 'builddeb' script, to say what each set of dependencies are for.</li> - <li>Separated bucts/flashrom builddeb sections into separate scripts: builddeb-flashrom, builddeb-bucts.</li> - <li>Documentation: Updated relevant parts based on the above.</li> - <li>Added instructions to 'build' script for including builddeb-bucts and builddeb-flashrom in libreboot_bin</li> - <li> - Updated flashrom checkout (r1822 2014-06-16) from SVN (http://flashrom.org/Downloads). - <ul> - <li>Updated flashing instructions in docs/ for new commands needed (Macronix chip on X60/T60)</li> - <li>For X60/T60 (flashrom): Patched flashchips.c_lenovobios_macronix and flashchips.c_lenovobios_sst executables for SST/macronix (included in resources/flashrom/patch)</li> - <li>Updated builddeps to build flashrom_lenovobios_sst and flashrom_lenovobios_macronix, for X60/T60 users with Lenovo BIOS</li> - <li>moved the flashrom build instructions from 'builddeps' and put them in 'builddeps-flashrom', excecuting that from 'builddeps'.</li> - <li>Added builddeps-flashrom to libreboot_bin.tar.gz</li> - </ul> - </li> - <li> - flashrom: added patched flashchips.c to resources/flashrom/patch (automatically use correct macronix chip on libreboot, without using '-c' switch) - <ul> - <li>removed 'MX25L1605' and 'MX25L1605A/MX25L1606E' entries in flashchips.c for the patched version of flashchips.c</li> - <li>added instructions to 'builddeps-flashrom' to automatically use this modified flashchips.c in the default build</li> - </ul> - </li> - <li>Added builddeb to libreboot_bin.tar.gz</li> - <li> - Moved 'bucts' build instructions from builddeps to builddeps-bucts - <ul> - <li>builddeps now runs 'builddeps-bucts' instead</li> - <li>Added 'builddeps-bucts' to libreboot_bin.tar.gz</li> - <li>Documentation: Added information about using 'builddep-bucts' to build the BUC.TS utility.</li> - </ul> - </li> - <li> - Added 'lenovobios_firstflash' and 'lenovobios_secondflash' scripts - <ul> - <li>Added instructions to 'build' script for including those files in libreboot_bin</li> - <li>Documentation: Add tutorial for flashing while Lenovo BIOS is running (on X60/T60)</li> - </ul> - </li> - <li> - Added 'flash' script (make sure to run builddeps-flashrom first) which (while libreboot is already running) can use flashrom to flash a ROM - <ul> - <li>eg: "sudo ./flash bin/x60/coreboot_serial_ukdvorak.rom" equivalent to "sudo ./flashrom/flashrom -p internal -w bin/x60/coreboot_uk_dvorak.rom"</li> - <li>updated 'build' script to include the 'flash' script in libreboot_bin.tar.gz</li> - </ul> - </li> - <li>Documentation: replaced default flashrom tutorial to recommend the 'flash' script instead.</li> - <li> - Re-add cbfstool source code back into libreboot_bin.tar.gz, as cbfstool_standalone - <ul> - <li>Patched that version to work (able to be built and used) without requiring the entire coreboot source code.</li> - <li> - Created patched version of the relevant source files and added it into resources/cbfstool/patch - <ul> - <li>see coreboot/util/cbfstool/rmodule.c and then the patched version in resources/cbfstool/patch/rmodule.c</li> - <li>see coreboot/src/include/rmodule-defs.h and the rule in 'build' for including this in ../libreboot_bin/cbfstool_standalone</li> - </ul> - </li> - <li>Added instructions to 'build' script for applying this patch to the cbfstool_standalone source in libreboot_bin</li> - <li>Added instructions to 'build' script for then re-compiling cbfstool_standalone in libreboot_bin after applying the patch</li> - <li>Added a 'builddeps-cbfstool' script (in src, but only used in bin and put in bin by 'build') that compiles cbfstool_standalone in libreboot_bin (make), moves the cbfstool and rmodtool binaries into libreboot_bin/ and then does 'make clean' in libreboot_bin/cbfstool_standalone</li> - <li>Updated the 'build' script to put 'builddeps-cbfstool' in libreboot_bin</li> - <li>Updated the 'build' script in the cbfstool (standalone) part to accomodate the above.</li> - <li>Documentation: added notes about cbfstool (standalone) in libreboot_bin</li> - </ul> - </li> - <li>Documentation: made docs/gnulinux/grub_cbfs.html slightly easier to follow.</li> - <li>Annotate the 'build*' scripts with 'echo' commands, to help the user understand what it actually happening during the build process.</li> - <li> - Documentation: added information about how 'dmidecode' data was put in the coreboot configs - <ul> - <li>Documentation: In fact, document how the 'config' files in resources/libreboot/config/ were created</li> - </ul> - </li> - <li>Documentation: Added information about which ThinkPad T60s are supported, and which are not.</li> - <li> - Documentation: added information about LCD inverters (for upgrading the LCD panel on a T60 14.1' XGA or 15.1' XGA) - <ul> - <li>it's FRU P/N 41W1478 (on T60 14.1") so this was added to the docs.</li> - <li>it's P/N 42T0078 FRU 42T0079 or P/N 41W1338 (on T60 15.1") so this was added to the docs.</li> - </ul> - </li> - <li>Documentation: added information about names of LCD panels for T60 to the relevant parts of the documentation.</li> - <li>Documentation: added information (with pictures) about the differences between T60 with Intel GPU and T60 with ATI GPU.</li> - <li>Documentation: added pictures of keyboard layouts (US/UK Qwerty/Dvorak) to the ROM list, to let the user compare with their own keyboard.</li> - <li> - Move the coreboot build instructions in 'builddeps' into 'builddeps-coreboot' and link it in 'builddeps' - <ul> - <li>Link to 'builddeps-coreboot' in final stage of 'getcb'</li> - </ul> - </li> - <li> - Move GRUB build instructions from 'builddeps' into 'builddeps-grub', link from 'builddeps' - <ul> - <li>Link to 'builddeps-grub' in final stage of 'getgrub'</li> - </ul> - </li> - <li> - Move MemTest86+ build instructions from 'builddeps' into 'builddeps-memtest86', link from 'builddeps' - <ul> - <li>Link to 'builddeps-memtest86' in final stage of 'getmt86'</li> - </ul> - </li> - <li>made 'build' script put resources/ directory in libreboot_bin, to make builddeps-flashrom work in libreboot_bin</li> - <li>Removed instructions for building source code in the 'get' script (they don't really belong there)</li> - <li>Added libfuse-dev and liblzma-dev to the list of GRUB dependencies in 'builddeb' script.</li> - <li>Converted the 'RELEASE' file to 'docs/RELEASE.html'</li> - <li>Added those dependencies to builddeb script (for GRUB part): gawk libdevmapper-dev libtool libfreetype6-dev</li> - <li>Added to build script the instruction at the end to create a sha512sum.txt with a file manifest plus checksums.</li> - <li>Deleted the RELEASE and BACKPORT files (no longer needed)</li> - <li> - Documentation: added information about X60/T60 dock (ultrabase x6 and advanced mini dock) to relevant sections. - <ul> - <li>Added to docs/#serial</li> - </ul> - </li> - </ul> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="release20140622">Release 20140622 (5th release)</h1> - - <ul> - <li>7th March 2014</li> - <li>revised 22nd June 2014</li> - </ul> - - <h2>Officially supported</h2> - <ul> - <li>ThinkPad X60</li> - <li>ThinkPad X60s</li> - </ul> - - <h2>Revision (22nd June 2014 - extra)</h2> - <ul> - <li>Documentation: added X60 Unbricking tutorial</li> - <li>Documentation: added info about enabling or disabling wifi</li> - <li>Documentation: added info about enabling or disabling trackpoint</li> - </ul> - - <h2>Revision (22nd June 2014 - extra)</h2> - <ul> - <li>Documentation: Improved the instructions for using flashrom</li> - <li>Documentation: Improved the instructions for using cbfstool (to change the default GRUB menu)</li> - <li>Documentation: Numerous small fixes.</li> - </ul> - - <h2>Revision notes (22nd June 2014)</h2> - <ul> - <li>updated GRUB (git 4b8b9135f1676924a8458da528d264bbc7bbb301, 20th April 2014)</li> - <li>Made "DeJavu Sans Mono" the default font in GRUB (fixes border corruption).</li> - <li>re-added background image in GRUB (meditating GNU)</li> - <li> - added 6 more images: - <ul> - <li>coreboot_ukqwerty.rom (UK Qwerty keyboard layout in GRUB)</li> - <li>coreboot_serial_ukqwerty.rom (UK Qwerty keyboard layout in GRUB)</li> - <li>coreboot_dvorak.rom (US Dvorak keyboard layout in GRUB)</li> - <li>coreboot_serial_dvorak.rom (US Dvorak keyboard layout in GRUB)</li> - <li>coreboot_ukdvorak.rom (UK Dvorak keyboard layout in GRUB)</li> - <li>coreboot_serial_ukdvorak.rom (UK Dvorak keyboard layout in GRUB)</li> - <li>(coreboot.rom and coreboot_serial.rom have US Qwerty keyboard layout in GRUB, as usual)</li> - </ul> - </li> - <li> - improved the documentation: - <ul> - <li>removed FLASH_INSTRUCTION and README.powertop and merged them with README</li> - <li>removed obsolete info from README and tidied it up</li> - <li>deleted README (replaced with docs/)</li> - </ul> - </li> - <li>tidied up the menu entries in GRUB</li> - <li>tidied up the root directory of X60_source/, sorted more files into subdirectories</li> - <li>improved the commenting inside the 'build' script (should make modifying it easier)</li> - <li>Renamed X60_binary.tar.gz and X60_source.tar.gz to libreboot_bin.tar.gz and libreboot_src.tar.gz, respectively.</li> - <li>Replaced "GNU GRUB version" with "FREE AS IN FREEDOM" on GNU GRUB start screen.</li> - <li>Added sha512.txt files in libreboot_src and libreboot_bin. (inside the archives)</li> - <li>Added libreboot_bin.tar.gz.sha512.txt and libreboot_src.tar.gz.sha512.txt files (outside of the archives)</li> - </ul> - - <h2>Revision notes (11th June 2014):</h2> - <ul> - <li>removed 'CD' boot option from coreboot.rom (not needed)</li> - <li>removed 'processor.max_cstate=2' and 'idle=halt' options (see README.powertop file)</li> - </ul> - - <h2>Revision notes (5th June 2014):</h2> - <ul> - <li>added backlight support (Fn+Home and Fn+End) on X60</li> - <li>fixed broken/unstable 3D when using kernel 3.12 or higher</li> - <li>(see 'BACKPORT' file)</li> - </ul> - - <h2>Revision notes (9th March 2015):</h2> - <ul> - <li>recreated coreboot config from scratch</li> - <li>GRUB loads even faster now (less than 2 seconds).</li> - <li>Total boot time reduced by further ~5 seconds.</li> - <li>Added crypto and cryptodisk modules to GRUB</li> - <li>cbfstool now included in the binary archives</li> - </ul> - - <h2>Development notes</h2> - <ul> - <li> - Binary archive now have 2 images: - <ul> - <li>With serial output enabled and memtest86+ included (debug level 8 in coreboot)</li> - <li>With serial output disabled and memtest86+ excluded (faster boot speeds) (debugging disabled)</li> - </ul> - </li> - <li> - Reduced impact on battery life: - <ul> - <li>'processor.max_cstate=2' instead of 'idle=halt' for booting default kernel</li> - </ul> - </li> - <li> - coreboot.rom (faster boot speeds, debugging disabled): - <ul> - <li>Disabled coreboot serial output (Console-> in "make menuconfig")</li> - <li>Set coreboot debug level to 0 instead of 8 (Console-> in "make menuconfig")</li> - <li>Changed GRUB timeout to 1 second instead of 2 (in grub.cfg</li> - <li>Removed background image in GRUB.</li> - <li>Removed memtest86+ payload (since it relies on serial output) - </ul> - </li> - <li> - coreboot_serial.rom (slower boot speeds, debugging enabled): - <ul> - <li>Boot time still reduced, but only by ~2 seconds</li> - <li>has the memtest86+ payload included in the ROM</li> - <li>has serial port enabled. How this is achieved (from X60_source): Turn on debugging level to 8, and enable serial output</li> - </ul> - </li> - <li>(in Console-> in coreboot "make menuconfig")</li> - <li>(and build with grub_serial.cfg and grub_memdisk_serial.cfg)</li> - </ul> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="release20140221">Release 20140221 (4th release)</h1> - - <ul> - <li>21st February 2014</li> - </ul> - - <h2>Officially supported</h2> - <ul> - <li>ThinkPad X60</li> - <li>ThinkPad X60s</li> - </ul> - - <h2>Development notes</h2> - <ul> - <li>Removed SeaBIOS (redundant)</li> - <li> - New GRUB version (2.02~beta2) - <ul> - <li>Fixes some USB issues</li> - <li>Includes ISOLINUX/SYSLINUX parser</li> - </ul> - </li> - <li>New grub.cfg</li> - <li> - Removed useless options: - <ul> - <li>options for booting sda 2/3/4</li> - <li>seabios boot option</li> - </ul> - </li> - <li> - Added new menu entries: - <ul> - <li>Parse ISOLINUX config (USB)</li> - <li>Parse ISOLINUX config (CD)</li> - <li>Added 'cat' module for use on GRUB command line.</li> - </ul> - </li> - <li>"set pager=1" is set in grub.cfg, for less-like functionality</li> - </ul> - <p> - 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. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="release20131214">r20131214 (3rd release)</h1> - - <ul> - <li>14th December 2013</li> - </ul> - - <h2>Supported:</h2> - <ul> - <li>ThinkPad X60</li> - <li>ThinkPad X60s</li> - </ul> - - <h2>Development notes</h2> - <ul> - <li>Added SeaBIOS payload to GRUB2 (for booting USB drives)</li> - <li>new grub.cfg</li> - </ul> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="release20131213">r20131213 (2nd release)</h1> - - <ul> - <li>13th December 2013</li> - </ul> - - <h2>Supported:</h2> - <ul> - <li>ThinkPad X60</li> - <li>ThinkPad X60s</li> - </ul> - - <h2>Development notes</h2> - <ul> - <li>added background image to GRUB2</li> - <li>added memtest86+ payload to grub2</li> - <li>improvements to the documentation</li> - <li>new grub.cfg</li> - </ul> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="release20131212">r20131212 (1st release)</h1> - - <ul> - <li>12th December 2013</li> - </ul> - - <h2>Supported:</h2> - <ul> - <li>ThinkPad X60</li> - <li>ThinkPad X60s</li> - </ul> - - <h2>Development notes</h2> - <ul> - <li>initial release</li> - <li>source code deblobbed</li> - </ul> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="cc-by-sa-4.0.txt">cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/archive_old.md b/docs/archive_old.md new file mode 100644 index 00000000..c68513d6 --- /dev/null +++ b/docs/archive_old.md @@ -0,0 +1,1402 @@ +<div class="section"> + +Libreboot release information (old) {#pagetop} +=================================== + +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/). + +<div class="important"> + +**This page is \*obsolete\*, provided for historical purposes.** + +</div> + +</div> + +<div class="section"> + +Releases +-------- + +- [r20150518 (18th May 2015)](#release20150518) +- [r20150124 (24th January 2015), r20150126 (26th January 2015), + r20150208 (8th February 2015)](#release20150124) +- [r20141015 (15th October 2014)](#release20141015) +- [r20140911 (6th release)](#release20140911) (11th September 2014 + **pre-release, 7th beta**) +- [r20140622 (5th release)](#release20140622) (7th March 2014, revised + 22nd June 2014) +- [r20140221 (4th release)](#release20140221) (21st February 2014) +- [r20131214 (3rd release)](#release20131214) (14th December 2013) +- [r20131213 (2nd release)](#release20131213) (13th December 2013) +- [r20131212 (1st release)](#release20131212) (12th December 2013) + +</div> + +<div class="section"> + +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***. + +Machines supported in this release: +----------------------------------- + +- **ThinkPad X60/X60s** + - You can also remove the motherboard from an X61/X61s and replace + it with an X60/X60s motherboard. An X60 Tablet motherboard will + 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 + 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 + panels. + - It is unknown whether a T61 can have it\'s mainboard replaced + with a T60 motherboard. + - See ***docs/future/\#t60\_cpu\_microcode***. + - T60P (and T60 laptops with ATI GPU) will likely never be + supported: ***docs/hcl/\#t60\_ati\_intel*** +- **ThinkPad X200** + - X200S and X200 Tablet are also supported, conditionally; see + ***docs/hcl/x200.html\#x200s*** + - **ME/AMT**: libreboot removes this, permanently. + ***docs/hcl/gm45\_remove\_me.html*** +- **ThinkPad R400** + - See ***docs/hcl/r400.html*** + - **ME/AMT**: libreboot removes this, permanently. + ***docs/hcl/gm45\_remove\_me.html*** +- **ThinkPad T400** + - See ***docs/hcl/t400.html*** + - **ME/AMT**: libreboot removes this, permanently. + ***docs/hcl/gm45\_remove\_me.html*** +- **ThinkPad T500** + - See ***docs/hcl/t500.html*** + - **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***. +- **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, + MB063LL/A, MB062LL/A) + - See ***docs/hcl/\#macbook21***. + +Changes for this release, relative to r20150208 (earliest changes last, recent changes first) +--------------------------------------------------------------------------------------------- + +- Add a whitelist entry to board\_enable.c in flashrom, for the + ThinkPad R400, T400 and T500 +- Updated flashrom (to SVN revision 1889) + - X200 whitelist patch removed (merged upstream) + - X200 whitelist modified to include X200S and X200 Tablet +- libreboot\_util: don\'t include cmos layout files (not needed + anymore) +- **coreboot-libre: backport patches for X200 Tablet digitizer + support** +- build/release/archives: create SHA512 sum manifest file of the + release archives +- build/release/archives: separate crossgcc into a new archive +- disabled generation of txtmode ROM images for now (they will be back + 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 + length - it was arbitrary and pointless. +- docs/maintain/: Finish the guide +- scripts/download/coreboot: use diffs included in libreboot, not + external gerrit cherry-picks - review.coreboot.org (gerrit) being + down no longer kills libreboot (backup mirrors of the master + repository exist) +- docs/install/bbb\_setup.html: Add info about wp/hold and pinouts +- docs/: improve the description of libreboot +- docs/hcl/gm45\_remove\_me.html: notes about the demefactory utility +- docs/install/bbb\_setup.html: EHCI debug: recommend linux-libre +- docs/install/bbb\_setup.html: EHCI Debug logging setup guide +- docs/hcl/t500.html: Add screen compatibility report (TODO: fix + incompatible screens) +- Update coreboot(again) + merge GM45 hybrid GPU patches - means that + T400/T500 with the ATI+Intel hybrid GPU setup will work (ATI + disabled, Intel permanently enabled). power\_on\_after\_fail nvram + option added to all GM45 boards, defaulting to No, so that plugging + it AC doesn\'t boot up the system against the users will. Net20DC is + now the default debug dongle on all boards (compatible with BBB). +- 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/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 +- docs/gnulinux/grub\_boot\_installer.html: Fix hazardous instruction +- 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/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 + ME +- docs/install/{t400,t500,r400}\_external.html: Notes about CPU + compatibility +- Delete the ich9macchange script. It\'s useless, and confuses people +- docs/hcl/gm45\_remove\_me.html: prioritize ich9gen executable path +- docs/hcl/gm45\_remove\_me.html: prioritize changing mac address +- docs/hcl/gm45\_remove\_me.html: less confusing notes about ich9gen +- build/dependencies/parabola: Add dependencies for x86\_64 +- scripts/dependencies/paraboladependencies: build dependencies + (32-bit Parabola) +- **New board**: ThinkPad T500 +- Add diffs for descriptor/gbe differences between T500 and X200 +- coreboot-libre: provide better blob categorization +- docs/hcl/gm45\_remove\_me.html: add notes about flash write protect +- **New board**: ThinkPad T400 +- GRUB: add partial vesamenu.c32 support (fixes tails ISOLINUX menu) +- Update GRUB (to revision fa07d919d1ff868b18d8a42276d094b63a58e299) +- Update coreboot (to revision + 83b05eb0a85d7b7ac0837cece67afabbdb46ea65) + - Intel CPU microcode (most of it) no longer deleted, because it + was deleted upstream (moved to a 3rd party repository). + - MacBook2,1 cstate patch is no longer cherry picked (merged + upstream) + - Patch to disable use of timestamps in coreboot no longer + 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 + blobs) +- coreboot-libre: add GPLv3 license to the findblobs script +- coreboot-libreboot: don\'t rm raminit\_tables (nahelem/sandybridge) + (they are not blobs) +- coreboot-libre: don\'t delete the .spd.hex files (they are not + blobs) +- build/release/archives: don\'t put rmodtool in libreboot\_util +- docs/install/x200\_external.html: recommend installing GNU+Linux at + the end +- docs/install/x200\_external.html: add more photos, improve + instructions +- build/clean/grub: use distclean instead of clean +- grub-assemble: Add the *bsd* and *part\_bsd* modules +- build/roms/withgrub: Only run ich9gen if gm45/gs45 images exist +- docs/git/: Add notes about building for specific boards +- build/roms/withgrub: Allow building for a custom range of boards +- grub-assemble: Disable verbose output +- Add documentation on how to unlock root encrypted fs with key in + initramfs in Parabola Linux +- docs/gnulinux/grub\_cbfs.html: Improve structure (easier to use) +- grub.cfg: Disable the beep on startup +- docs/install/bbb\_setup.html: Make the guide easier to use +- docs/gnulinux/grub\_cbfs.html: Remove redundant instructions +- docs/install/x200\_external.html: Mark pins in the images +- docs/install/bbb\_setup.html: Replace 3.3V PSU photo with ATX PSU +- docs/hcl/x200.html: Add dumps from 4-MiB X200 with Lenovo BIOS 3.22 +- docs/hcl/x200.html: Add dumps from 4-MiB X200 with Lenovo BIOS 3.18 +- grub.cfg: add syslinux\_configfile menuentry for ahci0 +- grub.cfg: Add more paths for syslinux\_configfile +- docs/future.html: T60: Add EDID dump from LG-Philips LP150E05-A2K1 +- docs/install/bbb\_setup.html: Further clarify which clip is needed +- bash scripts: Make script output more user-friendly in general +- bash scripts: Only enable verbose output if DEBUG= is used +- build: Support multiple extra options - now possible to build + multiple images for arbitrary boards (configs), but without building + the entire collection. +- Deleted the signing archive key - the finger print and ID is given + instead, so that the user can download it from a key server +- scripts/helpers/build/release: Move docs to separate archive - + reduces the size of the other archives considerably +- Move DEBLOB to resources/utilities/coreboot-libre/deblob +- scripts/helpers/build/release: Delete DEBLOB from libreboot\_src/ - + not needed in libreboot\_src (release archive) because it contains a + coreboot revision that has already been deblobbed. +- flash (script): Use *build* instead of *DEBLOB* to know if in src +- docs/install/r400\_external.html: Show images, don\'t link. +- docs/install/x200\_external.html: Show images, don\'t link. +- docs/install/bbb\_setup.html: Show images, instead of linking +- Documentation: optimize all images (reduce file sizes) +- Remove download links from the release page (and the archive page) - + release archives are hosted differently following this release, + which means that the old methods are no longer viable. +- Moved ich9macchange to resources/scripts/misc/ich9macchange +- ich9macchange: assume that the script is being run from \_util (act + only on one ROM image, defined by a user-provided path) +- Move grub-background to resources/scripts/misc/grub-background +- grub-background: assume that it is being run from libreboot\_util +- grub-background: change only one ROM image, specified by path +- build (release archives): Add the commitid file to release/ +- build-release: Move the release archives to release/ +- Merge all build scripts into a single generic script, with helpers + in resources/scripts/helpers/build/ +- Replace *getall* with *download*, which takes as input an argument + specifying which program the user wants to download. +- Moved the get scripts to resources/scripts/helpers/download/ +- build-release: Remove the powertop entries +- Documentation: general improvements to the flashing instructions +- Merged all flashing scripts into a single script +- Updated GRUB +- bucts: Make it build without git +- Moved dejavu-fonts-ttf-2.34/AUTHORS to resources/grub/font/ +- Deleted GRUB Invaders from libreboot +- Deleted SeaBIOS from libreboot +- build-release: optimize use of tar (reduced file sizes) +- grub.cfg: add another SYSLINUX config location + (/syslinux/syslinux.cfg) +- build-release: remove the bin/ directory from libreboot\_util +- cleandeps: delete the bin/ directory +- buildrom-withgrub: create the bin directory if it does not exist +- coreboot-libre: don\'t use git for version timestamp +- i945-pwm: add clean command to Makefile +- i945-pwm: add -lz to Makefile +- docs/install/x200\_external: Mention GPIO33 non-descriptor mode +- docs/hcl/: Remove redundant links +- ich9macchange: Add R400 +- build-release: Separate ROM images into individual archives +- build-release: rename libreboot\_bin to libreboot\_util +- **New board:** ThinkPad R400 support added to libreboot. +- bbb\_setup.html: tell user to use libreboot\'s own flashrom + +</div> + +<div class="section"> + +Release 20150124, 20150126 and 20150208 {#release20150124} +======================================= + +Release date: 24th January 2015. + +Machines supported in this release: +----------------------------------- + +- **Lenovo ThinkPad X60/X60s** + - You can also remove the motherboard from an X61/X61s and replace + it with an X60/X60s motherboard. An X60 Tablet motherboard will + 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 + 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. + - It is unknown whether a T61 can have it\'s mainboard replaced + with a T60 motherboard. + - See **future/\#t60\_cpu\_microcode**. + - T60P (and T60 laptops with ATI GPU) will likely never be + supported: **hcl/\#t60\_ati\_intel** +- **Lenovo ThinkPad X200** + - X200S and X200 Tablet are also supported, conditionally; see + **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**. +- **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, + MB063LL/A, MB062LL/A) + - See **hcl/\#macbook21**. + +Revisions for r20150208 (relative to r20150126) +----------------------------------------------- + +This is a maintenance release (polishing) based on r20150126. Users who +installed r20150126 don\'t really need to update to this release. + +- buildrom-withgrub: use gnulove.jpg background on 16:10 laptops + (MacBook2,1 and X200) +- build-release: include grub-background script in libreboot\_bin +- grub-background (new): lets user change GRUB background image +- grub-assemble: Add link to original utility. +- buildrom-withgrub: Put background.jpg in CBFS, not GRUB memdisk +- grub-assemble: merge scripts into a single script gen.sh +- Documentation: implement theme, drastically improve readability +- docs/hcl/: update list of compatible T60 LCD panels +- docs/: more clarification of libreboot\'s stated purpose. +- build-release: include the commitid file in the release archives +- docs/: Further emphasize the GNU+Linux requirement. +- lenovobios\_firstflash: fix BASH errors +- lenovobios\_secondflash: fix BASH errors +- docs/install/x200\_external.html: Tell user to switch MAC address. +- docs/git/: Add to the list of x86\_64 compatible hosts. +- docs/install/: Remove old (obsolete) information. +- docs/git/: Say that the build dependencies are for src (and not + nedeed for libreboot\_bin) +- build: re-factor the descriptor/gbe generating loop for GM45/ICH9M +- X60, X60S and X60 Tablet now the same ROM images. +- Add QEMU (q35/ich9) support to libreboot. +- Add QEMU (i440fx/piix4) support to libreboot +- docs/: Re-write the description of what libreboot is. +- docs/release.html: Add notes about how to use GPG. +- build-release: delete the commitid file from release archives +- build-release: create file named commitid after build-release + +Revisions for r20150126 (relative to r20150124) +----------------------------------------------- + +This is a bug fix release based on r20150124. It contains a few small +changes: + +- grub.cfg: hardcode the list of partitions to search (speeds up + booting considerably. GRUB regexp isn\'t very well optimized) +- Docs (x200.html hcl): Remove incorrect information +- Documentation (bbb\_setup.html): Fix typos +- build-release: delete ich9fdgbe\_{4m,8m}.bin files from ich9gen + - These were accidentically included in the r20150124 release. + They are generated from ich9gen so it\'s ok, but they don\'t + need to be in the archive. +- Documentation (grub\_cbfs.html): Looping in libreboot\_grub.cfg (Add + notes about it if the user copied from grub.cfg in CBFS.) + +Changes for this release (latest changes first, earliest changes last) +---------------------------------------------------------------------- + +- grub.cfg: Added (ahci1) to list of devices for ISOLINUX parser + (CD/DVD) (this is needed for the X200 docking station). +- grub.cfg: ISOLINUX parsing is now done on all USB partitions. +- grub.cfg: Automatically switched to /boot/grub/libreboot\_grub.cfg + on a partition, if it exists. +- libreboot\_bin: added static ARM binaries for flashrom, cbfstool, + ich9gen and ich9deblob (tested on beaglebone black). +- Flashrom: removed redundant Macronix flashchip definitions (for X200 + owners). +- Flashrom: added whitelist for ThinkPad X200. +- X200: fixed uneven backlight (at low levels) +- ich9macchange (new script, uses ich9gen): for changing the default + MAC address on X200 ROM images. +- ich9gen: added capability to change the default MAC address (and + update the checksum) +- ich9deblob: added new utility ich9gen: this can generate a + descriptor+gbe image without a factory.rom dump present. +- Modified ich9deblob to use a struct for Gbe, documenting everything. +- Massively updated the ich9deblob utility: re-factored everything + completely. +- Enabled cstates 1 and 2 on macbook21. This reduces idle heat / power + consumption. +- buildrom-withgrub: disabled creation of \*txtmode\*.rom for X200 + (only framebuffer graphics work) +- Updated SeaBIOS (again) +- docs/install/\#flashrom\_x200: improve instructions +- Updated flashrom (again) - patches updated +- Updated GRUB (again) +- Updated coreboot (again) +- build-release: not all files were copied to libreboot\_src. fix + that. +- build-release: include cbmem (statically compiled) in libreboot\_bin +- Documentation (X200): added software-based flashing instructions +- Documentation: remove all references to the bus pirate (replaced + with BBB flashing tutorials) +- **New board:** ThinkPad X200S and X200 Tablet support added to + libreboot +- build: automatically find board names (configs) to build for +- **New board:** ThinkPad X200 support added to libreboot +- coreboot-libre config (all boards): enable USB dongle log output + (for BeagleBone Black) +- cleandeps: actually clean grubinvaders +- .gitignore: add powertop directory +- cleandeps: clean i945-pwm utility +- scripts (all): fix typos +- Documentation: general cleanup. +- builddeps-flashrom: reduce build commands to a single for loop +- scripts (all): replace unnecessary rm -Rf with rm -f +- docs/release.html: add lenovo g505s to the list of candidates +- .gitignore: add libreboot\_bin.tar.xz and libreboot\_src.tar.xz +- libreboot\_bin.tar.xz: Include utils as statically linked binaries + - This means that the user does not have to install build + dependency or build from source anymore. +- deps-parabola (removed) Remove Parabola dependencies script. Will + re-add later (properly tested) +- grub.cfg: Add more path checks to isolinux parser (more ISOs should + work now) +- Update SeaBIOS +- x60flashfrom5 (new), for X60 users upgrading from 5th/early release +- Update flashrom +- Update GRUB +- Updated coreboot-libre + - i945: permanently set tft\_brightness to 0xff (fixes bug on X60 + where turning up brightness at max would make it loop back to + low brightness) +- getcb: Revert X60/T60 to legacy backlight controls + - The ACPI brightness patches were abandoned and obsolete. +- grub.cfg: Only load initrd.img if it exists. Add rw to linux line + (for ProteanOS) +- 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.vesafb.sh: Use GNU BASH +- scripts (error handling): Replace exit with exit 1 (make debugging + easier) +- Move most files in CBFS to GRUB memdisk, except grub.cfg and + grubtest.cfg +- docs/release.html Add DMP vortex86ex to list of candidates. +- docs/release.html Add ThinkPad X201 to list of candidates. +- New links added to docs/security/x60\_security and + docs/security/t60\_security +- lenovobios\_secondflash: Warn if BUCTS is not present. (not a + dealbreaker. Can just pull out nvram battery/coin). +- lenovobios\_firstflash: Fail if BUCTS fails. (anti-bricking + precaution) +- Removed obnoxious warnings from flashing scripts, improved + documentation instead. +- scripts (all): add proper error checking (fail fast, fail early. Do + not continue if there are errors) +- buildrom-withgrub: rename image to boardname\_layout\_romtype.rom +- buildrom-withgrub: don\'t move cbfstool, execute directly +- resources/utilities/grub-assemble: add French Dvorak (BEPO) keyboard + layout. +- Documentation: add docs/hardware/x60\_keyboard.html (show how to + replace keyboard on X60/X60T) +- Documentation: major cleanup (better structure, easier to find + things) +- docs/release.html: Remove Acer CB5 from list of future candidates. + - Too many issues. Chromebooks are crippled (soldered + RAM/storage/wifi) and have too many usability issues for the + libreboot project. +- docs/gnulinux/grub\_cbfs.html Major cleanup. Usability improvements. +- flash (flashrom script): remove boardmismatch=force + - This was put there before for users upgrading from libreboot r5 + to r6, but also allows the user to flash the wrong image. For + example, the user could flash a T60 image on an X60, thus + bricking the system. It\'s almost certain that most people have + upgraded by now, so remove this potentially dangerous option. +- Documentation: update compatibility list for X60T LCD panels. +- docs/release.html: add note about X60 Tablet board in X60/X60s +- docs/howtos/grub\_boot\_installer.html: small corrections +- docs/howtos/grub\_boot\_installer.html: improved readability, fixed + html errors +- Documentation (macbook21 related): clean up + +</div> + +<div class="section"> + +Release 20141015 {#release20141015} +================ + +Machines supported in this release: +----------------------------------- + +- **Lenovo ThinkPad X60/X60s** + - You can also remove the motherboard from an X61/X61s and replace + it with an X60/X60s motherboard. An X60 Tablet motherboard will + 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 + 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. + - It is unknown whether a T61 can have its mainboard replaced with + a T60 motherboard. + - See **future/\#t60\_cpu\_microcode**. + - T60P (and T60s with ATI GPU) will likely never be supported: + **hcl/\#t60\_ati\_intel** +- **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) + - See **hcl/\#macbook11**. +- **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, + MB063LL/A, MB062LL/A) + - See **hcl/\#macbook21**. + +Changes for this release (latest changes first, earliest changes last) +---------------------------------------------------------------------- + +- Updated coreboot (git commit + 8ffc085e1affaabbe3dca8ac6a89346b71dfc02e), the latest at the time of + writing. +- Updated SeaBIOS (git commit + 67d1fbef0f630e1e823f137d1bae7fa5790bcf4e), the latest at the time of + writing. +- Updated Flashrom (svn revision 1850), the latest at the time of + writing. +- Updated GRUB (git commit 9a67e1ac8e92cd0b7521c75a734fcaf2e58523ad), + the latest at the time of writing. +- Cleaned up the documentation, removed unneeded files. +- ec/lenovo/h8 (x60/x60s/x60t/t60): Enable + wifi/bluetooth/wwan/touchpad/trackpoint by default. +- Documentation: Updated list of T60 LCDs (Samsung LTN150XG 15\" XGA + listed as non-working). +- builddeps-coreboot: Don\'t build libpayload (not needed. This was + leftover by mistake, when trying out the TINT payload). +- Replaced most diff files (patches) for coreboot with gerrit + checkouts (cherry-pick). +- Documentation: x60\_security.html and t60\_security.html: added + links to info about the ethernet controller (Intel 82573). +- Documentation: x60\_security.html and t60\_security.html: added + notes about DMA and the docking station. +- Documentation: configuring\_parabola.html: basic post-install steps + for Parabola GNU+Linux (helpful, since libreboot development is + being moved to Parabola at the time of writing). +- builddeps-coreboot: use \'make crossgcc-i386\' instead of \'make + crossgcc\'. Libreboot only targets x86 at the time of writing. +- ROM images no longer include SeaBIOS. Instead, the user adds it + afterwards. Documentation and scripts updated. +- docs/images/encrypted\_parabola.html: Notes about linux-libre-grsec +- Documentation: encrypted\_parabola.html: add tutorial for encrypted + Parabola GNU+Linux installation. +- Documentation: added more info about wifi chipsets + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +6th release (pre-release, 7th beta) {#release20140911} +=================================== + +- Released 11th July 2014 (pre-release) 1st beta +- Revised (pre-release, 2nd beta) 16th July 2014 +- Revised (pre-release, 3rd beta) 20th July 2014 +- Revised (pre-release, 4th beta) 29th July 2014 +- Revised (pre-release, 5th beta) 11th August 2014 (corrected 11th + August 2014) +- Revised (pre-release, 6th beta) 3rd September 2014 +- Revised (pre-release, 7th beta) 11th September 2014 + +Machines still supported (compared to previous release): +-------------------------------------------------------- + +- **Lenovo ThinkPad X60/X60s** + - You can also remove the motherboard from an X61/X61s and replace + it with an X60/X60s motherboard. + +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 + 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. + - 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** +- **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) + - See **hcl/\#macbook11**. +- **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, + MB063LL/A, MB062LL/A) + - See **hcl/\#macbook21**. + +Machines no longer supported (compared to previous release): +------------------------------------------------------------ + +- **All previous systems still supported!** + +Revisions for r20140911 (7th beta) (11th September 2014) +-------------------------------------------------------- + +- The changes below were made in a git repository, unlike in previous + releases. Descriptions below are copied from \'git log\'. +- Update .gitignore for new dependencies. +- Use a submodule for i945-pwm. +- Don\'t clean packages that fail or don\'t need cleaning. +- Don\'t clean i945-pwm, it\'s not needed. +- Regression fix: Parabola live ISO boot issues +- Re-enable background images in ISOLINUX/SYSLINUX GRUB parser menus +- Regression fix: Re-add CD-ROM (ata0) in GRUB +- Documentation: add notes about performance penalty when using + ecryptfs. +- Documentation: Fixed spelling and grammatical errors. +- Documentation: macbook21: add new system as tested +- Documentation: macbook21: add info about improving touchpad + sensitivity +- Documentation: X60 Tablet: add more information about finger input +- Documentation: release.html: Add information about recently merged + commit in coreboot + +Revisions for r20140903 (6th beta) (3rd September 2014) +------------------------------------------------------- + +- 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. +- 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 + 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:\ + Merged commits (relates to boards that were already supported in + libreboot):** + - <http://review.coreboot.org/#/c/6697/> + - <http://review.coreboot.org/#/c/6698/> (merged already) + - <http://review.coreboot.org/#/c/6699/> (merged already) + - <http://review.coreboot.org/#/c/6696/> (merged already) + - <http://review.coreboot.org/#/c/6695/> (merged already) + - **<http://review.coreboot.org/#/c/5927/> (merged already)** + - <http://review.coreboot.org/#/c/6717/> (merged already) + - <http://review.coreboot.org/#/c/6718/> (merged already) + - <http://review.coreboot.org/#/c/6723/> (merged already) + (text-mode patch, might enable memtest. macbook21) + - <http://review.coreboot.org/#/c/6732/> (MERGED) (remove useless + ps/2 keyboard delay from macbook21. already merged) +- These were also merged in coreboot (relates to boards that libreboot + already supported): + - <http://review.coreboot.org/#/c/5320/> (merged) + - <http://review.coreboot.org/#/c/5321/> (merged) + - <http://review.coreboot.org/#/c/5323/> (merged) + - <http://review.coreboot.org/#/c/6693/> (merged) + - <http://review.coreboot.org/#/c/6694/> (merged) + - <http://review.coreboot.org/#/c/5324/> (merged) +- Documentation: removed the section about tft\_brightness on X60 (new + code makes it obsolete) +- Removed all patches from resources/libreboot/patch/ and added new + patch: 0000\_t60\_textmode.git.diff +- 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 + configs/rom files are now unified (containing same configuration as + serial rom files from before). + - 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/ +- Updated flashrom to new version from August 20th, 2014 +- Added getseabios and builddeps-seabios (builddeps and getall were + also updated) + - Added instructions to \'buildrom-withgrub\' to include + bios.bin.elf and vgaroms/vgabios.bin from SeaBIOS inside the + ROM. +- Added seabios (and sgavgabios) to grub as payload option in menu +- Disabled serial output in Memtest86+ (no longer needed) to speed up + tests. + - MemTest86+ now works properly, it can output on the laptop + screen (no serial port needed anymore). +- Added getgrubinvaders, builddeps-grubinvaders scripts. Added these + to getall and builddeps. + - Added [GRUB Invaders](http://www.coreboot.org/GRUB_invaders) + menu entry in resources/grub/config/grub.cfg +- Added rules to builddeps-coreboot to build libpayload with + TinyCurses. (added appropriate instructions to cleandeps script). +- Commented out lines in resources/grub/config/grub.cfg for loading + font/background (not useful anymore, now that GRUB is in text-mode). +- Commented out lines in buildrom-withgrub that included + backgrounds/fonts (not useful anymore, now that GRUB is in + text-mode). +- Added resources/utilities/i945-pwm/ (from + git://git.mtjm.eu/i945-pwm), for debugging acpi brightness on i945 + systems. + - Added instructions for it in builddeps, builddeps-i945pwm, + builddeb and cleandeps +- \'build\' script: removed the parts that generated sha512sum + 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 + accomodate this change. +- 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): + 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\_\* + modules above), cryptomount should be working now. +- Removed builddeb-bucts and builddeb-flashrom, merged them with + builddeb ( updated accordingly) +- Removed buildpac-bucts and buildpac-flashrom, merged them with + 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 +- 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 + provided pre-compiled in binary archives, and are now in source form + only. (to maximize distro compatibility). +- \'build\' script: replaced grub.elf assembly instructons, it is now + handled by a utility added under resources/utilities/grub-assemble +- Moved resources/grub/keymap to + resources/utilities/grub-assemble/keymap, and updated that utility + to use it +- Documentation: removed useless links to pictures of keyboard layouts + and unmodified layouts. +- 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 +- Deleted unused README and COPYING file from main directory +- 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 + menuentries/{common.cfg,txtmode.cfg,vesafb.cfg} + - buildrom-withgrub script uses these to generate the correct + grub.cfg for each type of configuration. +- grub\_memdisk.cfg (used inside grub.elf) now only loads grub.cfg + from cbfs. It no longer enables serial output or sets prefix. + (menuentries/common.cfg does instead) +- resources/grub/config/extra/common.cfg, added: + - insmod instructions to load those modules: nativedisk, ehci, + ohci, uhci, usb, usbserial\_pl2303, usbserial\_ftdi, + usbserial\_usbdebug + - set prefix=(memdisk)/boot/grub + - For native graphics (recommended by coreboot wiki):\ + gfxpayload=keep\ + terminal\_output \--append gfxterm + - Play a beep on startup:\ + play 480 440 1 +- Documentation: updated gnulinux/grub\_cbfs.html to make it safer + (and easier) to follow. + +Corrections to r20140811 (5th beta) (11th August 2014) +------------------------------------------------------ + +- Fixed typo where revision list for 5th beta was listed as March 11th + 2014, when in fact it was August 11th 2014 +- Fixed incorrect grub.cfg that was actually placed in + resources/grub/config/x60/grub\_usqwerty.cfg which broke the default + GRUB menu entry on X60 + +Revisions for r20140811 (5th beta) (11th August 2014) +----------------------------------------------------- + +- build: added \'luks\', \'lvm\', \'cmosdump\' and \'cmostest\' to the + list of modules for grub.elf +- Documentation: added pics showing T60 unbricking (still need to + write a tutorial) +- build: include cmos.layout + (coreboot/src/mainboard/manufacturer/model/cmos.layout) files in + libreboot\_bin +- Documentation: added **install/x60tablet\_unbrick.html** +- Documentation: added **install/t60\_unbrick.html** +- Documentation: added **install/t60\_lcd\_15.html** +- Documentation: added **install/t60\_security.html** +- Documentation: added **install/t60\_heatsink.html** +- Documentation: Renamed RELEASE.html to release.html +- Documentation: removed pcmcia reference in x60\_security.html (it\'s + cardbus) +- Documentation: added preliminary information about randomized seal + (for physical intrusion detection) in x60\_security.html and + t60\_security.html +- 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 + macbook21 +- Documentation: X60/T60: added information about checking custom ROMs + using dd to see whether or not the top 64K region is duplicated + below top or not. Advise caution about this in the tutorial that + deals with flashing on top of Lenovo BIOS, citing the correct dd + commands necessary if it is confirmed that the ROM has not been + applied with dd yet. (in the case that the user compiled their own + ROMs from libreboot, without using the build scripts, or if they + forgot to use dd, etc). +- Split resources/libreboot/patch/gitdiff into separate patch files + (getcb script updated to accomodate this change). +- Re-added .git files to bucts +- Fixed the oversight where macbook21\_firstflash wasn\'t included in + binary archives +- Release archives are now compressed using .tar.xz for better + compression + +Revisions for r20140729 (4th beta) (29th July 2014) +--------------------------------------------------- + +- Documentation: improved (more explanations, background info) in + docs/security/x60\_security.html (courtesy of Denis Carikli) +- MacBook2,1 tested (confirmed) +- macbook21: Added script \'macbook21\_firstflash\' for flashing + libreboot while Apple EFI firmware is running. +- Documentation: macbook21: added software-based flashing instructions + for flashing libreboot while Apple EFI firmware is running. +- Reduced size of libreboot\_src.tar.gz: + - Removed .git and .gitignore from grub directory + (libreboot\_src); not needed. Removing them reduces the size of + the archive (by a lot). GRUB development should be upstream. + - Removed .git and .gitignore from bucts directory + (libreboot\_src); not needed. Removing them reduces the size of + the archive. bucts development should be upstream. + - Removed .svn from flashrom directory (libreboot\_src); not + 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) +- 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)) + +Revisions for r20140720 (3rd beta) (20th July 2014) +--------------------------------------------------- + +- Fixed typo that existed in 2nd beta where the release date of the + 2nd beta was listed as being in year 2016, when in actual fact it + was 2014. +- Documentation: added (preliminary) details about (rare) buggy CPUs + on the ThinkPad T60 that were found to fail (instability, kernel + panics, etc) without the microcode updates. +- Documentation: added docs/hardware/x60\_heatsink.html for showing + how to change the heatsink on the Thinkpad X60 +- Added ROM images for Azerty (French) keyboard layout in GRUB + (courtesy of Olivier Mondoloni) +- Tidied up some scripts: + - ~~Re-factored those scripts (made easier to read/maintain): + build-x60, build-x60t, build-t60, build-macbook21~~ + - ~~Reduced the number of grub configs to 2 (or 1, for macbook21), + the build scripts now generate the other configs at build + time.~~ + - Deleted build-x60, build-x60t, build-t60, build-macbook21 and + replaced with intelligent (generic) buildrom-withgrub script + - Updated build to use buildrom-withgrub script for building the + ROM images. + - coreboot.rom and coreboot\_serial.rom renamed to + 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 + - 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 + above. +- Replaced background.png with background.jpg. added gnulove.jpg. + (resources/grub/background/) +- 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 + background. +- Updated resources/grub/config/{x60,t60,x60t}/grub\*cfg to use + background.jpg background. +- Documentation: updated docs/\#grub\_custom\_keyboard to be more + generally useful. +- nvramtool: + - Updated builddeps-coreboot script to build it + - Updated build script to include it in libreboot\_bin +- Documentation: added docs/security/x60\_security.html (security + hardening for X60) + +Revisions for r20140716 (2nd beta) (16th July 2014) +--------------------------------------------------- + +- Deleted all git-related files from the coreboot directory. This was + necessary because with those it is possible to run \'git diff\' + which shows the changes made in the form of a patch (diff format); + this includes the blobs that were deleted during deblobbing. + +Revisions for r20140711 (1st beta) (11th July 2014) +--------------------------------------------------- + +- Initial release (new coreboot base, dated 1st June 2014. See + \'getcb\' script for reference) +- DEBLOBBED coreboot +- Removed the part from memtest86+ \'make\' where it tried to connect + to some scp server while compiling. (commented out line 24 in the + Makefile) +- X60 now uses a single .config (for coreboot) +- X60 now uses a single grub.cfg (for grub memdisk) +- X60 now uses a single grub.elf (payload) +- Added new native graphics code for X60 (replaces the old \'replay\' + code) from Vladimir Serbinenko: 5320/9 from review.coreboot.org +- T60 is now supported, with native graphics. (5345/4 from + review.coreboot.org, cherry-picked on top of 5320/9 checkout) +- Added macbook2,1 support (from Mono Moosbart and Vladimir + Serbinenko) from review.coreboot.org (see \'getcb\' script to know + how that was done) + - Documentation: added information linking to correct page and + talking about which models are supported. + - Added resources/libreboot/config/macbook21config + - macbook21: Added \'build-macbook21\' script and linked to it in + \'build\' (ROMs included under bin/macbook21/) + - macbook21: Removed dd instructions from build-macbook21 script + (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 + - 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 + 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 + (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 + and docs/i945\_backlight.html) + - Documentation: added docs/i945\_backlight.html showing how + backlight controls were made to work on X60/T60 +- Documentation: Added info about getting LCD panel name based on EDID + data. + - Documentation: Added a link to this from the list of supported + T60s and LCD panels for T60 (so that the user can check what LCD + panel they have). +- X60/T60: Merged patches for 3D fix (from Paul Menzel) when using + kernel 3.12 or higher (see ./resources/libreboot/patch/gitdiff and + ./getcb) + - based on 5927/11 and 5932/5 from review.coreboot.org +- Improved thinkpad\_acpi support (from coreboot ): xsensors shows + more information. + - From 4650/29 in review.coreboot.org (merged in coreboot + \'master\' on June 1st 2014) +- Merged changes for digitizer (X60 Tablet) and IR (X60 and T60) based + on 5243/17, 5242/17 and 5239/19 from review.coreboot.org + - (see ./resources/libreboot/patch/gitdiff and ./getcb) +- Documentation: added information about building flashrom using + \'builddeps-flashrom\' script. +- Re-created resources/libreboot/config/x60config +- Re-created resources/libreboot/config/t60config +- Added \'x60tconfig\' in resources/libreboot/config (because X60 + Tablet has different information about serial/model/version in + \'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 x60t ROMs to the list of ROMs +- Tidied up the \'builddeps\' script (easier to read) +- Tidied up the \'cleandeps\' script (easier to read) +- Annotated the \'buildall\' script +- Added \'getcb\' script for getting coreboot revision used from git, + and patching it. +- Added \'getgrub\' script for getting the GRUB revision used from + git, and patching it. +- Added \'getmt86\' script for getting the memtest86+ version used, + and patching it. +- Added \'getbucts\' script for getting the bucts version used. +- Added \'getflashrom\' script for getting the flashrom version used, + and patching it +- Added \'getall\' script which runs all of the other \'get\' scripts. +- Add instructions to the \'build\' script to prepare + libreboot\_meta.tar.gz + - New archive: libreboot\_meta.tar.gz - minimal archive, using the + \'get\' scripts to download all the dependencies (coreboot, + memtest, grub and so on). +- Documentation: added information about where \'build\' script + prepares the libreboot\_meta.tar.gz archive. +- Documentation: added information about how to use the \'get\' + scripts in libreboot\_meta.tar.gz (to generate + libreboot\_src.tar.gz) + - Documentation: mention that meta doesn\'t create libreboot\_src/ + directory, but that libreboot\_meta itself becomes the same. + - Documentation: advise to rename libreboot\_meta to + libreboot\_src after running \'getall\'. +- Annotated the \'builddeb\' script, to say what each set of + dependencies are for. +- Separated bucts/flashrom builddeb sections into separate scripts: + builddeb-flashrom, builddeb-bucts. +- Documentation: Updated relevant parts based on the above. +- Added instructions to \'build\' script for including builddeb-bucts + and builddeb-flashrom in libreboot\_bin +- Updated flashrom checkout (r1822 2014-06-16) from SVN + (http://flashrom.org/Downloads). + - Updated flashing instructions in docs/ for new commands needed + (Macronix chip on X60/T60) + - For X60/T60 (flashrom): Patched + flashchips.c\_lenovobios\_macronix and + flashchips.c\_lenovobios\_sst executables for SST/macronix + (included in resources/flashrom/patch) + - Updated builddeps to build flashrom\_lenovobios\_sst and + flashrom\_lenovobios\_macronix, for X60/T60 users with Lenovo + BIOS + - moved the flashrom build instructions from \'builddeps\' and put + them in \'builddeps-flashrom\', excecuting that from + \'builddeps\'. + - Added builddeps-flashrom to libreboot\_bin.tar.gz +- flashrom: added patched flashchips.c to resources/flashrom/patch + (automatically use correct macronix chip on libreboot, without using + \'-c\' switch) + - removed \'MX25L1605\' and \'MX25L1605A/MX25L1606E\' entries in + flashchips.c for the patched version of flashchips.c + - added instructions to \'builddeps-flashrom\' to automatically + use this modified flashchips.c in the default build +- Added builddeb to libreboot\_bin.tar.gz +- Moved \'bucts\' build instructions from builddeps to builddeps-bucts + - builddeps now runs \'builddeps-bucts\' instead + - Added \'builddeps-bucts\' to libreboot\_bin.tar.gz + - Documentation: Added information about using \'builddep-bucts\' + to build the BUC.TS utility. +- Added \'lenovobios\_firstflash\' and \'lenovobios\_secondflash\' + scripts + - Added instructions to \'build\' script for including those files + in libreboot\_bin + - Documentation: Add tutorial for flashing while Lenovo BIOS is + running (on X60/T60) +- Added \'flash\' script (make sure to run builddeps-flashrom first) + which (while libreboot is already running) can use flashrom to flash + a ROM + - eg: \"sudo ./flash bin/x60/coreboot\_serial\_ukdvorak.rom\" + equivalent to \"sudo ./flashrom/flashrom -p internal -w + bin/x60/coreboot\_uk\_dvorak.rom\" + - updated \'build\' script to include the \'flash\' script in + libreboot\_bin.tar.gz +- Documentation: replaced default flashrom tutorial to recommend the + \'flash\' script instead. +- Re-add cbfstool source code back into libreboot\_bin.tar.gz, as + cbfstool\_standalone + - Patched that version to work (able to be built and used) without + requiring the entire coreboot source code. + - Created patched version of the relevant source files and added + it into resources/cbfstool/patch + - see coreboot/util/cbfstool/rmodule.c and then the patched + version in resources/cbfstool/patch/rmodule.c + - see coreboot/src/include/rmodule-defs.h and the rule in + \'build\' for including this in + ../libreboot\_bin/cbfstool\_standalone + - Added instructions to \'build\' script for applying this patch + to the cbfstool\_standalone source in libreboot\_bin + - Added instructions to \'build\' script for then re-compiling + cbfstool\_standalone in libreboot\_bin after applying the patch + - Added a \'builddeps-cbfstool\' script (in src, but only used in + bin and put in bin by \'build\') that compiles + cbfstool\_standalone in libreboot\_bin (make), moves the + cbfstool and rmodtool binaries into libreboot\_bin/ and then + does \'make clean\' in libreboot\_bin/cbfstool\_standalone + - Updated the \'build\' script to put \'builddeps-cbfstool\' in + libreboot\_bin + - Updated the \'build\' script in the cbfstool (standalone) part + to accomodate the above. + - Documentation: added notes about cbfstool (standalone) in + libreboot\_bin +- Documentation: made docs/gnulinux/grub\_cbfs.html slightly easier to + follow. +- 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 + - Documentation: In fact, document how the \'config\' files in + resources/libreboot/config/ were created +- Documentation: Added information about which ThinkPad T60s are + supported, and which are not. +- Documentation: added information about LCD inverters (for upgrading + the LCD panel on a T60 14.1\' XGA or 15.1\' XGA) + - it\'s FRU P/N 41W1478 (on T60 14.1\") so this was added to the + docs. + - it\'s P/N 42T0078 FRU 42T0079 or P/N 41W1338 (on T60 15.1\") so + this was added to the docs. +- Documentation: added information about names of LCD panels for T60 + to the relevant parts of the documentation. +- Documentation: added information (with pictures) about the + differences between T60 with Intel GPU and T60 with ATI GPU. +- Documentation: added pictures of keyboard layouts (US/UK + Qwerty/Dvorak) to the ROM list, to let the user compare with their + own keyboard. +- Move the coreboot build instructions in \'builddeps\' into + \'builddeps-coreboot\' and link it in \'builddeps\' + - Link to \'builddeps-coreboot\' in final stage of \'getcb\' +- Move GRUB build instructions from \'builddeps\' into + \'builddeps-grub\', link from \'builddeps\' + - Link to \'builddeps-grub\' in final stage of \'getgrub\' +- Move MemTest86+ build instructions from \'builddeps\' into + \'builddeps-memtest86\', link from \'builddeps\' + - Link to \'builddeps-memtest86\' in final stage of \'getmt86\' +- made \'build\' script put resources/ directory in libreboot\_bin, to + make builddeps-flashrom work in libreboot\_bin +- Removed instructions for building source code in the \'get\' script + (they don\'t really belong there) +- Added libfuse-dev and liblzma-dev to the list of GRUB dependencies + in \'builddeb\' script. +- Converted the \'RELEASE\' file to \'docs/RELEASE.html\' +- Added those dependencies to builddeb script (for GRUB part): gawk + libdevmapper-dev libtool libfreetype6-dev +- Added to build script the instruction at the end to create a + sha512sum.txt with a file manifest plus checksums. +- 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 + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Release 20140622 (5th release) {#release20140622} +============================== + +- 7th March 2014 +- revised 22nd June 2014 + +Officially supported +-------------------- + +- ThinkPad X60 +- ThinkPad X60s + +Revision (22nd June 2014 - extra) +--------------------------------- + +- Documentation: added X60 Unbricking tutorial +- Documentation: added info about enabling or disabling wifi +- Documentation: added info about enabling or disabling trackpoint + +Revision (22nd June 2014 - extra) +--------------------------------- + +- Documentation: Improved the instructions for using flashrom +- Documentation: Improved the instructions for using cbfstool (to + change the default GRUB menu) +- Documentation: Numerous small fixes. + +Revision notes (22nd June 2014) +------------------------------- + +- updated GRUB (git 4b8b9135f1676924a8458da528d264bbc7bbb301, 20th + April 2014) +- Made \"DeJavu Sans Mono\" the default font in GRUB (fixes border + corruption). +- re-added background image in GRUB (meditating GNU) +- added 6 more images: + - coreboot\_ukqwerty.rom (UK Qwerty keyboard layout in GRUB) + - coreboot\_serial\_ukqwerty.rom (UK Qwerty keyboard layout in + GRUB) + - coreboot\_dvorak.rom (US Dvorak keyboard layout in GRUB) + - coreboot\_serial\_dvorak.rom (US Dvorak keyboard layout in GRUB) + - coreboot\_ukdvorak.rom (UK Dvorak keyboard layout in GRUB) + - coreboot\_serial\_ukdvorak.rom (UK Dvorak keyboard layout in + GRUB) + - (coreboot.rom and coreboot\_serial.rom have US Qwerty keyboard + layout in GRUB, as usual) +- improved the documentation: + - removed FLASH\_INSTRUCTION and README.powertop and merged them + with README + - removed obsolete info from README and tidied it up + - deleted README (replaced with docs/) +- tidied up the menu entries in GRUB +- tidied up the root directory of X60\_source/, sorted more files into + subdirectories +- improved the commenting inside the \'build\' script (should make + modifying it easier) +- Renamed X60\_binary.tar.gz and X60\_source.tar.gz to + libreboot\_bin.tar.gz and libreboot\_src.tar.gz, respectively. +- Replaced \"GNU GRUB version\" with \"FREE AS IN FREEDOM\" on GNU + GRUB start screen. +- Added sha512.txt files in libreboot\_src and libreboot\_bin. (inside + the archives) +- Added libreboot\_bin.tar.gz.sha512.txt and + libreboot\_src.tar.gz.sha512.txt files (outside of the archives) + +Revision notes (11th June 2014): +-------------------------------- + +- removed \'CD\' boot option from coreboot.rom (not needed) +- removed \'processor.max\_cstate=2\' and \'idle=halt\' options (see + README.powertop file) + +Revision notes (5th June 2014): +------------------------------- + +- added backlight support (Fn+Home and Fn+End) on X60 +- fixed broken/unstable 3D when using kernel 3.12 or higher +- (see \'BACKPORT\' file) + +Revision notes (9th March 2015): +-------------------------------- + +- recreated coreboot config from scratch +- GRUB loads even faster now (less than 2 seconds). +- Total boot time reduced by further \~5 seconds. +- Added crypto and cryptodisk modules to GRUB +- cbfstool now included in the binary archives + +Development notes +----------------- + +- Binary archive now have 2 images: + - With serial output enabled and memtest86+ included (debug level + 8 in coreboot) + - With serial output disabled and memtest86+ excluded (faster boot + speeds) (debugging disabled) +- Reduced impact on battery life: + - \'processor.max\_cstate=2\' instead of \'idle=halt\' for booting + default kernel +- coreboot.rom (faster boot speeds, debugging disabled): + - Disabled coreboot serial output (Console-> in \"make + menuconfig\") + - Set coreboot debug level to 0 instead of 8 (Console-> in + \"make menuconfig\") + - Changed GRUB timeout to 1 second instead of 2 (in grub.cfg + - Removed background image in GRUB. + - Removed memtest86+ payload (since it relies on serial output) +- coreboot\_serial.rom (slower boot speeds, debugging enabled): + - Boot time still reduced, but only by \~2 seconds + - has the memtest86+ payload included in the ROM + - has serial port enabled. How this is achieved (from + X60\_source): Turn on debugging level to 8, and enable serial + output +- (in Console-> in coreboot \"make menuconfig\") +- (and build with grub\_serial.cfg and grub\_memdisk\_serial.cfg) + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Release 20140221 (4th release) {#release20140221} +============================== + +- 21st February 2014 + +Officially supported +-------------------- + +- ThinkPad X60 +- ThinkPad X60s + +Development notes +----------------- + +- Removed SeaBIOS (redundant) +- New GRUB version (2.02\~beta2) + - Fixes some USB issues + - Includes ISOLINUX/SYSLINUX parser +- New grub.cfg +- Removed useless options: + - options for booting sda 2/3/4 + - seabios boot option +- Added new menu entries: + - Parse ISOLINUX config (USB) + - Parse ISOLINUX config (CD) + - Added \'cat\' module for use on GRUB command line. +- \"set pager=1\" is set in grub.cfg, for less-like functionality + +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. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +r20131214 (3rd release) {#release20131214} +======================= + +- 14th December 2013 + +Supported: +---------- + +- ThinkPad X60 +- ThinkPad X60s + +Development notes +----------------- + +- Added SeaBIOS payload to GRUB2 (for booting USB drives) +- new grub.cfg + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +r20131213 (2nd release) {#release20131213} +======================= + +- 13th December 2013 + +Supported: +---------- + +- ThinkPad X60 +- ThinkPad X60s + +Development notes +----------------- + +- added background image to GRUB2 +- added memtest86+ payload to grub2 +- improvements to the documentation +- new grub.cfg + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +r20131212 (1st release) {#release20131212} +======================= + +- 12th December 2013 + +Supported: +---------- + +- ThinkPad X60 +- ThinkPad X60s + +Development notes +----------------- + +- initial release +- source code deblobbed + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/bsd/freebsd.html b/docs/bsd/freebsd.html deleted file mode 100644 index 99960882..00000000 --- a/docs/bsd/freebsd.html +++ /dev/null @@ -1,290 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>How to install FreeBSD on a libreboot system</title> -</head> - -<body> - <div id="pagetop" class="section"> - <h1>How to install FreeBSD on a libreboot system</h1> - <p> - This section relates to preparing, booting and installing - FreeBSD on your libreboot system, using nothing more than a USB flash drive (and <i>dd</i>). They've only been tested on a Lenovo ThinkPad x200. - </p> - <p> - It is expected that you use text mode in libreboot (txtmode images), - for the early boot process in FreeBSD. - <strong>Booting the installer results in a red flickering text display, - and doesn't boot.</strong> - </p> - <p> - Thanks go to ioxcide in <a href="https://www.reddit.com/r/BSD/comments/53jt70/libreboot_and_bsds/">this Reddit post</a> - for the initial instructions. - </p> - <p> - TODO: test FreeBSD more extensively, and make sure it works (and fix it if it does not). - Instructions are provided here, to boot and install FreeBSD but we're - not sure whether it is currently fully compatible with libreboot. - </p> - <ul> - <li><a href="#prepare">Prepare the USB drive (in FreeBSD)</a></li> - <li><a href="#noencryption">Installing FreeBSD without full disk encryption</a></li> - <li><a href="#encryption">Installing FreeBSD with full disk encryption</a></li> - <li><a href="#booting">Booting</a></li> - <li><a href="#configuring_grub">Configuring Grub</a></li> - <li><a href="#troubleshooting">Troubleshooting</a></li> - </ul> - <p> - <a href="./">Back to previous index</a> - </p> - </div> - - <div class="section"> - <p> - <b>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.</b> - </p> - </div> - - <div id="prepare" class="section"> - - <p> - freebsd.img is the installation image for FreeBSD. Adapt - the filename accordingly, for whatever FreeBSD version you use. - </p> - - <h2>Prepare the USB drive (in FreeBSD)</h2> - <p> - <a href="https://www.freebsd.org/doc/handbook/bsdinstall-pre.html">This page</a> - on the FreeBSD website shows how to create a bootable USB drive - for installing FreeBSD. Use the <em>dd</em> on that page. - </p> - - <h2>Prepare the USB drive (in NetBSD)</h2> - <p> - <a href="https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/">This page</a> - on the NetBSD website shows how to create a NetBSD bootable USB drive - from within NetBSD itself. You should use the <em>dd</em> method - documented there; you can use this with any ISO, including - FreeBSD. - </p> - - <h2>Prepare the USB drive (in LibertyBSD or OpenBSD)</h2> - - <p> - If you downloaded your ISO on a LibertyBSD or OpenBSD system, - here is how to create the bootable FreeBSD USB drive: - </p> - - <p> - Connect the USB drive. Check dmesg:<br/> - <b>$ dmesg | tail</b><br/> - - Check to confirm which drive it is, for example, if you think its sd3:<br/> - <b>$ disklabel sd3</b> - </p> - - <p> - Check that it wasn't automatically mounted. If it was, unmount it. For example:<br/> - <b>$ doas umount /dev/sd3i</b><br/> - </p> - - <p> - dmesg told you what device it is. Overwrite the drive, writing the FreeBSD installer to it with dd. For example:<br/> - <b>$ doas dd if=freebsd.img of=/dev/rsdXc bs=1M; sync</b><br/> - </p> - - <p> - You should now be able to boot the installer from your USB drive. Continue reading, for - information about how to do that. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - <h2>Prepare the USB drive (in GNU+Linux)</h2> - - <p> - If you downloaded your ISO on a GNU+Linux system, - here is how to create the bootable FreeBSD USB drive: - </p> - - <p> - Connect the USB drive. Check dmesg:<br/> - <b>$ dmesg</b><br/> - - Check lsblk to confirm which drive it is:<br/> - <b>$ lsblk</b> - </p> - - <p> - Check that it wasn't automatically mounted. If it was, unmount it. For example:<br/> - <b>$ sudo umount /dev/sdX*</b><br/> - <b># umount /dev/sdX*</b> - </p> - - <p> - dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example:<br/> - <b>$ sudo dd if=freebsd.img of=/dev/sdX bs=8M; sync</b><br/> - <b># dd if=freebsd.img of=/dev/sdX bs=8M; sync</b> - </p> - - <p> - You should now be able to boot the installer from your USB drive. Continue reading, for - information about how to do that. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - - <div id="noencryption" class="section"> - - <h2>Installing FreeBSD without full disk encryption</h2> - - <p> - Press C in GRUB to access the command line: - </p> - <p> - grub> <b>kfreebsd (usb0,gpt3)/boot/kernel/kernel</b><br/> - grub> <b>set FreeBSD.vfs.mountfrom=ufs:/dev/da1p3</b><br/> - grub> <b>boot</b> - </p> - <p> - It will start booting into the FreeBSD installer. Follow the normal process for installing FreeBSD. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="encryption" class="section"> - - <h2>Installing FreeBSD with full disk encryption</h2> - - <p> - TODO - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="booting" class="section"> - - <h2 id="booting">Booting</h2> - - <p> - TODO - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="configuring_grub" class="section"> - - <h2>Configuring Grub</h2> - - <p> - TODO - </p> - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="troubleshooting" class="section"> - - <h1>Troubleshooting</h1> - - <p> - Most of these issues occur when using libreboot with coreboot's 'text mode' instead of the coreboot framebuffer. - This mode is useful for booting payloads like memtest86+ which expect text-mode, but for FreeBSD - it can be problematic when they are trying to switch to a framebuffer because it doesn't exist. - </p> - - <p> - In most cases, you should use the vesafb ROM images. Example filename: libreboot_ukdvorak_vesafb.rom. - </p> - - <h2>won't boot...something about file not found</h2> - <p> - Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and numbers may differ. Use TAB completion. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - Copyright © 2016 Scott Bonds <scott@ggr.com><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md new file mode 100644 index 00000000..35590994 --- /dev/null +++ b/docs/bsd/freebsd.md @@ -0,0 +1,227 @@ +<div id="pagetop" class="section"> + +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 +*dd*). They\'ve only been tested on a Lenovo ThinkPad x200. + +It is expected that you use text mode in libreboot (txtmode images), for +the early boot process in FreeBSD. **Booting the installer results in a +red flickering text display, and doesn\'t boot.** + +Thanks go to ioxcide in [this Reddit +post](https://www.reddit.com/r/BSD/comments/53jt70/libreboot_and_bsds/) +for the initial instructions. + +TODO: test FreeBSD more extensively, and make sure it works (and fix it +if it does not). Instructions are provided here, to boot and install +FreeBSD but we\'re not sure whether it is currently fully compatible +with libreboot. + +- [Prepare the USB drive (in FreeBSD)](#prepare) +- [Installing FreeBSD without full disk encryption](#noencryption) +- [Installing FreeBSD with full disk encryption](#encryption) +- [Booting](#booting) +- [Configuring Grub](#configuring_grub) +- [Troubleshooting](#troubleshooting) + +[Back to previous index](./) + +</div> + +<div class="section"> + +**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.** + +</div> + +<div id="prepare" class="section"> + +freebsd.img is the installation image for FreeBSD. Adapt the filename +accordingly, for whatever FreeBSD version you use. + +Prepare the USB drive (in FreeBSD) +---------------------------------- + +[This page](https://www.freebsd.org/doc/handbook/bsdinstall-pre.html) on +the FreeBSD website shows how to create a bootable USB drive for +installing FreeBSD. Use the *dd* on that page. + +Prepare the USB drive (in NetBSD) +--------------------------------- + +[This +page](https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/) +on the NetBSD website shows how to create a NetBSD bootable USB drive +from within NetBSD itself. You should use the *dd* method documented +there; you can use this with any ISO, including FreeBSD. + +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** + +Check that it wasn\'t automatically mounted. If it was, unmount it. For +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**\ + +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** + +Check that it wasn\'t automatically mounted. If it was, unmount it. For +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** + +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). + +</div> + +<div id="noencryption" class="section"> + +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> **boot** + +It will start booting into the FreeBSD installer. Follow the normal +process for installing FreeBSD. + +[Back to top of page](#pagetop). + +</div> + +<div id="encryption" class="section"> + +Installing FreeBSD with full disk encryption +-------------------------------------------- + +TODO + +[Back to top of page](#pagetop). + +</div> + +<div id="booting" class="section"> + +Booting +------- + +TODO + +[Back to top of page](#pagetop). + +</div> + +<div id="configuring_grub" class="section"> + +Configuring Grub +---------------- + +TODO + +[Back to top of page](#pagetop). + +</div> + +<div id="troubleshooting" class="section"> + +Troubleshooting +=============== + +Most of these issues occur when using libreboot with coreboot\'s \'text +mode\' instead of the coreboot framebuffer. This mode is useful for +booting payloads like memtest86+ which expect text-mode, but for FreeBSD +it can be problematic when they are trying to switch to a framebuffer +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 +--------------------------------------------- + +Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and +numbers may differ. Use TAB completion. + +[Back to top of page](#pagetop). + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/bsd/index.html b/docs/bsd/index.html deleted file mode 100644 index 845e33e1..00000000 --- a/docs/bsd/index.html +++ /dev/null @@ -1,86 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>BSD projects</title> -</head> - -<body> - - <div class="section"> - - <h1 id="pagetop">BSD projects</h1> - <p> - This section relates to dealing with BSD projects: preparing bootable USB drives, - changing the default GRUB menu and so on. - </p> - <p> - <b>This section is only for the *GRUB* payload. For depthcharge, instructions have yet to be written.</b> - </p> - <p> - <a href="../">Back to previous index</a>. - </p> - <ul> - <li><a href="netbsd.html">How to install NetBSD on a libreboot system</a></li> - <li><a href="openbsd.html">How to install LibertyBSD or OpenBSD on a libreboot system</a></li> - <li><a href="freebsd.html">How to install FreeBSD on a libreboot system</a></li> - </ul> - - </div> - - <div class="section"> - - <p> - Copyright © 2016 Scott Bonds <scott@ggr.com><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/bsd/index.md b/docs/bsd/index.md new file mode 100644 index 00000000..7593aea8 --- /dev/null +++ b/docs/bsd/index.md @@ -0,0 +1,57 @@ +<div class="section"> + +BSD projects {#pagetop} +============ + +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, +instructions have yet to be written.** + +[Back to previous index](../). + +- [How to install NetBSD on a libreboot system](netbsd.html) +- [How to install LibertyBSD or OpenBSD on a libreboot + system](openbsd.html) +- [How to install FreeBSD on a libreboot system](freebsd.html) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/bsd/netbsd.html b/docs/bsd/netbsd.html deleted file mode 100644 index 2fab9f99..00000000 --- a/docs/bsd/netbsd.html +++ /dev/null @@ -1,301 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>How to install NetBSD on a libreboot system</title> -</head> - -<body> - <div id="pagetop" class="section"> - <h1>How to install NetBSD on a libreboot system</h1> - <p> - This section relates to preparing, booting and installing - NetBSD on your libreboot system, using nothing more than a USB flash drive (and <i>dd</i>). They've only been tested on a librebooted ThinkPad X60. - </p> - <p> - It is expected that you use text mode in libreboot (txtmode images), - for the early boot process in NetBSD. - <strong>Suspend/hibernate is broken, according to at least 1 user.</strong> - </p> - <p> - Thanks go to ioxcide in <a href="https://www.reddit.com/r/BSD/comments/53jt70/libreboot_and_bsds/">this Reddit post</a> - for the initial instructions. - </p> - <ul> - <li><a href="#prepare">Prepare the USB drive (in NetBSD)</a></li> - <li><a href="#noencryption">Installing NetBSD without full disk encryption</a></li> - <li><a href="#encryption">Installing NetBSD with full disk encryption</a></li> - <li><a href="#booting">Booting</a></li> - <li><a href="#configuring_grub">Configuring Grub</a></li> - <li><a href="#troubleshooting">Troubleshooting</a></li> - </ul> - <p> - <a href="./">Back to previous index</a> - </p> - </div> - - <div class="section"> - <p> - <b>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.</b> - </p> - </div> - - <div id="prepare" class="section"> - - <p> - netbsd.iso is the installation image for NetBSD. Adapt - the filename accordingly, for your version of NetBSD. - </p> - - <h2>Prepare the USB drive (in NetBSD)</h2> - <p> - <a href="https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/">This page</a> - on the NetBSD website shows how to create a NetBSD bootable USB drive - from within NetBSD itself. You should use the <em>dd</em> method - documented there. - </p> - - <h2>Prepare the USB drive (in FreeBSD)</h2> - <p> - <a href="https://www.freebsd.org/doc/handbook/bsdinstall-pre.html">This page</a> - on the FreeBSD website shows how to create a bootable USB drive - for installing FreeBSD. Use the <em>dd</em> on that page. You can - also use the same instructions with a NetBSD ISO image. - </p> - - <h2>Prepare the USB drive (in LibertyBSD or NetBSD)</h2> - - <p> - If you downloaded your ISO on a LibertyBSD or NetBSD system, - here is how to create the bootable NetBSD USB drive: - </p> - - <p> - Connect the USB drive. Check dmesg:<br/> - <b>$ dmesg | tail</b><br/> - - Check to confirm which drive it is, for example, if you think its sd3:<br/> - <b>$ disklabel sd3</b> - </p> - - <p> - Check that it wasn't automatically mounted. If it was, unmount it. For example:<br/> - <b>$ doas umount /dev/sd3i</b><br/> - </p> - - <p> - dmesg told you what device it is. Overwrite the drive, writing the NetBSD installer to it with dd. For example:<br/> - <b>$ doas netbsd.iso of=/dev/rsdXc bs=1M; sync</b><br/> - </p> - - <p> - You should now be able to boot the installer from your USB drive. Continue reading, for - information about how to do that. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - <h2>Prepare the USB drive (in GNU+Linux)</h2> - - <p> - If you downloaded your ISO on a GNU+Linux system, - here is how to create the bootable NetBSD USB drive: - </p> - - <p> - Connect the USB drive. Check dmesg:<br/> - <b>$ dmesg</b><br/> - - Check lsblk to confirm which drive it is:<br/> - <b>$ lsblk</b> - </p> - - <p> - Check that it wasn't automatically mounted. If it was, unmount it. For example:<br/> - <b>$ sudo umount /dev/sdX*</b><br/> - <b># umount /dev/sdX*</b> - </p> - - <p> - dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example:<br/> - <b>$ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync</b><br/> - <b># dd if=netbsd.iso of=/dev/sdX bs=8M; sync</b> - </p> - - <p> - You should now be able to boot the installer from your USB drive. Continue reading, for - information about how to do that. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - - <div id="noencryption" class="section"> - - <h2>Installing NetBSD without full disk encryption</h2> - - <p> - You might have to use an external USB keyboard during the installation. - Press C to access the GRUB terminal. - </p> - <p> - grub> <b>knetbsd -r sd0a (usb0,netbsd1)/netbsd</b><br/> - grub> <b>boot</b> - </p> - <p> - It will start booting into the NetBSD installer. Follow the normal process for installing NetBSD. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="encryption" class="section"> - - <h2>Installing NetBSD with full disk encryption</h2> - - <p> - TODO - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="booting" class="section"> - - <h2 id="booting">Booting</h2> - - <p> - Press C in GRUB to access the command line: - </p> - <p> - grub> <b>knetbsd -r wd0a (ahci0,netbsd1)/netbsd</b><br/> - grub> <b>boot</b> - </p> - <p> - NetBSD will start booting. Yay! - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="configuring_grub" class="section"> - - <h2>Configuring Grub</h2> - - <p> - If you don't want to drop to the GRUB command line and type in a command to boot NetBSD every time, you can create a GRUB configuration that's aware of your NetBSD installation and that will automatically be used by libreboot. - </p> - <p> - On your NetBSD root partition, create the <b>/grub</b> directory and add the file <b>libreboot_grub.cfg</b> to it. Inside the <b>libreboot_grub.cfg</b> add these lines: - <p><b> - default=0 - timeout=3 - menuentry "NetBSD" {<br> - knetbsd -r wd0a (ahci0,netbsd1)/netbsd<br> - }<br> - </b></p> - <p>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. - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="troubleshooting" class="section"> - - <h1>Troubleshooting</h1> - - <p> - Most of these issues occur when using libreboot with coreboot's 'text mode' instead of the coreboot framebuffer. - This mode is useful for booting payloads like memtest86+ which expect text-mode, but for NetBSD - it can be problematic when they are trying to switch to a framebuffer because it doesn't exist. - </p> - - <p> - In most cases, you should use the vesafb ROM images. Example filename: libreboot_ukdvorak_vesafb.rom. - </p> - - <h2>won't boot...something about file not found</h2> - <p> - Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and numbers may differ. Use TAB completion. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - Copyright © 2016 Scott Bonds <scott@ggr.com><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/bsd/netbsd.md b/docs/bsd/netbsd.md new file mode 100644 index 00000000..6a43ef0f --- /dev/null +++ b/docs/bsd/netbsd.md @@ -0,0 +1,244 @@ +<div id="pagetop" class="section"> + +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*). +They\'ve only been tested on a librebooted ThinkPad X60. + +It is expected that you use text mode in libreboot (txtmode images), for +the early boot process in NetBSD. **Suspend/hibernate is broken, +according to at least 1 user.** + +Thanks go to ioxcide in [this Reddit +post](https://www.reddit.com/r/BSD/comments/53jt70/libreboot_and_bsds/) +for the initial instructions. + +- [Prepare the USB drive (in NetBSD)](#prepare) +- [Installing NetBSD without full disk encryption](#noencryption) +- [Installing NetBSD with full disk encryption](#encryption) +- [Booting](#booting) +- [Configuring Grub](#configuring_grub) +- [Troubleshooting](#troubleshooting) + +[Back to previous index](./) + +</div> + +<div class="section"> + +**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.** + +</div> + +<div id="prepare" class="section"> + +netbsd.iso is the installation image for NetBSD. Adapt the filename +accordingly, for your version of NetBSD. + +Prepare the USB drive (in NetBSD) +--------------------------------- + +[This +page](https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/) +on the NetBSD website shows how to create a NetBSD bootable USB drive +from within NetBSD itself. You should use the *dd* method documented +there. + +Prepare the USB drive (in FreeBSD) +---------------------------------- + +[This page](https://www.freebsd.org/doc/handbook/bsdinstall-pre.html) on +the FreeBSD website shows how to create a bootable USB drive for +installing FreeBSD. Use the *dd* on that page. You can also use the same +instructions with a NetBSD ISO image. + +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** + +Check that it wasn\'t automatically mounted. If it was, unmount it. For +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**\ + +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** + +Check that it wasn\'t automatically mounted. If it was, unmount it. For +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** + +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). + +</div> + +<div id="noencryption" class="section"> + +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> **boot** + +It will start booting into the NetBSD installer. Follow the normal +process for installing NetBSD. + +[Back to top of page](#pagetop). + +</div> + +<div id="encryption" class="section"> + +Installing NetBSD with full disk encryption +------------------------------------------- + +TODO + +[Back to top of page](#pagetop). + +</div> + +<div id="booting" class="section"> + +Booting +------- + +Press C in GRUB to access the command line: + +grub> **knetbsd -r wd0a (ahci0,netbsd1)/netbsd**\ +grub> **boot** + +NetBSD will start booting. Yay! + +[Back to top of page](#pagetop). + +</div> + +<div id="configuring_grub" class="section"> + +Configuring Grub +---------------- + +If you don\'t want to drop to the GRUB command line and type in a +command to boot NetBSD every time, you can create a GRUB configuration +that\'s aware of your NetBSD installation and that will automatically be +used by libreboot. + +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\ +}\ +** + +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). + +</div> + +<div id="troubleshooting" class="section"> + +Troubleshooting +=============== + +Most of these issues occur when using libreboot with coreboot\'s \'text +mode\' instead of the coreboot framebuffer. This mode is useful for +booting payloads like memtest86+ which expect text-mode, but for NetBSD +it can be problematic when they are trying to switch to a framebuffer +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 +--------------------------------------------- + +Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and +numbers may differ. Use TAB completion. + +[Back to top of page](#pagetop). + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/bsd/openbsd.html b/docs/bsd/openbsd.html deleted file mode 100644 index 751e884a..00000000 --- a/docs/bsd/openbsd.html +++ /dev/null @@ -1,325 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>How to install LibertyBSD or OpenBSD on a libreboot system</title> -</head> - -<body> - <div id="pagetop" class="section"> - <h1>How to install LibertyBSD or OpenBSD on a libreboot system</h1> - <p> - NOTE: This guide was written for OpenBSD by the person who contributed - it, but the libreboot project recommends LibertyBSD. - LibertyBSD is a version of OpenBSD without proprietary software - in the repositories (OpenBSD distributes firmware blobs for - devices inside its kernel). - Go to the <a href="http://libertybsd.net/">LibertyBSD website</a> - -- TODO: test on LibertyBSD and prioritise that in this guide. - </p> - <p> - This section relates to preparing, booting and installing - OpenBSD on your libreboot system, using nothing more than a USB flash drive (and <i>dd</i>). They've only been tested on a Lenovo ThinkPad x200. - </p> - <ul> - <li><a href="#prepare">Prepare the USB drive (in OpenBSD)</a></li> - <li><a href="#noencryption">Installing OpenBSD without full disk encryption</a></li> - <li><a href="#encryption">Installing OpenBSD with full disk encryption</a></li> - <li><a href="#booting">Booting</a></li> - <li><a href="#configuring_grub">Configuring Grub</a></li> - <li><a href="#troubleshooting">Troubleshooting</a></li> - </ul> - <p> - <a href="./">Back to previous index</a> - </p> - </div> - - <div class="section"> - <p> - <b>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.</b> - </p> - </div> - - <div id="prepare" class="section"> - - <p> - install60.fs is the installation image for OpenBSD 6.0. Adapt - the filename accordingly, for a different OpenBSD version or - LibertyBSD. - </p> - - <h2>Prepare the USB drive (in LibertyBSD or OpenBSD)</h2> - - <p> - If you downloaded your ISO on a LibertyBSD or OpenBSD system, - here is how to create the bootable LibertyBSD/OpenBSD USB drive: - </p> - - <p> - Connect the USB drive. Check dmesg:<br/> - <b>$ dmesg | tail</b><br/> - - Check to confirm which drive it is, for example, if you think its sd3:<br/> - <b>$ disklabel sd3</b> - </p> - - <p> - Check that it wasn't automatically mounted. If it was, unmount it. For example:<br/> - <b>$ doas umount /dev/sd3i</b><br/> - </p> - - <p> - dmesg told you what device it is. Overwrite the drive, writing the OpenBSD installer to it with dd. For example:<br/> - <b>$ doas dd if=install60.fs of=/dev/rsdXc bs=1M; sync</b><br/> - </p> - - <p> - You should now be able to boot the installer from your USB drive. Continue reading, for - information about how to do that. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - <h2>Prepare the USB drive (in NetBSD)</h2> - <p> - <a href="https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/">This page</a> - on the NetBSD website shows how to create a NetBSD bootable USB drive - from within NetBSD itself. You should use the <em>dd</em> method - documented there. This will also work with the OpenBSD image. - </p> - - <h2>Prepare the USB drive (in FreeBSD)</h2> - <p> - <a href="https://www.freebsd.org/doc/handbook/bsdinstall-pre.html">This page</a> - on the FreeBSD website shows how to create a bootable USB drive - for installing FreeBSD. Use the <em>dd</em> on that page. You can - also use the same instructions with a OpenBSD ISO image. - </p> - - <h2>Prepare the USB drive (in GNU+Linux)</h2> - - <p> - If you downloaded your ISO on a GNU+Linux system, - here is how to create the bootable OpenBSD USB drive: - </p> - - <p> - Connect the USB drive. Check dmesg:<br/> - <b>$ dmesg</b><br/> - - Check lsblk to confirm which drive it is:<br/> - <b>$ lsblk</b> - </p> - - <p> - Check that it wasn't automatically mounted. If it was, unmount it. For example:<br/> - <b>$ sudo umount /dev/sdX*</b><br/> - <b># umount /dev/sdX*</b> - </p> - - <p> - dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example:<br/> - <b>$ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync</b><br/> - <b># dd if=install60.fs of=/dev/sdX bs=8M; sync</b> - </p> - - <p> - You should now be able to boot the installer from your USB drive. Continue reading, for - information about how to do that. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - - <div id="noencryption" class="section"> - - <h2>Installing OpenBSD without full disk encryption</h2> - - <p> - Press C in GRUB to access the command line: - </p> - <p> - grub> <b>kopenbsd (usb0,openbsd1)/6.0/amd64/bsd.rd</b><br/> - grub> <b>boot</b> - </p> - <p> - It will start booting into the OpenBSD installer. Follow the normal process for installing OpenBSD. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="encryption" class="section"> - - <h2>Installing OpenBSD with full disk encryption</h2> - - <p> - Not working. You can modify the above procedure (installation w/o encryption) to install OpenBSD using full disk encryption, and it appears to work, except that its not yet clear how to actually <i>boot</i> an OpenBSD+FDE installation using libreboot+Grub2. If you get it working, please let us know. - </p> - - <p> - If booting in text mode (framebuffer mode might also work), it - might be possible to chainload the OpenBSD or LibertyBSD bootloader - from the MBR section on the internal storage device. This way, - it would be possible to boot with an encrypted OpenBSD or - LibertyBSD installation. Please let us know (contact details - are on the libreboot homepage) if you get it working this way. - </p> - <p> - Alternatively, it would be good to port OpenBSD either natively - as a coreboot payload, or port it to libpayload (payload library - in coreboot; it has a basic C library and a few functions for - certain operations e.g. text/bitmap). <strong>This would be ideal, - because then it would be possible to boot a truly fully encrypted - OpenBSD or LibertyBSD installation, by putting everything in - the flash chip.</strong> - </p> - <p> - Alternatively, modifying GRUB to support booting fully encrypted - OpenBSD 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. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="booting" class="section"> - - <h2 id="booting">Booting</h2> - - <p> - Press C in GRUB to access the command line: - </p> - <p> - grub> <b>kopenbsd -r sd0a (ahci0,openbsd1)/bsd</b><br/> - grub> <b>boot</b> - </p> - <p> - OpenBSD will start booting. Yay! - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="configuring_grub" class="section"> - - <h2>Configuring Grub</h2> - - <p> - If you don't want to drop to the GRUB command line and type in a command to boot OpenBSD every time, you can create a GRUB configuration that's aware of your OpenBSD installation and that will automatically be used by libreboot. - </p> - <p> - On your OpenBSD root partition, create the <b>/grub</b> directory and add the file <b>libreboot_grub.cfg</b> to it. Inside the <b>libreboot_grub.cfg</b> add these lines: - <p><b> - default=0 - timeout=3 - menuentry "OpenBSD" {<br> - kopenbsd -r sd0a (ahci0,openbsd1)/bsd<br> - }<br> - </b></p> - <p>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. - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="troubleshooting" class="section"> - - <h1>Troubleshooting</h1> - - <p> - Most of these issues occur when using libreboot with coreboot's 'text mode' instead of the coreboot framebuffer. - This mode is useful for booting payloads like memtest86+ which expect text-mode, but for OpenBSD - it can be problematic when they are trying to switch to a framebuffer because it doesn't exist. - </p> - - <p> - In most cases, you should use the vesafb ROM images. Example filename: libreboot_ukdvorak_vesafb.rom. - </p> - - <h2>won't boot...something about file not found</h2> - <p> - Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and numbers may differ. Use TAB completion. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2016 Scott Bonds <scott@ggr.com><br/> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md new file mode 100644 index 00000000..18d27fbb --- /dev/null +++ b/docs/bsd/openbsd.md @@ -0,0 +1,265 @@ +<div id="pagetop" class="section"> + +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 +version of OpenBSD without proprietary software in the repositories +(OpenBSD distributes firmware blobs for devices inside its kernel). Go +to the [LibertyBSD website](http://libertybsd.net/) \-- TODO: test on +LibertyBSD and prioritise that in this guide. + +This section relates to preparing, booting and installing OpenBSD on +your libreboot system, using nothing more than a USB flash drive (and +*dd*). They\'ve only been tested on a Lenovo ThinkPad x200. + +- [Prepare the USB drive (in OpenBSD)](#prepare) +- [Installing OpenBSD without full disk encryption](#noencryption) +- [Installing OpenBSD with full disk encryption](#encryption) +- [Booting](#booting) +- [Configuring Grub](#configuring_grub) +- [Troubleshooting](#troubleshooting) + +[Back to previous index](./) + +</div> + +<div class="section"> + +**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.** + +</div> + +<div id="prepare" class="section"> + +install60.fs is the installation image for OpenBSD 6.0. Adapt the +filename accordingly, for a different OpenBSD version or LibertyBSD. + +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** + +Check that it wasn\'t automatically mounted. If it was, unmount it. For +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**\ + +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) +--------------------------------- + +[This +page](https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/) +on the NetBSD website shows how to create a NetBSD bootable USB drive +from within NetBSD itself. You should use the *dd* method documented +there. This will also work with the OpenBSD image. + +Prepare the USB drive (in FreeBSD) +---------------------------------- + +[This page](https://www.freebsd.org/doc/handbook/bsdinstall-pre.html) on +the FreeBSD website shows how to create a bootable USB drive for +installing FreeBSD. Use the *dd* on that page. You can also use the same +instructions with a OpenBSD ISO image. + +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** + +Check that it wasn\'t automatically mounted. If it was, unmount it. For +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** + +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). + +</div> + +<div id="noencryption" class="section"> + +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> **boot** + +It will start booting into the OpenBSD installer. Follow the normal +process for installing OpenBSD. + +[Back to top of page](#pagetop). + +</div> + +<div id="encryption" class="section"> + +Installing OpenBSD with full disk encryption +-------------------------------------------- + +Not working. You can modify the above procedure (installation w/o +encryption) to install OpenBSD using full disk encryption, and it +appears to work, except that its not yet clear how to actually *boot* an +OpenBSD+FDE installation using libreboot+Grub2. If you get it working, +please let us know. + +If booting in text mode (framebuffer mode might also work), it might be +possible to chainload the OpenBSD or LibertyBSD bootloader from the MBR +section on the internal storage device. This way, it would be possible +to boot with an encrypted OpenBSD or LibertyBSD installation. Please let +us know (contact details are on the libreboot homepage) if you get it +working this way. + +Alternatively, it would be good to port OpenBSD either natively as a +coreboot payload, or port it to libpayload (payload library in coreboot; +it has a basic C library and a few functions for certain operations e.g. +text/bitmap). **This would be ideal, because then it would be possible +to boot a truly fully encrypted OpenBSD or LibertyBSD installation, by +putting everything in the flash chip.** + +Alternatively, modifying GRUB to support booting fully encrypted OpenBSD +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). + +</div> + +<div id="booting" class="section"> + +Booting +------- + +Press C in GRUB to access the command line: + +grub> **kopenbsd -r sd0a (ahci0,openbsd1)/bsd**\ +grub> **boot** + +OpenBSD will start booting. Yay! + +[Back to top of page](#pagetop). + +</div> + +<div id="configuring_grub" class="section"> + +Configuring Grub +---------------- + +If you don\'t want to drop to the GRUB command line and type in a +command to boot OpenBSD every time, you can create a GRUB configuration +that\'s aware of your OpenBSD installation and that will automatically +be used by libreboot. + +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\ +}\ +** + +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). + +</div> + +<div id="troubleshooting" class="section"> + +Troubleshooting +=============== + +Most of these issues occur when using libreboot with coreboot\'s \'text +mode\' instead of the coreboot framebuffer. This mode is useful for +booting payloads like memtest86+ which expect text-mode, but for OpenBSD +it can be problematic when they are trying to switch to a framebuffer +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 +--------------------------------------------- + +Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and +numbers may differ. Use TAB completion. + +[Back to top of page](#pagetop). + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/depthcharge/index.html b/docs/depthcharge/index.html deleted file mode 100644 index 3088237e..00000000 --- a/docs/depthcharge/index.html +++ /dev/null @@ -1,362 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Depthcharge payload</title> -</head> - -<body> - - <div class="section"> - - <h1 id="pagetop">Depthcharge payload</h1> - - <p> - This section relates to the depthcharge payload used in libreboot. - </p> - - <p> - Or <a href="../">Back to main index</a>. - </p> - - <ul> - <li><a href="#cros_security_model">CrOS security model</a></li> - <li><a href="#developer_mode_screen">Developer mode screen</a> - <ul> - <li><a href="#holding_developer_mode_screen">Holding the developer mode screen</li> - <li><a href="#booting_normally">Booting normally</li> - <li><a href="#booting_different_mediums">Booting from different mediums</li> - <li><a href="#showing_device_information">Showing device information</li> - <li><a href="#warnings">Warnings</li> - </ul> - </li> - <li><a href="#recovery_mode_screen">Recovery mode screen</a> - <ul> - <li><a href="#recovering_bad_state">Recovering from a bad state</a></li> - <li><a href="#enabling_developer_mode">Enabling developer mode</a></li> - </ul> - </li> - <li><a href="#configuring_verified_boot_parameters">Configuring verified boot parameters</a></li> - </ul> - - </div> - - <div class="section"> - - <h1 id="cros_security_model">CrOS security model</h1> - - <p> - CrOS (Chromium OS/Chrome OS) devices such as Chromebooks implement a strict security model to ensure that these devices do not become 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. - </p> - - <div class="subsection"> - - <p> - 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 <a href="#configuring_verified_boot_parameters">configuring verified boot parameters</a>. - </p> - - </div> - - </div> - - <div class="section"> - - <h1 id="developer_mode_screen">Developer mode screen</h1> - - <p> - The developer mode screen can be accessed in depthcharge when developer mode is enabled.<br /> - Developer mode can be enabled from the <a href="#recovery_mode_screen">recovery mode screen</a>. - </p> - - <p> - It allows booting normally, booting from internal storage, booting from external media (when enabled), booting from legacy payload (when enabled), showing information about the device and disabling developer mode. - </p> - - <div class="subsection"> - - <h2 id="holding_developer_mode_screen">Holding the developer mode screen</h2> - - <p> - As instructed on the developer mode screen, the screen can be held by pressing <b>Ctrl + H</b> in the first 3 seconds after the screen is shown. - After that delay, depthcharge will resume booting normally. - </p> - - </div> - - <div class="subsection"> - - <h2 id="booting_normally">Booting normally</h2> - - <p> - As instructed on the developer mode screen, a regular boot will happen after <b>3 seconds</b> (if developer mode screen is not held).<br /> - The default boot medium (internal storage, external media, legacy payload) is shown on screen. - </p> - - </div> - - <div class="subsection"> - - <h2 id="booting_different_mediums">Booting from different mediums</h2> - - <p> - Depthcharge allows booting from different mediums, when they are allowed (see <a href="#configuring_verified_boot_parameters">configuring verified boot parameters</a> to enable or disable boot mediums).<br /> - As instructed on the developer mode screen, booting from various mediums can be triggered by pressing various key combinations: - </p> - - <ul> - <li>Internal storage: <b>Ctrl + D</b></li> - <li>External media: <b>Ctrl + U</b> (when enabled)</li> - <li>Legacy payload: <b>Ctrl + L</b> (when enabled)</li> - </ul> - - </div> - - <div class="subsection"> - - <h2 id="showing_device_information">Showing device information</h2> - - <p> - As instructed on the developer mode screen, showing device information can be triggered by pressing <b>Ctrl + I</b> or <b>Tab</b>.<br /> - Various information is shown, including vboot non-volatile data, TPM status, GBB flags and key hashes.<br /> - </p> - - </div> - - <div class="subsection"> - - <h2 id="warnings">Warnings</h2> - - <p> - The developer mode screen will show warnings when: - - <ul> - <li>Booting kernels without verifying their signature is enabled</li> - <li>Booting from external media is enabled</li> - <li>Booting legacy payloads is enabled</li> - </ul> - - </p> - - </div> - - </div> - - <div class="section"> - - <h1 id="recovery_mode_screen">Recovery mode screen</h1> - - <p> - The recovery mode screen can be accessed in depthcharge, by pressing <b>Escape + Refresh + Power</b> when the device is off. - </p> - - <p> - 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. - </p> - - <div class="subsection"> - - <h2 id="recovering_bad_state">Recovering from a bad state</h2> - - <p> - 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.<br /> - Recovery mode boots using only software located in write-protected memory, that is considered to be trusted and safe. - </p> - - <p> - 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. <br /> - Trusted recovery media are external media (USB drives, SD cards, etc) that hold a kernel signed with the recovery key. - </p> - - <p> - Google provides images of such recovery media for Chrome OS (which are not advised to users as they contain proprietary software). <br /> - They are signed with Google's recovery keys, that are pre-installed on the device when it ships. - </p> - - <p> - When replacing the full flash of the device, the pre-installed keys are 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. - </p> - - </div> - - <div class="subsection"> - - <h2 id="enabling_developer_mode">Enabling developer mode</h2> - - <p> - As instructed on the recovery mode screen, developer mode can be enabled by pressing <b>Ctrl + D</b>.<br /> - Instructions to confirm enabling developer mode are then shown on screen. - </p> - - </div> - - </div> - - <div class="section"> - - <h1 id="configuring_verified_boot_parameters">Configuring verified boot parameters</h1> - - <p> - 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.<br /> - These parameters can be modified with the <b>crossystem</b> tool, that requires sufficient privileges to access the verified boot non-volatile storage. - </p> - - <p> - <b>crossystem</b> relies on <b>mosys</b>, that is used to access the verified boot non-volatile storage on some devices. - <b>crossystem</b> and <b>mosys</b> are both free software and their source code is made available by Google: <a href="https://chromium.googlesource.com/chromiumos/platform/vboot_reference/">crossystem</a>. <a href="https://chromium.googlesource.com/chromiumos/platform/mosys/">mosys</a>.<br /> - These tools are not distributed along with Libreboot yet. However, they are preinstalled on the device, with ChromeOS. - </p> - - <p> - Some of these parameters have the potential of <b>weakening the security of the device</b>. - In particular, disabling kernels signature verification, external media boot and legacy payload boot can weaken the security of the device. - </p> - - <div class="subsection"> - - <p> - The following parameters can be configured: - </p> - - <ul> - - <li> - Kernels signature verification: - <ul> - - <li> - Enabled with:<br /> - # <b>crossystem dev_boot_signed_only=1</b> - </li> - - <li> - Disabled with:<br /> - # <b>crossystem dev_boot_signed_only=0</b> - </li> - - </ul> - </li> - - <li> - External media boot: - <ul> - - <li> - Enabled with:<br /> - # <b>crossystem dev_boot_usb=1</b> - </li> - - <li> - Disabled with:<br /> - # <b>crossystem dev_boot_usb=0</b> - </li> - - </ul> - </li> - - <li> - Legacy payload boot: - <ul> - - <li> - Enabled with:<br /> - # <b>crossystem dev_boot_legacy=1</b> - </li> - - <li> - Disabled with:<br /> - # <b>crossystem dev_boot_legacy=0</b> - </li> - - </ul> - </li> - - <li> - Default boot medium: - <ul> - - <li> - Internal storage:<br /> - # <b>crossystem dev_default_boot=disk</b> - </li> - - <li> - External media:<br /> - # <b>crossystem dev_default_boot=usb</b> - </li> - - <li> - Legacy payload:<br /> - # <b>crossystem dev_default_boot=legacy</b> - </li> - - </ul> - - </ul> - - </div> - - </div> - - <div class="section"> - - <p> - Copyright © 2015 Paul Kocialkowski <contact@paulk.fr><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/depthcharge/index.md b/docs/depthcharge/index.md new file mode 100644 index 00000000..60f4e78e --- /dev/null +++ b/docs/depthcharge/index.md @@ -0,0 +1,279 @@ +<div class="section"> + +Depthcharge payload {#pagetop} +=================== + +This section relates to the depthcharge payload used in libreboot. + +Or [Back to main index](../). + +- [CrOS security model](#cros_security_model) +- [Developer mode screen](#developer_mode_screen) + - Holding the developer mode screen + - Booting normally + - Booting from different mediums + - Showing device information + - Warnings +- [Recovery mode screen](#recovery_mode_screen) + - [Recovering from a bad state](#recovering_bad_state) + - [Enabling developer mode](#enabling_developer_mode) +- [Configuring verified boot + parameters](#configuring_verified_boot_parameters) + +</div> + +<div class="section"> + +CrOS security model {#cros_security_model} +=================== + +CrOS (Chromium OS/Chrome OS) devices such as Chromebooks implement a +strict security model to ensure that these devices do not become +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. + +<div class="subsection"> + +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). + +</div> + +</div> + +<div class="section"> + +Developer mode screen {#developer_mode_screen} +===================== + +The developer mode screen can be accessed in depthcharge when developer +mode is enabled.\ +Developer mode can be enabled from the [recovery mode +screen](#recovery_mode_screen). + +It allows booting normally, booting from internal storage, booting from +external media (when enabled), booting from legacy payload (when +enabled), showing information about the device and disabling developer +mode. + +<div class="subsection"> + +Holding the developer mode screen {#holding_developer_mode_screen} +--------------------------------- + +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. + +</div> + +<div class="subsection"> + +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).\ +The default boot medium (internal storage, external media, legacy +payload) is shown on screen. + +</div> + +<div class="subsection"> + +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).\ +As instructed on the developer mode screen, booting from various mediums +can be triggered by pressing various key combinations: + +- Internal storage: **Ctrl + D** +- External media: **Ctrl + U** (when enabled) +- Legacy payload: **Ctrl + L** (when enabled) + +</div> + +<div class="subsection"> + +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**.\ +Various information is shown, including vboot non-volatile data, TPM +status, GBB flags and key hashes.\ + +</div> + +<div class="subsection"> + +Warnings +-------- + +The developer mode screen will show warnings when: + +- Booting kernels without verifying their signature is enabled +- Booting from external media is enabled +- Booting legacy payloads is enabled + +</div> + +</div> + +<div class="section"> + +Recovery mode screen {#recovery_mode_screen} +==================== + +The recovery mode screen can be accessed in depthcharge, by pressing +**Escape + Refresh + Power** when the device is off. + +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. + +<div class="subsection"> + +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.\ +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.\ +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).\ +They are signed with Google\'s recovery keys, that are pre-installed on +the device when it ships. + +When replacing the full flash of the device, the pre-installed keys are +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. + +</div> + +<div class="subsection"> + +Enabling developer mode {#enabling_developer_mode} +----------------------- + +As instructed on the recovery mode screen, developer mode can be enabled +by pressing **Ctrl + D**.\ +Instructions to confirm enabling developer mode are then shown on +screen. + +</div> + +</div> + +<div class="section"> + +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.\ +These parameters can be modified with the **crossystem** tool, that +requires sufficient privileges to access the verified boot non-volatile +storage. + +**crossystem** relies on **mosys**, that is used to access the verified +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/).\ +These tools are not distributed along with Libreboot yet. However, they +are preinstalled on the device, with ChromeOS. + +Some of these parameters have the potential of **weakening the security +of the device**. In particular, disabling kernels signature +verification, external media boot and legacy payload boot can weaken the +security of the device. + +<div class="subsection"> + +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** +- External media boot: + - 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** +- Default boot medium: + - Internal storage:\ + \# **crossystem dev\_default\_boot=disk** + - External media:\ + \# **crossystem dev\_default\_boot=usb** + - Legacy payload:\ + \# **crossystem dev\_default\_boot=legacy** + +</div> + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/distros/index.html b/docs/distros/index.html deleted file mode 100644 index d698a90a..00000000 --- a/docs/distros/index.html +++ /dev/null @@ -1,181 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>List of recommended GNU+Linux distributions for libreboot</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">List of recommended GNU+Linux distributions for libreboot</h1> - <p> - 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. - </p> - <p> - 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 <em>Linux</em>. Despite libreboot's - <a href="../../gnu/">stance against the GNU project</a>, we still agree - with the free software philosophy and we still want you to call the - whole system <em>GNU+Linux</em>, since this is the technically correct - name for the system. - </p> - <h2>FSF-endorsed distros</h2> - <p> - Many FSF-endorsed GNU+Linux distributions are considered unfit - for general use by the libreboot project. - You can read about their problems here:<br/> - <a href="../fsf-distros/">Why we can't endorse many FSF-endorsed distributions</a>. - </p> - <p> - <a href="../gnulinux/grub_boot_installer.html">How to install GNU+Linux on a libreboot system</a> - </p> - <p> - <a href="../">Back to main index</a> - </p> - </div> - - <div class="section"> - - <h2>Debian</h2> - <p> - 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. - </p> - <p> - 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. - </p> - <p> - <a href="https://www.debian.org/">Visit the Debian website</a> - </p> - <p> - We recommend using the <em>MATE</em> desktop. - </p> - <h2>Devuan</h2> - <p> - Devuan is a fork of Debian that does not use the controversial - <em>systemd</em> init system. - </p> - <p> - See: <a href="https://www.devuan.org/os/init-freedom/">https://www.devuan.org/os/init-freedom/</a>. - </p> - <p> - <a href="https://www.devuan.org/">Visit the Devuan website</a> - </p> - <p> - We recommend using the <em>MATE</em> desktop. - </p> - <h2>Qubes</h2> - <p> - 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. - </p> - <p> - Also heavily in favour of adoption of both Libreboot and Coreboot. - </p> - <p> - <strong> - 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). - </strong> - </p> - <p> - <a href="https://www.qubes-os.org/">Visit the Qubes website</a> - </p> - <h2>Dragora</h2> - <p> - 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. - </p> - <p> - <a href="https://dragora.org/">Visit the Dragora website</a> - </p> - <h2>Parabola</h2> - <p> - Fully free bleeding edge distribution, based on the <em>Arch</em> distribution. - Good for saavy users and developers in general (some libreboot developers - use this). - </p> - <p> - Arch users, refer to the <a href="https://wiki.parabola.nu/Migration_from_the_GNU+Linux_distribution_of_Arch">Parabola migration guide</a>. - </p> - <p> - <a href="https://www.parabola.nu/">Visit the Parabola website</a> - </p> - <p> - We recommend using the <em>MATE</em> desktop. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/distros/index.md b/docs/distros/index.md new file mode 100644 index 00000000..e456e9f0 --- /dev/null +++ b/docs/distros/index.md @@ -0,0 +1,143 @@ +<div class="section"> + +List of recommended GNU+Linux distributions for libreboot {#pagetop} +========================================================= + +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/). + +[How to install GNU+Linux on a libreboot +system](../gnulinux/grub_boot_installer.html) + +[Back to main index](../) + +</div> + +<div class="section"> + +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 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/) + +We recommend using the *MATE* desktop. + +Devuan +------ + +Devuan is a fork of Debian that does not use the controversial *systemd* +init system. + +See: <https://www.devuan.org/os/init-freedom/>. + +[Visit the Devuan website](https://www.devuan.org/) + +We recommend using the *MATE* desktop. + +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. + +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).** + +[Visit the Qubes website](https://www.qubes-os.org/) + +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. + +[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). + +Arch users, refer to the [Parabola migration +guide](https://wiki.parabola.nu/Migration_from_the_GNU+Linux_distribution_of_Arch). + +[Visit the Parabola website](https://www.parabola.nu/) + +We recommend using the *MATE* desktop. + +</div> + +<div class="section"> + +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. + +</div> diff --git a/docs/fsf-distros/index.html b/docs/fsf-distros/index.html deleted file mode 100644 index 2e5500d5..00000000 --- a/docs/fsf-distros/index.html +++ /dev/null @@ -1,146 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Explaining Why We Don't Endorse FSF-endorsed Systems</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Explaining Why We Don't Endorse FSF-endorsed Systems</h1> - <p> - We are asked why we don't endorse most FSF-endorsed distributions, - usually well-known within the FSF community. - </p> - <p> - To learn more about the GNU+Linux systems that we do endorse, - check out our list of - <a href="../distros/">free GNU+Linux distributions</a>. The <em>only</em> - FSF-endorsed distribution that we endorse there is <em>Parabola</em>. - </p> - <p> - <a href="../">Back to main index</a> - </p> - </div> - - <div class="section"> - - <h2>Blag</h2> - <p> - It's a dead project. - </p> - <h2>Dynebolic</h2> - <p> - It's a dead project. - </p> - <h2>gNewSense</h2> - <p> - It's a dead project. - </p> - <h2>GuixSD</h2> - <p> - It's the GNU project's official distribution. - <a href="../../gnu/">Libreboot is opposed to the GNU project</a>. - It's actively developed, but it's not yet ready for use by - most end users. - </p> - <h2>Musix</h2> - <p> - It's a dead project. - </p> - <h2>Trisquel</h2> - <p> - The lead developer (Ruben Rodriguez) of Trisquel is one of the accused FSF employees - in their <a href="../../gnu/">recent discriminatory firing of - a trans person from the FSF</a>, and Trisquel is one of the most - aggressively promoted distributions on the part of the Free Software - Foundation. We are opposed to the FSF, and Trisquel endorses them, - so endorsing Trisquel means endorsing the FSF. - </p> - <p> - The lead developer (Ruben Rodriguez) also works full-time as an FSF - sysadmin, and seems to barely have time to develop Trisquel these days. - As a result, with a lack of leadership (and Ruben presumably still - <em>holding on</em>), the project has stalled and will probably end - up becoming a dead distro. <em>Critical security updates are currently - delayed compared to Ubuntu, their upstream!</em> - </p> - <p> - Several people within the Trisquel project have even left the - project as a result of this. For instance, this post on the Trisquel - forums clearly shows such discontent: - <a href="https://trisquel.info/en/forum/im-leaving-trisquel">https://trisquel.info/en/forum/im-leaving-trisquel</a> - - </p> - <p> - We advise all users of Trisquel, whether they use libreboot or not, - to switch to the most similar free distribution, Debian, which is - listed on our <a href="../distros/">official list of GNU+Linux - distributions recommendations</a>. - </p> - <h2>Ututo</h2> - <p> - It's a dead project. - </p> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/fsf-distros/index.md b/docs/fsf-distros/index.md new file mode 100644 index 00000000..e6cbfede --- /dev/null +++ b/docs/fsf-distros/index.md @@ -0,0 +1,118 @@ +<div class="section"> + +Explaining Why We Don\'t Endorse FSF-endorsed Systems {#pagetop} +===================================================== + +We are asked why we don\'t endorse most FSF-endorsed distributions, +usually well-known within the FSF community. + +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*. + +[Back to main index](../) + +</div> + +<div class="section"> + +Blag +---- + +It\'s a dead project. + +Dynebolic +--------- + +It\'s a dead project. + +gNewSense +--------- + +It\'s a dead project. + +GuixSD +------ + +It\'s the GNU project\'s official distribution. [Libreboot is opposed to +the GNU project](../../gnu/). It\'s actively developed, but it\'s not +yet ready for use by most end users. + +Musix +----- + +It\'s a dead project. + +Trisquel +-------- + +The lead developer (Ruben Rodriguez) of Trisquel is one of the accused +FSF employees in their [recent discriminatory firing of a trans person +from the FSF](../../gnu/), and Trisquel is one of the most aggressively +promoted distributions on the part of the Free Software Foundation. We +are opposed to the FSF, and Trisquel endorses them, so endorsing +Trisquel means endorsing the FSF. + +The lead developer (Ruben Rodriguez) also works full-time as an FSF +sysadmin, and seems to barely have time to develop Trisquel these days. +As a result, with a lack of leadership (and Ruben presumably still +*holding on*), the project has stalled and will probably end up becoming +a dead distro. *Critical security updates are currently delayed compared +to Ubuntu, their upstream!* + +Several people within the Trisquel project have even left the project as +a result of this. For instance, this post on the Trisquel forums clearly +shows such discontent: +<https://trisquel.info/en/forum/im-leaving-trisquel> + +We advise all users of Trisquel, whether they use libreboot or not, to +switch to the most similar free distribution, Debian, which is listed on +our [official list of GNU+Linux distributions +recommendations](../distros/). + +Ututo +----- + +It\'s a dead project. + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +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. + +</div> diff --git a/docs/future/index.html b/docs/future/index.html deleted file mode 100644 index 57aaa37f..00000000 --- a/docs/future/index.html +++ /dev/null @@ -1,598 +0,0 @@ -<!DOCTYPE html> -<html lang="en"> -<head> - <meta charset="utf-8"> - <title>libreboot tutorials</title> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <meta name="author" content="glugman"> - <meta name="description" content="tutorials for libreboot, the reboot library."> - <meta name="robots" content="all"> -</head> - -<body> - - <div class="section"> - - <h1 id="pagetop">Development notes</h1> - <p> - These are development notes, for future use. For old (obselete) notes, see <a href="old.html">old.html</a>. - </p> - <p> - Or go <a href="../tasks.html">back to main task list</a>. - </p> - - </div> - - <div class="section"> - - <h1>Table of contents</h1> - <ul> - <li><a href="#standard_test">Standard test</a></li> - <li><a href="#t60_cpu_microcode">T60 cpu microcode</a></li> - <li><a href="#i945_vram_size">i945 VRAM size</a></li> - <li><a href="#lcd_i945_incompatibility">LCD panels on i945 - fix incompatible panels</a></li> - <li><a href="#i945_vbt">i945 X60/T60 VBT implementation (experimental: testing)</a></li> - <li><a href="#intelvbttool_results">IntelVbtTool results</a></li> - <li><a href="#fallback_patches">Fallback patches for i945</a></li> - </ul> - - </div> - - <div class="section"> - - <h1 id="standard_test">standard test</h1> - <p> - These logs are usually obtained when testing changes related to graphics on i945 (X60 and T60). - </p> - <ul> - <li> - Make a copy of these files: - <ul> - <li>/var/log/dmesg</li> - <li>/var/log/kern.log</li> - <li>/var/log/Xorg.0.log</li> - <li>/proc/ioports</li> - <li>/proc/iomem</li> - <li>/sys/class/drm/card0/error</li> - </ul> - </li> - <li> - Record these outputs: - <ul> - <li>sudo intel_reg_dumper</li> - <li>uname -r</li> - <li>lspci -vvvvnnnnxxxx</li> - <li>sudo modprobe msr</li> - <li>sudo inteltool -a</li> - <li>sudo cbmem -c</li> - </ul> - </li> - <li> - Try some 3D games with latest kernel. - </li> - </ul> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="t60_cpu_microcode">T60 cpu microcode</h1> - - <p> - TODO: T60: find (for rare buggy CPUs that are unstable without microcode updates) if there is a workaround (patched kernel, special parameter, etc) So far, only 1 processor has been found to have issues. See microcode errata sheets http://download.intel.com/design/mobile/SPECUPDT/31407918.pdf and http://download.intel.com/design/mobile/SPECUPDT/30922214.pdf and then look at the debugging results collected in <a href="../t7200q">t7200q</a> directory (q means quirk). - </p> - - <p> - Every other T7200 tested so far has worked without microcode updates. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="i945_vram_size">i945 VRAM size</h1> - - <p> - Apparently, only 8MB VRAM is available on i945 GPUs (though it could do 64MB):<br/> - 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:<br/> - phcoder: TOM - BSM<br/> - phcoder: check what vendor BIOS offers as options<br/> - vimuser: I thought it could do 64MB usually<br/> - phcoder: not accorging to doc.<br/> - phcoder: see mobile-945-express-chipset-datasheet page 93<br/> - phcoder: see also src/northbridge/intel/i945/{early_init,northbridge,gma}.c<br/> - vimuser: "011 = DVMT (UMA) mode, 8 MB of memory pre-allocated for<br/> - vimuser: frame buffer."<br/> - vimuser: "Others - reserved"<br/> - phcoder: the easiest way is a loop at this position which tries different values and reads (and prints) BSM with them<br/> - stefanct: vimuser: they suggest that you change the value and look how BSM reacts to that<br/> - stefanct: as they pointed out earlier vram size = TOM - BSM<br/> - stefanct: different values of GMS<br/> - stefanct: phcoder: hm... this could be a hint. look at the text description of TOLUD at page 103<br/> - stefanct: it mentions 64 MB in the text about BSM as well<br/> - stefanct: table 18...<br/> - phcoder: stefanct: I have a guess which value make is 64 but I will not tell to avoid skewing test results<br/> - stefanct: phcoder: sure... i assumed you were not sure if it supports it at all. testing it properly is of course a good idea :)<br/> - stefanct: test the various possible (but reserved) values of GMS and see what the resulting VRAM size is<br/> - vimuser: so, TOM - BSM - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="lcd_i945_incompatibility">LCD panels on i945 - fix incompatible panels</h1> - - <p> - Fix T60 issues (see incompatible panels listed at <a href="../hcl/#supported_t60_list">../hcl/#supported_t60_list</a>). - </p> - - <p> - Run that tool (resources/utilities/i945gpu/intel-regs.py) as root on systems with the offending panels in: - </p> - <ul> - <li>Coreboot (or libreboot, whatever) with VBIOS (disable native graphics also)</li> - <li>(Factory BIOS also?)</li> - </ul> - - <p> - This shows values in devicetree.cb and src/northbridge/intel/i945/gma.c, the idea is that you run it on factory bios or vbios - and that it will (might) show different values: then you try those in the native graphics (in libreboot). - </p> - - <p> - Other values/registers might also need to be added to the script for these tests. - </p> - - <p> - check if intel_bios_reader from intel-gpu-tools reports the same value (BIOS has a hardcoded value) for PWM modulation frequency. - This file can read the VBIOS (64K dump). - </p> - - <p> - Check other tools in intel-gpu-tools aswell, compare outputs. Possibly add more information to intel-regs.py output (submit changes to mtjm). - Do oprom trace / replay (<a href="http://www.coreboot.org/User:GNUtoo#How_to_get_rid_of_the_vbios_of_the_x60_.5BNew_Version.5D">http://www.coreboot.org/User:GNUtoo#How_to_get_rid_of_the_vbios_of_the_x60_.5BNew_Version.5D</a>) - </p> - - <p> - Study how EDID works and how gma.c handles it. - </p> - - <p> - Original getregs.py script can be found at <a href="http://hg.mtjm.eu/scripts/file/tip/intel-regs.py">http://hg.mtjm.eu/scripts/file/tip/intel-regs.py</a> - written by Michał Masłowski. - </p> - - <p> - About fixing remaining LCD panels on 5345:<br/> - 'polarity' is mentioned in coreboot log (cbmem -c). compare output (with working and non-working panel). (and see the other notes in docs/future/) - </p> - <p> - There was a theory that working panels are - 6bpc (bits per colour) and nonworking are - 8bpc, but all EDIDs that we have here are - for 6bpc panels. - </p> - <p>We should compare coreboot logs - (from <code>cbmem -c</code> from systems with - working and nonworking panels.</p> - <p>How to dump EDID:</p> - <p> - # <b>apt-get install i2c-tools</b><br/> - # <b>modprobe i2c-dev</b><br/> - Find out the correct ID to use:<br/> - # <b>i2cdetect -l</b><br/> - Example:<br/> - # <b>i2cdump -y 2 0x50</b> - </p> - - <p> - Working panel: EDID dump from LG-Philips LP150E05-A2K1: - </p> -<pre> -No size specified (using byte-data access) - 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef -00: XX ff ff ff ff ff ff 00 30 ae 43 40 00 00 00 00 X.......0?C@.... -10: 00 0f 01 03 80 1e 17 78 ea af 00 99 58 53 8c 2a .??????x??.?XS?* -20: 25 50 54 21 08 00 81 80 01 01 01 01 01 01 01 01 %PT!?.?????????? -30: 01 01 01 01 01 01 30 2a 78 20 51 1a 10 40 30 70 ??????0*x Q??@0p -40: 13 00 31 e4 10 00 00 18 28 23 78 20 51 1a 10 40 ?.1??..?(#x Q??@ -50: 30 70 13 00 31 e4 10 00 00 18 00 00 00 0f 00 90 0p?.1??..?...?.? -60: 43 32 90 43 28 14 06 00 32 0c 00 00 00 00 00 fe C2?C(??.2?.....? -70: 00 4c 50 31 35 30 45 30 35 2d 41 32 0a 20 00 9b .LP150E05-A2? .? -80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -</pre> - - <p> - Working panel: EDID dump from Boe-Hydis HT14P12-100 FRU: 13N7061 (Inverter FRU: 41W1010) - </p> - -<pre> - 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef -00: 00 ff ff ff ff ff ff 00 30 ae 22 40 00 00 00 00 ........0?"@.... -10: 00 0f 01 03 80 1c 15 78 ea af 40 95 56 4a 8f 25 .??????x??@?VJ?% -20: 20 50 54 21 08 00 81 80 01 01 01 01 01 01 01 01 PT!?.?????????? -30: 01 01 01 01 01 01 30 2a 78 20 51 1a 10 40 30 70 ??????0*x Q??@0p -40: 13 00 1d d6 10 00 00 19 25 23 78 20 51 1a 10 40 ?.???..?%#x Q??@ -50: 30 70 13 00 1d d6 10 00 00 19 00 00 00 0f 00 90 0p?.???..?...?.? -60: 43 32 90 43 28 0f 01 00 09 e5 00 00 00 00 00 fe C2?C(??.??.....? -70: 00 48 54 31 34 50 31 32 2d 31 30 30 0a 20 00 3f .HT14P12-100? .? -80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -</pre> - -<p>LTN141XA-L01: revert to libreboot git commit c943281 to see this</p> - - <p> - <b>Non-</b>working panel: EDID dump from Samsung LTN150XG-L08: - </p> -<pre> - 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef -00: 00 ff ff ff ff ff ff 00 30 ae 40 40 00 00 00 00 ........0?@@.... -10: 00 0f 01 03 80 1f 17 78 ea 2d 05 97 57 51 8a 27 .??????x?-??WQ?' -20: 23 50 54 21 08 00 01 01 01 01 01 01 01 01 01 01 #PT!?.?????????? -30: 01 01 01 01 01 01 64 19 00 40 41 00 26 30 18 88 ??????d?.@A.&0?? -40: 36 00 30 e4 10 00 00 19 28 15 00 40 41 00 26 30 6.0??..?(?.@A.&0 -50: 18 88 36 00 30 e4 10 00 00 19 00 00 00 0f 00 61 ??6.0??..?...?.a -60: 43 32 61 43 28 14 01 00 4c a3 58 47 00 00 00 fe C2aC(??.L?XG...? -70: 00 4c 54 4e 31 35 30 58 47 2d 4c 30 38 0a 00 6d .LTN150XG-L08?.m -80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ -</pre> - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="i945_vbt">i945 gfx: X60/T60 VBT implementation (experimental: testing)</h1> - - <p> - intel_bios_dumper in intel-gpu-tools seems interesting. - </p> - <p> - <b>Use 'drm.debug=0x06' kernel parameter when booting in grub!</b> - </p> - <p> - Before each test run, boot a live USB and delete the old logs in /var/log (kernel log, xorg log, dmesg and so on). - </p> - <p> - Load (from the ROM) the runningvga.bin for each LCD panel on each system; do not execute it, only load it! (coreboot will have to be modified). - Rename the ROM appropriately, based on the system name and the panel name. coreboot_nativegfx_5868_plusrunningvga_t60_14_LTD141ECMB.rom, - for instance. Keep a copy for later use. - </p> - - <p>You are supposed to:</p> - <ul> - <li>enable native graphics in menuconfig</li> - <li>include the self-modified VGA ROM (load, but not execute) - for reverse engineering the correct VBT tables.</li> - </ul> - - <p> - With each boot, make notes about what you see and get logs using the <a href="#standard_test">standard test</a>. - You will need the files from <a href="#intelvbttool_results">#intelvbttool_results</a> for each system. - </p> - - Results (# means untested): - <ul> - <li> - <b>X60/X60s:</b> - <ul> - <li>TMD-Toshiba LTD121ECHB: #</li> - <li>CMO N121X5-L06: #</li> - <li>Samsung LTN121XJ-L07: #</li> - <li>BOE-Hydis HT121X01-101: #</li> - </ul> - </li> - <li> - <b>X60T XGA:</b> - <ul> - <li>BOE-Hydis HV121X03-100: #</li> - </ul> - </li> - <li> - <b>X60T SXGA+:</b> - <ul> - <li>BOE-Hydis HV121P01-100: #</li> - </ul> - </li> - <li> - <b>T60 14" XGA:</b> - <ul> - <li>Samsung LTN141XA-L01: #</li> - <li>CMO N141XC: #</li> - <li>BOE-Hydis HT14X14: #</li> - <li>TMD-Toshiba LTD141ECMB: #</li> - </ul> - </li> - <li> - <b>T60 14" SXGA+</b> - <ul> - <li>TMD-Toshiba LTD141EN9B: #</li> - <li>Samsung LTN141P4-L02: #</li> - <li>Boe-Hydis HT14P12: #</li> - </ul> - </li> - <li> - <b>T60 15" XGA</b> - <ul> - <li>Samsung LTN150XG-L08: #</li> - <li>LG-Philips LP150X09: #</li> - <li>13N7068 (IDtech): #</li> - <li>13N7069 (CMO): #</li> - - </ul> - </li> - <li> - <b>T60 15" SXGA+</b> - <ul> - <li>LG-Philips LP150E05-A2K1: #</li> - <li>BOE-Hydis HV150P01-100: #</li> - </ul> - </li> - <li> - <b>T60 15" UXGA</b> - <ul> - <li>BOE-Hydis HV150UX1-100: #</li> - <li>IDTech N150U3-L01: #</li> - <li>BOE-Hydis HV150UX1-102: #</li> - </ul> - </li> - <li> - <b>T50 15" QXGA</b> - <ul> - <li>IDtech IAQX10N: #</li> - <li>IDtech IAQX10S: #</li> - </ul> - </li> - </ul> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h1 id="intelvbttool_results">intelvbttool test results (VGA ROM dumps)</h1> - <p> - The VBIOS on i945 (intel gpu) platforms is self-modifying; that is, - its contents change when you run it. intelvbttool takes a dump of - the currently running vbios, and parses it. - </p> - - <p> - The idea is that we can extract the VBT tables using this knowledge, on the X60, X60 Tablet and T60 (Intel GPU). - </p> - - <p> - Here is an example of how VBT was implemented on the ThinkPad X230: - <a href="http://review.coreboot.org/#/c/5396">http://review.coreboot.org/#/c/5396</a>. - </p> - - <p> - You'll need to build a T60 ROM with SeaBIOS and the VGA ROM (for Intel GPU). An X60 ROM is also needed (same configuration, using the VGA ROM for X60). - </p> - - <p> - T60 has DVI on its dock, make sure that the dock is attached when getting this output. - </p> - - <p> - Get intelvbttool here: <a href="http://review.coreboot.org/#/c/5842">http://review.coreboot.org/#/c/5842</a> (util/intelvbttool). - </p> - - <p> - Now dump a copy of the running VGA BIOS: - <b>$ sudo dd if=/dev/mem bs=64k of=runningvga.bin skip=12 count=1</b><br/> - Then do (and record the output):<br/> - <b>$ ./intelvbttool runningvga.bin > intelvbttool_out</b> - </p> - - <p> - Backup both files (runningvga.bin and intelvbttool_out), renaming them to match the system and LCD panel used. - <a href="../misc/#get_edid_panelname">../misc/#get_edid_panelname</a> will show you how to get the name (model) of the LCD panel used. - </p> - - <h2>Test results (# means untested and all had docks, unless noted).</h2> - - <ul> - <li> - <b>X60/X60s:</b> - <ul> - <li>TMD-Toshiba LTD121ECHB: #</li> - <li>CMO N121X5-L06: #</li> - <li>Samsung LTN121XJ-L07: #</li> - <li>BOE-Hydis HT121X01-101: #</li> - </ul> - </li> - <li> - <b>X60T XGA (1024x768):</b> - <ul> - <li>BOE-Hydis HV121X03-100: #</li> - </ul> - </li> - <li> - <b>X60T SXGA+ (1400x1050):</b> - <ul> - <li>BOE-Hydis HV121P01-100: #</li> - </ul> - </li> - <li> - <b>T60 14" XGA (1024x768):</b> - <ul> - <li>Samsung LTN141XA-L01: #</li> - <li>CMO N141XC: #</li> - <li>BOE-Hydis HT14X14: #</li> - <li>TMD-Toshiba LTD141ECMB: #</li> - </ul> - </li> - <li> - <b>T60 14" SXGA+ (1400x1050):</b> - <ul> - <li>TMD-Toshiba LTD141EN9B: #</li> - <li>Samsung LTN141P4-L02: #</li> - <li>Boe-Hydis HT14P12: #</li> - </ul> - </li> - <li> - <b>T60 15" XGA (1024x768):</b> - <ul> - <li>Samsung LTN150XG-L08: #</li> - <li>LG-Philips LP150X09: #</li> - <li>13N7068 (IDtech): #</li> - <li>13N7069 (CMO): #</li> - </ul> - </li> - <li> - <b>T60 15" SXGA+ (1400x1050):</b> - <ul> - <li>LG-Philips LP150E05-A2K1: #</li> - <li>BOE-Hydis HV150P01-100: #</li> - </ul> - </li> - <li> - <b>T60 15" UXGA (1600x1200):</b> - <ul> - <li>BOE-Hydis HV150UX1-100: #</li> - <li>IDTech N150U3-L01: #</li> - <li>BOE-Hydis HV150UX1-102: #</li> - </ul> - </li> - <li> - <b>T60 15" QXGA (2048x1536):</b> - <ul> - <li>IDtech IAQX10N: #</li> - <li>IDtech IAQX10S: #</li> - </ul> - </li> - </ul> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="fallback_patches">Fallback patches</h1> - - <ul> - <li> - Todo: test gnutoo's fallback patches: <a href="http://www.coreboot.org/Fallback_mechanism">http://www.coreboot.org/Fallback_mechanism</a> - see <a href="gnutoo_fallback_patch">this IRC log</a> (warning, not cleaned up) - </li> - </ul> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="other">Other - unlisted (low priority)</h1> - - <ul> - <li> - PTE errors still exist on i945 with 6718 (which is merged). <a href="http://review.coreboot.org/#/c/6718/">http://review.coreboot.org/#/c/6718/</a> - <ul> - <li><a href="future/dumps/pte_x60_6718/dmesg">dmesg</a></li> - <li><a href="future/dumps/pte_x60_6718/kern.log">kern.log</a></li> - <li>This doesn't seem to cause any issues for general use.</li> - </ul> - </li> - <li> - Implement INT 10H support in i945 native graphics. (this will be a lot of work. SeaBIOS has code for some geode boards, to get a general idea). - </li> - <li> - T60 15" QXGA (2048x1536): fixed issue where GRUB wouldn't show any graphics. (Not many people have this panel) - <ul> - <li>It might be the same issue I ran into with Paul on the X60 (not enough memory being allocated) since the same code works on T60 SXGA+ and UXGA, where GRUB actually display graphics.</li> - </ul> - </li> - </ul> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/future/index.md b/docs/future/index.md new file mode 100644 index 00000000..23727e11 --- /dev/null +++ b/docs/future/index.md @@ -0,0 +1,465 @@ +<div class="section"> + +Development notes {#pagetop} +================= + +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). + +</div> + +<div class="section"> + +Table of contents +================= + +- [Standard test](#standard_test) +- [T60 cpu microcode](#t60_cpu_microcode) +- [i945 VRAM size](#i945_vram_size) +- [LCD panels on i945 - fix incompatible + panels](#lcd_i945_incompatibility) +- [i945 X60/T60 VBT implementation (experimental: testing)](#i945_vbt) +- [IntelVbtTool results](#intelvbttool_results) +- [Fallback patches for i945](#fallback_patches) + +</div> + +<div class="section"> + +standard test {#standard_test} +============= + +These logs are usually obtained when testing changes related to graphics +on i945 (X60 and T60). + +- Make a copy of these files: + - /var/log/dmesg + - /var/log/kern.log + - /var/log/Xorg.0.log + - /proc/ioports + - /proc/iomem + - /sys/class/drm/card0/error +- Record these outputs: + - sudo intel\_reg\_dumper + - uname -r + - lspci -vvvvnnnnxxxx + - sudo modprobe msr + - sudo inteltool -a + - sudo cbmem -c +- Try some 3D games with latest kernel. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +T60 cpu microcode {#t60_cpu_microcode} +================= + +TODO: T60: find (for rare buggy CPUs that are unstable without microcode +updates) if there is a workaround (patched kernel, special parameter, +etc) So far, only 1 processor has been found to have issues. See +microcode errata sheets +http://download.intel.com/design/mobile/SPECUPDT/31407918.pdf and +http://download.intel.com/design/mobile/SPECUPDT/30922214.pdf and then +look at the debugging results collected in [t7200q](../t7200q) directory +(q means quirk). + +Every other T7200 tested so far has worked without microcode updates. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +i945 VRAM size {#i945_vram_size} +============== + +Apparently, only 8MB VRAM is available on i945 GPUs (though it could do +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\ +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\"\ +phcoder: the easiest way is a loop at this position which tries +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\...\ +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 :)\ +stefanct: test the various possible (but reserved) values of GMS and see +what the resulting VRAM size is\ +vimuser: so, TOM - BSM + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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)). + +Run that tool (resources/utilities/i945gpu/intel-regs.py) as root on +systems with the offending panels in: + +- Coreboot (or libreboot, whatever) with VBIOS (disable native + graphics also) +- (Factory BIOS also?) + +This shows values in devicetree.cb and src/northbridge/intel/i945/gma.c, +the idea is that you run it on factory bios or vbios and that it will +(might) show different values: then you try those in the native graphics +(in libreboot). + +Other values/registers might also need to be added to the script for +these tests. + +check if intel\_bios\_reader from intel-gpu-tools reports the same value +(BIOS has a hardcoded value) for PWM modulation frequency. This file can +read the VBIOS (64K dump). + +Check other tools in intel-gpu-tools aswell, compare outputs. Possibly +add more information to intel-regs.py output (submit changes to mtjm). +Do oprom trace / replay +(<http://www.coreboot.org/User:GNUtoo#How_to_get_rid_of_the_vbios_of_the_x60_.5BNew_Version.5D>) + +Study how EDID works and how gma.c handles it. + +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:\ +\'polarity\' is mentioned in coreboot log (cbmem -c). compare output +(with working and non-working panel). (and see the other notes in +docs/future/) + +There was a theory that working panels are 6bpc (bits per colour) and +nonworking are 8bpc, but all EDIDs that we have here are for 6bpc +panels. + +We should compare coreboot logs (from `cbmem -c` from systems with +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** + +Working panel: EDID dump from LG-Philips LP150E05-A2K1: + + No size specified (using byte-data access) + 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef + 00: XX ff ff ff ff ff ff 00 30 ae 43 40 00 00 00 00 X.......0?C@.... + 10: 00 0f 01 03 80 1e 17 78 ea af 00 99 58 53 8c 2a .??????x??.?XS?* + 20: 25 50 54 21 08 00 81 80 01 01 01 01 01 01 01 01 %PT!?.?????????? + 30: 01 01 01 01 01 01 30 2a 78 20 51 1a 10 40 30 70 ??????0*x Q??@0p + 40: 13 00 31 e4 10 00 00 18 28 23 78 20 51 1a 10 40 ?.1??..?(#x Q??@ + 50: 30 70 13 00 31 e4 10 00 00 18 00 00 00 0f 00 90 0p?.1??..?...?.? + 60: 43 32 90 43 28 14 06 00 32 0c 00 00 00 00 00 fe C2?C(??.2?.....? + 70: 00 4c 50 31 35 30 45 30 35 2d 41 32 0a 20 00 9b .LP150E05-A2? .? + 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + +Working panel: EDID dump from Boe-Hydis HT14P12-100 FRU: 13N7061 +(Inverter FRU: 41W1010) + + 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef + 00: 00 ff ff ff ff ff ff 00 30 ae 22 40 00 00 00 00 ........0?"@.... + 10: 00 0f 01 03 80 1c 15 78 ea af 40 95 56 4a 8f 25 .??????x??@?VJ?% + 20: 20 50 54 21 08 00 81 80 01 01 01 01 01 01 01 01 PT!?.?????????? + 30: 01 01 01 01 01 01 30 2a 78 20 51 1a 10 40 30 70 ??????0*x Q??@0p + 40: 13 00 1d d6 10 00 00 19 25 23 78 20 51 1a 10 40 ?.???..?%#x Q??@ + 50: 30 70 13 00 1d d6 10 00 00 19 00 00 00 0f 00 90 0p?.???..?...?.? + 60: 43 32 90 43 28 0f 01 00 09 e5 00 00 00 00 00 fe C2?C(??.??.....? + 70: 00 48 54 31 34 50 31 32 2d 31 30 30 0a 20 00 3f .HT14P12-100? .? + 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + +LTN141XA-L01: revert to libreboot git commit c943281 to see this + +**Non-**working panel: EDID dump from Samsung LTN150XG-L08: + + 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef + 00: 00 ff ff ff ff ff ff 00 30 ae 40 40 00 00 00 00 ........0?@@.... + 10: 00 0f 01 03 80 1f 17 78 ea 2d 05 97 57 51 8a 27 .??????x?-??WQ?' + 20: 23 50 54 21 08 00 01 01 01 01 01 01 01 01 01 01 #PT!?.?????????? + 30: 01 01 01 01 01 01 64 19 00 40 41 00 26 30 18 88 ??????d?.@A.&0?? + 40: 36 00 30 e4 10 00 00 19 28 15 00 40 41 00 26 30 6.0??..?(?.@A.&0 + 50: 18 88 36 00 30 e4 10 00 00 19 00 00 00 0f 00 61 ??6.0??..?...?.a + 60: 43 32 61 43 28 14 01 00 4c a3 58 47 00 00 00 fe C2aC(??.L?XG...? + 70: 00 4c 54 4e 31 35 30 58 47 2d 4c 30 38 0a 00 6d .LTN150XG-L08?.m + 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +i945 gfx: X60/T60 VBT implementation (experimental: testing) {#i945_vbt} +============================================================ + +intel\_bios\_dumper in intel-gpu-tools seems interesting. + +**Use \'drm.debug=0x06\' kernel parameter when booting in grub!** + +Before each test run, boot a live USB and delete the old logs in +/var/log (kernel log, xorg log, dmesg and so on). + +Load (from the ROM) the runningvga.bin for each LCD panel on each +system; do not execute it, only load it! (coreboot will have to be +modified). Rename the ROM appropriately, based on the system name and +the panel name. +coreboot\_nativegfx\_5868\_plusrunningvga\_t60\_14\_LTD141ECMB.rom, for +instance. Keep a copy for later use. + +You are supposed to: + +- enable native graphics in menuconfig +- include the self-modified VGA ROM (load, but not execute) - for + reverse engineering the correct VBT tables. + +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. + +Results (\# means untested): +- **X60/X60s:** + - TMD-Toshiba LTD121ECHB: \# + - CMO N121X5-L06: \# + - Samsung LTN121XJ-L07: \# + - BOE-Hydis HT121X01-101: \# +- **X60T XGA:** + - BOE-Hydis HV121X03-100: \# +- **X60T SXGA+:** + - BOE-Hydis HV121P01-100: \# +- **T60 14\" XGA:** + - Samsung LTN141XA-L01: \# + - CMO N141XC: \# + - BOE-Hydis HT14X14: \# + - TMD-Toshiba LTD141ECMB: \# +- **T60 14\" SXGA+** + - TMD-Toshiba LTD141EN9B: \# + - Samsung LTN141P4-L02: \# + - Boe-Hydis HT14P12: \# +- **T60 15\" XGA** + - Samsung LTN150XG-L08: \# + - LG-Philips LP150X09: \# + - 13N7068 (IDtech): \# + - 13N7069 (CMO): \# +- **T60 15\" SXGA+** + - LG-Philips LP150E05-A2K1: \# + - BOE-Hydis HV150P01-100: \# +- **T60 15\" UXGA** + - BOE-Hydis HV150UX1-100: \# + - IDTech N150U3-L01: \# + - BOE-Hydis HV150UX1-102: \# +- **T50 15\" QXGA** + - IDtech IAQX10N: \# + - IDtech IAQX10S: \# + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +intelvbttool test results (VGA ROM dumps) {#intelvbttool_results} +========================================= + +The VBIOS on i945 (intel gpu) platforms is self-modifying; that is, its +contents change when you run it. intelvbttool takes a dump of the +currently running vbios, and parses it. + +The idea is that we can extract the VBT tables using this knowledge, on +the X60, X60 Tablet and T60 (Intel GPU). + +Here is an example of how VBT was implemented on the ThinkPad X230: +<http://review.coreboot.org/#/c/5396>. + +You\'ll need to build a T60 ROM with SeaBIOS and the VGA ROM (for Intel +GPU). An X60 ROM is also needed (same configuration, using the VGA ROM +for X60). + +T60 has DVI on its dock, make sure that the dock is attached when +getting this output. + +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** + +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 +you how to get the name (model) of the LCD panel used. + +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: \# +- **X60T XGA (1024x768):** + - BOE-Hydis HV121X03-100: \# +- **X60T SXGA+ (1400x1050):** + - BOE-Hydis HV121P01-100: \# +- **T60 14\" XGA (1024x768):** + - Samsung LTN141XA-L01: \# + - CMO N141XC: \# + - BOE-Hydis HT14X14: \# + - TMD-Toshiba LTD141ECMB: \# +- **T60 14\" SXGA+ (1400x1050):** + - TMD-Toshiba LTD141EN9B: \# + - Samsung LTN141P4-L02: \# + - Boe-Hydis HT14P12: \# +- **T60 15\" XGA (1024x768):** + - Samsung LTN150XG-L08: \# + - LG-Philips LP150X09: \# + - 13N7068 (IDtech): \# + - 13N7069 (CMO): \# +- **T60 15\" SXGA+ (1400x1050):** + - LG-Philips LP150E05-A2K1: \# + - BOE-Hydis HV150P01-100: \# +- **T60 15\" UXGA (1600x1200):** + - BOE-Hydis HV150UX1-100: \# + - IDTech N150U3-L01: \# + - BOE-Hydis HV150UX1-102: \# +- **T60 15\" QXGA (2048x1536):** + - IDtech IAQX10N: \# + - IDtech IAQX10S: \# + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Fallback patches {#fallback_patches} +================ + +- Todo: test gnutoo\'s fallback patches: + <http://www.coreboot.org/Fallback_mechanism> see [this IRC + log](gnutoo_fallback_patch) (warning, not cleaned up) + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Other - unlisted (low priority) {#other} +=============================== + +- PTE errors still exist on i945 with 6718 (which is merged). + <http://review.coreboot.org/#/c/6718/> + - [dmesg](future/dumps/pte_x60_6718/dmesg) + - [kern.log](future/dumps/pte_x60_6718/kern.log) + - This doesn\'t seem to cause any issues for general use. +- Implement INT 10H support in i945 native graphics. (this will be a + lot of work. SeaBIOS has code for some geode boards, to get a + general idea). +- T60 15\" QXGA (2048x1536): fixed issue where GRUB wouldn\'t show any + graphics. (Not many people have this panel) + - It might be the same issue I ran into with Paul on the X60 (not + enough memory being allocated) since the same code works on T60 + SXGA+ and UXGA, where GRUB actually display graphics. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/future/old.html b/docs/future/old.html deleted file mode 100644 index fe0c0910..00000000 --- a/docs/future/old.html +++ /dev/null @@ -1,319 +0,0 @@ -<!DOCTYPE html> -<html lang="en"> -<head> - <meta charset="utf-8"> - <title>libreboot tutorials</title> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <meta name="author" content="glugman"> - <meta name="description" content="tutorials for libreboot, the reboot library."> - <meta name="robots" content="all"> -</head> - -<body> - - <div class="section"> - - <h1 id="pagetop">Development notes (old/obsolete notes)</h1> - <p> - For current notes, see <a href="./"></a>. - </p> - - <p> - These are old (obsolete) notes that mare kept because they might become useful again in the future. - </p> - - </div> - - <div class="section"> - - <h1>Table of contents</h1> - <ul> - <li><a href="#x60_native_notes">X60 native graphics initialization (backlight controls)</a></li> - <li><a href="#t60_native_notes">T60 native graphics initialization (backlight controls)</a></li> - <li><a href="#5320_kernel312fix">i945: 3D fix (based on 5927) for kernel 3.12+ on 5320</a></li> - <li><a href="#x60_cb5927_testing">i945/x60: coreboot 5927 testing (3D fix for kernel 3.12+ on replay code)</a></li> - </ul> - - </div> - - <div class="section"> - - <h1 id="x60_native_notes">X60 native graphics initialization (with backlight controls)</h1> - - <p> - <b> - This is now obsolete. A better way was found (included in libreboot): <a href="http://review.coreboot.org/#/c/6731/">http://review.coreboot.org/#/c/6731/</a> - </b> - </p> - - <p> - <b><i>Also check <a href="#5320_kernel312fix">#5320_kernel312fix</a> (to fix 3D on kernel 3.12/higher)</i></b> - </p> - <p> - <b>The fix below was done on 5320/6 (from review.coreboot.org) but should work just fine on later versions of 5320.</b> - </p> - <p> - Native gpu init + backlight controls! (Fn keys). Also confirmed on X60 Tablet (1024x768) and X60 Tablet (1400x1050) - </p> - <p> - <b>Add backlight controls:</b> in <i>src/mainboard/lenovo/x60/devicetree.cb</i>, change <b>gpu_backlight</b> to <b>0x879F879E</b> - </p> - <p> - That's all! <b>This has also been backported into libreboot 5th release (line 1233 in src/mainboard/lenovo/x60/i915io.c)</b>. GNUtoo (Denis Carikli) - told me about the register <b>BLC_PWM_CTL</b> and that you could set it to control backlight. I read that address using devmem2 while running the VBIOS:<br/> - <b># devmem2 0xe4361254 w</b> - </p> - <p> - The change is also included in libreboot 6. - </p> - <p> - When doing this, it gave back that value. The same trick was used to get backlight controls for T60 (see <a href="#t60_native_notes">#t60_native_notes</a>). - </p> - - <h2>Further notes</h2> - <p> - Reading <b>0xe4361254</b> (address) in Lenovo BIOS always yields FFFFFFFF, even when writing to it (and writing to it doesn't affect brightness controls). - 'mtjm' on IRC found that the buttons (Fn keys) control /sys/class/backlight/acpi_video0 which has no affect on 61254 (BLC_PWM_CTL). This person says - intel_backlight has different values and uses the register. devmem2 works, needs checking <b>lspci -vv</b> for where the memory is mapped, - which is different than on coreboot; mtjm found that it was 0xec061254 on his system (X60 Tablet), and the register value is different too. - <b>This is relevant, because we still don't know how backlight controls are actually handled. We got it working by accident. We need to know more.</b>. - </p> - <p> - Intel-gpu-tools may prove useful for further debugging: <a href="http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/">http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/</a> - </p> - <p> - mtjm says 0xe4300000 is an MMIO region of the gpu (lspci -vv shows it), 0x61254 (BLC_PWM_CTL) is a documented register. Searching the kernel driver for backlight - shows that in intel_panel.c this register is used (there is an XXX comment about finding the right value, where recent kernels get it from. - </p> - <p> - What we want to do is calculate a good value, instead of setting it in devicetree.cb. mtjm says about backlight physics: - it has a light source , uses pulse width modulation (PWM) to turn it on/off, dimming is done by spending less time on. - <b>Note: this may not be correct; this person says that their understanding is based on how the Lenote yeeloong works</b>. - </p> - <p> - mtjm goes on to say, that the register specifies the frequency used for PWM in its depending on the GPU core frequency, so it - might be possible 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 - </p> - <p> - phcoder (Vladimir Serbinenko) who is author of 5320 (review.coreboot.org) talks about 'duty cycle limit' and 'flickering frequency'. - </p> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h1 id="t60_native_notes">T60 native graphics initialization (with backlight controls)</h1> - - <p> - <b> - This is now obsolete. A better way was found (included in libreboot): <a href="http://review.coreboot.org/#/c/6731/">http://review.coreboot.org/#/c/6731/</a> - </b> - </p> - <p> - <b><i>Also check <a href="#5320_kernel312fix">#5320_kernel312fix</a> (to fix 3D on kernel 3.12/higher)</i></b> - </p> - <p> - <b>The fix below was done on an earlier version of 5345 changeset (review.coreboot.org), but should work on the current version. it is included in libreboot 6</b> - </p> - <p> - <b>Add backlight controls:</b> in <i>src/mainboard/lenovo/t60/devicetree.cb</i>, change <b>gpu_backlight</b> to <b>0x58BF58BE</b> - </p> - <p> - Hold on! Check <a href="../misc/#get_edid_panelname">../misc/#get_edid_panelname</a> to know what LCD panel you have. This is important for the next step! - </p> - - <h2>Supported panels</h2> - <p> - <a href="../hcl/#supported_t60_list">../hcl/#supported_t60_list</a>. - </p> - - <p> - See <a href="./#lcd_i945_incompatibility">#lcd_i945_incompatibility</a>. - </p> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h1 id="5320_kernel312fix">i945: 3D fix (based on 5927) for kernel 3.12+ on 5320</h1> - - <p> - <b> - This is now obsolete. Merged in coreboot: <a href="http://review.coreboot.org/#/c/5927/">http://review.coreboot.org/#/c/5927/</a> - </b> - </p> - - <p><b>This needs to be rewritten (or better organized, or deleted?)</b>. This is also now included in libreboot 6 (using the proper way, not the 7c0000 method which was a hack)</p> - - <p> - <b>This was done on 5320/6 so far. The fix below is for 5320/6 which is now obsolete. This needs to be re-done for the latest version - of 5320. The fix below is (in practise) only for reference, therefore.</b> - </p> - - <p> - See <a href="#x60_cb5927_testing">#x60_cb5927_testing</a> for the original (and current) fix, for the replay code. Now we want - to implement that on top of <a href="http://review.coreboot.org/#/c/5320">http://review.coreboot.org/#/c/5320</a> - which is the current code for native graphics initialization on i945. - </p> - - <p> - src/northbridge/intel/i945/gma.c (using the 7c0000 hack) on 5320: <a href="dumps/5320_7c0000_gma.c">5320_7c0000_gma.c</a> (rename it to gma.c, - replacing the current one). - </p> - - <p> - The above is a hack (as is the original). A better (more correct) method is implemented in later versions of 5927, so - that should also be adapted for 5320. For now, you can use the above fix. - </p> - - <p> - The correct way to do it is to set gtt address to (end of stolen memory - gtt size), which is what later versions of 5927 do (successfully). - </p> - - <p> - Here is some debugging output using intel_gpu_tools v1.2-1 (from apt-get repositories) using tool "intel_gtt": - </p> - - <ul> - <li> - kernel 3.14.4: - <ul> - <li>with libreboot 5th release (using the 7c0000 gtt hack from 5927/3): <a href="http://paste.debian.net/104306">http://paste.debian.net/104306</a></li> - <li>with coreboot+vgarom: <a href="http://paste.debian.net/104309">http://paste.debian.net/104309</a></li> - </ul> - </li> - <li> - kernel 3.2.0-60 (from apt-get repositories): - <ul> - <li>with coreboot (no vbios or native init): <a href="http://paste.debian.net/104341">http://paste.debian.net/104341</a></li> - </ul> - </li> - </ul> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h1 id="x60_cb5927_testing">i945/X60: Coreboot 5927 testing (3D fix for kernel 3.12+ on replay code)</h1> - - <p> - <b> - This is now obsolete. Merged in coreboot: <a href="http://review.coreboot.org/#/c/5927/">http://review.coreboot.org/#/c/5927/</a> - </b> - </p> - - <p><b>The latest version as-is (5927/11) has not been tested by me yet. Always boot with 'drm.debug=0x06' kernel parameter when testing this.</b></p> - - <p> - This is the fix for 3D on kernel 3.12 and higher on i945 (ThinkPad X60 in this case). This is for the replay code. - Libreboot 5th release has a version of this backported already (based on 5927/3 using the '7c0000' hack). - </p> - - <p> - <b> - The replay code is obsolete (see 5320 changeset on review.coreboot.org for better version - which supports more systems/screens, and then 5345 for T60). Information here for reference since that is where the fix was first applied. - </b> - </p> - - <p> - Read the information on <a href="http://review.coreboot.org/#/c/5927/">http://review.coreboot.org/#/c/5927/</a>. - </p> - - <p> - For historical purposes, here is a collection of IRC logs that once existed on this page, related to the issue: - <a href="dumps/kernel312_irc">kernel312_irc</a>. - </p> - - <p> - PGETBL_CTL differs between VBIOS (-) and native graphics init (+).<br/> - - - PGETBL_CTL: 0x3ffc0001<br/> - + PGETBL_CTL: 0x3f800001 - </p> - - <p>GTT (graphics translation table) size is PGETBL_save, max 256 KiB. BSM (Base of Stolen Memory) is given by the bios.</p> - - <ul> - <li>5927/7: <a href="dumps/5927_7.tar.gz">5927_7.tar.gz</a> (GRUB graphics are correct now, and 3D still works)</li> - <li>5927/6: <a href="dumps/5927_6.tar.gz">5927_6.tar.gz</a> (GRUB graphics still corrupt, 3D/everything still works after GRUB)</li> - <li>5927/5: <a href="dumps/5927_5.tar.gz">5927_5.tar.gz</a> (GRUB graphics corrupt, 3D/everything still works after GRUB)</li> - <li>5927/3: <a href="dumps/5927_3.tar.gz">5927_3.tar.gz</a> (3D still works! kernel 3.14.4) - the '7c0000' hack</li> - <li>5927/2: <a href="dumps/5927_2.tar.gz">5927_2.tar.gz</a> (3D works! kernel 3.14.4) - the '7c0000' hack</li> - <li> - 5927/1 (didn't fix the 3D issue): - <ul> - <li><a href="dumps/5927_cbmemc">cbmem -c</a></li> - <li><a href="dumps/5927_crashdump">/sys/class/drm/card0/error</a></li> - <li><a href="dumps/5927_config">.config</a></li> - </ul> - </li> - </ul> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/future/old.md b/docs/future/old.md new file mode 100644 index 00000000..88c6cc1b --- /dev/null +++ b/docs/future/old.md @@ -0,0 +1,279 @@ +<div class="section"> + +Development notes (old/obsolete notes) {#pagetop} +====================================== + +For current notes, see [](./). + +These are old (obsolete) notes that mare kept because they might become +useful again in the future. + +</div> + +<div class="section"> + +Table of contents +================= + +- [X60 native graphics initialization (backlight + controls)](#x60_native_notes) +- [T60 native graphics initialization (backlight + controls)](#t60_native_notes) +- [i945: 3D fix (based on 5927) for kernel 3.12+ on + 5320](#5320_kernel312fix) +- [i945/x60: coreboot 5927 testing (3D fix for kernel 3.12+ on replay + code)](#x60_cb5927_testing) + +</div> + +<div class="section"> + +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 +kernel 3.12/higher)*** + +**The fix below was done on 5320/6 (from review.coreboot.org) but should +work just fine on later versions of 5320.** + +Native gpu init + backlight controls! (Fn keys). Also confirmed on X60 +Tablet (1024x768) and X60 Tablet (1400x1050) + +**Add backlight controls:** in *src/mainboard/lenovo/x60/devicetree.cb*, +change **gpu\_backlight** to **0x879F879E** + +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** + +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)). + +Further notes +------------- + +Reading **0xe4361254** (address) in Lenovo BIOS always yields FFFFFFFF, +even when writing to it (and writing to it doesn\'t affect brightness +controls). \'mtjm\' on IRC found that the buttons (Fn keys) control +/sys/class/backlight/acpi\_video0 which has no affect on 61254 +(BLC\_PWM\_CTL). This person says intel\_backlight has different values +and uses the register. devmem2 works, needs checking **lspci -vv** for +where the memory is mapped, which is different than on coreboot; mtjm +found that it was 0xec061254 on his system (X60 Tablet), and the +register value is different too. **This is relevant, because we still +don\'t know how backlight controls are actually handled. We got it +working by accident. We need to know more.**. + +Intel-gpu-tools may prove useful for further debugging: +<http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/> + +mtjm says 0xe4300000 is an MMIO region of the gpu (lspci -vv shows it), +0x61254 (BLC\_PWM\_CTL) is a documented register. Searching the kernel +driver for backlight shows that in intel\_panel.c this register is used +(there is an XXX comment about finding the right value, where recent +kernels get it from. + +What we want to do is calculate a good value, instead of setting it in +devicetree.cb. mtjm says about backlight physics: it has a light source +, uses pulse width modulation (PWM) to turn it on/off, dimming is done +by spending less time on. **Note: this may not be correct; this person +says that their understanding is based on how the Lenote yeeloong +works**. + +mtjm goes on to say, that the register specifies the frequency used for +PWM in its depending on the GPU core frequency, so it might be possible +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 + +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) + +</div> + +<div class="section"> + +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 +kernel 3.12/higher)*** + +**The fix below was done on an earlier version of 5345 changeset +(review.coreboot.org), but should work on the current version. it is +included in libreboot 6** + +**Add backlight controls:** in *src/mainboard/lenovo/t60/devicetree.cb*, +change **gpu\_backlight** to **0x58BF58BE** + +Hold on! Check +[../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). + +See [\#lcd\_i945\_incompatibility](./#lcd_i945_incompatibility). + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +i945: 3D fix (based on 5927) for kernel 3.12+ on 5320 {#5320_kernel312fix} +===================================================== + +**This is now obsolete. Merged in coreboot: +<http://review.coreboot.org/#/c/5927/>** + +**This needs to be rewritten (or better organized, or deleted?)**. This +is also now included in libreboot 6 (using the proper way, not the +7c0000 method which was a hack) + +**This was done on 5320/6 so far. The fix below is for 5320/6 which is +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 +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. + +src/northbridge/intel/i945/gma.c (using the 7c0000 hack) on 5320: +[5320\_7c0000\_gma.c](dumps/5320_7c0000_gma.c) (rename it to gma.c, +replacing the current one). + +The above is a hack (as is the original). A better (more correct) method +is implemented in later versions of 5927, so that should also be adapted +for 5320. For now, you can use the above fix. + +The correct way to do it is to set gtt address to (end of stolen memory +- gtt size), which is what later versions of 5927 do (successfully). + +Here is some debugging output using intel\_gpu\_tools v1.2-1 (from +apt-get repositories) using tool \"intel\_gtt\": + +- kernel 3.14.4: + - with libreboot 5th release (using the 7c0000 gtt hack from + 5927/3): <http://paste.debian.net/104306> + - with coreboot+vgarom: <http://paste.debian.net/104309> +- kernel 3.2.0-60 (from apt-get repositories): + - with coreboot (no vbios or native init): + <http://paste.debian.net/104341> + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +i945/X60: Coreboot 5927 testing (3D fix for kernel 3.12+ on replay code) {#x60_cb5927_testing} +======================================================================== + +**This is now obsolete. Merged in coreboot: +<http://review.coreboot.org/#/c/5927/>** + +**The latest version as-is (5927/11) has not been tested by me yet. +Always boot with \'drm.debug=0x06\' kernel parameter when testing +this.** + +This is the fix for 3D on kernel 3.12 and higher on i945 (ThinkPad X60 +in this case). This is for the replay code. Libreboot 5th release has a +version of this backported already (based on 5927/3 using the \'7c0000\' +hack). + +**The replay code is obsolete (see 5320 changeset on review.coreboot.org +for better version which supports more systems/screens, and then 5345 +for T60). Information here for reference since that is where the fix was +first applied.** + +Read the information on <http://review.coreboot.org/#/c/5927/>. + +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: 0x3f800001 + +GTT (graphics translation table) size is PGETBL\_save, max 256 KiB. BSM +(Base of Stolen Memory) is given by the bios. + +- 5927/7: [5927\_7.tar.gz](dumps/5927_7.tar.gz) (GRUB graphics are + correct now, and 3D still works) +- 5927/6: [5927\_6.tar.gz](dumps/5927_6.tar.gz) (GRUB graphics still + corrupt, 3D/everything still works after GRUB) +- 5927/5: [5927\_5.tar.gz](dumps/5927_5.tar.gz) (GRUB graphics + corrupt, 3D/everything still works after GRUB) +- 5927/3: [5927\_3.tar.gz](dumps/5927_3.tar.gz) (3D still works! + kernel 3.14.4) - the \'7c0000\' hack +- 5927/2: [5927\_2.tar.gz](dumps/5927_2.tar.gz) (3D works! kernel + 3.14.4) - the \'7c0000\' hack +- 5927/1 (didn\'t fix the 3D issue): + - [cbmem -c](dumps/5927_cbmemc) + - [/sys/class/drm/card0/error](dumps/5927_crashdump) + - [.config](dumps/5927_config) + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/git/index.html b/docs/git/index.html deleted file mode 100644 index dc4b584a..00000000 --- a/docs/git/index.html +++ /dev/null @@ -1,490 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Building libreboot from source</title> -</head> - -<body> - -<div class="section"> -<p> -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. -</p> -</div> - - <div class="section"> - <h1 id="pagetop">Building libreboot from source</h1> - <p> - This section relates to building libreboot from source, and - working with the git repository. - </p> - <p> - Or <a href="../">Back to main index</a>. - </p> - <ul> - <li><a href="#build_dependencies">Install build dependencies</a></li> - <li><a href="#build_meta">Get the full source code from metadata (git clone)</a></li> - <li><a href="#build_bucts">How to build "bucts" (for LenovoBIOS X60/X60S/X60T/T60)</a></li> - <li><a href="#build_flashrom">How to build "flashrom"</a></li> - <li><a href="#build">How to build the ROM images</a></li> - </ul> - </div> - - <div class="section"> - - <h1 id="build_dependencies">Install build dependencies</h1> - - <p> - Before doing anything, you need the dependencies first. This is true if - you want to build libreboot from source, with either libreboot_src.tar.xz or git. - <b>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.</b> - </p> - - <div class="important"> - <p> - For Debian Stretch (may also work on Debian Jessie), you can run the following command:<br/> - $ <b>sudo ./oldbuild dependencies debian</b> - <br/>(this will also work in Devuan) - </p> - <p> - For Parabola, you can run the following command:<br/> - $ <b>sudo ./oldbuild dependencies parabola</b><br/> - or:<br/> - # <b>./oldbuild dependencies parabola</b> - </p> - </div> - - <p> - For other GNU+Linux distributions, you can adapt the existing scripts. - </p> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h1 id="build_meta">Get the full source code from metadata (git clone)</h1> - - <p> - If you downloaded libreboot from git, then there are some steps to download and patch - the source code for all relevant dependencies. The archive in the git repository used to be - available as a tarball called 'libreboot_meta.tar.gz'. It contains 'metadata' (scripts) - which define how the source was created (where it came from). - </p> - - <p> - You can use the scripts included to download everything. - </p> - - <p> - First, <a href="#build_dependencies">install the build dependencies</a>. - </p> - - <p> - 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:<br/> - $ <b>git config --global user.name "Your Name"</b><br/> - $ <b>git config --global user.email your@emailaddress.com</b><br/> - This is what will also appear in git logs if you ever commit your own changes to a given repository. For - more information, see <a href="http://git-scm.com/doc">http://git-scm.com/doc</a>. - </p> - - <p> - Another nice config for you (optional, but recommended):<br/> - $ <b>git config --global core.editor nano</b><br/> - $ <b>git config --global color.status auto</b><br/> - $ <b>git config --global color.branch auto</b><br/> - $ <b>git config --global color.interactive auto</b><br/> - $ <b>git config --global color.diff auto</b> - </p> - - <p> - After that, run the script:<br/> - $ <b>./download all</b> - </p> - - <p> - 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. - </p> - - <p> - To build the ROM images, see <a href="#build">#build</a>. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="build_bucts">How to build "bucts" (for LenovoBIOS X60/X60S/X60T/T60)</h1> - - <p> - <b>This is for Lenovo BIOS users on the ThinkPad X60/X60S, X60 Tablet and T60. If you have coreboot or libreboot running already, ignore this.</b> - </p> - - <p> - BUC.TS isn't really specific to these laptops, but is a bit inside the a register in the chipset on some Intel systems. - </p> - - <p> - 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. Lenovo BIOS will prevent you from writing the - final one, so running "<b>bucts 1</b>" 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 <a href="#build_flashrom">#build_flashrom</a>). - 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 "<b>bucts 0</b>" to - make the system boot from the normal (highest) block again. - </p> - - <p> - *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. - </p> - - <p> - BUC.TS is backed up (powered) by the NVRAM battery (or CMOS battery, as some people call it). On thinkpads, - this is typically in a yellow plastic package with the battery inside, connected via power lines to the - mainboard. Removing that battery removes power to BUC.TS, resetting the bit back to 0 (if you previously set - it to 1). - </p> - - <p> - BUC.TS utility is included in libreboot_src.tar.xz and libreboot_util.tar.xz.<br/> - <b>If you downloaded from git, follow <a href="#build_meta">#build_meta</a> before you proceed.</b> - </p> - - <p> - "BUC" means "<b>B</b>ack<b>u</b>p <b>C</b>ontrol" (it's a register) and "TS" means "<b>T</b>op <b>S</b>wap" - (it's a status bit). Hence "bucts" (BUC.TS). TS 1 and TS 0 corresponds to bucts 1 and bucts 0. - </p> - - <p> - If you have the binary release archive, you'll find executables under ./bucts/. Otherwise if you need to build from source, continue reading. - </p> - - <p> - First, <a href="#build_dependencies">install the build dependencies</a>. - </p> - - <p> - To build bucts, do this in the main directory:<br/> - $ <b>./oldbuild module bucts</b> - </p> - - <p> - To statically compile it, do this:<br/> - $ <b>./oldbuild module bucts static</b> - </p> - - <p> - The "builddeps" script in libreboot_src also makes use of builddeps-bucts. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="build_flashrom">How to build "flashrom"</h1> - - <p> - Flashrom is the utility for flashing/dumping ROM images. This is what you will use to install libreboot. - </p> - - <p> - Flashrom source code is included in libreboot_src.tar.xz and libreboot_util.tar.xz.<br/> - <b>If you downloaded from git, follow <a href="#build_meta">#build_meta</a> before you proceed.</b> - </p> - - <p> - If you are using the binary release archive, then there are already binaries included - under ./flashrom/. The flashing scripts will try to choose the correct one for you. Otherwise - if you wish to re-build flashrom from source, continue reading. - </p> - - <p> - First, <a href="#build_dependencies">install the build dependencies</a>. - </p> - - <p> - To build it, do the following in the main directory:<br/> - $ <b>./oldbuild module flashrom</b> - </p> - - <p> - To statically compile it, do the following in the main directory:<br/> - $ <b>./oldbuild module flashrom static</b> - </p> - - <p> - After you've done that, under ./flashrom/ you will find the following executables: - </p> - <ul> - <li> - <b>flashrom</b> - <ul> - <li>For flashing while coreboot or libreboot is running.</li> - </ul> - </li> - <li> - <b>flashrom_lenovobios_sst</b> - <ul> - <li>This is patched for flashing while Lenovo BIOS is running on an X60 or T60 with the SST25VF016B (SST) flash chip.</li> - </ul> - </li> - <li> - <b>flashrom_lenovobios_macronix</b> - <ul> - <li>This is patched for flashing while Lenovo BIOS is running on an X60 or T60 with the MX25L1605D (Macronix) flash chip.</li> - </ul> - </li> - </ul> - - <p> - The "builddeps" script in libreboot_src also makes use of builddeps-flashrom. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="build">How to build the ROM images</h1> - - <p>You don't need to do much, as there are scripts already written for you that can build everything automatically.</p> - - <p> - You can build libreboot from source on a 32-bit (i686) or 64-bit (x86_64) system. Recommended (if possible): x86_64. - ASUS KFSN4-DRE has 64-bit CPUs. - On a ThinkPad T60, you can replace the CPU (Core 2 Duo T5600, T7200 or T7600. T5600 recommended) for 64-bit support. - On an X60s, you can replace the board with one that has a Core 2 Duo L7400 (you could also use an X60 Tablet board with the same CPU). - On an X60, you can replace the board with one that has a Core 2 Duo T5600 or T7200 (T5600 is recommended). All MacBook2,1 laptops - are 64-bit, as are all ThinkPad X200, X200S, X200 Tablet, R400, T400 and T500 laptops. Warning: MacBook1,1 laptops are all 32-bit only. - </p> - - <p> - First, <a href="#build_dependencies">install the build dependencies</a>. - </p> - <p> - If you downloaded libreboot from git, refer to <a href="#build_meta">#build_meta</a>. - </p> - - <p> - Build all of the components used in libreboot:<br/> - $ <b>./oldbuild module all</b> - </p> - - <p> - You can also build each modules separately, using <i>./oldbuild module modulename</i>. - To see the possible values for <i>modulename</i>, use:<br/> - $ <b>./oldbuild module list</b> - </p> - - <p> - After that, build the ROM images (for all boards):<br/> - $ <b>./oldbuild roms withgrub</b><br/> - Alternatively, you can build for a specific board or set of boards. - For example:<br/> - $ <b>./oldbuild roms withgrub x60</b><br/> - $ <b>./oldbuild roms withgrub x200_8mb</b><br/> - $ <b>./oldbuild roms withgrub x60 x200_8mb</b><br/> - The list of board options can be found by looking at the directory - names in <b>resources/libreboot/config/grub/</b>. - </p> - - <p> - To clean (reverse) everything, do the following:<br/> - $ <b>./oldbuild clean all</b> - </p> - - <p> - The ROM images will be stored under <b>bin/<i>payload</i>/</b>, - where <i>payload</i> could be <i>grub</i>, <i>seabios</i>, or - whatever other payload those images were built for. - </p> - - <div class="subsection"> - - <h2>Preparing release archives (optional)</h2> - - <p> - <b>This is only confirmed to work (tested) in Debian Stretch. Parabola *fails* at this stage - (for now). For all other distros, YMMV. This will also work in Devuan.</b> - </p> - - <p> - This is mainly intended for use with the git repository. - These commands will work in the release archive (_src), unless otherwise noted below. - </p> - - <p> - The archives will appear under <i>release/oldbuildsystem/${version}/</i>; - ${version} will either be set using <i>git describe</i> or, - if a <i>version</i> file already exists (_src release archive), - then it will simply re-use that. - </p> - - <p> - Tag the current commit, and that version will appear in both the ${version} - string on the directory under <i>release/oldbuildsystem/</i>, and in the file names of the - archives. Otherwise, whatever git uses for <i>git describe --tags HEAD</i> - will be used. - </p> - - <p> - Utilities (static executables):<br/> - $ <b>./oldbuild release util</b> - </p> - <p> - Archive containing flashrom and bucts source code:<br/> - $ <b>./oldbuild release tobuild</b> - </p> - <p> - Documentation archive (<b>does not work on _src release archive, only git</b>):<br/> - $ <b>./oldbuild release docs</b> - </p> - <p> - ROM image archives:<br/> - $ <b>./oldbuild release roms</b> - </p> - <p> - Source code archive:<br/> - $ <b>./oldbuild release src</b> - </p> - <p> - SHA512 sums of all other release archives that have been generated:<br/> - $ <b>./oldbuild release sha512sums</b> - </p> - - <p> - If you are building on an i686 host, this will build statically linked 32-bit binaries in - the binary release archive that you created, - for: <b>nvramtool, cbfstool, ich9deblob, cbmem</b>. - </p> - - <p> - If you are building on an x86_64 host, this will build statically linked 32- *and* 64-bit binaries for - <b>cbmem</b>, <b>ich9deblob</b>, <b>cbfstool</b> and <b>nvramtool</b>. - </p> - <p> - <b>To include statically linked i686 and x86_64 binaries for bucts and flashrom, - you will need to build them on a chroot, a virtual system or a real - system where the host uses each given architecture. These packages are difficult - to cross-compile, and the libreboot project is still figuring out how to deal - with them.</b> - </p> - <p> - The same applies if you want to include statically linked flashrom binaries for ARM. - </p> - - <p> - armv7l binaries (tested on a BeagleBone Black) are also included in libreboot_util, for: - </p> - <ul> - <li>cbfstool</li> - <li>ich9gen</li> - <li>ich9deblob</li> - <li>flashrom</li> - </ul> - - <p> - If you are building binaries on a live system or chroot (for flashrom/bucts), you can use the following to statically link them:<br/> - $ <b>./oldbuild module flashrom static</b><br/> - $ <b>./oldbuild module bucts static</b> - </p> - - <p> - The same conditions as above apply for ARM (except, building bucts on ARM is pointless, and for flashrom - you only need the normal executable since the lenovobios_sst and _macronix executables are meant - to run on an X60/T60 while lenovo bios is present, working around the security restrictions). - </p> - - <p> - The command that you used for generating the release archives will also run the following command:<br/> - $ <b>./oldbuild release tobuild</b><br/> - The archive <b>tobuild.tar.xz</b> will have been created under <b>release/oldbuildsystem/</b>, containing bucts, flashrom and all other required - resources for building them. - </p> - - <p> - You'll find that the files libreboot_util.tar.xz and libreboot_src.tar.xz have been created, under <b>release/oldbuildsystem/</b>. - </p> - - <p> - The ROM images will be stored in separate archives for each system, under <b>release/oldbuildsystem/rom/</b>. - </p> - - </div> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/git/index.md b/docs/git/index.md new file mode 100644 index 00000000..283ce0a8 --- /dev/null +++ b/docs/git/index.md @@ -0,0 +1,390 @@ +<div class="section"> + +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. + +</div> + +<div class="section"> + +Building libreboot from source {#pagetop} +============================== + +This section relates to building libreboot from source, and working with +the git repository. + +Or [Back to main index](../). + +- [Install build dependencies](#build_dependencies) +- [Get the full source code from metadata (git clone)](#build_meta) +- [How to build \"bucts\" (for LenovoBIOS + X60/X60S/X60T/T60)](#build_bucts) +- [How to build \"flashrom\"](#build_flashrom) +- [How to build the ROM images](#build) + +</div> + +<div class="section"> + +Install build dependencies {#build_dependencies} +========================== + +Before doing anything, you need the dependencies first. This is true if +you want to build libreboot from source, with either +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.** + +<div class="important"> + +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:\ +\# **./oldbuild dependencies parabola** + +</div> + +For other GNU+Linux distributions, you can adapt the existing scripts. + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +Get the full source code from metadata (git clone) {#build_meta} +================================================== + +If you downloaded libreboot from git, then there are some steps to +download and patch the source code for all relevant dependencies. The +archive in the git repository used to be available as a tarball called +\'libreboot\_meta.tar.gz\'. It contains \'metadata\' (scripts) which +define how the source was created (where it came from). + +You can use the scripts included to download everything. + +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**\ +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**\ +\$ **git config \--global color.diff auto** + +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). + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +How to build \"bucts\" (for LenovoBIOS X60/X60S/X60T/T60) {#build_bucts} +========================================================= + +**This is for Lenovo BIOS users on the ThinkPad X60/X60S, X60 Tablet and +T60. If you have coreboot or libreboot running already, ignore this.** + +BUC.TS isn\'t really specific to these laptops, but is a bit inside the +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. +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 +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 +because dd is used to do that, by the build system. If you\'re building +from upstream (coreboot), you have to do it manually. + +BUC.TS is backed up (powered) by the NVRAM battery (or CMOS battery, as +some people call it). On thinkpads, this is typically in a yellow +plastic package with the battery inside, connected via power lines to +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 +you proceed.** + +\"BUC\" means \"**B**ack**u**p **C**ontrol\" (it\'s a register) and +\"TS\" means \"**T**op **S**wap\" (it\'s a status bit). Hence \"bucts\" +(BUC.TS). TS 1 and TS 0 corresponds to bucts 1 and bucts 0. + +If you have the binary release archive, you\'ll find executables under +./bucts/. Otherwise if you need to build from source, continue reading. + +First, [install the build dependencies](#build_dependencies). + +To build bucts, do this in the main directory:\ +\$ **./oldbuild module bucts** + +To statically compile it, do this:\ +\$ **./oldbuild module bucts static** + +The \"builddeps\" script in libreboot\_src also makes use of +builddeps-bucts. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +How to build \"flashrom\" {#build_flashrom} +========================= + +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 +you proceed.** + +If you are using the binary release archive, then there are already +binaries included under ./flashrom/. The flashing scripts will try to +choose the correct one for you. Otherwise if you wish to re-build +flashrom from source, continue reading. + +First, [install the build dependencies](#build_dependencies). + +To build it, do the following in the main directory:\ +\$ **./oldbuild module flashrom** + +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 +executables: + +- **flashrom** + - For flashing while coreboot or libreboot is running. +- **flashrom\_lenovobios\_sst** + - This is patched for flashing while Lenovo BIOS is running on an + X60 or T60 with the SST25VF016B (SST) flash chip. +- **flashrom\_lenovobios\_macronix** + - This is patched for flashing while Lenovo BIOS is running on an + X60 or T60 with the MX25L1605D (Macronix) flash chip. + +The \"builddeps\" script in libreboot\_src also makes use of +builddeps-flashrom. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +How to build the ROM images {#build} +=========================== + +You don\'t need to do much, as there are scripts already written for you +that can build everything automatically. + +You can build libreboot from source on a 32-bit (i686) or 64-bit +(x86\_64) system. Recommended (if possible): x86\_64. ASUS KFSN4-DRE has +64-bit CPUs. On a ThinkPad T60, you can replace the CPU (Core 2 Duo +T5600, T7200 or T7600. T5600 recommended) for 64-bit support. On an +X60s, you can replace the board with one that has a Core 2 Duo L7400 +(you could also use an X60 Tablet board with the same CPU). On an X60, +you can replace the board with one that has a Core 2 Duo T5600 or T7200 +(T5600 is recommended). All MacBook2,1 laptops are 64-bit, as are all +ThinkPad X200, X200S, X200 Tablet, R400, T400 and T500 laptops. Warning: +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:\ +\$ **./oldbuild module all** + +You can also build each modules separately, using *./oldbuild module +modulename*. To see the possible values for *modulename*, use:\ +\$ **./oldbuild module list** + +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**\ +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:\ +\$ **./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. + +<div class="subsection"> + +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 +will also work in Devuan.** + +This is mainly intended for use with the git repository. These commands +will work in the release archive (\_src), unless otherwise noted below. + +The archives will appear under *release/oldbuildsystem/\${version}/*; +\${version} will either be set using *git describe* or, if a *version* +file already exists (\_src release archive), then it will simply re-use +that. + +Tag the current commit, and that version will appear in both the +\${version} string on the directory under *release/oldbuildsystem/*, and +in the file names of the archives. Otherwise, whatever git uses for *git +describe \--tags HEAD* will be used. + +Utilities (static executables):\ +\$ **./oldbuild release util** + +Archive containing flashrom and bucts source code:\ +\$ **./oldbuild release tobuild** + +Documentation archive (**does not work on \_src release archive, only +git**):\ +\$ **./oldbuild release docs** + +ROM image archives:\ +\$ **./oldbuild release roms** + +Source code archive:\ +\$ **./oldbuild release src** + +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 +32-bit binaries in the binary release archive that you created, for: +**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**, +**cbfstool** and **nvramtool**. + +**To include statically linked i686 and x86\_64 binaries for bucts and +flashrom, you will need to build them on a chroot, a virtual system or a +real system where the host uses each given architecture. These packages +are difficult to cross-compile, and the libreboot project is still +figuring out how to deal with them.** + +The same applies if you want to include statically linked flashrom +binaries for ARM. + +armv7l binaries (tested on a BeagleBone Black) are also included in +libreboot\_util, for: + +- cbfstool +- ich9gen +- ich9deblob +- 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**\ +\$ **./oldbuild module bucts static** + +The same conditions as above apply for ARM (except, building bucts on +ARM is pointless, and for flashrom you only need the normal executable +since the lenovobios\_sst and \_macronix executables are meant to run on +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**\ +The archive **tobuild.tar.xz** will have been created under +**release/oldbuildsystem/**, containing bucts, flashrom and all other +required resources for building them. + +You\'ll find that the files libreboot\_util.tar.xz and +libreboot\_src.tar.xz have been created, under +**release/oldbuildsystem/**. + +The ROM images will be stored in separate archives for each system, +under **release/oldbuildsystem/rom/**. + +</div> + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/gnulinux/configuring_parabola.html b/docs/gnulinux/configuring_parabola.html deleted file mode 100644 index ba4d7575..00000000 --- a/docs/gnulinux/configuring_parabola.html +++ /dev/null @@ -1,884 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Configuring Parabola (post-install)</title> -</head> - -<body> - <div class="section"> - <h1 id="pagetop">Configuring Parabola (post-install)</h1> - <p> - Post-installation configuration steps for Parabola GNU+Linux-libre. Parabola is extremely flexible; this is just an example. - This example uses LXDE because it's lightweight, but we recommend the <em>MATE</em> - desktop (which is actually about as lightweight as LXDE). - </p> - <p> - <a href="./">Back to previous index</a> - </p> - </div> - - <div class="section"> - - <h1>Table of Contents</h1> - <ul> - <li> - <a href="#pacman_configure">Configuring pacman</a> - <ul> - <li><a href="#pacman_update">Updating Parabola</a></li> - <li> - <a href="#pacman_maintain">Maintaining Parabola during system updates</a> - <ul> - <li><a href="#pacman_cacheclean">Clearing package cache after updating</a></li> - <li><a href="#pacman_commandequiv">Pacman command equivalents (compared to other package managers)</a></li> - </ul> - </li> - <li><a href="#yourfreedom">your-freedom</a></li> - </ul> - </li> - <li><a href="#useradd">Add a user account</a></li> - <li><a href="#systemd">System D</a></li> - <li><a href="#interesting_repos">Interesting repositories</a></li> - <li> - <a href="#network">Setup a network connection in Parabola</a> - <ul> - <li><a href="#network_hostname">Setting hostname</a></li> - <li><a href="#network_status">Network status</a></li> - <li><a href="#network_devicenames">Network interface names</a></li> - <li><a href="#network_setup">Network setup</a></li> - </ul> - </li> - <li><a href="#system_maintain">System maintenance</a> - important!</li> - <li> - <a href="#desktop">Configuring the desktop</a> - <ul> - <li><a href="#desktop_xorg">Install Xorg</a></li> - <li><a href="#desktop_kblayout">Xorg keyboard layout</a></li> - <li><a href="#desktop_lxde">Install LXDE</a></li> - <li><a href="#lxde_clock">LXDE - clock</a></li> - <li><a href="#lxde_font">LXDE - font</a></li> - <li><a href="#lxde_screenlock">LXDE - screenlock</a></li> - <li><a href="#lxde_automount">LXDE - automounting</a></li> - <li><a href="#lxde_suspend">LXDE - disable suspend</a></li> - <li><a href="#lxde_battery">LXDE - battery monitor</a></li> - <li><a href="#lxde_network">LXDE - network manager</a></li> - </ul> - </li> - </ul> - - </div> - - <div class="section"> - - <p> - 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. - </p> - - <p> - It details configuration steps that I took after installing the base system, - as a follow up to <a href="encrypted_parabola.html">encrypted_parabola.html</a>. - This guide is likely to become obsolete at a later date (due to the volatile - 'rolling-release' model that Arch/Parabola both use), but attempts will be made to maintain it. - </p> - - <p> - <b> - This guide was valid on 2014-09-21. If you see any changes that should to be made at the present date, please get in touch - with the libreboot project! - </b> - </p> - - </div> - - <div class="section"> - - <p> - You do not necessarily have to follow this guide word-for-word; <i>parabola</i> is extremely flexible. - The aim here is to provide a common setup that most users will be happy with. While Parabola - can seem daunting at first glance (especially for new GNU+Linux users), with a simple guide it can provide - all the same usability as Debian or Devuan, without hiding any details from the user. - </p> - - <p> - Paradoxically, as you get more advanced Parabola can actually become <i>easier to use</i> - when you want to set up your system in a special way compared to what most distributions provide. - You will find over time that other distributions tend to <i>get in your way</i>. - </p> - - </div> - - <div class="section"> - - <p> - <b> - This guide assumes that you already have Parabola installed. If you have not yet installed Parabola, - then <a href="encrypted_parabola.html">this guide</a> is highly recommended! - </b> - </p> - - <p> - A lot of the steps in this guide will refer to the Arch wiki. Arch is the upstream distribution that Parabola uses. - Most of this guide will also tell you to read wiki articles, other pages, manuals, and so on. In general it tries - to cherry pick the most useful information but nonetheless you are encouraged to learn as much as possible. - <b>It might take you a few days to fully install your system how you like, depending on how much you need to read. Patience is key, - especially for new users</b>. - </p> - - <p> - The Arch wiki will sometimes use bad language, such as calling the whole 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. - </p> - - </div> - - <div class="section"> - - <p> - 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:<br/> - # <b>systemctl start dhcpcd.service</b><br/> - You can stop it later by running:<br/> - # <b>systemctl stop dhcpcd.service</b><br/> - 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:<br/> - <a href="#network">Setup network connection in Parabola</a> - </p> - - </div> - - <div class="section"> - - <h2 id="pacman_configure">Configure pacman</h2> - <p> - pacman (<b>pac</b>kage <b>man</b>ager) is the name of the package management system in Arch, which Parabola - (as a deblobbed parallel effort) also uses. Like with 'apt-get' on Debian or Devuan, - this can be used to add/remove and update the software on your computer. - </p> - <p> - Based on <a href="https://wiki.parabolagnulinux.org/Installation_Guide#Configure_pacman">https://wiki.parabolagnulinux.org/Installation_Guide#Configure_pacman</a> - and from reading <a href="https://wiki.archlinux.org/index.php/Pacman">https://wiki.archlinux.org/index.php/Pacman</a> (make sure to read and understand this, - it's very important) and - <a href="https://wiki.parabolagnulinux.org/Official_Repositories">https://wiki.parabolagnulinux.org/Official_Repositories</a> - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="pacman_update">Updating Parabola</h2> - <p> - In the end, I didn't change my configuration for pacman. When you are updating, resync with the latest package names/versions:<br/> - # <b>pacman -Syy</b><br/> - (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).<br/> - Then, update the system:<br/> - # <b>pacman -Syu</b> - </p> - <p> - <b> - Before installing packages with 'pacman -S', always update first, using the notes above. - </b> - </p> - <p> - Keep an eye out on the output, or read it in /var/log/pacman.log. Sometimes, pacman will show messages - about maintenance steps that you will need to perform with certain files (typically configurations) - after the update. Also, you should check both the Parabola and Arch home pages to see if they mention any issues. - If a new kernel is installed, you should also update to be able to use it (the currently running kernel will - also be fine). It's generally good enough to update Parabola once every week, or maybe twice. As a - rolling release distribution, it's a good idea never to leave your install too outdated; update regularly. This - is simply because of the way the project works; old packages are deleted from the repositories quickly, once they are updated. - A system that hasn't been updated for quite a while will mean potentially more reading of previous posts through the website, - and more maintenance work. - </p> - <p> - The Arch forum can also be useful, if others have the same issue as you (if you encounter issues, that is). The <i>Parabola</i> - IRC channel (#parabola on freenode) can also help you. - </p> - <p> - 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 issues that need to be resolved. You should never update, for example, if you need your system for an important event, - like a presentation or sending an email to an important person before an allocated deadline, and so on. - </p> - <p> - Relax - packages are well-tested regularly when new updates are made to the repositories. Separate 'testing' repositories - exist for this exact reason. Despite what many people will tell you, Parabola is fairly stable and trouble-free, - so long as you are aware of how to check for issues, and are willing to spend some time fixing issues in - the rare event that they do occur. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="pacman_maintain">Maintaining Parabola</h2> - <p> - Parabola is a very simple distro, in the sense that you are in full control - and everything is made transparent to you. One consequence is - that you also need to know what you are doing, and what you have done before. In general, keeping notes (such as what I have done - with this page) can be very useful as a reference in the future (if you wanted to re-install it or install the distro - on another computer, for example). - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - <h3 id="pacman_cacheclean">Cleaning the package cache</h3> - <p> - <b> - The following is very important as you continue to use, update and maintain your Parabola system:<br/> - <a href="https://wiki.archlinux.org/index.php/Pacman#Cleaning_the_package_cache">https://wiki.archlinux.org/index.php/Pacman#Cleaning_the_package_cache</a>. - 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). - </b> - </p> - <p> - To clean out all old packages that are cached:<br/> - # <b>pacman -Sc</b> - </p> - <p> - 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 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. - </p> - <p> - The wiki also mentions this method for removing everything from the cache, including currently installed packages that are cached:<br/> - # <b>pacman -Scc</b><br/> - 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. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - <h3 id="pacman_commandequiv">pacman command equivalents</h3> - <p> - The following table lists other distro package manager commands, and their equivalent in pacman:<br/> - <a href="https://wiki.archlinux.org/index.php/Pacman_Rosetta">https://wiki.archlinux.org/index.php/Pacman_Rosetta</a> - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="yourfreedom">your-freedom</h2> - <p> - your-freedom is a package specific to Parabola, and it is installed by default. What it does is conflict with packages - from Arch that are known to be non-free (proprietary) software. When migrating from Arch (there is a guide on the Parabola - wiki for migrating - converting - an existing Arch system to a Parabola system), installing - your-freedom will also fail if these packages are installed, citing them as conflicts; the recommended solution - is then to delete the offending packages, and continue installing <i>your-freedom</i>. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="useradd">Add a user</h2> - <p> - Based on <a href="https://wiki.archlinux.org/index.php/Users_and_Groups">https://wiki.archlinux.org/index.php/Users_and_Groups</a>. - </p> - <p> - It is important (for security reasons) to create and use a non-root (non-admin) user account for everyday use. The default 'root' account is intended - only for critical administrative work, since it has complete access to the entire operating system. - </p> - <p> - Read the entire document linked to above, and then continue. - </p> - <p> - Add your user:<br/> - # <b>useradd -m -G wheel -s /bin/bash <i>yourusername</i></b><br/> - Set a password:<br/> - # <b>passwd <i>yourusername</i></b> - </p> - - <p> - Use of the <i>diceware method</i> is recommended, for generating secure passphrases (instead of passwords). - </p> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h2 id="systemd">systemd</h2> - <p> - This is the name of the system used for managing services in Parabola. It is a good idea to become familiar with it. - Read <a href="https://wiki.archlinux.org/index.php/systemd">https://wiki.archlinux.org/index.php/systemd</a> - and <a href="https://wiki.archlinux.org/index.php/systemd#Basic_systemctl_usage">https://wiki.archlinux.org/index.php/systemd#Basic_systemctl_usage</a> - to gain a full understanding. <b>This is very important! Make sure to read them.</b> - </p> - <p> - An example of a 'service' could be a webserver (such as lighttpd), or sshd (openssh), dhcp, etc. There are countless others. - </p> - <p> - <a href="https://bbs.archlinux.org/viewtopic.php?pid=1149530#p1149530">https://bbs.archlinux.org/viewtopic.php?pid=1149530#p1149530</a> explains - the background behind the decision by Arch (Parabola's upstream supplier) to use systemd. - </p> - - <p> - The manpage should also help:<br/> - # <b>man systemd</b><br/> - The section on 'unit types' is especially useful. - </p> - - <p> - According to the wiki, systemd 'journal' keeps logs of a size up to 10% of the total size your / partition takes up. - on a 60GB root this would mean 6GB. That's not exactly practical, and can have performance 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). - </p> - <p> - Open /etc/systemd/journald.conf and find the line that says:<br/> - <i>#SystemMaxUse=</i><br/> - Change it to say:<br/> - <i>SystemMaxUse=50M</i> - </p> - <p> - 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. - </p> - <p> - Restart journald:<br/> - # <b>systemctl restart systemd-journald</b> - </p> - - <p> - The wiki recommends that if the journal gets too large, you can also 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). - </p> - - <p> - Finally, the wiki mentions 'temporary' files and the utility for managing them.<br/> - # <b>man systemd-tmpfiles</b><br/> - The command for 'clean' is:<br/> - # <b>systemd-tmpfiles --clean</b><br/> - According to the manpage, this <i>"cleans all files and directories with an age parameter"</i>. - According to the Arch wiki, this reads information in /etc/tmpfiles.d/ and /usr/lib/tmpfiles.d/ - to know what actions to perform. Therefore, it is a good idea to read what's stored in these locations - to get a better understanding. - </p> - <p> - 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:<br/> - # <b>man tmpfiles.d</b><br/> - Read that manpage, and then continue studying all the files. - </p> - <p> - The systemd developers tell me that it isn't usually necessary to touch the systemd-tmpfiles utility manually at all. - </p> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h2 id="interesting_repos">Interesting repositories</h2> - <p> - Parabola wiki at <a href="https://wiki.parabolagnulinux.org/Repositories#kernels">https://wiki.parabolagnulinux.org/Repositories#kernels</a> - mentions about a repository called [kernels] for custom kernels that aren't in the default base. It might be worth looking into what is available - there, depending on your use case. - </p> - <p> - I enabled it on my system, to see what was in it. Edit /etc/pacman.conf and below the 'extra' section add:<br/> - <i> - [kernels]<br/> - Include = /etc/pacman.d/mirrorlist - </i> - </p> - <p> - Now sync with the repository:<br/> - # <b>pacman -Syy</b> - </p> - <p> - List all available packages in this repository:<br/> - # <b>pacman -Sl kernels</b> - </p> - <p> - In the end, I decided not to install anything from it but I kept the repository enabled regardless. - </p> - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h2 id="network">Setup a network connection in Parabola</h2> - <p> - Read <a href="https://wiki.archlinux.org/index.php/Configuring_Network">https://wiki.archlinux.org/index.php/Configuring_Network</a>. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - <h3 id="network_hostname">Set the hostname</h3> - <p> - 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):<br/> - # <b>hostnamectl set-hostname <i>yourhostname</i></b><br/> - This writes the specified hostname to /etc/hostname. More information can be found in these manpages:<br/> - # <b>man hostname</b><br/> - # <b>info hostname</b><br/> - # <b>man hostnamectl</b> - </p> - <p> - Add the same hostname to /etc/hosts, on each line. Example:<br/> - <i> - 127.0.0.1 localhost.localdomain localhost <u>myhostname</u><br/> - ::1 localhost.localdomain localhost <u>myhostname</u> - </i> - </p> - <p> - You'll note that I set both lines; the 2nd line is for IPv6. More and more ISPs are providing this now (mine does) - so it's good to be forward-thinking here. - </p> - <p> - The <i>hostname</i> utility is part of the <i>inetutils</i> package and is in core/, installed by default (as part of <i>base</i>). - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - <h3 id="network_status">Network Status</h3> - <p> - According to the Arch wiki, <a href="https://wiki.archlinux.org/index.php/Udev">udev</a> should already detect the ethernet chipset - and load the driver for it automatically at boot time. You can check this in the <i>"Ethernet controller"</i> section - when running this command:<br/> - # <b>lspci -v</b> - </p> - <p> - Look at the remaining sections <i>'Kernel driver in use'</i> and <i>'Kernel modules'</i>. In my case it was as follows:<br/> - <i> - Kernel driver in use: e1000e<br/> - Kernel modules: e1000e - </i> - </p> - <p> - Check that the driver was loaded by issuing <i>dmesg | grep module_name</i>. In my case, I did:<br/> - # <b>dmesg | grep e1000e</b> - </p> - <h3 id="network_devicenames">Network device names</h3> - <p> - According to <a href="https://wiki.archlinux.org/index.php/Configuring_Network#Device_names">https://wiki.archlinux.org/index.php/Configuring_Network#Device_names</a>, - it is important to note that the old interface names like eth0, wlan0, wwan0 and so on no longer apply. Instead, <i>systemd</i> - creates device names starting with en (for enternet), wl (for wifi) and ww (for wwan) with a fixed identifier that systemd automatically generates. - An example device name for your ethernet chipset would be <i>enp0s25</i>, where it is never supposed to change. - </p> - <p> - If you want to enable the old names (eth0, wlan0, wwan0, etc), the Arch wiki recommends - adding <i>net.ifnames=0</i> to your kernel parameters (in libreboot context, this would be accomplished by following the - instructions in <a href="grub_cbfs.html">grub_cbfs.html</a>). - </p> - <p> - For background information, - read <a href="http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/">Predictable Network Interface Names</a> - </p> - <p> - Show device names:<br/> - # <b>ls /sys/class/net</b> - </p> - <p> - Changing the device names is possible (I chose not to do it):<br/> - <a href="https://wiki.archlinux.org/index.php/Configuring_Network#Change_device_name">https://wiki.archlinux.org/index.php/Configuring_Network#Change_device_name</a> - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - <h3 id="network_setup">Network setup</h3> - <p> - 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:<br/> - <a href="https://wiki.archlinux.org/index.php/List_of_applications/Internet#Network_managers">https://wiki.archlinux.org/index.php/List_of_applications/Internet#Network_managers</a>. - If you need to, set a static IP address (temporarily) using the networking guide and the Arch wiki, or start the dhcpcd service in systemd. - NetworkManager will be setup later, after installing LXDE. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="system_maintain">System Maintenance</h2> - <p> - Read <a href="https://wiki.archlinux.org/index.php/System_maintenance">https://wiki.archlinux.org/index.php/System_maintenance</a> before continuing. - Also read <a href="https://wiki.archlinux.org/index.php/Enhance_system_stability">https://wiki.archlinux.org/index.php/Enhance_system_stability</a>. - <b>This is important, so make sure to read them!</b> - </p> - <p> - 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):<br/> - # <b>pacman -S smartmontools</b><br/> - Read <a href="https://wiki.archlinux.org/index.php/S.M.A.R.T.">https://wiki.archlinux.org/index.php/S.M.A.R.T.</a> to learn how to use it. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="desktop">Configuring the desktop</h2> - <p> - Based on steps from - <a href="https://wiki.archlinux.org/index.php/General_recommendations#Graphical_user_interface">General Recommendations</a> on the Arch wiki. - The plan is to use LXDE and LXDM/LightDM, along with everything else that you would expect on other distributions that provide LXDE - by default. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - <div class="subsection"> - <h3 id="desktop_xorg">Installing Xorg</h3> - <p> - Based on <a href="https://wiki.archlinux.org/index.php/Xorg">https://wiki.archlinux.org/index.php/Xorg</a>. - </p> - <p> - Firstly, install it!<br/> - # <b>pacman -S xorg-server</b><br/> - I also recommend installing this (contains lots of useful tools, including <i>xrandr</i>):<br/> - # <b>pacman -S xorg-server-utils</b> - </p> - <p> - Install the driver. For me this was <i>xf86-video-intel</i> on the ThinkPad X60. T60 and macbook11/21 should be the same.<br/> - # <b>pacman -S xf86-video-intel</b><br/> - For other systems you can try:<br/> - # <b>pacman -Ss xf86-video- | less</b><br/> - Combined with looking at your <i>lspci</i> 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. - </p> - <p> - Other drivers (not just video) can be found by looking at the <i>xorg-drivers</i> group:<br/> - # <b>pacman -Sg xorg-drivers</b><br/> - </p> - <p> - Mostly you will rely on a display manager, but in case you ever want to start X without one:<br/> - # <b>pacman -S xorg-xinit</b> - </p> - <p> - <optional><br/> - Arch wiki recommends installing these, for testing that X works:<br/> - # <b>pacman -S xorg-twm xorg-xclock xterm</b><br/> - Refer to <a href="https://wiki.archlinux.org/index.php/Xinitrc">https://wiki.archlinux.org/index.php/Xinitrc</a>. - and test X:<br/> - # <b>startx</b><br/> - When you are satisfied, type <b><i>exit</i></b> in xterm, inside the X session.<br/> - Uninstall them (clutter. eww): # <b>pacman -S xorg-xinit xorg-twm xorg-xclock xterm</b><br/> - </optional> - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - </div> - - <div class="subsection"> - <h3 id="desktop_kblayout">Xorg keyboard layout</h3> - <p> - Refer to <a href="https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg">https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg</a>. - </p> - <p> - Xorg uses a different configuration method for keyboard layouts, so you will notice that the layout you - set in /etc/vconsole.conf earlier might not actually be the same in X. - </p> - <p> - To see what layout you currently use, try this on a terminal emulator in X:<br/> - # <b>setxkbmap -print -verbose 10</b> - </p> - <p> - In my case, I wanted to use the Dvorak (UK) keyboard which is quite different from Xorg's default Qwerty (US) layout. - </p> - <p> - I'll just say it now: <i>XkbModel</i> can be <i>pc105</i> in this case (ThinkPad X60, with a 105-key UK keyboard). - If you use an American keyboard (typically 104 keys) you will want to use <i>pc104</i>. - </p> - <p> - <i>XkbLayout</i> in my case would be <i>gb</i>, and <i>XkbVariant</i> would be <i>dvorak</i>. - </p> - <p> - The Arch wiki recommends two different methods for setting the keyboard layout:<br/> - <a href="https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_X_configuration_files">https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_X_configuration_files</a> and<br/> - <a href="https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_localectl">https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_localectl</a>. - </p> - <p> - In my case, I chose to use the <i>configuration file</i> method:<br/> - Create the file /etc/X11/xorg.conf.d/10-keyboard.conf and put this inside:<br/> - <i> - Section "InputClass"<br/> - Identifier "system-keyboard"<br/> - MatchIsKeyboard "on"<br/> - Option "XkbLayout" "gb"<br/> - Option "XkbModel" "pc105"<br/> - Option "XkbVariant" "dvorak"<br/> - EndSection - </i> - </p> - <p> - For you, the steps above may differ if you have a different layout. If you use a US Qwerty keyboard, then - you don't even need to do anything (though it might help, for the sake of being explicit). - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - </div> - - <div class="subsection"> - <h3 id="desktop_lxde">Install LXDE</h3> - <p> - Desktop choice isn't that important to me, so for simplicity I decided to use LXDE. It's lightweight - and does everything that I need. - If you would like to try something different, refer to - <a href="https://wiki.archlinux.org/index.php/Desktop_environment">https://wiki.archlinux.org/index.php/Desktop_environment</a> - </p> - <p> - Refer to <a href="https://wiki.archlinux.org/index.php/LXDE">https://wiki.archlinux.org/index.php/LXDE</a>. - </p> - <p> - Install it, choosing 'all' when asked for the default package list:<br/> - # <b>pacman -S lxde obconf</b> - </p> - <p> - I didn't want the following, so I removed them:<br/> - # <b>pacman -R lxmusic lxtask</b> - </p> - <p> - I also lazily installed all fonts:<br/> - # <b>pacman -S $(pacman -Ssq ttf-)</b> - </p> - <p> - And a mail client:<br/> - # <b>pacman -S icedove</b> - </p> - <p> - In IceCat, go to <i>Preferences :: Advanced</i> and disable <i>GNU IceCat Health Report</i>. - </p> - <p> - I also like to install these:<br/> - # <b>pacman -S xsensors stress htop</b> - </p> - <p> - Enable LXDM (the default display manager, providing a graphical login):<br/> - # <b>systemctl enable lxdm.service</b><br/> - It will start when you boot up the system. To start it now, do:<br/> - # <b>systemctl start lxdm.service</b> - </p> - <p> - 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 <a href="https://wiki.archlinux.org/index.php/Xinitrc">https://wiki.archlinux.org/index.php/Xinitrc</a>. - </p> - <p> - Open LXterminal:<br/> - $ <b>cp /etc/skel/.xinitrc ~</b><br/> - Open .xinitrc and add the following plus a line break at the bottom of the file.<br/> - <i> - # Probably not needed. The same locale info that we set before<br/> - # Based on advice from the LXDE wiki - export LC_ALL=en_GB.UTF-8<br/> - export LANGUAGE=en_GB.UTF-8<br/> - export LANG=en_GB.UTF-8<br/> - <br/> - # Start lxde desktop<br/> - exec startlxde<br/> - </i> - Now make sure that it is executable:<br/> - $ <b>chmod +x .xinitrc</b> - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - </div> - - <div class="subsection"> - <h3 id="lxde_clock">LXDE - clock</h3> - <p> - In <b>Digital Clock Settings</b> (right click the clock) I set the Clock Format to <i>%Y/%m/%d %H:%M:%S</i> - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - </div> - - <div class="subsection"> - <h3 id="lxde_font">LXDE - font</h3> - <p> - NOTE TO SELF: come back to this later. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - </div> - - <div class="subsection"> - <h3 id="lxde_screenlock">LXDE - screenlock</h3> - <p> - Arch wiki recommends to use <i>xscreensaver</i>:<br/> - # <b>pacman -S xscreensaver</b> - </p> - <p> - Under <i>Preferences :: Screensaver</i> in the LXDE menu, I chose <i>Mode: Blank Screen Only</i>, - setting <i>Blank After</i>, <i>Cycle After</i> and <i>Lock Screen After</i> (checked) to 10 minutes. - </p> - <p> - You can now lock the screen with <i>Logout :: Lock Screen</i> in the LXDE menu. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - </div> - - <div class="subsection"> - <h3 id="lxde_automount">LXDE - automounting</h3> - <p> - Refer to <a href="https://wiki.archlinux.org/index.php/File_manager_functionality">https://wiki.archlinux.org/index.php/File_manager_functionality</a>. - </p> - <p> - I chose to ignore this for now. NOTE TO SELF: come back to this later. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - </div> - - <div class="subsection"> - <h3 id="lxde_suspend">LXDE - disable suspend</h3> - <p> - When closing the laptop lid, the system suspends. This is annoying at least to me. - NOTE TO SELF: disable it, then document the steps here. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - </div> - - <div class="subsection"> - <h3 id="lxde_battery">LXDE - battery monitor</h3> - <p> - Right click lxde panel and <i>Add/Remove Panel Items</i>. Click <i>Add</i> and select <i>Battery Monitor</i>, then click <i>Add</i>. - Close and then right-click the applet and go to <i>Battery Monitor Settings</i>, check the box that says <i>Show Extended Information</i>. - Now click <i>Close</i>. When you hover the cursor over it, it'll show information about the battery. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - </div> - - <div class="subsection"> - <h3 id="lxde_network">LXDE - Network Manager</h3> - <p> - Refer to <a href="https://wiki.archlinux.org/index.php/LXDE#Network_Management">https://wiki.archlinux.org/index.php/LXDE#Network_Management</a>. - Then I read: <a href="https://wiki.archlinux.org/index.php/NetworkManager">https://wiki.archlinux.org/index.php/NetworkManager</a>. - </p> - <p> - Install Network Manager:<br/> - # <b>pacman -S networkmanager</b> - </p> - <p> - You will also want the graphical applet:<br/> - # <b>pacman -S network-manager-applet</b><br/> - Arch wiki says that an autostart rule will be written at <i>/etc/xdg/autostart/nm-applet.desktop</i> - </p> - <p> - I want to be able to use a VPN at some point, so the wiki tells me to do:<br/> - # <b>pacman -S networkmanager-openvpn</b> - </p> - <p> - LXDE uses openbox, so I refer to:<br/> - <a href="https://wiki.archlinux.org/index.php/NetworkManager#Openbox">https://wiki.archlinux.org/index.php/NetworkManager#Openbox</a>. - </p> - <p> - It tells me for the applet I need:<br/> - # <b>pacman -S xfce4-notifyd gnome-icon-theme</b><br/> - Also, for storing authentication details (wifi) I need:<br/> - # <b>pacman -S gnome-keyring</b> - </p> - <p> - I wanted to quickly enable networkmanager:<br/> - # <b>systemctl stop dhcpcd</b><br/> - # <b>systemctl start NetworkManager</b><br/> - Enable NetworkManager at boot time:<br/> - # <b>systemctl enable NetworkManager</b> - </p> - <p> - Restart LXDE (log out, and then log back in). - </p> - <p> - I added the volume control applet to the panel (right click panel, and add a new applet). - I also later changed the icons to use the gnome icon theme, in <i>lxappearance</i>. - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - </div> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md new file mode 100644 index 00000000..24278ba6 --- /dev/null +++ b/docs/gnulinux/configuring_parabola.md @@ -0,0 +1,827 @@ +<div class="section"> + +Configuring Parabola (post-install) {#pagetop} +=================================== + +Post-installation configuration steps for Parabola GNU+Linux-libre. +Parabola is extremely flexible; this is just an example. This example +uses LXDE because it\'s lightweight, but we recommend the *MATE* desktop +(which is actually about as lightweight as LXDE). + +[Back to previous index](./) + +</div> + +<div class="section"> + +Table of Contents +================= + +- [Configuring pacman](#pacman_configure) + - [Updating Parabola](#pacman_update) + - [Maintaining Parabola during system updates](#pacman_maintain) + - [Clearing package cache after updating](#pacman_cacheclean) + - [Pacman command equivalents (compared to other package + managers)](#pacman_commandequiv) + - [your-freedom](#yourfreedom) +- [Add a user account](#useradd) +- [System D](#systemd) +- [Interesting repositories](#interesting_repos) +- [Setup a network connection in Parabola](#network) + - [Setting hostname](#network_hostname) + - [Network status](#network_status) + - [Network interface names](#network_devicenames) + - [Network setup](#network_setup) +- [System maintenance](#system_maintain) - important! +- [Configuring the desktop](#desktop) + - [Install Xorg](#desktop_xorg) + - [Xorg keyboard layout](#desktop_kblayout) + - [Install LXDE](#desktop_lxde) + - [LXDE - clock](#lxde_clock) + - [LXDE - font](#lxde_font) + - [LXDE - screenlock](#lxde_screenlock) + - [LXDE - automounting](#lxde_automount) + - [LXDE - disable suspend](#lxde_suspend) + - [LXDE - battery monitor](#lxde_battery) + - [LXDE - network manager](#lxde_network) + +</div> + +<div class="section"> + +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. + +It details configuration steps that I took after installing the base +system, as a follow up to +[encrypted\_parabola.html](encrypted_parabola.html). This guide is +likely to become obsolete at a later date (due to the volatile +\'rolling-release\' model that Arch/Parabola both use), but attempts +will be made to maintain it. + +**This guide was valid on 2014-09-21. If you see any changes that should +to be made at the present date, please get in touch with the libreboot +project!** + +</div> + +<div class="section"> + +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 +daunting at first glance (especially for new GNU+Linux users), with a +simple guide it can provide all the same usability as Debian or Devuan, +without hiding any details from the user. + +Paradoxically, as you get more advanced Parabola can actually become +*easier to use* when you want to set up your system in a special way +compared to what most distributions provide. You will find over time +that other distributions tend to *get in your way*. + +</div> + +<div class="section"> + +**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!** + +A lot of the steps in this guide will refer to the Arch wiki. Arch is +the upstream distribution that Parabola uses. Most of this guide will +also tell you to read wiki articles, other pages, manuals, and so on. In +general it tries to cherry pick the most useful information but +nonetheless you are encouraged to learn as much as possible. **It might +take you a few days to fully install your system how you like, depending +on how much you need to read. Patience is key, especially for new +users**. + +The Arch wiki will sometimes use bad language, such as calling the whole +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. + +</div> + +<div class="section"> + +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:\ +[Setup network connection in Parabola](#network) + +</div> + +<div class="section"> + +Configure pacman {#pacman_configure} +---------------- + +pacman (**pac**kage **man**ager) is the name of the package management +system in Arch, which Parabola (as a deblobbed parallel effort) also +uses. Like with \'apt-get\' on Debian or Devuan, this can be used to +add/remove and update the software on your computer. + +Based on +<https://wiki.parabolagnulinux.org/Installation_Guide#Configure_pacman> +and from reading <https://wiki.archlinux.org/index.php/Pacman> (make +sure to read and understand this, it\'s very important) and +<https://wiki.parabolagnulinux.org/Official_Repositories> + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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**\ +(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** + +**Before installing packages with \'pacman -S\', always update first, +using the notes above.** + +Keep an eye out on the output, or read it in /var/log/pacman.log. +Sometimes, pacman will show messages about maintenance steps that you +will need to perform with certain files (typically configurations) after +the update. Also, you should check both the Parabola and Arch home pages +to see if they mention any issues. If a new kernel is installed, you +should also update to be able to use it (the currently running kernel +will also be fine). It\'s generally good enough to update Parabola once +every week, or maybe twice. As a rolling release distribution, it\'s a +good idea never to leave your install too outdated; update regularly. +This is simply because of the way the project works; old packages are +deleted from the repositories quickly, once they are updated. A system +that hasn\'t been updated for quite a while will mean potentially more +reading of previous posts through the website, and more maintenance +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. + +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 +issues that need to be resolved. You should never update, for example, +if you need your system for an important event, like a presentation or +sending an email to an important person before an allocated deadline, +and so on. + +Relax - packages are well-tested regularly when new updates are made to +the repositories. Separate \'testing\' repositories exist for this exact +reason. Despite what many people will tell you, Parabola is fairly +stable and trouble-free, so long as you are aware of how to check for +issues, and are willing to spend some time fixing issues in the rare +event that they do occur. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Maintaining Parabola {#pacman_maintain} +-------------------- + +Parabola is a very simple distro, in the sense that you are in full +control and everything is made transparent to you. One consequence is +that you also need to know what you are doing, and what you have done +before. In general, keeping notes (such as what I have done with this +page) can be very useful as a reference in the future (if you wanted to +re-install it or install the distro on another computer, for example). + +[Back to top of page.](#pagetop) + +### Cleaning the package cache {#pacman_cacheclean} + +**The following is very important as you continue to use, update and +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** + +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 +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**\ +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. + +[Back to top of page.](#pagetop) + +### pacman command equivalents {#pacman_commandequiv} + +The following table lists other distro package manager commands, and +their equivalent in pacman:\ +<https://wiki.archlinux.org/index.php/Pacman_Rosetta> + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +your-freedom {#yourfreedom} +------------ + +your-freedom is a package specific to Parabola, and it is installed by +default. What it does is conflict with packages from Arch that are known +to be non-free (proprietary) software. When migrating from Arch (there +is a guide on the Parabola wiki for migrating - converting - an existing +Arch system to a Parabola system), installing your-freedom will also +fail if these packages are installed, citing them as conflicts; the +recommended solution is then to delete the offending packages, and +continue installing *your-freedom*. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Add a user {#useradd} +---------- + +Based on <https://wiki.archlinux.org/index.php/Users_and_Groups>. + +It is important (for security reasons) to create and use a non-root +(non-admin) user account for everyday use. The default \'root\' account +is intended only for critical administrative work, since it has complete +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*** + +Use of the *diceware method* is recommended, for generating secure +passphrases (instead of passwords). + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +systemd +------- + +This is the name of the system used for managing services in Parabola. +It is a good idea to become familiar with it. Read +<https://wiki.archlinux.org/index.php/systemd> and +<https://wiki.archlinux.org/index.php/systemd#Basic_systemctl_usage> to +gain a full understanding. **This is very important! Make sure to read +them.** + +An example of a \'service\' could be a webserver (such as lighttpd), or +sshd (openssh), dhcp, etc. There are countless others. + +<https://bbs.archlinux.org/viewtopic.php?pid=1149530#p1149530> explains +the background behind the decision by Arch (Parabola\'s upstream +supplier) to use 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 +10% of the total size your / partition takes up. on a 60GB root this +would mean 6GB. That\'s not exactly practical, and can have performance +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:\ +*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** + +The wiki recommends that if the journal gets too large, you can also +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**\ +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 +perform. Therefore, it is a good idea to read what\'s stored in these +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**\ +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) + +</div> + +<div class="section"> + +Interesting repositories {#interesting_repos} +------------------------ + +Parabola wiki at +<https://wiki.parabolagnulinux.org/Repositories#kernels> mentions about +a repository called \[kernels\] for custom kernels that aren\'t in the +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\]\ +Include = /etc/pacman.d/mirrorlist* + +Now sync with the repository:\ +\# **pacman -Syy** + +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) + +</div> + +<div class="section"> + +Setup a network connection in Parabola {#network} +-------------------------------------- + +Read <https://wiki.archlinux.org/index.php/Configuring_Network>. + +[Back to top of page.](#pagetop) + +### Set the hostname {#network_hostname} + +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***\ +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\ +::1 localhost.localdomain localhost myhostname* + +You\'ll note that I set both lines; the 2nd line is for IPv6. More and +more ISPs are providing this now (mine does) so it\'s good to be +forward-thinking here. + +The *hostname* utility is part of the *inetutils* package and is in +core/, installed by default (as part of *base*). + +[Back to top of page.](#pagetop) + +### Network Status {#network_status} + +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** + +Look at the remaining sections *\'Kernel driver in use\'* and *\'Kernel +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** + +### Network device names {#network_devicenames} + +According to +<https://wiki.archlinux.org/index.php/Configuring_Network#Device_names>, +it is important to note that the old interface names like eth0, wlan0, +wwan0 and so on no longer apply. Instead, *systemd* creates device names +starting with en (for enternet), wl (for wifi) and ww (for wwan) with a +fixed identifier that systemd automatically generates. An example device +name for your ethernet chipset would be *enp0s25*, where it is never +supposed to change. + +If you want to enable the old names (eth0, wlan0, wwan0, etc), the Arch +wiki recommends adding *net.ifnames=0* to your kernel parameters (in +libreboot context, this would be accomplished by following the +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):\ +<https://wiki.archlinux.org/index.php/Configuring_Network#Change_device_name> + +[Back to top of page.](#pagetop) + +### Network setup {#network_setup} + +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:\ +<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 +systemd. NetworkManager will be setup later, after installing LXDE. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +System Maintenance {#system_maintain} +------------------ + +Read <https://wiki.archlinux.org/index.php/System_maintenance> before +continuing. Also read +<https://wiki.archlinux.org/index.php/Enhance_system_stability>. **This +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**\ +Read <https://wiki.archlinux.org/index.php/S.M.A.R.T.> to learn how to +use it. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Configuring the desktop {#desktop} +----------------------- + +Based on steps from [General +Recommendations](https://wiki.archlinux.org/index.php/General_recommendations#Graphical_user_interface) +on the Arch wiki. The plan is to use LXDE and LXDM/LightDM, along with +everything else that you would expect on other distributions that +provide LXDE by default. + +[Back to top of page.](#pagetop) + +<div class="subsection"> + +### Installing Xorg {#desktop_xorg} + +Based on <https://wiki.archlinux.org/index.php/Xorg>. + +Firstly, install it!\ +\# **pacman -S xorg-server**\ +I also recommend installing this (contains lots of useful tools, +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**\ +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**\ + +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**\ + 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**\ +</optional> + +[Back to top of page.](#pagetop) + +</div> + +<div class="subsection"> + +### Xorg keyboard layout {#desktop_kblayout} + +Refer to +<https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg>. + +Xorg uses a different configuration method for keyboard layouts, so you +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** + +In my case, I wanted to use the Dvorak (UK) keyboard which is quite +different from Xorg\'s default Qwerty (US) layout. + +I\'ll just say it now: *XkbModel* can be *pc105* in this case (ThinkPad +X60, with a 105-key UK keyboard). If you use an American keyboard +(typically 104 keys) you will want to use *pc104*. + +*XkbLayout* in my case would be *gb*, and *XkbVariant* would be +*dvorak*. + +The Arch wiki recommends two different methods for setting the keyboard +layout:\ +<https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_X_configuration_files> +and\ +<https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_localectl>. + +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\"\ +EndSection* + +For you, the steps above may differ if you have a different layout. If +you use a US Qwerty keyboard, then you don\'t even need to do anything +(though it might help, for the sake of being explicit). + +[Back to top of page.](#pagetop) + +</div> + +<div class="subsection"> + +### Install LXDE {#desktop_lxde} + +Desktop choice isn\'t that important to me, so for simplicity I decided +to use LXDE. It\'s lightweight and does everything that I need. If you +would like to try something different, refer to +<https://wiki.archlinux.org/index.php/Desktop_environment> + +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** + +I also lazily installed all fonts:\ +\# **pacman -S \$(pacman -Ssq ttf-)** + +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:\ +\# **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 .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:\ +\$ **chmod +x .xinitrc** + +[Back to top of page.](#pagetop) + +</div> + +<div class="subsection"> + +### LXDE - clock {#lxde_clock} + +In **Digital Clock Settings** (right click the clock) I set the Clock +Format to *%Y/%m/%d %H:%M:%S* + +[Back to top of page.](#pagetop) + +</div> + +<div class="subsection"> + +### LXDE - font {#lxde_font} + +NOTE TO SELF: come back to this later. + +[Back to top of page.](#pagetop) + +</div> + +<div class="subsection"> + +### 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 +Screen After* (checked) to 10 minutes. + +You can now lock the screen with *Logout :: Lock Screen* in the LXDE +menu. + +[Back to top of page.](#pagetop) + +</div> + +<div class="subsection"> + +### LXDE - automounting {#lxde_automount} + +Refer to +<https://wiki.archlinux.org/index.php/File_manager_functionality>. + +I chose to ignore this for now. NOTE TO SELF: come back to this later. + +[Back to top of page.](#pagetop) + +</div> + +<div class="subsection"> + +### LXDE - disable suspend {#lxde_suspend} + +When closing the laptop lid, the system suspends. This is annoying at +least to me. NOTE TO SELF: disable it, then document the steps here. + +[Back to top of page.](#pagetop) + +</div> + +<div class="subsection"> + +### LXDE - battery monitor {#lxde_battery} + +Right click lxde panel and *Add/Remove Panel Items*. Click *Add* and +select *Battery Monitor*, then click *Add*. Close and then right-click +the applet and go to *Battery Monitor Settings*, check the box that says +*Show Extended Information*. Now click *Close*. When you hover the +cursor over it, it\'ll show information about the battery. + +[Back to top of page.](#pagetop) + +</div> + +<div class="subsection"> + +### 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:\ +\# **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:\ +<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** + +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). + +I added the volume control applet to the panel (right click panel, and +add a new applet). I also later changed the icons to use the gnome icon +theme, in *lxappearance*. + +[Back to top of page.](#pagetop) + +</div> + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/gnulinux/encrypted_debian.html b/docs/gnulinux/encrypted_debian.html deleted file mode 100644 index 1201d4ce..00000000 --- a/docs/gnulinux/encrypted_debian.html +++ /dev/null @@ -1,495 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Installing Debian or Devuan GNU+Linux with full disk encryption (including /boot)</title> -</head> - -<body> - <div class="section"> - <h1>Installing Debian or Devuan GNU+Linux with full disk encryption (including /boot)</h1> - <p> - This guide is written for the Debian distribution, but it should - also work for Devuan with the net installer. - </p> - <p> - Libreboot on x86 uses the GRUB <a href="http://www.coreboot.org/Payloads#GRUB_2">payload</a> - by default, which means that the GRUB configuration file - (where your GRUB menu comes from) is stored directly alongside libreboot - and its GRUB payload executable, inside - the flash chip. In context, this means that installing distributions and managing them - is handled slightly differently compared to traditional BIOS systems. - </p> - - <p> - On most systems, the /boot partition has to be left unencrypted while the others are encrypted. - This is so that GRUB, and therefore the kernel, can be loaded and executed since the firmware - can't open a LUKS 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. - </p> - <p> - This guide is written for Debian net installer. You can download the ISO from the homepage on - <a href="https://www.debian.org/">debian.org</a>. - Use this on the GRUB terminal to boot it from USB (for 64-bit Intel or AMD):<br/> - <strong> - set root='usb0'<br/> - linux /install.amd/vmlinuz<br/> - initrd /install.amd/initrd.gz<br/> - boot<br/> - </strong> - If you are on a 32-bit system (e.g. X60):<br/> - <strong> - set root='usb0'<br/> - linux /install.386/vmlinuz<br/> - initrd /install.386/initrd.gz<br/> - boot - </strong> - </p> - <p> - <a href="grub_boot_installer.html">This guide</a> shows how to - create a boot USB drive with the Debian ISO image. - </p> - <p> - <b>This guide is *only* for the GRUB payload. If you use the depthcharge payload, ignore this section entirely.</b> - </p> - - - <p> - Note: on some thinkpads, a faulty DVD drive can cause the cryptomount -a step during boot to fail. If this happens to you, try removing the drive. - </p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - - <p> - Set a strong user password (lots of lowercase/uppercase, numbers and symbols). - </p> - - <p> - Use of the <i>diceware method</i> is recommended, for generating secure passphrases (instead of passwords). - </p> - - <p> - when the installer asks you to set up - encryption (ecryptfs) for your home directory, select 'Yes' if you want to: <b>LUKS is already secure and performs well. Having ecryptfs on top of it - will add noticeable performance penalty, for little security gain in most use cases. This is therefore optional, and not recommended. - Choose 'no'.</b> - </p> - - <p> - <b> - Your user password should be different from the LUKS password which you will set later on. - Your LUKS password should, like the user password, be secure. - </b> - </p> - - </div> - - <div class="section"> - - <h1>Partitioning</h1> - - <p>Choose 'Manual' partitioning:</p> - <ul> - <li>Select drive and create new partition table</li> - <li> - Single large partition. The following are mostly defaults: - <ul> - <li>Use as: physical volume for encryption</li> - <li>Encryption: aes</li> - <li>key size: whatever default is given to you</li> - <li>IV algorithm: whatever default is given to you</li> - <li>Encryption key: passphrase</li> (<i>diceware method</i> recommended for choosing password) - <li>erase data: Yes (only choose 'No' if it's a new drive that doesn't contain your private data)</li> - </ul> - </li> - <li> - Select 'configure encrypted volumes' - <ul> - <li>Create encrypted volumes</li> - <li>Select your partition</li> - <li>Finish</li> - <li>Really erase: Yes</li> - <li>(erase will take a long time. be patient)</li> - <li>(if your old system was encrypted, just let this run for about a minute to - make sure that the LUKS header is wiped out)</li> - </ul> - </li> - <li> - Select encrypted space: - <ul> - <li>use as: physical volume for LVM</li> - <li>Choose 'done setting up the partition'</li> - </ul> - </li> - <li> - Configure the logical volume manager: - <ul> - <li>Keep settings: Yes</li> - </ul> - </li> - <li> - Create volume group: - <ul> - <li>Name: <b>matrix</b> (use this exact name)</li> - <li>Select crypto partition</li> - </ul> - </li> - <li> - Create logical volume - <ul> - <li>select <b>matrix</b> (use this exact name)</li> - <li>name: <b>rootvol</b> (use this exact name)</li> - <li>size: default, minus 2048 MB</li> - </ul> - </li> - <li> - Create logical volume - <ul> - <li>select <b>matrix</b> (use this exact name)</li> - <li>name: <b>swap</b> (user this exact name)</li> - <li>size: press enter</li> - </ul> - </li> - </ul> - - </div> - - <div class="section"> - - <h1>Further partitioning</h1> - - <p> - Now you are back at the main partitioning screen. You will simply set mountpoints and filesystems to use. - </p> - <ul> - <li> - LVM LV rootvol - <ul> - <li>use as: btrfs</li> - <li>mount point: /</li> - <li>done setting up partition</li> - </ul> - </li> - <li> - LVM LV swap - <ul> - <li>use as: swap area</li> - <li>done setting up partition</li> - </ul> - </li> - <li>Now you select 'Finished partitioning and write changes to disk'.</li> - </ul> - - </div> - - <div class="section"> - - <h1>Kernel</h1> - - <p> - Installation will ask what kernel you want to use. linux-generic is fine. - </p> - - </div> - - <div class="section"> - - <h1>Tasksel</h1> - - <p> - For Debian, use the <em>MATE</em> option, or one of the others if you want. - The libreboot project recommends MATE, unless you're saavy enough to choose something - else. - </p> - <p> - If you want debian-testing, then you should only select barebones options here - and change the entries in /etc/apt/sources.list after install to point to the new distro, - and then run <strong>apt-get update</strong> and <strong>apt-get dist-upgrade</strong> - as root, then reboot and run <b>tasksel</b> as root. This is to avoid downloading large - packages twice. - </p> - <p> - NOTE: If you want the latest up to date version of the Linux kernel, - Debian's kernel is sometimes outdated, even in the testing distro. - You might consider using <a href="https://jxself.org/linux-libre/">this repository</a> - 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. - </p> - - </div> - - <div class="section"> - - <h1>Postfix configuration</h1> - - <p> - If asked, choose <i>"No Configuration"</i> here (or maybe you want to select something else. It's up to you.) - </p> - - </div> - - <div class="section"> - - <h1>Install the GRUB boot loader to the master boot record</h1> - - <p> - Choose 'Yes'. It will fail, but don't worry. Then at the main menu, choose 'Continue without a bootloader'. - You could also choose 'No'. Choice is irrelevant here. - </p> - - <p> - <i>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.</i> - </p> - - </div> - - <div class="section"> - - <h1>Clock UTC</h1> - - <p> - Just say 'Yes'. - </p> - - </div> - - <div class="section"> - - <h1> - Booting your system - </h1> - - <p> - At this point, you will have finished the installation. At your GRUB payload, press C to get to the command line. - </p> - - <p> - Do that:<br/> - grub> <b>cryptomount -a</b><br/> - grub> <b>set root='lvm/matrix-rootvol'</b><br/> - grub> <b>linux /vmlinuz root=/dev/mapper/matrix-rootvol cryptdevice=/dev/mapper/matrix-rootvol:root</b><br/> - grub> <b>initrd /initrd.img</b><br/> - grub> <b>boot</b> - </p> - - </div> - - <div class="section"> - - <h1> - ecryptfs - </h1> - - <p> - If you didn't encrypt your home directory, then you can safely ignore this section. - </p> - - <p> - Immediately after logging in, do that:<br/> - $ <b>sudo ecryptfs-unwrap-passphrase</b> - </p> - - <p> - This will be needed in the future if you ever need to recover your home 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)> - </p> - - </div> - - <div class="section"> - - <h1> - Modify grub.cfg (CBFS) - </h1> - - <p> - Now you need to set it up so that the system will automatically boot, without having to type a bunch of commands. - </p> - - <p> - Modify your grub.cfg (in the firmware) <a href="grub_cbfs.html">using this tutorial</a>; - just change the default menu entry 'Load Operating System' to say this inside: - </p> - - <p> - <b>cryptomount -a</b><br/> - <b>set root='lvm/matrix-rootvol'</b><br/> - <b>linux /vmlinuz root=/dev/mapper/matrix-rootvol cryptdevice=/dev/mapper/matrix-rootvol:root</b><br/> - <b>initrd /initrd.img</b> - </p> - - <p> - Without specifying a device, the <i>-a</i> parameter tries to unlock all detected LUKS volumes. - You can also specify -u UUID or -a (device). - </p> - - <p> - <a href="grub_hardening.html">Refer to this guide</a> for further guidance - on hardening your GRUB configuration, for security purposes. - </p> - - <p> - Flash the modified ROM - using <a href="../install/#flashrom">this tutorial</a>. - </p> - - </div> - - <div class="section"> - - <h1 id="troubleshooting">Troubleshooting</h1> - - <p> - A user reported issues when booting with a docking station attached - on an X200, when decrypting the disk in GRUB. The error - <i>AHCI transfer timed out</i> was observed. The workaround - was to remove the docking station. - </p> - - <p> - Further investigation revealed that it was the DVD drive causing problems. - Removing that worked around the issue. - </p> - -<pre> - -"sudo wodim -prcap" shows information about the drive: -Device was not specified. Trying to find an appropriate drive... -Detected CD-R drive: /dev/sr0 -Using /dev/cdrom of unknown capabilities -Device type : Removable CD-ROM -Version : 5 -Response Format: 2 -Capabilities : -Vendor_info : 'HL-DT-ST' -Identification : 'DVDRAM GU10N ' -Revision : 'MX05' -Device seems to be: Generic mmc2 DVD-R/DVD-RW. - -Drive capabilities, per MMC-3 page 2A: - - Does read CD-R media - Does write CD-R media - Does read CD-RW media - Does write CD-RW media - Does read DVD-ROM media - Does read DVD-R media - Does write DVD-R media - Does read DVD-RAM media - Does write DVD-RAM media - Does support test writing - - Does read Mode 2 Form 1 blocks - Does read Mode 2 Form 2 blocks - Does read digital audio blocks - Does restart non-streamed digital audio reads accurately - Does support Buffer-Underrun-Free recording - Does read multi-session CDs - Does read fixed-packet CD media using Method 2 - Does not read CD bar code - Does not read R-W subcode information - Does read raw P-W subcode data from lead in - Does return CD media catalog number - Does return CD ISRC information - Does support C2 error pointers - Does not deliver composite A/V data - - Does play audio CDs - Number of volume control levels: 256 - Does support individual volume control setting for each channel - Does support independent mute setting for each channel - Does not support digital output on port 1 - Does not support digital output on port 2 - - Loading mechanism type: tray - Does support ejection of CD via START/STOP command - Does not lock media on power up via prevent jumper - Does allow media to be locked in the drive via PREVENT/ALLOW command - Is not currently in a media-locked state - Does not support changing side of disk - Does not have load-empty-slot-in-changer feature - Does not support Individual Disk Present feature - - Maximum read speed: 4234 kB/s (CD 24x, DVD 3x) - Current read speed: 4234 kB/s (CD 24x, DVD 3x) - Maximum write speed: 4234 kB/s (CD 24x, DVD 3x) - Current write speed: 4234 kB/s (CD 24x, DVD 3x) - Rotational control selected: CLV/PCAV - Buffer size in KB: 1024 - Copy management revision supported: 1 - Number of supported write speeds: 4 - Write speed # 0: 4234 kB/s CLV/PCAV (CD 24x, DVD 3x) - Write speed # 1: 2822 kB/s CLV/PCAV (CD 16x, DVD 2x) - Write speed # 2: 1764 kB/s CLV/PCAV (CD 10x, DVD 1x) - Write speed # 3: 706 kB/s CLV/PCAV (CD 4x, DVD 0x) - -Supported CD-RW media types according to MMC-4 feature 0x37: - Does write multi speed CD-RW media - Does write high speed CD-RW media - Does write ultra high speed CD-RW media - Does not write ultra high speed+ CD-RW media - -</pre> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/gnulinux/encrypted_debian.md b/docs/gnulinux/encrypted_debian.md new file mode 100644 index 00000000..61265f7f --- /dev/null +++ b/docs/gnulinux/encrypted_debian.md @@ -0,0 +1,392 @@ +<div class="section"> + +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. + +Libreboot on x86 uses the GRUB +[payload](http://www.coreboot.org/Payloads#GRUB_2) by default, which +means that the GRUB configuration file (where your GRUB menu comes from) +is stored directly alongside libreboot and its GRUB payload executable, +inside the flash chip. In context, this means that installing +distributions and managing them is handled slightly differently compared +to traditional BIOS systems. + +On most systems, the /boot partition has to be left unencrypted while +the others are encrypted. This is so that GRUB, and therefore the +kernel, can be loaded and executed since the firmware can\'t open a LUKS +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 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\ +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 +depthcharge payload, ignore this section entirely.** + +Note: on some thinkpads, a faulty DVD drive can cause the cryptomount -a +step during boot to fail. If this happens to you, try removing the +drive. + +[Back to previous index](./) + +</div> + +<div class="section"> + +Set a strong user password (lots of lowercase/uppercase, numbers and +symbols). + +Use of the *diceware method* is recommended, for generating secure +passphrases (instead of passwords). + +when the installer asks you to set up encryption (ecryptfs) for your +home directory, select \'Yes\' if you want to: **LUKS is already secure +and performs well. Having ecryptfs on top of it will add noticeable +performance penalty, for little security gain in most use cases. This is +therefore optional, and not recommended. Choose \'no\'.** + +**Your user password should be different from the LUKS password which +you will set later on. Your LUKS password should, like the user +password, be secure.** + +</div> + +<div class="section"> + +Partitioning +============ + +Choose \'Manual\' partitioning: + +- Select drive and create new partition table +- Single large partition. The following are mostly defaults: + - Use as: physical volume for encryption + - Encryption: aes + - key size: whatever default is given to you + - IV algorithm: whatever default is given to you + - Encryption key: passphrase + - erase data: Yes (only choose \'No\' if it\'s a new drive that + doesn\'t contain your private data) +- Select \'configure encrypted volumes\' + - Create encrypted volumes + - Select your partition + - Finish + - Really erase: Yes + - (erase will take a long time. be patient) + - (if your old system was encrypted, just let this run for about a + minute to make sure that the LUKS header is wiped out) +- Select encrypted space: + - use as: physical volume for LVM + - Choose \'done setting up the partition\' +- Configure the logical volume manager: + - Keep settings: Yes +- Create volume group: + - Name: **matrix** (use this exact name) + - Select crypto partition +- Create logical volume + - select **matrix** (use this exact name) + - name: **rootvol** (use this exact name) + - size: default, minus 2048 MB +- Create logical volume + - select **matrix** (use this exact name) + - name: **swap** (user this exact name) + - size: press enter + +</div> + +<div class="section"> + +Further partitioning +==================== + +Now you are back at the main partitioning screen. You will simply set +mountpoints and filesystems to use. + +- LVM LV rootvol + - use as: btrfs + - mount point: / + - done setting up partition +- LVM LV swap + - use as: swap area + - done setting up partition +- Now you select \'Finished partitioning and write changes to disk\'. + +</div> + +<div class="section"> + +Kernel +====== + +Installation will ask what kernel you want to use. linux-generic is +fine. + +</div> + +<div class="section"> + +Tasksel +======= + +For Debian, use the *MATE* option, or one of the others if you want. The +libreboot project recommends MATE, unless you\'re saavy enough to choose +something else. + +If you want debian-testing, then you should only select barebones +options here and change the entries in /etc/apt/sources.list after +install to point to the new distro, and then run **apt-get update** and +**apt-get dist-upgrade** as root, then reboot and run **tasksel** as +root. This is to avoid downloading large packages twice. + +NOTE: If you want the latest up to date version of the Linux kernel, +Debian\'s kernel is sometimes outdated, even in the testing distro. You +might consider using [this repository](https://jxself.org/linux-libre/) +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. + +</div> + +<div class="section"> + +Postfix configuration +===================== + +If asked, choose *\"No Configuration\"* here (or maybe you want to +select something else. It\'s up to you.) + +</div> + +<div class="section"> + +Install the GRUB boot loader to the master boot record +====================================================== + +Choose \'Yes\'. It will fail, but don\'t worry. Then at the main menu, +choose \'Continue without a bootloader\'. You could also choose \'No\'. +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.* + +</div> + +<div class="section"> + +Clock UTC +========= + +Just say \'Yes\'. + +</div> + +<div class="section"> + +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\'**\ +grub> **linux /vmlinuz root=/dev/mapper/matrix-rootvol +cryptdevice=/dev/mapper/matrix-rootvol:root**\ +grub> **initrd /initrd.img**\ +grub> **boot** + +</div> + +<div class="section"> + +ecryptfs +======== + +If you didn\'t encrypt your home directory, then you can safely ignore +this section. + +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 +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)> + +</div> + +<div class="section"> + +Modify grub.cfg (CBFS) +====================== + +Now you need to set it up so that the system will automatically boot, +without having to type a bunch of commands. + +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\'**\ +**linux /vmlinuz root=/dev/mapper/matrix-rootvol +cryptdevice=/dev/mapper/matrix-rootvol:root**\ +**initrd /initrd.img** + +Without specifying a device, the *-a* parameter tries to unlock all +detected LUKS volumes. You can also specify -u UUID or -a (device). + +[Refer to this guide](grub_hardening.html) for further guidance on +hardening your GRUB configuration, for security purposes. + +Flash the modified ROM using [this tutorial](../install/#flashrom). + +</div> + +<div class="section"> + +Troubleshooting +=============== + +A user reported issues when booting with a docking station attached on +an X200, when decrypting the disk in GRUB. The error *AHCI transfer +timed out* was observed. The workaround was to remove the docking +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 + Using /dev/cdrom of unknown capabilities + Device type : Removable CD-ROM + Version : 5 + Response Format: 2 + Capabilities : + Vendor_info : 'HL-DT-ST' + Identification : 'DVDRAM GU10N ' + Revision : 'MX05' + Device seems to be: Generic mmc2 DVD-R/DVD-RW. + + Drive capabilities, per MMC-3 page 2A: + + Does read CD-R media + Does write CD-R media + Does read CD-RW media + Does write CD-RW media + Does read DVD-ROM media + Does read DVD-R media + Does write DVD-R media + Does read DVD-RAM media + Does write DVD-RAM media + Does support test writing + + Does read Mode 2 Form 1 blocks + Does read Mode 2 Form 2 blocks + Does read digital audio blocks + Does restart non-streamed digital audio reads accurately + Does support Buffer-Underrun-Free recording + Does read multi-session CDs + Does read fixed-packet CD media using Method 2 + Does not read CD bar code + Does not read R-W subcode information + Does read raw P-W subcode data from lead in + Does return CD media catalog number + Does return CD ISRC information + Does support C2 error pointers + Does not deliver composite A/V data + + Does play audio CDs + Number of volume control levels: 256 + Does support individual volume control setting for each channel + Does support independent mute setting for each channel + Does not support digital output on port 1 + Does not support digital output on port 2 + + Loading mechanism type: tray + Does support ejection of CD via START/STOP command + Does not lock media on power up via prevent jumper + Does allow media to be locked in the drive via PREVENT/ALLOW command + Is not currently in a media-locked state + Does not support changing side of disk + Does not have load-empty-slot-in-changer feature + Does not support Individual Disk Present feature + + Maximum read speed: 4234 kB/s (CD 24x, DVD 3x) + Current read speed: 4234 kB/s (CD 24x, DVD 3x) + Maximum write speed: 4234 kB/s (CD 24x, DVD 3x) + Current write speed: 4234 kB/s (CD 24x, DVD 3x) + Rotational control selected: CLV/PCAV + Buffer size in KB: 1024 + Copy management revision supported: 1 + Number of supported write speeds: 4 + Write speed # 0: 4234 kB/s CLV/PCAV (CD 24x, DVD 3x) + Write speed # 1: 2822 kB/s CLV/PCAV (CD 16x, DVD 2x) + Write speed # 2: 1764 kB/s CLV/PCAV (CD 10x, DVD 1x) + Write speed # 3: 706 kB/s CLV/PCAV (CD 4x, DVD 0x) + + Supported CD-RW media types according to MMC-4 feature 0x37: + Does write multi speed CD-RW media + Does write high speed CD-RW media + Does write ultra high speed CD-RW media + Does not write ultra high speed+ CD-RW media + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/gnulinux/encrypted_parabola.html b/docs/gnulinux/encrypted_parabola.html deleted file mode 100644 index ec4229e8..00000000 --- a/docs/gnulinux/encrypted_parabola.html +++ /dev/null @@ -1,830 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Installing Parabola or Arch GNU+Linux with full disk encryption (including /boot)</title> -</head> - -<body> - <div class="section"> - <h1>Installing Parabola or Arch GNU+Linux with full disk encryption (including /boot)</h1> - <p> - Libreboot on x86 uses the GRUB <a href="http://www.coreboot.org/Payloads#GRUB_2">payload</a> - by default, which means that the GRUB configuration file - (where your GRUB menu comes from) is stored directly alongside libreboot - and it's GRUB payload executable, inside - the flash chip. In context, this means that installing distributions and managing them - is handled slightly differently compared to traditional BIOS systems. - </p> - - <p> - On most systems, the /boot partition has to be left unencrypted while the others are encrypted. - This is so that GRUB, and therefore the kernel, can be loaded and executed since the firmware - can't open a LUKS 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. - </p> - <p> - <b>This guide is *only* for the GRUB payload. If you use the depthcharge payload, ignore this section entirely.</b> - </p> - <p> - This guide is intended for the Parabola distribution, but it should also work (with some adaptation) - for <em>Arch</em>. - We recomend using Parabola, which is a version of Arch that removes all - proprietary software, both in the default installation and in the package repositories. It usually lags - behind Arch by only a day or two, so it is still usable for most people. - See <a href="https://wiki.parabola.nu/index.php?title=Migration_from_the_GNU+Linux_distribution_of_Arch&redirect=no">Arch to Parabola migration guide</a>. - </p> - - <p> - Note: on some thinkpads, a faulty DVD drive can cause the cryptomount -a step during boot to fail. If this happens to you, try removing the drive. - </p> - <p> - <a href="./">Back to previous index</a> - </p> - </div> - - <div class="section"> - - <p> - Boot Parabola's install environment. <a href="grub_boot_installer.html">How to boot a GNU+Linux installer</a>. - </p> - - <p> - For this guide I used the 2015 08 01 image to boot the live installer and install the system. - This is available at <a href="https://wiki.parabola.nu/Get_Parabola#Main_live_ISO">this page</a>. - </p> - - <p> - This guide will go through the installation steps taken at the time of writing, which may or may not change due to - the volatile nature of Parabola (it changes all the time). In general most of it should remain the same. If you spot mistakes, - please say so! This guide will be ported 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). - </p> - - </div> - - <div class="section"> - - <p> 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: - - <p> - - beware there are issues with TRIM (not enabled through luks) and security issues if you do enable it. - See <a href="https://wiki.archlinux.org/index.php/Dm-crypt/Specialties#Discard.2FTRIM_support_for_solid_state_drives_.28SSD.29">this page</a> - for more info. - </p> - - <p> - make sure it's brand-new (or barely used). Or, otherwise, be sure that it never previously contained plaintext copies of your data. - </p> - - <p> - make sure to read <a href="https://wiki.archlinux.org/index.php/Solid_State_Drives">this article</a>. 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. - </p> - - <p> - Securely wipe the drive:<br/> - # <b>dd if=/dev/urandom of=/dev/sda; sync</b><br/> - 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:<br/> - # <b>dd if=/dev/urandom of=/dev/sda bs=2M; sync</b> - </p> - <p> - 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 header. - <a href="https://www.lisenet.com/2013/luks-add-keys-backup-and-restore-volume-header/">https://www.lisenet.com/2013/luks-add-keys-backup-and-restore-volume-header/</a> - 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:<br/> - # <b>head -c 3145728 /dev/urandom > /dev/sda; sync</b><br/> - (Wiping the LUKS header is important, since it has hashed passphrases and so on. It's 'secure', but 'potentially' a risk). - </p> - - </div> - - <div class="section"> - - <h2> - Change keyboard layout - </h2> - <p> - Parabola live shell assumes US Qwerty. If you have something different, list the available keymaps and use yours:<br/> - # <b>localectl list-keymaps</b><br/> - # <b>loadkeys LAYOUT</b><br/> - For me, LAYOUT would have been dvorak-uk. - </p> - - </div> - - <div class="section"> - - <h2>Establish an internet connection</h2> - <p> - Refer to <a href="https://wiki.parabola.nu/Beginners%27_guide#Establish_an_internet_connection">this guide</a>. Wired is recommended, - but wireless is also explained there. - </p> - - </div> - - <div class="section"> - - <h2>Getting started</h2> - <p> - The beginning is based on <a href="https://wiki.parabolagnulinux.org/Installation_Guide">https://wiki.parabolagnulinux.org/Installation_Guide</a>. - Then I referred to <a href="https://wiki.archlinux.org/index.php/Partitioning">https://wiki.archlinux.org/index.php/Partitioning</a> at first. - </p> - - </div> - - <div class="section"> - - <h2>dm-mod</h2> - <p> - device-mapper will be used - a lot. Make sure that the kernel module is loaded:<br/> - # <b>modprobe dm-mod</b> - </p> - - <h2>Create LUKS partition</h2> - <p> - Note that the default iteration time is 2000ms (2 seconds) if not specified - in cryptsetup. You should set a lower time than this, otherwise there will be - an approximate 20 second delay when booting your system. - We recommend 500ms (0.5 seconds), and this is included in the 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. - </p> - <p> - I am using MBR partitioning, so I use cfdisk:<br/> - # <b>cfdisk /dev/sda</b> - </p> - <p> - I create a single large sda1 filling the whole drive, leaving it as the default type 'Linux' (83). - </p> - <p> - Now I refer to <a href="https://wiki.archlinux.org/index.php/Dm-crypt/Drive_preparation#Partitioning">https://wiki.archlinux.org/index.php/Dm-crypt/Drive_preparation#Partitioning</a>:<br/> - I am then directed to <a href="https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption">https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption</a>. - </p> - <p> - Parabola forces you to RTFM. Do that. - </p> - <p> - It tells me to run:<br/> - # <b>cryptsetup benchmark</b> (for making sure the list below is populated)<br/> - Then:<br/> - # <b>cat /proc/crypto</b><br/> - 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:<br/> - # <b>man cryptsetup</b> - </p> - <p> - Following that page, based on my requirements, I do the following based on <a href="https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption#Encryption_options_for_LUKS_mode">https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption#Encryption_options_for_LUKS_mode</a>. - Reading through, it seems like Serpent (encryption) and Whirlpool (hash) is the best option. - </p> - <p> - I am initializing LUKS with the following:<br/> - # <b>cryptsetup -v --cipher serpent-xts-plain64 --key-size 512 --hash whirlpool --iter-time 500 --use-random --verify-passphrase luksFormat /dev/sda1</b> - Choose a <b>secure</b> passphrase here. Ideally lots of lowercase/uppercase numbers, letters, symbols etc all in a random pattern. The - password length should be as long as you are able to handle without writing it down or storing it anywhere. - </p> - - <p> - Use of the <i>diceware method</i> is recommended, for generating secure passphrases (instead of passwords). - </p> - - </div> - - <div class="section"> - - <h2>Create LVM</h2> - <p> - Now I refer to <a href="https://wiki.archlinux.org/index.php/LVM">https://wiki.archlinux.org/index.php/LVM</a>. - </p> - <p> - Open the LUKS partition:<br/> - # <b>cryptsetup luksOpen /dev/sda1 lvm</b><br/> - (it will be available at /dev/mapper/lvm) - </p> - <p> - Create LVM partition:<br/> - # <b>pvcreate /dev/mapper/lvm</b><br/> - Show that you just created it:<br/> - # <b>pvdisplay</b> - </p> - <p> - Now I create the volume group, inside of which the logical volumes will be created:<br/> - # <b>vgcreate matrix /dev/mapper/lvm</b><br/> - (volume group name is 'matrix' - choose your own name, if you like) - Show that you created it:<br/> - # <b>vgdisplay</b> - </p> - <p> - Now create the logical volumes:<br/> - # <b>lvcreate -L 2G matrix -n swapvol</b> (2G swap partition, named <u>swapvol</u>)<br/> - 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 <a -href="http://www.linux.com/news/software/applications/8208-all-about-linux-swap-space">http://www.linux.com/news/software/applications/8208-all-about-linux-swap-space</a>.<br/> - # <b>lvcreate -l +100%FREE matrix -n root</b> (single large partition in the rest of the space, named <u>root</u>)<br/> - 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 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). - </p> - <p> - Verify that the logical volumes were created, using the following command:<br/> - # <b>lvdisplay</b> - </p> - - </div> - - <div class="section"> - - <h2>Create / and swap partitions, and mount</h2> - <p> - For the swapvol LV I use:<br/> - # <b>mkswap /dev/mapper/matrix-swapvol</b><br/> - Activate swap:<br/> - # <b>swapon /dev/matrix/swapvol</b> - </p> - <p> - For the root LV I use:<br/> - # <b>mkfs.btrfs /dev/mapper/matrix-root</b> - </p> - <p> - Mount the root (/) partition:<br/> - # <b>mount /dev/matrix/root /mnt</b> - </p> - - </div> - - <div class="section"> - - <h2>Continue with Parabola installation</h2> - <p> - This guide is really about GRUB, Parabola and cryptomount. I have to show how to install Parabola - so that the guide can continue. - </p> - <p> - Now I am following the rest of <a href="https://wiki.parabolagnulinux.org/Installation_Guide">https://wiki.parabolagnulinux.org/Installation_Guide</a>. - I also cross referenced <a href="https://wiki.archlinux.org/index.php/Installation_guide">https://wiki.archlinux.org/index.php/Installation_guide</a>. - </p> - <p> - Create /home and /boot on root mountpoint:<br/> - # <b>mkdir -p /mnt/home</b><br/> - # <b>mkdir -p /mnt/boot</b> - </p> - <p> - Once all the remaining partitions, if any, have been mounted, the devices are ready to install Parabola. - </p> - - <p> - In <b>/etc/pacman.d/mirrorlist</b>, comment out all lines except the Server line closest to where you are (I chose the UK Parabola - server (main server)) and then did:<br/> - # <b>pacman -Syy</b><br/> - # <b>pacman -Syu</b><br/> - # <b>pacman -Sy pacman</b> (and then I did the other 2 steps above, again)<br/> - In my case I did the steps in the next paragraph, and followed the steps in this paragraph again. - </p> - <p> - <troubleshooting><br/> - The following is based on 'Verification of package signatures' in the Parabola install guide.<br/> - Check there first to see if steps differ by now.<br/> - Now you have to update the default Parabola keyring. This is used for signing and verifying packages:<br/> - # <b>pacman -Sy parabola-keyring</b><br/> - It says that if you get GPG errors, then it's probably an expired key and, therefore, you should do:<br/> - # <b>pacman-key --populate parabola</b><br/> - # <b>pacman-key --refresh-keys</b><br/> - # <b>pacman -Sy parabola-keyring</b><br/> - To be honest, you should do the above anyway. Parabola has a lot of maintainers, and a lot of keys. Really!<br/> - If you get an error mentioning dirmngr, do:<br/> - # <b>dirmngr </dev/null</b><br/> - Also, it says that if the clock is set incorrectly then you have to manually set the correct time <br/> - (if keys are listed as expired because of it):<br/> - # <b>date MMDDhhmm[[CC]YY][.ss]</b><br/> - I also had to install:<br/> - # <b>pacman -S archlinux-keyring</b><br/> - # <b>pacman-key --populate archlinux</b><br/> - In my case I saw some conflicting files reported in pacman, stopping me from using it.<br/> - I deleted the files that it mentioned - and then it worked. Specifically, I had this error:<br/> - <i>licenses: /usr/share/licenses/common/MPS exists in filesystem</i><br/> - I rm -Rf'd the file and then pacman worked. I'm told that the following would have also made it work:<br/> - # <b>pacman -Sf licenses</b><br/> - </troubleshooting><br/> - </p> - <p> - 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:<br/> - # <b>pacstrap /mnt base base-devel wpa_supplicant dialog iw wpa_actiond</b> - </p> - - </div> - - <div class="section"> - - <h2>Configure the system</h2> - <p> - Generate an fstab - UUIDs are used because they have certain advantages (see <a href="https://wiki.parabola.nu/Fstab#Identifying_filesystems">https://wiki.parabola.nu/Fstab#Identifying_filesystems</a>. - If you prefer labels instead, replace the -U option with -L):<br/> - # <b>genfstab -U -p /mnt >> /mnt/etc/fstab</b><br/> - Check the created file:<br/> - # <b>cat /mnt/etc/fstab</b><br/> - (If there are any errors, edit the file. Do <b>NOT</b> run the genfstab command again!) - </p> - <p> - Chroot into new system:<br/> - # <b>arch-chroot /mnt /bin/bash</b> - </p> - <p> - It's a good idea to have this installed:<br/> - # <b>pacman -S linux-libre-lts</b> - </p> - <p> - It was also suggested that you should install this kernel (read up on what GRSEC is):<br/> - # <b>pacman -S linux-libre-grsec</b> - </p> - <p> - 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. - </p> - <p> - Parabola does not have wget. This is sinister. Install it:<br/> - # <b>pacman -S wget</b> - </p> - <p> - Locale:<br/> - # <b>vi /etc/locale.gen</b><br/> - Uncomment your needed localisations. For example en_GB.UTF-8 (UTF-8 is highly recommended over other options).<br/> - # <b>locale-gen</b><br/> - # <b>echo LANG=en_GB.UTF-8 > /etc/locale.conf</b><br/> - # <b>export LANG=en_GB.UTF-8</b> - </p> - <p> - Console font and keymap:<br/> - # <b>vi /etc/vconsole.conf</b><br/> - In my case: - </p> -<pre> -KEYMAP=dvorak-uk -FONT=lat9w-16 -</pre> - <p> - Time zone:<br/> - # <b>ln -s /usr/share/zoneinfo/Europe/London /etc/localtime</b><br/> - (Replace Zone and Subzone to your liking. See /usr/share/zoneinfo) - </p> - <p> - Hardware clock:<br/> - # <b>hwclock --systohc --utc</b> - </p> - <p> - Hostname: - Write your hostname to /etc/hostname. For example, if your hostname is parabola:<br/> - # <b>echo parabola > /etc/hostname</b><br/> - Add the same hostname to /etc/hosts:<br/> - # <b>vi /etc/hosts</b><br/> - </p> -<pre> -#<ip-address> <hostname.domain.org> <hostname> -127.0.0.1 localhost.localdomain localhost parabola -::1 localhost.localdomain localhost parabola -</pre> - <p> Configure the network: - Refer to <a href="https://wiki.parabola.nu/Beginners%27_guide#Configure_the_network">https://wiki.parabola.nu/Beginners%27_guide#Configure_the_network</a>. - </p> - <p> Mkinitcpio: - Configure /etc/mkinitcpio.conf as needed (see <a href="https://wiki.parabola.nu/Mkinitcpio">https://wiki.parabola.nu/Mkinitcpio</a>). - Runtime modules can be found in /usr/lib/initcpio/hooks, and build hooks can be found in /usr/lib/initcpio/install. (# <b>mkinitcpio -H hookname</b> gives information about each hook.) - Specifically, for this use case:<br/> - # <b>vi /etc/mkinitcpio.conf</b><br/> - Then modify the file like so: - </p> - <ul> - <li>MODULES="i915"</li> - <li>This forces the driver to load earlier, so that the console font isn't wiped out after getting to login). Macbook21 users will also need <strong>hid-generic, hid and hid-apple to have a working keyboard when asked to enter the LUKS password.</strong></li> - <li>HOOKS="base udev autodetect modconf block keyboard keymap consolefont encrypt lvm2 filesystems fsck shutdown"</li> - <li>Explanation:</li> - <li>keymap adds to initramfs the keymap that you specified in /etc/vconsole.conf</li> - <li>consolefont adds to initramfs the font that you specified in /etc/vconsole.conf</li> - <li>encrypt adds LUKS support to the initramfs - needed to unlock your disks at boot time</li> - <li>lvm2 adds LVM support to the initramfs - needed to mount the LVM partitions at boot time</li> - <li>shutdown is needed according to Parabola wiki for unmounting devices (such as LUKS/LVM) during shutdown)</li> - </ul> - <p> - Now using mkinitcpio, you can create the kernel and ramdisk for booting with (this is different from Arch, specifying linux-libre instead of linux):<br/> - # <b>mkinitcpio -p linux-libre</b><br/> - Also do it for linux-libre-lts:<br/> - # <b>mkinitcpio -p linux-libre-lts</b><br/> - Also do it for linux-libre-grsec:<br/> - # <b>mkinitcpio -p linux-libre-grsec</b> - </p> - <p> - Set the root password: - At the time of writing, Parabola used SHA512 by default for its password hashing. I referred to <a href="https://wiki.archlinux.org/index.php/SHA_password_hashes">https://wiki.archlinux.org/index.php/SHA_password_hashes</a>.<br/> - # <b>vi /etc/pam.d/passwd</b><br/> - Add rounds=65536 at the end of the uncommented 'password' line.<br/> - # <b>passwd root</b><br/> - Make sure to set a secure password! Also, it must never be the same as your LUKS password. - </p> - - <p> - Use of the <i>diceware method</i> is recommended, for generating secure passphrases (instead of passwords). - </p> - - </div> - - <div class="section"> - - <h2>Extra security tweaks</h2> - <p> - Based on <a href="https://wiki.archlinux.org/index.php/Security">https://wiki.archlinux.org/index.php/Security</a>. - </p> - <p> - Restrict access to important directories:<br/> - # <b>chmod 700 /boot /etc/{iptables,arptables}</b> - </p> - <p> - Lockout user after three failed login attempts:<br/> - Edit the file /etc/pam.d/system-login and comment out that line:<br/> - <i># auth required pam_tally.so onerr=succeed file=/var/log/faillog</i><br/> - Or just delete it. Above it, put:<br/> - <i>auth required pam_tally.so deny=2 unlock_time=600 onerr=succeed file=/var/log/faillog</i><br/> - To unlock a user manually (if a password attempt is failed 3 times), do:<br/> - # <b>pam_tally --user <i>theusername</i> --reset</b> - What the above configuration does is lock the user out for 10 minutes, if they make 3 failed login attempts. - </p> - <p> - 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. - </p> - - </div> - - <div class="section"> - - <h2>Unmount, reboot!</h2> - <p> - Exit from chroot:<br/> - # <b>exit</b> - </p> - <p> - unmount:<br/> - # <b>umount -R /mnt</b><br/> - # <b>swapoff -a</b> - </p> - <p> - deactivate the lvm lv's:<br/> - # <b>lvchange -an /dev/matrix/root</b><br/> - # <b>lvchange -an /dev/matrix/swapvol</b><br/> - </p> - <p> - Lock the encrypted partition (close it):<br/> - # <b>cryptsetup luksClose lvm</b> - </p> - <p> - # <b>shutdown -h now</b><br/> - Remove the installation media, then boot up again. - </p> - - </div> - - <div class="section"> - - <h2>Booting from GRUB</h2> - <p> - 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). - </p> - <p> - grub> <b>cryptomount -a</b><br/> - grub> <b>set root='lvm/matrix-root'</b><br/> - grub> <b>linux /boot/vmlinuz-linux-libre<u>-lts</u> root=/dev/matrix/root cryptdevice=/dev/sda1:root</b><br/> - grub> <b>initrd /boot/initramfs-linux-libre<u>-lts</u>.img</b><br/> - grub> <b>boot</b><br/> - </p> - <p> - You could also make it load /boot/vmlinuz-linux-libre-grsec and /boot/initramfs-linux-libre-grsec.img - </p> - - </div> - - <div class="section"> - - <h2>Follow-up tutorial: configuring Parabola</h2> - <p> - We will modify grub.config inside the ROM and do all kinds of fun stuff, but I recommend that you first transform the current bare-bones Parabola install into a more useable system. - Doing so will make the upcoming ROM modifications MUCH easier to perform and less risky! - <a href="configuring_parabola.html">configuring_parabola.html</a> shows my own notes post-installation. Using these, you can get a basic - system similar to the one that I chose for myself. You can also cherry pick useful notes and come up with your own system. - Parabola is user-centric, which means that you are in control. For more information, read <a href="https://wiki.archlinux.org/index.php/The_Arch_Way">The Arch Way</a> - (Parabola also follows it). - </p> - - </div> - - <div class="section"> - - <h2>Modify grub.cfg inside the ROM</h2> - - <p> - (Re-)log in to your system, pressing C, so booting manually from GRUB (see above). You need to modify the ROM, so that Parabola can boot automatically with this configuration. - <a href="grub_cbfs.html">grub_cbfs.html</a> shows you how. Follow that guide, using the configuration details below. - If you go for option 2 (re-flash), promise to do this on grubtest.cfg first! We can't emphasise this enough. This is to reduce the possibility of bricking your device! - </p> - - <p> - 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 <i>libreboot.rom</i> is an example: make sure to adapt:<br/> - # <b>flashrom -p internal -r libreboot.rom</b><br/> - If flashrom complains about multiple flash chips detected, add a <i>-c</i> option at the end, with the name of your chosen chip is quotes.<br/> - You can check if everything is in there (<i>grub.cfg</i> and <i>grubtest.cfg</i> would be really nice):<br/> - $ <b>./cbfstool libreboot.rom print</b><br/> - Extract grubtest.cfg:<br/> - $ <b>./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg</b><br/> - And modify:<br/> - $ <b>vi grubtest.cfg</b> - </p> - - <p> - In grubtest.cfg, inside the 'Load Operating System' menu entry, change the contents to: - </p> -<pre> -cryptomount -a<br/> -set root='lvm/matrix-root'<br/> -linux /boot/vmlinuz-linux-libre<u>-lts</u> root=/dev/matrix/root cryptdevice=/dev/sda1:root<br/> -initrd /boot/initramfs-linux-libre<u>-lts</u>.img -</pre> - - <p> - Note: the underlined parts above (-lts) can also be removed, to boot the latest kernel instead of LTS (long-term support) kernels. - You could also copy the menu entry and in one have -lts, and without in the other menuentry. - You could also create a menu entry to load /boot/vmlinuz-linux-libre-grsec and /boot/initramfs-linux-libre-grsec.img - The first entry will load by default. - </p> - - <p> - Without specifying a device, the <i>-a</i> parameter tries to unlock all detected LUKS volumes. - You can also specify -u UUID or -a (device). - </p> - - <p> - <a href="grub_hardening.html">Refer to this guide</a> for further guidance - on hardening your GRUB configuration, for security purposes. - </p> - - <p> - Save your changes in grubtest.cfg, then delete the unmodified config from the ROM image:<br/> - $ <b>./cbfstool libreboot.rom remove -n grubtest.cfg</b><br/> - and insert the modified grubtest.cfg:<br/> - $ <b>./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t raw</b><br/> - </p> - - <p> - Now refer to <a href="http://libreboot.org/docs/install/#flashrom">http://libreboot.org/docs/install/#flashrom</a>. - Cd (up) to the libreboot_util directory and update the flash chip contents:<br/> - # <b>./flash update libreboot.rom</b><br/> - 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:<br/> - # <b>./flash forceupdate libreboot.rom</b><br/> - You should see "Verifying flash... VERIFIED." written at the end of the flashrom output. - </p> - - <p> - With this new configuration, Parabola can boot automatically and you will have to enter a password at boot time, in GRUB, before being able to use any of the menu entries or switch to the terminal. - Let's test it out: reboot and choose grubtest.cfg from the GRUB menu, using the arrow keys on your keyboard. - Enter the name you chose, the GRUB password, your LUKS passphrase and login as root/your user. All went well? Great! - </p> - - <p> - 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! - <b>Do *not* proceed past this point unless you are 100% sure that your new configuration is safe (or desirable) to use.</b> - </p> - - <p> - Now, we can easily and safely create a copy of grubtest.cfg, called grub.cfg. This will be the same except for one difference: the menuentry 'Switch to grub.cfg' is changed to 'Switch to grubtest.cfg' - and, inside it, all instances of grub.cfg 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). - Inside libreboot_util/cbfstool/{armv7l i686 x86_64}, we can do this with the following command:<br/> - $ <b>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</b><br/> - Delete the grub.cfg that remained inside the ROM:<br/> - $ <b>./cbfstool libreboot.rom remove -n grub.cfg</b><br/> - Add the modified version that you just made:<br/> - $ <b>./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw</b><br/> - </p> - - <p> - Now you have a modified ROM. Once more, refer to <a href="http://libreboot.org/docs/install/#flashrom">http://libreboot.org/docs/install/#flashrom</a>. - Cd to the libreboot_util directory and update the flash chip contents:<br/> - # <b>./flash update libreboot.rom</b><br/> - And wait for the "Verifying flash... VERIFIED." Once you have done that, shut down and then boot up with your new configuration. - </p> - - <p> - When done, delete GRUB (remember, we only needed it for the <i>grub-mkpasswd-pbkdf2</i> utility; - GRUB is already part of libreboot, flashed alongside it as a <i>payload</i>):<br/> - # <b>pacman -R grub</b> - </p> - - </div> - - <div class="section"> - - <p> - 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. - </p> - - </div> - - <div class="section"> - <h2>Bonus: Using a key file to unlock /boot/</h2> - <p> - By default, you will have to enter your LUKS passphrase twice; once in GRUB, and once when booting the kernel. - GRUB unlocks the encrypted partition and then loads the kernel, but the kernel is not aware of the 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).<br/> - - Boot up and login as root or your user. Then generate the key file:<br/> - # <b>dd bs=512 count=4 if=/dev/urandom of=/etc/mykeyfile iflag=fullblock</b><br/> - Insert it into the luks volume:<br/> - # <b>cryptsetup luksAddKey /dev/sdX /etc/mykeyfile</b><br/> - and enter your LUKS passphrase when prompted. - Add the keyfile to the initramfs by adding it to FILES in /etc/mkinitcpio.conf. For example:<br/> - # <b>FILES="/etc/mykeyfile"</b><br/> - Create the initramfs image from scratch:<br/> - # <b>mkinitcpio -p linux-libre</b><br/> - # <b>mkinitcpio -p linux-libre-lts</b><br/> - # <b>mkinitcpio -p linux-libre-grsec</b><br/> - 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:<br/> - # <b>cryptkey=rootfs:/etc/mykeyfile</b><br/> - <br/> - You can also place this inside the grub.cfg that exists in CBFS: <a href="grub_cbfs.html">grub_cbfs.html</a>. - </p> - - </div> - - <div class="section"> - - <h2>Further security tips</h2> - <p> - <a href="https://wiki.archlinux.org/index.php/Security">https://wiki.archlinux.org/index.php/Security</a>.<br/> - <a href="https://wiki.parabolagnulinux.org/User:GNUtoo/laptop">https://wiki.parabolagnulinux.org/User:GNUtoo/laptop</a> - </p> - - </div> - - <div class="section"> - - <h1 id="troubleshooting">Troubleshooting</h1> - - <p> - A user reported issues when booting with a docking station attached - on an X200, when decrypting the disk in GRUB. The error - <i>AHCI transfer timed out</i> was observed. The workaround - was to remove the docking station. - </p> - - <p> - Further investigation revealed that it was the DVD drive causing problems. - Removing that worked around the issue. - </p> - -<pre> - -"sudo wodim -prcap" shows information about the drive: -Device was not specified. Trying to find an appropriate drive... -Detected CD-R drive: /dev/sr0 -Using /dev/cdrom of unknown capabilities -Device type : Removable CD-ROM -Version : 5 -Response Format: 2 -Capabilities : -Vendor_info : 'HL-DT-ST' -Identification : 'DVDRAM GU10N ' -Revision : 'MX05' -Device seems to be: Generic mmc2 DVD-R/DVD-RW. - -Drive capabilities, per MMC-3 page 2A: - - Does read CD-R media - Does write CD-R media - Does read CD-RW media - Does write CD-RW media - Does read DVD-ROM media - Does read DVD-R media - Does write DVD-R media - Does read DVD-RAM media - Does write DVD-RAM media - Does support test writing - - Does read Mode 2 Form 1 blocks - Does read Mode 2 Form 2 blocks - Does read digital audio blocks - Does restart non-streamed digital audio reads accurately - Does support Buffer-Underrun-Free recording - Does read multi-session CDs - Does read fixed-packet CD media using Method 2 - Does not read CD bar code - Does not read R-W subcode information - Does read raw P-W subcode data from lead in - Does return CD media catalog number - Does return CD ISRC information - Does support C2 error pointers - Does not deliver composite A/V data - - Does play audio CDs - Number of volume control levels: 256 - Does support individual volume control setting for each channel - Does support independent mute setting for each channel - Does not support digital output on port 1 - Does not support digital output on port 2 - - Loading mechanism type: tray - Does support ejection of CD via START/STOP command - Does not lock media on power up via prevent jumper - Does allow media to be locked in the drive via PREVENT/ALLOW command - Is not currently in a media-locked state - Does not support changing side of disk - Does not have load-empty-slot-in-changer feature - Does not support Individual Disk Present feature - - Maximum read speed: 4234 kB/s (CD 24x, DVD 3x) - Current read speed: 4234 kB/s (CD 24x, DVD 3x) - Maximum write speed: 4234 kB/s (CD 24x, DVD 3x) - Current write speed: 4234 kB/s (CD 24x, DVD 3x) - Rotational control selected: CLV/PCAV - Buffer size in KB: 1024 - Copy management revision supported: 1 - Number of supported write speeds: 4 - Write speed # 0: 4234 kB/s CLV/PCAV (CD 24x, DVD 3x) - Write speed # 1: 2822 kB/s CLV/PCAV (CD 16x, DVD 2x) - Write speed # 2: 1764 kB/s CLV/PCAV (CD 10x, DVD 1x) - Write speed # 3: 706 kB/s CLV/PCAV (CD 4x, DVD 0x) - -Supported CD-RW media types according to MMC-4 feature 0x37: - Does write multi speed CD-RW media - Does write high speed CD-RW media - Does write ultra high speed CD-RW media - Does not write ultra high speed+ CD-RW media - -</pre> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org><br/> - Copyright © 2015 Jeroen Quint <jezza@diplomail.ch><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md new file mode 100644 index 00000000..3480a2e9 --- /dev/null +++ b/docs/gnulinux/encrypted_parabola.md @@ -0,0 +1,834 @@ +<div class="section"> + +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 +means that the GRUB configuration file (where your GRUB menu comes from) +is stored directly alongside libreboot and it\'s GRUB payload +executable, inside the flash chip. In context, this means that +installing distributions and managing them is handled slightly +differently compared to traditional BIOS systems. + +On most systems, the /boot partition has to be left unencrypted while +the others are encrypted. This is so that GRUB, and therefore the +kernel, can be loaded and executed since the firmware can\'t open a LUKS +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 +depthcharge payload, ignore this section entirely.** + +This guide is intended for the Parabola distribution, but it should also +work (with some adaptation) for *Arch*. We recomend using Parabola, +which is a version of Arch that removes all proprietary software, both +in the default installation and in the package repositories. It usually +lags behind Arch by only a day or two, so it is still usable for most +people. See [Arch to Parabola migration +guide](https://wiki.parabola.nu/index.php?title=Migration_from_the_GNU+Linux_distribution_of_Arch&redirect=no). + +Note: on some thinkpads, a faulty DVD drive can cause the cryptomount -a +step during boot to fail. If this happens to you, try removing the +drive. + +[Back to previous index](./) + +</div> + +<div class="section"> + +Boot Parabola\'s install environment. [How to boot a GNU+Linux +installer](grub_boot_installer.html). + +For this guide I used the 2015 08 01 image to boot the live installer +and install the system. This is available at [this +page](https://wiki.parabola.nu/Get_Parabola#Main_live_ISO). + +This guide will go through the installation steps taken at the time of +writing, which may or may not change due to the volatile nature of +Parabola (it changes all the time). In general most of it should remain +the same. If you spot mistakes, please say so! This guide will be ported +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). + +</div> + +<div class="section"> + +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: + +- beware there are issues with TRIM (not enabled through luks) and +security issues if you do enable it. See [this +page](https://wiki.archlinux.org/index.php/Dm-crypt/Specialties#Discard.2FTRIM_support_for_solid_state_drives_.28SSD.29) +for more info. + +- make sure it\'s brand-new (or barely used). Or, otherwise, be sure +that it never previously contained plaintext copies of your data. + +- make sure to read [this +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**\ +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** + +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 +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**\ +(Wiping the LUKS header is important, since it has hashed passphrases +and so on. It\'s \'secure\', but \'potentially\' a risk). + +</div> + +<div class="section"> + +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**\ +For me, LAYOUT would have been dvorak-uk. + +</div> + +<div class="section"> + +Establish an internet connection +-------------------------------- + +Refer to [this +guide](https://wiki.parabola.nu/Beginners%27_guide#Establish_an_internet_connection). +Wired is recommended, but wireless is also explained there. + +</div> + +<div class="section"> + +Getting started +--------------- + +The beginning is based on +<https://wiki.parabolagnulinux.org/Installation_Guide>. Then I referred +to <https://wiki.archlinux.org/index.php/Partitioning> at first. + +</div> + +<div class="section"> + +dm-mod +------ + +device-mapper will be used - a lot. Make sure that the kernel module is +loaded:\ +\# **modprobe dm-mod** + +Create LUKS partition +--------------------- + +Note that the default iteration time is 2000ms (2 seconds) if not +specified in cryptsetup. You should set a lower time than this, +otherwise there will be an approximate 20 second delay when booting your +system. We recommend 500ms (0.5 seconds), and this is included in the +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 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>:\ +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**\ +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** + +Following that page, based on my requirements, I do the following based +on +<https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption#Encryption_options_for_LUKS_mode>. +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 +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 +pattern. The password length should be as long as you are able to handle +without writing it down or storing it anywhere. + +Use of the *diceware method* is recommended, for generating secure +passphrases (instead of passwords). + +</div> + +<div class="section"> + +Create LVM +---------- + +Now I refer to <https://wiki.archlinux.org/index.php/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** + +Now I create the volume group, inside of which the logical volumes will +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)\ +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)\ +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 +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:\ +\# **lvdisplay** + +</div> + +<div class="section"> + +Create / and swap partitions, and mount +--------------------------------------- + +For the swapvol LV I use:\ +\# **mkswap /dev/mapper/matrix-swapvol**\ +Activate swap:\ +\# **swapon /dev/matrix/swapvol** + +For the root LV I use:\ +\# **mkfs.btrfs /dev/mapper/matrix-root** + +Mount the root (/) partition:\ +\# **mount /dev/matrix/root /mnt** + +</div> + +<div class="section"> + +Continue with Parabola installation +----------------------------------- + +This guide is really about GRUB, Parabola and cryptomount. I have to +show how to install Parabola so that the guide can continue. + +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** + +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)\ +In my case I did the steps in the next paragraph, and followed the steps +in this paragraph again. + +<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.\ + Now you have to update the default Parabola keyring. This is used for +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**\ + 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**\ + 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**\ + In my case I saw some conflicting files reported in pacman, stopping +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*\ + 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>\ + +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 +wpa\_actiond** + +</div> + +<div class="section"> + +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**\ +(If there are any errors, edit the file. Do **NOT** run the genfstab +command again!) + +Chroot into new system:\ +\# **arch-chroot /mnt /bin/bash** + +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** + +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** + +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** + +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**\ +(Replace Zone and Subzone to your liking. See /usr/share/zoneinfo) + +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**\ + + #<ip-address> <hostname.domain.org> <hostname> + 127.0.0.1 localhost.localdomain localhost parabola + ::1 localhost.localdomain localhost parabola + +Configure the network: Refer to +<https://wiki.parabola.nu/Beginners%27_guide#Configure_the_network>. + +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**\ +Then modify the file like so: + +- MODULES=\"i915\" +- This forces the driver to load earlier, so that the console font + isn\'t wiped out after getting to login). Macbook21 users will also + need **hid-generic, hid and hid-apple to have a working keyboard + when asked to enter the LUKS password.** +- HOOKS=\"base udev autodetect modconf block keyboard keymap + consolefont encrypt lvm2 filesystems fsck shutdown\" +- Explanation: +- keymap adds to initramfs the keymap that you specified in + /etc/vconsole.conf +- consolefont adds to initramfs the font that you specified in + /etc/vconsole.conf +- encrypt adds LUKS support to the initramfs - needed to unlock your + disks at boot time +- lvm2 adds LVM support to the initramfs - needed to mount the LVM + partitions at boot time +- shutdown is needed according to Parabola wiki for unmounting devices + (such as LUKS/LVM) during shutdown) + +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** + +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**\ +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). + +</div> + +<div class="section"> + +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:\ +*auth required pam\_tally.so deny=2 unlock\_time=600 onerr=succeed +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 +configuration does is lock the user out for 10 minutes, if they make 3 +failed login attempts. + +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. + +</div> + +<div class="section"> + +Unmount, reboot! +---------------- + +Exit from chroot:\ +\# **exit** + +unmount:\ +\# **umount -R /mnt**\ +\# **swapoff -a** + +deactivate the lvm lv\'s:\ +\# **lvchange -an /dev/matrix/root**\ +\# **lvchange -an /dev/matrix/swapvol**\ + +Lock the encrypted partition (close it):\ +\# **cryptsetup luksClose lvm** + +\# **shutdown -h now**\ +Remove the installation media, then boot up again. + +</div> + +<div class="section"> + +Booting from GRUB +----------------- + +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> **linux /boot/vmlinuz-linux-libre-lts root=/dev/matrix/root +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 + +</div> + +<div class="section"> + +Follow-up tutorial: configuring Parabola +---------------------------------------- + +We will modify grub.config inside the ROM and do all kinds of fun stuff, +but I recommend that you first transform the current bare-bones Parabola +install into a more useable system. Doing so will make the upcoming ROM +modifications MUCH easier to perform and less risky! +[configuring\_parabola.html](configuring_parabola.html) shows my own +notes post-installation. Using these, you can get a basic system similar +to the one that I chose for myself. You can also cherry pick useful +notes and come up with your own system. Parabola is user-centric, which +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). + +</div> + +<div class="section"> + +Modify grub.cfg inside the ROM +------------------------------ + +(Re-)log in to your system, pressing C, so booting manually from GRUB +(see above). You need to modify the ROM, so that Parabola can boot +automatically with this configuration. [grub\_cbfs.html](grub_cbfs.html) +shows you how. Follow that guide, using the configuration details below. +If you go for option 2 (re-flash), promise to do this on grubtest.cfg +first! We can\'t emphasise this enough. This is to reduce the +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**\ +If flashrom complains about multiple flash chips detected, add a *-c* +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:\ +\$ **vi grubtest.cfg** + +In grubtest.cfg, inside the \'Load Operating System\' menu entry, change +the contents to: + + cryptomount -a + + set root='lvm/matrix-root' + + linux /boot/vmlinuz-linux-libre-lts root=/dev/matrix/root cryptdevice=/dev/sda1:root + + initrd /boot/initramfs-linux-libre-lts.img + +Note: the underlined parts above (-lts) can also be removed, to boot the +latest kernel instead of LTS (long-term support) kernels. You could also +copy the menu entry and in one have -lts, and without in the other +menuentry. You could also create a menu entry to load +/boot/vmlinuz-linux-libre-grsec and +/boot/initramfs-linux-libre-grsec.img The first entry will load by +default. + +Without specifying a device, the *-a* parameter tries to unlock all +detected LUKS volumes. You can also specify -u UUID or -a (device). + +[Refer to this guide](grub_hardening.html) for further guidance on +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:\ +\$ **./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t +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**\ +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 +the flashrom output. + +With this new configuration, Parabola can boot automatically and you +will have to enter a password at boot time, in GRUB, before being able +to use any of the menu entries or switch to the terminal. Let\'s test it +out: reboot and choose grubtest.cfg from the GRUB menu, using the arrow +keys on your keyboard. Enter the name you chose, the GRUB password, your +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 +point unless you are 100% sure that your new configuration is safe (or +desirable) to use.** + +Now, we can easily and safely create a copy of grubtest.cfg, called +grub.cfg. This will be the same except for one difference: the menuentry +\'Switch to grub.cfg\' is changed to \'Switch to grubtest.cfg\' and, +inside it, all instances of grub.cfg 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). +Inside libreboot\_util/cbfstool/{armv7l i686 x86\_64}, we can do this +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**\ + +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 +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*):\ +\# **pacman -R grub** + +</div> + +<div class="section"> + +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. + +</div> + +<div class="section"> + +Bonus: Using a key file to unlock /boot/ +---------------------------------------- + +By default, you will have to enter your LUKS passphrase twice; once in +GRUB, and once when booting the kernel. GRUB unlocks the encrypted +partition and then loads the kernel, but the kernel is not aware of the +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**\ +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**\ +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**\ +\ +You can also place this inside the grub.cfg that exists in CBFS: +[grub\_cbfs.html](grub_cbfs.html). + +</div> + +<div class="section"> + +Further security tips +--------------------- + +<https://wiki.archlinux.org/index.php/Security>.\ +<https://wiki.parabolagnulinux.org/User:GNUtoo/laptop> + +</div> + +<div class="section"> + +Troubleshooting +=============== + +A user reported issues when booting with a docking station attached on +an X200, when decrypting the disk in GRUB. The error *AHCI transfer +timed out* was observed. The workaround was to remove the docking +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 + Using /dev/cdrom of unknown capabilities + Device type : Removable CD-ROM + Version : 5 + Response Format: 2 + Capabilities : + Vendor_info : 'HL-DT-ST' + Identification : 'DVDRAM GU10N ' + Revision : 'MX05' + Device seems to be: Generic mmc2 DVD-R/DVD-RW. + + Drive capabilities, per MMC-3 page 2A: + + Does read CD-R media + Does write CD-R media + Does read CD-RW media + Does write CD-RW media + Does read DVD-ROM media + Does read DVD-R media + Does write DVD-R media + Does read DVD-RAM media + Does write DVD-RAM media + Does support test writing + + Does read Mode 2 Form 1 blocks + Does read Mode 2 Form 2 blocks + Does read digital audio blocks + Does restart non-streamed digital audio reads accurately + Does support Buffer-Underrun-Free recording + Does read multi-session CDs + Does read fixed-packet CD media using Method 2 + Does not read CD bar code + Does not read R-W subcode information + Does read raw P-W subcode data from lead in + Does return CD media catalog number + Does return CD ISRC information + Does support C2 error pointers + Does not deliver composite A/V data + + Does play audio CDs + Number of volume control levels: 256 + Does support individual volume control setting for each channel + Does support independent mute setting for each channel + Does not support digital output on port 1 + Does not support digital output on port 2 + + Loading mechanism type: tray + Does support ejection of CD via START/STOP command + Does not lock media on power up via prevent jumper + Does allow media to be locked in the drive via PREVENT/ALLOW command + Is not currently in a media-locked state + Does not support changing side of disk + Does not have load-empty-slot-in-changer feature + Does not support Individual Disk Present feature + + Maximum read speed: 4234 kB/s (CD 24x, DVD 3x) + Current read speed: 4234 kB/s (CD 24x, DVD 3x) + Maximum write speed: 4234 kB/s (CD 24x, DVD 3x) + Current write speed: 4234 kB/s (CD 24x, DVD 3x) + Rotational control selected: CLV/PCAV + Buffer size in KB: 1024 + Copy management revision supported: 1 + Number of supported write speeds: 4 + Write speed # 0: 4234 kB/s CLV/PCAV (CD 24x, DVD 3x) + Write speed # 1: 2822 kB/s CLV/PCAV (CD 16x, DVD 2x) + Write speed # 2: 1764 kB/s CLV/PCAV (CD 10x, DVD 1x) + Write speed # 3: 706 kB/s CLV/PCAV (CD 4x, DVD 0x) + + Supported CD-RW media types according to MMC-4 feature 0x37: + Does write multi speed CD-RW media + Does write high speed CD-RW media + Does write ultra high speed CD-RW media + Does not write ultra high speed+ CD-RW media + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/gnulinux/grub_boot_installer.html b/docs/gnulinux/grub_boot_installer.html deleted file mode 100644 index 0de04cac..00000000 --- a/docs/gnulinux/grub_boot_installer.html +++ /dev/null @@ -1,355 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>How to install GNU+Linux on a libreboot system</title> -</head> - -<body> - <div id="pagetop" class="section"> - <h1>How to install GNU+Linux on a libreboot system</h1> - <p> - This section relates to preparing, booting and installing a - GNU+Linux distribution on your libreboot system, using nothing more than a USB flash drive (and <i>dd</i>). - </p> - <ul> - <li><a href="../distros">List of recommended GNU+Linux distributions</a></li> - <li><a href="#prepare">Prepare the USB drive (in GNU+Linux)</a></li> - <li><a href="#encryption">Installing GNU+Linux with full disk encryption</a></li> - <li><a href="#debian_netinstall">Debian or Devuan net install?</a></li> - <li><a href="#parse_isolinux">Booting ISOLINUX images (automatic method)</a></li> - <li><a href="#manual_isolinux">Booting ISOLINUX images (manual method)</a></li> - <li><a href="#troubleshooting">Troubleshooting</a></li> - </ul> - <p> - <a href="./">Back to previous index</a> - </p> - </div> - - <div class="section"> - <p> - <b>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.</b> - </p> - </div> - - <div id="prepare" class="section"> - - <h2>Prepare the USB drive (in GNU+Linux)</h2> - - <p> - If you downloaded your ISO on an existing GNU+Linux system, - here is how to create the bootable GNU+Linux USB drive: - </p> - - <p> - Connect the USB drive. Check dmesg:<br/> - <b>$ dmesg</b><br/> - - Check lsblk to confirm which drive it is:<br/> - <b>$ lsblk</b> - </p> - - <p> - Check that it wasn't automatically mounted. If it was, unmount it. For example:<br/> - <b>$ sudo umount /dev/sdX*</b><br/> - <b># umount /dev/sdX*</b> - </p> - - <p> - dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example:<br/> - <b>$ sudo dd if=gnulinux.iso of=/dev/sdX bs=8M; sync</b><br/> - <b># dd if=gnulinux.iso of=/dev/sdX bs=8M; sync</b> - </p> - - <p> - You should now be able to boot the installer from your USB drive. Continue reading, for - information about how to do that. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - <h2>Prepare the USB drive (in NetBSD)</h2> - <p> - <a href="https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/">This page</a> - on the NetBSD website shows how to create a NetBSD bootable USB drive - from within NetBSD itself. You should use the <em>dd</em> method - documented there. This will also work with any GNU+Linux ISO image. - </p> - - <h2>Prepare the USB drive (in FreeBSD)</h2> - <p> - <a href="https://www.freebsd.org/doc/handbook/bsdinstall-pre.html">This page</a> - on the FreeBSD website shows how to create a bootable USB drive - for installing FreeBSD. Use the <em>dd</em> on that page. You can - also use the same instructions with any GNU+Linux ISO image.. - </p> - - <h2>Prepare the USB drive (in LibertyBSD or OpenBSD)</h2> - - <p> - If you downloaded your ISO on a LibertyBSD or OpenBSD system, - here is how to create the bootable GNU+Linux USB drive: - </p> - - <p> - Connect the USB drive. Check dmesg:<br/> - <b>$ dmesg | tail</b><br/> - - Check to confirm which drive it is, for example, if you think its sd3:<br/> - <b>$ disklabel sd3</b> - </p> - - <p> - Check that it wasn't automatically mounted. If it was, unmount it. For example:<br/> - <b>$ doas umount /dev/sd3i</b><br/> - </p> - - <p> - dmesg told you what device it is. Overwrite the drive, writing the OpenBSD installer to it with dd. For example:<br/> - <b>$ doas dd if=gnulinux.iso of=/dev/rsdXc bs=1M; sync</b><br/> - </p> - - <p> - You should now be able to boot the installer from your USB drive. Continue reading, for - information about how to do that. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="encryption" class="section"> - - <h2>Installing GNU+Linux with full disk encryption</h2> - - <ul> - <li><a href="encrypted_debian.html">Installing Debian or Devuan GNU+Linux with full disk encryption (including /boot)</a></li> - <li><a href="encrypted_parabola.html">Installing Parabola GNU+Linux with full disk encryption (including /boot)</a></li> - </ul> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="debian_netinstall" class="section"> - - <h2>Debian or Devuan net install?</h2> - - <p> - Download the Debian or Devuan net installer. You can download the ISO from the homepage on - <a href="https://www.debian.org/">debian.org</a>, or <a href="https://www.devuan.org/">the Devuan homepage</a> for Devuan. - Use this on the GRUB terminal to boot it from USB (for 64-bit Intel or AMD):<br/> - <strong> - set root='usb0'<br/> - linux /install.amd/vmlinuz<br/> - initrd /install.amd/initrd.gz<br/> - boot<br/> - </strong> - If you are on a 32-bit system (e.g. X60):<br/> - <strong> - set root='usb0'<br/> - linux /install.386/vmlinuz<br/> - initrd /install.386/initrd.gz<br/> - boot - </strong> - <br/> - We recommend using the <em>MATE</em> desktop. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="parse_isolinux" class="section"> - - <h2>Booting ISOLINUX images (automatic method)</h2> - - <p> - Boot it in GRUB using the <i>Parse ISOLINUX config (USB)</i> option. - - A new 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. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="manual_isolinux" class="section"> - - <h2>Booting ISOLINUX images (manual method)</h2> - - <p> - <i>These are generic instructions. They may or may not be correct for your - distribution. You must adapt them appropriately, for whatever GNU+Linux distribution - it is that you are trying to install.</i> - </p> - - <p> - If the ISOLINUX parser or <i>Search for GRUB configuration</i> options won't work, then press C in GRUB to access the command line.<br/> - grub> <b>ls</b><br/> - - Get the device from above output, eg (usb0). Example:<br/> - grub> <b>cat (usb0)/isolinux/isolinux.cfg</b><br/> - - Either this will show the ISOLINUX menuentries for that ISO, or link to other .cfg files, for example /isolinux/foo.cfg.<br/> - - If it did that, then you do:<br/> - grub> <b>cat (usb0)/isolinux/foo.cfg</b><br/> - - And so on, until you find the correct menuentries for ISOLINUX. - <b>The file <i>/isolinux/foo.cfg</i> is a fictional example. Do not actually - use this example, unless you actually have that file, if it is appropriate.</b> - </p> - - <p> - For Debian or Devuan (and other debian-based distros), there are typically menuentries listed in - <i>/isolinux/txt.cfg</i> or <i>/isolinux/gtk.cfg</i>. For dual-architecture ISO images - (i686 and x86_64), there may be separate files/directories for each architecture. - Just keep searching through the image, until you find the correct ISOLINUX configuration file. - NOTE: Debian 8.6 ISO only lists 32-bit boot 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. - </p> - - <p> - Now look at the ISOLINUX menuentry. It'll look like:<br/> - <b> - kernel /path/to/kernel<br/> - append PARAMETERS initrd=/path/to/initrd MAYBE_MORE_PARAMETERS<br/> - </b> - - GRUB works the same way, but in it's own way. Example GRUB commands:<br/> - grub> <b>set root='usb0'</b><br/> - grub> <b>linux /path/to/kernel PARAMETERS MAYBE_MORE_PARAMETERS</b><br/> - grub> <b>initrd /path/to/initrd</b><br/> - grub> <b>boot</b><br/> - Note: <i>usb0</i> may be incorrect. Check the output of the <i>ls</i> 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. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div id="troubleshooting" class="section"> - - <h1>Troubleshooting</h1> - - <p> - Most of these issues occur when using libreboot with coreboot's 'text mode' instead of the coreboot framebuffer. - This mode is useful for booting payloads like memtest86+ which expect text-mode, but for GNU+Linux distributions - it can be problematic when they are trying to switch to a framebuffer because it doesn't exist. - </p> - - <p> - In most cases, you should use the vesafb ROM images. Example filename: libreboot_ukdvorak_vesafb.rom. - </p> - - <h2>parabola won't boot in text-mode</h2> - - <p> - Use one of the ROM images with vesafb in the filename (uses coreboot framebuffer instead of text-mode). - </p> - - <h2>debian-installer graphical corruption in text-mode (Debian and Devuan)</h2> - <p> - 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:<br/> - <b>vga=normal fb=false</b> - </p> - - <p> - This forces debian-installer to start in text-mode, instead of trying to switch to a framebuffer. - </p> - - <p> - If selecting text-mode from a GRUB menu created using the ISOLINUX parser, you can press E on the menu entry to add this. - Or, if you are booting manually (from GRUB terminal) then just add the parameters. - </p> - - <p> - This workaround was found on the page: <a href="https://www.debian.org/releases/stable/i386/ch05s04.html">https://www.debian.org/releases/stable/i386/ch05s04.html</a>. - It should also work for Debian, Devuan and any other apt-get distro that provides debian-installer (text mode) net install method. - </p> - - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org><br/> - Copyright © 2016 Scott Bonds <scott@ggr.com><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md new file mode 100644 index 00000000..adab1da1 --- /dev/null +++ b/docs/gnulinux/grub_boot_installer.md @@ -0,0 +1,287 @@ +<div id="pagetop" class="section"> + +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 +flash drive (and *dd*). + +- [List of recommended GNU+Linux distributions](../distros) +- [Prepare the USB drive (in GNU+Linux)](#prepare) +- [Installing GNU+Linux with full disk encryption](#encryption) +- [Debian or Devuan net install?](#debian_netinstall) +- [Booting ISOLINUX images (automatic method)](#parse_isolinux) +- [Booting ISOLINUX images (manual method)](#manual_isolinux) +- [Troubleshooting](#troubleshooting) + +[Back to previous index](./) + +</div> + +<div class="section"> + +**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.** + +</div> + +<div id="prepare" class="section"> + +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** + +Check that it wasn\'t automatically mounted. If it was, unmount it. For +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** + +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) +--------------------------------- + +[This +page](https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/) +on the NetBSD website shows how to create a NetBSD bootable USB drive +from within NetBSD itself. You should use the *dd* method documented +there. This will also work with any GNU+Linux ISO image. + +Prepare the USB drive (in FreeBSD) +---------------------------------- + +[This page](https://www.freebsd.org/doc/handbook/bsdinstall-pre.html) on +the FreeBSD website shows how to create a bootable USB drive for +installing FreeBSD. Use the *dd* on that page. You can also use the same +instructions with any GNU+Linux ISO image.. + +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** + +Check that it wasn\'t automatically mounted. If it was, unmount it. For +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**\ + +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). + +</div> + +<div id="encryption" class="section"> + +Installing GNU+Linux with full disk encryption +---------------------------------------------- + +- [Installing Debian or Devuan GNU+Linux with full disk encryption + (including /boot)](encrypted_debian.html) +- [Installing Parabola GNU+Linux with full disk encryption (including + /boot)](encrypted_parabola.html) + +[Back to top of page](#pagetop). + +</div> + +<div id="debian_netinstall" class="section"> + +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\ +initrd /install.386/initrd.gz\ +boot**\ +We recommend using the *MATE* desktop. + +[Back to top of page](#pagetop). + +</div> + +<div id="parse_isolinux" class="section"> + +Booting ISOLINUX images (automatic method) +------------------------------------------ + +Boot it in GRUB using the *Parse ISOLINUX config (USB)* option. A new +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). + +</div> + +<div id="manual_isolinux" class="section"> + +Booting ISOLINUX images (manual method) +--------------------------------------- + +*These are generic instructions. They may or may not be correct for your +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**\ +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**\ +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 +appropriate.** + +For Debian or Devuan (and other debian-based distros), there are +typically menuentries listed in */isolinux/txt.cfg* or +*/isolinux/gtk.cfg*. For dual-architecture ISO images (i686 and +x86\_64), there may be separate files/directories for each architecture. +Just keep searching through the image, until you find the correct +ISOLINUX configuration file. NOTE: Debian 8.6 ISO only lists 32-bit boot +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\ +** 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**\ +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). + +</div> + +<div id="troubleshooting" class="section"> + +Troubleshooting +=============== + +Most of these issues occur when using libreboot with coreboot\'s \'text +mode\' instead of the coreboot framebuffer. This mode is useful for +booting payloads like memtest86+ which expect text-mode, but for +GNU+Linux distributions it can be problematic when they are trying to +switch to a framebuffer because it doesn\'t exist. + +In most cases, you should use the vesafb ROM images. Example filename: +libreboot\_ukdvorak\_vesafb.rom. + +parabola won\'t boot in text-mode +--------------------------------- + +Use one of the ROM images with vesafb in the filename (uses coreboot +framebuffer instead of text-mode). + +debian-installer graphical corruption in text-mode (Debian and Devuan) +---------------------------------------------------------------------- + +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:\ +**vga=normal fb=false** + +This forces debian-installer to start in text-mode, instead of trying to +switch to a framebuffer. + +If selecting text-mode from a GRUB menu created using the ISOLINUX +parser, you can press E on the menu entry to add this. Or, if you are +booting manually (from GRUB terminal) then just add the parameters. + +This workaround was found on the page: +<https://www.debian.org/releases/stable/i386/ch05s04.html>. It should +also work for Debian, Devuan and any other apt-get distro that provides +debian-installer (text mode) net install method. + +[Back to top of page](#pagetop). + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/gnulinux/grub_cbfs.html b/docs/gnulinux/grub_cbfs.html deleted file mode 100644 index 4b1923ee..00000000 --- a/docs/gnulinux/grub_cbfs.html +++ /dev/null @@ -1,366 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>How to replace the default GRUB configuration file on a libreboot system</title> -</head> - -<body> - <div class="section"> - <h1 id="pagetop">How to replace the default GRUB configuration file on a libreboot system</h1> - <p> - Libreboot on x86 uses the GRUB <a href="http://www.coreboot.org/Payloads#GRUB_2">payload</a> - by default, which means that the GRUB configuration file - (where your GRUB menu comes from) is stored directly alongside libreboot - and its GRUB payload executable, inside - the flash chip. In context, this means that installing distributions and managing them - is handled slightly differently compared to traditional BIOS systems. - </p> - <p> - A libreboot (or coreboot) ROM image is not simply "flat"; there is an actual - filesystem inside called CBFS (coreboot filesystem). A utility called 'cbfstool' - allows you to change the contents of the ROM image. In this case, libreboot is configured - such that the 'grub.cfg' and 'grubtest.cfg' files exist directly inside CBFS instead of - inside the GRUB payload 'memdisk' (which is itself stored in CBFS). - </p> - <p> - You can either modify - the GRUB configuration stored in the flash chip, or you can modify a GRUB configuration - file on the main storage which the libreboot GRUB payload will automatically search for. - </p> - <p> - Here is an excellent writeup about CBFS (coreboot filesystem): - <a href="http://lennartb.home.xs4all.nl/coreboot/col5.html">http://lennartb.home.xs4all.nl/coreboot/col5.html</a>. - </p> - <p> - <b>This guide is *only* for the GRUB payload. If you use the depthcharge payload, ignore this section entirely.</b> - </p> - <p> - <a href="./">Back to previous index</a> - </p> - </div> - - <div class="section"> - - <h1>Table of Contents</h1> - - <ul> - <li><a href="#introduction">Introduction</a></li> - <li><a href="#option1_dont_reflash">1st option: don't re-flash</a></li> - <li> - <a href="#option2_reflash">2nd option: re-flash</a> - <ul> - <li><a href="#tools">Acquire the necessary utilities</a></li> - <li><a href="#rom">Acquiring the correct ROM image</a></li> - <li><a href="#extract_testconfig">Extract grubtest from the ROM image</a> - <li><a href="#reinsert_modified_testconfig">Re-insert the modified grubtest.cfg into the ROM image</a></li> - <li><a href="#testing">Testing</a> - <li><a href="#final_steps">Final steps</a></li> - </ul> - </li> - </ul> - - </div> - - <div class="section"> - - <h2 id="introduction">Introduction</h2> - - <p> - Download the latest release from - <a href="http://libreboot.org/">http://libreboot.org/</a> - <br/><b>If you downloaded from git, refer to - <a href="../git/#build_meta">../git/#build_meta</a> before continuing.</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - <p> - There are several advantages to modifying the GRUB configuration stored in CBFS, but - this also means that you have to flash a new libreboot ROM image on your system (some users - feel intimidated by this, to say the least). - Doing so can be risky if not handled correctly, because it can result in a bricked - system (recovery is easy if you have the <a href="../install/bbb_setup.html">equipment</a> - for it, but most people don't). 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. - </p> - - - </div> - - <div class="section"> - - <h2 id="option1_dont_reflash">1st option: don't re-flash</h2> - - <p> - By default, GRUB in libreboot is configured to scan all partitions on the main storage - for /boot/grub/libreboot_grub.cfg or /grub/libreboot_grub.cfg(for systems where /boot - is on a dedicated partition), and then use it automatically. - </p> - <p> - Simply create your custom GRUB configuration and save it to <b>/boot/grub/libreboot_grub.cfg</b> - on the running system. The next time you boot, GRUB (in libreboot) will automatically switch to - this configuration file. <b>This means that you do not have to re-flash, recompile or otherwise - modify libreboot at all!</b> - </p> - - <p> - Ideally, your distribution should automatically generate a libreboot_grub.cfg file that is written - specifically under the assumption that it will be read and used on a libreboot system that uses - GRUB as a payload. If your distribution does not do this, then you can try to add that feature - yourself or politely ask someone involved with or otherwise knowledgeable about the distribution - to do it for you. The libreboot_grub.cfg could either contain the full configuration, or it could - chainload another GRUB ELF executable (built to be used as a coreboot payload) that is located in - a partition on the main storage. - </p> - - <p> - If you want to adapt a copy of the existing <i>libreboot</i> GRUB configuration and use that for the libreboot_grub.cfg file, then - follow <a href="#tools">#tools</a>, <a href="#rom">#rom</a> and - <a href="#extract_testconfig">#extract_testconfig</a> to get the <b><i>grubtest.cfg</i></b>. - Rename <b><i>grubtest.cfg</i></b> to <b><i>libreboot_grub.cfg</i></b> and save it to <b><i>/boot/grub/</i></b> - on the running system where it is intended to be used. Modify the file at that location however you see fit, - and then stop reading this guide (the rest of this page is irrelevant to you); <b>in libreboot_grub.cfg on disk, - if you are adapting it based on grub.cfg from CBFS then remove the check for libreboot_grub.cfg otherwise it will loop.</b>. - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="option2_reflash">2nd option: re-flash</h2> - - <p> - You can modify what is stored inside the flash chip quite easily. Read on to find out how. - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - <div class="section"> - <h2 id="tools">Acquire the necessary utilities</h2> - - <p> - Use <b><i>cbfstool</i></b> and <b><i>flashrom</i></b>. There are available in the <i>libreboot_util</i> release archive, - or they can be compiled (see <a href="../git/#build_flashrom">../git/#build_flashrom</a>). - Flashrom is also available from the repositories:<br/> - # <b>pacman -S flashrom</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="rom">Acquiring the correct ROM image</h2> - - <p> - You can either work directly with one of the ROM images already included in the libreboot ROM archives, or re-use the ROM that - you have currently flashed. For the purpose of this tutorial it is assumed that your ROM image file is named <i>libreboot.rom</i>, - so please make sure to adapt. - </p> - <p> - ROM images are included pre-compiled in libreboot. You can also dump your current firmware, using flashrom:<br/> - $ <b>sudo flashrom -p internal -r libreboot.rom</b><br/> - # <b>flashrom -p internal -r libreboot.rom</b><br/> - If you are told to specify the chip, add the option <b>-c {your chip}</b> to the command, for example:<br/> - # <b>flashrom -c MX25L6405 -p internal -r libreboot.rom</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="extract_testconfig">Extract grubtest.cfg from the ROM image</h2> - - <p> - You can check the contents of the ROM image, inside CBFS:<br/> - <b>$ cd .../libreboot_util/cbfstool</b> - <b>$ ./cbfstool libreboot.rom print</b> - </p> - - <p> - The files <i>grub.cfg</i> and <i>grubtest.cfg</i> should be present. grub.cfg is loaded by default, - with a menuentry for switching to grubtest.cfg. In this tutorial, you will first modify and test <i>grubtest.cfg</i>. - This is to reduce the possibility of bricking your device, so DO NOT SKIP THIS! - </p> - - <p> - Extract grubtest.cfg from the ROM image:<br/> - <b>$ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg</b> - </p> - - <p> - Modify the grubtest.cfg accordingly. - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="reinsert_modified_testconfig">Re-insert the modified grubtest.cfg into the ROM image</h2> - - <p> - Once your grubtest.cfg is modified and saved, delete the unmodified config from the ROM image:<br/> - <b>$ ./cbfstool libreboot.rom remove -n grubtest.cfg</b> - </p> - - <p> - Next, insert the modified version:<br/> - <b>$ ./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t raw</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="testing">Testing</h2> - - <p> - <b> - Now you have a modified ROM. Refer back to <a href="../install/#flashrom">../install/#flashrom</a> for information - on how to flash it.<br/> - $ <b>cd /libreboot_util</b> - # <b>./flash update libreboot.rom</b><br/> - 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:<br/> - # <b>./flash forceupdate libreboot.rom</b><br/> - You should see <b>"Verifying flash... VERIFIED."</b> written at the end of the flashrom output. - Once you have done that, shut down and then boot up with your new test configuration. - </b> - </p> - - <p> - Choose (in GRUB) the menu entry that switches to grubtest.cfg. If it works, then your config is safe and you can continue below. - </p> - - <p> - <b> - 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 new configuration is safe (or desirable) to use. - </b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h2 id="final_steps">Final steps</h2> - - <p> - When you are satisfied booting from grubtest.cfg, you can create a copy of grubtest.cfg, called grub.cfg. This is the same except for one difference: - the menuentry 'Switch to grub.cfg' will be changed to 'Switch to grubtest.cfg' and inside it, - all instances of grub.cfg 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:<br/> - $ <b>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</b><br/> - </p> - - <p> - Delete the grub.cfg that remained inside the ROM:<br/> - <b>$ ./cbfstool libreboot.rom remove -n grub.cfg</b> - </p> - - <p> - Add the modified version that you just made:<br/> - <b>$ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw</b> - </p> - - <p> - <b> - Now you have a modified ROM. Again, refer back to <a href="../install/#flashrom">../install/#flashrom</a> 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. - </b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - Copyright © 2015 Jeroen Quint <jezza@diplomail.ch><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md new file mode 100644 index 00000000..1dd1a983 --- /dev/null +++ b/docs/gnulinux/grub_cbfs.md @@ -0,0 +1,305 @@ +<div class="section"> + +How to replace the default GRUB configuration file on a libreboot system {#pagetop} +======================================================================== + +Libreboot on x86 uses the GRUB +[payload](http://www.coreboot.org/Payloads#GRUB_2) by default, which +means that the GRUB configuration file (where your GRUB menu comes from) +is stored directly alongside libreboot and its GRUB payload executable, +inside the flash chip. In context, this means that installing +distributions and managing them is handled slightly differently compared +to traditional BIOS systems. + +A libreboot (or coreboot) ROM image is not simply \"flat\"; there is an +actual filesystem inside called CBFS (coreboot filesystem). A utility +called \'cbfstool\' allows you to change the contents of the ROM image. +In this case, libreboot is configured such that the \'grub.cfg\' and +\'grubtest.cfg\' files exist directly inside CBFS instead of inside the +GRUB payload \'memdisk\' (which is itself stored in CBFS). + +You can either modify the GRUB configuration stored in the flash chip, +or you can modify a GRUB configuration file on the main storage which +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 +depthcharge payload, ignore this section entirely.** + +[Back to previous index](./) + +</div> + +<div class="section"> + +Table of Contents +================= + +- [Introduction](#introduction) +- [1st option: don\'t re-flash](#option1_dont_reflash) +- [2nd option: re-flash](#option2_reflash) + - [Acquire the necessary utilities](#tools) + - [Acquiring the correct ROM image](#rom) + - [Extract grubtest from the ROM image](#extract_testconfig) + - [Re-insert the modified grubtest.cfg into the ROM + image](#reinsert_modified_testconfig) + - [Testing](#testing) + - [Final steps](#final_steps) + +</div> + +<div class="section"> + +Introduction +------------ + +Download the latest release from <http://libreboot.org/>\ +**If you downloaded from git, refer to +[../git/\#build\_meta](../git/#build_meta) before continuing.** + +[Back to top of page.](#pagetop) + +There are several advantages to modifying the GRUB configuration stored +in CBFS, but this also means that you have to flash a new libreboot ROM +image on your system (some users feel intimidated by this, to say the +least). Doing so can be risky if not handled correctly, because it can +result in a bricked system (recovery is easy if you have the +[equipment](../install/bbb_setup.html) for it, but most people don\'t). +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. + +</div> + +<div class="section"> + +1st option: don\'t re-flash {#option1_dont_reflash} +--------------------------- + +By default, GRUB in libreboot is configured to scan all partitions on +the main storage for /boot/grub/libreboot\_grub.cfg or +/grub/libreboot\_grub.cfg(for systems where /boot is on a dedicated +partition), and then use it automatically. + +Simply create your custom GRUB configuration and save it to +**/boot/grub/libreboot\_grub.cfg** on the running system. The next time +you boot, GRUB (in libreboot) will automatically switch to this +configuration file. **This means that you do not have to re-flash, +recompile or otherwise modify libreboot at all!** + +Ideally, your distribution should automatically generate a +libreboot\_grub.cfg file that is written specifically under the +assumption that it will be read and used on a libreboot system that uses +GRUB as a payload. If your distribution does not do this, then you can +try to add that feature yourself or politely ask someone involved with +or otherwise knowledgeable about the distribution to do it for you. The +libreboot\_grub.cfg could either contain the full configuration, or it +could chainload another GRUB ELF executable (built to be used as a +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 +***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 +location however you see fit, and then stop reading this guide (the rest +of this page is irrelevant to you); **in libreboot\_grub.cfg on disk, if +you are adapting it based on grub.cfg from CBFS then remove the check +for libreboot\_grub.cfg otherwise it will loop.**. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +2nd option: re-flash {#option2_reflash} +-------------------- + +You can modify what is stored inside the flash chip quite easily. Read +on to find out how. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Acquiring the correct ROM image {#rom} +------------------------------- + +You can either work directly with one of the ROM images already included +in the libreboot ROM archives, or re-use the ROM that you have currently +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**\ +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** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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 +print** + +The files *grub.cfg* and *grubtest.cfg* should be present. grub.cfg is +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** + +Modify the grubtest.cfg accordingly. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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:\ +**\$ ./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t +raw** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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**\ +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 the flashrom output. Once you have done that, shut down and then boot +up with your new test configuration.** + +Choose (in GRUB) the menu entry that switches to grubtest.cfg. If it +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 +new configuration is safe (or desirable) to use.** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Final steps {#final_steps} +----------- + +When you are satisfied booting from grubtest.cfg, you can create a copy +of grubtest.cfg, called grub.cfg. This is the same except for one +difference: the menuentry \'Switch to grub.cfg\' will be changed to +\'Switch to grubtest.cfg\' and inside it, all instances of grub.cfg 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:\ +\$ **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** + +**Now you have a modified ROM. Again, refer back 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) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/gnulinux/grub_hardening.html b/docs/gnulinux/grub_hardening.html deleted file mode 100644 index f86b7c4d..00000000 --- a/docs/gnulinux/grub_hardening.html +++ /dev/null @@ -1,281 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>GRUB hardening</title> -</head> - -<body> - <div class="section"> - <h1>GRUB hardening</h1> - <p> - This guide deals with various ways in which you can harden - your GRUB configuration, for security purposes. These steps - are optional, but highly recommended by the Libreboot project. - </p> - <p> - <a href="./">Back to previous index</a> - </p> - </div> - <div class="section"> - <h1> - GRUB secure boot with GPG - </h1> - - <p> - This uses the free implementation of the GPG standard for encryption - and signing/verifying data. We will be using this for checking the signature - of a Linux kernel at boot time. - More information about GPG can be found on the - <a href="https://www.gnu.org/software/gnupg/">GPG project website</a>. - GRUB has some GPG support built in, for checking signatures. - </p> - - <p> - This tutorial assumes you have a libreboot image (rom) that you wish to modify, - to which we shall henceforth refer to as "my.rom". - This tutorial modifies grubtest.cfg, this means signing and password protection - will work after switching to it in the main boot menu and bricking due to - incorrect configuration will be impossible. - After you are satisfied with the setup, you should transfer the new settings - to grub.cfg to make your machine actually secure. - </p> - - <p> - First extract the old grubtest.cfg and remove it from the libreboot image: -<pre> -cbfstool my.rom extract -n grubtest.cfg -f my.grubtest.cfg -cbfstool my.rom remove -n grubtest.cfg -</pre> - </p> - <p> - Helpful links: - <ul> - <li><a href="https://www.gnu.org/software/grub/manual/html_node/Security.html#Security"> - GRUB manual #security</a></li> - <li><a href="http://git.savannah.gnu.org/cgit/grub.git/tree/docs/grub.texi"> - GRUB info pages</a></li> - <li><a href="https://libreboot.org/faq/#firmware-hddssd"> - SATA connected storage considered dangerous until proven otherwise.</a></li> - <li><a href="https://www.coreboot.org/GRUB2#Security"> - Coreboot GRUB security howto</a></li> - </ul> - </p> - </div> - <div class="section"> - <h1> - GRUB Password - </h1> - <p> - The security of this setup depends on a good GRUB password as GPG signature - checking can be disabled through the interactive console: - </p> - <pre>set check_signatures=no</pre> - <p> - This is good in that it allows you to occasionally boot unsigned liveCDs and such. - You may think of supplying signatures on an usb key, but the signature - checking code currently looks for </path/to/filename>.sig when verifying - </path/to/filename> and as such it is not possible to supply signatures - in an alternate location. - </p> - <p> - Note that this is not your LUKS password, but it's a password that you have to - enter in order to use "restricted" functionality (such as console). This - protects your system from an attacker simply booting a live USB and re-flashing - your firmware. - <b>This should be different than your LUKS passphrase and user password.</b> - </p> - - <p> - Use of the <i>diceware method</i> is recommended, for generating secure passphrases (as opposed to passwords). - Diceware method involves using dice to generate random numbers, which are - then used as an index to pick a random word from a large dictionary of words. - You can use any language (e.g. English, German). - Look it up on a search engine. Diceware method is a way to generate - secure passphrases that are very hard (almost impossible, with enough words) - to crack, while being easy enough to remember. On the other hand, most - kinds of secure passwords are hard to remember and easier to crack. - Diceware passphrases are harder to crack because of far higher entropy - (there are many words available to use, but only about 50 commonly used symbols - in pass<em>words</em>). - </p> ---> - <p> - The GRUB password can be entered in two ways: - <ul> - <li>plaintext</li> - <li>protected with <a href="https://en.wikipedia.org/wiki/Pbkdf2">PBKDF2</a></li> - </ul> - We will (obviously) use the later. Generating the PBKDF2 derived key is done - using the <b>grub-mkpasswd-pbkdf2</b> utility. You can get it by installing - GRUB version 2. Generate a key by giving it a password: - </p> - <pre>grub-mkpasswd-pbkdf2</pre> - <p> - Its output will be a string of the following form: - grub.pbkdf2.sha512.10000.HEXDIGITS.MOREHEXDIGITS - </p> - <p> - Now open my.grubtest.cfg and put the following before the menu entries (prefered - above the functions and after other directives). Of course use the pbdkf string - that you had generated yourself: - </p> - <pre> -set superusers="root" -password_pbkdf2 root grub.pbkdf2.sha512.10000.711F186347156BC105CD83A2ED7AF1EB971AA2B1EB2640172F34B0DEFFC97E654AF48E5F0C3B7622502B76458DA494270CC0EA6504411D676E6752FD1651E749.8DD11178EB8D1F633308FD8FCC64D0B243F949B9B99CCEADE2ECA11657A757D22025986B0FA116F1D5191E0A22677674C994EDBFADE62240E9D161688266A711</pre> - <p> - Obviously, replace it with the correct hash that you actually got for the password - that you entered. Meaning, not the hash that you see above! - </p> - <p> - As enabling password protection as above means that you have to input it on - every single boot, we will make one menu entry work without it. Remember that - we will have GPG signing active, thus a potential attacker will not be able - to boot an arbitrary operating system. We do this by adding option - <b>--unrestricted</b> to a menuentry definition: - </p> - <pre>menuentry 'Load Operating System (incl. fully encrypted disks) [o]' --hotkey='o' --unrestricted { -...</pre> - <p> - Another good thing to do, if we chose to load signed on-disk GRUB configurations, - is to remove (or comment out) <b>unset superusers</b> in function try_user_config: - </p> - <pre> -function try_user_config { - 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 - #unset superusers - configfile /"${dir}"/"${name}"grub.cfg - fi - done - done -}</pre> - <p> - Why? We allowed booting normally without entering a password above. - When we unset superusers and then load a signed GRUB configuration file, - we can easily use the command line as password protection will be completely - disabled. Disabling signature checking and booting whatever an attacker wants - is then just a few GRUB commands away. - </p> - - <p> - As far as basic password setup is concerned we are done and we can now move on to signing. - </p> - </div> - <div class="section"> - <h1> - GPG keys - </h1> - <p> - First generate a GPG keypair to use for signing. Option RSA (sign only) is ok. - </p> - <p> - <b>Warning:</b> GRUB does not read ASCII armored keys. - When attempting to trust ... a key filename it will print error: bad signature - </p> - <pre> -mkdir --mode 0700 keys -gpg --homedir keys --gen-key -gpg --homedir keys --export-secret-keys --armor > boot.secret.key # backup -gpg --homedir keys --export > boot.key</pre> - - <p> - Now that we have a key, we can sign some files with it. We have to sign: - <ul> - <li>a kernel</li> - <li>(if we have one) an initramfs</li> - <li>(if we wish to transfer control to it) an on-disk grub.cfg</li> - <li>grubtest.cfg (this is so one can go back to grubtest.cfg after signature - checking is enforced. You can always get back to grub.cfg by pressing ESC, - but afterwards grubtest.cfg is not signed and it will not load.</li> - </ul> - - Suppose that we have a pair of <b>my.kernel</b> and <b>my.initramfs</b> - and an on-disk <b>libreboot_grub.cfg</b>. We sign them by issuing the - following commands: - </p> -<pre> -gpg --homedir keys --detach-sign my.initramfs -gpg --homedir keys --detach-sign my.kernel -gpg --homedir keys --detach-sign libreboot_grub.cfg -gpg --homedir keys --detach-sign my.grubtest.cfg -</pre> - <p> - Of course some further modifications to my.grubtest.cfg will be required. - We have to trust the key and enable signature enforcement - (put this before menu entries): - </p> -<pre> -trust (cbfsdisk)/boot.key -set check_signatures=enforce -</pre> - <p> - What remains now is to include the modifications into the image (rom): - </p> -<pre> -cbfstool my.rom add -n boot.key -f boot.key -t raw -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 -</pre> - <p> - ... and flashing it. - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2017 Fedja Beader <fedja@protonmail.ch><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - </div> - -</body> -</html> diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md new file mode 100644 index 00000000..e2a6a6a1 --- /dev/null +++ b/docs/gnulinux/grub_hardening.md @@ -0,0 +1,234 @@ +<div class="section"> + +GRUB hardening +============== + +This guide deals with various ways in which you can harden your GRUB +configuration, for security purposes. These steps are optional, but +highly recommended by the Libreboot project. + +[Back to previous index](./) + +</div> + +<div class="section"> + +GRUB secure boot with GPG +========================= + +This uses the free implementation of the GPG standard for encryption and +signing/verifying data. We will be using this for checking the signature +of a Linux kernel at boot time. More information about GPG can be found +on the [GPG project website](https://www.gnu.org/software/gnupg/). GRUB +has some GPG support built in, for checking signatures. + +This tutorial assumes you have a libreboot image (rom) that you wish to +modify, to which we shall henceforth refer to as \"my.rom\". This +tutorial modifies grubtest.cfg, this means signing and password +protection will work after switching to it in the main boot menu and +bricking due to incorrect configuration will be impossible. After you +are satisfied with the setup, you should transfer the new settings to +grub.cfg to make your machine actually secure. + +First extract the old grubtest.cfg and remove it from the libreboot +image: + + cbfstool my.rom extract -n grubtest.cfg -f my.grubtest.cfg + cbfstool my.rom remove -n grubtest.cfg + +Helpful links: + +- [GRUB manual + \#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 + otherwise.](https://libreboot.org/faq/#firmware-hddssd) +- [Coreboot GRUB security + howto](https://www.coreboot.org/GRUB2#Security) + +</div> + +<div class="section"> + +GRUB Password +============= + +The security of this setup depends on a good GRUB password as GPG +signature checking can be disabled through the interactive console: + + set check_signatures=no + +This is good in that it allows you to occasionally boot unsigned liveCDs +and such. You may think of supplying signatures on an usb key, but the +signature checking code currently looks for +</path/to/filename>.sig when verifying </path/to/filename> +and as such it is not possible to supply signatures in an alternate +location. + +Note that this is not your LUKS password, but it\'s a password that you +have to enter in order to use \"restricted\" functionality (such as +console). This protects your system from an attacker simply booting a +live USB and re-flashing your firmware. **This should be different than +your LUKS passphrase and user password.** + +Use of the *diceware method* is recommended, for generating secure +passphrases (as opposed to passwords). Diceware method involves using +dice to generate random numbers, which are then used as an index to pick +a random word from a large dictionary of words. You can use any language +(e.g. English, German). Look it up on a search engine. Diceware method +is a way to generate secure passphrases that are very hard (almost +impossible, with enough words) to crack, while being easy enough to +remember. On the other hand, most kinds of secure passwords are hard to +remember and easier to crack. Diceware passphrases are harder to crack +because of far higher entropy (there are many words available to use, +but only about 50 commonly used symbols in pass*words*). + +\--> +The GRUB password can be entered in two ways: + +- plaintext +- protected with [PBKDF2](https://en.wikipedia.org/wiki/Pbkdf2) + +We will (obviously) use the later. Generating the PBKDF2 derived key is +done using the **grub-mkpasswd-pbkdf2** utility. You can get it by +installing GRUB version 2. Generate a key by giving it a password: + grub-mkpasswd-pbkdf2 + +Its output will be a string of the following form: +grub.pbkdf2.sha512.10000.HEXDIGITS.MOREHEXDIGITS + +Now open my.grubtest.cfg and put the following before the menu entries +(prefered above the functions and after other directives). Of course use +the pbdkf string that you had generated yourself: + + set superusers="root" + password_pbkdf2 root grub.pbkdf2.sha512.10000.711F186347156BC105CD83A2ED7AF1EB971AA2B1EB2640172F34B0DEFFC97E654AF48E5F0C3B7622502B76458DA494270CC0EA6504411D676E6752FD1651E749.8DD11178EB8D1F633308FD8FCC64D0B243F949B9B99CCEADE2ECA11657A757D22025986B0FA116F1D5191E0A22677674C994EDBFADE62240E9D161688266A711 + +Obviously, replace it with the correct hash that you actually got for +the password that you entered. Meaning, not the hash that you see above! + +As enabling password protection as above means that you have to input it +on every single boot, we will make one menu entry work without it. +Remember that we will have GPG signing active, thus a potential attacker +will not be able to boot an arbitrary operating system. We do this by +adding option **\--unrestricted** to a menuentry definition: + + menuentry 'Load Operating System (incl. fully encrypted disks) [o]' --hotkey='o' --unrestricted { + ... + +Another good thing to do, if we chose to load signed on-disk GRUB +configurations, is to remove (or comment out) **unset superusers** in +function try\_user\_config: + + function try_user_config { + 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 + #unset superusers + configfile /"${dir}"/"${name}"grub.cfg + fi + done + done + } + +Why? We allowed booting normally without entering a password above. When +we unset superusers and then load a signed GRUB configuration file, we +can easily use the command line as password protection will be +completely disabled. Disabling signature checking and booting whatever +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. + +</div> + +<div class="section"> + +GPG keys +======== + +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 + + mkdir --mode 0700 keys + gpg --homedir keys --gen-key + gpg --homedir keys --export-secret-keys --armor > boot.secret.key # backup + gpg --homedir keys --export > boot.key + +Now that we have a key, we can sign some files with it. We have to sign: + +- a kernel +- (if we have one) an initramfs +- (if we wish to transfer control to it) an on-disk grub.cfg +- grubtest.cfg (this is so one can go back to grubtest.cfg after + signature checking is enforced. You can always get back to grub.cfg + by pressing ESC, but afterwards grubtest.cfg is not signed and it + will not load. + +Suppose that we have a pair of **my.kernel** and **my.initramfs** and an +on-disk **libreboot\_grub.cfg**. We sign them by issuing the following +commands: + gpg --homedir keys --detach-sign my.initramfs + gpg --homedir keys --detach-sign my.kernel + gpg --homedir keys --detach-sign libreboot_grub.cfg + gpg --homedir keys --detach-sign my.grubtest.cfg + +Of course some further modifications to my.grubtest.cfg will be +required. We have to trust the key and enable signature enforcement (put +this before menu entries): + + trust (cbfsdisk)/boot.key + set check_signatures=enforce + +What remains now is to include the modifications into the image (rom): + + cbfstool my.rom add -n boot.key -f boot.key -t raw + 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. + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/gnulinux/index.html b/docs/gnulinux/index.html deleted file mode 100644 index 2b1ef868..00000000 --- a/docs/gnulinux/index.html +++ /dev/null @@ -1,93 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>GNU+Linux distributions</title> -</head> - -<body> - - <div class="section"> - - <h1 id="pagetop">GNU+Linux distributions</h1> - <p> - This section relates to dealing with GNU+Linux distributions: preparing bootable USB drives, - changing the default GRUB menu and so on. - </p> - <p> - <b>This section is only for the *GRUB* payload. For depthcharge, instructions have yet to be written.</b> - </p> - <p> - <a href="../">Back to previous index</a>. - </p> - <ul> - <li><a href="grub_boot_installer.html">How to install GNU+Linux on a libreboot system</a></li> - <li><a href="grub_cbfs.html">How to replace the default GRUB configuration file on a libreboot system</a></li> - <li> - <a href="encrypted_parabola.html">Installing Parabola or Arch GNU+Linux-libre with full disk encryption (including /boot)</a> - <ul> - <li>Follow-up tutorial: <a href="configuring_parabola.html">Configuring Parabola (post-install)</a></li> - </ul> - </li> - <li><a href="encrypted_debian.html">Installing Debian or Devuan GNU+Linux-libre with full disk encryption (including /boot)</a></li> - <li><a href="grub_hardening.html">How to harden your GRUB configuration, for security</a></li> - </ul> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/gnulinux/index.md b/docs/gnulinux/index.md new file mode 100644 index 00000000..070296bb --- /dev/null +++ b/docs/gnulinux/index.md @@ -0,0 +1,65 @@ +<div class="section"> + +GNU+Linux distributions {#pagetop} +======================= + +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, +instructions have yet to be written.** + +[Back to previous index](../). + +- [How to install GNU+Linux on a libreboot + system](grub_boot_installer.html) +- [How to replace the default GRUB configuration file on a libreboot + system](grub_cbfs.html) +- [Installing Parabola or Arch GNU+Linux-libre with full disk + encryption (including /boot)](encrypted_parabola.html) + - Follow-up tutorial: [Configuring Parabola + (post-install)](configuring_parabola.html) +- [Installing Debian or Devuan GNU+Linux-libre with full disk + encryption (including /boot)](encrypted_debian.html) +- [How to harden your GRUB configuration, for + security](grub_hardening.html) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/grub/index.html b/docs/grub/index.html deleted file mode 100644 index 78beb3e6..00000000 --- a/docs/grub/index.html +++ /dev/null @@ -1,190 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>GRUB payload</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">GRUB payload</h1> - <p> - This section relates to the GRUB payload used in libreboot. - </p> - <p> - Or <a href="../">Back to main index</a>. - </p> - <ul> - <li><a href="#grub_background">Changing the background image in GRUB</a></li> - <li><a href="#grub_font">Setting font in GRUB</a></li> - <li><a href="#grub_keyboard">GRUB keyboard layouts</a> - <ul> - <li><a href="#grub_custom_keyboard">Custom keyboard layout in GRUB</a></li> - <li><a href="#grub_ukdvorak_keyboard">UK Dvorak keyboard layout in GRUB</a></li> - </ul> - </li> - </ul> - </div> - - <div class="section"> - - <h1 id="grub_background">Changing the background image in GRUB</h1> - - <p> - Use cbfstool from libreboot_util, or libreboot_src/coreboot/util/cbfstool/ if you want to build from source. - </p> - <p> - ./cbfstool yourrom.rom remove background.png -n background.png<br/> - ./cbfstool yourrom.rom add -f background.png -n background.png -t raw - </p> - <p> - When you've done this, re-flash your ROM and you should have a new background at boot time. - </p> - - </div> - - <div class="section"> - - <h1 id="grub_font">Setting font in GRUB (for reference)</h1> - - <p>You don't need to do this unless you would like to change the default font yourself. - (this is just for reference. It has already been done for you)</p> - - <p>The old font used was Unifont, and this had some missing characters: for instance, the border showed ??? characters instead of lines.</p> - - <p>I tried DeJavu Sans Mono from this website: - <a href="http://dejavu-fonts.org/wiki/Download">dejavu-fonts.org</a></p> - - <p>Specifically, the version that I chose was the latest at the time of writing (Saturday 21 June 2014): - <a href="http://sourceforge.net/projects/dejavu/files/dejavu/2.34/dejavu-fonts-ttf-2.34.tar.bz2">this one</a></p> - - <p>This is a free font that is also contained in GNU+Linux distributions like Debian, Devuan or Parabola.</p> - - <p><b>$ cd libreboot_src/grub</b><br/> - compile grub (the build scripts info on how to do this)<br/> - come back out into libreboot_src/resources/grub:<br/> - <b>$ cd ../libreboot_src/resources/grub/font</b></p> - - <p>I took Dejavu Sans Mono from dejavu (included in this version of libreboot) and did:<br/> - <b>$ ../../../grub/grub-mkfont -o dejavusansmono.pf2 dejavu-fonts-ttf-2.34/ttf/DejaVuSansMono.ttf</b></p> - - <p>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.<br/> - I then added that instructions to the grub.cfg files (to load the font):<br/> - <b>loadfont (memdisk)/dejavusansmono.pf2</b></p> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h1 id="grub_keyboard">GRUB keyboard layouts (for reference)</h1> - - <div class="subsection"> - - <h2 id="grub_custom_keyboard">Custom keyboard layout in GRUB (for reference)</h2> - - <p> - Keymaps are stored in resources/utilities/grub-assemble/keymap/. - </p> - - <p> - Example (French Azerty):<br/> - <b>$ ckbcomp fr > frazerty</b><br/><br/> - Go in grub directory:<br/> - <b>cat frazerty | ./grub/grub-mklayout -o frazerty.gkb</b> - </p> - - <p> - You must make sure that the files are named keymap and keymap.gkb (where 'keymap' can be whatever you want). - </p> - - <p> - Then from the above example, you would put <b>frazerty</b> in <b>resources/utilities/grub-assemble/keymap/original/</b> and - the <b>frazerty.gkb</b> file goes under <b>resources/utilities/grub-assemble/keymap/</b> - </p> - - <p> - 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: <b>libreboot_frazerty.rom</b>. - </p> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="subsection"> - - <h2 id="grub_ukdvorak_keyboard">UK Dvorak keyboard layout in GRUB (for reference)</h2> - - <p> - 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 - </p> - - <p><b>$ cat ukdvorak | ./grub/grub-mklayout -o ukdvorak.gkb</b></p> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - </div> - - <div class="section"> - - <p> - Copyright © 2014 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/grub/index.md b/docs/grub/index.md new file mode 100644 index 00000000..2ca95bc8 --- /dev/null +++ b/docs/grub/index.md @@ -0,0 +1,164 @@ +<div class="section"> + +GRUB payload {#pagetop} +============ + +This section relates to the GRUB payload used in libreboot. + +Or [Back to main index](../). + +- [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) + +</div> + +<div class="section"> + +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 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. + +</div> + +<div class="section"> + +Setting font in GRUB (for reference) {#grub_font} +==================================== + +You don\'t need to do this unless you would like to change the default +font yourself. (this is just for reference. It has already been done for +you) + +The old font used was Unifont, and this had some missing characters: for +instance, the border showed ??? characters instead of lines. + +I tried DeJavu Sans Mono from this website: +[dejavu-fonts.org](http://dejavu-fonts.org/wiki/Download) + +Specifically, the version that I chose was the latest at the time of +writing (Saturday 21 June 2014): [this +one](http://sourceforge.net/projects/dejavu/files/dejavu/2.34/dejavu-fonts-ttf-2.34.tar.bz2) + +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** + +I took Dejavu Sans Mono from dejavu (included in this version of +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.\ +I then added that instructions to the grub.cfg files (to load the +font):\ +**loadfont (memdisk)/dejavusansmono.pf2** + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +GRUB keyboard layouts (for reference) {#grub_keyboard} +===================================== + +<div class="subsection"> + +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:\ +**cat frazerty | ./grub/grub-mklayout -o frazerty.gkb** + +You must make sure that the files are named keymap and keymap.gkb (where +\'keymap\' can be whatever you want). + +Then from the above example, you would put **frazerty** in +**resources/utilities/grub-assemble/keymap/original/** and the +**frazerty.gkb** file goes under +**resources/utilities/grub-assemble/keymap/** + +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) + +</div> + +<div class="subsection"> + +UK Dvorak keyboard layout in GRUB (for reference) {#grub_ukdvorak_keyboard} +------------------------------------------------- + +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** + +[Back to top of page](#pagetop) + +</div> + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hardware/dock.html b/docs/hardware/dock.html deleted file mode 100644 index 6dc54322..00000000 --- a/docs/hardware/dock.html +++ /dev/null @@ -1,190 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Notes about DMA and the docking station (X60/T60)</title> -</head> - -<body> - <div class="section"> - <h1>Notes about DMA and the docking station (X60/T60)</h1> - </div> - - <div class="section"> -<pre> - -Use case: ---------- -Usually when people do full disk encryption, it's not really full disk, -instead they still have a /boot in clear. - -So an evil maid attack can still be done, in two passes: -1) Clone the hdd, Infect the initramfs or the kernel. -2) Wait for the user to enter its password, recover the password, -luksOpen the hdd image. - -I wanted a real full-disk encryption so I've put grub in flash and I -have the following: The HDD has a LUKS rootfs(containing /boot) on an -lvm partition, so no partition is in clear. - -So when the computer boots it executes coreboot, then grub as a payload. -Grub then opens the LUKS partition and loads the kernel and initramfs -from there. - -To prevent hardware level tempering(like reflashing), I used nail -polish with a lot of gilder, that acts like a seal. Then a high -resolution picture of it is taken, to be able to tell the difference. - -The problem: ------------- -But then comes the docking port issue: Some LPC pins are exported -there, such as the CLKRUN and LDRQ#. - -LDRQ# is "Encoded DMA/Bus Master Request": "Only needed by -peripherals that need DMA or bus mastering. Requires an -individual signal per peripheral. Peripherals may not share -an LDRQ# signal." - -So now DMA access is possible trough the dock connector. -So I want to be able to turn that off. - -If I got it right, the X60 has 2 superio, one is in the dock, and the -other one is in the laptop, so we have: - ________________ - _________________ | | -| | | Dock connector:| -|Dock: NSC pc87982|<--LPC--->D_LPC_DREQ0 | -|_________________| |_______^________| - | - | - | - | - ___________________|____ - | v | - | SuperIO: DLDRQ# | - | NSC pc87382 LDRQ# | - |___________________^____| - | - | - | - | - ___________________|___ - | v | - | Southbridge: LDRQ0 | - | ICH7 | - |_______________________| - - -The code: ---------- -Now if I look at the existing code, there is some superio drivers, like -pc87382 in src/superio/nsc, the code is very small. -The only interesting part is the pnp_info pnp_dev_info struct. - -Now if I look inside src/mainboard/lenovo/x60 there is some more -complete dock driver: - -Inside dock.c I see some dock_connect and dock_disconnect functions. - -Such functions are called during the initialisation (romstage.c) and -from the X60 SMI handler (smihandler.c). - -Questions: ----------- -1) Would the following be sufficent to prevent DMA access from the -outside: -> int dock_connect(void) -> { -> int timeout = 1000; -> + int val; -> + -> + if (get_option(&val, "dock") != CB_SUCCESS) -> + val = 1; -> + if (val == 0) -> + return 0; -> [...] -> } -> -> void dock_disconnect(void) { -> + if (dock_present()) -> + return; -> [...] -> } -2) Would an nvram option be ok for that? Should a Kconfig option be -added too? - -> config DOCK_AUTODETECT -> bool "Autodetect" -> help -> The dock is autodetected. If unsure select this option. -> -> config DOCK_DISABLED -> bool "Disabled" -> help -> The dock is always disabled. -> -> config DOCK_NVRAM_ENABLE -> bool "Nvram" -> help -> The dock autodetection is tried only if it is also enabled -> trough nvram. - -</pre> - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hardware/dock.md b/docs/hardware/dock.md new file mode 100644 index 00000000..4602fc02 --- /dev/null +++ b/docs/hardware/dock.md @@ -0,0 +1,165 @@ +<div class="section"> + +Notes about DMA and the docking station (X60/T60) +================================================= + +</div> + +<div class="section"> + + + Use case: + --------- + Usually when people do full disk encryption, it's not really full disk, + instead they still have a /boot in clear. + + So an evil maid attack can still be done, in two passes: + 1) Clone the hdd, Infect the initramfs or the kernel. + 2) Wait for the user to enter its password, recover the password, + luksOpen the hdd image. + + I wanted a real full-disk encryption so I've put grub in flash and I + have the following: The HDD has a LUKS rootfs(containing /boot) on an + lvm partition, so no partition is in clear. + + So when the computer boots it executes coreboot, then grub as a payload. + Grub then opens the LUKS partition and loads the kernel and initramfs + from there. + + To prevent hardware level tempering(like reflashing), I used nail + polish with a lot of gilder, that acts like a seal. Then a high + resolution picture of it is taken, to be able to tell the difference. + + The problem: + ------------ + But then comes the docking port issue: Some LPC pins are exported + there, such as the CLKRUN and LDRQ#. + + LDRQ# is "Encoded DMA/Bus Master Request": "Only needed by + peripherals that need DMA or bus mastering. Requires an + individual signal per peripheral. Peripherals may not share + an LDRQ# signal." + + So now DMA access is possible trough the dock connector. + So I want to be able to turn that off. + + If I got it right, the X60 has 2 superio, one is in the dock, and the + other one is in the laptop, so we have: + ________________ + _________________ | | + | | | Dock connector:| + |Dock: NSC pc87982|<--LPC--->D_LPC_DREQ0 | + |_________________| |_______^________| + | + | + | + | + ___________________|____ + | v | + | SuperIO: DLDRQ# | + | NSC pc87382 LDRQ# | + |___________________^____| + | + | + | + | + ___________________|___ + | v | + | Southbridge: LDRQ0 | + | ICH7 | + |_______________________| + + + The code: + --------- + Now if I look at the existing code, there is some superio drivers, like + pc87382 in src/superio/nsc, the code is very small. + The only interesting part is the pnp_info pnp_dev_info struct. + + Now if I look inside src/mainboard/lenovo/x60 there is some more + complete dock driver: + + Inside dock.c I see some dock_connect and dock_disconnect functions. + + Such functions are called during the initialisation (romstage.c) and + from the X60 SMI handler (smihandler.c). + + Questions: + ---------- + 1) Would the following be sufficent to prevent DMA access from the + outside: + > int dock_connect(void) + > { + > int timeout = 1000; + > + int val; + > + + > + if (get_option(&val, "dock") != CB_SUCCESS) + > + val = 1; + > + if (val == 0) + > + return 0; + > [...] + > } + > + > void dock_disconnect(void) { + > + if (dock_present()) + > + return; + > [...] + > } + 2) Would an nvram option be ok for that? Should a Kconfig option be + added too? + + > config DOCK_AUTODETECT + > bool "Autodetect" + > help + > The dock is autodetected. If unsure select this option. + > + > config DOCK_DISABLED + > bool "Disabled" + > help + > The dock is always disabled. + > + > config DOCK_NVRAM_ENABLE + > bool "Nvram" + > help + > The dock autodetection is tried only if it is also enabled + > trough nvram. + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hardware/index.html b/docs/hardware/index.html deleted file mode 100644 index d89d7212..00000000 --- a/docs/hardware/index.html +++ /dev/null @@ -1,84 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Hardware modifications</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Hardware modifications</h1> - <p> - This section relates to hardware maintenance on supported targets. - </p> - <p> - <a href="../">Back to previous index</a>. - </p> - <ul> - <li><a href="x60_keyboard.html">ThinkPad X60/X60s/X60T: Change keyboard</a> (the procedure on X200/X200S/X200T is almost identical)</li> - <li><a href="x60_heatsink.html">ThinkPad X60/X60S: change the fan/heatsink</a></li> - <li><a href="x60_lcd_change.html">ThinkPad X60/X60s: How to change the LCD panel</a> (incomplete. pics only for now)</li> - <li><a href="t60_lcd_15.html">ThinkPad T60 15.1" changing LCD panel</a></li> - <li><a href="t60_heatsink.html">ThinkPad T60: change the fan/heatsink</a></li> - <li><a href="x60_security.html">ThinkPad X60/X60S: hardware security</a></li> - <li><a href="t60_security.html">ThinkPad T60: hardware security</a></li> - </ul> - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hardware/index.md b/docs/hardware/index.md new file mode 100644 index 00000000..99b8ed91 --- /dev/null +++ b/docs/hardware/index.md @@ -0,0 +1,58 @@ +<div class="section"> + +Hardware modifications {#pagetop} +====================== + +This section relates to hardware maintenance on supported targets. + +[Back to previous index](../). + +- [ThinkPad X60/X60s/X60T: Change keyboard](x60_keyboard.html) (the + procedure on X200/X200S/X200T is almost identical) +- [ThinkPad X60/X60S: change the fan/heatsink](x60_heatsink.html) +- [ThinkPad X60/X60s: How to change the LCD + panel](x60_lcd_change.html) (incomplete. pics only for now) +- [ThinkPad T60 15.1\" changing LCD panel](t60_lcd_15.html) +- [ThinkPad T60: change the fan/heatsink](t60_heatsink.html) +- [ThinkPad X60/X60S: hardware security](x60_security.html) +- [ThinkPad T60: hardware security](t60_security.html) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hardware/t60_heatsink.html b/docs/hardware/t60_heatsink.html deleted file mode 100644 index c3f2286d..00000000 --- a/docs/hardware/t60_heatsink.html +++ /dev/null @@ -1,171 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Changing the heatsink or CPU on a ThinkPad T60</title> -</head> - -<body> - - <div class="section"> - <h1>Changing heatsink (or CPU) on the ThinkPad T60</h1> - <p> - Using this guide you can also change/upgrade the CPU. - </p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - <h1 id="hardware_requirements">Hardware requirements</h1> - <ul> - <li>rubbing alcohol or isopropyl alcohol, and thermal compound for changing CPU heatsink (procedure involves removing heatsink)</li> - <li>thermal compound/paste (Arctic MX-4 is good. Others are also good.)</li> - </ul> - </div> - - <div class="section"> - <h1 id="software_requirements">Software requirements</h1> - <ul> - <li>xsensors</li> - <li>stress</li> - </ul> - </div> - - <div class="section"> - - <h1 id="recovery">Disassembly</h1> - - <p> - Remove those screws and remove the HDD:<br/> - <img src="../images/t60_dev/0001.JPG" alt="" /> <img src="../images/t60_dev/0002.JPG" alt="" /> - </p> - - <p> - Lift off the palm rest:<br/> - <img src="../images/t60_dev/0003.JPG" alt="" /> - </p> - - <p> - Lift up the keyboard, pull it back a bit, flip it over like that and then disconnect it from the board:<br/> - <img src="../images/t60_dev/0004.JPG" alt="" /> <img src="../images/t60_dev/0005.JPG" alt="" /> <img src="../images/t60_dev/0006.JPG" alt="" /> - </p> - - <p> - Gently wedge both sides loose:<br/> - <img src="../images/t60_dev/0007.JPG" alt="" /> <img src="../images/t60_dev/0008.JPG" alt="" /> - </p> - - <p> - Remove that cable from the position:<br/> - <img src="../images/t60_dev/0009.JPG" alt="" /> <img src="../images/t60_dev/0010.JPG" alt="" /> - </p> - - <p> - Remove the bezel (sorry forgot to take pics). - </p> - - <p> - 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<br/> - <img src="../images/t60_dev/0051.JPG" alt="" /> - </p> - - <p> - This is also an opportunity to change the CPU to another one. For example if you had a Core Duo T2400, you can upgrade it to a better processor - (higher speed, 64-bit support). A Core 2 Duo T7600 was installed here. - </p> - - <p> - Attach the heatsink and install the screws (also, make sure to install the AC jack as highlighted):<br/> - <img src="../images/t60_dev/0052.JPG" alt="" /> - </p> - - <p> - Reinstall that upper bezel:<br/> - <img src="../images/t60_dev/0053.JPG" alt="" /> - </p> - - <p> - Do that:<br/> - <img src="../images/t60_dev/0054.JPG" alt="" /> <img src="../images/t60_dev/0055.JPG" alt="" /> - </p> - - <p> - Attach keyboard:<br/> - <img src="../images/t60_dev/0056.JPG" alt="" /> - </p> - - <p> - Place keyboard and (sorry, forgot to take pics) reinstall the palmrest and insert screws on the underside:<br/> - <img src="../images/t60_dev/0058.JPG" alt="" /> - </p> - - <p> - It lives!<br/> - <img src="../images/t60_dev/0071.JPG" alt="" /> <img src="../images/t60_dev/0072.JPG" alt="" /> <img src="../images/t60_dev/0073.JPG" alt="" /> - </p> - - <p> - Always stress test ('stress -c 2' and xsensors. below 90C is ok) when replacing cpu paste/heatsink:<br/> - <img src="../images/t60_dev/0074.JPG" alt="" /> - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hardware/t60_heatsink.md b/docs/hardware/t60_heatsink.md new file mode 100644 index 00000000..4828d68d --- /dev/null +++ b/docs/hardware/t60_heatsink.md @@ -0,0 +1,131 @@ +<div class="section"> + +Changing heatsink (or CPU) on the ThinkPad T60 +============================================== + +Using this guide you can also change/upgrade the CPU. + +[Back to previous index](./) + +</div> + +<div class="section"> + +Hardware requirements {#hardware_requirements} +===================== + +- rubbing alcohol or isopropyl alcohol, and thermal compound for + changing CPU heatsink (procedure involves removing heatsink) +- thermal compound/paste (Arctic MX-4 is good. Others are also good.) + +</div> + +<div class="section"> + +Software requirements {#software_requirements} +===================== + +- xsensors +- stress + +</div> + +<div class="section"> + +Disassembly {#recovery} +=========== + +Remove those screws and remove the HDD:\ +  + +Lift off the palm rest:\ + + +Lift up the keyboard, pull it back a bit, flip it over like that and +then disconnect it from the board:\ +  + + +Gently wedge both sides loose:\ +  + +Remove that cable from the position:\ +  + +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\ + + +This is also an opportunity to change the CPU to another one. For +example if you had a Core Duo T2400, you can upgrade it to a better +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):\ + + +Reinstall that upper bezel:\ + + +Do that:\ +  + +Attach keyboard:\ + + +Place keyboard and (sorry, forgot to take pics) reinstall the palmrest +and insert screws on the underside:\ + + +It lives!\ +  + + +Always stress test (\'stress -c 2\' and xsensors. below 90C is ok) when +replacing cpu paste/heatsink:\ + + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hardware/t60_lcd_15.html b/docs/hardware/t60_lcd_15.html deleted file mode 100644 index c74bb8f3..00000000 --- a/docs/hardware/t60_lcd_15.html +++ /dev/null @@ -1,128 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Changing LCD panel on 15.1 inch T60</title> -</head> - -<body> - - <div class="section"> - <h1>Changing the LCD panel on a 15.1" T60</h1> - <p> - 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 the procedure is a bit more involved than on 15.1". - </p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - - <h1 id="recovery">Disassembly</h1> - - <p> - Remove those covers and unscrew:<br/> - <img src="../images/t60_dev/0059.JPG" alt="" /> <img src="../images/t60_dev/0060.JPG" alt="" /> <img src="../images/t60_dev/0061.JPG" alt="" /> - </p> - - <p> - Gently pry off the front bezel. - </p> - - <p> - Remove inverter board:<br/> - <img src="../images/t60_dev/0064.JPG" alt="" /> - </p> - - <p> - Disconnect LCD cable:<br/> - <img src="../images/t60_dev/0065.JPG" alt="" /> - </p> - - <p> - Remove the panel:<br/> - <img src="../images/t60_dev/0066.JPG" alt="" /> - </p> - - <p> - Move the rails (left and right side) from the old panel to the new one and then attach LCD cable:<br/> - <img src="../images/t60_dev/0068.JPG" alt="" /> - </p> - - <p> - Insert panel (this one is an LG-Philips LP150E05-A2K1, and there are others. See <a href="../hcl/#supported_t60_list">../hcl/#supported_t60_list</a>):<br/> - <img src="../images/t60_dev/0069.JPG" alt="" /> - </p> - - <p> - Insert new inverter board (see <a href="../hcl/#supported_t60_list">../hcl/#supported_t60_list</a> for what is recommended on your LCD panel):<br/> - <img src="../images/t60_dev/0070.JPG" alt="" /> - </p> - - <p> - Now re-attach the front bezel and put all the screws in. - </p> - - <p> - It lives!<br/> - <img src="../images/t60_dev/0071.JPG" alt="" /> <img src="../images/t60_dev/0072.JPG" alt="" /> <img src="../images/t60_dev/0073.JPG" alt="" /> - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hardware/t60_lcd_15.md b/docs/hardware/t60_lcd_15.md new file mode 100644 index 00000000..49b35135 --- /dev/null +++ b/docs/hardware/t60_lcd_15.md @@ -0,0 +1,92 @@ +<div class="section"> + +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 +the procedure is a bit more involved than on 15.1\". + +[Back to previous index](./) + +</div> + +<div class="section"> + +Disassembly {#recovery} +=========== + +Remove those covers and unscrew:\ +  + + +Gently pry off the front bezel. + +Remove inverter board:\ + + +Disconnect LCD cable:\ + + +Remove the panel:\ + + +Move the rails (left and right side) from the old panel to the new one +and then attach LCD cable:\ + + +Insert panel (this one is an LG-Philips LP150E05-A2K1, and there are +others. See +[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list)):\ + + +Insert new inverter board (see +[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list) for what is +recommended on your LCD panel):\ + + +Now re-attach the front bezel and put all the screws in. + +It lives!\ +  + + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hardware/t60_security.html b/docs/hardware/t60_security.html deleted file mode 100644 index 5e0c4bdd..00000000 --- a/docs/hardware/t60_security.html +++ /dev/null @@ -1,484 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Libreboot documentation: Security on the ThinkPad T60</title> -</head> - -<body> - - <div class="section"> - <h1>Security on the ThinkPad T60</h1> - <p>Hardware modifications to enhance security on the ThinkPad T60. This tutorial is <b>incomplete</b> at the time of writing.</p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - <h1>Table of Contents</h1> - <ul> - <li><a href="#hardware_requirements">Hardware Requirements</a></li> - <li><a href="#software_requirements">Software Requirements</a></li> - <li><a href="#procedure">The procedure</a></li> - </ul> - <h1 id="hardware_requirements">Hardware requirements</h1> - <ul> - <li>A T60</li> - <li>screwdriver</li> - <li>Rubbing or isopropyl alcohol, and thermal compound.</li> - <li>(in a later version of this tutorial: soldering iron and scalpel)</li> - </ul> - <h1 id="software_requirements">Software requirements</h1> - <ul> - <li>none (at least in the scope of the article as-is)</li> - <li>You probably want to encrypt your GNU+Linux install using LUKS</li> - </ul> - </div> - - <div class="section"> - <h1> - Rationale - </h1> - <p> - Most people think of security on the software side: the hardware is important aswell. - </p> - <p> - This tutorial deals with reducing the number of devices that have direct 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. - </p> - </div> - - <div class="section"> - - <h1 id="procedure">Disassembly</h1> - - <p> - Remove those screws and remove the HDD:<br/> - <img src="../images/t60_dev/0001.JPG" alt="" /> <img src="../images/t60_dev/0002.JPG" alt="" /> - </p> - - <p> - Lift off the palm rest:<br/> - <img src="../images/t60_dev/0003.JPG" alt="" /> - </p> - - <p> - Lift up the keyboard, pull it back a bit, flip it over like that and then disconnect it from the board:<br/> - <img src="../images/t60_dev/0004.JPG" alt="" /> <img src="../images/t60_dev/0005.JPG" alt="" /> <img src="../images/t60_dev/0006.JPG" alt="" /> - </p> - - <p> - Gently wedge both sides loose:<br/> - <img src="../images/t60_dev/0007.JPG" alt="" /> <img src="../images/t60_dev/0008.JPG" alt="" /> - </p> - - <p> - Remove that cable from the position:<br/> - <img src="../images/t60_dev/0009.JPG" alt="" /> <img src="../images/t60_dev/0010.JPG" alt="" /> - </p> - - <p> - Now remove that bezel. Remove wifi, nvram battery and speaker connector (also remove 56k modem, on the left of wifi):<br/> - <img src="../images/t60_dev/0011.JPG" alt="" /><br/> - Reason: has direct (and very fast) memory access, and could (theoretically) leak data over a side-channel.<br/> - <b>Wifi:</b> 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 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. - </p> - - <p> - Remove those screws:<br/> - <img src="../images/t60_dev/0012.JPG" alt="" /> - </p> - - <p> - Disconnect the power jack:<br/> - <img src="../images/t60_dev/0013.JPG" alt="" /> - </p> - - <p> - Remove nvram battery (we will put it back later):<br/> - <img src="../images/t60_dev/0014.JPG" alt="" /> - </p> - - <p> - Disconnect cable (for 56k modem) and disconnect the other cable:<br/> - <img src="../images/t60_dev/0015.JPG" alt="" /> <img src="../images/t60_dev/0016.JPG" alt="" /> - </p> - - <p> - Disconnect speaker cable:<br/> - <img src="../images/t60_dev/0017.JPG" alt="" /> - </p> - - <p> - Disconnect the other end of the 56k modem cable:<br/> - <img src="../images/t60_dev/0018.JPG" alt="" /> - </p> - - <p> - Make sure you removed it:<br/> - <img src="../images/t60_dev/0019.JPG" alt="" /> - </p> - - <p> - Unscrew those:<br/> - <img src="../images/t60_dev/0020.JPG" alt="" /> - </p> - - <p> - Make sure you removed those:<br/> - <img src="../images/t60_dev/0021.JPG" alt="" /> - </p> - - <p> - Disconnect LCD cable from board:<br/> - <img src="../images/t60_dev/0022.JPG" alt="" /> - </p> - - <p> - Remove those screws then remove the LCD assembly:<br/> - <img src="../images/t60_dev/0023.JPG" alt="" /> <img src="../images/t60_dev/0024.JPG" alt="" /> <img src="../images/t60_dev/0025.JPG" alt="" /> - </p> - - <p> - Once again, make sure you removed those:<br/> - <img src="../images/t60_dev/0026.JPG" alt="" /> - </p> - - <p> - Remove the shielding containing the motherboard, then flip it over. 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:<br/> - <img src="../images/t60_dev/0027.JPG" alt="" /> <img src="../images/t60_dev/0028.JPG" alt="" /> <img src="../images/t60_dev/0029.JPG" alt="" /> - <img src="../images/t60_dev/0031.JPG" alt="" /> <img src="../images/t60_dev/0032.JPG" alt="" /> <img src="../images/t60_dev/0033.JPG" alt="" /> - </p> - - <p> - Remove microphone (soldering iron not needed. Just wedge it out gently):<br/> - <img src="../images/t60_dev/0039.JPG" alt="" /><br/> - <b>Rationale:</b><br/> - Another reason to remove the microphone: If your computer gets<a href="#ref1">[1]</a> compromised, it can - record what you say, and use it to receive data from nearby devices if - they're compromised too. Also, we do not know what the built-in microcode (in the CPU) is doing; it could theoretically - be programmed to accept remote commands from some speaker somewhere (remote security hole). <b>In other words, - the system could already be compromised from the factory.</b> - </p> - - <p> - Remove infrared:<br/> - <img src="../images/t60_dev/0040.JPG" alt="" /> <img src="../images/t60_dev/0042.JPG" alt="" /> - </p> - - <p> - Remove cardbus (it's in a socket, no need to disable. Just remove the port itself):<br/> - <img src="../images/t60_dev/0041.JPG" alt="" /><br/> - <b>Rationale:</b><br/> - 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. - </p> - - <p> - Before re-installing the upper chassis, remove the speaker:<br/> - <img src="../images/t60_dev/0043.JPG" alt="" /> <img src="../images/t60_dev/0044.JPG" alt="" /><br/> - Reason: combined with the microphone issue, this could be used to leak data.<br/> - If your computer gets<a href="#ref1">[1]</a> compromised, it can be used to - transmit data to nearby compromised devices. It's unknown if it can be - turned into a microphone<a href="#ref2">[2]</a>.<br/> - Replacement: headphones/speakers (line-out) or external DAC (USB). - </p> - - <p> - Remove the wwan:<br/> - <img src="../images/t60_dev/0045.JPG" alt="" /><br/> - <b>Wwan (3g modem):</b> They run proprietary software! It's like AMT but over the GSM network which is - probably even worse.<br/> - Replacement: external USB wifi dongle. (or USB wwan/3g dongle; note, this has all the same privacy issues as mobile phones. wwan not recommended). - </p> - - <p> - 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?)<br/> - <img src="../images/t60_dev/0046.JPG" alt="" /> - </p> - - <p> - Put those screws back:<br/> - <img src="../images/t60_dev/0047.JPG" alt="" /> - </p> - - <p> - Put it back into lower chassis:<br/> - <img src="../images/t60_dev/0048.JPG" alt="" /> - </p> - - <p> - Attach LCD and insert screws (also, attach the lcd cable to the board):<br/> - <img src="../images/t60_dev/0049.JPG" alt="" /> - </p> - - <p> - Insert those screws:<br/> - <img src="../images/t60_dev/0050.JPG" alt="" /> - </p> - - <p> - 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<br/> - <img src="../images/t60_dev/0051.JPG" alt="" /> - </p> - - <p> - Attach the heatsink and install the screws (also, make sure to install the AC jack as highlighted):<br/> - <img src="../images/t60_dev/0052.JPG" alt="" /> - </p> - - <p> - Reinstall that upper bezel:<br/> - <img src="../images/t60_dev/0053.JPG" alt="" /> - </p> - - <p> - Do that:<br/> - <img src="../images/t60_dev/0054.JPG" alt="" /> <img src="../images/t60_dev/0055.JPG" alt="" /> - </p> - - <p> - Attach keyboard and install nvram battery:<br/> - <img src="../images/t60_dev/0056.JPG" alt="" /> <img src="../images/t60_dev/0057.JPG" alt="" /> - </p> - - <p> - Place keyboard and (sorry, forgot to take pics) reinstall the palmrest and insert screws on the underside:<br/> - <img src="../images/t60_dev/0058.JPG" alt="" /> - </p> - - <p> - Remove those covers and unscrew:<br/> - <img src="../images/t60_dev/0059.JPG" alt="" /> <img src="../images/t60_dev/0060.JPG" alt="" /> <img src="../images/t60_dev/0061.JPG" alt="" /> - </p> - - <p> - Gently pry off the front bezel (sorry, forgot to take pics). - </p> - - <p> - Remove bluetooth module:<br/> - <img src="../images/t60_dev/0062.JPG" alt="" /> <img src="../images/t60_dev/0063.JPG" alt="" /> - </p> - - <p> - Re-attach the front bezel and re-insert the screws (sorry, forgot to take pics). - </p> - - <p> - It lives!<br/> - <img src="../images/t60_dev/0071.JPG" alt="" /> <img src="../images/t60_dev/0072.JPG" alt="" /> <img src="../images/t60_dev/0073.JPG" alt="" /> - </p> - - <p> - Always stress test ('stress -c 2' and xsensors. below 90C is ok) when replacing cpu paste/heatsink:<br/> - <img src="../images/t60_dev/0074.JPG" alt="" /> - </p> - - </div> - - <div class="section"> - <h2> - Not covered yet: - </h2> - <ul> - <li>Disable flashing the ethernet firmware</li> - <li>Disable SPI flash writes (can be re-enabled by unsoldering two parts)</li> - <li>Disable use of xrandr/edid on external monitor (cut 2 pins on VGA)</li> - <li>Disable docking station (might be possible to do it in software, in coreboot upstream as a Kconfig option)</li> - </ul> - <p> - Go to <a href="http://media.ccc.de/browse/congress/2013/30C3_-_5529_-_en_-_saal_2_-_201312271830_-_hardening_hardware_and_choosing_a_goodbios_-_peter_stuge.html">http://media.ccc.de/browse/congress/2013/30C3_-_5529_-_en_-_saal_2_-_201312271830_-_hardening_hardware_and_choosing_a_goodbios_-_peter_stuge.html</a> - or directly to the video: <a href="http://mirror.netcologne.de/CCC/congress/2013/webm/30c3-5529-en-Hardening_hardware_and_choosing_a_goodBIOS_webm.webm">http://mirror.netcologne.de/CCC/congress/2013/webm/30c3-5529-en-Hardening_hardware_and_choosing_a_goodBIOS_webm.webm</a>. - </p> - <p> - 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. - </p> - </div> - - <div class="section"> - <h2> - Also not covered yet: - </h2> - <ul> - <li> - Intrusion detection: randomized seal on screws<br/> - 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 on the laptop. - </li> - <li> - Tips about preventing/mitigating risk of cold boot attack. - <ul> - <li>soldered RAM?</li> - <li>wipe all RAM at boot/power-off/power-on? (patch in coreboot upstream?)</li> - <li>ask gnutoo about fallback patches (counts number of boots)</li> - </ul> - </li> - <li> - General tips/advice and web links showing how to detect physical intrusions. - </li> - <li> - For example: <a href="http://cs.tau.ac.il/~tromer/acoustic/">http://cs.tau.ac.il/~tromer/acoustic/</a> - or <a href="http://cyber.bgu.ac.il/content/how-leak-sensitive-data-isolated-computer-air-gap-near-mobile-phone-airhopper">http://cyber.bgu.ac.il/content/how-leak-sensitive-data-isolated-computer-air-gap-near-mobile-phone-airhopper</a>. - </li> - <li> - <a href="https://en.wikipedia.org/wiki/Tempest_%28codename%29">https://en.wikipedia.org/wiki/Tempest_%28codename%29</a> - </li> - <li> - https://gitorious.org/gnutoo-for-coreboot/grub-assemble/source/a61f636797777a742f65f4c9c58032aa6a9b23c3: - </li> - </ul> - </div> - - <div class="section"> - <h1> - Extra notes - </h1> - <p> - EC: Cannot be removed but can be mitigated: it contains non-free - non-loadable code, but it has no access to the computer's RAM. - It has access to the on-switch of the wifi, bluetooth, modem and some - other power management features. The issue is that it has access to the - keyboard, however if the software security howto <b>(not yet written)</b> is followed correctly, - it won't be able to leak data to a local attacker. It has no network - access but it may still be able to leak data remotely, but that - requires someone to be nearby to recover the data with the help of an - SDR and some directional antennas<a href="#ref3">[3]</a>. - </p> - <p> - <a href="http://www.coreboot.org/Intel_82573_Ethernet_controller">Intel 82573 Ethernet controller</a> - on the X60 seems safe, according to Denis. - </p> - - <div class="subsection"> - <h2> - Risk level - </h2> - <ul> - <li>Modem (3g/wwan): highest</li> - <li>Intel wifi: Near highest</li> - <li>Atheros PCI wifi: unknown, but lower than intel wifi.</li> - <li>Microphone: only problematic if the computer gets compromised.</li> - <li>Speakers: only problematic if the computer gets compromised.</li> - <li>EC: can be mitigated if following the guide on software security.</li> - </ul> - </div> - </div> - - <div class="section"> - <h1> - Further reading material (software security) - </h1> - <ul> - <li><a href="../gnulinux/encrypted_debian.html">Installing Debian or Devuan GNU+Linux with full disk encryption (including /boot)</a></li> - <li><a href="../gnulinux/encrypted_parabola.html">Installing Parabola GNU+Linux with full disk encryption (including /boot)</a></li> - <li><a href="dock.html">Notes about DMA access and the docking station</a></li> - </ul> - </div> - - <div class="section"> - <h1> - References - </h1> - <div class="subsection"> - <h2 id="ref1">[1] physical access</h2> - <p> - Explain that black hats, TAO, and so on might use a 0day to get in, - and explain that in this case it mitigates what the attacker can do. - Also the TAO do some evaluation before launching an attack: they take - the probability of beeing caught into account, along with the kind of - target. A 0day costs a lot of money, I heard that it was from 100000$ - 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. - </p> - </div> - <div class="subsection"> - <h2 id="ref2">[2] microphone</h2> - <p> - It's possible to turn headphones into a microphone, you could try - yourself, however they don't record loud at all. Also intel cards have - the capability to change a connector's function, for instance the - 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. - </p> - </div> - <div class="subsection"> - <h2 id="ref3">[3] Video (CCC)</h2> - <p> - 30c3-5356-en-Firmware_Fat_Camp_webm.webm from the 30th CCC. While - their demo is experimental(their hardware also got damaged during the - transport), the spies probably already have that since a long time. - <a href="http://berlin.ftp.media.ccc.de/congress/2013/webm/30c3-5356-en-Firmware_Fat_Camp_webm.webm">http://berlin.ftp.media.ccc.de/congress/2013/webm/30c3-5356-en-Firmware_Fat_Camp_webm.webm</a> - </p> - </div> - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hardware/t60_security.md b/docs/hardware/t60_security.md new file mode 100644 index 00000000..667c906a --- /dev/null +++ b/docs/hardware/t60_security.md @@ -0,0 +1,416 @@ +<div class="section"> + +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](./) + +</div> + +<div class="section"> + +Table of Contents +================= + +- [Hardware Requirements](#hardware_requirements) +- [Software Requirements](#software_requirements) +- [The procedure](#procedure) + +Hardware requirements {#hardware_requirements} +===================== + +- A T60 +- screwdriver +- Rubbing or isopropyl alcohol, and thermal compound. +- (in a later version of this tutorial: soldering iron and scalpel) + +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 + +</div> + +<div class="section"> + +Rationale +========= + +Most people think of security on the software side: the hardware is +important aswell. + +This tutorial deals with reducing the number of devices that have direct +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. + +</div> + +<div class="section"> + +Disassembly {#procedure} +=========== + +Remove those screws and remove the HDD:\ +  + +Lift off the palm rest:\ + + +Lift up the keyboard, pull it back a bit, flip it over like that and +then disconnect it from the board:\ +  + + +Gently wedge both sides loose:\ +  + +Remove that cable from the position:\ +  + +Now remove that bezel. Remove wifi, nvram battery and speaker connector +(also remove 56k modem, on the left of wifi):\ +\ +Reason: has direct (and very fast) memory access, and could +(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 +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:\ + + +Disconnect the power jack:\ + + +Remove nvram battery (we will put it back later):\ + + +Disconnect cable (for 56k modem) and disconnect the other cable:\ +  + +Disconnect speaker cable:\ + + +Disconnect the other end of the 56k modem cable:\ + + +Make sure you removed it:\ + + +Unscrew those:\ + + +Make sure you removed those:\ + + +Disconnect LCD cable from board:\ + + +Remove those screws then remove the LCD assembly:\ +  + + +Once again, make sure you removed those:\ + + +Remove the shielding containing the motherboard, then flip it over. +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:\ +  +  +  + +Remove microphone (soldering iron not needed. Just wedge it out +gently):\ +\ +**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, +we do not know what the built-in microcode (in the CPU) is doing; it +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 cardbus (it\'s in a socket, no need to disable. Just remove the +port itself):\ +\ +**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:\ + \ +Reason: combined with the microphone issue, this could be used to leak +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).\ +Replacement: headphones/speakers (line-out) or external DAC (USB). + +Remove the wwan:\ +\ +**Wwan (3g modem):** They run proprietary software! It\'s like AMT but +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?)\ + + +Put those screws back:\ + + +Put it back into lower chassis:\ + + +Attach LCD and insert screws (also, attach the lcd cable to the board):\ + + +Insert those screws:\ + + +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\ + + +Attach the heatsink and install the screws (also, make sure to install +the AC jack as highlighted):\ + + +Reinstall that upper bezel:\ + + +Do that:\ +  + +Attach keyboard and install nvram battery:\ +  + +Place keyboard and (sorry, forgot to take pics) reinstall the palmrest +and insert screws on the underside:\ + + +Remove those covers and unscrew:\ +  + + +Gently pry off the front bezel (sorry, forgot to take pics). + +Remove bluetooth module:\ +  + +Re-attach the front bezel and re-insert the screws (sorry, forgot to +take pics). + +It lives!\ +  + + +Always stress test (\'stress -c 2\' and xsensors. below 90C is ok) when +replacing cpu paste/heatsink:\ + + +</div> + +<div class="section"> + +Not covered yet: +---------------- + +- Disable flashing the ethernet firmware +- Disable SPI flash writes (can be re-enabled by unsoldering two + parts) +- Disable use of xrandr/edid on external monitor (cut 2 pins on VGA) +- Disable docking station (might be possible to do it in software, in + coreboot upstream as a Kconfig option) + +Go to +<http://media.ccc.de/browse/congress/2013/30C3_-_5529_-_en_-_saal_2_-_201312271830_-_hardening_hardware_and_choosing_a_goodbios_-_peter_stuge.html> +or directly to the video: +<http://mirror.netcologne.de/CCC/congress/2013/webm/30c3-5529-en-Hardening_hardware_and_choosing_a_goodBIOS_webm.webm>. + +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. + +</div> + +<div class="section"> + +Also not covered yet: +--------------------- + +- 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 + on the laptop. +- Tips about preventing/mitigating risk of cold boot attack. + - soldered RAM? + - wipe all RAM at boot/power-off/power-on? (patch in coreboot + upstream?) + - ask gnutoo about fallback patches (counts number of boots) +- General tips/advice and web links showing how to detect physical + intrusions. +- For example: <http://cs.tau.ac.il/~tromer/acoustic/> or + <http://cyber.bgu.ac.il/content/how-leak-sensitive-data-isolated-computer-air-gap-near-mobile-phone-airhopper>. +- <https://en.wikipedia.org/wiki/Tempest_%28codename%29> +- https://gitorious.org/gnutoo-for-coreboot/grub-assemble/source/a61f636797777a742f65f4c9c58032aa6a9b23c3: + +</div> + +<div class="section"> + +Extra notes +=========== + +EC: Cannot be removed but can be mitigated: it contains non-free +non-loadable code, but it has no access to the computer\'s RAM. It has +access to the on-switch of the wifi, bluetooth, modem and some other +power management features. The issue is that it has access to the +keyboard, however if the software security howto **(not yet written)** +is followed correctly, it won\'t be able to leak data to a local +attacker. It has no network access but it may still be able to leak data +remotely, but that requires someone to be nearby to recover the data +with the help of an SDR and some directional antennas[\[3\]](#ref3). + +[Intel 82573 Ethernet +controller](http://www.coreboot.org/Intel_82573_Ethernet_controller) on +the X60 seems safe, according to Denis. + +<div class="subsection"> + +Risk level +---------- + +- Modem (3g/wwan): highest +- Intel wifi: Near highest +- Atheros PCI wifi: unknown, but lower than intel wifi. +- Microphone: only problematic if the computer gets compromised. +- Speakers: only problematic if the computer gets compromised. +- EC: can be mitigated if following the guide on software security. + +</div> + +</div> + +<div class="section"> + +Further reading material (software security) +============================================ + +- [Installing Debian or Devuan GNU+Linux with full disk encryption + (including /boot)](../gnulinux/encrypted_debian.html) +- [Installing Parabola GNU+Linux with full disk encryption (including + /boot)](../gnulinux/encrypted_parabola.html) +- [Notes about DMA access and the docking station](dock.html) + +</div> + +<div class="section"> + +References +========== + +<div class="subsection"> + +\[1\] physical access {#ref1} +--------------------- + +Explain that black hats, TAO, and so on might use a 0day to get in, and +explain that in this case it mitigates what the attacker can do. Also +the TAO do some evaluation before launching an attack: they take the +probability of beeing caught into account, along with the kind of +target. A 0day costs a lot of money, I heard that it was from 100000\$ +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. + +</div> + +<div class="subsection"> + +\[2\] microphone {#ref2} +---------------- + +It\'s possible to turn headphones into a microphone, you could try +yourself, however they don\'t record loud at all. Also intel cards have +the capability to change a connector\'s function, for instance the +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. + +</div> + +<div class="subsection"> + +\[3\] Video (CCC) {#ref3} +----------------- + +30c3-5356-en-Firmware\_Fat\_Camp\_webm.webm from the 30th CCC. While +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> + +</div> + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hardware/x60_heatsink.html b/docs/hardware/x60_heatsink.html deleted file mode 100644 index a5e3f847..00000000 --- a/docs/hardware/x60_heatsink.html +++ /dev/null @@ -1,187 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Libreboot documentation: Switch heatsink on ThinkPad X60</title> -</head> - -<body> - - <div class="section"> - <h1>Changing the fan/heatsink on the ThinkPad X60</h1> - <p> - This guide will teach you how to replace the fan and heatsink on your ThinkPad X60. - </p> - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - <h1>Table of Contents</h1> - <ul> - <li><a href="#hardware_requirements">Hardware Requirements</a></li> - <li><a href="#software_requirements">Software Requirements</a></li> - <li><a href="#procedure">Disassembly</a></li> - </ul> - </div> - - <div class="section"> - <h1 id="hardware_requirements">Hardware requirements</h1> - <ul> - <li>isopropyl alcohol (sometimes called rubbing alcohol)</li> - <li>your new fan and/or heatsink</li> - <li>CPU thermal compound (some say Arctic MX-4 is good, others are also 'ok')</li> - <li>Something to spread the paste with</li> - </ul> - </div> - - <div class="section"> - <h1 id="software_requirements">Software requirements (for CPU stress testing)</h1> - <ul> - <li>xsensors utility</li> - <li>stress utility</li> - </ul> - </div> - - <div class="section"> - <h1 id="procedure">Disassembly</h1> - <p> - Remove those screws:<br/> - <img src="../images/x60_heatsink/0000.jpg" alt="" /> - </p> - <p> - Push the keyboard forward (carefully):<br/> - <img src="../images/x60_heatsink/0001.jpg" alt="" /> - </p> - <p> - Lift the keyboard up and disconnect it from the board:<br/> - <img src="../images/x60_heatsink/0002.jpg" alt="" /> - </p> - <p> - Grab the right-hand side of the chassis and force it off (gently) and pry up the rest of the chassis:<br/> - <img src="../images/x60_heatsink/0003.jpg" alt="" /> - </p> - <p> - You should now have this:<br/> - <img src="../images/x60_heatsink/0004.jpg" alt="" /> - </p> - <p> - Disconnect the wifi antenna cables, the modem cable and the speaker:<br/> - <img src="../images/x60_heatsink/0005.jpg" alt="" /> - </p> - <p> - 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:<br/> - <img src="../images/x60_heatsink/0006.jpg" alt="" /> - </p> - <p> - Disconnect the monitor from the motherboard, and unroute the grey antenna cable, carefully lifting the tape - that holds it into place:<br/> - <img src="../images/x60_heatsink/0008.jpg" alt="" /> - </p> - <p> - Carefully lift the remaining tape and unroute the left antenna cable so that it is loose:<br/> - <img src="../images/x60_heatsink/0009.jpg" alt="" /> - </p> - <p> - Remove those screws:<br/> - <img src="../images/x60_heatsink/0011.jpg" alt="" /> - </p> - <p> - Remove those screws:<br/> - <img src="../images/x60_heatsink/0012.jpg" alt="" /> - </p> - <p> - Carefully remove the plate, like so:<br/> - <img src="../images/x60_heatsink/0013.jpg" alt="" /> - </p> - <p> - Remove the SATA connector:<br/> - <img src="../images/x60_heatsink/0014.jpg" alt="" /> - </p> - <p> - Now remove the motherboard (gently) and cast the lcd/chassis aside:<br/> - <img src="../images/x60_heatsink/0015.jpg" alt="" /> - </p> - <p> - Look at that black tape above the heatsink, remove it:<br/> - <img src="../images/x60_heatsink/0016.jpg" alt="" /> - </p> - <p> - Now you have removed it:<br/> - <img src="../images/x60_heatsink/0017.jpg" alt="" /> - </p> - - <p> - Disconnect the fan and remove all the screws, heatsink will easily come off:<br/> - <img src="../images/x60_heatsink/0018.jpg" alt="" /> - </p> - - <p> - Remove the old paste with a cloth (from the CPU and heatsink) and then clean both of them with the alcohol (to remove remaining residue of the paste). - Apply a pea-sized amount of paste to the both chipsets that the heatsink covered and spread it evenly (uniformally). - Finally reinstall the heatsink, reversing previous steps. - </p> - - <p> - <b>stress -c 2</b> command can be used to push the CPU to 100%, and <b>xsensors</b> (or <b>watch sensors</b> command) can be used to monitor heat. - Below 90C is ok. - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hardware/x60_heatsink.md b/docs/hardware/x60_heatsink.md new file mode 100644 index 00000000..366c36c9 --- /dev/null +++ b/docs/hardware/x60_heatsink.md @@ -0,0 +1,158 @@ +<div class="section"> + +Changing the fan/heatsink on the ThinkPad X60 +============================================= + +This guide will teach you how to replace the fan and heatsink on your +ThinkPad X60. + +[Back to main index](./) + +</div> + +<div class="section"> + +Table of Contents +================= + +- [Hardware Requirements](#hardware_requirements) +- [Software Requirements](#software_requirements) +- [Disassembly](#procedure) + +</div> + +<div class="section"> + +Hardware requirements {#hardware_requirements} +===================== + +- isopropyl alcohol (sometimes called rubbing alcohol) +- your new fan and/or heatsink +- CPU thermal compound (some say Arctic MX-4 is good, others are also + \'ok\') +- Something to spread the paste with + +</div> + +<div class="section"> + +Software requirements (for CPU stress testing) {#software_requirements} +============================================== + +- xsensors utility +- stress utility + +</div> + +<div class="section"> + +Disassembly {#procedure} +=========== + +Remove those screws:\ + + +Push the keyboard forward (carefully):\ + + +Lift the keyboard up and disconnect it from the board:\ + + +Grab the right-hand side of the chassis and force it off (gently) and +pry up the rest of the chassis:\ + + +You should now have this:\ + + +Disconnect the wifi antenna cables, the modem cable and the speaker:\ + + +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:\ + + +Disconnect the monitor from the motherboard, and unroute the grey +antenna cable, carefully lifting the tape that holds it into place:\ + + +Carefully lift the remaining tape and unroute the left antenna cable so +that it is loose:\ + + +Remove those screws:\ + + +Remove those screws:\ + + +Carefully remove the plate, like so:\ + + +Remove the SATA connector:\ + + +Now remove the motherboard (gently) and cast the lcd/chassis aside:\ + + +Look at that black tape above the heatsink, remove it:\ + + +Now you have removed it:\ + + +Disconnect the fan and remove all the screws, heatsink will easily come +off:\ + + +Remove the old paste with a cloth (from the CPU and heatsink) and then +clean both of them with the alcohol (to remove remaining residue of the +paste). Apply a pea-sized amount of paste to the both chipsets that the +heatsink covered and spread it evenly (uniformally). Finally reinstall +the heatsink, reversing previous steps. + +**stress -c 2** command can be used to push the CPU to 100%, and +**xsensors** (or **watch sensors** command) can be used to monitor heat. +Below 90C is ok. + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hardware/x60_keyboard.html b/docs/hardware/x60_keyboard.html deleted file mode 100644 index 0f0ea92d..00000000 --- a/docs/hardware/x60_keyboard.html +++ /dev/null @@ -1,91 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad X60: Change keyboard</title> -</head> - -<body> - - <div class="section"> - <h1>Thinkpad X60/X60s/X60t: Change keyboard</h1> - <p> - Use this guide to replace the keyboard on your ThinkPad X60. Also works for X60s and X60 Tablet. - </p> - <p> - Although slightly different, this guide can also be followed for the ThinkPad X200, X200S and X200 Tablet. - The screws are in more or less the same place, and it's the same procedure. - </p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - - <h1 id="recovery">Just follow these steps, and then reverse</h1> - - <p> - <img src="../images/x60_keyboard/1.JPG"><br/> - <img src="../images/x60_keyboard/2.JPG"><br/> - <img src="../images/x60_keyboard/3.JPG"><br/> - <img src="../images/x60_keyboard/4.JPG"><br/> - <img src="../images/x60_keyboard/5.JPG"> - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hardware/x60_keyboard.md b/docs/hardware/x60_keyboard.md new file mode 100644 index 00000000..3bc3c159 --- /dev/null +++ b/docs/hardware/x60_keyboard.md @@ -0,0 +1,66 @@ +<div class="section"> + +Thinkpad X60/X60s/X60t: Change keyboard +======================================= + +Use this guide to replace the keyboard on your ThinkPad X60. Also works +for X60s and X60 Tablet. + +Although slightly different, this guide can also be followed for the +ThinkPad X200, X200S and X200 Tablet. The screws are in more or less the +same place, and it\'s the same procedure. + +[Back to previous index](./) + +</div> + +<div class="section"> + +Just follow these steps, and then reverse {#recovery} +========================================= + +\ +\ +\ +\ + + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hardware/x60_lcd_change.html b/docs/hardware/x60_lcd_change.html deleted file mode 100644 index f6d2d3ce..00000000 --- a/docs/hardware/x60_lcd_change.html +++ /dev/null @@ -1,83 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Libreboot documentation: Unbricking the ThinkPad T60</title> -</head> - -<body> - - <div class="section"> - <h1>Changing the LCD panel on X60</h1> - <p>This tutorial is incomplete, and only pictures for now.</p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - <p> - <img src="../images/x60_lcd_change/0001.JPG" alt="" /> - <img src="../images/x60_lcd_change/0002.JPG" alt="" /> - <img src="../images/x60_lcd_change/0003.JPG" alt="" /> - <img src="../images/x60_lcd_change/0004.JPG" alt="" /> - <img src="../images/x60_lcd_change/0005.JPG" alt="" /> - <img src="../images/x60_lcd_change/0006.JPG" alt="" /> - <img src="../images/x60_lcd_change/0007.JPG" alt="" /> - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hardware/x60_lcd_change.md b/docs/hardware/x60_lcd_change.md new file mode 100644 index 00000000..32c5c967 --- /dev/null +++ b/docs/hardware/x60_lcd_change.md @@ -0,0 +1,60 @@ +<div class="section"> + +Changing the LCD panel on X60 +============================= + +This tutorial is incomplete, and only pictures for now. + +[Back to previous index](./) + +</div> + +<div class="section"> + + + + + + + + + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hardware/x60_security.html b/docs/hardware/x60_security.html deleted file mode 100644 index f2bb70af..00000000 --- a/docs/hardware/x60_security.html +++ /dev/null @@ -1,344 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Libreboot documentation: Security on the ThinkPad X60</title> -</head> - -<body> - - <div class="section"> - <h1>Security on the ThinkPad X60</h1> - <p>Hardware modifications to enhance security on the ThinkPad X60. This tutorial is <b>incomplete</b> at the time of writing.</p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - <h1>Table of Contents</h1> - <ul> - <li><a href="#hardware_requirements">Hardware Requirements</a></li> - <li><a href="#software_requirements">Software Requirements</a></li> - <li><a href="#procedure">The procedure</a></li> - </ul> - </div> - - <div class="section"> - - <h1 id="hardware_requirements">Hardware requirements</h1> - <ul> - <li>An X60</li> - <li>screwdriver</li> - <li>(in a later version of this tutorial: soldering iron and scalpel)</li> - </ul> - - <h1 id="software_requirements">Software requirements</h1> - <ul> - <li>none (at least in the scope of the article as-is)</li> - <li>You probably want to encrypt your GNU+Linux install using LUKS</li> - </ul> - - </div> - - <div class="section"> - - <h1> - Rationale - </h1> - <p> - Most people think of security on the software side: the hardware is important aswell. - </p> - <p> - This tutorial deals with reducing the number of devices that have direct 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. - </p> - - <h1 id="procedure">Disassembly</h1> - - <p> - Firstly remove the bluetooth (if your X60 has this):<br/> - The marked screws are underneath those stickers (marked in those 3 locations at the bottom of the LCD assembly):<br/> - <img src="../images/x60_security/0000_bluetooth0.jpg" alt="" /><br/> - Now gently pry off the bottom part of the front bezel, and the bluetooth module is on the left (easily removable):<br/> - <img src="../images/x60_security/0000_bluetooth.jpg" alt="" /><br/> - </p> - - <p> - If your model was WWAN, remove the simcard (check anyway):<br/> - Uncover those 2 screws at the bottom:<br/> - <img src="../images/x60_security/0000_simcard0.jpg" alt="" /><br/> - SIM card (not present in the picture) is in the marked location:<br/> - <img src="../images/x60_security/0000_simcard1.jpg" alt="" /><br/> - Replacement: USB dongle. - </p> - - <p> - Now get into the motherboard. - </p> - - <p> - Remove those screws:<br/> - <img src="../images/x60_security/0000.jpg" alt="" /> - </p> - <p> - Push the keyboard forward (carefully):<br/> - <img src="../images/x60_security/0001.jpg" alt="" /> - </p> - <p> - Lift the keyboard up and disconnect it from the board:<br/> - <img src="../images/x60_security/0002.jpg" alt="" /> - </p> - <p> - Grab the right-hand side of the chassis and force it off (gently) and pry up the rest of the chassis:<br/> - <img src="../images/x60_security/0003.jpg" alt="" /> - </p> - <p> - You should now have this:<br/> - <img src="../images/x60_security/0004.jpg" alt="" /> - </p> - - <p> - The following is a summary of what you will remove (already done to this system):<br/> - <img src="../images/x60_security/0001_overview.jpg" alt="" /><br/> - 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 jack, the modem cable and - also (on another model) a device inside the part where the wwan antenna goes (wasn't sure what it was, but I knew it wasn't needed). <b>This is optional</b> - </p> - - <p> - Remove the microphone (can desolder it, but you can also easily pull it off with you hands). Already removed here:<br/> - <img src="../images/x60_security/0001_microphone.jpg" alt="" /><br/> - <b>Rationale:</b><br/> - Another reason to remove the microphone: If your computer gets<a href="#ref1">[1]</a> compromised, it can - record what you say, and use it to receive data from nearby devices if - they're compromised too. Also, we do not know what the built-in microcode (in the CPU) is doing; it could theoretically - be programmed to accept remote commands from some speaker somewhere (remote security hole). <b>In other words, - the system could already be compromised from the factory.</b> - </p> - - <p> - Remove the modem:<br/> - <img src="../images/x60_security/0001_modem.jpg" alt="" /><br/> - (useless, obsolete device) - </p> - - <p> - Remove the speaker:<br/> - <img src="../images/x60_security/0001_speaker.jpg" alt="" /><br/> - Reason: combined with the microphone issue, this could be used to leak data.<br/> - If your computer gets<a href="#ref1">[1]</a> compromised, it can be used to - transmit data to nearby compromised devices. It's unknown if it can be - turned into a microphone<a href="#ref2">[2]</a>.<br/> - Replacement: headphones/speakers (line-out) or external DAC (USB). - </p> - - <p> - Remove the wlan (also remove wwan if you have it):<br/> - <img src="../images/x60_security/0001_wlan_wwan.jpg" alt="" /><br/> - Reason: has direct (and very fast) memory access, and could (theoretically) leak data over a side-channel.<br/> - <b>Wifi:</b> 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.<br/> - <b>Wwan (3g modem):</b> They run proprietary software! It's like AMT but over the GSM network which is - probably even worse.<br/> - Replacement: external USB wifi dongle. (or USB wwan/3g dongle; note, this has all the same privacy issues as mobile phones. wwan not recommended). - </p> - - <h2> - Not covered yet: - </h2> - <ul> - <li>Disable cardbus (has fast/direct memory access)</li> - <li>Disable firewire (has fast/direct memory access)</li> - <li>Disable flashing the ethernet firmware</li> - <li>Disable SPI flash writes (can be re-enabled by unsoldering two parts)</li> - <li>Disable use of xrandr/edid on external monitor (cut 2 pins on VGA)</li> - <li>Disable docking station (might be possible to do it in software, in coreboot upstream as a Kconfig option)</li> - </ul> - <p> - Go to <a href="http://media.ccc.de/browse/congress/2013/30C3_-_5529_-_en_-_saal_2_-_201312271830_-_hardening_hardware_and_choosing_a_goodbios_-_peter_stuge.html">http://media.ccc.de/browse/congress/2013/30C3_-_5529_-_en_-_saal_2_-_201312271830_-_hardening_hardware_and_choosing_a_goodbios_-_peter_stuge.html</a> - or directly to the video: <a href="http://mirror.netcologne.de/CCC/congress/2013/webm/30c3-5529-en-Hardening_hardware_and_choosing_a_goodBIOS_webm.webm">http://mirror.netcologne.de/CCC/congress/2013/webm/30c3-5529-en-Hardening_hardware_and_choosing_a_goodBIOS_webm.webm</a>. - </p> - <p> - 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. - </p> - - <h2> - Also not covered yet: - </h2> - <ul> - <li> - Intrusion detection: randomized seal on screws<br/> - 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 on the laptop. - </li> - <li> - Tips about preventing/mitigating risk of cold boot attack. - <ul> - <li>soldered RAM?</li> - <li>seal RAM door shut (possibly modified lower chassis) so that system has to be disassembled (which has to go through the nail polish)</li> - <li>wipe all RAM at boot/power-off/power-on? (patch in coreboot upstream?)</li> - <li>ask gnutoo about fallback patches (counts number of boots)</li> - </ul> - </li> - <li> - General tips/advice and web links showing how to detect physical intrusions. - </li> - <li> - For example: <a href="http://cs.tau.ac.il/~tromer/acoustic/">http://cs.tau.ac.il/~tromer/acoustic/</a> - or <a href="http://cyber.bgu.ac.il/content/how-leak-sensitive-data-isolated-computer-air-gap-near-mobile-phone-airhopper">http://cyber.bgu.ac.il/content/how-leak-sensitive-data-isolated-computer-air-gap-near-mobile-phone-airhopper</a>. - </li> - <li> - <a href="https://en.wikipedia.org/wiki/Tempest_%28codename%29">https://en.wikipedia.org/wiki/Tempest_%28codename%29</a> - </li> - <li> - https://gitorious.org/gnutoo-for-coreboot/grub-assemble/source/a61f636797777a742f65f4c9c58032aa6a9b23c3: - </li> - </ul> - - </div> - - <div class="section"> - <h1> - Extra notes - </h1> - <p> - EC: Cannot be removed but can be mitigated: it contains non-free - non-loadable code, but it has no access to the computer's RAM. - It has access to the on-switch of the wifi, bluetooth, modem and some - other power management features. The issue is that it has access to the - keyboard, however if the software security howto <b>(not yet written)</b> is followed correctly, - it won't be able to leak data to a local attacker. It has no network - access but it may still be able to leak data remotely, but that - requires someone to be nearby to recover the data with the help of an - SDR and some directional antennas<a href="#ref3">[3]</a>. - </p> - <p> - <a href="http://www.coreboot.org/Intel_82573_Ethernet_controller">Intel 82573 Ethernet controller</a> - on the X60 seems safe, according to Denis. - </p> - - <div class="subsection"> - <h2> - Risk level - </h2> - <ul> - <li>Modem (3g/wwan): highest</li> - <li>Intel wifi: Near highest</li> - <li>Atheros PCI wifi: unknown, but lower than intel wifi.</li> - <li>Microphone: only problematic if the computer gets compromised.</li> - <li>Speakers: only problematic if the computer gets compromised.</li> - <li>EC: can be mitigated if following the guide on software security.</li> - </ul> - </div> - </div> - - <div class="section"> - <h1> - Further reading material (software security) - </h1> - <ul> - <li><a href="../gnulinux/encrypted_debian.html">Installing Debian or Devuan GNU+Linux with full disk encryption (including /boot)</a></li> - <li><a href="../gnulinux/encrypted_parabola.html">Installing Parabola GNU+Linux with full disk encryption (including /boot)</a></li> - <li><a href="dock.html">Notes about DMA access and the docking station</a></li> - </ul> - </div> - - <div class="section"> - <h1> - References - </h1> - <div class="subsection"> - <h2 id="ref1">[1] physical access</h2> - <p> - Explain that black hats, TAO, and so on might use a 0day to get in, - and explain that in this case it mitigates what the attacker can do. - Also the TAO do some evaluation before launching an attack: they take - the probability of beeing caught into account, along with the kind of - target. A 0day costs a lot of money, I heard that it was from 100000$ - 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. - </p> - </div> - <div class="subsection"> - <h2 id="ref2">[2] microphone</h2> - <p> - It's possible to turn headphones into a microphone, you could try - yourself, however they don't record loud at all. Also intel cards have - the capability to change a connector's function, for instance the - 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. - </p> - </div> - <div class="subsection"> - <h2 id="ref3">[3] Video (CCC)</h2> - <p> - 30c3-5356-en-Firmware_Fat_Camp_webm.webm from the 30th CCC. While - their demo is experimental(their hardware also got damaged during the - transport), the spies probably already have that since a long time. - <a href="http://berlin.ftp.media.ccc.de/congress/2013/webm/30c3-5356-en-Firmware_Fat_Camp_webm.webm">http://berlin.ftp.media.ccc.de/congress/2013/webm/30c3-5356-en-Firmware_Fat_Camp_webm.webm</a> - </p> - </div> - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hardware/x60_security.md b/docs/hardware/x60_security.md new file mode 100644 index 00000000..82cd2401 --- /dev/null +++ b/docs/hardware/x60_security.md @@ -0,0 +1,319 @@ +<div class="section"> + +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](./) + +</div> + +<div class="section"> + +Table of Contents +================= + +- [Hardware Requirements](#hardware_requirements) +- [Software Requirements](#software_requirements) +- [The procedure](#procedure) + +</div> + +<div class="section"> + +Hardware requirements {#hardware_requirements} +===================== + +- An X60 +- screwdriver +- (in a later version of this tutorial: soldering iron and scalpel) + +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 + +</div> + +<div class="section"> + +Rationale +========= + +Most people think of security on the software side: the hardware is +important aswell. + +This tutorial deals with reducing the number of devices that have direct +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} +=========== + +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):\ +\ +Now gently pry off the bottom part of the front bezel, and the bluetooth +module is on the left (easily removable):\ +\ + +If your model was WWAN, remove the simcard (check anyway):\ +Uncover those 2 screws at the bottom:\ +\ +SIM card (not present in the picture) is in the marked location:\ +\ +Replacement: USB dongle. + +Now get into the motherboard. + +Remove those screws:\ + + +Push the keyboard forward (carefully):\ + + +Lift the keyboard up and disconnect it from the board:\ + + +Grab the right-hand side of the chassis and force it off (gently) and +pry up the rest of the chassis:\ + + +You should now have this:\ + + +The following is a summary of what you will remove (already done to this +system):\ +\ +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 +jack, the modem cable and also (on another model) a device inside the +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:\ +\ +**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, +we do not know what the built-in microcode (in the CPU) is doing; it +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:\ +\ +(useless, obsolete device) + +Remove the speaker:\ +\ +Reason: combined with the microphone issue, this could be used to leak +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).\ +Replacement: headphones/speakers (line-out) or external DAC (USB). + +Remove the wlan (also remove wwan if you have it):\ +\ +Reason: has direct (and very fast) memory access, and could +(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.\ +**Wwan (3g modem):** They run proprietary software! It\'s like AMT but +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). + +Not covered yet: +---------------- + +- Disable cardbus (has fast/direct memory access) +- Disable firewire (has fast/direct memory access) +- Disable flashing the ethernet firmware +- Disable SPI flash writes (can be re-enabled by unsoldering two + parts) +- Disable use of xrandr/edid on external monitor (cut 2 pins on VGA) +- Disable docking station (might be possible to do it in software, in + coreboot upstream as a Kconfig option) + +Go to +<http://media.ccc.de/browse/congress/2013/30C3_-_5529_-_en_-_saal_2_-_201312271830_-_hardening_hardware_and_choosing_a_goodbios_-_peter_stuge.html> +or directly to the video: +<http://mirror.netcologne.de/CCC/congress/2013/webm/30c3-5529-en-Hardening_hardware_and_choosing_a_goodBIOS_webm.webm>. + +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\ + 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 + on the laptop. +- Tips about preventing/mitigating risk of cold boot attack. + - soldered RAM? + - seal RAM door shut (possibly modified lower chassis) so that + system has to be disassembled (which has to go through the nail + polish) + - wipe all RAM at boot/power-off/power-on? (patch in coreboot + upstream?) + - ask gnutoo about fallback patches (counts number of boots) +- General tips/advice and web links showing how to detect physical + intrusions. +- For example: <http://cs.tau.ac.il/~tromer/acoustic/> or + <http://cyber.bgu.ac.il/content/how-leak-sensitive-data-isolated-computer-air-gap-near-mobile-phone-airhopper>. +- <https://en.wikipedia.org/wiki/Tempest_%28codename%29> +- https://gitorious.org/gnutoo-for-coreboot/grub-assemble/source/a61f636797777a742f65f4c9c58032aa6a9b23c3: + +</div> + +<div class="section"> + +Extra notes +=========== + +EC: Cannot be removed but can be mitigated: it contains non-free +non-loadable code, but it has no access to the computer\'s RAM. It has +access to the on-switch of the wifi, bluetooth, modem and some other +power management features. The issue is that it has access to the +keyboard, however if the software security howto **(not yet written)** +is followed correctly, it won\'t be able to leak data to a local +attacker. It has no network access but it may still be able to leak data +remotely, but that requires someone to be nearby to recover the data +with the help of an SDR and some directional antennas[\[3\]](#ref3). + +[Intel 82573 Ethernet +controller](http://www.coreboot.org/Intel_82573_Ethernet_controller) on +the X60 seems safe, according to Denis. + +<div class="subsection"> + +Risk level +---------- + +- Modem (3g/wwan): highest +- Intel wifi: Near highest +- Atheros PCI wifi: unknown, but lower than intel wifi. +- Microphone: only problematic if the computer gets compromised. +- Speakers: only problematic if the computer gets compromised. +- EC: can be mitigated if following the guide on software security. + +</div> + +</div> + +<div class="section"> + +Further reading material (software security) +============================================ + +- [Installing Debian or Devuan GNU+Linux with full disk encryption + (including /boot)](../gnulinux/encrypted_debian.html) +- [Installing Parabola GNU+Linux with full disk encryption (including + /boot)](../gnulinux/encrypted_parabola.html) +- [Notes about DMA access and the docking station](dock.html) + +</div> + +<div class="section"> + +References +========== + +<div class="subsection"> + +\[1\] physical access {#ref1} +--------------------- + +Explain that black hats, TAO, and so on might use a 0day to get in, and +explain that in this case it mitigates what the attacker can do. Also +the TAO do some evaluation before launching an attack: they take the +probability of beeing caught into account, along with the kind of +target. A 0day costs a lot of money, I heard that it was from 100000\$ +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. + +</div> + +<div class="subsection"> + +\[2\] microphone {#ref2} +---------------- + +It\'s possible to turn headphones into a microphone, you could try +yourself, however they don\'t record loud at all. Also intel cards have +the capability to change a connector\'s function, for instance the +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. + +</div> + +<div class="subsection"> + +\[3\] Video (CCC) {#ref3} +----------------- + +30c3-5356-en-Firmware\_Fat\_Camp\_webm.webm from the 30th CCC. While +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> + +</div> + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hcl/c201.html b/docs/hcl/c201.html deleted file mode 100644 index 595cd63e..00000000 --- a/docs/hcl/c201.html +++ /dev/null @@ -1,262 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ASUS Chromebook C201</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">ASUS Chromebook C201</h1> - - <p> - 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 laptops will be added to libreboot at a later date. - </p> - <p> - Paul Kocialkowski, a <a href="http://www.replicant.us/">Replicant</a> developer, ported this laptop to libreboot. Thank you, Paul! - </p> - - <p> - <b>More info will be added later, including build/installation instructions. - The board is supported in libreboot, however, and has been confirmed to work.</b> - </p> - - <p> - Flashing instructions can be found at <a href="../install/#flashrom">../install/#flashrom</a> - </p> - - <p> - <a href="./">Back to previous index</a>. - </p> - </div> - - <div class="section"> - <ul> - <li><a href="#googlesintent">Google's intent with CrOS devices</a></li> - <li><a href="#os">Considerations about ChromeOS and free operating systems</a></li> - <li><a href="#videoblobs">Caution: Video acceleration requires a non-free blob, software rendering can be used instead.</a></li> - <li><a href="#wifiblobs">Caution: WiFi requires a non-free blob, a USB dongle can be used instead.</a></li> - <li><a href="#ec">EC firmware is free software!</a></li> - <li><a href="#microcode">No microcode!</a></li> - <li><a href="#depthcharge">Depthcharge payload</a></li> - <li><a href="#thescrew">Flash chip write protection: the screw</a></li> - </ul> - </div> - - <div class="section"> - <h1 id="googlesintent">Google's intent with CrOS devices</h1> - <p> - CrOS (Chromium OS/Chrome OS) devices, such as Chromebooks, were not designed with the intent of bringing more freedom to users. - However, they run with a lot of free software at the boot software and embedded controller levels, - since free software gives Google enough flexibility to optimize various aspects such as boot time - and most importantly, to implement the CrOS security system, that involves various aspects of the software. - Google does hire a lot of Coreboot developers, who are generally friendly to the free software movement - and try to be good members of the free software community, by contributing code back. - </p> - <p> - CrOS devices are designed (from the factory) to actually coax the user into using - proprietary web services - (SaaSS) that invade the user's privacy (ChromeOS is literally just the Google Chrome browser when you boot up, itself proprietary - and comes with proprietary add-ons like flash. It's only intended for SaaSS, not actual, real computing). - Google is even a member of the <i>PRISM</i> program, as outlined - by Edward Snowden. See notes about ChromeOS below. The libreboot project recommends - that the user replace the default <i>ChromeOS</i> with a distribution that can be used in freedom, - without invading the user's privacy. - </p> - <p> - We also use a similar argument for the MacBook and the ThinkPads that are supported in libreboot. - Those laptops are supported, in spite of Apple and Lenovo, companies which are actually <i>hostile</i> - to the free software movement. - </p> - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - </div> - - <div class="section"> - <h1 id="os">Considerations about ChromeOS and free operating systems</h1> - <p> - This laptop comes preinstalled (from the factory) with Google ChromeOS. This is a GNU+Linux distribution, but it's not general purpose - and it comes with proprietary software. It's designed for SaaSS. Libreboot recommends that users of this laptop replace it with another distribution. - </p> - <p> - Use one of the distributions recommend by the libreboot project. - See <a href="../distros/">../distros/</a> - </p> - <h2>Debian GNU+Linux</h2> - <p> - <a href="https://wiki.debian.org/InstallingDebianOn/Asus/C201">https://wiki.debian.org/InstallingDebianOn/Asus/C201</a> - shows how to install Debian. - </p> - <p> - TODO: instructions for Devuan - </p> - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - </div> - - <div class="section"> - <h1 id="videoblobs">Caution: Video acceleration requires a non-free blob, software rendering can be used instead.</h1> - <p> - The Tamil driver source code for the onboard Mali T GPU is not released. The developer has so-far withheld it. Until that is released, the only way to use video (in freedom) on this laptop is to not have video acceleration, by making sure not to install the relevant blob. Most tasks can still be performed without video acceleration, without any noticeable performance penalty. - </p> - <p> - In practise, this means that certain things like games, blender and GNOME shell (or other fancy desktops) won't work well. - The libreboot project recommends a lightweight desktop which does not need video acceleration, such as <i>XFCE</i> or <i>LXDE</i>. - </p> - <p> - The Tamil developer wrote this blog post, which sheds light on the story: <a href="http://libv.livejournal.com/27461.html">http://libv.livejournal.com/27461.html,http://libv.livejournal.com/27461.html</a>. - </p> - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - </div> - <div class="section"> - <h1 id="wifiblobs">Caution: WiFi requires a non-free blob, a USB dongle can be used instead.</h1> - <p> - These laptops have non-removeable (soldered on) WiFi chips, which require non-free firmware in the Linux kernel - in order to work. - </p> - <p> - The libreboot project recommends using an external USB wifi dongle that works - with free software. See <a href="./#recommended_wifi">#recommended_wifi</a>. - </p> - <p> - There are 2 companies (endorsed by Creative Commons, under their <i>Respects your Freedom</i> - guidelines), that sell USB WiFi dongles guaranteed to work with free software (i.e. linux-libre kernel): - </p> - <ul> - <li><a href="https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb">ThinkPenguin sells them</a> (company based in USA)</li> - <li><a href="https://tehnoetic.com/tehnoetic-wireless-adapter-gnu-linux-libre-tet-n150">Tehnoetic sells them</a> (company based in Europe)</li> - </ul> - <p> - These wifi dongles use the AR9271 (atheros) chipset, supported by - the free <i>ath9k_htc</i> driver in the Linux kernel. They work in <i>linux-libre</i> too. - </p> - </div> - - <div class="section"> - <h1 id="ec">EC firmware is free software!</h1> - <p> - It's free software. Google provides the source. Build scripts will be added later, with EC sources - provided in libreboot, and builds of the EC firmware. - </p> - <p> - This is unlike the other current libreboot laptops (Intel based). In practise, you can - (if you do without the video/wifi blobs, and replace ChromeOS with a distribution - that respects your freedom) be more free when using one of these laptops. - </p> - <p> - The libreboot FAQ briefly describes what an <i>EC</i> is: - <a href="http://libreboot.org/faq/#firmware-ec">http://libreboot.org/faq/#firmware-ec</a> - </p> - </div> - - <div class="section"> - <h1 id="microcode">No microcode!</h1> - <p> - Unlike x86 (e.g. Intel/AMD) CPUs, ARM CPUs do not use microcode, not even built in. - On the Intel/AMD based libreboot systems, there is still microcode in the CPU - (not considered problematic by the FSF, provided that it is reasonably trusted - to not be malicious, since it's part of the hardware and read-only), but we - exclude microcode updates (volatile updates which are uploaded at boot time by the boot firmware, - if present), which are proprietary software. - </p> - <p> - On ARM CPUs, the instruction set is implemented in circuitry, without microcode. - </p> - <p> - <a href="#pagetop">Back to top of page</a>. - </p> - </div> - - <div class="section"> - <h1 id="depthcharge">Depthcharge payload</h1> - <p> - 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. - </p> - </div> - - <div class="section"> - <h1 id="thescrew">Flash chip write protection: the screw</h1> - <p> - It's next to the flash chip. Unscrew it, and the flash chip is read-write. Screw it back in, and the flash chip is read-only. - It's called the screw. - </p> - <p> - <i>The screw</i> is accessible by removing other screws and gently prying off the upper shell, where the flash chip and the screw - are then directly accessible. User flashing from software is possible, without having to externally re-flash, but the flash chip - is SPI (SOIC-8 form factor) so you can also externally re-flash if you want to. In practise, you only need to externally re-flash - if you brick the laptop; read <a href="../install/bbb_setup.html">../install/bbb_setup.html</a> for an example of how to set up - an SPI programmer. - </p> - <p> - Write protection is useful, because it prevents the firmware from being re-flashed by any malicious software that - might become executed on your GNU+Linux system, as root. In other words, it can prevent a firmware-level <i>evil maid</i> 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. - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> - diff --git a/docs/hcl/c201.md b/docs/hcl/c201.md new file mode 100644 index 00000000..5c92e5b5 --- /dev/null +++ b/docs/hcl/c201.md @@ -0,0 +1,267 @@ +<div class="section"> + +ASUS Chromebook C201 {#pagetop} +==================== + +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 +laptops will be added to libreboot at a later date. + +Paul Kocialkowski, a [Replicant](http://www.replicant.us/) developer, +ported this laptop to libreboot. Thank you, Paul! + +**More info will be added later, including build/installation +instructions. The board is supported in libreboot, however, and has been +confirmed to work.** + +Flashing instructions can be found at +[../install/\#flashrom](../install/#flashrom) + +[Back to previous index](./). + +</div> + +<div class="section"> + +- [Google\'s intent with CrOS devices](#googlesintent) +- [Considerations about ChromeOS and free operating systems](#os) +- [Caution: Video acceleration requires a non-free blob, software + rendering can be used instead.](#videoblobs) +- [Caution: WiFi requires a non-free blob, a USB dongle can be used + instead.](#wifiblobs) +- [EC firmware is free software!](#ec) +- [No microcode!](#microcode) +- [Depthcharge payload](#depthcharge) +- [Flash chip write protection: the screw](#thescrew) + +</div> + +<div class="section"> + +Google\'s intent with CrOS devices {#googlesintent} +================================== + +CrOS (Chromium OS/Chrome OS) devices, such as Chromebooks, were not +designed with the intent of bringing more freedom to users. However, +they run with a lot of free software at the boot software and embedded +controller levels, since free software gives Google enough flexibility +to optimize various aspects such as boot time and most importantly, to +implement the CrOS security system, that involves various aspects of the +software. Google does hire a lot of Coreboot developers, who are +generally friendly to the free software movement and try to be good +members of the free software community, by contributing code back. + +CrOS devices are designed (from the factory) to actually coax the user +into using proprietary web services (SaaSS) that invade the user\'s +privacy (ChromeOS is literally just the Google Chrome browser when you +boot up, itself proprietary and comes with proprietary add-ons like +flash. It\'s only intended for SaaSS, not actual, real computing). +Google is even a member of the *PRISM* program, as outlined by Edward +Snowden. See notes about ChromeOS below. The libreboot project +recommends that the user replace the default *ChromeOS* with a +distribution that can be used in freedom, without invading the user\'s +privacy. + +We also use a similar argument for the MacBook and the ThinkPads that +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). + +</div> + +<div class="section"> + +Considerations about ChromeOS and free operating systems {#os} +======================================================== + +This laptop comes preinstalled (from the factory) with Google ChromeOS. +This is a GNU+Linux distribution, but it\'s not general purpose and it +comes with proprietary software. It\'s designed for SaaSS. Libreboot +recommends that users of this laptop replace it with another +distribution. + +Use one of the distributions recommend by the libreboot project. See +[../distros/](../distros/) + +Debian GNU+Linux +---------------- + +<https://wiki.debian.org/InstallingDebianOn/Asus/C201> shows how to +install Debian. + +TODO: instructions for Devuan + +[Back to top of page](#pagetop). + +</div> + +<div class="section"> + +Caution: Video acceleration requires a non-free blob, software rendering can be used instead. {#videoblobs} +============================================================================================= + +The Tamil driver source code for the onboard Mali T GPU is not released. +The developer has so-far withheld it. Until that is released, the only +way to use video (in freedom) on this laptop is to not have video +acceleration, by making sure not to install the relevant blob. Most +tasks can still be performed without video acceleration, without any +noticeable performance penalty. + +In practise, this means that certain things like games, blender and +GNOME shell (or other fancy desktops) won\'t work well. The libreboot +project recommends a lightweight desktop which does not need video +acceleration, such as *XFCE* or *LXDE*. + +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). + +</div> + +<div class="section"> + +Caution: WiFi requires a non-free blob, a USB dongle can be used instead. {#wifiblobs} +========================================================================= + +These laptops have non-removeable (soldered on) WiFi chips, which +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). + +There are 2 companies (endorsed by Creative Commons, under their +*Respects your Freedom* guidelines), that sell USB WiFi dongles +guaranteed to work with free software (i.e. linux-libre kernel): + +- [ThinkPenguin sells + them](https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb) + (company based in USA) +- [Tehnoetic sells + them](https://tehnoetic.com/tehnoetic-wireless-adapter-gnu-linux-libre-tet-n150) + (company based in Europe) + +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. + +</div> + +<div class="section"> + +EC firmware is free software! {#ec} +============================= + +It\'s free software. Google provides the source. Build scripts will be +added later, with EC sources provided in libreboot, and builds of the EC +firmware. + +This is unlike the other current libreboot laptops (Intel based). In +practise, you can (if you do without the video/wifi blobs, and replace +ChromeOS with a distribution that respects your freedom) be more free +when using one of these laptops. + +The libreboot FAQ briefly describes what an *EC* is: +<http://libreboot.org/faq/#firmware-ec> + +</div> + +<div class="section"> + +No microcode! {#microcode} +============= + +Unlike x86 (e.g. Intel/AMD) CPUs, ARM CPUs do not use microcode, not +even built in. On the Intel/AMD based libreboot systems, there is still +microcode in the CPU (not considered problematic by the FSF, provided +that it is reasonably trusted to not be malicious, since it\'s part of +the hardware and read-only), but we exclude microcode updates (volatile +updates which are uploaded at boot time by the boot firmware, if +present), which are proprietary software. + +On ARM CPUs, the instruction set is implemented in circuitry, without +microcode. + +[Back to top of page](#pagetop). + +</div> + +<div class="section"> + +Depthcharge payload {#depthcharge} +=================== + +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. + +</div> + +<div class="section"> + +Flash chip write protection: the screw {#thescrew} +====================================== + +It\'s next to the flash chip. Unscrew it, and the flash chip is +read-write. Screw it back in, and the flash chip is read-only. It\'s +called the screw. + +*The screw* is accessible by removing other screws and gently prying off +the upper shell, where the flash chip and the screw are then directly +accessible. User flashing from software is possible, without having to +externally re-flash, but the flash chip is SPI (SOIC-8 form factor) so +you can also externally re-flash if you want to. In practise, you only +need to externally re-flash if you brick the laptop; read +[../install/bbb\_setup.html](../install/bbb_setup.html) for an example +of how to set up an SPI programmer. + +Write protection is useful, because it prevents the firmware from being +re-flashed by any malicious software that might become executed on your +GNU+Linux system, as root. In other words, it can prevent a +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. + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hcl/d510mo.html b/docs/hcl/d510mo.html deleted file mode 100644 index f11693cf..00000000 --- a/docs/hcl/d510mo.html +++ /dev/null @@ -1,82 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Intel D510MO desktop board</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Intel D510MO desktop board</h1> - - <p> - This is a desktop board using intel hardware (circa ~2009, ICH7 southbridge, similar performance-wise to the Libreboot X200. It can make for quite a nifty desktop. Powered by libreboot. - </p> - <p> - NOTE: This board has a working framebuffer in Grub, but in GNU+Linux in native resolution the display is unusable due to some raminit issues. - This board can however be used for building a headless server. - </p> - <p> - Flashing instructions can be found at <a href="../install/d510mo.html">../install/d510mo.html</a> - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> - diff --git a/docs/hcl/d510mo.md b/docs/hcl/d510mo.md new file mode 100644 index 00000000..522e34e8 --- /dev/null +++ b/docs/hcl/d510mo.md @@ -0,0 +1,55 @@ +<div class="section"> + +Intel D510MO desktop board {#pagetop} +========================== + +This is a desktop board using intel hardware (circa \~2009, ICH7 +southbridge, similar performance-wise to the Libreboot X200. It can make +for quite a nifty desktop. Powered by libreboot. + +NOTE: This board has a working framebuffer in Grub, but in GNU+Linux in +native resolution the display is unusable due to some raminit issues. +This board can however be used for building a headless server. + +Flashing instructions can be found at +[../install/d510mo.html](../install/d510mo.html) + +</div> + +<div class="section"> + +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. + +</div> diff --git a/docs/hcl/d945gclf.html b/docs/hcl/d945gclf.html deleted file mode 100644 index f18d7c19..00000000 --- a/docs/hcl/d945gclf.html +++ /dev/null @@ -1,151 +0,0 @@ -<!DOCTYPE html> -<html><head> -<meta http-equiv="content-type" content="text/html; charset=UTF-8"> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Intel D945GCLF desktop board</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Intel D945GCLF desktop board</h1> - - <p> - <a href="https://libreboot.org/docs/hcl/">Back to previous index</a> - </p> - - <p> - If you just want flashing instructions, go to - <a href="https://libreboot.org/docs/install/d945gclf.html">../install/d945gclf.html</a> - </p> - - <p> - This board is a mini-itx desktop board for 2008. It uses an atom -230, which is a singe core CPU but it is hyperthreaded so it appears to -have 2 thread to the OS. The flash chip is very small, 512KiB, so grub2 -does not fit, which is why libreboot has to use seabios on this target. -Full disk encryption like on other supported targets will not be -possible, so plan accordingly. - </p> - <p> - This board has a 945gc chipset which is the desktop equivalent of -945gm which can be found in the Lenovo x60/t60 or macbook2,1. This -chipset features an ICH7 southbridge. It has 1 DIMM slot that can -accommodate up to 2G of DDR2 RAM. - </p> - <p> - Connectivity-wise it has 1 PCI slot, a 10/100 ethernet port, 4 -usb slot and 4 usb ports, with one internal header and 2 SATA ports. - </p> - <p> - The D945GCLF2 is an upgraded version of this board. The -differences are: 1 more USB header, 10/100/1000 ethernet and a dual core - cpu (also hyperthreaded). Since the board is almost identical (and -coreboot code seem to indicate that it works, since MAX_CPU=4 is set), -it is believed that it should also work but this is untested. - </p> - <h2> - Remarks about vendor bios: - </h2> - <ul> - <li>Without coreboot/libreboot this board is utery useless, since the -vendor bios is very bad. It cannot boot from any HDD wether it is -connected to the SATA port or USB. With libreboot it works just fine.</li> - <li>The vendor bios write protects the flash so it requires external -flashing to install libreboot on this device. Once libreboot is flashed -there is no problem to update the firmware internally</li> - </ul> - <p> - Here is an image of the board:<br> - <img alt="" src="../images/d945gclf/d945gclf.jpg"><br/> - Here is an image of the D945GCLF2 board:<br> - <img alt="" src="../images/d945gclf/20160923_141521.jpg" width="80%" height="80%"><br/> - And SPI SOIC8 flash chip<br/> - <img alt="" src="../images/d945gclf/20160923_141550.jpg" width="50%" height="50%"> - </p> - </div> - - <div class="section"> - <h2>How to replace thermal paste and fan</h2> - <p> - 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<br/> - <img alt="" src="../images/d945gclf/20160923_141620.jpg" width="50%" height="50%"> - <img alt="" src="../images/d945gclf/20160923_141614.jpg" width="50%" height="50%"> - <br/> - Make sure that new one has same wiring<br/> - <img alt="" src="../images/d945gclf/20160923_142618.jpg" width="50%" height="50%"><br/> - This is a new one, with bearing and maintenable<br/> - <img alt="" src="../images/d945gclf/20160923_141738.jpg" width="50%" height="50%"> - <img alt="" src="../images/d945gclf/20160923_141814.jpg" width="50%" height="50%"><br/> - Now remove the both coolers rotating them a bit, slowly, then clean both silicons -and both coolers (removing cmos battery first is recommended)<br/> - <img alt="" src="../images/d945gclf/20160923_141601.jpg" width="50%" height="50%"><br/> - Put a little bit of non conductive thermal paste on both silicons (only cpu silicon iis shown on that image)<br/> - <img alt="" src="../images/d945gclf/20160923_142031.jpg" width="50%" height="50%"><br/> - <p>Before assembling new fan, some need new longer screws, make sure having these (on the left is original one, too short for new fan)<br/> - <img alt="" src="../images/d945gclf/20160923_141659.jpg" width="50%" height="50%"><br/> - After that, assemble your new fan into CPU cooler<br/> - <img alt="" src="../images/d945gclf/20160923_141635.jpg" width="50%" height="50%"><br/> - Finally assemle both coolers on both chips, do not forget put in the CPU fan connector back, and you are done. - </div> - - <div class="section"> - - <p> - Copyright © 2016 Arthur Heymans <arthur@aheymans.xyz><br> - Copyright © 2016 Vitaly Castaño Solana <vita_cell@hotmail.com><br> - 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 <a href="https://libreboot.org/docs/cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - - - - -</body></html> diff --git a/docs/hcl/d945gclf.md b/docs/hcl/d945gclf.md new file mode 100644 index 00000000..2e19f527 --- /dev/null +++ b/docs/hcl/d945gclf.md @@ -0,0 +1,121 @@ +<div class="section"> + +Intel D945GCLF desktop board {#pagetop} +============================ + +[Back to previous index](https://libreboot.org/docs/hcl/) + +If you just want flashing instructions, go to +[../install/d945gclf.html](https://libreboot.org/docs/install/d945gclf.html) + +This board is a mini-itx desktop board for 2008. It uses an atom 230, +which is a singe core CPU but it is hyperthreaded so it appears to have +2 thread to the OS. The flash chip is very small, 512KiB, so grub2 does +not fit, which is why libreboot has to use seabios on this target. Full +disk encryption like on other supported targets will not be possible, so +plan accordingly. + +This board has a 945gc chipset which is the desktop equivalent of 945gm +which can be found in the Lenovo x60/t60 or macbook2,1. This chipset +features an ICH7 southbridge. It has 1 DIMM slot that can accommodate up +to 2G of DDR2 RAM. + +Connectivity-wise it has 1 PCI slot, a 10/100 ethernet port, 4 usb slot +and 4 usb ports, with one internal header and 2 SATA ports. + +The D945GCLF2 is an upgraded version of this board. The differences are: +1 more USB header, 10/100/1000 ethernet and a dual core cpu (also +hyperthreaded). Since the board is almost identical (and coreboot code +seem to indicate that it works, since MAX\_CPU=4 is set), it is believed +that it should also work but this is untested. + +Remarks about vendor bios: +-------------------------- + +- Without coreboot/libreboot this board is utery useless, since the + vendor bios is very bad. It cannot boot from any HDD wether it is + connected to the SATA port or USB. With libreboot it works just + fine. +- The vendor bios write protects the flash so it requires external + flashing to install libreboot on this device. Once libreboot is + flashed there is no problem to update the firmware internally + +Here is an image of the board:\ +\ +Here is an image of the D945GCLF2 board:\ +{width="80%" height="80%"}\ +And SPI SOIC8 flash chip\ +{width="50%" height="50%"} + +</div> + +<div class="section"> + +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\ +{width="50%" height="50%"} +{width="50%" height="50%"}\ +Make sure that new one has same wiring\ +{width="50%" height="50%"}\ +This is a new one, with bearing and maintenable\ +{width="50%" height="50%"} +{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)\ +{width="50%" height="50%"}\ +Put a little bit of non conductive thermal paste on both silicons (only +cpu silicon iis shown on that image)\ +{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)\ +{width="50%" height="50%"}\ +After that, assemble your new fan into CPU cooler\ +{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. + +</div> + +<div class="section"> + +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 +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](https://libreboot.org/docs/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. + +</div> diff --git a/docs/hcl/ga-g41m-es2l.html b/docs/hcl/ga-g41m-es2l.html deleted file mode 100644 index da009d67..00000000 --- a/docs/hcl/ga-g41m-es2l.html +++ /dev/null @@ -1,86 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Gigabyte GA-G41M-ES2L desktop board</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Gigabyte GA-G41M-ES2L desktop board</h1> - - <p> - This is a desktop board using intel hardware (circa ~2009, ICH7 southbridge, similar performance-wise to the Libreboot X200. It can make for quite a nifty desktop. Powered by libreboot. - </p> - <p> - IDE on the board is untested, but it might be possible to use a SATA HDD using an IDE SATA adapter. The SATA ports do work. - </p> - <p> - 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:<br/> - hwaddress ether macaddressgoeshere - </p> - <p> - Flashing instructions can be found at <a href="../install/#flashrom">../install/#flashrom</a> - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> - diff --git a/docs/hcl/ga-g41m-es2l.md b/docs/hcl/ga-g41m-es2l.md new file mode 100644 index 00000000..98912994 --- /dev/null +++ b/docs/hcl/ga-g41m-es2l.md @@ -0,0 +1,59 @@ +<div class="section"> + +Gigabyte GA-G41M-ES2L desktop board {#pagetop} +=================================== + +This is a desktop board using intel hardware (circa \~2009, ICH7 +southbridge, similar performance-wise to the Libreboot X200. It can make +for quite a nifty desktop. Powered by libreboot. + +IDE on the board is untested, but it might be possible to use a SATA HDD +using an IDE SATA adapter. The SATA ports do work. + +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:\ +hwaddress ether macaddressgoeshere + +Flashing instructions can be found at +[../install/\#flashrom](../install/#flashrom) + +</div> + +<div class="section"> + +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. + +</div> diff --git a/docs/hcl/gm45_remove_me.html b/docs/hcl/gm45_remove_me.html deleted file mode 100644 index 8e66ef7d..00000000 --- a/docs/hcl/gm45_remove_me.html +++ /dev/null @@ -1,693 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>GM45 chipsets: remove the ME (manageability engine)</title> -</head> - -<body> - - <div class="section"> - - <h1 id="pagetop">GM45 chipsets: remove the ME (manageability engine)</h1> - <p> - This sections relates to disabling and removing the ME (Intel <b>M</b>anagement <b>E</b>ngine) on - GM45. This was originally done on the ThinkPad X200, and later adapted for the ThinkPad R400/T400/T500. It can - in principle be done on any GM45 or GS45 system. - </p> - <p> - The ME is a blob that typically must be left inside the flash chip (in the ME region, as outlined - by the default descriptor). On GM45, it is possible to remove it without any ill effects. All - other parts of coreboot on GM45 systems (provided GMA MHD4500 / Intel graphics) can be blob-free, - so removing the ME was the last obstacle to - make GM45 a feasible target in libreboot (the systems can also work without the microcode blobs). - </p> - <p> - The ME is removed and disabled in libreboot by modifying the descriptor. More info about - this can be found in the ich9deblob/ich9gen source code in resources/utilities/ich9deblob/ - in libreboot, or more generally on this page. - </p> - <p> - More information about the ME can be found at - <a href="http://www.coreboot.org/Intel_Management_Engine">http://www.coreboot.org/Intel_Management_Engine</a> - and <a href="http://me.bios.io/Main_Page">http://me.bios.io/Main_Page</a>. - </p> - <p> - Another project recently found: - <a href="http://io.smashthestack.org/me/">http://io.smashthestack.org/me/</a> - </p> - <p> - <a href="./">Back to previous index</a>. - </p> - - </div> - - <div class="section"> - - <h1 id="ich9gen">ICH9 gen utility</h1> - - <p> - It is no longer necessary to use <a href="#ich9deblob">ich9deblob</a> to generate - a deblobbed descriptor+gbe image for GM45 targets. ich9gen is a small utility within - ich9deblob that can generate them from scratch, without a factory.bin dump. - </p> - - <p> - ich9gen executables can be found under ./ich9deblob/ statically compiled in - libreboot_util. If you are using src or git, build ich9gen from source with:<br/> - $ <b>./oldbuild module ich9deblob</b><br/> - The executable will appear under resources/utilities/ich9deblob/ - </p> - - <p> - Run:<br/> - $ <b>./ich9gen</b> - </p> - - <p> - Running ich9gen this way (without any arguments) generates - a default descriptor+gbe image with a generic MAC address. - You probably don't want to use the generic one; the ROM images - in libreboot contain a descriptor+gbe image by default (already - inserted) just to prevent or mitigate the risk of bricking - your laptop, but with the generic MAC address (the libreboot - project does not know what your real MAC address is). - </p> - - <p> - You can find out your MAC address from <b>ip addr</b> or <b>ifconfig</b> in GNU+Linux. - Alternatively, if you are running libreboot already (with the correct MAC address in your - ROM), dump it (flashrom -r) and read the first 6 bytes from position 0x1000 (or 0x2000) in a hex editor - (or, rename it to factory.rom and run it in ich9deblob: in the newly created mkgbe.c - will be the individual bytes of your MAC address). If you are currently running the stock firmware - and haven't installed libreboot yet, you can also run that through ich9deblob to get the mac address. - </p> - - <p> - An even simpler way to get the MAC address would be to read what's on the little sticker on - the bottom/base of the laptop. - </p> - - <p> - 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:<br/> - $ <b>./ich9gen --macaddress XX:XX:XX:XX:XX:XX</b><br/> - (replace the XX chars with the hexadecimal chars in the MAC address that you want) - </p> - - <p> - Two new files will be created: - </p> - <ul> - <li><b>ich9fdgbe_4m.bin</b>: this is for GM45 laptops with the 4MB flash chip.</li> - <li><b>ich9fdgbe_8m.bin</b>: this is for GM45 laptops with the 8MB flash chip.</li> - <li><b>ich9fdgbe_16m.bin</b>: this is for GM45 laptops with the 16MB flash chip.</li> - </ul> - - <p> - Assuming that your libreboot image is named <b>libreboot.rom</b>, copy - the file to where <b>libreboot.rom</b> is located - and then insert the descriptor+gbe file into the ROM image.<br/> - For 16MiB flash chips:<br/> - $ <b>dd if=ich9fdgbe_16m.bin of=libreboot.rom bs=1 count=12k conv=notrunc</b><br/> - For 8MiB flash chips:<br/> - $ <b>dd if=ich9fdgbe_8m.bin of=libreboot.rom bs=1 count=12k conv=notrunc</b><br/> - For 4MiB flash chips:<br/> - $ <b>dd if=ich9fdgbe_4m.bin of=libreboot.rom bs=1 count=12k conv=notrunc</b><br/> - </p> - - <p> - Your libreboot.rom image is now ready to be flashed on the system. Refer back to - <a href="../install/#flashrom">../install/#flashrom</a> - for how to flash it. - </p> - - <h2> - Write-protecting the flash chip - </h2> - <p> - Look in <i>resources/utilities/ich9deblob/src/descriptor/descriptor.c</i> - for the following lines in the <i>descriptorHostRegionsUnlocked</i> function: - </p> -<pre> - descriptorStruct.masterAccessSection.flMstr1.fdRegionWriteAccess = 0x1; - descriptorStruct.masterAccessSection.flMstr1.biosRegionWriteAccess = 0x1; - descriptorStruct.masterAccessSection.flMstr1.meRegionWriteAccess = 0x1; - descriptorStruct.masterAccessSection.flMstr1.gbeRegionWriteAccess = 0x1; - descriptorStruct.masterAccessSection.flMstr1.pdRegionWriteAccess = 0x1; -</pre> - <p> - Also look in <i>resources/utilities/ich9deblob/src/ich9gen/mkdescriptor.c</i> - for the following lines: - </p> -<pre> - descriptorStruct.masterAccessSection.flMstr1.fdRegionWriteAccess = 0x1; /* see ../descriptor/descriptor.c */ - descriptorStruct.masterAccessSection.flMstr1.biosRegionWriteAccess = 0x1; /* see ../descriptor/descriptor.c */ - descriptorStruct.masterAccessSection.flMstr1.meRegionWriteAccess = 0x1; /* see ../descriptor/descriptor.c */ - descriptorStruct.masterAccessSection.flMstr1.gbeRegionWriteAccess = 0x1; /* see ../descriptor/descriptor.c */ - descriptorStruct.masterAccessSection.flMstr1.pdRegionWriteAccess = 0x1; /* see ../descriptor/descriptor.c */ -</pre> - - <p style="font-size:2em;"> - 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* write-protect - the chip if you have the right equipment for external flashing later on; for example, see - <a href="../install/bbb_setup.html">../install/bbb_setup.html</a>. - </p> - - <p> - Change them all to 0x0, then re-compile ich9gen. After you have done that, - follow the notes in <a href="#ich9gen">#ich9gen</a> 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 re-flashing - the chip after write-protecting it, to clear the write protection or - to flash yet another ROM image with write protection set in the descriptor). - </p> - <p> - Flashrom will tell you that you can still forcefully re-flash, using <i>-p internal:ich_spi_force=yes</i> but - this won't actually work; it'll just brick your laptop. - </p> - <p> - For external flashing guides, refer to <a href="../install/">../install/</a>. - </p> - - </div> - - <div class="section"> - - <h1 id="ich9deblob">ICH9 deblob utility</h1> - - <p> - <b>This is no longer strictly necessary. Libreboot ROM images for GM45 systems now - contain the 12KiB descriptor+gbe generated from ich9gen, by default.</b> - </p> - - <p> - This was the tool originally used to disable the ME on X200 (later adapted for other systems that use the - GM45 chipset). <a href="#ich9gen">ich9gen</a> now supersedes it; - ich9gen is better because it does not rely on dumping the factory.rom image (whereas, ich9deblob does). - </p> - - <p> - This is what you will use to generate the deblobbed descriptor+gbe regions for your libreboot ROM image. - </p> - <p> - 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 <b>./oldbuild module all</b> or <b>./oldbuild module ich9deblob</b> from the main directory (./), - otherwise you can build it like so:<br/> - $ <b>./oldbuild module ich9deblob</b><br/> - An executable file named <b>ich9deblob</b> will now appear under resources/utilities/ich9deblob/ - </p> - <p> - If you are working with libreboot_util release archive, you can find the utility included, statically compiled - (for i686 and x86_64 on GNU+Linux) under ./ich9deblob/. - </p> - - <p> - Place the factory.rom from your system - (can be obtained using the external flashing guides for GM45 targets linked <a href="../install/">../install/</a>) in - the directory where you have your ich9deblob executable, then run the tool:<br/> - $ <b>./ich9deblob</b> - </p> - <p> - A 12kiB file named <b>deblobbed_descriptor.bin</b> will now appear. <b>Keep this and the factory.rom stored in a safe location!</b> - The first 4KiB contains the descriptor data region for your system, and the next 8KiB contains the gbe region (config data for your - gigabit NIC). These 2 regions could actually be separate files, but they are joined into 1 file in this case. - </p> - <p> - A 4KiB file named <b>deblobbed_4kdescriptor.bin</b> will alternatively appear, if no GbE region was detected inside the ROM image. - This is usually the case, when a discrete NIC is used (eg Broadcom) instead of Intel. Only the Intel NICs need a GbE region in - the flash chip. - </p> - - <p> - Assuming that your libreboot image is named <b>libreboot.rom</b>, copy - the <b>deblobbed_descriptor.bin</b> file to where <b>libreboot.rom</b> is located - and then run:<br/> - $ <b>dd if=deblobbed_descriptor.bin of=libreboot.rom bs=1 count=12k conv=notrunc</b> - </p> - <p> - Alternatively, if you got a the <b>deblobbed_4kdescriptor.bin</b> file (no GbE defined), - do this: - $ <b>dd if=deblobbed_4kdescriptor.bin of=libreboot.rom bs=1 count=4k conv=notrunc</b> - </p> - <p> - - </p> - - <p> - The utility will also generate 4 additional files: - </p> - <ul> - <li>mkdescriptor.c</li> - <li>mkdescriptor.h</li> - <li>mkgbe.c</li> - <li>mkgbe.h</li> - </ul> - <p> - These are C source files that can re-generate the very same Gbe and Descriptor structs - (from ich9deblob/ich9gen). To use these, place them in src/ich9gen/ in ich9deblob, then re-build. - The newly built <b>ich9gen</b> executable will be able to re-create the very same 12KiB file from scratch, - based on the C structs, this time <b>without</b> the need for a factory.rom dump! - </p> - - <p> - You should now have a <b>libreboot.rom</b> image containing the correct 4K descriptor and 8K gbe regions, which - will then be safe to flash. Refer back to <a href="../install/#flashrom">../install/#flashrom</a> - for how to flash it. - </p> - - </div> - - <div class="section"> - - <h1 id="demefactory">demefactory utility</h1> - - <p> - This takes a factory.rom dump and disables the ME/TPM, but leaves the region intact. - It also sets all regions read-write. - </p> - - <p> - 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. - </p> - - <p> - Simply run (with factory.rom in the same directory):<br/> - $ <b>./demefactory</b> - </p> - - <p> - 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):<br/> - $ <b>dd if=demefactory_4kdescriptor.bin of=factory_nome.rom bs=1 count=4k conv=notrunc</b> - </p> - - <p> - TODO: test this.<br/> - 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: - </p> -<pre> -<roxfan> vimuser: try bios_extract with ffv patch <a href="http://patchwork.coreboot.org/patch/3444/">http://patchwork.coreboot.org/patch/3444/</a> -<roxfan> or <a href="https://github.com/coreboot/bios_extract/blob/master/phoenix_extract.py">https://github.com/coreboot/bios_extract/blob/master/phoenix_extract.py</a> -<roxfan> what are you looking for specifically, btw? - -0x74: 0x9fff03e0 PR0: Warning: 0x003e0000-0x01ffffff is read-only. -0x84: 0x81ff81f8 PR4: Warning: 0x001f8000-0x001fffff is locked. -</pre> - - <p> - Use-case: a factory.rom image modified in this way would theoretically have no - flash protections whatsoever, making it easy to quickly switch between factory/libreboot - in software, without ever having to disassemble and re-flash externally unless you brick - the device. - </p> - - <p> - demefactory is part of the ich9deblob src, found at <i>resources/utilities/ich9deblob/</i> - </p> - - </div> - - <div class="section"> - - <p> - 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. - </p> - - <div class="subsection"> - - <h2 id="early_notes">Early notes</h2> - - <ul> - <li> - <a href="http://www.intel.co.uk/content/dam/doc/datasheet/io-controller-hub-10-family-datasheet.pdf">http://www.intel.co.uk/content/dam/doc/datasheet/io-controller-hub-10-family-datasheet.pdf</a> - page 230 mentions about descriptor and non-descriptor mode (which wipes out gbe and ME/AMT). - </li> - <li> - <s><b>See reference to HDA_SDO (disable descriptor security)</b></s> - strap connected GPIO33 pin is it on ICH9-M (X200). HDA_SDO applies to later chipsets (series 6 or higher). - Disabling descriptor security also disables the ethernet according to sgsit. sgsit's method - involves use of 'soft straps' (see IRC logs below) instead of disabling the descriptor. - </li> - <li> - <b>and the location of GPIO33 on the x200s: (was an external link. Putting it here instead)</b> - <a href="images/x200/gpio33_location.jpg">images/x200/gpio33_location.jpg</a> - - it's above the number 7 on TP37 (which is above the big intel chip at the bottom) - </li> - <li> - The ME datasheet may not be for the mobile chipsets but it doesn't vary that much. - This one gives some detail and covers QM67 which is what the X201 uses: - <a href="http://www.intel.co.uk/content/dam/www/public/us/en/documents/datasheets/6-chipset-c200-chipset-datasheet.pdf">http://www.intel.co.uk/content/dam/www/public/us/en/documents/datasheets/6-chipset-c200-chipset-datasheet.pdf</a> - </li> - </ul> - - </div> - - </div> - - <div class="section"> - - <div class="subsection"> - - <h2 id="flashchips">Flash chips</h2> - - <ul> - <li> - Schematics for X200 laptop: <a href="http://pdf.datasheetarchive.com/indexerfiles/Datasheets-USER/DSAUPLD00006075.pdf">http://pdf.datasheetarchive.com/indexerfiles/Datasheets-USER/DSAUPLD00006075.pdf</a> - <b><s>- Page 20 and page 9 refer to SDA_HDO or SDA_HDOUT</s></b> only on series 6 or higher chipsets. ICH9-M (X200) does it with a strap connected to GPIO33 pin (see IRC notes below)<br/> - - According to page 29, the X200 can have any of the following flash chips: - <ul> - <li>ATMEL AT26DF321-SU 72.26321.A01 - this is a 32Mb (4MiB) chip</li> - <li>MXIC (Macronix?) MX25L3205DM2I-12G 72.25325.A01 - another 32Mb (4MiB) chip</li> - <li>MXIC (Macronix?) MX25L6405DMI-12G 41R0820AA - this is a 64Mb (8MiB) chip</li> - <li>Winbond W25X64VSFIG 41R0820BA - another 64Mb (8MiB) chip</li> - </ul> - sgsit says that the X200s with the 64Mb flash chips are (probably) the ones with AMT (alongside the ME), whereas - the 32Mb chips contain only the ME. - </li> - <li> - Schematics for X200s laptop: <a href="http://pdf.datasheetarchive.com/indexerfiles/Datasheets-USER/DSAUPLD00006104.pdf">http://pdf.datasheetarchive.com/indexerfiles/Datasheets-USER/DSAUPLD00006104.pdf</a>. - </li> - </ul> - - </div> - - </div> - - <div class="section"> - - <h2 id="early_development_notes">Early development notes</h2> - -<pre> -<i> -Start (hex) End (hex) Length (hex) Area Name ------------ --------- ------------ --------- -00000000 003FFFFF 00400000 Flash Image - -00000000 00000FFF 00001000 Descriptor Region -00000004 0000000F 0000000C Descriptor Map -00000010 0000001B 0000000C Component Section -00000040 0000004F 00000010 Region Section -00000060 0000006B 0000000C Master Access Section -00000060 00000063 00000004 CPU/BIOS -00000064 00000067 00000004 Manageability Engine (ME) -00000068 0000006B 00000004 GbE LAN -00000100 00000103 00000004 ICH Strap 0 -00000104 00000107 00000004 ICH Strap 1 -00000200 00000203 00000004 MCH Strap 0 -00000EFC 00000EFF 00000004 Descriptor Map 2 -00000ED0 00000EF7 00000028 ME VSCC Table -00000ED0 00000ED7 00000008 Flash device 1 -00000ED8 00000EDF 00000008 Flash device 2 -00000EE0 00000EE7 00000008 Flash device 3 -00000EE8 00000EEF 00000008 Flash device 4 -00000EF0 00000EF7 00000008 Flash device 5 -00000F00 00000FFF 00000100 OEM Section -00001000 001F5FFF 001F5000 ME Region -001F6000 001F7FFF 00002000 GbE Region -001F8000 001FFFFF 00008000 PDR Region -00200000 003FFFFF 00200000 BIOS Region - -Start (hex) End (hex) Length (hex) Area Name ------------ --------- ------------ --------- -00000000 003FFFFF 00400000 Flash Image - -00000000 00000FFF 00001000 Descriptor Region -00000004 0000000F 0000000C Descriptor Map -00000010 0000001B 0000000C Component Section -00000040 0000004F 00000010 Region Section -00000060 0000006B 0000000C Master Access Section -00000060 00000063 00000004 CPU/BIOS -00000064 00000067 00000004 Manageability Engine (ME) -00000068 0000006B 00000004 GbE LAN -00000100 00000103 00000004 ICH Strap 0 -00000104 00000107 00000004 ICH Strap 1 -00000200 00000203 00000004 MCH Strap 0 -00000ED0 00000EF7 00000028 ME VSCC Table -00000ED0 00000ED7 00000008 Flash device 1 -00000ED8 00000EDF 00000008 Flash device 2 -00000EE0 00000EE7 00000008 Flash device 3 -00000EE8 00000EEF 00000008 Flash device 4 -00000EF0 00000EF7 00000008 Flash device 5 -00000EFC 00000EFF 00000004 Descriptor Map 2 -00000F00 00000FFF 00000100 OEM Section -00001000 00002FFF 00002000 GbE Region -00003000 00202FFF 00200000 BIOS Region - -Build Settings --------------- -Flash Erase Size = 0x1000 - -</i> -</pre> - - <p> - It's a utility called 'Flash Image Tool' for ME 4.x that was used for this. You drag a complete - image into in and the utility decomposes the various components, allowing you to set soft straps. - </p> - <p> - This tool is proprietary, for Windows only, but was used to deblob the 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. - </p> - - </div> - - <div class="section"> - - <h2 id="gbe_region"> - GBE (gigabit ethernet) region in SPI flash - </h2> - - <p> - Of the 8K, about 95% is 0xFF. - The data is the gbe region is fully documented in this public datasheet: - <a href="http://www.intel.co.uk/content/dam/doc/application-note/i-o-controller-hub-9m-82567lf-lm-v-nvm-map-appl-note.pdf">http://www.intel.co.uk/content/dam/doc/application-note/i-o-controller-hub-9m-82567lf-lm-v-nvm-map-appl-note.pdf</a> - </p> - - <p> - The only actual content found was: - </p> - -<pre> -<i> -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 -02 06 40 2B 43 00 00 00 F5 10 AD BA F5 10 BF 10 -AD BA CB 10 AD BA AD BA 00 00 00 00 00 00 00 00 -00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -00 01 00 40 28 12 07 40 FF FF FF FF FF FF FF FF -FF FF FF FF FF FF FF FF FF FF FF FF FF FF D9 F0 -20 60 1F 00 02 00 13 00 00 80 1D 00 FF 00 16 00 -DD CC 18 00 11 20 17 00 DD DD 18 00 12 20 17 00 -00 80 1D 00 00 00 1F -</i> -</pre> - - <p> - 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. - </p> - - <p> - 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. - </p> - - <div class="subsection"> - - <h3 id="gbe_region_changemacaddress">GBE region: change MAC address</h3> - - <p> - According to the datasheet, it's supposed to add up to 0xBABA but can actually be others on the X200. - <a href="https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums">https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums</a> - </p> - <p> - <i>"One of those engineers loves classic rock music, so they selected 0xBABA"</i> - </p> - <p>In honour of the song <i>Baba O'Reilly</i> by <i>The Who</i> apparently. We're not making this stuff up...</p> - - <p> - 0x3ABA, 0x34BA, 0x40BA and more have been observed in the main Gbe regions on the X200 factory.rom dumps. - The checksums of the backup regions match BABA, however. - </p> - - <p> - 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. - </p> - - <p> - Look at resources/utilities/ich9deblob/ich9deblob.c. - </p> - <ul> - <li>Add the first 0x3F 16bit numbers (unsigned) of the GBe descriptor together (this includes the checksum value) - and that has to add up to 0xBABA. In other words, the checksum is 0xBABA minus the total of the first - 0x3E 16bit numbers (unsigned), ignoring any overflow.</li> - </ul> - - </div> - - </div> - - <div class="section"> - - <h2 id="flash_descriptor_region">Flash descriptor region</h2> - - <p> - <a href="http://www.intel.co.uk/content/dam/doc/datasheet/io-controller-hub-9-datasheet.pdf">http://www.intel.co.uk/content/dam/doc/datasheet/io-controller-hub-9-datasheet.pdf</a> - from page 850 onwards. This explains everything that is in the flash descriptor, which can be used to understand what libreboot - is doing about modifying it. - </p> - - <p> - How to deblob: - </p> - <ul> - <li>patch the number of regions present in the descriptor from 5 - 3</li> - <li>originally descriptor + bios + me + gbe + platform</li> - <li>modified = descriptor + bios + gbe</li> - <li>the next stage is to patch the part of the descriptor which defines the start and end point of each section</li> - <li>then cut out the gbe region and insert it just after the region</li> - <li>all this can be substantiated with public docs (ICH9 datasheet)</li> - <li>the final part is flipping 2 bits. Halting the ME via 1 MCH soft strap and 1 ICH soft strap</li> - <li>the part of the descriptor described there gives the base address and length of each region (bits 12:24 of each address)</li> - <li>to disable a region, you set the base address to 0xFFF and the length to 0</li> - <li>and you change the number of regions from 4 (zero based) to 2</li> - </ul> - - <p> - There's an interesting parameter called 'ME Alternate disable', which allows the ME to only handle hardware errata in the southbridge, - but disables any other functionality. This is similar to the 'ignition' in the 5 series and higher but using the standard firmware - instead of a small 128K version. Useless for libreboot, though. - </p> - - <p> - To deblob GM45, you chop out the platform and ME regions and correct the addresses in flReg1-4. - Then you set meDisable to 1 in ICHSTRAP0 and MCHSTRAP0. - </p> - - <p>How to patch the descriptor from the factory.rom dump</p> - <ul> - <li>map the first 4k into the struct (minus the gbe region)</li> - <li>set NR in FLMAP0 to 2 (from 4)</li> - <li>adjust BASE and LIMIT in flReg1,2,3,4 to reflect the new location of each region (or remove them in the case of Platform and ME)</li> - <li>set meDisable to 1/true in ICHSTRAP0 and MCHSTRAP0</li> - <li>extract the 8k GBe region and append that to the end of the 4k descriptor</li> - <li>output the 12k concatenated chunk</li> - <li>Then it can be dd'd into the first 12K part of a coreboot image.</li> - <li>the GBe region always starts 0x20A000 bytes from the end of the ROM</li> - </ul> - - <p> - This means that libreboot's descriptor region will simply define the following regions: - </p> - <ul> - <li>descriptor (4K)</li> - <li>gbe (8K)</li> - <li>bios (rest of flash chip. CBFS also set to occupy this whole size)</li> - </ul> - - <p> - The data in the descriptor region is little endian, and it represents bits 24:12 of the address - (bits 12-24, written this way since bit 24 is nearer to left than bit 12 in the binary representation). - </p> - <p> - So, <i>x << 12 = address</i> - </p> - <p> - If it's in descriptor mode, then the first 4 bytes will be 5A A5 F0 0F. - </p> - - </div> - - - <div class="section"> - - <h2 id="platform_data_region">platform data partition in boot flash (factory.rom / lenovo bios)</h2> - - <p> - Basically useless for libreboot, since it appears to be a blob. - Removing it didn't cause any issues in libreboot. - </p> - <p> - This is a 32K region from the factory image. It could be data - (non-functional) that the original Lenovo BIOS used, but we don't know. - </p> - - <p> - It has only a 448 byte fragment different from 0x00 or 0xFF. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md new file mode 100644 index 00000000..92ef4347 --- /dev/null +++ b/docs/hcl/gm45_remove_me.md @@ -0,0 +1,604 @@ +<div class="section"> + +GM45 chipsets: remove the ME (manageability engine) {#pagetop} +=================================================== + +This sections relates to disabling and removing the ME (Intel +**M**anagement **E**ngine) on GM45. This was originally done on the +ThinkPad X200, and later adapted for the ThinkPad R400/T400/T500. It can +in principle be done on any GM45 or GS45 system. + +The ME is a blob that typically must be left inside the flash chip (in +the ME region, as outlined by the default descriptor). On GM45, it is +possible to remove it without any ill effects. All other parts of +coreboot on GM45 systems (provided GMA MHD4500 / Intel graphics) can be +blob-free, so removing the ME was the last obstacle to make GM45 a +feasible target in libreboot (the systems can also work without the +microcode blobs). + +The ME is removed and disabled in libreboot by modifying the descriptor. +More info about this can be found in the ich9deblob/ich9gen source code +in resources/utilities/ich9deblob/ in libreboot, or more generally on +this page. + +More information about the ME can be found at +<http://www.coreboot.org/Intel_Management_Engine> and +<http://me.bios.io/Main_Page>. + +Another project recently found: <http://io.smashthestack.org/me/> + +[Back to previous index](./). + +</div> + +<div class="section"> + +ICH9 gen utility {#ich9gen} +================ + +It is no longer necessary to use [ich9deblob](#ich9deblob) to generate a +deblobbed descriptor+gbe image for GM45 targets. ich9gen is a small +utility within ich9deblob that can generate them from scratch, without a +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**\ +The executable will appear under resources/utilities/ich9deblob/ + +Run:\ +\$ **./ich9gen** + +Running ich9gen this way (without any arguments) generates a default +descriptor+gbe image with a generic MAC address. You probably don\'t +want to use the generic one; the ROM images in libreboot contain a +descriptor+gbe image by default (already inserted) just to prevent or +mitigate the risk of bricking your laptop, but with the generic MAC +address (the libreboot project does not know what your real MAC address +is). + +You can find out your MAC address from **ip addr** or **ifconfig** in +GNU+Linux. Alternatively, if you are running libreboot already (with the +correct MAC address in your ROM), dump it (flashrom -r) and read the +first 6 bytes from position 0x1000 (or 0x2000) in a hex editor (or, +rename it to factory.rom and run it in ich9deblob: in the newly created +mkgbe.c will be the individual bytes of your MAC address). If you are +currently running the stock firmware and haven\'t installed libreboot +yet, you can also run that through ich9deblob to get the mac address. + +An even simpler way to get the MAC address would be to read what\'s on +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**\ +(replace the XX chars with the hexadecimal chars in the MAC address that +you want) + +Two new files will be created: + +- **ich9fdgbe\_4m.bin**: this is for GM45 laptops with the 4MB flash + chip. +- **ich9fdgbe\_8m.bin**: this is for GM45 laptops with the 8MB flash + chip. +- **ich9fdgbe\_16m.bin**: this is for GM45 laptops with the 16MB flash + chip. + +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:\ +\$ **dd if=ich9fdgbe\_16m.bin of=libreboot.rom bs=1 count=12k +conv=notrunc**\ +For 8MiB flash chips:\ +\$ **dd if=ich9fdgbe\_8m.bin of=libreboot.rom bs=1 count=12k +conv=notrunc**\ +For 4MiB flash chips:\ +\$ **dd if=ich9fdgbe\_4m.bin of=libreboot.rom bs=1 count=12k +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 +it. + +Write-protecting the flash chip +------------------------------- + +Look in *resources/utilities/ich9deblob/src/descriptor/descriptor.c* for +the following lines in the *descriptorHostRegionsUnlocked* function: + + descriptorStruct.masterAccessSection.flMstr1.fdRegionWriteAccess = 0x1; + descriptorStruct.masterAccessSection.flMstr1.biosRegionWriteAccess = 0x1; + descriptorStruct.masterAccessSection.flMstr1.meRegionWriteAccess = 0x1; + descriptorStruct.masterAccessSection.flMstr1.gbeRegionWriteAccess = 0x1; + descriptorStruct.masterAccessSection.flMstr1.pdRegionWriteAccess = 0x1; + +Also look in *resources/utilities/ich9deblob/src/ich9gen/mkdescriptor.c* +for the following lines: + + descriptorStruct.masterAccessSection.flMstr1.fdRegionWriteAccess = 0x1; /* see ../descriptor/descriptor.c */ + descriptorStruct.masterAccessSection.flMstr1.biosRegionWriteAccess = 0x1; /* see ../descriptor/descriptor.c */ + descriptorStruct.masterAccessSection.flMstr1.meRegionWriteAccess = 0x1; /* see ../descriptor/descriptor.c */ + descriptorStruct.masterAccessSection.flMstr1.gbeRegionWriteAccess = 0x1; /* see ../descriptor/descriptor.c */ + descriptorStruct.masterAccessSection.flMstr1.pdRegionWriteAccess = 0x1; /* see ../descriptor/descriptor.c */ + +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\* +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 +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 +re-flashing the chip after write-protecting it, to clear the write +protection or to flash yet another ROM image with write protection set +in the descriptor). + +Flashrom will tell you that you can still forcefully re-flash, using *-p +internal:ich\_spi\_force=yes* but this won\'t actually work; it\'ll just +brick your laptop. + +For external flashing guides, refer to [../install/](../install/). + +</div> + +<div class="section"> + +ICH9 deblob utility {#ich9deblob} +=================== + +**This is no longer strictly necessary. Libreboot ROM images for GM45 +systems now contain the 12KiB descriptor+gbe generated from ich9gen, by +default.** + +This was the tool originally used to disable the ME on X200 (later +adapted for other systems that use the GM45 chipset). +[ich9gen](#ich9gen) now supersedes it; ich9gen is better because it does +not rely on dumping the factory.rom image (whereas, ich9deblob does). + +This is what you will use to generate the deblobbed descriptor+gbe +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**\ +An executable file named **ich9deblob** will now appear under +resources/utilities/ich9deblob/ + +If you are working with libreboot\_util release archive, you can find +the utility included, statically compiled (for i686 and x86\_64 on +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** + +A 12kiB file named **deblobbed\_descriptor.bin** will now appear. **Keep +this and the factory.rom stored in a safe location!** The first 4KiB +contains the descriptor data region for your system, and the next 8KiB +contains the gbe region (config data for your gigabit NIC). These 2 +regions could actually be separate files, but they are joined into 1 +file in this case. + +A 4KiB file named **deblobbed\_4kdescriptor.bin** will alternatively +appear, if no GbE region was detected inside the ROM image. This is +usually the case, when a discrete NIC is used (eg Broadcom) instead of +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:\ +\$ **dd if=deblobbed\_descriptor.bin of=libreboot.rom bs=1 count=12k +conv=notrunc** + +Alternatively, if you got a the **deblobbed\_4kdescriptor.bin** file (no +GbE defined), do this: \$ **dd if=deblobbed\_4kdescriptor.bin +of=libreboot.rom bs=1 count=4k conv=notrunc** + +The utility will also generate 4 additional files: + +- mkdescriptor.c +- mkdescriptor.h +- mkgbe.c +- mkgbe.h + +These are C source files that can re-generate the very same Gbe and +Descriptor structs (from ich9deblob/ich9gen). To use these, place them +in src/ich9gen/ in ich9deblob, then re-build. The newly built +**ich9gen** executable will be able to re-create the very same 12KiB +file from scratch, based on the C structs, this time **without** the +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 +it. + +</div> + +<div class="section"> + +demefactory utility {#demefactory} +=================== + +This takes a factory.rom dump and disables the ME/TPM, but leaves the +region intact. It also sets all regions read-write. + +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):\ +\$ **./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):\ +\$ **dd if=demefactory\_4kdescriptor.bin of=factory\_nome.rom bs=1 +count=4k conv=notrunc** + +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: + + <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 + <roxfan> what are you looking for specifically, btw? + + 0x74: 0x9fff03e0 PR0: Warning: 0x003e0000-0x01ffffff is read-only. + 0x84: 0x81ff81f8 PR4: Warning: 0x001f8000-0x001fffff is locked. + +Use-case: a factory.rom image modified in this way would theoretically +have no flash protections whatsoever, making it easy to quickly switch +between factory/libreboot in software, without ever having to +disassemble and re-flash externally unless you brick the device. + +demefactory is part of the ich9deblob src, found at +*resources/utilities/ich9deblob/* + +</div> + +<div class="section"> + +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. + +<div class="subsection"> + +Early notes {#early_notes} +----------- + +- <http://www.intel.co.uk/content/dam/doc/datasheet/io-controller-hub-10-family-datasheet.pdf> + page 230 mentions about descriptor and non-descriptor mode (which + wipes out gbe and ME/AMT). +- ~~**See reference to HDA\_SDO (disable descriptor security)**~~ + strap connected GPIO33 pin is it on ICH9-M (X200). HDA\_SDO applies + to later chipsets (series 6 or higher). Disabling descriptor + security also disables the ethernet according to sgsit. sgsit\'s + method involves use of \'soft straps\' (see IRC logs below) instead + of disabling the descriptor. +- **and the location of GPIO33 on the x200s: (was an external link. + Putting it here instead)** + [images/x200/gpio33\_location.jpg](images/x200/gpio33_location.jpg) - + it\'s above the number 7 on TP37 (which is above the big intel chip + at the bottom) +- The ME datasheet may not be for the mobile chipsets but it doesn\'t + vary that much. This one gives some detail and covers QM67 which is + what the X201 uses: + <http://www.intel.co.uk/content/dam/www/public/us/en/documents/datasheets/6-chipset-c200-chipset-datasheet.pdf> + +</div> + +</div> + +<div class="section"> + +<div class="subsection"> + +Flash chips {#flashchips} +----------- + +- Schematics for X200 laptop: + <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)\ + - 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 + - MXIC (Macronix?) MX25L3205DM2I-12G 72.25325.A01 - another 32Mb + (4MiB) chip + - MXIC (Macronix?) MX25L6405DMI-12G 41R0820AA - this is a 64Mb + (8MiB) chip + - Winbond W25X64VSFIG 41R0820BA - another 64Mb (8MiB) chip + + sgsit says that the X200s with the 64Mb flash chips are (probably) + the ones with AMT (alongside the ME), whereas the 32Mb chips contain + only the ME. +- Schematics for X200s laptop: + <http://pdf.datasheetarchive.com/indexerfiles/Datasheets-USER/DSAUPLD00006104.pdf>. + +</div> + +</div> + +<div class="section"> + +Early development notes {#early_development_notes} +----------------------- + + + Start (hex) End (hex) Length (hex) Area Name + ----------- --------- ------------ --------- + 00000000 003FFFFF 00400000 Flash Image + + 00000000 00000FFF 00001000 Descriptor Region + 00000004 0000000F 0000000C Descriptor Map + 00000010 0000001B 0000000C Component Section + 00000040 0000004F 00000010 Region Section + 00000060 0000006B 0000000C Master Access Section + 00000060 00000063 00000004 CPU/BIOS + 00000064 00000067 00000004 Manageability Engine (ME) + 00000068 0000006B 00000004 GbE LAN + 00000100 00000103 00000004 ICH Strap 0 + 00000104 00000107 00000004 ICH Strap 1 + 00000200 00000203 00000004 MCH Strap 0 + 00000EFC 00000EFF 00000004 Descriptor Map 2 + 00000ED0 00000EF7 00000028 ME VSCC Table + 00000ED0 00000ED7 00000008 Flash device 1 + 00000ED8 00000EDF 00000008 Flash device 2 + 00000EE0 00000EE7 00000008 Flash device 3 + 00000EE8 00000EEF 00000008 Flash device 4 + 00000EF0 00000EF7 00000008 Flash device 5 + 00000F00 00000FFF 00000100 OEM Section + 00001000 001F5FFF 001F5000 ME Region + 001F6000 001F7FFF 00002000 GbE Region + 001F8000 001FFFFF 00008000 PDR Region + 00200000 003FFFFF 00200000 BIOS Region + + Start (hex) End (hex) Length (hex) Area Name + ----------- --------- ------------ --------- + 00000000 003FFFFF 00400000 Flash Image + + 00000000 00000FFF 00001000 Descriptor Region + 00000004 0000000F 0000000C Descriptor Map + 00000010 0000001B 0000000C Component Section + 00000040 0000004F 00000010 Region Section + 00000060 0000006B 0000000C Master Access Section + 00000060 00000063 00000004 CPU/BIOS + 00000064 00000067 00000004 Manageability Engine (ME) + 00000068 0000006B 00000004 GbE LAN + 00000100 00000103 00000004 ICH Strap 0 + 00000104 00000107 00000004 ICH Strap 1 + 00000200 00000203 00000004 MCH Strap 0 + 00000ED0 00000EF7 00000028 ME VSCC Table + 00000ED0 00000ED7 00000008 Flash device 1 + 00000ED8 00000EDF 00000008 Flash device 2 + 00000EE0 00000EE7 00000008 Flash device 3 + 00000EE8 00000EEF 00000008 Flash device 4 + 00000EF0 00000EF7 00000008 Flash device 5 + 00000EFC 00000EFF 00000004 Descriptor Map 2 + 00000F00 00000FFF 00000100 OEM Section + 00001000 00002FFF 00002000 GbE Region + 00003000 00202FFF 00200000 BIOS Region + + Build Settings + -------------- + Flash Erase Size = 0x1000 + +It\'s a utility called \'Flash Image Tool\' for ME 4.x that was used for +this. You drag a complete image into in and the utility decomposes the +various components, allowing you to set soft straps. + +This tool is proprietary, for Windows only, but was used to deblob the +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. + +</div> + +<div class="section"> + +GBE (gigabit ethernet) region in SPI flash {#gbe_region} +------------------------------------------ + +Of the 8K, about 95% is 0xFF. The data is the gbe region is fully +documented in this public datasheet: +<http://www.intel.co.uk/content/dam/doc/application-note/i-o-controller-hub-9m-82567lf-lm-v-nvm-map-appl-note.pdf> + +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 + 02 06 40 2B 43 00 00 00 F5 10 AD BA F5 10 BF 10 + AD BA CB 10 AD BA AD BA 00 00 00 00 00 00 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 01 00 40 28 12 07 40 FF FF FF FF FF FF FF FF + FF FF FF FF FF FF FF FF FF FF FF FF FF FF D9 F0 + 20 60 1F 00 02 00 13 00 00 80 1D 00 FF 00 16 00 + DD CC 18 00 11 20 17 00 DD DD 18 00 12 20 17 00 + 00 80 1D 00 00 00 1F + +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 +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. + +<div class="subsection"> + +### GBE region: change MAC address {#gbe_region_changemacaddress} + +According to the datasheet, it\'s supposed to add up to 0xBABA but can +actually be others on the X200. +<https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums> + +*\"One of those engineers loves classic rock music, so they selected +0xBABA\"* + +In honour of the song *Baba O\'Reilly* by *The Who* apparently. We\'re +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 +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. + +Look at resources/utilities/ich9deblob/ich9deblob.c. + +- Add the first 0x3F 16bit numbers (unsigned) of the GBe descriptor + together (this includes the checksum value) and that has to add up + to 0xBABA. In other words, the checksum is 0xBABA minus the total of + the first 0x3E 16bit numbers (unsigned), ignoring any overflow. + +</div> + +</div> + +<div class="section"> + +Flash descriptor region {#flash_descriptor_region} +----------------------- + +<http://www.intel.co.uk/content/dam/doc/datasheet/io-controller-hub-9-datasheet.pdf> +from page 850 onwards. This explains everything that is in the flash +descriptor, which can be used to understand what libreboot is doing +about modifying it. + +How to deblob: + +- patch the number of regions present in the descriptor from 5 - 3 +- originally descriptor + bios + me + gbe + platform +- modified = descriptor + bios + gbe +- the next stage is to patch the part of the descriptor which defines + the start and end point of each section +- then cut out the gbe region and insert it just after the region +- all this can be substantiated with public docs (ICH9 datasheet) +- the final part is flipping 2 bits. Halting the ME via 1 MCH soft + strap and 1 ICH soft strap +- the part of the descriptor described there gives the base address + and length of each region (bits 12:24 of each address) +- to disable a region, you set the base address to 0xFFF and the + length to 0 +- and you change the number of regions from 4 (zero based) to 2 + +There\'s an interesting parameter called \'ME Alternate disable\', which +allows the ME to only handle hardware errata in the southbridge, but +disables any other functionality. This is similar to the \'ignition\' in +the 5 series and higher but using the standard firmware instead of a +small 128K version. Useless for libreboot, though. + +To deblob GM45, you chop out the platform and ME regions and correct the +addresses in flReg1-4. Then you set meDisable to 1 in ICHSTRAP0 and +MCHSTRAP0. + +How to patch the descriptor from the factory.rom dump + +- map the first 4k into the struct (minus the gbe region) +- set NR in FLMAP0 to 2 (from 4) +- adjust BASE and LIMIT in flReg1,2,3,4 to reflect the new location of + each region (or remove them in the case of Platform and ME) +- set meDisable to 1/true in ICHSTRAP0 and MCHSTRAP0 +- extract the 8k GBe region and append that to the end of the 4k + descriptor +- output the 12k concatenated chunk +- Then it can be dd\'d into the first 12K part of a coreboot image. +- the GBe region always starts 0x20A000 bytes from the end of the ROM + +This means that libreboot\'s descriptor region will simply define the +following regions: + +- descriptor (4K) +- gbe (8K) +- bios (rest of flash chip. CBFS also set to occupy this whole size) + +The data in the descriptor region is little endian, and it represents +bits 24:12 of the address (bits 12-24, written this way since bit 24 is +nearer to left than bit 12 in the binary representation). + +So, *x << 12 = address* + +If it\'s in descriptor mode, then the first 4 bytes will be 5A A5 F0 0F. + +</div> + +<div class="section"> + +platform data partition in boot flash (factory.rom / lenovo bios) {#platform_data_region} +----------------------------------------------------------------- + +Basically useless for libreboot, since it appears to be a blob. Removing +it didn\'t cause any issues in libreboot. + +This is a 32K region from the factory image. It could be data +(non-functional) that the original Lenovo BIOS used, but we don\'t know. + +It has only a 448 byte fragment different from 0x00 or 0xFF. + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hcl/imac52.html b/docs/hcl/imac52.html deleted file mode 100644 index 0dad8992..00000000 --- a/docs/hcl/imac52.html +++ /dev/null @@ -1,76 +0,0 @@ - -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Apple iMac 5,2</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Apple iMac 5,2</h1> - - <p> - Information to be written soon, but this board is merged in libreboot. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> - diff --git a/docs/hcl/imac52.md b/docs/hcl/imac52.md new file mode 100644 index 00000000..ea4d0394 --- /dev/null +++ b/docs/hcl/imac52.md @@ -0,0 +1,46 @@ +<div class="section"> + +Apple iMac 5,2 {#pagetop} +============== + +Information to be written soon, but this board is merged in libreboot. + +</div> + +<div class="section"> + +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. + +</div> diff --git a/docs/hcl/index.html b/docs/hcl/index.html deleted file mode 100644 index 3c1dd403..00000000 --- a/docs/hcl/index.html +++ /dev/null @@ -1,736 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Hardware compatibility list</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Hardware compatibility list</h1> - <p> - This sections relates to known hardware compatibility in libreboot. - </p> - <ul> - <li> - <a href="#supported_list">List of supported hardware</a> - <ul> - <li><a href="#supported_desktops_x86amdintel">Desktops (x86, AMD and Intel)</a></li> - <li><a href="#supported_workstations_x86amd">Servers/workstations</a></li> - <li><a href="#supported_laptops_arm">Laptops (ARM)</a></li> - <li><a href="#supported_laptops_x86intel">Laptops (Intel, x86)</a></li> - </ul> - </li> - <li> - NOTES: - <ul> - <li><a href="#ecupdate">Updating the EC firmware on i945 and GM45 (recommended)</a></li> - <li><a href="#ecversion">How to find what EC version you have (i945/GM45)</a></li> - </ul> - </li> - <li><a href="#recommended_wifi">Recommended wifi chipsets</a></li> - </ul> - <p> - <a href="../">Back to previous index</a>. - </p> - </div> - - <div class="section"> - - <h2 id="supported_list">List of supported hardware</h2> - - <p> - Libreboot supports the following systems in this release: - </p> - <h3 id="supported_desktops_x86amdintel">Desktops (AMD, Intel, x86)</h3> - <ul> - <li><a href="ga-g41m-es2l.html">Gigabyte GA-G41M-ES2L motherboard</a></li> - <li><a href="d510mo.html">Intel D510MO motherboard</a></li> - <li><a href="kcma-d8.html">ASUS KCMA-D8 motherboard</a></li> - <li><a href="d945gclf.html">Intel D945GCLF</a></li> - <li><a href="imac52.html">Apple iMac 5,2</a></li> - </ul> - <h3 id="supported_workstations_x86amd">Servers/workstations (AMD, x86)</h3> - <ul> - <li><a href="kfsn4-dre.html">ASUS KFSN4-DRE motherboard</a></li> - <li><a href="kgpe-d16.html">ASUS KGPE-D16 motherboard</a></li> - </ul> - <h3 id="supported_laptops_arm">Laptops (ARM)</h3> - <ul> - <li><a href="c201.html">ASUS Chromebook C201</a></li> - </ul> - <h3 id="supported_laptops_x86intel">Laptops (Intel, x86)</h3> - <ul> - <li><a href="#supported_x60_list">Lenovo ThinkPad X60/X60s</a></li> - <li><a href="#supported_x60t_list">Lenovo ThinkPad X60 Tablet</a></li> - <li><a href="#supported_t60_list">Lenovo ThinkPad T60</a> (there are exceptions. see link)</li> - <li><a href="x200.html">Lenovo ThinkPad X200</a></li> - <li><a href="r400.html">Lenovo ThinkPad R400</a></li> - <li><a href="t400.html">Lenovo ThinkPad T400</a></li> - <li><a href="t500.html">Lenovo ThinkPad T500</a></li> - <li><a href="#macbook11">Apple MacBook1,1</a></li> - <li><a href="#macbook21">Apple MacBook2,1</a></li> - </ul> - - <p> - 'Supported' means that the build scripts know how to build ROM images for these systems, - and that the systems have been tested (confirmed working). There may be exceptions; - in other words, this is a list of 'officially' supported systems. - </p> - - <p> - It is also possible to build ROM images (from source) for other systems (and virtual systems, e.g. QEMU). - </p> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - - <div class="section"> - - <h1 id="ecupdate">EC update on i945 (X60, T60) and GM45 (X200, T400, T500, R400)</h1> - - <p> - It is recommended that you update to the latest EC firmware version. - The <a href="https://libreboot.org/faq/#firmware-ec">EC firmware</a> - is separate from libreboot, so we don't actually provide that, but - if you still have Lenovo BIOS then you can just run the Lenovo BIOS - update utility, which will update both the BIOS and EC version. - See: - </p> - <ul> - <li><a href="https://libreboot.org/docs/install/index.html#flashrom">https://libreboot.org/docs/install/index.html#flashrom</a></li> - <li><a href="http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk">http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk</a></li> - </ul> - <p> - NOTE: this can only be done when you are using Lenovo BIOS. How to - update the EC firmware while running libreboot is unknown. - Libreboot only replaces the BIOS firmware, not EC. - </p> - <p> - Updated EC firmware has several advantages e.g. - bettery battery handling. - </p> - <p> - <a href="#pagetop">Back to top of page</a> - </p> - - </div> - - <div class="section"> - - <h1 id="ecversion">How to find what EC version you have (i945/GM45)</h1> - - <p> - In GNU+Linux, you can try this:<br/> - <strong>grep 'at EC' /proc/asound/cards</strong> - </p> - <p> - Sample output:<br/> - <strong>ThinkPad Console Audio Control at EC reg 0x30, fw 7WHT19WW-3.6</strong> - </p> - <p> - 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 - </p> - <p> - <a href="#pagetop">Back to top of page</a> - </p> - - </div> - - <div class="section"> - - <h2 id="recommended_wifi">Recommended wifi chipsets</h2> - <p> - The following are known to work well: - </p> - <ul> - <li>mini PCI express cards using the Atheros AR9285 chipset (e.g. Atheros AR5B95) - 802.11n</li> - <li>USB dongles using the AR9271 chipset (e.g. Unex DNuA 93-F) - 802.11n</li> - <li>Any of the chipsets listed at <a href="https://h-node.org/wifi/catalogue/en/1/1/undef/undef/yes?">https://h-node.org/wifi/catalogue/en/1/1/undef/undef/yes?</a></li> - </ul> - <p> - The following was mentioned (on IRC), but it's unknown to the libreboot project if these work with linux-libre kernel (TODO: test): - </p> - <ul> - <li>ar5bhb116 ar9382 ABGN</li> - <li>[0200]: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) [168c:001c]</li> - </ul> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h2 id="supported_x60_list">List of supported ThinkPad X60s</h2> - - <p> - Native gpu initialization ('native graphics') which replaces the proprietary VGA Option ROM - ('<a href="https://en.wikipedia.org/wiki/Video_BIOS">Video BIOS</a>' or 'VBIOS'), - all known LCD panels are currently compatible: - </p> - - <p> - To find what LCD panel you have, see: <a href="../misc/#get_edid_panelname">../misc/#get_edid_panelname</a>. - </p> - - <ul> - <li>TMD-Toshiba LTD121ECHB: #</li> - <li>CMO N121X5-L06: #</li> - <li>Samsung LTN121XJ-L07: #</li> - <li>BOE-Hydis HT121X01-101: #</li> - </ul> - - <p> - You can remove an X61/X61s motherboard from the chassis and install an X60/X60s motherboard in it's place (for flashing libreboot). The chassis is mostly identical - and the motherboards are the same shape/size. - </p> - - <p> - The X60 typically comes with an Intel wifi chipset which does not 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 <b>after</b> libreboot is installed. See <a href="#recommended_wifi">#recommended_wifi</a> for replacements. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h2 id="supported_x60t_list">List of supported ThinkPad X60 Tablets</h2> - - <p> - Native gpu initialization ('native graphics') which replaces the proprietary VGA Option ROM - ('<a href="https://en.wikipedia.org/wiki/Video_BIOS">Video BIOS</a>' or 'VBIOS'). - </p> - - <p> - To find what LCD panel you have, see: <a href="../misc/#get_edid_panelname">../misc/#get_edid_panelname</a>. - </p> - - <p> - There are 5 known LCD panels for the X60 Tablet: - </p> - <ul> - <li> - <b>X60T XGA (1024x768):</b> - <ul> - <li>BOE-Hydis HV121X03-100 (works)</li> - <li>Samsung LTN121XP01 (does not work. blank screen)</li> - <li>BOE-Hydis HT12X21-351 (does not work. blank screen)</li> - </ul> - </li> - <li> - <b>X60T SXGA+ (1400x1050):</b> - <ul> - <li>BOE-Hydis HV121P01-100 (works)</li> - <li>BOE-Hydis HV121P01-101 (works)</li> - </ul> - </li> - </ul> - - <p> - Most X60Ts only have digitizer (pen), but some have finger (touch) aswell as pen; finger/multitouch doesn't work, only digitizer (pen) does. - </p> - - <p> - You can remove an X61/X61s motherboard from the chassis and install an X60/X60s motherboard in its place (for flashing libreboot). The chassis is mostly identical - and the motherboards are the same shape/size. <b>It is unknown if the same applies between the X60 Tablet and the X61 Tablet</b>. - </p> - - <p> - The X60 Tablet typically comes with an Intel wifi chipset which does not 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 <b>after</b> libreboot is installed. See <a href="#recommended_wifi">#recommended_wifi</a> for replacements. - </p> - - <p> - A user with a X60T that has digitizer+finger support, reported that they could get finger input working. They - used linuxwacom at git tag 0.25.99.2 and had the following in their xorg.conf: - </p> - -<pre> -# 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 -# -# tested with linuxwacom git 42a42b2a8636abc9e105559e5dea467163499de7 - -Section "Monitor" - Identifier "<default monitor>" - DisplaySize 245 184 -EndSection - -Section "Screen" - Identifier "Default Screen Section" - Monitor "<default monitor<" -EndSection - -Section "InputDevice" - Identifier "WTouch" - Driver "wacom" - Option "Device" "/dev/ttyS0" -# Option "DebugLevel" "12" - Option "BaudRate" "38400" - Option "Type" "touch" - Option "Touch" "on" - Option "Gesture" "on" - Option "ForceDevice" "ISDV4" -# Option "KeepShape" "on" - Option "Mode" "Absolute" - Option "RawSample" "2" -# Option "TPCButton" "off" - Option "TopX" "17" - Option "TopY" "53" - Option "BottomX" "961" - Option "BottomY" "985" -EndSection - -Section "ServerLayout" - Identifier "Default Layout" - Screen "Default Screen Section" - InputDevice "WTouch" "SendCoreEvents" -EndSection - -</pre> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h2 id="supported_t60_list">Supported T60 list</h2> - - <p> - Native gpu initialization ('native graphics') which replaces the proprietary VGA Option ROM - ('<a href="https://en.wikipedia.org/wiki/Video_BIOS">Video BIOS</a>' or 'VBIOS'). - </p> - - <p> - To find what LCD panel you have, see: <a href="../misc/#get_edid_panelname">../misc/#get_edid_panelname</a>. - </p> - - <p> - <b> - Some T60s have ATI GPUs, and all T60P laptops have ATI GPUs These are incompatible! See <a href="#t60_ati_intel">#t60_ati_intel</a> for how to remedy this. - </b> - </p> - - <p> - Tested LCD panels: <b>working(compatible)</b> - </p> - <ul> - <li>TMD-Toshiba LTD141EN9B (14.1" 1400x1050) (FRU P/N 41W1478 recommended for the inverter board)</li> - <li>Samsung LTN141P4-L02 (14.1" 1400x1050) (FRU P/N 41W1478 recommended for the inverter board)</li> - <li>LG-Philips LP150E05-A2K1 (15.1" 1400x1050) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)</li> - <li>Samsung LTN150P4-L01 (15.1" 1400x1050) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board) (not a T60 screen afaik, but it works)</li> - <li>BOE-Hydis HV150UX1-100 (15.1" 1600x1200) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)</li> - </ul> - - <div class="subsection"> - - <p> - Tested LCD panels: <b>not working yet (incompatible; see <a href="../future/#lcd_i945_incompatibility">../future/#lcd_i945_incompatibility</a>)</b> - </p> - <ul> - <li>Samsung LTN141XA-L01 (14.1" 1024x768)</li> - <li>LG-Philips LP150X09 (15.1" 1024x768)</li> - <li>Samsung LTN150XG (15.1" 1024x768)</li> - <li>LG-Philips LP150E06-A5K4 (15.1" 1400x1050) (also, not an official T60 screen)</li> - <li>Samsung LTN154X3-L0A (15.4" 1280x800)</li> - <li>IDtech IAQX10N (15.1" 2048x1536) (no display in GRUB, display in GNU+Linux is temperamental) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)</li> - <li>IDtech N150U3-L01 (15.1" 1600x1200) (no display in GRUB, display in GNU+Linux works) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)</li> - </ul> - - </div> - - <div class="subsection"> - - <p> - <u><i>The following LCD panels are <b>UNTESTED</b>. If you have one of these panels - then please submit a report!</i></u>: - </p> - <ul> - <li>CMO(IDtech?) N141XC (14.1" 1024x768)</li> - <li>BOE-Hydis HT14X14 (14.1" 1024x768)</li> - <li>TMD-Toshiba LTD141ECMB (14.1" 1024x768)</li> - <li>Boe-Hydis HT14P12 (14.1" 1400x1050) (FRU P/N 41W1478 recommended for the inverter board)</li> - <li>CMO (IDtech?) 13N7068 (15.1" 1024x768)</li> - <li>CMO (IDtech?) 13N7069 (15.1" 1024x768)</li> - <li>BOE-Hydis HV150P01-100 (15.1" 1400x1050) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)</li> - <li>BOE-Hydis HV150UX1-102 (15.1" 1600x1200) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)</li> - <li>IDtech IAQX10S (15.1" 2048x1536) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)</li> - <li>Samsung LTN154P2-L05 (42X4641 42T0329) (15.4" 1680x1050)</li> - <li>LG-Philips LP154W02-TL10 (13N7020 42T0423) (15.4" 1680x1050)</li> - <li>LG-Philips LP154WU1-TLB1 (42T0361) (15.4" 1920x1200) <b>(for T61p but it might work in T60. Unknown!)</b></li> - <li>Samsung LTN154U2-L05 (42T0408 42T0574) (15.4" 1920x1200) <b>(for T61p but it might work in T60. Unknown!)</b></li> - </ul> - - <p> - It is unknown whether the 1680x1050 (15.4") and 1920x1200 (15.4") panels use a different inverter board than the 1280x800 panels. - </p> - - <p> - The T60 typically comes with an Intel wifi chipset which does not 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 <b>after</b> libreboot is installed. See <a href="#recommended_wifi">#recommended_wifi</a> for replacements. - </p> - - </div> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h2 id="t60_ati_intel">ThinkPad T60 (ATI GPU) and ThinkPad T60 (Intel GPU) differences.</h2> - - <p> - If your T60 is a 14.1" or 15.1" model with an ATI GPU, it won't work with libreboot by default but - you can replace the motherboard with another T60 motherboard that has an Intel GPU, and then libreboot should work. - </p> - - <p> - As far as I know, 14.1" (Intel GPU) and 15.1" (Intel GPU) T60 motherboards are the same, where - 'spacers' are used on the 15.1" T60. In any case, it makes sense to find one that is guaranteed to fit in your chassis. - </p> - - <p> - There is also a 15.4" T60 with Intel GPU. - </p> - - <p> - Note: the T60<b>p</b> laptops all have ATI graphics. - The T60p laptops cannot be used with libreboot under any circumstances. - </p> - - <p> - 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):<br/><br/> - <img src="../images/t60_dev/t60_unbrick.jpg" alt="" /> - </p> - - <p> - The reason that the ATI GPU on T60 is unsupported is due to the VBIOS (Video BIOS) which is non-free. - The VBIOS for the Intel GPU on X60/T60 has been reverse engineered, and replaced with Free Software and - so will work in libreboot. - </p> - - <p> - The 'Video BIOS' is what initializes graphics. - </p> - - <p> - See: <a href="https://en.wikipedia.org/wiki/Video_BIOS">https://en.wikipedia.org/wiki/Video_BIOS</a>.<br/> - 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. - </p> - - <p> - Theoretically, the ThinkPad T60 with ATI GPU can work with libreboot and have ROM images compiled for it, however - in practise it would not be usable as a laptop because there would be no visual display at all. That being said, - such a configuration is acceptable for use in a 'headless' server setup (with serial and/or ssh console as the display). - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h2 id="macbook11">Information about the macbook1,1</h2> - - <p> - There is an Apple laptop called the macbook1,1 from 2006 which uses the same i945 chipset as the ThinkPad X60/T60. - A developer ported the <a href="#macbook21">MacBook2,1</a> to coreboot, the ROM images also work on the macbook1,1. - </p> - - <p> - You can refer to <a href="#macbook21">#macbook21</a> 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 difference. - </p> - - <p> - It is believed that all models are compatible, listed here: - </p> - <ul> - <li><a href="http://www.everymac.com/ultimate-mac-lookup/?search_keywords=MacBook1,1">http://www.everymac.com/ultimate-mac-lookup/?search_keywords=MacBook1,1</a></li> - </ul> - - <div class="subsection"> - <h3> - Compatible models - </h3> - <p> - Specifically (Order No. / Model No. / CPU): - </p> - <ul> - <li>MA255LL/A / A1181 (EMC 2092) / Core Duo T2500 <b>(tested - working)</b></li> - <li>MA254LL/A / A1181 (EMC 2092) / Core Duo T2400 <b>(tested - working)</b></li> - <li>MA472LL/A / A1181 (EMC 2092) / Core Duo T2500 (untested)</li> - </ul> - </div> - - <p> - Also of interest: <a href="../git/#config_macbook21">../git/#config_macbook21</a>. - </p> - - <p> - Unbricking: <a href="https://www.ifixit.com/Device/MacBook_Core_2_Duo">this page shows disassembly guides</a> and mono's page (see <a href="#macbook21">#macbook21</a>) - shows the location of the SPI flash chip on the motherboard. <a href="https://www.ifixit.com/Guide/MacBook+Core+2+Duo+PRAM+Battery+Replacement/529">How to remove the motherboard</a>. - </p> - - <p> - No method is yet known for flashing in GNU+Linux while the Apple firmware is running. You will need to disassemble the system and flash externally. - Reading from flash seems to work. For external flashing, refer to <a href="../install/bbb_setup.html">../install/bbb_setup.html</a>. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h2 id="macbook21">Information about the macbook2,1</h2> - - <p> - There is an Apple laptop called the macbook2,1 from late 2006 or early 2007 that uses the same i945 chipset - as the ThinkPad X60 and ThinkPad T60. A developer ported coreboot to their macbook2,1, and now libreboot can run on it. - </p> - <p> - Mono Moosbart is the person who wrote the port for macbook2,1. Referenced below are copies (up to date at the time of writing, 20140630) - of the pages that this person wrote when porting coreboot to 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. - </p> - <p> - Backups created using wget:<br/> - <b>$ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/</b><br/> - <b>$ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/coreboot/</b><br/> - Use <b>-e robots=off</b> if using this trick for other sites and the site restricts using robots.txt - </p> - - <p> - <b>Links to wget backups (and the backups themselves) of Mono's pages (see above) removed temporarily. Mono has given me permission to 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</b> - </p> - - <div class="subsection"> - <h3> - Installing GNU+Linux distributions (on Apple EFI firmware) - </h3> - <ul> - <li><a href="#">Parabola GNU+Linux installation on a macbook2,1 with Apple EFI firmware</a> (this is a copy of Mono's page, see above)</li> - </ul> - <p> - How to boot an ISO: burn it to a CD (like you would normally) and hold down the Alt/Control key while booting. - The bootloader will detect the GNU+Linux CD as 'Windows' (because Apple doesn't think GNU+Linux exists). Install it like you normally would. - When you boot up again, hold Alt/Control once more. The installation (on the HDD) will once again be seen as 'Windows'. (it's not actually Windows, - but Apple likes to think that Apple and Microsoft are all that exist.) - Now to install libreboot, follow <a href="../install/#flashrom_macbook21">../install/#flashrom_macbook21</a>. - </p> - </div> - - <div class="subsection"> - <h3> - Information about coreboot - </h3> - <ul> - <li><a href="#">Coreboot on the macbook2,1</a> (this is a copy of Mono's page, see above)</li> - </ul> - </div> - - <div class="subsection"> - <h3> - coreboot wiki page - </h3> - <ul> - <li><a href="https://www.coreboot.org/Board:apple/macbook21">https://www.coreboot.org/Board:apple/macbook21</a></li> - </ul> - </div> - - <div class="subsection"> - <h3> - Compatible models - </h3> - <p> - It is believed that all models are compatible, listed here: - </p> - <ul> - <li><a href="http://www.everymac.com/ultimate-mac-lookup/?search_keywords=MacBook2,1">http://www.everymac.com/ultimate-mac-lookup/?search_keywords=MacBook2,1</a></li> - </ul> - <p> - Specifically (Order No. / Model No. / CPU): - </p> - <ul> - <li>MA699LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T5600 <b>(tested - working)</b></li> - <li>MA701LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 <b>(tested - working)</b></li> - <li>MB061LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7200 (untested)</li> - <li>MA700LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 <b>(tested - working)</b></li> - <li>MB063LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 (works)</li> - <li>MB062LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 <b>(tested - working)</b></li> - </ul> - </div> - - <p> - Also of interest: <a href="../git/#config_macbook21">../git/#config_macbook21</a>. - </p> - - <p> - Unbricking: <a href="https://www.ifixit.com/Device/MacBook_Core_2_Duo">this page shows disassembly guides</a> and mono's page (see above) - shows the location of the SPI flash chip on the motherboard. <a href="https://www.ifixit.com/Guide/MacBook+Core+2+Duo+PRAM+Battery+Replacement/529">How to remove the motherboard</a>. - </p> - - <p> - For external flashing, refer to <a href="../install/bbb_setup.html">../install/bbb_setup.html</a>. - </p> - - <p> - You need to replace OS X with GNU+Linux before flashing libreboot. (OSX won't run at all in libreboot). - </p> - - <p> - There are some issues with this system (compared to other computers that libreboot supports): - </p> - - <p> - This is an apple laptop, so it comes with OS X: it has an Apple keyboard, which means that certain keys are missing: - insert, del, home, end, pgup, pgdown. There is also one mouse button only. Battery life is poor compared to X60/T60 (for now). - It also has other issues: for example, the Apple logo on the back is a hole, exposing the backlight, which means that it glows. You should cover it up. - </p> - - <p> - The system does get a bit hotter compared to when running the original firmware. It is certainly hotter - than an X60/T60. The heat issues have been partially fixed by the following patch (now merged in libreboot): - <a href="https://review.coreboot.org/#/c/7923/">https://review.coreboot.org/#/c/7923/</a>. - </p> - - <p> - <b> - The MacBook2,1 comes with a webcam, which does not work without proprietary software. Also, webcams are a security risk; cover it up! Or remove it. - </b> - </p> - - <p> - A user reported that they could get better response from the touchpad with the following in their xorg.conf: - </p> - -<pre> -Section "InputClass" - Identifier "Synaptics Touchpad" - Driver "synaptics" - MatchIsTouchpad "on" - MatchDevicePath "/dev/input/event*" - Driver "synaptics" -# The next two values determine how much pressure one needs -# for tapping, moving the cursor and other events. - Option "FingerLow" "10" - Option "FingerHigh" "15" -# Do not emulate mouse buttons in the touchpad corners. - Option "RTCornerButton" "0" - Option "RBCornerButton" "0" - Option "LTCornerButton" "0" - Option "LBCornerButton" "0" -# One finger tap = left-click - Option "TapButton1" "1" -# Two fingers tap = right-click - Option "TapButton2" "3" -# Three fingers tap = middle-mouse - Option "TapButton3" "2" -# Try to not count the palm of the hand landing on the touchpad -# as a tap. Not sure if helps. - Option "PalmDetect" "1" -# The following modifies how long and how fast scrolling continues -# after lifting the finger when scrolling - Option "CoastingSpeed" "20" - Option "CoastingFriction" "200" -# Smaller number means that the finger has to travel less distance -# for it to count as cursor movement. Larger number prevents cursor -# shaking. - Option "HorizHysteresis" "10" - Option "VertHysteresis" "10" -# Prevent two-finger scrolling. Very jerky movement - Option "HorizTwoFingerScroll" "0" - Option "VertTwoFingerScroll" "0" -# Use edge scrolling - Option "HorizEdgeScroll" "1" - Option "VertEdgeScroll" "1" -EndSection -</pre> - <p> - A user reported that the above is only for linux kernel 3.15 or lower. For newer kernels, - the touchpad works fine out of the box, except middle tapping. - </p> - - <p> - A user submitted a utility to enable 3-finger tap on this laptop. It's - available at <i>resources/utilities/macbook21-three-finger-tap</i> in - the libreboot git repository. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hcl/index.md b/docs/hcl/index.md new file mode 100644 index 00000000..dd8d7e9f --- /dev/null +++ b/docs/hcl/index.md @@ -0,0 +1,666 @@ +<div class="section"> + +Hardware compatibility list {#pagetop} +=========================== + +This sections relates to known hardware compatibility in libreboot. + +- [List of supported hardware](#supported_list) + - [Desktops (x86, AMD and Intel)](#supported_desktops_x86amdintel) + - [Servers/workstations](#supported_workstations_x86amd) + - [Laptops (ARM)](#supported_laptops_arm) + - [Laptops (Intel, x86)](#supported_laptops_x86intel) +- NOTES: + - [Updating the EC firmware on i945 and GM45 + (recommended)](#ecupdate) + - [How to find what EC version you have (i945/GM45)](#ecversion) +- [Recommended wifi chipsets](#recommended_wifi) + +[Back to previous index](../). + +</div> + +<div class="section"> + +List of supported hardware {#supported_list} +-------------------------- + +Libreboot supports the following systems in this release: + +### Desktops (AMD, Intel, x86) {#supported_desktops_x86amdintel} + +- [Gigabyte GA-G41M-ES2L motherboard](ga-g41m-es2l.html) +- [Intel D510MO motherboard](d510mo.html) +- [ASUS KCMA-D8 motherboard](kcma-d8.html) +- [Intel D945GCLF](d945gclf.html) +- [Apple iMac 5,2](imac52.html) + +### Servers/workstations (AMD, x86) {#supported_workstations_x86amd} + +- [ASUS KFSN4-DRE motherboard](kfsn4-dre.html) +- [ASUS KGPE-D16 motherboard](kgpe-d16.html) + +### Laptops (ARM) {#supported_laptops_arm} + +- [ASUS Chromebook C201](c201.html) + +### Laptops (Intel, x86) {#supported_laptops_x86intel} + +- [Lenovo ThinkPad X60/X60s](#supported_x60_list) +- [Lenovo ThinkPad X60 Tablet](#supported_x60t_list) +- [Lenovo ThinkPad T60](#supported_t60_list) (there are exceptions. + see link) +- [Lenovo ThinkPad X200](x200.html) +- [Lenovo ThinkPad R400](r400.html) +- [Lenovo ThinkPad T400](t400.html) +- [Lenovo ThinkPad T500](t500.html) +- [Apple MacBook1,1](#macbook11) +- [Apple MacBook2,1](#macbook21) + +\'Supported\' means that the build scripts know how to build ROM images +for these systems, and that the systems have been tested (confirmed +working). There may be exceptions; in other words, this is a list of +\'officially\' supported systems. + +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) + +</div> + +<div class="section"> + +EC update on i945 (X60, T60) and GM45 (X200, T400, T500, R400) {#ecupdate} +============================================================== + +It is recommended that you update to the latest EC firmware version. The +[EC firmware](https://libreboot.org/faq/#firmware-ec) is separate from +libreboot, so we don\'t actually provide that, but if you still have +Lenovo BIOS then you can just run the Lenovo BIOS update utility, which +will update both the BIOS and EC version. See: + +- <https://libreboot.org/docs/install/index.html#flashrom> +- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk> + +NOTE: this can only be done when you are using Lenovo BIOS. How to +update the EC firmware while running libreboot is unknown. Libreboot +only replaces the BIOS firmware, not EC. + +Updated EC firmware has several advantages e.g. bettery battery +handling. + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +How to find what EC version you have (i945/GM45) {#ecversion} +================================================ + +In GNU+Linux, you can try this:\ +**grep \'at EC\' /proc/asound/cards** + +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) + +</div> + +<div class="section"> + +Recommended wifi chipsets {#recommended_wifi} +------------------------- + +The following are known to work well: + +- mini PCI express cards using the Atheros AR9285 chipset (e.g. + Atheros AR5B95) - 802.11n +- USB dongles using the AR9271 chipset (e.g. Unex DNuA 93-F) - 802.11n +- Any of the chipsets listed at + <https://h-node.org/wifi/catalogue/en/1/1/undef/undef/yes?> + +The following was mentioned (on IRC), but it\'s unknown to the libreboot +project if these work with linux-libre kernel (TODO: test): + +- ar5bhb116 ar9382 ABGN +- \[0200\]: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter + (PCI-Express) \[168c:001c\] + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +List of supported ThinkPad X60s {#supported_x60_list} +------------------------------- + +Native gpu initialization (\'native graphics\') which replaces the +proprietary VGA Option ROM (\'[Video +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). + +- 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 +chassis is mostly identical and the motherboards are the same +shape/size. + +The X60 typically comes with an Intel wifi chipset which does not 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. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +List of supported ThinkPad X60 Tablets {#supported_x60t_list} +-------------------------------------- + +Native gpu initialization (\'native graphics\') which replaces the +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). + +There are 5 known LCD panels for the X60 Tablet: + +- **X60T XGA (1024x768):** + - BOE-Hydis HV121X03-100 (works) + - Samsung LTN121XP01 (does not work. blank screen) + - BOE-Hydis HT12X21-351 (does not work. blank screen) +- **X60T SXGA+ (1400x1050):** + - BOE-Hydis HV121P01-100 (works) + - BOE-Hydis HV121P01-101 (works) + +Most X60Ts only have digitizer (pen), but some have finger (touch) +aswell as pen; finger/multitouch doesn\'t work, only digitizer (pen) +does. + +You can remove an X61/X61s motherboard from the chassis and install an +X60/X60s motherboard in its place (for flashing libreboot). The chassis +is mostly identical and the motherboards are the same shape/size. **It +is unknown if the same applies between the X60 Tablet and the X61 +Tablet**. + +The X60 Tablet typically comes with an Intel wifi chipset which does not +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. + +A user with a X60T that has digitizer+finger support, reported that they +could get finger input working. They used linuxwacom at git tag +0.25.99.2 and had the following in their xorg.conf: + + # 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 + # + # tested with linuxwacom git 42a42b2a8636abc9e105559e5dea467163499de7 + + Section "Monitor" + Identifier "<default monitor>" + DisplaySize 245 184 + EndSection + + Section "Screen" + Identifier "Default Screen Section" + Monitor "<default monitor<" + EndSection + + Section "InputDevice" + Identifier "WTouch" + Driver "wacom" + Option "Device" "/dev/ttyS0" + # Option "DebugLevel" "12" + Option "BaudRate" "38400" + Option "Type" "touch" + Option "Touch" "on" + Option "Gesture" "on" + Option "ForceDevice" "ISDV4" + # Option "KeepShape" "on" + Option "Mode" "Absolute" + Option "RawSample" "2" + # Option "TPCButton" "off" + Option "TopX" "17" + Option "TopY" "53" + Option "BottomX" "961" + Option "BottomY" "985" + EndSection + + Section "ServerLayout" + Identifier "Default Layout" + Screen "Default Screen Section" + InputDevice "WTouch" "SendCoreEvents" + EndSection + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Supported T60 list {#supported_t60_list} +------------------ + +Native gpu initialization (\'native graphics\') which replaces the +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). + +**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 +this.** + +Tested LCD panels: **working(compatible)** + +- TMD-Toshiba LTD141EN9B (14.1\" 1400x1050) (FRU P/N 41W1478 + recommended for the inverter board) +- Samsung LTN141P4-L02 (14.1\" 1400x1050) (FRU P/N 41W1478 recommended + for the inverter board) +- LG-Philips LP150E05-A2K1 (15.1\" 1400x1050) (P/N 42T0078 FRU 42T0079 + or P/N 41W1338 recommended for the inverter board) +- Samsung LTN150P4-L01 (15.1\" 1400x1050) (P/N 42T0078 FRU 42T0079 or + P/N 41W1338 recommended for the inverter board) (not a T60 screen + afaik, but it works) +- BOE-Hydis HV150UX1-100 (15.1\" 1600x1200) (P/N 42T0078 FRU 42T0079 + or P/N 41W1338 recommended for the inverter board) + +<div class="subsection"> + +Tested LCD panels: **not working yet (incompatible; see +[../future/\#lcd\_i945\_incompatibility](../future/#lcd_i945_incompatibility))** + +- Samsung LTN141XA-L01 (14.1\" 1024x768) +- LG-Philips LP150X09 (15.1\" 1024x768) +- Samsung LTN150XG (15.1\" 1024x768) +- LG-Philips LP150E06-A5K4 (15.1\" 1400x1050) (also, not an official + T60 screen) +- Samsung LTN154X3-L0A (15.4\" 1280x800) +- IDtech IAQX10N (15.1\" 2048x1536) (no display in GRUB, display in + GNU+Linux is temperamental) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 + recommended for the inverter board) +- IDtech N150U3-L01 (15.1\" 1600x1200) (no display in GRUB, display in + GNU+Linux works) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended + for the inverter board) + +</div> + +<div class="subsection"> + +*The following LCD panels are **UNTESTED**. If you have one of these +panels then please submit a report!*: + +- CMO(IDtech?) N141XC (14.1\" 1024x768) +- BOE-Hydis HT14X14 (14.1\" 1024x768) +- TMD-Toshiba LTD141ECMB (14.1\" 1024x768) +- Boe-Hydis HT14P12 (14.1\" 1400x1050) (FRU P/N 41W1478 recommended + for the inverter board) +- CMO (IDtech?) 13N7068 (15.1\" 1024x768) +- CMO (IDtech?) 13N7069 (15.1\" 1024x768) +- BOE-Hydis HV150P01-100 (15.1\" 1400x1050) (P/N 42T0078 FRU 42T0079 + or P/N 41W1338 recommended for the inverter board) +- BOE-Hydis HV150UX1-102 (15.1\" 1600x1200) (P/N 42T0078 FRU 42T0079 + or P/N 41W1338 recommended for the inverter board) +- IDtech IAQX10S (15.1\" 2048x1536) (P/N 42T0078 FRU 42T0079 or P/N + 41W1338 recommended for the inverter board) +- Samsung LTN154P2-L05 (42X4641 42T0329) (15.4\" 1680x1050) +- LG-Philips LP154W02-TL10 (13N7020 42T0423) (15.4\" 1680x1050) +- LG-Philips LP154WU1-TLB1 (42T0361) (15.4\" 1920x1200) **(for T61p + but it might work in T60. Unknown!)** +- Samsung LTN154U2-L05 (42T0408 42T0574) (15.4\" 1920x1200) **(for + T61p but it might work in T60. Unknown!)** + +It is unknown whether the 1680x1050 (15.4\") and 1920x1200 (15.4\") +panels use a different inverter board than the 1280x800 panels. + +The T60 typically comes with an Intel wifi chipset which does not 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. + +</div> + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +ThinkPad T60 (ATI GPU) and ThinkPad T60 (Intel GPU) differences. {#t60_ati_intel} +---------------------------------------------------------------- + +If your T60 is a 14.1\" or 15.1\" model with an ATI GPU, it won\'t work +with libreboot by default but you can replace the motherboard with +another T60 motherboard that has an Intel GPU, and then libreboot should +work. + +As far as I know, 14.1\" (Intel GPU) and 15.1\" (Intel GPU) T60 +motherboards are the same, where \'spacers\' are used on the 15.1\" T60. +In any case, it makes sense to find one that is guaranteed to fit in +your chassis. + +There is also a 15.4\" T60 with Intel GPU. + +Note: the T60**p** laptops all have ATI graphics. The T60p laptops +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):\ +\ + + +The reason that the ATI GPU on T60 is unsupported is due to the VBIOS +(Video BIOS) which is non-free. The VBIOS for the Intel GPU on X60/T60 +has been reverse engineered, and replaced with Free Software and so will +work in libreboot. + +The \'Video BIOS\' is what initializes graphics. + +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. + +Theoretically, the ThinkPad T60 with ATI GPU can work with libreboot and +have ROM images compiled for it, however in practise it would not be +usable as a laptop because there would be no visual display at all. That +being said, such a configuration is acceptable for use in a \'headless\' +server setup (with serial and/or ssh console as the display). + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Information about the macbook1,1 {#macbook11} +-------------------------------- + +There is an Apple laptop called the macbook1,1 from 2006 which uses the +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 +laptops come with Core 2 Duo processors which support 64-bit operating +systems (and 32-bit). The MacBook1,1 uses Core Duo processors (supports +32-bit OS but not 64-bit), and it is believed that this is the only +difference. + +It is believed that all models are compatible, listed here: + +- <http://www.everymac.com/ultimate-mac-lookup/?search_keywords=MacBook1,1> + +<div class="subsection"> + +### Compatible models + +Specifically (Order No. / Model No. / CPU): + +- MA255LL/A / A1181 (EMC 2092) / Core Duo T2500 **(tested - working)** +- MA254LL/A / A1181 (EMC 2092) / Core Duo T2400 **(tested - working)** +- MA472LL/A / A1181 (EMC 2092) / Core Duo T2500 (untested) + +</div> + +Also of interest: +[../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 +chip on the motherboard. [How to remove the +motherboard](https://www.ifixit.com/Guide/MacBook+Core+2+Duo+PRAM+Battery+Replacement/529). + +No method is yet known for flashing in GNU+Linux while the Apple +firmware is running. You will need to disassemble the system and flash +externally. Reading from flash seems to work. For external flashing, +refer to [../install/bbb\_setup.html](../install/bbb_setup.html). + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Information about the macbook2,1 {#macbook21} +-------------------------------- + +There is an Apple laptop called the macbook2,1 from late 2006 or early +2007 that uses the same i945 chipset as the ThinkPad X60 and ThinkPad +T60. A developer ported coreboot to their macbook2,1, and now libreboot +can run on it. + +Mono Moosbart is the person who wrote the port for macbook2,1. +Referenced below are copies (up to date at the time of writing, +20140630) of the pages that this person wrote when porting coreboot to +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/**\ +**\$ wget -m -p -E -k -K -np +http://macbook.donderklumpen.de/coreboot/**\ +Use **-e robots=off** if using this trick for other sites and the site +restricts using robots.txt + +**Links to wget backups (and the backups themselves) of Mono\'s pages +(see above) removed temporarily. Mono has given me permission to +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** + +<div class="subsection"> + +### Installing GNU+Linux distributions (on Apple EFI firmware) + +- [Parabola GNU+Linux installation on a macbook2,1 with Apple EFI + firmware](#) (this is a copy of Mono\'s page, see above) + +How to boot an ISO: burn it to a CD (like you would normally) and hold +down the Alt/Control key while booting. The bootloader will detect the +GNU+Linux CD as \'Windows\' (because Apple doesn\'t think GNU+Linux +exists). Install it like you normally would. When you boot up again, +hold Alt/Control once more. The installation (on the HDD) will once +again be seen as \'Windows\'. (it\'s not actually Windows, but Apple +likes to think that Apple and Microsoft are all that exist.) Now to +install libreboot, follow +[../install/\#flashrom\_macbook21](../install/#flashrom_macbook21). + +</div> + +<div class="subsection"> + +### Information about coreboot + +- [Coreboot on the macbook2,1](#) (this is a copy of Mono\'s page, see + above) + +</div> + +<div class="subsection"> + +### coreboot wiki page + +- <https://www.coreboot.org/Board:apple/macbook21> + +</div> + +<div class="subsection"> + +### Compatible models + +It is believed that all models are compatible, listed here: + +- <http://www.everymac.com/ultimate-mac-lookup/?search_keywords=MacBook2,1> + +Specifically (Order No. / Model No. / CPU): + +- MA699LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T5600 **(tested - + working)** +- MA701LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 **(tested - + working)** +- MB061LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7200 (untested) +- MA700LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 **(tested - + working)** +- MB063LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 (works) +- MB062LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 **(tested - + working)** + +</div> + +Also of interest: +[../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 above) 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). + +For external flashing, refer to +[../install/bbb\_setup.html](../install/bbb_setup.html). + +You need to replace OS X with GNU+Linux before flashing libreboot. (OSX +won\'t run at all in libreboot). + +There are some issues with this system (compared to other computers that +libreboot supports): + +This is an apple laptop, so it comes with OS X: it has an Apple +keyboard, which means that certain keys are missing: insert, del, home, +end, pgup, pgdown. There is also one mouse button only. Battery life is +poor compared to X60/T60 (for now). It also has other issues: for +example, the Apple logo on the back is a hole, exposing the backlight, +which means that it glows. You should cover it up. + +The system does get a bit hotter compared to when running the original +firmware. It is certainly hotter than an X60/T60. The heat issues have +been partially fixed by the following patch (now merged in libreboot): +<https://review.coreboot.org/#/c/7923/>. + +**The MacBook2,1 comes with a webcam, which does not work without +proprietary software. Also, webcams are a security risk; cover it up! Or +remove it.** + +A user reported that they could get better response from the touchpad +with the following in their xorg.conf: + + Section "InputClass" + Identifier "Synaptics Touchpad" + Driver "synaptics" + MatchIsTouchpad "on" + MatchDevicePath "/dev/input/event*" + Driver "synaptics" + # The next two values determine how much pressure one needs + # for tapping, moving the cursor and other events. + Option "FingerLow" "10" + Option "FingerHigh" "15" + # Do not emulate mouse buttons in the touchpad corners. + Option "RTCornerButton" "0" + Option "RBCornerButton" "0" + Option "LTCornerButton" "0" + Option "LBCornerButton" "0" + # One finger tap = left-click + Option "TapButton1" "1" + # Two fingers tap = right-click + Option "TapButton2" "3" + # Three fingers tap = middle-mouse + Option "TapButton3" "2" + # Try to not count the palm of the hand landing on the touchpad + # as a tap. Not sure if helps. + Option "PalmDetect" "1" + # The following modifies how long and how fast scrolling continues + # after lifting the finger when scrolling + Option "CoastingSpeed" "20" + Option "CoastingFriction" "200" + # Smaller number means that the finger has to travel less distance + # for it to count as cursor movement. Larger number prevents cursor + # shaking. + Option "HorizHysteresis" "10" + Option "VertHysteresis" "10" + # Prevent two-finger scrolling. Very jerky movement + Option "HorizTwoFingerScroll" "0" + Option "VertTwoFingerScroll" "0" + # Use edge scrolling + Option "HorizEdgeScroll" "1" + Option "VertEdgeScroll" "1" + EndSection + +A user reported that the above is only for linux kernel 3.15 or lower. +For newer kernels, the touchpad works fine out of the box, except middle +tapping. + +A user submitted a utility to enable 3-finger tap on this laptop. It\'s +available at *resources/utilities/macbook21-three-finger-tap* in the +libreboot git repository. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hcl/kcma-d8.html b/docs/hcl/kcma-d8.html deleted file mode 100644 index 05b42ce9..00000000 --- a/docs/hcl/kcma-d8.html +++ /dev/null @@ -1,186 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ASUS KCMA-D8 desktop/workstation board</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">ASUS KCMA-D8 desktop/workstation board</h1> - - <p> - This is a desktop board using AMD hardware (Fam10h <b>and Fam15h</b> CPUs available). It can also be used - for building a high-powered workstation. Powered by libreboot. The coreboot port was done by - Timothy Pearson of Raptor Engineering Inc. and, - working with them, merged into libreboot. - </p> - - <p> - <b>Memory initialization is still problematic, for some modules. We recommend avoiding Kingston modules.</b> - </p> - - <p> - Flashing instructions can be found at <a href="../install/#flashrom">../install/#flashrom</a> - - 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, without using external hardware. - </p> - - <p> - <a href="./">Back to previous index</a>. - </p> - </div> - - <div class="section"> - <h1 id="cpu-compatibility">CPU compatibility</h1> - <p> - <strong>Use Opteron 4200 series (works without microcode updates, including hw virt).</strong> - 4300 series needs microcode updates, so avoid those CPUs. 4100 series is too old, and mostly untested. - </p> - </div> - - <div class="section"> - <h1 id="boardstatus">Board status (compatibility)</h1> - <p> - See <a href="https://raptorengineeringinc.com/coreboot/kcma-d8-status.php">https://raptorengineeringinc.com/coreboot/kcma-d8-status.php</a>. - </p> - </div> - - <div class="section"> - <h1 id="formfactor">Form factor</h1> - <p> - 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. - </p> - </div> - - <div class="section"> - <h1 id="ipmi">IPMI iKVM module add-on</h1> - <p> - Don't use it. It uses proprietary firmware and adds a backdoor (remote out-of-band management chip, - similar to the <a href="http://libreboot.org/faq/#intelme">Intel Management Engine</a>. Fortunately, - the firmware is 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. - </p> - </div> - - <div class="section"> - <h1 id="flashchips">Flash chips</h1> - <p> - 2MiB flash chips are included by default, on these boards. It's on a P-DIP 8 slot (SPI chip). - The flash chip can be upgraded to higher sizes: 4MiB, 8MiB or 16MiB. With at least 8MiB, - you could feasibly fit a compressed linux+initramfs image (BusyBox+Linux system) into CBFS - and boot that, loading it into memory. - </p> - <p> - Libreboot has configs for 2, 4, 8 and 16 MiB flash chip sizes (default flash chip is 2MiB). - </p> - <p> - <b> - DO NOT hot-swap the chip with your bare hands. Use a P-DIP 8 - chip extractor. These can be found online. - See <a href="http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools">http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools</a> - </b> - </p> - </div> - - <div class="section"> - <h1 id="graphics">Native graphics initialization</h1> - <p> - Only text-mode is known to work, but linux(kernel) can initialize - the framebuffer display (if it has KMS - kernel mode setting). - </p> - </div> - - <div class="section"> - <h1 id="issues">Current issues</h1> - <ul> - <li>LRDIMM memory modules are currently incompatible</li> - <li> - SAS (via PIKE 2008 module) requires non-free option ROM (and SeaBIOS) to boot from it - (theoretically possible to replace, but you can put a kernel in CBFS or on SATA - and use that to boot GNU, which can be on a SAS drive. The linux kernel can use - those SAS drives (via PIKE module) without an option ROM). - </li> - <li> - IPMI iKVM module (optional add-on card) uses proprietary firmware. Since it's for - remote out-of-band management, it's theoretically a backdoor similar to the Intel - Management Engine. Fortunately, unlike the ME, this firmware is unsigned which - means that a free replacement is theoretically possible. For now, the libreboot project - recommends not installing the module. <a href="https://github.com/facebook/openbmc">This project</a> - might be interesting 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). - </li> - <li>Graphics: only text-mode works. See <a href="#graphics">#graphics</a></li> - </ul> - </div> - - <div class="section"> - <h2 id="specifications">Hardware specifications</h2> - <p> - Check the ASUS website. - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> - diff --git a/docs/hcl/kcma-d8.md b/docs/hcl/kcma-d8.md new file mode 100644 index 00000000..0e57a659 --- /dev/null +++ b/docs/hcl/kcma-d8.md @@ -0,0 +1,170 @@ +<div class="section"> + +ASUS KCMA-D8 desktop/workstation board {#pagetop} +====================================== + +This is a desktop board using AMD hardware (Fam10h **and Fam15h** CPUs +available). It can also be used for building a high-powered workstation. +Powered by libreboot. The coreboot port was done by Timothy Pearson of +Raptor Engineering Inc. and, working with them, merged into libreboot. + +**Memory initialization is still problematic, for some modules. We +recommend avoiding Kingston modules.** + +Flashing instructions can be found at +[../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, +without using external hardware. + +[Back to previous index](./). + +</div> + +<div class="section"> + +CPU compatibility +================= + +**Use Opteron 4200 series (works without microcode updates, including hw +virt).** 4300 series needs microcode updates, so avoid those CPUs. 4100 +series is too old, and mostly untested. + +</div> + +<div class="section"> + +Board status (compatibility) {#boardstatus} +============================ + +See <https://raptorengineeringinc.com/coreboot/kcma-d8-status.php>. + +</div> + +<div class="section"> + +Form factor {#formfactor} +=========== + +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. + +</div> + +<div class="section"> + +IPMI iKVM module add-on {#ipmi} +======================= + +Don\'t use it. It uses proprietary firmware and adds a backdoor (remote +out-of-band management chip, similar to the [Intel Management +Engine](http://libreboot.org/faq/#intelme). Fortunately, the firmware is +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. + +</div> + +<div class="section"> + +Flash chips {#flashchips} +=========== + +2MiB flash chips are included by default, on these boards. It\'s on a +P-DIP 8 slot (SPI chip). The flash chip can be upgraded to higher sizes: +4MiB, 8MiB or 16MiB. With at least 8MiB, you could feasibly fit a +compressed linux+initramfs image (BusyBox+Linux system) into CBFS and +boot that, loading it into memory. + +Libreboot has configs for 2, 4, 8 and 16 MiB flash chip sizes (default +flash chip is 2MiB). + +**DO NOT hot-swap the chip with your bare hands. Use a P-DIP 8 chip +extractor. These can be found online. See +<http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + +</div> + +<div class="section"> + +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). + +</div> + +<div class="section"> + +Current issues {#issues} +============== + +- LRDIMM memory modules are currently incompatible +- SAS (via PIKE 2008 module) requires non-free option ROM (and + SeaBIOS) to boot from it (theoretically possible to replace, but you + can put a kernel in CBFS or on SATA and use that to boot GNU, which + can be on a SAS drive. The linux kernel can use those SAS drives + (via PIKE module) without an option ROM). +- IPMI iKVM module (optional add-on card) uses proprietary firmware. + Since it\'s for remote out-of-band management, it\'s theoretically a + backdoor similar to the Intel Management Engine. Fortunately, unlike + the ME, this firmware is unsigned which means that a free + replacement is theoretically possible. For now, the libreboot + project recommends not installing the module. [This + project](https://github.com/facebook/openbmc) might be interesting + 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) + +</div> + +<div class="section"> + +Hardware specifications {#specifications} +----------------------- + +Check the ASUS website. + +</div> + +<div class="section"> + +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. + +</div> diff --git a/docs/hcl/kfsn4-dre.html b/docs/hcl/kfsn4-dre.html deleted file mode 100644 index 17ad8d31..00000000 --- a/docs/hcl/kfsn4-dre.html +++ /dev/null @@ -1,164 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ASUS KFSN4-DRE server/workstation board</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">ASUS KFSN4-DRE server/workstation board</h1> - - <p> - This is a server board using AMD hardware (Fam10h). It can also be used - for building a high-powered workstation. Powered by libreboot. - </p> - - <p> - Flashing instructions can be found at <a href="../install/#flashrom">../install/#flashrom</a> - </p> - - <p> - <a href="./">Back to previous index</a>. - </p> - </div> - - <div class="section"> - <h1 id="formfactor">Form factor</h1> - <p> - 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. - </p> - </div> - - <div class="section"> - <h1 id="flashchips">Flash chips</h1> - <p> - These boards use LPC flash (not SPI), in a PLCC socket. The default flash size - 1MiB (8Mbits), and can be upgraded to 2MiB (16Mbits). - SST49LF080A is the default that the board uses. - SST49LF016C is an example of a 2MiB (16Mbits) chip, which might work. - It is believed that 2MiB (16Mbits) is the maximum size available for the flash chip. - </p> - <p> - <b> - DO NOT hot-swap the chip with your bare hands. Use a PLCC - chip extractor. These can be found online. - See <a href="http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools">http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools</a> - </b> - </p> - </div> - - <div class="section"> - <h1 id="graphics">Native graphics initialization</h1> - <p> - Native graphics initialization exists (XGI Z9s) for this board. - Framebuffer- and text-mode both work. A serial port is also - available. - </p> - </div> - - <div class="section"> - <h1>Memory</h1> - <p> - DDR2 533/667 Registered ECC. 16 slots. Total capacity up to 64GiB. - </p> - </div> - - <div class="section"> - <h1 id="hexcore">Hex-core CPUs</h1> - <p> - PCB revision 1.05G is the best version of this board (the - revision 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. - </p> - </div> - - <div class="section"> - <h1 id="issues">Current issues</h1> - <ul> - <li> - There seems to be a 30 second bootblock delay (observed by tpearson); - the system otherwise boots and works as expected. - See <a href="text/kfsn4-dre/bootlog.txt">text/kfsn4-dre/bootlog.txt</a> - - this uses the 'simple' bootblock, while tpearson uses the 'normal' - bootblock, which tpearson suspects may be a possible cause. - This person says that they will look into it. - <a href="http://review.coreboot.org/gitweb?p=board-status.git;a=blob;f=asus/kfsn4-dre/4.0-10101-g039edeb/2015-06-27T03:59:16Z/config.txt;h=4742905c185a93fbda8eb14322dd82c70641aef0;hb=055f5df4e000a97453dfad6c91c2d06ea22b8545">This config</a> doesn't have the issue. - </li> - <li> - Text-mode is a bit jittery (but still usable). (the jitter disappears - if using KMS, once the kernel starts. The jitter will remain, if - booting the kernel in text-mode). - </li> - </ul> - </div> - - <div class="section"> - <h1>Other information</h1> - <p> - <a href="ftp://ftp.sgi.com/public/Technical%20Support/Pdf%20files/Asus/kfsn4-dre.pdf">specifications</a> - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> - diff --git a/docs/hcl/kfsn4-dre.md b/docs/hcl/kfsn4-dre.md new file mode 100644 index 00000000..5f195ac9 --- /dev/null +++ b/docs/hcl/kfsn4-dre.md @@ -0,0 +1,139 @@ +<div class="section"> + +ASUS KFSN4-DRE server/workstation board {#pagetop} +======================================= + +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) + +[Back to previous index](./). + +</div> + +<div class="section"> + +Form factor {#formfactor} +=========== + +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. + +</div> + +<div class="section"> + +Flash chips {#flashchips} +=========== + +These boards use LPC flash (not SPI), in a PLCC socket. The default +flash size 1MiB (8Mbits), and can be upgraded to 2MiB (16Mbits). +SST49LF080A is the default that the board uses. SST49LF016C is an +example of a 2MiB (16Mbits) chip, which might work. It is believed that +2MiB (16Mbits) is the maximum size available for the flash chip. + +**DO NOT hot-swap the chip with your bare hands. Use a PLCC chip +extractor. These can be found online. See +<http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + +</div> + +<div class="section"> + +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. + +</div> + +<div class="section"> + +Memory +====== + +DDR2 533/667 Registered ECC. 16 slots. Total capacity up to 64GiB. + +</div> + +<div class="section"> + +Hex-core CPUs {#hexcore} +============= + +PCB revision 1.05G is the best version of this board (the revision +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. + +</div> + +<div class="section"> + +Current issues {#issues} +============== + +- There seems to be a 30 second bootblock delay (observed by + tpearson); the system otherwise boots and works as expected. See + [text/kfsn4-dre/bootlog.txt](text/kfsn4-dre/bootlog.txt) - this uses + the \'simple\' bootblock, while tpearson uses the \'normal\' + bootblock, which tpearson suspects may be a possible cause. This + person says that they will look into it. [This + config](http://review.coreboot.org/gitweb?p=board-status.git;a=blob;f=asus/kfsn4-dre/4.0-10101-g039edeb/2015-06-27T03:59:16Z/config.txt;h=4742905c185a93fbda8eb14322dd82c70641aef0;hb=055f5df4e000a97453dfad6c91c2d06ea22b8545) + doesn\'t have the issue. +- Text-mode is a bit jittery (but still usable). (the jitter + disappears if using KMS, once the kernel starts. The jitter will + remain, if booting the kernel in text-mode). + +</div> + +<div class="section"> + +Other information +================= + +[specifications](ftp://ftp.sgi.com/public/Technical%20Support/Pdf%20files/Asus/kfsn4-dre.pdf) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hcl/kgpe-d16.html b/docs/hcl/kgpe-d16.html deleted file mode 100644 index a1fdac40..00000000 --- a/docs/hcl/kgpe-d16.html +++ /dev/null @@ -1,310 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ASUS KGPE-D16 server/workstation board</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">ASUS KGPE-D16 server/workstation board</h1> - - <p> - This is a server board using AMD hardware (Fam10h <b>and Fam15h</b> CPUs available). It can also be used - for building a high-powered workstation. Powered by libreboot. The coreboot port was done by - Timothy Pearson of Raptor Engineering Inc. and, - working with them (and sponsoring the work), merged into libreboot. - </p> - - - <p> - <b>Memory initialization is still problematic, for some modules. We recommend avoiding Kingston modules.</b> - </p> - - <p> - Flashing instructions can be found at <a href="../install/#flashrom">../install/#flashrom</a> - - 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 KGPE-D16, without using external hardware. - </p> - - <p> - <a href="./">Back to previous index</a>. - </p> - </div> - - <div class="section"> - <h1 id="cpu-compatibility">CPU compatibility</h1> - <p> - <strong>Use Opteron 6200 series (works without microcode updates, including hw virt).</strong> - 6300 series needs microcode updates, so avoid those CPUs. 6100 series is too old, and mostly untested. - </p> - </div> - - <div class="section"> - <h1 id="boardstatus">Board status (compatibility)</h1> - <p> - See <a href="https://raptorengineeringinc.com/coreboot/kgpe-d16-status.php">https://raptorengineeringinc.com/coreboot/kgpe-d16-status.php</a>. - </p> - </div> - - <div class="section"> - <h1 id="formfactor">Form factor</h1> - <p> - 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. - </p> - </div> - - <div class="section"> - <h1 id="ipmi">IPMI iKVM module add-on</h1> - <p> - Don't use it. It uses proprietary firmware and adds a backdoor (remote out-of-band management chip, - similar to the <a href="http://libreboot.org/faq/#intelme">Intel Management Engine</a>. Fortunately, - the firmware is 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. - </p> - </div> - - <div class="section"> - <h1 id="flashchips">Flash chips</h1> - <p> - 2MiB flash chips are included by default, on these boards. It's on a P-DIP 8 slot (SPI chip). - The flash chip can be upgraded to higher sizes: 4MiB, 8MiB or 16MiB. With at least 8MiB, - you could feasibly fit a compressed linux+initramfs image (BusyBox+Linux system) into CBFS - and boot that, loading it into memory. - </p> - <p> - Libreboot has configs for 2, 4, 8 and 16 MiB flash chip sizes (default flash chip is 2MiB). - </p> - <p> - <b> - DO NOT hot-swap the chip with your bare hands. Use a P-DIP 8 - chip extractor. These can be found online. - See <a href="http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools">http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools</a> - </b> - </p> - </div> - - <div class="section"> - <h1 id="graphics">Native graphics initialization</h1> - <p> - Only text-mode is known to work, but linux(kernel) can initialize - the framebuffer display (if it has KMS - kernel mode setting). - </p> - </div> - - <div class="section"> - <h1 id="issues">Current issues</h1> - <ul> - <li>LRDIMM memory modules are currently incompatible</li> - <li> - SAS (via PIKE 2008 module) requires non-free option ROM (and SeaBIOS) to boot from it - (theoretically possible to replace, but you can put a kernel in CBFS or on SATA - and use that to boot GNU, which can be on a SAS drive. The linux kernel can use - those SAS drives (via PIKE module) without an option ROM). - </li> - <li> - IPMI iKVM module (optional add-on card) uses proprietary firmware. Since it's for - remote out-of-band management, it's theoretically a backdoor similar to the Intel - Management Engine. Fortunately, unlike the ME, this firmware is unsigned which - means that a free replacement is theoretically possible. For now, the libreboot project - recommends not installing the module. <a href="https://github.com/facebook/openbmc">This project</a> - might be interesting 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). - </li> - <li>Graphics: only text-mode works. See <a href="#graphics">#graphics</a></li> - </ul> - </div> - - <div class="section"> - <h2 id="specifications">Hardware specifications</h2> - <p> - The information here is adapted, from the ASUS website. - </p> - <h3>Processor / system bus</h3> - <ul> - <li>2 CPU sockets (G34 compatible)</li> - <li>HyperTransport™ Technology 3.0</li> - <li> - CPUs supported: - <ul> - <li>AMD Opteron 6100 series (Fam10h. No IOMMU support. <b>Not</b> recommended - old. View errata datasheet here: <a href="http://support.amd.com/TechDocs/41322_10h_Rev_Gd.pdf">http://support.amd.com/TechDocs/41322_10h_Rev_Gd.pdf</a>)</li> - <li>AMD Opteron 6200 series (Fam15h, with full IOMMU support in libreboot - <strong>highly recommended - fast, and works well without microcode updates, including virtualization</strong>)</li> - <li>AMD Opteron 6300 series (Fam15h, with full IOMMU support in libreboot. <b>AVOID LIKE THE PLAGUE - virtualization is broken without microcode updates.</b></li> - <li> - NOTE: 6300 series CPUs have buggy microcode built-in, and libreboot recommends avoiding the updates. The 6200 series CPUs have more reliable microcode. - Look at this errata datasheet: <a href="http://support.amd.com/TechDocs/48063_15h_Mod_00h-0Fh_Rev_Guide.pdf">http://support.amd.com/TechDocs/48063_15h_Mod_00h-0Fh_Rev_Guide.pdf</a> - (see Errata 734 - this is what kills the 6300 series) - </li> - </ul> - </li> - <li>6.4 GT/s per link (triple link)</li> - </ul> - <h3>Core logic</h3> - <ul> - <li>AMD SR5690</li> - <li>AMD SP5100</li> - </ul> - <h3>Memory compatibility (with libreboot)</h3> - <ul> - <li><b>Total Slots:</b> 16 (4-channel per CPU, 8 DIMM per CPU), ECC</li> - <li><b>Capacity:</b> Maximum up to 256GB RDIMM</li> - <li> - <b>Memory Type that is compatible:</b> - <ul> - <li>DDR3 1600/1333/1066/800 UDIMM*</li> - <li>DDR3 1600/1333/1066/800 RDIMM*</li> - </ul> - </li> - <li> - <b>Compatible sizes per memory module:</b> - <ul> - <li>16GB, 8GB, 4GB, 3GB, 2GB, 1GB RDIMM</li> - <li>8GB, 4GB, 2GB, 1GB UDIMM</li> - </ul> - </li> - </ul> - <h3>Expansion slots</h3> - <ul> - <li><b>Total slot:</b> 6</li> - <li><b>Slot Location 1:</b> PCI 32bit/33MHz</li> - <li><b>Slot Location 2:</b> PCI-E x16 (Gen2 X8 Link)</li> - <li><b>Slot Location 3:</b> PCI-E x16 (Gen2 X16 Link), Auto switch to x8 link if slot 2 is occupied</li> - <li><b>Slot Location 4:</b> PCI-E x8 (Gen2 X4 Link)</li> - <li><b>Slot Location 5:</b> PCI-E x16 (Gen2 X16 Link)</li> - <li><b>Slot Location 6:</b> PCI-E x16 (Gen2 X16 Link), Auto turn off if slot 5 is occupied, For 1U FH/FL Card, MIO supported</li> - <li><b>Additional Slot 1:</b> PIKE slot (for SAS drives. See notes above)</li> - <li>Follow SSI Location#</li> - </ul> - <h3>Form factor</h3> - <ul> - <li>SSI EEB 3.61 (12"x13")</li> - </ul> - <h3>ASUS features</h3> - <ul> - <li>Fan Speed Control</li> - <li>Rack Ready (Rack and Pedestal dual use)</li> - </ul> - <h3>Storage</h3> - <ul> - <li> - <b>SATA controller:</b> - <ul> - <li>AMD SP5100</li> - <li>6 x SATA2 300MB/s</li> - </ul> - </li> - <li> - <b>SAS/SATA Controller:</b> - <ul> - <li>ASUS PIKE2008 3Gbps 8-port SAS card included</li> - </ul> - </li> - </ul> - <h3>Networking</h3> - <ul> - <li>2 x Intel® 82574L + 1 x Mgmt LAN</li> - </ul> - <h3>Graphics</h3> - <ul> - <li>Aspeed AST2050 with 8MB VRAM</li> - </ul> - <h3>On board I/O</h3> - <ul> - <li>1 x PSU Power Connector (24-pin SSI power connector + 8-pin SSI 12V + 8-pin SSI 12V power connector)</li> - <li>1 x Management Connector , Onboard socket for management card</li> - <li>3 x USB pin header , Up to 6 Devices</li> - <li>1 x Internal A Type USB Port</li> - <li>8 x Fan Header , 4pin (3pin/4pin fan dual support)</li> - <li>2 x SMBus</li> - <li>1 x Serial Port Header</li> - <li>1 x TPM header</li> - <li>1 x PS/2 KB/MS port</li> - </ul> - <h3>Back I/O ports</h3> - <ul> - <li>1 x External Serial Port</li> - <li>2 x External USB Port</li> - <li>1 x VGA Port</li> - <li>2 x RJ-45</li> - <li>1 x PS/2 KB/Mouse</li> - </ul> - <h3>Environment</h3> - <ul> - <li><b>Operation temperature:</b> 10C ~ 35C</li> - <li><b>Non operation temperature:</b> -40C ~ 70C</li> - <li><b>Non operation humidity:</b> 20% ~ 90% ( Non condensing)</li> - </ul> - <h3>Monitoring</h3> - <ul> - <li>CPU temperatures</li> - <li>Fan speed (RPM)</li> - </ul> - <h3>Note:</h3> - <ul> - <li>* DDR3 1600 can only be supported with AMD Opteron 6300/6200 series processor</li> - </ul> - </div> - - <div class="section"> - - <p> - Copyright © 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> - diff --git a/docs/hcl/kgpe-d16.md b/docs/hcl/kgpe-d16.md new file mode 100644 index 00000000..1764026c --- /dev/null +++ b/docs/hcl/kgpe-d16.md @@ -0,0 +1,284 @@ +<div class="section"> + +ASUS KGPE-D16 server/workstation board {#pagetop} +====================================== + +This is a server board using AMD hardware (Fam10h **and Fam15h** CPUs +available). It can also be used for building a high-powered workstation. +Powered by libreboot. The coreboot port was done by Timothy Pearson of +Raptor Engineering Inc. and, working with them (and sponsoring the +work), merged into libreboot. + +**Memory initialization is still problematic, for some modules. We +recommend avoiding Kingston modules.** + +Flashing instructions can be found at +[../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 +KGPE-D16, without using external hardware. + +[Back to previous index](./). + +</div> + +<div class="section"> + +CPU compatibility +================= + +**Use Opteron 6200 series (works without microcode updates, including hw +virt).** 6300 series needs microcode updates, so avoid those CPUs. 6100 +series is too old, and mostly untested. + +</div> + +<div class="section"> + +Board status (compatibility) {#boardstatus} +============================ + +See <https://raptorengineeringinc.com/coreboot/kgpe-d16-status.php>. + +</div> + +<div class="section"> + +Form factor {#formfactor} +=========== + +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. + +</div> + +<div class="section"> + +IPMI iKVM module add-on {#ipmi} +======================= + +Don\'t use it. It uses proprietary firmware and adds a backdoor (remote +out-of-band management chip, similar to the [Intel Management +Engine](http://libreboot.org/faq/#intelme). Fortunately, the firmware is +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. + +</div> + +<div class="section"> + +Flash chips {#flashchips} +=========== + +2MiB flash chips are included by default, on these boards. It\'s on a +P-DIP 8 slot (SPI chip). The flash chip can be upgraded to higher sizes: +4MiB, 8MiB or 16MiB. With at least 8MiB, you could feasibly fit a +compressed linux+initramfs image (BusyBox+Linux system) into CBFS and +boot that, loading it into memory. + +Libreboot has configs for 2, 4, 8 and 16 MiB flash chip sizes (default +flash chip is 2MiB). + +**DO NOT hot-swap the chip with your bare hands. Use a P-DIP 8 chip +extractor. These can be found online. See +<http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + +</div> + +<div class="section"> + +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). + +</div> + +<div class="section"> + +Current issues {#issues} +============== + +- LRDIMM memory modules are currently incompatible +- SAS (via PIKE 2008 module) requires non-free option ROM (and + SeaBIOS) to boot from it (theoretically possible to replace, but you + can put a kernel in CBFS or on SATA and use that to boot GNU, which + can be on a SAS drive. The linux kernel can use those SAS drives + (via PIKE module) without an option ROM). +- IPMI iKVM module (optional add-on card) uses proprietary firmware. + Since it\'s for remote out-of-band management, it\'s theoretically a + backdoor similar to the Intel Management Engine. Fortunately, unlike + the ME, this firmware is unsigned which means that a free + replacement is theoretically possible. For now, the libreboot + project recommends not installing the module. [This + project](https://github.com/facebook/openbmc) might be interesting + 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) + +</div> + +<div class="section"> + +Hardware specifications {#specifications} +----------------------- + +The information here is adapted, from the ASUS website. + +### Processor / system bus + +- 2 CPU sockets (G34 compatible) +- HyperTransport™ Technology 3.0 +- CPUs supported: + - AMD Opteron 6100 series (Fam10h. No IOMMU support. **Not** + recommended - old. View errata datasheet here: + <http://support.amd.com/TechDocs/41322_10h_Rev_Gd.pdf>) + - AMD Opteron 6200 series (Fam15h, with full IOMMU support in + libreboot - **highly recommended - fast, and works well without + microcode updates, including virtualization**) + - AMD Opteron 6300 series (Fam15h, with full IOMMU support in + libreboot. **AVOID LIKE THE PLAGUE - virtualization is broken + without microcode updates.** + - NOTE: 6300 series CPUs have buggy microcode built-in, and + libreboot recommends avoiding the updates. The 6200 series CPUs + have more reliable microcode. Look at this errata datasheet: + <http://support.amd.com/TechDocs/48063_15h_Mod_00h-0Fh_Rev_Guide.pdf> + (see Errata 734 - this is what kills the 6300 series) +- 6.4 GT/s per link (triple link) + +### Core logic + +- AMD SR5690 +- AMD SP5100 + +### Memory compatibility (with libreboot) + +- **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\* +- **Compatible sizes per memory module:** + - 16GB, 8GB, 4GB, 3GB, 2GB, 1GB RDIMM + - 8GB, 4GB, 2GB, 1GB UDIMM + +### Expansion slots + +- **Total slot:** 6 +- **Slot Location 1:** PCI 32bit/33MHz +- **Slot Location 2:** PCI-E x16 (Gen2 X8 Link) +- **Slot Location 3:** PCI-E x16 (Gen2 X16 Link), Auto switch to x8 + link if slot 2 is occupied +- **Slot Location 4:** PCI-E x8 (Gen2 X4 Link) +- **Slot Location 5:** PCI-E x16 (Gen2 X16 Link) +- **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\# + +### Form factor {#form-factor} + +- SSI EEB 3.61 (12\"x13\") + +### ASUS features + +- Fan Speed Control +- Rack Ready (Rack and Pedestal dual use) + +### Storage + +- **SATA controller:** + - AMD SP5100 + - 6 x SATA2 300MB/s +- **SAS/SATA Controller:** + - ASUS PIKE2008 3Gbps 8-port SAS card included + +### Networking + +- 2 x Intel® 82574L + 1 x Mgmt LAN + +### Graphics + +- Aspeed AST2050 with 8MB VRAM + +### On board I/O + +- 1 x PSU Power Connector (24-pin SSI power connector + 8-pin SSI + 12V + 8-pin SSI 12V power connector) +- 1 x Management Connector , Onboard socket for management card +- 3 x USB pin header , Up to 6 Devices +- 1 x Internal A Type USB Port +- 8 x Fan Header , 4pin (3pin/4pin fan dual support) +- 2 x SMBus +- 1 x Serial Port Header +- 1 x TPM header +- 1 x PS/2 KB/MS port + +### Back I/O ports + +- 1 x External Serial Port +- 2 x External USB Port +- 1 x VGA Port +- 2 x RJ-45 +- 1 x PS/2 KB/Mouse + +### Environment + +- **Operation temperature:** 10C \~ 35C +- **Non operation temperature:** -40C \~ 70C +- **Non operation humidity:** 20% \~ 90% ( Non condensing) + +### Monitoring + +- CPU temperatures +- Fan speed (RPM) + +### Note: + +- \* DDR3 1600 can only be supported with AMD Opteron 6300/6200 series + processor + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hcl/r400.html b/docs/hcl/r400.html deleted file mode 100644 index cf948209..00000000 --- a/docs/hcl/r400.html +++ /dev/null @@ -1,158 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad R400</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">ThinkPad R400</h1> - - <p> - It is believed that all or most R400 laptops are compatible. - See notes about <a href="../install/r400_external.html#cpu_compatibility">CPU compatibility</a> for - potential incompatibilities. - </p> - - <p> - There are two possible flash chip sizes for the R400: 4MiB (32Mbit) or 8MiB (64Mbit). - This can be identified by the type of flash chip below the palmrest: 4MiB is SOIC-8, 8MiB - is SOIC-16. - </p> - - <p> - <b>The R400 laptops come with the ME (and sometimes AMT in addition) before flashing libreboot. Libreboot disables and removes it - by using a modified descriptor: see <a href="gm45_remove_me.html">gm45_remove_me.html</a></b> (contains notes, plus - instructions) - </p> - - <p> - Flashing instructions can be found at <a href="../install/#flashrom">../install/#flashrom</a> - </p> - - <p> - <a href="./">Back to previous index</a>. - </p> - </div> - - <div class="section"> - - <h1 id="ecupdate">EC update</h1> - - <p> - It is recommended that you update to the latest EC firmware version. - The <a href="https://libreboot.org/faq/#firmware-ec">EC firmware</a> - is separate from libreboot, so we don't actually provide that, but - if you still have Lenovo BIOS then you can just run the Lenovo BIOS - update utility, which will update both the BIOS and EC version. - See: - </p> - <ul> - <li><a href="https://libreboot.org/docs/install/index.html#flashrom">https://libreboot.org/docs/install/index.html#flashrom</a></li> - <li><a href="http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk">http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk</a></li> - </ul> - <p> - NOTE: this can only be done when you are using Lenovo BIOS. How to - update the EC firmware while running libreboot is unknown. - Libreboot only replaces the BIOS firmware, not EC. - </p> - <p> - Updated EC firmware has several advantages e.g. - bettery battery handling. - </p> - - </div> - <div class="section"> - - <h2 id="compatibility_noblobs">Compatibility (without blobs)</h2> - - <div class="subsection"> - <h3 id="hwvirt">Hardware virtualization (vt-x)</h3> - <p> - The R400, when run without CPU microcode updates in coreboot, currently kernel panics - if running QEMU with vt-x enabled on 2 cores for the guest. With a single core enabled - for the guest, the guest panics (but the host is fine). Working around this in QEMU - might be possible; if not, software virtualization should work fine (it's just slower). - </p> - <p> - On GM45 hardware (with libreboot), make sure that the <i>kvm</i> and <i>kvm_intel</i> kernel modules - are not loaded, when using QEMU. - </p> - <p> - The following errata datasheet from Intel might help with investigation: - <a href="http://download.intel.com/design/mobile/specupdt/320121.pdf">http://download.intel.com/design/mobile/specupdt/320121.pdf</a> - </p> - </div> - - </div> - - <div class="section"> - - <p> - The R400 is almost identical to the X200, code-wise. See <a href="x200.html">x200.html</a>. - </p> - - <p> - TODO: put hardware register logs here like on the <a href="x200.html">X200</a> and <a href="t400.html">T400</a> page. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hcl/r400.md b/docs/hcl/r400.md new file mode 100644 index 00000000..51afdfdc --- /dev/null +++ b/docs/hcl/r400.md @@ -0,0 +1,121 @@ +<div class="section"> + +ThinkPad R400 {#pagetop} +============= + +It is believed that all or most R400 laptops are compatible. See notes +about [CPU +compatibility](../install/r400_external.html#cpu_compatibility) for +potential incompatibilities. + +There are two possible flash chip sizes for the R400: 4MiB (32Mbit) or +8MiB (64Mbit). This can be identified by the type of flash chip below +the palmrest: 4MiB is SOIC-8, 8MiB is SOIC-16. + +**The R400 laptops come with the ME (and sometimes AMT in addition) +before flashing libreboot. Libreboot disables and removes it by using a +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) + +[Back to previous index](./). + +</div> + +<div class="section"> + +EC update {#ecupdate} +========= + +It is recommended that you update to the latest EC firmware version. The +[EC firmware](https://libreboot.org/faq/#firmware-ec) is separate from +libreboot, so we don\'t actually provide that, but if you still have +Lenovo BIOS then you can just run the Lenovo BIOS update utility, which +will update both the BIOS and EC version. See: + +- <https://libreboot.org/docs/install/index.html#flashrom> +- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk> + +NOTE: this can only be done when you are using Lenovo BIOS. How to +update the EC firmware while running libreboot is unknown. Libreboot +only replaces the BIOS firmware, not EC. + +Updated EC firmware has several advantages e.g. bettery battery +handling. + +</div> + +<div class="section"> + +Compatibility (without blobs) {#compatibility_noblobs} +----------------------------- + +<div class="subsection"> + +### Hardware virtualization (vt-x) {#hwvirt} + +The R400, when run without CPU microcode updates in coreboot, currently +kernel panics if running QEMU with vt-x enabled on 2 cores for the +guest. With a single core enabled for the guest, the guest panics (but +the host is fine). Working around this in QEMU might be possible; if +not, software virtualization should work fine (it\'s just slower). + +On GM45 hardware (with libreboot), make sure that the *kvm* and +*kvm\_intel* kernel modules are not loaded, when using QEMU. + +The following errata datasheet from Intel might help with investigation: +<http://download.intel.com/design/mobile/specupdt/320121.pdf> + +</div> + +</div> + +<div class="section"> + +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. + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hcl/t400.html b/docs/hcl/t400.html deleted file mode 100644 index 56dfea24..00000000 --- a/docs/hcl/t400.html +++ /dev/null @@ -1,179 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad T400</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">ThinkPad T400</h1> - - <p> - It is believed that all or most T400 laptops are compatible. - See notes about <a href="../install/t400_external.html#cpu_compatibility">CPU compatibility</a> - for potential incompatibilities. - </p> - - <p> - There are two possible flash chip sizes for the T400: 4MiB (32Mbit) or 8MiB (64Mbit). - This can be identified by the type of flash chip below the palmrest: 4MiB is SOIC-8, 8MiB - is SOIC-16. - </p> - - <p> - <b>The T400 laptops come with the ME (and sometimes AMT in addition) before flashing libreboot. Libreboot disables and removes it - by using a modified descriptor: see <a href="gm45_remove_me.html">gm45_remove_me.html</a></b> (contains notes, plus - instructions) - </p> - - <p> - Flashing instructions can be found at <a href="../install/#flashrom">../install/#flashrom</a> - </p> - - <p> - <a href="./">Back to previous index</a>. - </p> - </div> - - <div class="section"> - - <h1 id="ecupdate">EC update</h1> - - <p> - It is recommended that you update to the latest EC firmware version. - The <a href="https://libreboot.org/faq/#firmware-ec">EC firmware</a> - is separate from libreboot, so we don't actually provide that, but - if you still have Lenovo BIOS then you can just run the Lenovo BIOS - update utility, which will update both the BIOS and EC version. - See: - </p> - <ul> - <li><a href="https://libreboot.org/docs/install/index.html#flashrom">https://libreboot.org/docs/install/index.html#flashrom</a></li> - <li><a href="http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk">http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk</a></li> - </ul> - <p> - NOTE: this can only be done when you are using Lenovo BIOS. How to - update the EC firmware while running libreboot is unknown. - Libreboot only replaces the BIOS firmware, not EC. - </p> - <p> - Updated EC firmware has several advantages e.g. - bettery battery handling. - </p> - - </div> - <div class="section"> - - <h2 id="compatibility_noblobs">Compatibility (without blobs)</h2> - - <div class="subsection"> - <h3 id="hwvirt">Hardware virtualization (vt-x)</h3> - <p> - The T400, when run without CPU microcode updates in coreboot, currently kernel panics - if running QEMU with vt-x enabled on 2 cores for the guest. With a single core enabled - for the guest, the guest panics (but the host is fine). Working around this in QEMU - might be possible; if not, software virtualization should work fine (it's just slower). - </p> - <p> - On GM45 hardware (with libreboot), make sure that the <i>kvm</i> and <i>kvm_intel</i> kernel modules - are not loaded, when using QEMU. - </p> - <p> - The following errata datasheet from Intel might help with investigation: - <a href="http://download.intel.com/design/mobile/specupdt/320121.pdf">http://download.intel.com/design/mobile/specupdt/320121.pdf</a> - </p> - </div> - - </div> - - <div class="section"> - - <p> - The T400 is almost identical to the X200, code-wise. See <a href="x200.html">x200.html</a>. - </p> - - </div> - - <div class="section"> - - <h2 id="regdumps">Hardware register dumps</h2> - - <p> - The coreboot wiki <a href="http://www.coreboot.org/Motherboard_Porting_Guide">shows</a> - how to collect various logs useful in porting to new - boards. Following are outputs from the T400: - </p> - - <ul> - <li> - T400 with <b>Winbond W25X64</b> flash chip (8MiB, SOIC-16) - and Lenovo BIOS 2.02 (EC firmware 1.01): - <ul> - <li><a href="../future/dumps/logs-t400-bios2.02-ec1.01/">../future/dumps/logs-t400-bios2.02-ec1.01/</a></li> - </ul> - </li> - <li> - Version of flashrom used for the external flashing/reading logs is the one that libreboot git revision c164960 uses. - </li> - </ul> - - </div> - - <div class="section"> - - <p> - Copyright © 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hcl/t400.md b/docs/hcl/t400.md new file mode 100644 index 00000000..ab1523f8 --- /dev/null +++ b/docs/hcl/t400.md @@ -0,0 +1,136 @@ +<div class="section"> + +ThinkPad T400 {#pagetop} +============= + +It is believed that all or most T400 laptops are compatible. See notes +about [CPU +compatibility](../install/t400_external.html#cpu_compatibility) for +potential incompatibilities. + +There are two possible flash chip sizes for the T400: 4MiB (32Mbit) or +8MiB (64Mbit). This can be identified by the type of flash chip below +the palmrest: 4MiB is SOIC-8, 8MiB is SOIC-16. + +**The T400 laptops come with the ME (and sometimes AMT in addition) +before flashing libreboot. Libreboot disables and removes it by using a +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) + +[Back to previous index](./). + +</div> + +<div class="section"> + +EC update {#ecupdate} +========= + +It is recommended that you update to the latest EC firmware version. The +[EC firmware](https://libreboot.org/faq/#firmware-ec) is separate from +libreboot, so we don\'t actually provide that, but if you still have +Lenovo BIOS then you can just run the Lenovo BIOS update utility, which +will update both the BIOS and EC version. See: + +- <https://libreboot.org/docs/install/index.html#flashrom> +- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk> + +NOTE: this can only be done when you are using Lenovo BIOS. How to +update the EC firmware while running libreboot is unknown. Libreboot +only replaces the BIOS firmware, not EC. + +Updated EC firmware has several advantages e.g. bettery battery +handling. + +</div> + +<div class="section"> + +Compatibility (without blobs) {#compatibility_noblobs} +----------------------------- + +<div class="subsection"> + +### Hardware virtualization (vt-x) {#hwvirt} + +The T400, when run without CPU microcode updates in coreboot, currently +kernel panics if running QEMU with vt-x enabled on 2 cores for the +guest. With a single core enabled for the guest, the guest panics (but +the host is fine). Working around this in QEMU might be possible; if +not, software virtualization should work fine (it\'s just slower). + +On GM45 hardware (with libreboot), make sure that the *kvm* and +*kvm\_intel* kernel modules are not loaded, when using QEMU. + +The following errata datasheet from Intel might help with investigation: +<http://download.intel.com/design/mobile/specupdt/320121.pdf> + +</div> + +</div> + +<div class="section"> + +The T400 is almost identical to the X200, code-wise. See +[x200.html](x200.html). + +</div> + +<div class="section"> + +Hardware register dumps {#regdumps} +----------------------- + +The coreboot wiki +[shows](http://www.coreboot.org/Motherboard_Porting_Guide) how to +collect various logs useful in porting to new boards. Following are +outputs from the T400: + +- T400 with **Winbond W25X64** flash chip (8MiB, SOIC-16) and Lenovo + BIOS 2.02 (EC firmware 1.01): + - [../future/dumps/logs-t400-bios2.02-ec1.01/](../future/dumps/logs-t400-bios2.02-ec1.01/) +- Version of flashrom used for the external flashing/reading logs is + the one that libreboot git revision c164960 uses. + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hcl/t500.html b/docs/hcl/t500.html deleted file mode 100644 index b8d451eb..00000000 --- a/docs/hcl/t500.html +++ /dev/null @@ -1,209 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad T500</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">ThinkPad T500</h1> - - <p> - It is believed that all or most T500 laptops are compatible. - See notes about <a href="../install/t500_external.html#cpu_compatibility">CPU compatibility</a> - for potential incompatibilities. - </p> - - <p> - There are two possible flash chip sizes for the T500: 4MiB (32Mbit) or 8MiB (64Mbit). - This can be identified by the type of flash chip below the palmrest: 4MiB is SOIC-8, 8MiB - is SOIC-16. - </p> - - <p> - <b>The T500 laptops come with the ME (and sometimes AMT in addition) before flashing libreboot. Libreboot disables and removes it - by using a modified descriptor: see <a href="gm45_remove_me.html">gm45_remove_me.html</a></b> (contains notes, plus - instructions) - </p> - - <p> - Flashing instructions can be found at <a href="../install/#flashrom">../install/#flashrom</a> - </p> - - <p> - <a href="./">Back to previous index</a>. - </p> - </div> - - <div class="section"> - - <h1 id="ecupdate">EC update</h1> - - <p> - It is recommended that you update to the latest EC firmware version. - The <a href="https://libreboot.org/faq/#firmware-ec">EC firmware</a> - is separate from libreboot, so we don't actually provide that, but - if you still have Lenovo BIOS then you can just run the Lenovo BIOS - update utility, which will update both the BIOS and EC version. - See: - </p> - <ul> - <li><a href="https://libreboot.org/docs/install/index.html#flashrom">https://libreboot.org/docs/install/index.html#flashrom</a></li> - <li><a href="http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk">http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk</a></li> - </ul> - <p> - NOTE: this can only be done when you are using Lenovo BIOS. How to - update the EC firmware while running libreboot is unknown. - Libreboot only replaces the BIOS firmware, not EC. - </p> - <p> - Updated EC firmware has several advantages e.g. - bettery battery handling. - </p> - - </div> - <div class="section"> - - <h2 id="compatibility_noblobs">Compatibility (without blobs)</h2> - - <div class="subsection"> - <h3 id="hwvirt">Hardware virtualization (vt-x)</h3> - <p> - The T500, when run without CPU microcode updates in coreboot, currently kernel panics - if running QEMU with vt-x enabled on 2 cores for the guest. With a single core enabled - for the guest, the guest panics (but the host is fine). Working around this in QEMU - might be possible; if not, software virtualization should work fine (it's just slower). - </p> - <p> - On GM45 hardware (with libreboot), make sure that the <i>kvm</i> and <i>kvm_intel</i> kernel modules - are not loaded, when using QEMU. - </p> - <p> - The following errata datasheet from Intel might help with investigation: - <a href="http://download.intel.com/design/mobile/specupdt/320121.pdf">http://download.intel.com/design/mobile/specupdt/320121.pdf</a> - </p> - </div> - - </div> - - <div class="section"> - - <p> - The T500 is almost identical to the X200, code-wise. See <a href="x200.html">x200.html</a>. - </p> - - </div> - - <div class="section"> - - <h2 id="descriptor_difference"> - Descriptor and Gbe differences - </h2> - - <p> - See - <a href="../future/dumps/t500_x200_descriptor/descriptor_diff_t500_x200.txt">../future/dumps/t500_x200_descriptor/descriptor_diff_t500_x200.txt</a> - and - <a href="../future/dumps/t500_x200_descriptor/gbe_diff_t500_x200.txt">../future/dumps/t500_x200_descriptor/gbe_diff_t500_x200.txt</a> - </p> - - <p> - 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:<br/> - $ <b>diff -u t500gbe x200gbe</b><br/> - $ <b>diff -u t500descriptor x200descriptor</b> - </p> - - <p> - ME VSCC table is in a different place and a different size on the T500. Libreboot disables and removes the ME - anyway, so it doesn't matter. - </p> - - <p> - The very same descriptor/gbe used on the X200 (generated by <a href="gm45_remove_me.html#ich9gen">ich9gen</a>) - was re-used on the T500, and it still worked. - </p> - - </div> - - <div class="section"> - - <h2 id="regdumps">Hardware register dumps</h2> - - <p> - The coreboot wiki <a href="http://www.coreboot.org/Motherboard_Porting_Guide">shows</a> - how to collect various logs useful in porting to new - boards. Following are outputs from the T500: - </p> - - <ul> - <li> - T500 with <b>Macronix MX25L3205D</b> flash chip (4MiB, SOIC-8) - and Lenovo BIOS 3.13 7VET83WW (EC firmware 1.06): - <ul> - <li><a href="../future/dumps/t500log/">../future/dumps/t500log/</a></li> - </ul> - </li> - </ul> - - </div> - - <div class="section"> - - <p> - Copyright © 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hcl/t500.md b/docs/hcl/t500.md new file mode 100644 index 00000000..eebeccb1 --- /dev/null +++ b/docs/hcl/t500.md @@ -0,0 +1,160 @@ +<div class="section"> + +ThinkPad T500 {#pagetop} +============= + +It is believed that all or most T500 laptops are compatible. See notes +about [CPU +compatibility](../install/t500_external.html#cpu_compatibility) for +potential incompatibilities. + +There are two possible flash chip sizes for the T500: 4MiB (32Mbit) or +8MiB (64Mbit). This can be identified by the type of flash chip below +the palmrest: 4MiB is SOIC-8, 8MiB is SOIC-16. + +**The T500 laptops come with the ME (and sometimes AMT in addition) +before flashing libreboot. Libreboot disables and removes it by using a +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) + +[Back to previous index](./). + +</div> + +<div class="section"> + +EC update {#ecupdate} +========= + +It is recommended that you update to the latest EC firmware version. The +[EC firmware](https://libreboot.org/faq/#firmware-ec) is separate from +libreboot, so we don\'t actually provide that, but if you still have +Lenovo BIOS then you can just run the Lenovo BIOS update utility, which +will update both the BIOS and EC version. See: + +- <https://libreboot.org/docs/install/index.html#flashrom> +- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk> + +NOTE: this can only be done when you are using Lenovo BIOS. How to +update the EC firmware while running libreboot is unknown. Libreboot +only replaces the BIOS firmware, not EC. + +Updated EC firmware has several advantages e.g. bettery battery +handling. + +</div> + +<div class="section"> + +Compatibility (without blobs) {#compatibility_noblobs} +----------------------------- + +<div class="subsection"> + +### Hardware virtualization (vt-x) {#hwvirt} + +The T500, when run without CPU microcode updates in coreboot, currently +kernel panics if running QEMU with vt-x enabled on 2 cores for the +guest. With a single core enabled for the guest, the guest panics (but +the host is fine). Working around this in QEMU might be possible; if +not, software virtualization should work fine (it\'s just slower). + +On GM45 hardware (with libreboot), make sure that the *kvm* and +*kvm\_intel* kernel modules are not loaded, when using QEMU. + +The following errata datasheet from Intel might help with investigation: +<http://download.intel.com/design/mobile/specupdt/320121.pdf> + +</div> + +</div> + +<div class="section"> + +The T500 is almost identical to the X200, code-wise. See +[x200.html](x200.html). + +</div> + +<div class="section"> + +Descriptor and Gbe differences {#descriptor_difference} +------------------------------ + +See +[../future/dumps/t500\_x200\_descriptor/descriptor\_diff\_t500\_x200.txt](../future/dumps/t500_x200_descriptor/descriptor_diff_t500_x200.txt) +and +[../future/dumps/t500\_x200\_descriptor/gbe\_diff\_t500\_x200.txt](../future/dumps/t500_x200_descriptor/gbe_diff_t500_x200.txt) + +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**\ +\$ **diff -u t500descriptor x200descriptor** + +ME VSCC table is in a different place and a different size on the T500. +Libreboot disables and removes the ME anyway, so it doesn\'t matter. + +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. + +</div> + +<div class="section"> + +Hardware register dumps {#regdumps} +----------------------- + +The coreboot wiki +[shows](http://www.coreboot.org/Motherboard_Porting_Guide) how to +collect various logs useful in porting to new boards. Following are +outputs from the T500: + +- T500 with **Macronix MX25L3205D** flash chip (4MiB, SOIC-8) and + Lenovo BIOS 3.13 7VET83WW (EC firmware 1.06): + - [../future/dumps/t500log/](../future/dumps/t500log/) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/hcl/x200.html b/docs/hcl/x200.html deleted file mode 100644 index d5c8f528..00000000 --- a/docs/hcl/x200.html +++ /dev/null @@ -1,423 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad X200</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">ThinkPad X200</h1> - - <p> - It is believed that all X200 laptops are compatible. X200S and X200 Tablet will - also work, <a href="#x200s">depending on the configuration</a>. - </p> - <p> - 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. - <b>It's most likely true.</b> - </p> - - <p> - There are two possible flash chip sizes for the X200: 4MiB (32Mbit) or 8MiB (64Mbit). - This can be identified by the type of flash chip below the palmrest: 4MiB is SOIC-8, 8MiB - is SOIC-16. - </p> - - <p> - <b>The X200 laptops come with the ME (and sometimes AMT in addition) before flashing libreboot. Libreboot disables and removes it - by using a modified descriptor: see <a href="gm45_remove_me.html">gm45_remove_me.html</a></b> (contains notes, plus - instructions) - </p> - - <p> - Flashing instructions can be found at <a href="../install/#flashrom">../install/#flashrom</a> - </p> - - <p> - <a href="./">Back to previous index</a>. - </p> - </div> - - <div class="section"> - - <h1 id="ecupdate">EC update</h1> - - <p> - It is recommended that you update to the latest EC firmware version. - The <a href="https://libreboot.org/faq/#firmware-ec">EC firmware</a> - is separate from libreboot, so we don't actually provide that, but - if you still have Lenovo BIOS then you can just run the Lenovo BIOS - update utility, which will update both the BIOS and EC version. - See: - </p> - <ul> - <li><a href="https://libreboot.org/docs/install/index.html#flashrom">https://libreboot.org/docs/install/index.html#flashrom</a></li> - <li><a href="http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk">http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk</a></li> - </ul> - <p> - NOTE: this can only be done when you are using Lenovo BIOS. How to - update the EC firmware while running libreboot is unknown. - Libreboot only replaces the BIOS firmware, not EC. - </p> - <p> - Updated EC firmware has several advantages e.g. - bettery battery handling. - </p> - - </div> - - <div class="section"> - - <h2 id="compatibility_noblobs">Compatibility (without blobs)</h2> - - <div class="subsection"> - <h3 id="hwvirt">Hardware virtualization (vt-x)</h3> - <p> - The X200, when run without CPU microcode updates in coreboot, currently kernel panics - if running QEMU with vt-x enabled on 2 cores for the guest. With a single core enabled - for the guest, the guest panics (but the host is fine). Working around this in QEMU - might be possible; if not, software virtualization should work fine (it's just slower). - </p> - <p> - On GM45 hardware (with libreboot), make sure that the <i>kvm</i> and <i>kvm_intel</i> kernel modules - are not loaded, when using QEMU. - </p> - <p> - The following errata datasheet from Intel might help with investigation: - <a href="http://download.intel.com/design/mobile/specupdt/320121.pdf">http://download.intel.com/design/mobile/specupdt/320121.pdf</a> - </p> - <p> - 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. - </p> - </div> - - </div> - - <div class="section"> - - <h2 id="x200s">X200S and X200 Tablet.</h2> - - <p> - X200S and X200 Tablet have raminit issues at the time of writing - (GS45 chipset. X200 uses GM45). - </p> - - <p> - X200S and X200 Tablet are known to work, but only with certain CPU+RAM configurations. - The current stumbling block is RCOMP and SFF, mentioned in - <a href="https://www.cs.cmu.edu/~410/doc/minimal_boot.pdf">https://www.cs.cmu.edu/~410/doc/minimal_boot.pdf</a>. - </p> - <p> - The issues mostly relate to raminit (memory initialization). With an - unpatched coreboot, you get the following: <a href="text/x200s/cblog00.txt">text/x200s/cblog00.txt</a>. - No SODIMM combination that was tested would work. At first glance, it looks - like GS45 (chipset that X200S uses. X200 uses GM45) is unsupported, but - there is a workaround that can be used to make certain models of the X200S - work, depending on the RAM. - </p> - <p> - The datasheet for GS45 describes two modes: low-performance and - high-performance. Low performance uses the SU range of ultra-low - voltage procesors (SU9400, for example), and high-performance uses the - SL range of processors (SL9400, for example). According to datasheets, - GS45 behaves very similarly to GM45 when operating in high-performance - mode. - </p> - <p> - The theory then was that you could simply remove - the checks in coreboot and make it pass GS45 off as GM45; the idea is - that, with a high-performance mode CPU (SL9400, for example) it would - just boot up and work. - </p> - <p> - This suspicion was confirmed with the following log: - <a href="text/x200s/cblog01.txt">text/x200s/cblog01.txt</a>. - The memory modules in this case are 2x4GB. <s><b>However, not all - configurations work: <a href="text/x200s/cblog02.txt">text/x200s/cblog02.txt</a> (2x2GB) - and <a href="text/x200s/cblog03.txt">text/x200s/cblog03.txt</a> (1x2GB) - show a failed bootup.</b></s> <i>False alarm. The modules were mixed (non-matching). X200S - with high-performance mode CPU will work so long as you use matching memory modules - (doesn't matter what size).</i> - </p> - <p> - This was then pushed as a patch for coreboot, which can be found at - <a href="http://review.coreboot.org/#/c/7786/">http://review.coreboot.org/#/c/7786/</a> - (libreboot merges this patch in coreboot-libre now. Check the 'getcb' script in - src or git). - </p> - - <div class="subsection"> - <h3 id="x200s_raminit">Proper GS45 raminit</h3> - <p> - A new northbridge gs45 should be added to coreboot, based on gm45, - and a new port x200st (X200S and X200T) should be added based on - the x200 port. - </p> - <p> - This port would have proper raminit. Alternatively, gs45 (if - raminit is taken to be the only issue with it) can be part of - gm45 northbridge support (and X200S/Tablet being part of the X200 - port) with conditional checks in the raminit that make raminit - work differently (as required) for GS45. nico_h and pgeorgi/patrickg - in the coreboot IRC channel should know more about raminit on gm45 - and likely gs45. - </p> - <p> - pgeorgi recommends to run SerialICE on the factory BIOS (for X200S), - 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. - </p> - </div> - - </div> - - <div class="section"> - - <h2>Trouble undocking (button doesn't work)</h2> - - <p> - This person seems to have a workaround: - <a href="https://github.com/the-unconventional/libreboot-undock">https://github.com/the-unconventional/libreboot-undock</a> - </p> - - </div> - - <div class="section"> - - <h2 id="lcd_supported_list">LCD compatibility list</h2> - - <p> - LCD panel list (X200 panels listed there): - <a href="http://www.thinkwiki.org/wiki/TFT_display">http://www.thinkwiki.org/wiki/TFT_display</a> - </p> - - <p> - All LCD panels for the X200, X200S and X200 Tablet are known to work. - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - <div class="subsection"> - <h3 id="ips"> - AFFS/IPS panels - </h3> - <h4>X200</h4> - <p> - Adapted from <a href="https://github.com/bibanon/Coreboot-ThinkPads/wiki/ThinkPad-X200">https://github.com/bibanon/Coreboot-ThinkPads/wiki/ThinkPad-X200</a> - </p> - <p> - Look at wikipedia for difference between TN and IPS panels. IPS have much better colour/contrast than - a regular TN, and will typically have good viewing angles. - </p> - <p> - These seem to be from the X200 tablet. You need to find one without the glass touchscreen protection on it - (might be able to remove it, though). It also must not have a digitizer on it (again, might be possible to - just simply remove the digitizer). - </p> - <ul> - <li>BOE-Hydis HV121WX4-120, HV121WX4-110 or HV121WX4-100 - cheap-ish, might be hard to find</li> - <li>Samsung LTN121AP02-001 - common to find, cheap</li> - </ul> - <p> - <b>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 - <a href="#led_howtotell">#led_howtotell</a>. 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.</b> - </p> - <p> - There are glossy and matte versions of these. Matte means anti-glare, which is what you want (in this authors opinion). - </p> - <p> - Refer to the HMM (hardware maintenance manual) for how to replace the screen. - </p> - <p>Sources:</p> - <ul> - <li><a href="http://forum.thinkpads.com/viewtopic.php?f=2&t=84941">ThinkPad Forums - Matte AFFS Panel on X200</a></li> - <li><a href="http://forum.thinkpads.com/viewtopic.php?p=660662#p660662">ThinkPad Forums - Parts for X200 AFFS Mod</a></li> - <li><a href="http://thinkwiki.de/X200_Displayumbau">ThinkWiki.de - X200 Displayumbau</a></li> - </ul> - </div> - <div class="subsection"> - <h3>X200S</h3> - <p> - <a href="http://forum.thinkpads.com/viewtopic.php?p=618928#p618928">http://forum.thinkpads.com/viewtopic.php?p=618928#p618928</a> - explains that the X200S screens/assemblies are thinner. You need to replace the whole lid with one from a normal X200/X201. - </p> - </div> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - <h2 id="led_howtotell">How to tell if it has an LED or CCFL?</h2> - - <p> - Some X200s have a CCFL backlight and some have an LED backlight, in their LCD panel. This - also means that the inverters will vary, so you must be careful if ever replacing either - the panel and/or inverter. (a CCFL inverter is high-voltage and will destroy an LED backlit panel). - </p> - <p> - CCFLs contain mercury. An X200 with a CCFL backlight will (<b></b>unless it has been changed to an LED, - with the correct inverter. Check with your supplier!</b>) the following: <i>"This product - contains Lithium Ion Battery, Lithium Battery and a lamp which contains mercury; dispose according to - local, state or federal laws"</i> (one with an LED backlit panel will say something different). - </p> - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - </div> - - <div class="section"> - - <h2 id="regdumps">Hardware register dumps</h2> - - <p> - The coreboot wiki <a href="http://www.coreboot.org/Motherboard_Porting_Guide">shows</a> - how to collect various logs useful in porting to new - boards. Following are outputs from the X200: - </p> - - <ul> - <li> - BIOS 3.15, EC 1.06 - <ul> - <li><a href="hwdumps/x200/">hwdumps/x200/</a></li> - </ul> - </li> - </ul> - - </div> - - <div class="section"> - - <h1 id="ram_s3_microcode">RAM, S3 and microcode updates</h1> - - <p> - Not all memory modules work. Most of the default ones do, but you have to be careful - when upgrading to 8GiB; some modules work, some don't. - </p> - - <p> - Someone on reddit also did their own research on RAM compatibility: - <a href="https://www.reddit.com/r/libreboot/comments/5ax17e/liberated_x200_is_really_picky_with_memory/">on this post</a> - </p> - - <p> - <a href="http://www.forum.thinkpads.com/viewtopic.php?p=760721">This page</a> might be useful for RAM compatibility info - (note: coreboot raminit is different, so this page might be BS) - </p> - - <p> - pehjota started collecting some steppings for different CPUs on several X200 laptops. - You can get the CPUID by running: <br/> - $ <b>dmesg | sed -n 's/^.* microcode: CPU0 sig=0x\([^,]*\),.*$/\1/p'</b> - </p> - - <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 boot with any Samsung DIMMs, all have CPUID 0x10676 (stepping M0). - </p> - - <p> - What pehjota wrote: - Laptops with CPUID 0x167A (stepping R0) resume properly every time and work with Samsung DIMMs. I'll - need to do more testing on more units to better confirm these trends, but it looks like the M0 microcode - is very buggy. That would also explain why I didn't have issues with Samsung DIMMs with the Lenovo BIOS - (which would have microcode updates). I wonder if VT-x works on R0. - </p> - - <p> - What pehjota wrote: - As I said, 10676 is M0 and 1067A is R0; those are the two CPUIDs and steppings for Intel Core 2 Duo P8xxx CPUs with factory microcode. (1067 is the family and model, and 6 or A is the stepping ID.) - </p> - - <p> - <b> - TODO: check the CPUIDs and test S3 resume and/or KVM on any C2D systems (including non-P8xxx ones, which I don't have here) you have available. I'd be curious if you could confirm these results. - </b> - It might not be coreboot that's buggy with raminit/S3; it might just be down to the microcode updates. - </p> - - </div> - - <div class="section"> - - <h2 id="unsorted">Unsorted notes</h2> - -<pre> -<sgsit> do you know if it's possible to flash thinkpads over the LPC debug connector at the front edge? -<sgsit> that would make life much easier for systems like this -<sgsit> all the Wistron manufactured systems have this thing called a "golden finger", normally at the front edge of the board -<sgsit> you can plug a board in which gives diagnostic codes but i'm wondering whether it is capable of more -<sgsit> <a href="http://www.endeer.cz/bios.tools/bios.html">http://www.endeer.cz/bios.tools/bios.html</a> -</pre> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/hcl/x200.md b/docs/hcl/x200.md new file mode 100644 index 00000000..c559d275 --- /dev/null +++ b/docs/hcl/x200.md @@ -0,0 +1,363 @@ +<div class="section"> + +ThinkPad X200 {#pagetop} +============= + +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, +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.** + +There are two possible flash chip sizes for the X200: 4MiB (32Mbit) or +8MiB (64Mbit). This can be identified by the type of flash chip below +the palmrest: 4MiB is SOIC-8, 8MiB is SOIC-16. + +**The X200 laptops come with the ME (and sometimes AMT in addition) +before flashing libreboot. Libreboot disables and removes it by using a +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) + +[Back to previous index](./). + +</div> + +<div class="section"> + +EC update {#ecupdate} +========= + +It is recommended that you update to the latest EC firmware version. The +[EC firmware](https://libreboot.org/faq/#firmware-ec) is separate from +libreboot, so we don\'t actually provide that, but if you still have +Lenovo BIOS then you can just run the Lenovo BIOS update utility, which +will update both the BIOS and EC version. See: + +- <https://libreboot.org/docs/install/index.html#flashrom> +- <http://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk> + +NOTE: this can only be done when you are using Lenovo BIOS. How to +update the EC firmware while running libreboot is unknown. Libreboot +only replaces the BIOS firmware, not EC. + +Updated EC firmware has several advantages e.g. bettery battery +handling. + +</div> + +<div class="section"> + +Compatibility (without blobs) {#compatibility_noblobs} +----------------------------- + +<div class="subsection"> + +### Hardware virtualization (vt-x) {#hwvirt} + +The X200, when run without CPU microcode updates in coreboot, currently +kernel panics if running QEMU with vt-x enabled on 2 cores for the +guest. With a single core enabled for the guest, the guest panics (but +the host is fine). Working around this in QEMU might be possible; if +not, software virtualization should work fine (it\'s just slower). + +On GM45 hardware (with libreboot), make sure that the *kvm* and +*kvm\_intel* kernel modules are not loaded, when using QEMU. + +The following errata datasheet from Intel might help with investigation: +<http://download.intel.com/design/mobile/specupdt/320121.pdf> + +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. + +</div> + +</div> + +<div class="section"> + +X200S and X200 Tablet. {#x200s} +---------------------- + +X200S and X200 Tablet have raminit issues at the time of writing (GS45 +chipset. X200 uses GM45). + +X200S and X200 Tablet are known to work, but only with certain CPU+RAM +configurations. The current stumbling block is RCOMP and SFF, mentioned +in <https://www.cs.cmu.edu/~410/doc/minimal_boot.pdf>. + +The issues mostly relate to raminit (memory initialization). With an +unpatched coreboot, you get the following: +[text/x200s/cblog00.txt](text/x200s/cblog00.txt). No SODIMM combination +that was tested would work. At first glance, it looks like GS45 (chipset +that X200S uses. X200 uses GM45) is unsupported, but there is a +workaround that can be used to make certain models of the X200S work, +depending on the RAM. + +The datasheet for GS45 describes two modes: low-performance and +high-performance. Low performance uses the SU range of ultra-low voltage +procesors (SU9400, for example), and high-performance uses the SL range +of processors (SL9400, for example). According to datasheets, GS45 +behaves very similarly to GM45 when operating in high-performance mode. + +The theory then was that you could simply remove the checks in coreboot +and make it pass GS45 off as GM45; the idea is that, with a +high-performance mode CPU (SL9400, for example) it would just boot up +and work. + +This suspicion was confirmed with the following log: +[text/x200s/cblog01.txt](text/x200s/cblog01.txt). The memory modules in +this case are 2x4GB. ~~**However, not all configurations work: +[text/x200s/cblog02.txt](text/x200s/cblog02.txt) (2x2GB) and +[text/x200s/cblog03.txt](text/x200s/cblog03.txt) (1x2GB) show a failed +bootup.**~~ *False alarm. The modules were mixed (non-matching). X200S +with high-performance mode CPU will work so long as you use matching +memory modules (doesn\'t matter what size).* + +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). + +<div class="subsection"> + +### Proper GS45 raminit {#x200s_raminit} + +A new northbridge gs45 should be added to coreboot, based on gm45, and a +new port x200st (X200S and X200T) should be added based on the x200 +port. + +This port would have proper raminit. Alternatively, gs45 (if raminit is +taken to be the only issue with it) can be part of gm45 northbridge +support (and X200S/Tablet being part of the X200 port) with conditional +checks in the raminit that make raminit work differently (as required) +for GS45. nico\_h and pgeorgi/patrickg in the coreboot IRC channel +should know more about raminit on gm45 and likely gs45. + +pgeorgi recommends to run SerialICE on the factory BIOS (for X200S), +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. + +</div> + +</div> + +<div class="section"> + +Trouble undocking (button doesn\'t work) +---------------------------------------- + +This person seems to have a workaround: +<https://github.com/the-unconventional/libreboot-undock> + +</div> + +<div class="section"> + +LCD compatibility list {#lcd_supported_list} +---------------------- + +LCD panel list (X200 panels listed there): +<http://www.thinkwiki.org/wiki/TFT_display> + +All LCD panels for the X200, X200S and X200 Tablet are known to work. + +[Back to top of page.](#pagetop) + +<div class="subsection"> + +### AFFS/IPS panels {#ips} + +#### X200 + +Adapted from +<https://github.com/bibanon/Coreboot-ThinkPads/wiki/ThinkPad-X200> + +Look at wikipedia for difference between TN and IPS panels. IPS have +much better colour/contrast than a regular TN, and will typically have +good viewing angles. + +These seem to be from the X200 tablet. You need to find one without the +glass touchscreen protection on it (might be able to remove it, though). +It also must not have a digitizer on it (again, might be possible to +just simply remove the digitizer). + +- BOE-Hydis HV121WX4-120, HV121WX4-110 or HV121WX4-100 - cheap-ish, + might be hard to find +- Samsung LTN121AP02-001 - common to find, cheap + +**If your X200 has an LED backlit panel in it, then you also need to get +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 +are part numbers: 44C9909 for CCFL LVDS cable with bluetooth and camera +connections, and 42W8009 or 42W8010 for the inverter.** + +There are glossy and matte versions of these. Matte means anti-glare, +which is what you want (in this authors opinion). + +Refer to the HMM (hardware maintenance manual) for how to replace the +screen. + +Sources: + +- [ThinkPad Forums - Matte AFFS Panel on + X200](http://forum.thinkpads.com/viewtopic.php?f=2&t=84941) +- [ThinkPad Forums - Parts for X200 AFFS + Mod](http://forum.thinkpads.com/viewtopic.php?p=660662#p660662) +- [ThinkWiki.de - X200 + Displayumbau](http://thinkwiki.de/X200_Displayumbau) + +</div> + +<div class="subsection"> + +### 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. + +</div> + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +How to tell if it has an LED or CCFL? {#led_howtotell} +------------------------------------- + +Some X200s have a CCFL backlight and some have an LED backlight, in +their LCD panel. This also means that the inverters will vary, so you +must be careful if ever replacing either the panel and/or inverter. (a +CCFL inverter is high-voltage and will destroy an LED backlit panel). + +CCFLs contain mercury. An X200 with a CCFL backlight will (****unless it +has been changed to an LED, with the correct inverter. Check with your +supplier!) the following: *\"This product contains Lithium Ion Battery, +Lithium Battery and a lamp which contains mercury; dispose according to +local, state or federal laws\"* (one with an LED backlit panel will say +something different). + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Hardware register dumps {#regdumps} +----------------------- + +The coreboot wiki +[shows](http://www.coreboot.org/Motherboard_Porting_Guide) how to +collect various logs useful in porting to new boards. Following are +outputs from the X200: + +- BIOS 3.15, EC 1.06 + - [hwdumps/x200/](hwdumps/x200/) + +</div> + +<div class="section"> + +RAM, S3 and microcode updates {#ram_s3_microcode} +============================= + +Not all memory modules work. Most of the default ones do, but you have +to be careful when upgrading to 8GiB; some modules work, some don\'t. + +Someone on reddit also did their own research on RAM compatibility: [on +this +post](https://www.reddit.com/r/libreboot/comments/5ax17e/liberated_x200_is_really_picky_with_memory/) + +[This page](http://www.forum.thinkpads.com/viewtopic.php?p=760721) might +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\'** + +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 +boot with any Samsung DIMMs, all have CPUID 0x10676 (stepping M0). + +What pehjota wrote: Laptops with CPUID 0x167A (stepping R0) resume +properly every time and work with Samsung DIMMs. I\'ll need to do more +testing on more units to better confirm these trends, but it looks like +the M0 microcode is very buggy. That would also explain why I didn\'t +have issues with Samsung DIMMs with the Lenovo BIOS (which would have +microcode updates). I wonder if VT-x works on R0. + +What pehjota wrote: As I said, 10676 is M0 and 1067A is R0; those are +the two CPUIDs and steppings for Intel Core 2 Duo P8xxx CPUs with +factory microcode. (1067 is the family and model, and 6 or A is the +stepping ID.) + +**TODO: check the CPUIDs and test S3 resume and/or KVM on any C2D +systems (including non-P8xxx ones, which I don\'t have here) you have +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. + +</div> + +<div class="section"> + +Unsorted notes {#unsorted} +-------------- + + <sgsit> do you know if it's possible to flash thinkpads over the LPC debug connector at the front edge? + <sgsit> that would make life much easier for systems like this + <sgsit> all the Wistron manufactured systems have this thing called a "golden finger", normally at the front edge of the board + <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 + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/index.html b/docs/index.html deleted file mode 100644 index 9d197f56..00000000 --- a/docs/index.html +++ /dev/null @@ -1,309 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('css/main.css'); - </style> - - <title>Libreboot project documentation</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Libreboot documentation</h1> - <p> - Information about this release can be found at <a href="release.html">release.html</a>. - Always check <a href="http://libreboot.org">libreboot.org</a> for updates. - </p> - <p> - <a href="#why">What is libreboot?</a> - </p> - <p> - <a href="https://libreboot.org/faq/">Answers to frequently asked questions about Libreboot</a> - </p> - </div> - - <div class="section"> - - <p> - Libreboot is compatible with GNU+Linux and several BSD systems. - </p> - <p> - For GNU+Linux, - have a look at our <a href="distros/">list of GNU+Linux distributions that we recommend</a>. - </p> - <p> - For BSD, refer to <a href="https://libreboot.org/faq/#bsd">the libreboot FAQ</a>. We wish - to merge instructions into the official libreboot documentation, if someone - will provide it. We do have some instructions now for NetBSD, FreeBSD and OpenBSD, - but they are still incomplete. See <a href="bsd/">bsd/</a>. - </p> - - <h1>Installing libreboot</h1> - <ul> - <li><a href="hcl/">What systems can I use libreboot on?</a></li> - <li><a href="install/">How to install libreboot</a></li> - </ul> - <h1>Installing operating systems</h1> - <ul> - <li><a href="distros/">List of recommended GNU+Linux distributions for libreboot</a></li> - <li><a href="gnulinux/">How to install GNU+Linux on a libreboot system</a></li> - <li><a href="bsd/">How to install BSD on a libreboot system</a></li> - </ul> - <h1>Information for developers</h1> - <ul> - <li><a href="git/">How to compile the libreboot source code</a></li> - <li><a href="depthcharge/">Depthcharge payload</a></li> - <li><a href="grub/">GRUB payload</a></li> - </ul> - <h1>Other information</h1> - <ul> - <li><a href="hardware/">Hardware modifications</a></li> - <li><a href="misc/">Miscellaneous</a></li> - </ul> - - </div> - - <div class="section" id="why"> - - <h1>About the libreboot project</h1> - - <p> - Libreboot is a free BIOS or UEFI replacement (<a href="https://en.wikipedia.org/wiki/Free_software">free as in freedom</a>); - libre <em>boot firmware</em> that initializes the hardware and starts a bootloader for your operating - system. - It's also an open source BIOS, but open source fails to - promote freedom; <em>please call libreboot <strong><a href="https://en.wikipedia.org/wiki/Free_software">free software</a></strong></em>. - </p> - - <p> - Libreboot originally began during December 2013, as a commercial effort - by the <a href="https://minifree.org">Ministry of Freedom</a> to achieve - RYF endorsement for a modified ThinkPad X60 - (the first system to ever be added to libreboot), which it did then achieve. - </p> - - <p> - Back then, the name <i>libreboot</i> didn't exist; the project was nameless, - referring to itself as a <i>deblobbed version of coreboot</i>. The project named - itself libreboot at some point during early 2014, and has since rapidly expanded - to support more hardware and become more user-friendly. - </p> - - <p> - Libreboot is a <a href="http://coreboot.org/">coreboot</a> distribution (distro) with proprietary software removed, - intended to be a <a href="https://en.wikipedia.org/wiki/Free_software">free</a> - (libre) 'BIOS' replacement for your computer. The project is aimed at users, attempting to make - coreboot as easy to use as possible. - </p> - - <p> - Libreboot has many practical advantages over proprietary boot firmware, - such as faster boot speeds and better security. You can - <a href="gnulinux/">install GNU+Linux with encrypted /boot/</a>, - <a href="http://www.coreboot.org/GRUB2#signed_kernels">verify GPG signatures on your kernel</a>, - put a kernel in the flash chip and more. - </p> - - <h2> - The libreboot project has three main goals: - </h2> - <ul> - <li> - <i><u><b>Recommend and distribute only free software</b></u></i>. - Coreboot distributes certain pieces of proprietary software which is needed on some systems. - Examples can include things like CPU microcode updates, memory initialization blobs and so on. - The coreboot project sometimes recommends adding more blobs which it does not distribute, such - as the Video BIOS or Intel's <i>Management Engine</i>. However, a lot of dedicated and talented - individuals in coreboot work hard to replace these blobs whenever possible. - </li> - <li> - <i><u><b>Support as much hardware as possible!</b></u></i> - Libreboot supports less hardware than coreboot, because most systems from coreboot still require - certain proprietary software to work properly. Libreboot is an attempt to support as much - hardware as possible, without any proprietary software. - </li> - <li> - <i><u><b>Make coreboot easy to use</b></u></i>. - 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.<br/><br/> - - 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.<br/><br/> - - 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.<br/><br/> - - 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 wanted to do that (for whatever reason). - </li> - </ul> - - <h2> - Libreboot is a coreboot distribution, not a coreboot fork - </h2> - - <p> - Libreboot is not a fork of coreboot. Every so often, the project re-bases on the latest - version of coreboot, with the number of custom patches in use minimized. - </p> - - <p> - All new coreboot development should be done in coreboot (upstream), not libreboot! - Libreboot is about deblobbing and packaging coreboot in a user-friendly way, where most work - is already done for the user. - </p> - - <p> - For example, if you wanted to add a new board to libreboot, you should add it to coreboot first. - Libreboot will automatically receive your code at a later date, when it updates itself. - </p> - - <p> - The deblobbed coreboot tree used in libreboot is referred to as <i>coreboot-libre</i>, - to distinguish it as a component of <i>libreboot</i>. - </p> - - <h2> - Libreboot is a 'stable' version of coreboot - </h2> - <ul> - <li> - Coreboot uses the <a href="https://en.wikipedia.org/wiki/Rolling_release">rolling release</a> model, - which means that it is not guaranteed to be stable, or to even work at all on a given day. - Coreboot does have a strict code review process, but being such a large project with so many contributors, regressions - are always possible. - </li> - <li> - Libreboot freezes on a particular revision of coreboot, making sure that everything works properly, - making fixes on top of that and repeating this during each subsequent update to a later version - of coreboot. By doing this, it provides a stronger guarantee to the user that the firmware - will be reliable, and not break their system. - </li> - </ul> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section" id="version"> - - <h1>How do I know what version I'm running?</h1> - <p> - If you are at least 127 commits after release 20150518 - (commit message <em>build/roms/helper: add version information to CBFS</em>) - (or you have any <strong>upstream</strong> 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:<br/> - <strong>cat (cbfsdisk)/lbversion</strong><br/> - This will also work on non-release images (the version string is automatically generated, - using <em>git describe --tags HEAD</em>), built from the git repository. - A file named <em>version</em> will also be included in the archives that you downloaded (if you are - using release archives). - </p> - - <p> - If it exists, you can also extract this <em>lbversion</em> file by using the <i>cbfstool</i> 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 (<em>libreboot.rom</em>, in this example):<br/> - $ <strong>./cbfstool libreboot.rom extract -n lbversion -f lbversion</strong><br/> - You will now have a file, named <em>lbversion</em>, which you can read in whatever program - it is that you use for reading/writing text files. - </p> - - <p> - For git, it's easy. Just check the git log. - </p> - - <p> - For releases on or below 20150518, or snapshots generated from the git repository below 127 commits - after 20150518, you can find a file named <em>commitid</em> 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:<br/> - <strong>lscoreboot</strong><br/> - 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 - numbers are dated, and the release archives are typically built on the same day as the release; you can - correlate that with the release information in <a href="release.html">release.html</a>. - </p> - <p> - For 20160818, note that the lbversion file was missing from CBFS on GRUB images. You can still find out - what libreboot version you have by comparing checksums of image dumps (with the descriptor blanked out with 00s, - and the same done to the ROMs from the release archive, if you are on a GM45 laptop). - </p> - <p> - There may also be a ChangeLog file included in your release archive, so that you can - look in there to figure out what version you have. - </p> - - <p> - You can also check the documentation that came with your archives, and in <em>docs/release.html</em> will be - the information about the version of libreboot that you are using. - </p> - - <p> - Generally speaking, it is advisable to use the latest version of libreboot. - </p> - - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="cc-by-sa-4.0.txt">cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> - - diff --git a/docs/index.md b/docs/index.md new file mode 100644 index 00000000..19620c15 --- /dev/null +++ b/docs/index.md @@ -0,0 +1,260 @@ +<div class="section"> + +Libreboot documentation {#pagetop} +======================= + +Information about this release can be found at +[release.html](release.html). Always check +[libreboot.org](http://libreboot.org) for updates. + +[What is libreboot?](#why) + +[Answers to frequently asked questions about +Libreboot](https://libreboot.org/faq/) + +</div> + +<div class="section"> + +Libreboot is compatible with GNU+Linux and several BSD systems. + +For GNU+Linux, have a look at our [list of GNU+Linux distributions that +we recommend](distros/). + +For BSD, refer to [the libreboot FAQ](https://libreboot.org/faq/#bsd). +We wish to merge instructions into the official libreboot documentation, +if someone will provide it. We do have some instructions now for NetBSD, +FreeBSD and OpenBSD, but they are still incomplete. See [bsd/](bsd/). + +Installing libreboot +==================== + +- [What systems can I use libreboot on?](hcl/) +- [How to install libreboot](install/) + +Installing operating systems +============================ + +- [List of recommended GNU+Linux distributions for + libreboot](distros/) +- [How to install GNU+Linux on a libreboot system](gnulinux/) +- [How to install BSD on a libreboot system](bsd/) + +Information for developers +========================== + +- [How to compile the libreboot source code](git/) +- [Depthcharge payload](depthcharge/) +- [GRUB payload](grub/) + +Other information +================= + +- [Hardware modifications](hardware/) +- [Miscellaneous](misc/) + +</div> + +<div id="why" class="section"> + +About the libreboot project +=========================== + +Libreboot is a free BIOS or UEFI replacement ([free as in +freedom](https://en.wikipedia.org/wiki/Free_software)); libre *boot +firmware* that initializes the hardware and starts a bootloader for your +operating system. It\'s also an open source BIOS, but open source fails +to promote freedom; *please call libreboot **[free +software](https://en.wikipedia.org/wiki/Free_software)***. + +Libreboot originally began during December 2013, as a commercial effort +by the [Ministry of Freedom](https://minifree.org) to achieve RYF +endorsement for a modified ThinkPad X60 (the first system to ever be +added to libreboot), which it did then achieve. + +Back then, the name *libreboot* didn\'t exist; the project was nameless, +referring to itself as a *deblobbed version of coreboot*. The project +named itself libreboot at some point during early 2014, and has since +rapidly expanded to support more hardware and become more user-friendly. + +Libreboot is a [coreboot](http://coreboot.org/) distribution (distro) +with proprietary software removed, intended to be a +[free](https://en.wikipedia.org/wiki/Free_software) (libre) \'BIOS\' +replacement for your computer. The project is aimed at users, attempting +to make coreboot as easy to use as possible. + +Libreboot has many practical advantages over proprietary boot firmware, +such as faster boot speeds and better security. You can [install +GNU+Linux with encrypted /boot/](gnulinux/), [verify GPG signatures on +your kernel](http://www.coreboot.org/GRUB2#signed_kernels), put a kernel +in the flash chip and more. + +The libreboot project has three main goals: +------------------------------------------- + +- ***Recommend and distribute only free software***. Coreboot + distributes certain pieces of proprietary software which is needed + on some systems. Examples can include things like CPU microcode + updates, memory initialization blobs and so on. The coreboot project + sometimes recommends adding more blobs which it does not distribute, + such as the Video BIOS or Intel\'s *Management Engine*. However, a + lot of dedicated and talented individuals in coreboot work hard to + replace these blobs whenever possible. +- ***Support as much hardware as possible!*** Libreboot supports less + hardware than coreboot, because most systems from coreboot still + require certain proprietary software to work properly. Libreboot is + an attempt to support as much hardware as possible, without any + proprietary software. +- ***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.\ + \ + 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.\ + \ + 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.\ + \ + 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 + wanted to do that (for whatever reason). + +Libreboot is a coreboot distribution, not a coreboot fork +--------------------------------------------------------- + +Libreboot is not a fork of coreboot. Every so often, the project +re-bases on the latest version of coreboot, with the number of custom +patches in use minimized. + +All new coreboot development should be done in coreboot (upstream), not +libreboot! Libreboot is about deblobbing and packaging coreboot in a +user-friendly way, where most work is already done for the user. + +For example, if you wanted to add a new board to libreboot, you should +add it to coreboot first. Libreboot will automatically receive your code +at a later date, when it updates itself. + +The deblobbed coreboot tree used in libreboot is referred to as +*coreboot-libre*, to distinguish it as a component of *libreboot*. + +Libreboot is a \'stable\' version of coreboot +--------------------------------------------- + +- Coreboot uses the [rolling + release](https://en.wikipedia.org/wiki/Rolling_release) model, which + means that it is not guaranteed to be stable, or to even work at all + on a given day. Coreboot does have a strict code review process, but + being such a large project with so many contributors, regressions + are always possible. +- Libreboot freezes on a particular revision of coreboot, making sure + that everything works properly, making fixes on top of that and + repeating this during each subsequent update to a later version of + coreboot. By doing this, it provides a stronger guarantee to the + user that the firmware will be reliable, and not break their system. + +[Back to top of page.](#pagetop) + +</div> + +<div id="version" class="section"> + +How do I know what version I\'m running? +======================================== + +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**\ +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 +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**\ +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. + +For git, it\'s easy. Just check the git log. + +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**\ +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 +numbers are dated, and the release archives are typically built on the +same day as the release; you can correlate that with the release +information in [release.html](release.html). + +For 20160818, note that the lbversion file was missing from CBFS on GRUB +images. You can still find out what libreboot version you have by +comparing checksums of image dumps (with the descriptor blanked out with +00s, and the same done to the ROMs from the release archive, if you are +on a GM45 laptop). + +There may also be a ChangeLog file included in your release archive, so +that you can look in there to figure out what version you have. + +You can also check the documentation that came with your archives, and +in *docs/release.html* will be the information about the version of +libreboot that you are using. + +Generally speaking, it is advisable to use the latest version of +libreboot. + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/bbb_setup.html b/docs/install/bbb_setup.html deleted file mode 100644 index fee34c8b..00000000 --- a/docs/install/bbb_setup.html +++ /dev/null @@ -1,478 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>How to program an SPI flash chip with the BeagleBone Black or Teensy 3.1</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">How to program an SPI flash chip with the BeagleBone Black or Teensy 3.1</h1> - <p> - This document exists as a guide for reading from or writing to an SPI flash chip with the BeagleBone Black, - using the <a href="http://flashrom.org/Flashrom">flashrom</a> software. - A BeagleBone Black, rev. C was used when creating this guide, but earlier revisions - may also work. - </p> - - <p> - <strong> - NOTE: this documentation may be outdated, and discusses - configuring SPI flashing on the default Debian system that the BBB - sometimes comes with. If you want an easier time, just use - <a href="https://www.coreboot.org/BBB_screwdriver">BBB ScrewDriver</a> - which comes pre-configured. - </strong> - </p> - <p> - <strong> - This guide is written for Debian Wheezy 7.5, which is what came on - the BBB at the time this guide was written. This one: - <a href="https://debian.beagleboard.org/images/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz">https://debian.beagleboard.org/images/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz</a> - </strong> - </p> - - <p> - There was no justification for a further section for the Teensy. Simply refer to <a href="https://www.flashrom.org/Teensy_3.1_SPI_%2B_LPC/FWH_Flasher#ISP_Usage">this page on flashrom.org</a> for information about how to set it up, and correlate that with the pins on the SPI flash chip as per other guides in the libreboot documentation for each board. At the time of writing, the teensy is tested for flashing on the ThinkPad X200, but it should work for other targets. here is a photo of the setup for the teensy: <a href="http://h5ai.swiftgeek.net/IMG_20160601_120855.jpg">http://h5ai.swiftgeek.net/IMG_20160601_120855.jpg</a></p> - <p> - Onto the Beaglebone black... - </p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section" id="hardware_requirements"> - - <h1>Hardware requirements</h1> - - <p> - Shopping list (pictures of this hardware is shown later): - </p> - <ul> - <li> - A <a href="http://flashrom.org">Flashrom</a>-compatible external SPI programmer: - <strong>BeagleBone Black</strong>, sometimes referred to as 'BBB', (rev. C) is highly recommended. - You can buy one from <a href="https://www.adafruit.com">Adafruit</a> (USA), <a href="http://electrokit.com">ElectroKit</a> (Sweden) - or any of the distributors listed <a href="http://beagleboard.org/black">here</a> (look below 'Purchase'). - We recommend this product because we know that it works well for our purposes and doesn't require any non-free software. - </li> - <li> - Electrical/insulative tape: cover the entire bottom surface of the BBB (the part that rests on a surface). - This is important, when placing the BBB on top of a board so that nothing shorts. - Most hardware/electronics stores have this. Optionally, you can use the bottom half of a - <a href="http://www.hammondmfg.com/1593HAM.htm#BeagleBoneBlack">hammond plastic enclosure</a>. - </li> - <li> - Clip for connecting to the flash chip: if you have a SOIC-16 flash chip (16 pins), you will need the - <strong>Pomona 5252</strong> or equivalent. For SOIC-8 flash chips (8 pins), you will need the <strong>Pomona 5250</strong> - or equivalent. Do check which chip you have, before ordering a clip. Also, you might as well buy two clips or more since they break easily. - <a href="http://farnell.com/">Farnell element 14</a> sells these and ships to many countries. Some people find these clips difficult to - get hold of, especially in South America. If you know of any good suppliers, please contact the libreboot project with the relevant information. - <strong>If you can't get hold of a pomona clip, some other clips might work, e.g. 3M, but they are not always reliable. - You can also directly solder the wires to the chip, if that suits you; the clip is just for convenience, really.</strong> - </li> - <li> - <strong>External 3.3V DC power supply</strong>, for powering the flash chip: an ATX power supply / PSU (common on Intel/AMD desktop - computers) will work for this. A lab PSU (DC) will also work (adjusted to 3.3V). - <ul> - <li>Getting a multimeter might be worthwhile, to verify that it's supplying 3.3V.</li> - </ul> - </li> - <li> - <strong>External 5V DC power supply</strong> (barrel connector), for powering the BBB: - the latter can have power supplied via USB, but a dedicated power supply is recommended. - These should be easy to find in most places that sell electronics. <strong>OPTIONAL. - Only needed if not powering with the USB cable, or if you want to use <a href="../misc/bbb_ehci.html">EHCI debug</a></strong>. - </li> - <li> - <strong>Pin header / jumper cables</strong> (2.54mm / 0.1" headers): you should get male--male, - male--female and female--female cables in 10cm size. Just get a load of them. - Other possible names for these cables/wires/leads are as follows: - <ul> - <li>flying leads</li> - <li>breadboard cables (since they are often used on breadboards).</li> - <li>You might also be able to make these cables yourself.</li> - </ul> - <a href="https://www.adafruit.com">Adafruit</a> sell them, as do many others. - <strong>Some people find them difficult to buy. Please contact the libreboot project if you know of any good sellers.</strong> - You might also be able to make these cables yourself. For PSU connections, using long cables, e.g. 20cm, is fine, and you can extend them longer than that if needed. - </li> - <li> - <b>Mini USB A-B cable</b> (the BeagleBone probably already comes - with one.) - <b>OPTIONAL - only needed for <a href="../misc/bbb_ehci.html">EHCI debug</a> or for serial/ssh access without ethernet cable (g_multi kernel module)</b> - </li> - <li> - <strong>FTDI TTL cable or debug board</strong>: used for accessing the serial console on the BBB. - <a href="http://elinux.org/Beagleboard:BeagleBone_Black_Serial">This page</a> contains a list. - <strong>OPTIONAL---only needed for serial console on the BBB, if not using SSH via ethernet cable.</strong> - </li> - </ul> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section" id="psu33"> - - <h1>Setting up the 3.3V DC PSU</h1> - - <p> - ATX PSU pinouts can be read on <a href="https://en.wikipedia.org/wiki/Power_supply_unit_%28computer%29#Wiring_diagrams">this Wikipedia page</a>. - </p> - <p> - 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 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). - </p> - <p> - <strong>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).</strong> - </p> - <p> - You only need one 3.3V supply and one ground for the flash chip, after grounding PS_ON#. - </p> - - <p> - 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 header cables to the connector on the ATX PSU, use a female end attached 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. - </p> - - <p> - Here is an example set up:<br/> - <img src="images/x200/psu33.jpg" alt="" title="Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net> see license notice at the end of this document" /> - </p> - - </div> - - <div class="section" id="bbb_access"> - - <h1>Accessing the operating system on the BBB</h1> - <p> - The operating system on your BBB will probably have an SSH daemon - running where the root account has no password. Use SSH to access - the operating system and set a root password. By default, the OS - on your BBB will most likely use DHCP, so it should already have an IP - address. - </p> - <p> - You will also be using the OS on your BBB for programming an SPI flash chip. - </p> - <h2>Alternatives to SSH (in case SSH fails)</h2> - <p> - You can also use a serial FTDI debug board with GNU Screen, to access the serial console.<br/> - # <b>screen /dev/ttyUSB0 115200</b><br/> - Here are some example photos:<br/> - <img src="images/x200/ftdi.jpg" alt="" /> - <img src="images/x200/ftdi_port.jpg" alt="" /><br/> - </p> - <p> - 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:<br/> - # <b>screen /dev/ttyACM0 115200</b> - </p> - <p> - You can also access the uboot console, using the serial method - instead of SSH. - </p> - - </div> - - <div class="section" id="spidev"> - - <h1>Setting up spidev on the BBB</h1> - - <p> - Log on as root on the BBB, using either SSH or a serial console as defined in - <a href="#bbb_access">#bbb_access</a>. Make sure that you have internet access - on your BBB. - </p> - - <p> - Follow the instructions at <a href="http://elinux.org/BeagleBone_Black_Enable_SPIDEV#SPI0">http://elinux.org/BeagleBone_Black_Enable_SPIDEV#SPI0</a> - up to (and excluding) the point where it tells you to modify uEnv.txt - </p> - <p> - You need to update the software on the BBB first. If you have an - element14 brand BBB (sold by Premier Farnell plc. stores like - Farnell element14, Newark element14, and Embest), you may need - to <a href="https://groups.google.com/forum/?_escaped_fragment_=msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ#!msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ">work around a bug</a> - in the LED aging init script before you can update your - software. If you don't have a file named - /etc/init.d/led_aging.sh, you can skip this step and update your - software as described below. Otherwise, replace the contents of - this file with: - </p> -<pre> -#!/bin/sh -e -### BEGIN INIT INFO -# Provides: led_aging.sh -# Required-Start: $local_fs -# Required-Stop: $local_fs -# Default-Start: 2 3 4 5 -# Default-Stop: 0 1 6 -# Short-Description: Start LED aging -# 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 - /usr/bin/led_acc & -fi -</pre> - </p> - Run <b>apt-get update</b> and <b>apt-get upgrade</b> then reboot the BBB, before continuing. - </p> - - <p> - Check that the firmware exists:<br/> - # <b>ls /lib/firmware/BB-SPI0-01-00A0.*</b><br/> - Output: - </p> -<pre> -/lib/firmware/BB-SPI0-01-00A0.dtbo -</pre> - <p> - Then:<br/> - # <b>echo BB-SPI0-01 > /sys/devices/bone_capemgr.*/slots</b><br/> - # <b>cat /sys/devices/bone_capemgr.*/slots</b><br/> - Output: - </p> -<pre> - 0: 54:PF--- - 1: 55:PF--- - 2: 56:PF--- - 3: 57:PF--- - 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G - 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 -</pre> - - <p> - Verify that the spidev device now exists:<br/> - # <b>ls -al /dev/spid*</b><br/> - Output: - </p> -<pre> -crw-rw---T 1 root spi 153, 0 Nov 19 21:07 /dev/spidev1.0 -</pre> - <p> - Now the BBB is ready to be used for flashing. Make this persist - across reboots:<br/> - In /etc/default/capemgr add <b>CAPE=BB-SPI0-01</b> at the end - (or change the existing <b>CAPE=</b> entry to say that, if an - entry already exists. - </p> - <p> - Get flashrom from the libreboot_util release archive, or build it from libreboot_src/git if you need to. - An ARM binary (statically compiled) for flashrom exists in libreboot_util releases. Put the flashrom binary - on your BBB. - </p> - <p> - You may also need ich9gen, if you will be flashing an ICH9-M laptop (such as the X200). Get it from libreboot_util, - or build it from libreboot_src, and put the ARM binary for it on your BBB. - </p> - <p> - Finally, get the ROM image that you would like to flash and put that on your BBB. - </p> - - <p> - Now test flashrom:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512</b><br/> - Output: - </p> -<pre> -Calibrating delay loop... OK. -No EEPROM/flash device found. -Note: flashrom can never write if the flash chip isn't found automatically. -</pre> - - <p> - This means that it's working (the clip isn't connected to any flash chip, - so the error is fine). - </p> - - </div> - - <div class="section" id="clip"> - - <h1> - Connecting the Pomona 5250/5252 - </h1> - <p> - Use this image for reference when connecting the pomona to the BBB: - <a href="http://beagleboard.org/Support/bone101#headers">http://beagleboard.org/Support/bone101#headers</a> - (D0 = MISO or connects to MISO). - </p> - - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-16 (clip: Pomona 5252): - </p> -<pre> - NC - - 21 - 1 - - 17 - NC - - NC - NC - - NC - NC - - NC - NC - - NC - 18 - - 3.3V (PSU) - 22 - - NC - this is pin 1 on the flash chip -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> - -You may also need to connect pins 1 and 9 (tie to 3.3V supply). These are HOLD# and WP#. -On some systems they are held high, if the flash chip is attached to the board. -If you're flashing a chip that isn't connected to a board, you'll almost certainly -have to connect them. - -SOIC16 pinout (more info available online, or in the datasheet for your flash chip): -HOLD 1-16 SCK -VDD 2-15 MOSI -N/C 3-14 N/C -N/C 4-13 N/C -N/C 5-12 N/C -N/C 6-11 N/C -SS 7-10 GND -MISO 8-9 WP -</pre> - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): - </p> -<pre> - 18 - - 1 - 22 - - NC - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> - -You may also need to connect pins 3 and 7 (tie to 3.3V supply). These are HOLD# and WP#. -On some systems they are held high, if the flash chip is attached to the board. -If you're flashing a chip that isn't connected to a board, you'll almost certainly -have to connect them. - -SOIC8 pinout (more info available online, or in the datasheet for your flash chip): -SS 1-8 VDD -MISO 2-7 HOLD -WP 3-6 SCK -GND 4-5 MOSI -</pre> - <p> - <b>NC = no connection</b> - </p> - <p> - <b><u>DO NOT</u> connect 3.3V (PSU) yet. ONLY connect this once the pomona is connected to the flash chip.</b> - </p> - <p> - <b>You also need to connect the BLACK wire (ground/earth) from the 3.3V PSU to pin 2 on the BBB (P9 header). - It is safe to install this now - (that is, before you connect the pomona to the flash chip); in fact, you should.</b> - </p> - <p> - if you need to extend the 3.3v psu leads, just use the same colour M-F leads, <b>but</b> keep all other - leads short (10cm or less) - </p> - - <p> - You should now have something that looks like this:<br/> - <img src="images/x200/5252_bbb0.jpg" alt="" /> - <img src="images/x200/5252_bbb1.jpg" alt="" /> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="stability">Notes about stability</h1> - - <p> - <a href="http://flashrom.org/ISP">http://flashrom.org/ISP</a> - is what we typically do in libreboot, though 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. - </p> - - <p> - tty0_ in #libreboot was able to get better flashing speeds with the following configuration: - </p> - <ul> - <li>"coax" with 0.1 mm core and aluminum foley (from my kitchen), add 100 Ohm resistors (serial)</li> - <li>put heatshrink above the foley, for: CS, CLK, D0, D1</li> - <li>Twisted pair used as core (in case more capacitors are needed)</li> - <li> - See this image: - <a href="http://i.imgur.com/qHGxKpj.jpg">http://i.imgur.com/qHGxKpj.jpg</a> - </li> - <li>He was able to flash at 50MHz (lower speeds are also fine).</li> - </ul> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net><br/> - Copyright © 2015 Albin Söderqvist<br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md new file mode 100644 index 00000000..8471cad9 --- /dev/null +++ b/docs/install/bbb_setup.md @@ -0,0 +1,414 @@ +<div class="section"> + +How to program an SPI flash chip with the BeagleBone Black or Teensy 3.1 {#pagetop} +======================================================================== + +This document exists as a guide for reading from or writing to an SPI +flash chip with the BeagleBone Black, using the +[flashrom](http://flashrom.org/Flashrom) software. A BeagleBone Black, +rev. C was used when creating this guide, but earlier revisions may also +work. + +**NOTE: this documentation may be outdated, and discusses configuring +SPI flashing on the default Debian system that the BBB sometimes comes +with. If you want an easier time, just use [BBB +ScrewDriver](https://www.coreboot.org/BBB_screwdriver) which comes +pre-configured.** + +**This guide is written for Debian Wheezy 7.5, which is what came on the +BBB at the time this guide was written. This one: +<https://debian.beagleboard.org/images/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz>** + +There was no justification for a further section for the Teensy. Simply +refer to [this page on +flashrom.org](https://www.flashrom.org/Teensy_3.1_SPI_%2B_LPC/FWH_Flasher#ISP_Usage) +for information about how to set it up, and correlate that with the pins +on the SPI flash chip as per other guides in the libreboot documentation +for each board. At the time of writing, the teensy is tested for +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\... + +[Back to previous index](./) + +</div> + +<div id="hardware_requirements" class="section"> + +Hardware requirements +===================== + +Shopping list (pictures of this hardware is shown later): + +- A [Flashrom](http://flashrom.org)-compatible external SPI + programmer: **BeagleBone Black**, sometimes referred to as \'BBB\', + (rev. C) is highly recommended. You can buy one from + [Adafruit](https://www.adafruit.com) (USA), + [ElectroKit](http://electrokit.com) (Sweden) or any of the + distributors listed [here](http://beagleboard.org/black) (look below + \'Purchase\'). We recommend this product because we know that it + works well for our purposes and doesn\'t require any non-free + software. +- Electrical/insulative tape: cover the entire bottom surface of the + BBB (the part that rests on a surface). This is important, when + placing the BBB on top of a board so that nothing shorts. Most + hardware/electronics stores have this. Optionally, you can use the + bottom half of a [hammond plastic + enclosure](http://www.hammondmfg.com/1593HAM.htm#BeagleBoneBlack). +- Clip for connecting to the flash chip: if you have a SOIC-16 flash + chip (16 pins), you will need the **Pomona 5252** or equivalent. For + SOIC-8 flash chips (8 pins), you will need the **Pomona 5250** or + equivalent. Do check which chip you have, before ordering a clip. + Also, you might as well buy two clips or more since they break + easily. [Farnell element 14](http://farnell.com/) sells these and + ships to many countries. Some people find these clips difficult to + get hold of, especially in South America. If you know of any good + suppliers, please contact the libreboot project with the relevant + information. **If you can\'t get hold of a pomona clip, some other + clips might work, e.g. 3M, but they are not always reliable. You can + also directly solder the wires to the chip, if that suits you; the + clip is just for convenience, really.** +- **External 3.3V DC power supply**, for powering the flash chip: an + ATX power supply / PSU (common on Intel/AMD desktop computers) will + work for this. A lab PSU (DC) will also work (adjusted to 3.3V). + - Getting a multimeter might be worthwhile, to verify that it\'s + supplying 3.3V. +- **External 5V DC power supply** (barrel connector), for powering the + BBB: the latter can have power supplied via USB, but a dedicated + power supply is recommended. These should be easy to find in most + places that sell electronics. **OPTIONAL. Only needed if not + powering with the USB cable, or if you want to use [EHCI + debug](../misc/bbb_ehci.html)**. +- **Pin header / jumper cables** (2.54mm / 0.1\" headers): you should + get male\--male, male\--female and female\--female cables in 10cm + size. Just get a load of them. Other possible names for these + cables/wires/leads are as follows: + - flying leads + - breadboard cables (since they are often used on breadboards). + - You might also be able to make these cables yourself. + + [Adafruit](https://www.adafruit.com) sell them, as do many others. + **Some people find them difficult to buy. Please contact the + libreboot project if you know of any good sellers.** You might also + be able to make these cables yourself. For PSU connections, using + long cables, e.g. 20cm, is fine, and you can extend them longer than + that if needed. +- **Mini USB A-B cable** (the BeagleBone probably already comes with + one.) - **OPTIONAL - only needed for [EHCI + debug](../misc/bbb_ehci.html) or for serial/ssh access without + ethernet cable (g\_multi kernel module)** +- **FTDI TTL cable or debug board**: used for accessing the serial + console on the BBB. [This + page](http://elinux.org/Beagleboard:BeagleBone_Black_Serial) + contains a list. **OPTIONAL\-\--only needed for serial console on + the BBB, if not using SSH via ethernet cable.** + +[Back to top of page.](#pagetop) + +</div> + +<div id="psu33" class="section"> + +Setting up the 3.3V DC PSU +========================== + +ATX PSU pinouts can be read on [this Wikipedia +page](https://en.wikipedia.org/wiki/Power_supply_unit_%28computer%29#Wiring_diagrams). + +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 +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). + +**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\#. + +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 +header cables to the connector on the ATX PSU, use a female end attached +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:\ +![](images/x200/psu33.jpg "Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net> see license notice at the end of this document") + +</div> + +<div id="bbb_access" class="section"> + +Accessing the operating system on the BBB +========================================= + +The operating system on your BBB will probably have an SSH daemon +running where the root account has no password. Use SSH to access the +operating system and set a root password. By default, the OS on your BBB +will most likely use DHCP, so it should already have an IP address. + +You will also be using the OS on your BBB for programming an SPI flash +chip. + +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:\ + \ + +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** + +You can also access the uboot console, using the serial method instead +of SSH. + +</div> + +<div id="spidev" class="section"> + +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 +internet access on your BBB. + +Follow the instructions at +<http://elinux.org/BeagleBone_Black_Enable_SPIDEV#SPI0> up to (and +excluding) the point where it tells you to modify uEnv.txt + +You need to update the software on the BBB first. If you have an +element14 brand BBB (sold by Premier Farnell plc. stores like Farnell +element14, Newark element14, and Embest), you may need to [work around a +bug](https://groups.google.com/forum/?_escaped_fragment_=msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ#!msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ) +in the LED aging init script before you can update your software. If you +don\'t have a file named /etc/init.d/led\_aging.sh, you can skip this +step and update your software as described below. Otherwise, replace the +contents of this file with: + + #!/bin/sh -e + ### BEGIN INIT INFO + # Provides: led_aging.sh + # Required-Start: $local_fs + # Required-Stop: $local_fs + # Default-Start: 2 3 4 5 + # Default-Stop: 0 1 6 + # Short-Description: Start LED aging + # 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 + /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.\***\ +Output: + + /lib/firmware/BB-SPI0-01-00A0.dtbo + +Then:\ +\# **echo BB-SPI0-01 > /sys/devices/bone\_capemgr.\*/slots**\ +\# **cat /sys/devices/bone\_capemgr.\*/slots**\ +Output: + + 0: 54:PF--- + 1: 55:PF--- + 2: 56:PF--- + 3: 57:PF--- + 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G + 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\***\ +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:\ +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. + +Get flashrom from the libreboot\_util release archive, or build it from +libreboot\_src/git if you need to. An ARM binary (statically compiled) +for flashrom exists in libreboot\_util releases. Put the flashrom binary +on your BBB. + +You may also need ich9gen, if you will be flashing an ICH9-M laptop +(such as the X200). Get it from libreboot\_util, or build it from +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**\ +Output: + + Calibrating delay loop... OK. + No EEPROM/flash device found. + Note: flashrom can never write if the flash chip isn't found automatically. + +This means that it\'s working (the clip isn\'t connected to any flash +chip, so the error is fine). + +</div> + +<div id="clip" class="section"> + +Connecting the Pomona 5250/5252 +=============================== + +Use this image for reference when connecting the pomona to the BBB: +<http://beagleboard.org/Support/bone101#headers> (D0 = MISO or connects +to MISO). + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-16 (clip: Pomona 5252): + + NC - - 21 + 1 - - 17 + NC - - NC + NC - - NC + NC - - NC + NC - - NC + 18 - - 3.3V (PSU) + 22 - - NC - this is pin 1 on the flash chip + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + + You may also need to connect pins 1 and 9 (tie to 3.3V supply). These are HOLD# and WP#. + On some systems they are held high, if the flash chip is attached to the board. + If you're flashing a chip that isn't connected to a board, you'll almost certainly + have to connect them. + + SOIC16 pinout (more info available online, or in the datasheet for your flash chip): + HOLD 1-16 SCK + VDD 2-15 MOSI + N/C 3-14 N/C + N/C 4-13 N/C + N/C 5-12 N/C + N/C 6-11 N/C + SS 7-10 GND + MISO 8-9 WP + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-8 (clip: Pomona 5250): + + 18 - - 1 + 22 - - NC + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + + You may also need to connect pins 3 and 7 (tie to 3.3V supply). These are HOLD# and WP#. + On some systems they are held high, if the flash chip is attached to the board. + If you're flashing a chip that isn't connected to a board, you'll almost certainly + have to connect them. + + SOIC8 pinout (more info available online, or in the datasheet for your flash chip): + SS 1-8 VDD + MISO 2-7 HOLD + WP 3-6 SCK + GND 4-5 MOSI + +**NC = no connection** + +**DO NOT connect 3.3V (PSU) yet. ONLY connect this once the pomona is +connected to the flash chip.** + +**You also need to connect the BLACK wire (ground/earth) from the 3.3V +PSU to pin 2 on the BBB (P9 header). It is safe to install this now +(that is, before you connect the pomona to the flash chip); in fact, you +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:\ +  + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Notes about stability {#stability} +===================== + +<http://flashrom.org/ISP> is what we typically do in libreboot, though +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 +following configuration: + +- \"coax\" with 0.1 mm core and aluminum foley (from my kitchen), add + 100 Ohm resistors (serial) +- put heatshrink above the foley, for: CS, CLK, D0, D1 +- Twisted pair used as core (in case more capacitors are needed) +- See this image: <http://i.imgur.com/qHGxKpj.jpg> +- He was able to flash at 50MHz (lower speeds are also fine). + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/c201.html b/docs/install/c201.html deleted file mode 100644 index b009c6bd..00000000 --- a/docs/install/c201.html +++ /dev/null @@ -1,336 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ASUS Chromebook C201 installation guide</title> -</head> - -<body> - - <div class="section"> - - <h1 id="pagetop">ASUS Chromebook C201 installation guide</h1> - - <p> - 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. - </p> - - <div class="important"> - - <p> - <b>If you are using libreboot_src or git, then make sure that you built the sources first (see <a href="../git/#build">../git/#build</a>).</b> - </p> - - </div> - - <p> - Look at the <a href="#rom">list of ROM images</a> to see which image is compatible with your device. - </p> - - <p> - Libreboot can be installed internally from the device, with sufficient privileges. - The installation process requires using <b>Google's modified version of flashrom</b>, - that has support for reflashing the Chromebook's SPI flash. - Otherwise, flashing externally will work with the upstream flashrom version. - </p> - - <p> - <b>Google's modified version of flashrom</b> is free software and its source code is made available by Google: <a href="https://chromium.googlesource.com/chromiumos/third_party/flashrom/">flashrom</a>.<br /> - It is not distributed along with Libreboot yet. However, it is preinstalled on the device, with ChromeOS. - </p> - - <p> - Installing Libreboot internally requires sufficient privileges on the system installed on the device.<br /> - 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. - </p> - - <ul> - <li><a href="#root_chromeos">Gaining root privileges on ChromeOS</a></li> - <li><a href="#preparing_device">Preparing the device for the installation</a> - <ul> - <li><a href="#configuring_verified_boot_parameters">Configuring verified boot parameters</a></li> - <li><a href="#removing_write_protect_screw">Removing the write protect screw</a></li> - </ul> - </li> - <li><a href="">Installing Libreboot to the SPI flash</a> - <ul> - <li><a href="#installing_libreboot_internally">Installing Libreboot internally, from the device</a></li> - <li><a href="#installing_libreboot_externally">Installing Libreboot externally, with a SPI flash programmer</a></li> - </ul> - </li> - <li> - <a href="#debian">Debian GNU+Linux is recommended for this device</a> (TODO: instructions for Devuan) - </i> - </ul> - - <p> - <a href="../">Back to main index</a> - </p> - - </div> - - <div class="section"> - - <h1 id="root_chromeos">Gaining root privileges on ChromeOS</h2> - - <p> - 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. - </p> - - <div class="important"> - - <p> - Instructions to access the <a href="../depthcharge/#recovery_mode_screen">recovery mode screen</a> and <a href="../depthcharge/#enabling_developer_mode">enabling developer mode</a> are available on the page dedicated to <a href="../depthcharge/">depthcharge</a>. - </p> - - <p> - Once developer mode is enabled, the device will boot to the <a href="../depthcharge/#developer_mode_screen">developer mode screen</a>. ChromeOS can be booted by waiting for 30 seconds (the delay is shortened in Libreboot) or by pressing <b>Ctrl + D</b> - </p> - - <p> - After the system has booted, root access can be enabled by clicking on the <b>Enable debugging features</b> link. A confirmation dialog will ask whether to proceed.<br /> - After confirming by clicking <b>Proceed</b>, the device will reboot and ask for the root password to set. Finally, the operation has to be confirmed by clicking <b>Enable</b>. - </p> - - <p> - After setting the root password, it becomes possible to log-in as root. - A tty prompt can be obtained by pressing <strong>Ctrl + Alt + Next</strong>. - The <strong>Next</strong> key is the one on the top left of the keyboard. - </p> - - </div> - - </div> - - <div class="section"> - - <h1 id="preparing_device">Preparing the device for the installation</h2> - - <p> - 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. - </p> - - <div class="subsection"> - - <h2 id="configuring_verified_boot_parameters">Configuring verified boot parameters</h2> - - <p> - It is recommended to have access to the <a href="../depthcharge/#developer_mode_screen">developer mode screen</a> and to <a href="../depthcharge/#configuring_verified_boot_parameters">configure the following verified boot parameters</a>: - <ul> - <li>Kernels signature verification: <i>disabled</i></li> - <li>External media boot: <i>enabled</i></li> - </ul> - Those changes can be reverted later, when the device is known to be in a working state. - </p> - - </div> - - <div class="subsection"> - - <h2 id="removing_write_protect_screw">Removing the write protect screw</h2> - - <p> - Since part of the SPI flash is write-protected by a screw, it is necessary to remove the screw to remove the write protection and allow writing Libreboot to the <i>read-only</i> part of the flash. - </p> - - <p> - To access the screw, the device has to be opened. There are 8 screws to remove from the bottom of the device, as shown on the picture below. Two are hidden under the top pads. After removing the screws, the keyboard plastic part can be carefully detached from the rest. <strong>Beware: there are cables attached to it!</strong> It is advised to flip the keyboard plastic part over, as shown on the picture below. The write protect screw is located next to the SPI flash chip, circled in red in the picture below. It has to be removed. - </p> - - <p> - <a href="images/c201/screws.jpg"><img src="images/c201/screws.jpg" alt="Screws" style="width: 400px;"/></a> - <a href="images/c201/wp-screw.jpg"><img src="images/c201/wp-screw.jpg" alt="WP screw" style="width: 400px;"/></a> - </p> - - <p> - The write protect screw can be put back in place later, when the device is known to be in a working state. - </p> - - </div> - - </div> - - <div class="section"> - - <h1 id="installing_libreboot_spi_flash">Installing Libreboot to the SPI flash</h1> - - <p> - The SPI flash (that holds Libreboot) is divided into various partitions that are used to implement parts of the CrOS security system. - Libreboot is installed in the <i>read-only</i> coreboot partition, that becomes writable after removing the write-protect screw. - </p> - - <div class="subsection"> - - <h2 id="installing_libreboot_internally">Installing Libreboot internally, from the device</h2> - - <p> - Before installing Libreboot to the SPI flash internally, the device has to be reassembled. - </p> - - <p> - All the files from the <b>veyron_speedy</b> release (or build) have to be transferred to the device. - </p> - - <p> - The following operations have to be executed with root privileges on the device (e.g. using the <em>root</em> account). - In addition, the <b>cros-flash-replace</b> script has to be made executable:<br /> - # <b>chmod a+x cros-flash-replace</b><br /> - </p> - - <p> - The SPI flash has to be read first:<br /> - # <b>flashrom -p host -r flash.img</b><br /> - <b>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.</b> - </p> - - <p> - Then, the <b>cros-flash-replace</b> script has to be executed as such:<br /> - # <b>./cros-flash-replace flash.img coreboot ro-frid</b><br /> - If any error is shown, it is definitely a bad idea to go further than this point. - </p> - - <p> - The resulting flash image can then be flashed back:<br /> - # <b>flashrom -p host -w flash.img</b><br /> - </p> - - <p> - You should also see within the output the following:<br/> - <b>"Verifying flash... VERIFIED."</b> - </p> - - <p> - Shut down. The device will now boot to Libreboot. - </p> - - </div> - - <div class="subsection"> - - <h2 id="installing_libreboot_externally">Installing Libreboot externally, with a SPI flash programmer</h2> - - <p> - Before installing Libreboot to the SPI flash internally, the device has to be opened. - </p> - - <p> - 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 <b>WP#</b> 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 the right and has colorful cables, as shown on the picture below. - </p> - - <p> - <a href="images/c201/spi-flash-layout.jpg"><img src="images/c201/spi-flash-layout.jpg" alt="SPI flash layout" style="width: 400px;"/></a> - <a href="images/c201/battery-connector.jpg"><img src="images/c201/battery-connector.jpg" alt="Battery connector" style="width: 400px;"/></a> - </p> - - <p> - All the files from the <b>veyron_speedy</b> release (or build) have to be transferred to the host. - </p> - - <p> - The following operations have to be executed with root privileges on the host (e.g. using the <em>root</em> account). - In addition, the <b>cros-flash-replace</b> script has to be made executable:<br /> - # <b>chmod a+x cros-flash-replace</b><br /> - </p> - - <p> - The SPI flash has to be read first (using the right spi programmer):<br /> - # <b>flashrom -p <i>programmer</i> -r flash.img</b><br /> - <b>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.</b> - </p> - - <p> - Then, the <b>cros-flash-replace</b> script has to be executed as such:<br /> - # <b>./cros-flash-replace flash.img coreboot ro-frid</b><br /> - If any error is shown, it is definitely a bad idea to go further than this point. - </p> - - <p> - The resulting flash image can then be flashed back (using the right spi programmer):<br /> - # <b>flashrom -p <i>programmer</i> -w flash.img</b><br /> - </p> - - <p> - You should also see within the output the following:<br/> - <b>"Verifying flash... VERIFIED."</b> - </p> - - <p> - The device will now boot to Libreboot. - </p> - - </div> - - <h2 id="debian"> - Debian GNU+Linux - </h2> - <p> - You might consider replacing ChromeOS with a free distro. - We have a <a href="../distros/">list of recommended distributions</a> - but Debian is recommended for this device (which is on that list). - TODO: Devuan instructions. - </p> - <p> - See <a href="https://wiki.debian.org/InstallingDebianOn/Asus/C201">https://wiki.debian.org/InstallingDebianOn/Asus/C201</a>. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - </div> - - <div class="section"> - - <p> - Copyright © 2015 Paul Kocialkowski <contact@paulk.fr><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/c201.md b/docs/install/c201.md new file mode 100644 index 00000000..9774e335 --- /dev/null +++ b/docs/install/c201.md @@ -0,0 +1,290 @@ +<div class="section"> + +ASUS Chromebook C201 installation guide {#pagetop} +======================================= + +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. + +<div class="important"> + +**If you are using libreboot\_src or git, then make sure that you built +the sources first (see [../git/\#build](../git/#build)).** + +</div> + +Look at the [list of ROM images](#rom) to see which image is compatible +with your device. + +Libreboot can be installed internally from the device, with sufficient +privileges. The installation process requires using **Google\'s modified +version of flashrom**, that has support for reflashing the Chromebook\'s +SPI flash. Otherwise, flashing externally will work with the upstream +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/).\ +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.\ +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. + +- [Gaining root privileges on ChromeOS](#root_chromeos) +- [Preparing the device for the installation](#preparing_device) + - [Configuring verified boot + parameters](#configuring_verified_boot_parameters) + - [Removing the write protect + screw](#removing_write_protect_screw) +- [Installing Libreboot to the SPI flash]() + - [Installing Libreboot internally, from the + device](#installing_libreboot_internally) + - [Installing Libreboot externally, with a SPI flash + programmer](#installing_libreboot_externally) +- [Debian GNU+Linux is recommended for this device](#debian) (TODO: + instructions for Devuan) + +[Back to main index](../) + +</div> + +<div class="section"> + +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. + +<div class="important"> + +Instructions to access the [recovery mode +screen](../depthcharge/#recovery_mode_screen) and [enabling developer +mode](../depthcharge/#enabling_developer_mode) are available on the page +dedicated to [depthcharge](../depthcharge/). + +Once developer mode is enabled, the device will boot to the [developer +mode screen](../depthcharge/#developer_mode_screen). ChromeOS can be +booted by waiting for 30 seconds (the delay is shortened in Libreboot) +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.\ +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**. + +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. + +</div> + +</div> + +<div class="section"> + +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. + +<div class="subsection"> + +Configuring verified boot parameters {#configuring_verified_boot_parameters} +------------------------------------ + +It is recommended to have access to the [developer mode +screen](../depthcharge/#developer_mode_screen) and to [configure the +following verified boot +parameters](../depthcharge/#configuring_verified_boot_parameters): + +- Kernels signature verification: *disabled* +- External media boot: *enabled* + +Those changes can be reverted later, when the device is known to be in a +working state. + +</div> + +<div class="subsection"> + +Removing the write protect screw {#removing_write_protect_screw} +-------------------------------- + +Since part of the SPI flash is write-protected by a screw, it is +necessary to remove the screw to remove the write protection and allow +writing Libreboot to the *read-only* part of the flash. + +To access the screw, the device has to be opened. There are 8 screws to +remove from the bottom of the device, as shown on the picture below. Two +are hidden under the top pads. After removing the screws, the keyboard +plastic part can be carefully detached from the rest. **Beware: there +are cables attached to it!** It is advised to flip the keyboard plastic +part over, as shown on the picture below. The write protect screw is +located next to the SPI flash chip, circled in red in the picture below. +It has to be removed. + +[](images/c201/screws.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. + +</div> + +</div> + +<div class="section"> + +Installing Libreboot to the SPI flash {#installing_libreboot_spi_flash} +===================================== + +The SPI flash (that holds Libreboot) is divided into various partitions +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. + +<div class="subsection"> + +Installing Libreboot internally, from the device {#installing_libreboot_internally} +------------------------------------------------ + +Before installing Libreboot to the SPI flash internally, the device has +to be reassembled. + +All the files from the **veyron\_speedy** release (or build) have to be +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:\ +\# **chmod a+x cros-flash-replace**\ + +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**\ +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:\ +\# **flashrom -p host -w flash.img**\ + +You should also see within the output the following:\ +**\"Verifying flash\... VERIFIED.\"** + +Shut down. The device will now boot to Libreboot. + +</div> + +<div class="subsection"> + +Installing Libreboot externally, with a SPI flash programmer {#installing_libreboot_externally} +------------------------------------------------------------ + +Before installing Libreboot to the SPI flash internally, the device has +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 +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 +the right and has colorful cables, as shown on the picture below. + +[](images/c201/spi-flash-layout.jpg) +[](images/c201/battery-connector.jpg) + +All the files from the **veyron\_speedy** release (or build) have to be +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**\ + +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**\ +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):\ +\# **flashrom -p *programmer* -w flash.img**\ + +You should also see within the output the following:\ +**\"Verifying flash\... VERIFIED.\"** + +The device will now boot to Libreboot. + +</div> + +Debian GNU+Linux {#debian} +---------------- + +You might consider replacing ChromeOS with a free distro. We have a +[list of recommended distributions](../distros/) but Debian is +recommended for this device (which is on that list). TODO: Devuan +instructions. + +See <https://wiki.debian.org/InstallingDebianOn/Asus/C201>. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/d510mo.html b/docs/install/d510mo.html deleted file mode 100644 index 54071d01..00000000 --- a/docs/install/d510mo.html +++ /dev/null @@ -1,107 +0,0 @@ - -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>D510MO flashing tutorial</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">D510MO flashing tutorial</h1> - <p> - This guide is for those who want libreboot on their Intel D510MO - motherboard while they still have the original BIOS present. - </p> - <p> - <a href="./">Back to main index</a> - </p> - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br/> - # <b>flashrom -p internal -V</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="clip">Flashing instructions</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - set up the BBB for flashing. - </p> - <p> - This is an image of the flash chip, for reference:<br/> - <img src="../images/d510mo/d510mo.jpg" alt="" /> - </p> - </div> - - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/d510mo.md b/docs/install/d510mo.md new file mode 100644 index 00000000..3ef3801c --- /dev/null +++ b/docs/install/d510mo.md @@ -0,0 +1,74 @@ +<div class="section"> + +D510MO flashing tutorial {#pagetop} +======================== + +This guide is for those who want libreboot on their Intel D510MO +motherboard while they still have the original BIOS present. + +[Back to main index](./) + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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:\ + + +</div> + +<div class="section"> + +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. + +</div> diff --git a/docs/install/d945gclf.html b/docs/install/d945gclf.html deleted file mode 100644 index a8874e8e..00000000 --- a/docs/install/d945gclf.html +++ /dev/null @@ -1,88 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Intel D945GCLF flashing tutorial</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Intel D945GCLF flashing tutorial</h1> - <p> - This guide is for those who want libreboot on their Intel D945GCLF - motherboard while they still have the original BIOS present. - </p> - <p> - For information about this board, go to - <a href="../hcl/d945gclf.html">../hcl/d945gclf.html</a> - </p> - <p> - <a href="./">Back to main index</a> - </p> - </div> - - <div class="section"> - <h1 id="clip">Flashing instructions</h1> - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - set up the BBB for external flashing. - </p> - <p> - Here is an image of the flash chip:<br/> - <img alt="" src="../images/d945gclf/d945gclf_spi.jpg" /> - </p> - </div> - - <div class="section"> - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - </div> - -</body> -</html> diff --git a/docs/install/d945gclf.md b/docs/install/d945gclf.md new file mode 100644 index 00000000..d0d02cb9 --- /dev/null +++ b/docs/install/d945gclf.md @@ -0,0 +1,65 @@ +<div class="section"> + +Intel D945GCLF flashing tutorial {#pagetop} +================================ + +This guide is for those who want libreboot on their Intel D945GCLF +motherboard while they still have the original BIOS present. + +For information about this board, go to +[../hcl/d945gclf.html](../hcl/d945gclf.html) + +[Back to main index](./) + +</div> + +<div class="section"> + +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:\ + + +</div> + +<div class="section"> + +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. + +</div> diff --git a/docs/install/ga-g41m-es2l.html b/docs/install/ga-g41m-es2l.html deleted file mode 100644 index 770f453e..00000000 --- a/docs/install/ga-g41m-es2l.html +++ /dev/null @@ -1,139 +0,0 @@ - -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>GA-G41M-ES2L flashing tutorial</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">GA-G41M-ES2L flashing tutorial</h1> - <p> - This guide is for those who want libreboot on their Intel GA-G41M-ES2L - motherboard while they still have the original BIOS present. - </p> - <p> - <a href="./">Back to main index</a> - </p> - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br/> - # <b>flashrom -p internal -V</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="clip">Flashing instructions</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - set up the BBB for external flashing. - <strong> - You can only externally reprogram one of the chips at a time, and - you need to disable the chip that you're not flashing, 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). - </strong> - </p> - <p> - Here is an image of the flash chip:<br/> - <img alt="" src="../images/ga-g41m-es2l/ga-g41m-es2l.jpg" /> - </p> - <p> - Internal flashing is possible. Boot with the proprietary BIOS - and GNU+Linux. There are 2 flash chips (one is backup). - </p> - <p> - Flash the first chip: - <br/> - <strong>./flashrom -p internal:dualbiosindex=0 -w libreboot.rom</strong> - </p> - <p> - Flash the second chip: - <br/> - <strong>./flashrom -p internal:dualbiosindex=1 -w libreboot.rom</strong> - </p> - <p> - NOTE: you can still boot the system with just the main flash chip connected, - after desoldering the backup chip. This has been tested while libreboot was - already installed onto the main chip. - </p> - <p> - NOTE: You need the latest flashrom. Just get it on flashrom.org from - their SVN or Git repos. - </p> - <p> - 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. - </p> - </div> - - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/ga-g41m-es2l.md b/docs/install/ga-g41m-es2l.md new file mode 100644 index 00000000..e3218280 --- /dev/null +++ b/docs/install/ga-g41m-es2l.md @@ -0,0 +1,98 @@ +<div class="section"> + +GA-G41M-ES2L flashing tutorial {#pagetop} +============================== + +This guide is for those who want libreboot on their Intel GA-G41M-ES2L +motherboard while they still have the original BIOS present. + +[Back to main index](./) + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Flashing instructions {#clip} +===================== + +Refer to [bbb\_setup.html](bbb_setup.html) for how to set up the BBB for +external flashing. **You can only externally reprogram one of the chips +at a time, and you need to disable the chip that you\'re not flashing, +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:\ + + +Internal flashing is possible. Boot with the proprietary BIOS and +GNU+Linux. There are 2 flash chips (one is backup). + +Flash the first chip:\ +**./flashrom -p internal:dualbiosindex=0 -w libreboot.rom** + +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 +connected, after desoldering the backup chip. This has been tested while +libreboot was already installed onto the main chip. + +NOTE: You need the latest flashrom. Just get it on flashrom.org from +their SVN or Git repos. + +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. + +</div> + +<div class="section"> + +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. + +</div> diff --git a/docs/install/index.html b/docs/install/index.html deleted file mode 100644 index f35604c3..00000000 --- a/docs/install/index.html +++ /dev/null @@ -1,566 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Installing libreboot</title> -</head> - -<body> - - <div class="section"> - - <h1 id="pagetop">Installing libreboot</h1> - <p> - This section relates to installing libreboot on supported targets. - </p> - <p> - NOTE: if running flashrom -p internal for software based flashing, and you - get an error related to /dev/mem access, you should reboot with iomem=relaxed - kernel parameter before running flashrom, or use a kernel that has - CONFIG_STRICT_DEVMEM not enabled. - </p> - <p> - <a href="../">Back to previous index</a> - </p> - - </div> - - <div class="section"> - - <h2>General information</h2> - <ul> - <li><a href="#rom">Information about libreboot ROM images</a></li> - </ul> - <h2>Flashing via software methods, on system:</h2> - <ul> - <li><a href="#flashrom">How to update or install libreboot on all systems</a></li> - <li><a href="#flashrom">ASUS KFSN4-DRE</a></li> - <li><a href="#flashrom_lenovobios">ThinkPad X60/T60 (if running Lenovo BIOS)</a></li> - <li><a href="#flashrom_macbook21">Apple MacBook2,1</a></li> - <li><a href="c201.html">ASUS Chromebook C201</a></li> - </ul> - - <h2>Setting up programmers, for external flashing via hardware method</h2> - <ul> - <li><a href="bbb_setup.html">How to program an SPI flash chip with the BeagleBone Black</a></li> - <li><a href="rpi_setup.html">How to program an SPI flash chip with the Raspberry Pi</a></li> - </ul> - <h2>Flashing via hardware methods, on system:</h2> - <ul> - <li><a href="ga-g41m-es2l.html">Gigabyte GA-G41-ES2L</a></li> - <li><a href="d510mo.html">Intel D510MO</a></li> - <li><a href="d945gclf.html">Intel D945GCLF</a></li> - <li><a href="kgpe-d16.html">ASUS KGPE-D16</a></li> - <li><a href="kcma-d8.html">ASUS KCMA-D8</a></li> - <li><a href="c201.html">ASUS Chromebook C201</a></li> - <li><a href="x60_unbrick.html">ThinkPad X60</a></li> - <li><a href="x60tablet_unbrick.html">ThinkPad X60 Tablet</a></li> - <li><a href="t60_unbrick.html">ThinkPad T60</a></li> - <li><a href="x200_external.html">ThinkPad X200/X200S/X200T</a></li> - <li><a href="r400_external.html">ThinkPad R400</a></li> - <li><a href="t400_external.html">ThinkPad T400</a></li> - <li><a href="t500_external.html">ThinkPad T500</a></li> - </ul> - - </div> - - <div class="section"> - - <h1 id="rom">Information about libreboot ROM images</h1> - - <p> - Libreboot distributes pre-compiled ROM images, built from the libreboot source code. - These images are provided for user convenience, so that they don't have - to build anything from source on their own. - </p> - - <p> - The ROM images in each archive use the following at the end of the file name, - if they are built with the GRUB payload: <b>_<i>keymap</i>_<i>mode</i>.rom</b> - </p> - <p> - Available <i>modes</i>: <b>vesafb</b> or <b>txtmode</b>. The <i>vesafb</i> ROM images are recommended, in most cases; - <i>txtmode</i> ROM images come with MemTest86+, which requires text-mode instead of the usual framebuffer used - by coreboot native graphics initialization. - </p> - <p> - <i>keymap</i> can be one of several keymaps that keyboard supports (there are quite a few), - which affects the keyboard layout configuration that is used in GRUB. It doesn't matter - which ROM image you choose here, as far as the keymap in GNU+Linux is concerned. - </p> - <p> - Keymaps are named appropriately according to each keyboard layout - support in GRUB. To learn how these keymaps are created, see - <a href="../grub/#grub_keyboard">../grub/#grub_keyboard</a> - </p> - - <h2 id="qemu">QEMU</h2> - - <p> - Libreboot comes with ROM images built for QEMU, by default: - </p> - - <p> - Examples of how to use libreboot ROM images in QEMU: - </p> - <ul> - <li>$ <b>qemu-system-i386 -M q35 -m 512 -bios qemu_q35_ich9_keymap_mode.rom</b></li> - <li>$ <b>qemu-system-i386 -M pc -m 512 -bios qemu_i440fx_piix4_keymap_mode.rom</b></li> - </ul> - <p> - You can optionally specify the <b>-serial stdio</b> argument, so that QEMU will emulate - a serial terminal on the standard input/output (most likely your terminal emulator or TTY). - </p> - <p> - Other arguments are available for QEMU. The manual will contain more information. - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="flashrom">How to update or install libreboot (if you are already running libreboot or coreboot)</h1> - - <p> - On all current targets, updating libreboot can be accomplished without disassembly and, - therefore, without having to externally re-flash using any dedicated hardware. In other words, - you can do everything entirely in software, directly from the OS that is running on your libreboot - system. - </p> - - <div class="important"> - <p> - <b>If you are using libreboot_src or git, then make sure that you built the sources first (see <a href="../git/#build">../git/#build</a>).</b> - </p> - </div> - - <p> - Look at the <a href="#rom">list of ROM images</a> to see which image is compatible with your device. - </p> - - <h2>Are you currently running the original, proprietary firmware?</h2> - - <p> - If you are currently running the proprietary firmware (not libreboot or coreboot), - then the flashing instructions for your system are going to be different. - </p> - <p> - X60/T60 users running the proprietary firmware should refer to <a href="#flashrom_lenovobios">#flashrom_lenovobios</a>. - MacBook2,1 users running Apple EFI should refer to <a href="#flashrom_macbook21">#flashrom_macbook21</a> - </p> - <p> - X200 users, refer to <a href="x200_external.html">x200_external.html</a>, - R400 users refer to <a href="r400_external.html">r400_external.html</a>, - T400 users refer to <a href="t400_external.html">t400_external.html</a>, - T500 users refer to <a href="t500_external.html">t500_external.html</a> - </p> - - <h2>ASUS KFSN4-DRE?</h2> - - <p> - Internal flashing should work just fine, even if you are - currently booting the proprietary firmware. - </p> - - <p> - Libreboot currently lacks documentation for externally - re-flashing an LPC flash chip. However, these boards have - the flash chip inside of a PLCC socket, and it is possible - to hot-swap the chips. If you want to back up your - known-working image, simply hot-swap the chip for one that - is the same capacity, after having dumped a copy of the - current firmware (flashrom -p internal -r yourchosenname.rom), - and then flash that chip with the known-working image. - Check whether the system still boots, and if it does, then - it should be safe to flash the new image (because you now - have a backup of the old image). - </p> - - <p> - Keeping at least one spare LPC PLCC chip with working firmware - on it is highly recommended, in case of bricks. - </p> - - <p> - <b> - DO NOT hot-swap the chip with your bare hands. Use a PLCC - chip extractor. These can be found online. - See <a href="http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools">http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools</a> - </b> - </p> - - <p> - Do check the HCL entry: <a href="../hcl/kfsn4-dre.html">../hcl/kfsn4-dre.html</a> - </p> - - <h2>ASUS KGPE-D16?</h2> - - <p> - If you have the proprietary BIOS, you need to flash libreboot externally. - See <a href="kgpe-d16.html">kgpe-d16.html</a>. - </p> - <p> - If you already have coreboot or libreboot installed, without write protection on the flash - chip, then you can do it in software (otherwise, see link above). - </p> - - <p> - <b> - DO NOT hot-swap the chip with your bare hands. Use a PDIP-8 - chip extractor. These can be found online. - See <a href="http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools">http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools</a> - </b> - </p> - - <p> - Do check the HCL entry: <a href="../hcl/kgpe-d16.html">../hcl/kgpe-d16.html</a> - </p> - - <h2>ASUS KCMA-D8?</h2> - - <p> - If you have the proprietary BIOS, you need to flash libreboot externally. - See <a href="kgpe-d8.html">kcma-d8.html</a>. - </p> - <p> - If you already have coreboot or libreboot installed, without write protection on the flash - chip, then you can do it in software (otherwise, see link above). - </p> - - <p> - <b> - DO NOT hot-swap the chip with your bare hands. Use a PDIP-8 - chip extractor. These can be found online. - See <a href="http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools">http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools</a> - </b> - </p> - - <p> - Do check the HCL entry: <a href="../hcl/kcma-d8.html">../hcl/kcma-d8.html</a> - </p> - - <h2>Intel D945GCLF?</h2> - <p> - If you're running the original Intel factory BIOS, then you will need to flash externally. - For instructions on how to do that, refer to <a href="d945gclf.html">d945gclf.html</a>. - </p> - <p> - Otherwise, read the generic instructions below for using the <em>flash</em> script. - </p> - - <h2>Are you currently running libreboot (or coreboot)?</h2> - - <p> - X60/T60 users should be fine with this guide. If you write-protected the flash chip, please refer to - <a href="x60_unbrick.html">x60_unbrick.html</a>, <a href="x60tablet_unbrick.html">x60tablet_unbrick.html</a> - or <a href="t60_unbrick.html">t60_unbrick.html</a>. <i>This probably does not apply to you. Most people - do not write-protect the flash chip, so you probably didn't either.</i> - </p> - <p> - Similarly, it is possible to write-protect the flash chip in coreboot or libreboot on GM45 laptops - (X200/R400/T400/T500). If you did this, then you will need to use the links above for flashing, - treating your laptop as though it currently has the proprietary firmware (because write-protected SPI flash - requires external re-flashing, as is also the case when running the proprietary firmware). - </p> - - <p> - If you did not write-protect the flash chip, or it came to you without any write-protection - (<b><i>libreboot does not write-protect the flash chip by default, so this probably applies to you</i></b>), - read on! - </p> - - <h2>MAC address on GM45 (X200/R400/T400/T500)</h2> - - <p> - <b>Users of the X200/R400/T400/T500 take note:</b> The MAC address for the 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. - <i>Make sure to change the MAC address inside the ROM image, before flashing it. - The instructions on <a href="../hcl/gm45_remove_me.html#ich9gen">../hcl/gm45_remove_me.html#ich9gen</a> - show how to do this.</i> - </p> - - <p> - It is important that you change the default MAC address, before flashing. It will be printed on a sticker - at the bottom of the laptop, or it will be printed on a sticker next to or underneath the RAM. Alternatively, - and assuming that your current firmware has the correct MAC address in it, you can get it from your OS. - </p> - <h2>Apple iMac 5,2?</h2> - <p> - Internal flashing works, even when flashing from Apple EFI to libreboot. Continue reading the instructions below. - </p> - <p> - <strong> - NOTE: If you're flashing an older version of Libreboot, - the iMac5,2 motherboard is compatible with the MacBook2,1. - Simply flash a MacBook2,1 ROM image, and it should work. - </strong> - </p> - - <h2>Flash chip size</h2> - - <p> - Use this to find out:<br/> - # <b>flashrom -p internal -V</b> - </p> - - <h2>All good?</h2> - - <p>Excellent! Moving on...</p> - - <p> - Download the <i>libreboot_util.tar.xz</i> archive, and extract it. Inside, you will find - a directory called <i>flashrom</i>. This contains statically compiled executable files of - the <i>flashrom</i> utility, which you will use to re-flash your libreboot system. - </p> - - <p> - Simply use <i>cd</i> on your terminal, to switch to the <i>libreboot_util</i> directory. Inside, - there is a script called <i>flash</i>, which will detect 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. - </p> - - <div class="important"> - <p> - How to update the flash chip contents:<br/> - $ <b>sudo ./flash update <a href="#rom">yourrom.rom</a></b> - </p> - </div> - <div class="important"> - <p> - 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:<br/> - $ <b>sudo ./flash forceupdate <a href="#rom">yourrom.rom</a></b> - </p> - </div> - - <div class="important"> - - <p> - You should see <b>"Verifying flash... VERIFIED."</b> written at the end of the flashrom output. <b>Shut down</b> - after you see this, and then boot up again after a few seconds. - </p> - - </div> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h1 id="flashrom_lenovobios">ThinkPad X60/T60: Initial installation guide (if running the proprietary firmware)</h1> - - <p><b>This is for the ThinkPad X60 and T60 while running Lenovo BIOS. If you already have coreboot or libreboot running, - then go to <a href="#flashrom">#flashrom</a> instead!</b></p> - - <p><b>If you are flashing a Lenovo ThinkPad T60, be sure to read <a href="../hcl/#supported_t60_list">../hcl/#supported_t60_list</a></b></p> - - <div class="important"> - <p> - <b>If you are using libreboot_src or git, then make sure that you built the sources first (see <a href="../git/#build">../git/#build</a>).</b> - </p> - </div> - - <p> - <b> - 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 <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>. - </b> - </p> - - <div class="important"> - - <p> - <b> - If you're using libreboot 20150518, note that there is a mistake in the flashing script. - do this: <em>rm -f patch && wget -O flash https://notabug.org/vimuser/libreboot/raw/9d850543ad90b72e0e333c98075530b31e5d23f1/flash && chmod +x flash</em> - </b> - </p> - - <p> - The first half of the procedure is as follows:<br/> - $ <b>sudo ./flash i945lenovo_firstflash <a href="#rom">yourrom.rom</a>.</b> - </p> - - </div> - - <div class="important"> - - <p> - You should see within the output the following:<br/> - <b>"Updated BUC.TS=1 - 64kb address ranges at 0xFFFE0000 and 0xFFFF0000 are swapped"</b>. - </p> - - <p> - You should also see within the output the following:<br/> - <b>"Your flash chip is in an unknown state"</b>, <b>"FAILED"</b> and <b>"DO NOT REBOOT OR POWEROFF"</b><br/> - Seeing this means that the operation was a <b>resounding</b> success! <b>DON'T PANIC</b>. - </p> - - <p> - See this link for more details: - <a href="http://thread.gmane.org/gmane.linux.bios.flashrom/575">http://thread.gmane.org/gmane.linux.bios.flashrom/575</a>. - </p> - - <p> - If the above is what you see, then <b>SHUT DOWN</b>. Wait a few seconds, and then boot; libreboot is running, but there is a 2nd procedure <b>*needed*</b> (see below). - </p> - - </div> - - <div class="important"> - <p> - When you have booted up again, you must also do this:<br/> - $ <b>sudo ./flash i945lenovo_secondflash <a href="#rom">yourrom.rom</a></b> - </p> - <p> - If flashing fails at this stage, try the following:<br/> - $ <b>sudo ./flashrom/i686/flashrom -p internal:laptop=force_I_want_a_brick -w <a href="#rom">yourrom.rom</a></b> - </p> - </div> - - <div class="important"> - - <p> - You should see within the output the following:<br/> - <b>"Updated BUC.TS=0 - 128kb address range 0xFFFE0000-0xFFFFFFFF is untranslated"</b> - </p> - - <p> - You should also see within the output the following:<br/> - <b>"Verifying flash... VERIFIED."</b> - </p> - - </div> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="flashrom_macbook21">MacBook2,1: Initial installation guide (if running the proprietary firmware)</h1> - - <div class="important"> - - <p> - <b>If you have a MacBook1,1, refer to <a href="../hcl/#macbook11">../hcl/#macbook11</a> for flashing instructions.</b> - </p> - - </div> - - <p> - <b> - This is for the MacBook2,1 while running Apple EFI firmware. If you already have - coreboot or libreboot running, then go to <a href="#flashrom">#flashrom</a> instead! - </b> - </p> - - <p> - Be sure to read the information in <a href="../hcl/#macbook21">../hcl/#macbook21</a>. - </p> - - <p> - <b> - Warning: this guide will not instruct the user how to backup the original Apple EFI firmware. - For that, please refer to <a href="http://www.coreboot.org/Board:apple/macbook21">http://www.coreboot.org/Board:apple/macbook21</a>. - </b> - </p> - - <div class="important"> - <p> - <b>If you are using libreboot_src or git, then make sure that you built the sources first (see <a href="../git/#build">../git/#build</a>).</b> - </p> - </div> - - <p> - Look at the <a href="#rom">list of ROM images</a> to see which image is compatible with your device. - </p> - - <div class="important"> - <p> - Use this flashing script, to install libreboot:<br/> - $ <b>sudo ./flash i945apple_firstflash <a href="#rom">yourrom.rom</a></b> - </p> - </div> - - <div class="important"> - - <p> - You should also see within the output the following:<br/> - <b>"Verifying flash... VERIFIED."</b> - </p> - - <p> - Shut down. - </p> - - </div> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/index.md b/docs/install/index.md new file mode 100644 index 00000000..66e750e7 --- /dev/null +++ b/docs/install/index.md @@ -0,0 +1,484 @@ +<div class="section"> + +Installing libreboot {#pagetop} +==================== + +This section relates to installing libreboot on supported targets. + +NOTE: if running flashrom -p internal for software based flashing, and +you get an error related to /dev/mem access, you should reboot with +iomem=relaxed kernel parameter before running flashrom, or use a kernel +that has CONFIG\_STRICT\_DEVMEM not enabled. + +[Back to previous index](../) + +</div> + +<div class="section"> + +General information +------------------- + +- [Information about libreboot ROM images](#rom) + +Flashing via software methods, on system: +----------------------------------------- + +- [How to update or install libreboot on all systems](#flashrom) +- [ASUS KFSN4-DRE](#flashrom) +- [ThinkPad X60/T60 (if running Lenovo BIOS)](#flashrom_lenovobios) +- [Apple MacBook2,1](#flashrom_macbook21) +- [ASUS Chromebook C201](c201.html) + +Setting up programmers, for external flashing via hardware method +----------------------------------------------------------------- + +- [How to program an SPI flash chip with the BeagleBone + Black](bbb_setup.html) +- [How to program an SPI flash chip with the Raspberry + Pi](rpi_setup.html) + +Flashing via hardware methods, on system: +----------------------------------------- + +- [Gigabyte GA-G41-ES2L](ga-g41m-es2l.html) +- [Intel D510MO](d510mo.html) +- [Intel D945GCLF](d945gclf.html) +- [ASUS KGPE-D16](kgpe-d16.html) +- [ASUS KCMA-D8](kcma-d8.html) +- [ASUS Chromebook C201](c201.html) +- [ThinkPad X60](x60_unbrick.html) +- [ThinkPad X60 Tablet](x60tablet_unbrick.html) +- [ThinkPad T60](t60_unbrick.html) +- [ThinkPad X200/X200S/X200T](x200_external.html) +- [ThinkPad R400](r400_external.html) +- [ThinkPad T400](t400_external.html) +- [ThinkPad T500](t500_external.html) + +</div> + +<div class="section"> + +Information about libreboot ROM images {#rom} +====================================== + +Libreboot distributes pre-compiled ROM images, built from the libreboot +source code. These images are provided for user convenience, so that +they don\'t have to build anything from source on their own. + +The ROM images in each archive use the following at the end of the file +name, if they are built with the GRUB payload: +**\_*keymap*\_*mode*.rom** + +Available *modes*: **vesafb** or **txtmode**. The *vesafb* ROM images +are recommended, in most cases; *txtmode* ROM images come with +MemTest86+, which requires text-mode instead of the usual framebuffer +used by coreboot native graphics initialization. + +*keymap* can be one of several keymaps that keyboard supports (there are +quite a few), which affects the keyboard layout configuration that is +used in GRUB. It doesn\'t matter which ROM image you choose here, as far +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) + +QEMU +---- + +Libreboot comes with ROM images built for QEMU, by default: + +Examples of how to use libreboot ROM images in QEMU: + +- \$ **qemu-system-i386 -M q35 -m 512 -bios + qemu\_q35\_ich9\_keymap\_mode.rom** +- \$ **qemu-system-i386 -M pc -m 512 -bios + qemu\_i440fx\_piix4\_keymap\_mode.rom** + +You can optionally specify the **-serial stdio** argument, so that QEMU +will emulate a serial terminal on the standard input/output (most likely +your terminal emulator or TTY). + +Other arguments are available for QEMU. The manual will contain more +information. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +How to update or install libreboot (if you are already running libreboot or coreboot) {#flashrom} +===================================================================================== + +On all current targets, updating libreboot can be accomplished without +disassembly and, therefore, without having to externally re-flash using +any dedicated hardware. In other words, you can do everything entirely +in software, directly from the OS that is running on your libreboot +system. + +<div class="important"> + +**If you are using libreboot\_src or git, then make sure that you built +the sources first (see [../git/\#build](../git/#build)).** + +</div> + +Look at the [list of ROM images](#rom) to see which image is compatible +with your device. + +Are you currently running the original, proprietary firmware? +------------------------------------------------------------- + +If you are currently running the proprietary firmware (not libreboot or +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) + +X200 users, refer to [x200\_external.html](x200_external.html), R400 +users refer to [r400\_external.html](r400_external.html), T400 users +refer to [t400\_external.html](t400_external.html), T500 users refer to +[t500\_external.html](t500_external.html) + +ASUS KFSN4-DRE? +--------------- + +Internal flashing should work just fine, even if you are currently +booting the proprietary firmware. + +Libreboot currently lacks documentation for externally re-flashing an +LPC flash chip. However, these boards have the flash chip inside of a +PLCC socket, and it is possible to hot-swap the chips. If you want to +back up your known-working image, simply hot-swap the chip for one that +is the same capacity, after having dumped a copy of the current firmware +(flashrom -p internal -r yourchosenname.rom), and then flash that chip +with the known-working image. Check whether the system still boots, and +if it does, then it should be safe to flash the new image (because you +now have a backup of the old image). + +Keeping at least one spare LPC PLCC chip with working firmware on it is +highly recommended, in case of bricks. + +**DO NOT hot-swap the chip with your bare hands. Use a PLCC chip +extractor. These can be found online. See +<http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + +Do check the HCL entry: [../hcl/kfsn4-dre.html](../hcl/kfsn4-dre.html) + +ASUS KGPE-D16? +-------------- + +If you have the proprietary BIOS, you need to flash libreboot +externally. See [kgpe-d16.html](kgpe-d16.html). + +If you already have coreboot or libreboot installed, without write +protection on the flash chip, then you can do it in software (otherwise, +see link above). + +**DO NOT hot-swap the chip with your bare hands. Use a PDIP-8 chip +extractor. These can be found online. See +<http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + +Do check the HCL entry: [../hcl/kgpe-d16.html](../hcl/kgpe-d16.html) + +ASUS KCMA-D8? +------------- + +If you have the proprietary BIOS, you need to flash libreboot +externally. See [kcma-d8.html](kgpe-d8.html). + +If you already have coreboot or libreboot installed, without write +protection on the flash chip, then you can do it in software (otherwise, +see link above). + +**DO NOT hot-swap the chip with your bare hands. Use a PDIP-8 chip +extractor. These can be found online. See +<http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + +Do check the HCL entry: [../hcl/kcma-d8.html](../hcl/kcma-d8.html) + +Intel D945GCLF? +--------------- + +If you\'re running the original Intel factory BIOS, then you will need +to flash externally. For instructions on how to do that, refer to +[d945gclf.html](d945gclf.html). + +Otherwise, read the generic instructions below for using the *flash* +script. + +Are you currently running libreboot (or coreboot)? +-------------------------------------------------- + +X60/T60 users should be fine with this guide. If you write-protected the +flash chip, please refer to [x60\_unbrick.html](x60_unbrick.html), +[x60tablet\_unbrick.html](x60tablet_unbrick.html) or +[t60\_unbrick.html](t60_unbrick.html). *This probably does not apply to +you. Most people do not write-protect the flash chip, so you probably +didn\'t either.* + +Similarly, it is possible to write-protect the flash chip in coreboot or +libreboot on GM45 laptops (X200/R400/T400/T500). If you did this, then +you will need to use the links above for flashing, treating your laptop +as though it currently has the proprietary firmware (because +write-protected SPI flash requires external re-flashing, as is also the +case when running the proprietary firmware). + +If you did not write-protect the flash chip, or it came to you without +any write-protection (***libreboot does not write-protect the flash chip +by default, so this probably applies to you***), read on! + +MAC address on GM45 (X200/R400/T400/T500) +----------------------------------------- + +**Users of the X200/R400/T400/T500 take note:** The MAC address for the +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) +show how to do this.* + +It is important that you change the default MAC address, before +flashing. It will be printed on a sticker at the bottom of the laptop, +or it will be printed on a sticker next to or underneath the RAM. +Alternatively, and assuming that your current firmware has the correct +MAC address in it, you can get it from your OS. + +Apple iMac 5,2? +--------------- + +Internal flashing works, even when flashing from Apple EFI to libreboot. +Continue reading the instructions below. + +**NOTE: If you\'re flashing an older version of Libreboot, the iMac5,2 +motherboard is compatible with the MacBook2,1. Simply flash a MacBook2,1 +ROM image, and it should work.** + +Flash chip size +--------------- + +Use this to find out:\ +\# **flashrom -p internal -V** + +All good? +--------- + +Excellent! Moving on\... + +Download the *libreboot\_util.tar.xz* archive, and extract it. Inside, +you will find a directory called *flashrom*. This contains statically +compiled executable files of the *flashrom* utility, which you will use +to re-flash your libreboot system. + +Simply use *cd* on your terminal, to switch to the *libreboot\_util* +directory. Inside, there is a script called *flash*, which will detect +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. + +<div class="important"> + +How to update the flash chip contents:\ +\$ **sudo ./flash update [yourrom.rom](#rom)** + +</div> + +<div class="important"> + +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:\ +\$ **sudo ./flash forceupdate [yourrom.rom](#rom)** + +</div> + +<div class="important"> + +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. + +</div> + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +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!** + +**If you are flashing a Lenovo ThinkPad T60, be sure to read +[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list)** + +<div class="important"> + +**If you are using libreboot\_src or git, then make sure that you built +the sources first (see [../git/\#build](../git/#build)).** + +</div> + +**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>.** + +<div class="important"> + +**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:\ +\$ **sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom).** + +</div> + +<div class="important"> + +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:\ +**\"Your flash chip is in an unknown state\"**, **\"FAILED\"** and +**\"DO NOT REBOOT OR POWEROFF\"**\ +Seeing this means that the operation was a **resounding** success! +**DON\'T PANIC**. + +See this link for more details: +<http://thread.gmane.org/gmane.linux.bios.flashrom/575>. + +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). + +</div> + +<div class="important"> + +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)** + +</div> + +<div class="important"> + +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:\ +**\"Verifying flash\... VERIFIED.\"** + +</div> + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +MacBook2,1: Initial installation guide (if running the proprietary firmware) {#flashrom_macbook21} +============================================================================ + +<div class="important"> + +**If you have a MacBook1,1, refer to +[../hcl/\#macbook11](../hcl/#macbook11) for flashing instructions.** + +</div> + +**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!** + +Be sure to read the information in +[../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>.** + +<div class="important"> + +**If you are using libreboot\_src or git, then make sure that you built +the sources first (see [../git/\#build](../git/#build)).** + +</div> + +Look at the [list of ROM images](#rom) to see which image is compatible +with your device. + +<div class="important"> + +Use this flashing script, to install libreboot:\ +\$ **sudo ./flash i945apple\_firstflash [yourrom.rom](#rom)** + +</div> + +<div class="important"> + +You should also see within the output the following:\ +**\"Verifying flash\... VERIFIED.\"** + +Shut down. + +</div> + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/kcma-d8.html b/docs/install/kcma-d8.html deleted file mode 100644 index c4dfbc71..00000000 --- a/docs/install/kcma-d8.html +++ /dev/null @@ -1,109 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>KCMA-D8 external flashing instructions</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">KCMA-D8 external flashing instructions</h1> - <p>Initial flashing instructions for kcma-d8.</p> - <p> - This guide is for those who want libreboot on their ASUS kcma-d8 - motherboard, while they still have the proprietary ASUS BIOS present. - This guide can also be followed (adapted) if you brick you board, to know - how to recover. - </p> - - - <p> - <b>Memory initialization is still problematic, for some modules. We recommend avoiding Kingston modules.</b> - </p> - <p> - For more general information about this board, refer to - <a href="../hcl/kcma-d8.html">../hcl/kcma-d8.html</a>. - </p> - - <p> - TODO: show photos here, and other info. - </p> - - <ul> - <li><a href="#preinstall">kcma-d8 boards (and full systems) with libreboot preinstalled</a></li> - <li><a href="#programmer">External programmer</a></li> - </ul> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - <h1 id="programmer">External programmer</h1> - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for a guide on - how to set up an external SPI programmer. - </p> - <p> - The flash chip is in a PDIP 8 socket (SPI flash chip) on the motherboard, - which you take out and then re-flash with libreboot, using the programmer. - <b>DO NOT</b> remove the chip with your hands. Use a chip extractor tool. - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/kcma-d8.md b/docs/install/kcma-d8.md new file mode 100644 index 00000000..ecbb4a17 --- /dev/null +++ b/docs/install/kcma-d8.md @@ -0,0 +1,80 @@ +<div class="section"> + +KCMA-D8 external flashing instructions {#pagetop} +====================================== + +Initial flashing instructions for kcma-d8. + +This guide is for those who want libreboot on their ASUS kcma-d8 +motherboard, while they still have the proprietary ASUS BIOS present. +This guide can also be followed (adapted) if you brick you board, to +know how to recover. + +**Memory initialization is still problematic, for some modules. We +recommend avoiding Kingston modules.** + +For more general information about this board, refer to +[../hcl/kcma-d8.html](../hcl/kcma-d8.html). + +TODO: show photos here, and other info. + +- [kcma-d8 boards (and full systems) with libreboot + preinstalled](#preinstall) +- [External programmer](#programmer) + +[Back to main index](./) + +</div> + +<div class="section"> + +External programmer {#programmer} +=================== + +Refer to [bbb\_setup.html](bbb_setup.html) for a guide on how to set up +an external SPI programmer. + +The flash chip is in a PDIP 8 socket (SPI flash chip) on the +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. + +</div> + +<div class="section"> + +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. + +</div> diff --git a/docs/install/kgpe-d16.html b/docs/install/kgpe-d16.html deleted file mode 100644 index d2e10dd4..00000000 --- a/docs/install/kgpe-d16.html +++ /dev/null @@ -1,124 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>KGPE-D16 external flashing instructions</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">KGPE-D16 external flashing instructions</h1> - <p>Initial flashing instructions for KGPE-D16.</p> - <p> - This guide is for those who want libreboot on their ASUS KGPE-D16 - motherboard, while they still have the proprietary ASUS BIOS present. - This guide can also be followed (adapted) if you brick you board, to know - how to recover. - </p> - - - <p> - <b>Memory initialization is still problematic, for some modules. We recommend avoiding Kingston modules.</b> - </p> - - <p> - For more general information about this board, refer to - <a href="../hcl/kgpe-d16.html">../hcl/kgpe-d16.html</a>. - </p> - - <p> - TODO: show photos here, and other info. - </p> - - <ul> - <li><a href="#preinstall">KGPE-D16 boards (and full systems) with libreboot preinstalled</a></li> - <li><a href="#programmer">External programmer</a></li> - </ul> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - - <h1 id="preinstall">KGPE-D16 boards (and full systems) with libreboot preinstalled</h1> - - <p> - If you don't want to install libreboot yourself, companies exist that sell these boards - with libreboot pre-installed, along with a free GNU+Linux distribution. - </p> - <p> - Check the <a href="../../suppliers">suppliers</a> page for more information. - </p> - - </div> - - <div class="section"> - <h1 id="programmer">External programmer</h1> - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for a guide on - how to set up an external SPI programmer. - </p> - <p> - The flash chip is in a PDIP 8 socket (SPI flash chip) on the motherboard, - which you take out and then re-flash with libreboot, using the programmer. - <b>DO NOT</b> remove the chip with your hands. Use a chip extractor tool. - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/kgpe-d16.md b/docs/install/kgpe-d16.md new file mode 100644 index 00000000..a91af3ff --- /dev/null +++ b/docs/install/kgpe-d16.md @@ -0,0 +1,93 @@ +<div class="section"> + +KGPE-D16 external flashing instructions {#pagetop} +======================================= + +Initial flashing instructions for KGPE-D16. + +This guide is for those who want libreboot on their ASUS KGPE-D16 +motherboard, while they still have the proprietary ASUS BIOS present. +This guide can also be followed (adapted) if you brick you board, to +know how to recover. + +**Memory initialization is still problematic, for some modules. We +recommend avoiding Kingston modules.** + +For more general information about this board, refer to +[../hcl/kgpe-d16.html](../hcl/kgpe-d16.html). + +TODO: show photos here, and other info. + +- [KGPE-D16 boards (and full systems) with libreboot + preinstalled](#preinstall) +- [External programmer](#programmer) + +[Back to main index](./) + +</div> + +<div class="section"> + +KGPE-D16 boards (and full systems) with libreboot preinstalled {#preinstall} +============================================================== + +If you don\'t want to install libreboot yourself, companies exist that +sell these boards with libreboot pre-installed, along with a free +GNU+Linux distribution. + +Check the [suppliers](../../suppliers) page for more information. + +</div> + +<div class="section"> + +External programmer {#programmer} +=================== + +Refer to [bbb\_setup.html](bbb_setup.html) for a guide on how to set up +an external SPI programmer. + +The flash chip is in a PDIP 8 socket (SPI flash chip) on the +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. + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/r400_external.html b/docs/install/r400_external.html deleted file mode 100644 index 04bb8a98..00000000 --- a/docs/install/r400_external.html +++ /dev/null @@ -1,587 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad R400: flashing tutorial (BeagleBone Black)</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Flashing the R400 with a BeagleBone Black</h1> - <p>Initial flashing instructions for R400.</p> - <p> - This guide is for those who want libreboot on their ThinkPad R400 - while they still have the original Lenovo BIOS present. This guide - can also be followed (adapted) if you brick your R400, to know how - to recover. - </p> - <p> - Before following this section, please make sure to setup your libreboot 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) - </p> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - - <h1 id="t400">Libreboot T400</h1> - <p> - You may also be interested in the smaller, more portable <a href="t400_external.html">Libreboot T400</a>. - </p> - - </div> - - <div class="section"> - - <h2 id="serial_port">Serial port</h2> - - <p> - 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. - </p> - - </div> - - <div class="section" id="cpu_compatibility"> - - <h1>A note about CPUs</h1> - <p> - <a href="http://www.thinkwiki.org/wiki/Category:R400">ThinkWiki</a> has a list of CPUs - for this system. The Core 2 Duo P8400 and P8600 are believed to work in libreboot. - The Core 2 Duo T9600 was confirmed to work, so the T9400 probably also works. - <b>The Core 2 Duo T5870/5670 and Celeron M 575/585 are untested!</b> - </p> - - <h2>Quad-core CPUs</h2> - - <p> - Incompatible. Do not use. - </p> - - </div> - - <div class="section" id="switchable_graphics"> - - <h1>A note about GPUs</h1> - - <p> - Some models have an Intel GPU, while others have both an ATI and an Intel GPU; this - is referred to as "switchable graphics". In the <i>BIOS setup</i> program - for lenovobios, you can specify that the system will use one or the other (but not both). - </p> - - <p> - Libreboot is known to work on systems with only the Intel GPU, using native graphics initialization. - On systems with switchable graphics, the Intel GPU is used and the ATI GPU is disabled, so - native graphics initialization works all the same. - </p> - - <h1>CPU paste required</h1> - - <p> - See <a href="#paste">#paste</a>. - </p> - - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br> - # <b>flashrom -p internal -V</b><br> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos"> - - <h1 id="macaddress">MAC address</h1> - - <p> - On the R400, the MAC address for the onboard - gigabit ethernet chipset is stored inside the flash chip, - along with other configuration data. - </p> - <p> - Keep a note of the MAC address before disassembly; this is - very important, because you will need to insert this into - the libreboot ROM image before flashing it. - It will be written in one of these locations: - </p> - - <p> - <img src="images/t400/macaddress0.jpg" alt="" /> - <img src="images/t400/macaddress1.jpg" alt="" /> - <img src="images/x200/disassembly/0001.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h1>Initial BBB configuration</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - setup the BBB for flashing. - </p> - - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-16 (clip: Pomona 5252): - </p> -<pre> -POMONA 5252 (correlate with the BBB guide) -=== ethernet jack and VGA port ==== - NC - - 21 - 1 - - 17 - NC - - NC - NC - - NC - NC - - NC - NC - - NC - 18 - - 3.3V (PSU) - 22 - - NC - this is pin 1 on the flash chip -=== SATA port === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/t400/0065.jpg" alt="" /> -</pre> - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): - </p> -<pre> -POMONA 5250 (correlate with the BBB guide) -=== RAM slots ==== - 18 - - 1 - 22 - - NC - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== slot where the AC jack is connected === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/r400/0051.jpg" alt="" /> -</pre> - - <h2 id="disassembly">Disassembly</h2> - - <p> - Remove all screws:<br/> - <img src="images/r400/0000.jpg" alt="" /><br/> - Remove the HDD and optical drive:<br/> - <img src="images/r400/0001.jpg" alt="" /><br/> - Remove the hinge screws:<br/> - <img src="images/r400/0002.jpg" alt="" /> - <img src="images/r400/0003.jpg" alt="" /> - </p> - - <p> - Remove the palm rest and keyboard:<br/> - <img src="images/r400/0004.jpg" alt="" /> - <img src="images/r400/0005.jpg" alt="" /> - </p> - - <p> - Remove these screws, and then remove the bezel:<br/> - <img src="images/r400/0006.jpg" alt="" /> - <img src="images/r400/0007.jpg" alt="" /> - </p> - - <p> - Remove the speaker screws, but don't remove the speakers yet - (just set them loose):<br/> - <img src="images/r400/0008.jpg" alt="" /> - <img src="images/r400/0009.jpg" alt="" /> - <img src="images/r400/0010.jpg" alt="" /> - </p> - - <p> - Remove these screws, and then remove the metal plate:<br/> - <img src="images/r400/0011.jpg" alt="" /> - <img src="images/r400/0012.jpg" alt="" /> - <img src="images/r400/0013.jpg" alt="" /> - </p> - - <p> - Remove the antennas from the wifi card, and then - start unrouting them:<br/> - <img src="images/r400/0014.jpg" alt="" /> - <img src="images/r400/0015.jpg" alt="" /> - <img src="images/r400/0016.jpg" alt="" /> - <img src="images/r400/0017.jpg" alt="" /> - <img src="images/r400/0018.jpg" alt="" /> - <img src="images/r400/0019.jpg" alt="" /> - </p> - - <p> - Disconnect the LCD cable from the motherboard:<br/> - <img src="images/r400/0020.jpg" alt="" /> - <img src="images/r400/0021.jpg" alt="" /> - <img src="images/r400/0022.jpg" alt="" /> - <img src="images/r400/0023.jpg" alt="" /> - </p> - - <p> - Remove the hinge screws, and then remove the LCD panel:<br/> - <img src="images/r400/0024.jpg" alt="" /> - <img src="images/r400/0025.jpg" alt="" /> - <img src="images/r400/0026.jpg" alt="" /> - <img src="images/r400/0027.jpg" alt="" /> - </p> - - <p> - Remove this:<br/> - <img src="images/r400/0028.jpg" alt="" /> - <img src="images/r400/0029.jpg" alt="" /> - </p> - - <p> - Remove this long cable (there are 3 connections):<br/> - <img src="images/r400/0030.jpg" alt="" /> - <img src="images/r400/0031.jpg" alt="" /> - <img src="images/r400/0032.jpg" alt="" /> - <img src="images/r400/0033.jpg" alt="" /> - </p> - - <p> - Disconnect the speaker cable, and remove the speakers:<br/> - <img src="images/r400/0034.jpg" alt="" /> - </p> - - <p> - Remove the heatsink screws, remove the fan - and then remove the heatsink/fan:<br/> - <img src="images/r400/0035.jpg" alt="" /> - <img src="images/r400/0036.jpg" alt="" /> - <img src="images/r400/0037.jpg" alt="" /> - <img src="images/r400/0038.jpg" alt="" /> - </p> - - <p> - Remove the NVRAM battery:<br/> - <img src="images/r400/0039.jpg" alt="" /> - <img src="images/r400/0040.jpg" alt="" /> - </p> - - <p> - Remove this screw:<br/> - <img src="images/r400/0041.jpg" alt="" /> - <img src="images/r400/0042.jpg" alt="" /> - </p> - - <p> - Disconnect the AC jack:<br/> - <img src="images/r400/0043.jpg" alt="" /> - <img src="images/r400/0044.jpg" alt="" /> - </p> - - <p> - Remove this screw and then remove what is under it:<br/> - <img src="images/r400/0045.jpg" alt="" /> - </p> - - <p> - Remove this:<br/> - <img src="images/r400/0046.jpg" alt="" /> - </p> - - <p> - Lift the motherboard (which is still inside the cage) - from the side on the right, removing it completely:<br/> - <img src="images/r400/0047.jpg" alt="" /> - <img src="images/r400/0048.jpg" alt="" /> - </p> - - <p> - Remove all screws, marking each hole so that you know - where to re-insert them. You should place the screws in - a layout corresponding to the order that they were in - before removal: - <img src="images/r400/0049.jpg" alt="" /> - <img src="images/r400/0050.jpg" alt="" /> - </p> - - <p> - Remove the motherboard from the cage, and the SPI flash - chip will be next to the memory slots:<br/> - <img src="images/r400/0051.jpg" alt="" /> - <img src="images/r400/0052.jpg" alt="" /> - </p> - - <p> - Connect your programmer, then connect GND and 3.3V<br/> - <img src="images/t400/0065.jpg" alt="" /> - <img src="images/t400/0066.jpg" alt="" /> - <img src="images/t400/0067.jpg" alt="" /> - <img src="images/t400/0069.jpg" alt="" /> - <img src="images/t400/0070.jpg" alt="" /> - <img src="images/t400/0071.jpg" alt="" /> - </p> - <p> - A dedicated 3.3V PSU was used to create this guide, but - at ATX PSU is also fine:<br/> - <img src="images/t400/0072.jpg" alt="" /> - </p> - - <p> - Of course, make sure to turn on your PSU:<br/> - <img src="images/x200/disassembly/0013.jpg" alt="" /> - </p> - - <p> - Now, you should be ready to install libreboot. - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - <p> - Log in as root on your BBB, using the instructions in <a href="bbb_setup.html#bbb_access">bbb_setup.html#bbb_access</a>. - </p> - <p> - Test that flashrom works:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512</b><br/> - In this case, the output was: - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. -Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" -Please specify which chip definition to use with the -c <chipname> option. -</pre> - <p> - How to backup factory.rom (change the -c option as neeed, for your flash chip):<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom</b><br/> - Note: the <b>-c</b> option is not required in libreboot's patched flashrom, because - the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/> - Now compare the 3 images:<br/> - # <b>sha512sum factory*.rom</b><br/> - 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 behaviour in the original firmware - that could be replicated in coreboot and libreboot. - </p> - <p> - Follow the instructions at <a href="../hcl/gm45_remove_me.html#ich9gen">../hcl/gm45_remove_me.html#ich9gen</a> - 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. <b>Make sure - to always change the MAC address to one that is correct for your system.</b> - </p> - <p> - Now flash it:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V</b> - </p> - <p> - <img src="images/x200/disassembly/0015.jpg" alt="" /> - </p> - <p> - You might see errors, but if it says <b>Verifying flash... VERIFIED</b> at the end, then it's flashed and should boot. - If you see errors, try again (and again, and again); the message <b>Chip content is identical to the requested image</b> - is also an indication of a successful installation. - </p> - <p> - Example output from running the command (see above): - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Reading old flash chip contents... done. -Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 -ERASE FAILED! -Reading current flash chip contents... done. Looking for another erase function. -Erase/write done. -Verifying flash... VERIFIED. -</pre> - - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos" id="paste"> - - <h1>Thermal paste (IMPORTANT)</h1> - - <p> - Because part of this procedure involved removing the heatsink, you will need to apply new paste. - Arctic MX-4 is ok. You will also need isopropyl alcohol and an anti-static cloth to clean with. - </p> - - <p> - When re-installing the heatsink, you must first clean off all old paste with the alcohol/cloth. - Then apply new paste. Arctic MX-4 is also much better than the default paste used on these systems. - </p> - - <p> - <img src="images/t400/paste.jpg" alt="" /> - </p> - - <p> - 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. - </p> - - </div> - - <div class="section"> - - <h1 id="wifi">Wifi</h1> - - <p> - 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 - <a href="../hcl/#recommended_wifi">../hcl/#recommended_wifi</a>. - </p> - - <p> - Some R400 laptops might come with an Atheros chipset, but this is 802.11g only. - </p> - - <p> - It is recommended that you install a new wifi chipset. This can only - be done after installing libreboot, because the original firmware has - a whitelist of approved chips, and it will refuse to boot if you - use an 'unauthorized' wifi card. - </p> - - <p> - The following photos show an Atheros AR5B95 being installed, to - replace the Intel chip that this R400 came with:<br/> - <img src="images/t400/0012.jpg" alt="" /> - <img src="images/t400/ar5b95.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h1 id="wwan">WWAN</h1> - <p> - 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. - </p> - <p> - Not to be confused with wifi (wifi is fine). - </p> - - </div> - - <div class="section photos"> - - <h1 id="memory">Memory</h1> - - <p> - You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs - (speed/size). Non-matching pairs won't work. You can also install a - single module (meaning, one of the slots will be empty) in slot 0. - </p> - - <p> - Make sure that the RAM you buy is the 2Rx8 density. - </p> - - <p> - <a href="http://www.forum.thinkpads.com/viewtopic.php?p=760721">This page</a> might be useful for RAM compatibility info - (note: coreboot raminit is different, so this page might be BS) - </p> - - <p> - The following photo shows 8GiB (2x4GiB) of RAM installed:<br/> - <img src="images/t400/memory.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h2> - Boot it! - </h2> - <p> - You should see something like this: - </p> - <p> - <img src="images/t400/boot0.jpg" alt="" /> - <img src="images/t400/boot1.jpg" alt="" /> - </p> - - <p> - Now <a href="../gnulinux/">install GNU+Linux</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md new file mode 100644 index 00000000..16e96258 --- /dev/null +++ b/docs/install/r400_external.md @@ -0,0 +1,445 @@ +<div class="section"> + +Flashing the R400 with a BeagleBone Black {#pagetop} +========================================= + +Initial flashing instructions for R400. + +This guide is for those who want libreboot on their ThinkPad R400 while +they still have the original Lenovo BIOS present. This guide can also be +followed (adapted) if you brick your R400, to know how to recover. + +Before following this section, please make sure to setup your libreboot +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) + +[Back to main index](./) + +</div> + +<div class="section"> + +Libreboot T400 {#t400} +============== + +You may also be interested in the smaller, more portable [Libreboot +T400](t400_external.html). + +</div> + +<div class="section"> + +Serial port {#serial_port} +----------- + +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. + +</div> + +<div id="cpu_compatibility" class="section"> + +A note about CPUs +================= + +[ThinkWiki](http://www.thinkwiki.org/wiki/Category:R400) has a list of +CPUs for this system. The Core 2 Duo P8400 and P8600 are believed to +work in libreboot. The Core 2 Duo T9600 was confirmed to work, so the +T9400 probably also works. **The Core 2 Duo T5870/5670 and Celeron M +575/585 are untested!** + +Quad-core CPUs +-------------- + +Incompatible. Do not use. + +</div> + +<div id="switchable_graphics" class="section"> + +A note about GPUs +================= + +Some models have an Intel GPU, while others have both an ATI and an +Intel GPU; this is referred to as \"switchable graphics\". In the *BIOS +setup* program for lenovobios, you can specify that the system will use +one or the other (but not both). + +Libreboot is known to work on systems with only the Intel GPU, using +native graphics initialization. On systems with switchable graphics, the +Intel GPU is used and the ATI GPU is disabled, so native graphics +initialization works all the same. + +CPU paste required +================== + +See [\#paste](#paste). + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V**\ + +[Back to top of page.](#pagetop) + +</div> + +<div class="section photos"> + +MAC address {#macaddress} +=========== + +On the R400, the MAC address for the onboard gigabit ethernet chipset is +stored inside the flash chip, along with other configuration data. + +Keep a note of the MAC address before disassembly; this is very +important, because you will need to insert this into the libreboot ROM +image before flashing it. It will be written in one of these locations: + +  + + +</div> + +<div class="section photos"> + +Initial BBB configuration +========================= + +Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for +flashing. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-16 (clip: Pomona 5252): + + POMONA 5252 (correlate with the BBB guide) + === ethernet jack and VGA port ==== + NC - - 21 + 1 - - 17 + NC - - NC + NC - - NC + NC - - NC + NC - - NC + 18 - - 3.3V (PSU) + 22 - - NC - this is pin 1 on the flash chip + === SATA port === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-8 (clip: Pomona 5250): + + POMONA 5250 (correlate with the BBB guide) + === RAM slots ==== + 18 - - 1 + 22 - - NC + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === slot where the AC jack is connected === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +Disassembly +----------- + +Remove all screws:\ +\ +Remove the HDD and optical drive:\ +\ +Remove the hinge screws:\ +  + +Remove the palm rest and keyboard:\ +  + +Remove these screws, and then remove the bezel:\ +  + +Remove the speaker screws, but don\'t remove the speakers yet (just set +them loose):\ +  + + +Remove these screws, and then remove the metal plate:\ +  + + +Remove the antennas from the wifi card, and then start unrouting them:\ +  +  +  + +Disconnect the LCD cable from the motherboard:\ +  +  + +Remove the hinge screws, and then remove the LCD panel:\ +  +  + +Remove this:\ +  + +Remove this long cable (there are 3 connections):\ +  +  + +Disconnect the speaker cable, and remove the speakers:\ + + +Remove the heatsink screws, remove the fan and then remove the +heatsink/fan:\ +  +  + +Remove the NVRAM battery:\ +  + +Remove this screw:\ +  + +Disconnect the AC jack:\ +  + +Remove this screw and then remove what is under it:\ + + +Remove this:\ + + +Lift the motherboard (which is still inside the cage) from the side on +the right, removing it completely:\ +  + +Remove all screws, marking each hole so that you know where to re-insert +them. You should place the screws in a layout corresponding to the order +that they were in before removal:  + + +Remove the motherboard from the cage, and the SPI flash chip will be +next to the memory slots:\ +  + +Connect your programmer, then connect GND and 3.3V\ +  +  +  + +A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is +also fine:\ + + +Of course, make sure to turn on your PSU:\ + + +Now, you should be ready to install libreboot. + +Flashrom binaries for ARM (tested on a BBB) are distributed in +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:\ +\# **./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) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. + Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" + 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**\ +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**\ +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 +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) +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 +path/to/libreboot/rom/image.rom -V** + + + +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 +installation. + +Example output from running the command (see above): + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Reading old flash chip contents... done. + Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 + ERASE FAILED! + Reading current flash chip contents... done. Looking for another erase function. + Erase/write done. + Verifying flash... VERIFIED. + +[Back to top of page.](#pagetop) + +</div> + +<div id="paste" class="section photos"> + +Thermal paste (IMPORTANT) +========================= + +Because part of this procedure involved removing the heatsink, you will +need to apply new paste. Arctic MX-4 is ok. You will also need isopropyl +alcohol and an anti-static cloth to clean with. + +When re-installing the heatsink, you must first clean off all old paste +with the alcohol/cloth. Then apply new paste. Arctic MX-4 is also much +better than the default paste used on these systems. + + + +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. + +</div> + +<div class="section"> + +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). + +Some R400 laptops might come with an Atheros chipset, but this is +802.11g only. + +It is recommended that you install a new wifi chipset. This can only be +done after installing libreboot, because the original firmware has a +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:\ +  + +</div> + +<div class="section"> + +WWAN +==== + +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. + +Not to be confused with wifi (wifi is fine). + +</div> + +<div class="section photos"> + +Memory +====== + +You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs +(speed/size). Non-matching pairs won\'t work. You can also install a +single module (meaning, one of the slots will be empty) in slot 0. + +Make sure that the RAM you buy is the 2Rx8 density. + +[This page](http://www.forum.thinkpads.com/viewtopic.php?p=760721) might +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:\ + + +</div> + +<div class="section photos"> + +Boot it! +-------- + +You should see something like this: + +  + +Now [install GNU+Linux](../gnulinux/). + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/rpi_setup.html b/docs/install/rpi_setup.html deleted file mode 100644 index 9c0e1c17..00000000 --- a/docs/install/rpi_setup.html +++ /dev/null @@ -1,702 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>How to program an SPI flash chip with the Raspberry Pi</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">How to program an SPI flash chip with the Raspberry Pi</h1> - <p> - This document exists as a guide for reading from or writing to an SPI flash chip with the Raspberry Pi, - using the <a href="http://flashrom.org/Flashrom">flashrom</a> software. - Most revisions of the RPi should work. - </p> - <p> - This only covers SOIC-8 flash chips, for now. SOIC-16 guide coming later - (for now, it should be easy enough for you to figure this out for SOIC-16). - </p> - <p> - <a href="../">Back to previous index</a> - </p> - </div> - - <div class="section"> - -<h2> -<a id="user-content-raspberry-pi-thinkpad-x60t60-and-macbook-21" class="anchor" href="#raspberry-pi-thinkpad-x60t60-and-macbook-21" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Raspberry Pi (ThinkPad X60/T60 and Macbook 2,1)</h2> - -<p>The Raspberry Pi (a multipurpose $25 GNU+Linux computer) can be used as a BIOS flashing tool, thanks to its GPIO pins and SPI support.</p> - -<blockquote> -<p><strong>Note:</strong> The Raspberry Pi Model A is not supported, since it has no GPIO pins.</p> -</blockquote> - -<h3> -<a id="user-content-disassembling-the-thinkpad" class="anchor" href="#disassembling-the-thinkpad" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Disassembling the ThinkPad</h3> - -<p>Follow the <a href="http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/42x3550_04.pdf">X60 Hardware Maintenance Manual</a> or <a href="http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/42t7844_04.pdf">T60 Hardware Maintenance Manual</a> to disassemble the laptop, until you can access the BIOS chip.</p> - -<p>For photos, follow the <a href="http://libreboot.org/docs/install/t60_unbrick.html">Libreboot T60 Recovery Guide</a>.</p> - -<ul> -<li>On the X60, the BIOS chip is on the bottom of the motherboard, under a layer of protective black tape.</li> -<li>On the T60, the BIOS chip is just under the palmrest, but blocked by a magnesium frame (which you will have to remove).</li> -</ul> - -<h3> -<a id="user-content-pomona-clip-pinout" class="anchor" href="#pomona-clip-pinout" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Pomona Clip Pinout</h3> - -<p>Diagram of the 26 GPIO Pins of the Raspberry Pi Model B (for the Model B+ with 40 pins, start counting from the right and leave 14 pins):</p> - -<p><img src="images/rpi/0012.png" alt="" data-canonical-src="http://i.imgur.com/GjuQaJN.png"> -<img src="images/rpi/0013.png" alt="" data-canonical-src="http://i.imgur.com/WkNvOUy.png"></p> - -<pre><code> 8-pin for X60: - -~~~~ LCD (Front) ~~~~ - 8765 - ---- - | | - ---- - 1234 -~~~ Palmrest (back) ~~ -</code></pre> - -<table> -<thead> -<tr> -<th align="center">Pin #</th> -<th align="center">SPI Pin Name</th> -<th align="center">BP (Seeed)</th> -<th align="center">BP (Spkfun)</th> -<th align="center"><a href="http://beagleboard.org/Support/bone101#headers">Beagleboard Black</a></th> -<th align="center"><a href="images/rpi/0000.jpg">Raspberry Pi</a></th> -</tr> -</thead> -<tbody> -<tr> -<td align="center">1</td> -<td align="center">CS</td> -<td align="center">White</td> -<td align="center">Red</td> -<td align="center">Pin 17</td> -<td align="center">24</td> -</tr> -<tr> -<td align="center">2</td> -<td align="center">MISO</td> -<td align="center">Black</td> -<td align="center">Brown</td> -<td align="center">Pin 21</td> -<td align="center">21</td> -</tr> -<tr> -<td align="center">3</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">4</td> -<td align="center">GND</td> -<td align="center">Brown</td> -<td align="center">Black</td> -<td align="center">Pin 1</td> -<td align="center">25</td> -</tr> -<tr> -<td align="center">5</td> -<td align="center">MOSI</td> -<td align="center">Gray</td> -<td align="center">Orange</td> -<td align="center">Pin 18</td> -<td align="center">19</td> -</tr> -<tr> -<td align="center">6</td> -<td align="center">CLK</td> -<td align="center">Purple</td> -<td align="center">Yellow</td> -<td align="center">Pin 22</td> -<td align="center">23</td> -</tr> -<tr> -<td align="center">7</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">8</td> -<td align="center">3.3V</td> -<td align="center"><em>red</em></td> -<td align="center">White</td> -<td align="center"><a href="http://libreboot.org/docs/install/bbb_setup.html">3.3V PSU RED</a></td> -<td align="center">17</td> -</tr> -</tbody> -</table> - -<p>Make sure the pinouts are correct; otherwise, Flashrom will fail to detect a chip, or it will "detect" a <code>0x0</code> chip. Finally, make sure that the Pomona clip makes contact with the metal wires of the chip. It can be a challenge, but keep trying.</p> - -<h3> -<a id="user-content-how-to-supply-power-to-the-flashchip" class="anchor" href="#how-to-supply-power-to-the-flashchip" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How to supply power to the flashchip</h3> - -<p>There are two ways to supply power to the chip: plugging in an AC adapter (without turning the laptop on), and using the 8th 3.3v pin.</p> - -<p>I have found that the SST chips work best with the 8th pin, while the Macronix chips require an AC Adapter to power up.</p> - -<p><strong>Never connect both the 8th pin and the AC adapter at the same time.</strong></p> - -<p>Your results may vary.</p> - -<h2> -<a id="user-content-reading-the-flashchip" class="anchor" href="#reading-the-flashchip" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Reading the Flashchip</h2> - -<p>First, visually inspect (with a magnifying glass) the type of flashchip on the motherboard. </p> - -<p>Next, download and compile the latest Flashrom source code on the Raspberry Pi.</p> - -<pre><code>sudo apt-get install build-essential pciutils usbutils libpci-dev libusb-dev libftdi1 libftdi-dev zlib1g-dev subversion -svn co svn://flashrom.org/flashrom/trunk flashrom -cd flashrom -make -sudo modprobe spi_bcm2708 -sudo modprobe spidev -</code></pre> - -<p>If your chip is an SST, run this command:</p> - -<pre><code>sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0 -r test.rom -</code></pre> - -<p>If your chip is a Macronix, run this command:</p> - -<pre><code>sudo ./flashrom -c "MX25L1605" -p linux_spi:dev=/dev/spidev0.0 -r test.rom -</code></pre> - -<p>Next, check the md5sum of the dump:</p> - -<pre><code>md5sum test.rom -</code></pre> - -<p>Run the <code>flashrom</code> command again to make a second dump. Then, check the md5sum of the second dump:</p> - -<pre><code>md5sum test.rom -</code></pre> - -<p>If the md5sums match after three tries, <code>flashrom</code> has managed to read the flashchip precisely (but not always accurately). You may try and flash Libreboot now.</p> - -<h2> -<a id="user-content-flashing-libreboot" class="anchor" href="#flashing-libreboot" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Flashing Libreboot</h2> - -<blockquote> -<p><strong>Note:</strong> replace <code>/path/to/libreboot.rom</code> with the location of your chosen ROM, such as <code>../bin/x60/libreboot_usqwerty.rom</code>):</p> -</blockquote> - -<p>If your chip is an SST, run this command: </p> - -<pre><code>sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0 -w /path/to/libreboot.rom -</code></pre> - -<p>If your chip is a Macronix, run this command:</p> - -<pre><code>sudo ./flashrom -c "MX25L1605" -p linux_spi:dev=/dev/spidev0.0 -w /path/to/libreboot.rom -</code></pre> - -<p>Once that command outputs the following, the flash has completed successfully. If not, just flash again.</p> - -<pre><code>Reading old flash chip contents... done. -Erasing and writing flash chip... Erase/write done. -Verifying flash... VERIFIED. -</code></pre> - -<h3> -<a id="user-content-sources" class="anchor" href="#sources" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Sources</h3> - -<ul> -<li><a href="http://scruss.com/blog/2013/02/02/simple-adc-with-the-raspberry-pi/">Scruss - Simple ADC with the Raspberry Pi</a></li> -<li><a href="https://blogs.fsfe.org/the_unconventional/2015/05/08/flashing-coreboot-on-a-t60-with-a-raspberry-pi/">Flashing coreboot on a T60 with a Raspberry Pi - the_unconventional's blog</a></li> -<li> -<strong>Pomona SOIC Clip flashing</strong> - -<ul> -<li><a href="https://wiki.archlinux.org/index.php/Chromebook">Arch Linux Wiki - Installing Arch Linux on Chromebook</a></li> -<li><a href="https://drive.google.com/folderview?id=0B9f62MH0umbmRTA2Xzd5WHhjWEU&usp=sharing">Google Drive - Raspberry Pi SOIC Clip connection</a></li> -<li><a href="http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf">rPI with Flashrom and SOIC Clip Powerpoint</a></li> -</ul> -</li> -</ul> - -<h3> -<a id="user-content-raspberry-pi-pinout-diagrams" class="anchor" href="#raspberry-pi-pinout-diagrams" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Raspberry Pi Pinout Diagrams</h3> - -<table> -<thead> -<tr> -<th>MCP</th> -<th>3008 Pin</th> -<th>Pi GPIO Pin #</th> -<th>Pi Pin Name</th> -</tr> -</thead> -<tbody> -<tr> -<td>16</td> -<td><code>VDD</code></td> -<td>1</td> -<td><code>3.3 V</code></td> -</tr> -<tr> -<td>15</td> -<td><code>VREF</code></td> -<td>1</td> -<td><code>3.3 V</code></td> -</tr> -<tr> -<td>14</td> -<td><code>AGND</code></td> -<td>6</td> -<td><code>GND</code></td> -</tr> -<tr> -<td>13</td> -<td><code>CLK</code></td> -<td>23</td> -<td><code>GPIO11 SPI0_SCLK</code></td> -</tr> -<tr> -<td>12</td> -<td><code>DOUT</code></td> -<td>21</td> -<td><code>GPIO09 SPI0_MISO</code></td> -</tr> -<tr> -<td>11</td> -<td><code>DIN</code></td> -<td>19</td> -<td><code>GPIO10 SPI0_MOSI</code></td> -</tr> -<tr> -<td>10</td> -<td><code>CS</code></td> -<td>24</td> -<td><code>GPIO08 CE0</code></td> -</tr> -<tr> -<td>9</td> -<td><code>DGND</code></td> -<td>6</td> -<td><code>GND</code></td> -</tr> -</tbody> -</table> - -<ul> -<li>Source: <a href="http://raspberrypi.znix.com/hipidocs/topic_gpiopins.htm">Perl & Raspberry Pi - Raspberry Pi GPIO Pinout</a> -</li> -</ul> - -<h2> -<a id="user-content-raspberry-pi-thinkpad-x200" class="anchor" href="#raspberry-pi-thinkpad-x200" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Raspberry Pi (ThinkPad X200)</h2> - -<h3> -<a id="user-content-requirements" class="anchor" href="#requirements" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Requirements:</h3> - -<ul> -<li>An x86, x86_64, or arm7l (for changing the libreboot.rom image mac address)</li> -<li>Raspberry Pi and peripherals</li> -<li>Relevant SOIC clip</li> -<li>6 female - female jumpers</li> -<li>Internet connection</li> -<li>Screw drivers</li> -</ul> - -<p>Follow the <a href="http://libreboot.org/docs/install/x200_external.html">ThinkPad X200: Initial installation guide</a> to disassemble the laptop, and access the BIOS rom chip.</p> - -<blockquote> -<p><strong>Note:</strong> <code>x86#</code> refers to commands to be run on the x86 computer, and <code>pi#</code> refers to commands to be run on the pi. -A good practice is to make a work directory to keep your libreboot stuff inside.</p> -</blockquote> - -<pre><code>x86# mkdir ~/work -</code></pre> - -<p>Download NOOBS from <a href="https://www.raspberrypi.org/downloads/">The Raspberry Pi Foundation.</a> Torrent download recommended, and remember to seed. :)</p> - -<p> -If you're running Raspian, you can do <strong>sudo raspi-config</strong>, enable SPI under Advanced and then -spidev will be enabled. Simple, eh? -</p> - -<p><a href="http://www.libreboot.org/download/">Download Libreboot from their releases page</a>. For your safety, verify the GPG signature as well. </p> - -<pre><code>x86# gpg --keyserver prefered.keyserver.org --recv-keys 0x656F212E - -x86# for signature in $(ls *.sig); do gpg --verify $signature; done -</code></pre> - -<p>Extract NOOBS and libreboot.</p> - -<pre><code>x86# mkdir ~/work/noobs - -x86# unzip ~/Downloads/NOOBS_v1_4_1.zip -d ~/work/noobs/ - -x86# cd ~/work && tar -xvJf ~/Downloads/libreboot_bin.tar.xz -</code></pre> - -<p>Install Noobs to your fat32 formatted SD card</p> - -<pre><code>x86# cp -R ~/work/noobs/* /path/to/mounted/SDcard/ -</code></pre> - -<h3> -<a id="user-content-set-up-noobs-on-raspberry-pi" class="anchor" href="#set-up-noobs-on-raspberry-pi" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Set up NOOBS on Raspberry Pi</h3> - -<p>Plug in the NOOBs SDCard to your Raspberry Pi, and enable the following under 'Advanced Options':</p> - -<p>SSH server</p> - -<p>SPI</p> - -<p>I2C</p> - -<p>On first boot</p> - -<pre><code>pi# sudo apt-get update && sudo apt-get dist-upgrade && reboot -</code></pre> - -<p>On second boot</p> - -<pre><code>pi# sudo apt-get update && sudo apt-get install libftdi1 libftdi-dev libusb-dev libpci-dev subversion -</code></pre> - -<p>Other dependencies that should already be installed with the noobs base install include:</p> - -<p>pciutils, zlib, libusb, build-essential</p> - -<p>If they are missing then install them.</p> - -<p>Download and build flashrom.</p> - -<pre><code>pi# svn co svn://flashrom.org/flashrom/trunk ~/flashrom - -pi# cd ~/flashrom - -pi# make - -pi# sudo make install -</code></pre> - -<p>On your x86 box change the libreboot.rom mac address</p> - -<pre><code>x86# cd ~/work/libreboot_bin/ -</code></pre> - -<p>Change the mac address on the libreboot images to match yours.</p> - -<pre><code>x86# ./ich9macchange XX:XX:XX:XX:XX:XX -</code></pre> - -<p>Move the libreboot.rom image over to your pi</p> - -<pre><code>x86# scp ~/work/libreboot_bin/<path_to_your_bin> pi@your.pi.address:~/flashrom/libreboot.rom -</code></pre> - -<p>Shutdown your pi, write down your rom chip model, and wire up the clip</p> - -<pre><code>pi# sudo shutdown now -hP -</code></pre> - -<p>Chip model name</p> - -<p><img src="images/rpi/0001.jpg" alt="" data-canonical-src="http://i.imgur.com/GMbcbqS.jpg"></p> - -<p>Pinout. You may want to download the image so you can zoom in on the text.</p> - -<p><img src="images/rpi/0002.jpg" alt="" data-canonical-src="http://i.imgur.com/QkoInwr.jpg"></p> - -<table> -<thead> -<tr> -<th align="center">Pin #</th> -<th align="center">SPI Pin Name</th> -<th align="center">Raspberry Pi Pin #</th> -</tr> -</thead> -<tbody> -<tr> -<td align="center">1</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">2</td> -<td align="center">3.3V</td> -<td align="center">1</td> -</tr> -<tr> -<td align="center">3</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">4</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">5</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">6</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">7</td> -<td align="center">CS#</td> -<td align="center">24</td> -</tr> -<tr> -<td align="center">8</td> -<td align="center">S0/SIO1</td> -<td align="center">21</td> -</tr> -<tr> -<td align="center">9</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">10</td> -<td align="center">GND</td> -<td align="center">25</td> -</tr> -<tr> -<td align="center">11</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">12</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">13</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">14</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">15</td> -<td align="center">S1/SIO0</td> -<td align="center">19</td> -</tr> -<tr> -<td align="center">16</td> -<td align="center">SCLK</td> -<td align="center">23</td> -</tr> -</tbody> -</table> - -<blockquote> -<p><strong>Note:</strong> The raspberry pi 3.3V rail should be sufficient to power the chip during flashing, so no external power supply should be required; however, at the time of writing that has only been tested and confirmed for one chip, the MX25L6405D.</p> -</blockquote> - -<p>Macronix Spec sheet so you can adjust your pinout for 8 pin 4Mb chips as necessary</p> - -<p><img src="images/rpi/0014.gif" alt="" data-canonical-src="http://i.imgur.com/IQI0Shj.gif"></p> - -<p>At this point connect your SOIC clip to the rom chip before powering on your PI.</p> - -<p>Power on your Pi, and run the following. Ensure you swap out "your_chip_name" with the proper name/model of your chip. Check that it can be read successfully. If you cannot read the chip and receive an error similar to "no EEPROM Detected" or "0x0 Chip detected" then you may want to try powering off your PI, and switching the two pins which are connected to the IO ports. I.E. Connect pins (clip)8 to (pi)19 and pins (clip)15 to (pi)21</p> - -<pre><code>pi# cd ~/flashrom - -pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread1.rom - -pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread2.rom - -pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread3.rom - -pi# sha512sum romread*.rom -</code></pre> - -<p>If they are identical sha512 hashes then you can generally assume that it's safe to flash your rom.</p> - -<pre><code>pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -w libreboot.rom -</code></pre> - -<p>It may fail a couple times, but keep at it and when you get the message <code>Verifying flash... Verified</code> or <code>Warning: Chip content is identical to the requested image</code> then you're done. </p> - -<p>Shut down your pi, put your box back together, and install a libre OS for great good!</p> - -<h2> -<a id="user-content-raspberry-pi-c720-chromebook" class="anchor" href="#raspberry-pi-c720-chromebook" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Raspberry Pi (C720 Chromebook)</h2> - -<p>The Raspberry Pi (a multipurpose $25 GNU+Linux computer) can be used as a BIOS flashing tool, thanks to its GPIO pins and SPI support.</p> - -<h3> -<a id="user-content-what-you-need" class="anchor" href="#what-you-need" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What you need</h3> - -<ul> -<li>$25 - Raspberry Pi Model B (Rev.2 or higher)</li> -<li>$10-20 - SOIC-8 Pomona Clip - -<ul> -<li>Usually comes bundled with nice, color-colored <em>female to female</em> wires</li> -</ul> -</li> -</ul> - -<h3> -<a id="user-content-raspberry-pi-pinouts" class="anchor" href="#raspberry-pi-pinouts" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Raspberry Pi Pinouts</h3> - -<p>GPIO Pinouts:</p> - -<p><img src="images/rpi/0009.png" alt="" data-canonical-src="http://i.imgur.com/GjuQaJN.png"> -<img src="images/rpi/0010.png" alt="" data-canonical-src="http://i.imgur.com/WkNvOUy.png"></p> - -<blockquote> -<p>*Diagram made by <a href="http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html">"Pacman" from Win-Raid Forums*</a></p> -</blockquote> - -<p>SOIC Pinouts:</p> - -<p><img src="docs/rpi/0011.png" alt="" data-canonical-src="http://i.imgur.com/2Z9tveR.png"></p> - -<h3> -<a id="user-content-plugging-in-the-soic-clip" class="anchor" href="#plugging-in-the-soic-clip" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Plugging in the SOIC Clip</h3> - -<p>We have to connect the Raspberry Pi to the SOIC Clip as shown in the below diagram (using the f-f wires usually included with the Pomona clip).</p> - -<p><img src="images/rpi/0003.png" alt="SOIC Pinouts for C720 Chromebook" data-canonical-src="http://i.imgur.com/2Z9tveR.png"></p> - -<p>(C720 Only?) The diagram depicts a "bridged" connection. You will need to fashion one with some copper wire:</p> - -<p><img src="images/rpi/0004.jpg" alt="Bridged wires" data-canonical-src="http://i.imgur.com/iDJQu0x.jpg"></p> - -<p>Plug in the wires to the clip as shown below:</p> - -<p><img src="images/rpi/0005.jpg" alt="Pomona Clip connections" data-canonical-src="http://i.imgur.com/zQjqQCk.jpg"></p> - -<p>Plug in the other end of the wires to the Raspberry Pi as shown below:</p> - -<p><img src="images/rpi/0006.jpg" alt="Raspberry Pi connections" data-canonical-src="http://i.imgur.com/c7CcppU.jpg"></p> - -<p>(C720 only?) Plug in the "bridged" wires as shown below:</p> - -<p><img src="images/rpi/0007.jpg" alt="Bridged wires connected" data-canonical-src="http://i.imgur.com/MCvpyDi.jpg"></p> - -<p>Finally, put the Pomona SOIC clip on the chip:</p> - -<p><img src="images/rpi/0008.jpg" alt="Pomona Clip Connected" data-canonical-src="http://i.imgur.com/BBZlEgh.jpg"></p> - -<h3> -<a id="user-content-flashrom" class="anchor" href="#flashrom" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Flashrom</h3> - -<p><a href="http://www.flashrom.org/RaspberryPi">Once it's all set up, flashrom works out of the box.</a></p> - -<h3> -<a id="user-content-sources-1" class="anchor" href="#sources-1" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Sources</h3> - -<ul> -<li> -<strong>Pomona SOIC Clip flashing</strong> - -<ul> -<li><a href="https://wiki.archlinux.org/index.php/Chromebook">Arch Linux Wiki - Installing Arch Linux on Chromebook</a></li> -<li><a href="https://drive.google.com/folderview?id=0B9f62MH0umbmRTA2Xzd5WHhjWEU&usp=sharing">Google Drive - Raspberry Pi SOIC Clip connection</a></li> -<li><a href="http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf">rPI with Flashrom and SOIC Clip Powerpoint</a></li> -<li> -<a href="http://www.tnhh.net/2014/08/25/unbricking-chromebook-with-beaglebone.html">Tnhh - Unbricking Chromebook with Beaglebone</a> </li> -</ul> -</li> -<li> -<strong>Use a DIY DIP System to flash an desoldered BIOS chip</strong> - -<ul> -<li><a href="http://diy.viktak.com/2014/07/how-to-recover-laptop-after-failed-bios.html">Viktak - How to recover laptop after failed BIOS flash</a></li> -<li><a href="http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html">Win-Raid - Recover from Failed BIOS Flashing using Raspberry Pi</a></li> -</ul> -</li> -</ul> - - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Lawrence Wu <sagnessagiel@gmail.com><br/> - Copyright © 2015 snuffeluffegus <><br/> - Copyright © 2015 Kevin Keijzer <><br/> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md new file mode 100644 index 00000000..8b53196e --- /dev/null +++ b/docs/install/rpi_setup.md @@ -0,0 +1,472 @@ +<div class="section"> + +How to program an SPI flash chip with the Raspberry Pi {#pagetop} +====================================================== + +This document exists as a guide for reading from or writing to an SPI +flash chip with the Raspberry Pi, using the +[flashrom](http://flashrom.org/Flashrom) software. Most revisions of the +RPi should work. + +This only covers SOIC-8 flash chips, for now. SOIC-16 guide coming later +(for now, it should be easy enough for you to figure this out for +SOIC-16). + +[Back to previous index](../) + +</div> + +<div class="section"> + +[](#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) +------------------------------------------------------------------------------------------------------------------------------------------------------------------ + +The Raspberry Pi (a multipurpose \$25 GNU+Linux computer) can be used as +a BIOS flashing tool, thanks to its GPIO pins and SPI support. + +> **Note:** The Raspberry Pi Model A is not supported, since it has no +> GPIO pins. + +### [](#disassembling-the-thinkpad){#user-content-disassembling-the-thinkpad .anchor}Disassembling the ThinkPad + +Follow the [X60 Hardware Maintenance +Manual](http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/42x3550_04.pdf) +or [T60 Hardware Maintenance +Manual](http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/42t7844_04.pdf) +to disassemble the laptop, until you can access the BIOS chip. + +For photos, follow the [Libreboot T60 Recovery +Guide](http://libreboot.org/docs/install/t60_unbrick.html). + +- On the X60, the BIOS chip is on the bottom of the motherboard, under + a layer of protective black tape. +- On the T60, the BIOS chip is just under the palmrest, but blocked by + a magnesium frame (which you will have to remove). + +### [](#pomona-clip-pinout){#user-content-pomona-clip-pinout .anchor}Pomona Clip Pinout + +Diagram of the 26 GPIO Pins of the Raspberry Pi Model B (for the Model +B+ with 40 pins, start counting from the right and leave 14 pins): + +  + + 8-pin for X60: + + ~~~~ LCD (Front) ~~~~ + 8765 + ---- + | | + ---- + 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) + -------- -------------- ------------ ------------- --------------------------------------------------------------------- ------------------------------------- + 1 CS White Red Pin 17 24 + 2 MISO Black Brown Pin 21 21 + 3 *not used* *not used* *not used* *not used* *not used* + 4 GND Brown Black Pin 1 25 + 5 MOSI Gray Orange Pin 18 19 + 6 CLK Purple Yellow Pin 22 23 + 7 *not used* *not used* *not used* *not used* *not used* + 8 3.3V *red* White [3.3V PSU RED](http://libreboot.org/docs/install/bbb_setup.html) 17 + +Make sure the pinouts are correct; otherwise, Flashrom will fail to +detect a chip, or it will \"detect\" a `0x0` chip. Finally, make sure +that the Pomona clip makes contact with the metal wires of the chip. It +can be a challenge, but keep trying. + +### [](#how-to-supply-power-to-the-flashchip){#user-content-how-to-supply-power-to-the-flashchip .anchor}How to supply power to the flashchip + +There are two ways to supply power to the chip: plugging in an AC +adapter (without turning the laptop on), and using the 8th 3.3v pin. + +I have found that the SST chips work best with the 8th pin, while the +Macronix chips require an AC Adapter to power up. + +**Never connect both the 8th pin and the AC adapter at the same time.** + +Your results may vary. + +[](#reading-the-flashchip){#user-content-reading-the-flashchip .anchor}Reading the Flashchip +-------------------------------------------------------------------------------------------- + +First, visually inspect (with a magnifying glass) the type of flashchip +on the motherboard. + +Next, download and compile the latest Flashrom source code on the +Raspberry Pi. + + sudo apt-get install build-essential pciutils usbutils libpci-dev libusb-dev libftdi1 libftdi-dev zlib1g-dev subversion + svn co svn://flashrom.org/flashrom/trunk flashrom + cd flashrom + make + sudo modprobe spi_bcm2708 + sudo modprobe spidev + +If your chip is an SST, run this command: + + sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0 -r test.rom + +If your chip is a Macronix, run this command: + + sudo ./flashrom -c "MX25L1605" -p linux_spi:dev=/dev/spidev0.0 -r test.rom + +Next, check the md5sum of the dump: + + md5sum test.rom + +Run the `flashrom` command again to make a second dump. Then, check the +md5sum of the second dump: + + md5sum test.rom + +If the md5sums match after three tries, `flashrom` has managed to read +the flashchip precisely (but not always accurately). You may try and +flash Libreboot now. + +[](#flashing-libreboot){#user-content-flashing-libreboot .anchor}Flashing Libreboot +----------------------------------------------------------------------------------- + +> **Note:** replace `/path/to/libreboot.rom` with the location of your +> chosen ROM, such as `../bin/x60/libreboot_usqwerty.rom`): + +If your chip is an SST, run this command: + + sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0 -w /path/to/libreboot.rom + +If your chip is a Macronix, run this command: + + sudo ./flashrom -c "MX25L1605" -p linux_spi:dev=/dev/spidev0.0 -w /path/to/libreboot.rom + +Once that command outputs the following, the flash has completed +successfully. If not, just flash again. + + Reading old flash chip contents... done. + Erasing and writing flash chip... Erase/write done. + Verifying flash... VERIFIED. + +### [](#sources){#user-content-sources .anchor}Sources + +- [Scruss - Simple ADC with the Raspberry + Pi](http://scruss.com/blog/2013/02/02/simple-adc-with-the-raspberry-pi/) +- [Flashing coreboot on a T60 with a Raspberry Pi - + the\_unconventional\'s + blog](https://blogs.fsfe.org/the_unconventional/2015/05/08/flashing-coreboot-on-a-t60-with-a-raspberry-pi/) +- **Pomona SOIC Clip flashing** + - [Arch Linux Wiki - Installing Arch Linux on + Chromebook](https://wiki.archlinux.org/index.php/Chromebook) + - [Google Drive - Raspberry Pi SOIC Clip + connection](https://drive.google.com/folderview?id=0B9f62MH0umbmRTA2Xzd5WHhjWEU&usp=sharing) + - [rPI with Flashrom and SOIC Clip + Powerpoint](http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf) + +### [](#raspberry-pi-pinout-diagrams){#user-content-raspberry-pi-pinout-diagrams .anchor}Raspberry Pi Pinout Diagrams + + MCP 3008 Pin Pi GPIO Pin \# Pi Pin Name + ----- ---------- ---------------- -------------------- + 16 `VDD` 1 `3.3 V` + 15 `VREF` 1 `3.3 V` + 14 `AGND` 6 `GND` + 13 `CLK` 23 `GPIO11 SPI0_SCLK` + 12 `DOUT` 21 `GPIO09 SPI0_MISO` + 11 `DIN` 19 `GPIO10 SPI0_MOSI` + 10 `CS` 24 `GPIO08 CE0` + 9 `DGND` 6 `GND` + +- Source: [Perl & Raspberry Pi - Raspberry Pi GPIO + Pinout](http://raspberrypi.znix.com/hipidocs/topic_gpiopins.htm) + +[](#raspberry-pi-thinkpad-x200){#user-content-raspberry-pi-thinkpad-x200 .anchor}Raspberry Pi (ThinkPad X200) +------------------------------------------------------------------------------------------------------------- + +### [](#requirements){#user-content-requirements .anchor}Requirements: + +- An x86, x86\_64, or arm7l (for changing the libreboot.rom image mac + address) +- Raspberry Pi and peripherals +- Relevant SOIC clip +- 6 female - female jumpers +- Internet connection +- Screw drivers + +Follow the [ThinkPad X200: Initial installation +guide](http://libreboot.org/docs/install/x200_external.html) to +disassemble the laptop, and access the BIOS rom chip. + +> **Note:** `x86#` refers to commands to be run on the x86 computer, and +> `pi#` refers to commands to be run on the pi. A good practice is to +> make a work directory to keep your libreboot stuff inside. + + x86# mkdir ~/work + +Download NOOBS from [The Raspberry Pi +Foundation.](https://www.raspberrypi.org/downloads/) Torrent download +recommended, and remember to seed. :) + +If you\'re running Raspian, you can do **sudo raspi-config**, enable SPI +under Advanced and then spidev will be enabled. Simple, eh? + +[Download Libreboot from their releases +page](http://www.libreboot.org/download/). For your safety, verify the +GPG signature as well. + + x86# gpg --keyserver prefered.keyserver.org --recv-keys 0x656F212E + + x86# for signature in $(ls *.sig); do gpg --verify $signature; done + +Extract NOOBS and libreboot. + + x86# mkdir ~/work/noobs + + x86# unzip ~/Downloads/NOOBS_v1_4_1.zip -d ~/work/noobs/ + + x86# cd ~/work && tar -xvJf ~/Downloads/libreboot_bin.tar.xz + +Install Noobs to your fat32 formatted SD card + + x86# cp -R ~/work/noobs/* /path/to/mounted/SDcard/ + +### [](#set-up-noobs-on-raspberry-pi){#user-content-set-up-noobs-on-raspberry-pi .anchor}Set up NOOBS on Raspberry Pi + +Plug in the NOOBs SDCard to your Raspberry Pi, and enable the following +under \'Advanced Options\': + +SSH server + +SPI + +I2C + +On first boot + + pi# sudo apt-get update && sudo apt-get dist-upgrade && reboot + +On second boot + + pi# sudo apt-get update && sudo apt-get install libftdi1 libftdi-dev libusb-dev libpci-dev subversion + +Other dependencies that should already be installed with the noobs base +install include: + +pciutils, zlib, libusb, build-essential + +If they are missing then install them. + +Download and build flashrom. + + pi# svn co svn://flashrom.org/flashrom/trunk ~/flashrom + + pi# cd ~/flashrom + + pi# make + + pi# sudo make install + +On your x86 box change the libreboot.rom mac address + + x86# cd ~/work/libreboot_bin/ + +Change the mac address on the libreboot images to match yours. + + x86# ./ich9macchange XX:XX:XX:XX:XX:XX + +Move the libreboot.rom image over to your pi + + x86# scp ~/work/libreboot_bin/<path_to_your_bin> pi@your.pi.address:~/flashrom/libreboot.rom + +Shutdown your pi, write down your rom chip model, and wire up the clip + + pi# sudo shutdown now -hP + +Chip model name + + + +Pinout. You may want to download the image so you can zoom in on the +text. + + + + Pin \# SPI Pin Name Raspberry Pi Pin \# + -------- -------------- --------------------- + 1 *not used* *not used* + 2 3.3V 1 + 3 *not used* *not used* + 4 *not used* *not used* + 5 *not used* *not used* + 6 *not used* *not used* + 7 CS\# 24 + 8 S0/SIO1 21 + 9 *not used* *not used* + 10 GND 25 + 11 *not used* *not used* + 12 *not used* *not used* + 13 *not used* *not used* + 14 *not used* *not used* + 15 S1/SIO0 19 + 16 SCLK 23 + +> **Note:** The raspberry pi 3.3V rail should be sufficient to power the +> chip during flashing, so no external power supply should be required; +> however, at the time of writing that has only been tested and +> confirmed for one chip, the MX25L6405D. + +Macronix Spec sheet so you can adjust your pinout for 8 pin 4Mb chips as +necessary + + + +At this point connect your SOIC clip to the rom chip before powering on +your PI. + +Power on your Pi, and run the following. Ensure you swap out +\"your\_chip\_name\" with the proper name/model of your chip. Check that +it can be read successfully. If you cannot read the chip and receive an +error similar to \"no EEPROM Detected\" or \"0x0 Chip detected\" then +you may want to try powering off your PI, and switching the two pins +which are connected to the IO ports. I.E. Connect pins (clip)8 to (pi)19 +and pins (clip)15 to (pi)21 + + pi# cd ~/flashrom + + pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread1.rom + + pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread2.rom + + pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread3.rom + + pi# sha512sum romread*.rom + +If they are identical sha512 hashes then you can generally assume that +it\'s safe to flash your rom. + + pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -w libreboot.rom + +It may fail a couple times, but keep at it and when you get the message +`Verifying flash... Verified` or +`Warning: Chip content is identical to the requested image` then you\'re +done. + +Shut down your pi, put your box back together, and install a libre OS +for great good! + +[](#raspberry-pi-c720-chromebook){#user-content-raspberry-pi-c720-chromebook .anchor}Raspberry Pi (C720 Chromebook) +------------------------------------------------------------------------------------------------------------------- + +The Raspberry Pi (a multipurpose \$25 GNU+Linux computer) can be used as +a BIOS flashing tool, thanks to its GPIO pins and SPI support. + +### [](#what-you-need){#user-content-what-you-need .anchor}What you need + +- \$25 - Raspberry Pi Model B (Rev.2 or higher) +- \$10-20 - SOIC-8 Pomona Clip + - Usually comes bundled with nice, color-colored *female to + female* wires + +### [](#raspberry-pi-pinouts){#user-content-raspberry-pi-pinouts .anchor}Raspberry Pi Pinouts + +GPIO Pinouts: + +  + +> \*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: + + + +### [](#plugging-in-the-soic-clip){#user-content-plugging-in-the-soic-clip .anchor}Plugging in the SOIC Clip + +We have to connect the Raspberry Pi to the SOIC Clip as shown in the +below diagram (using the f-f wires usually included with the Pomona +clip). + + + +(C720 Only?) The diagram depicts a \"bridged\" connection. You will need +to fashion one with some copper wire: + + + +Plug in the wires to the clip as shown below: + + + +Plug in the other end of the wires to the Raspberry Pi as shown below: + + + +(C720 only?) Plug in the \"bridged\" wires as shown below: + + + +Finally, put the Pomona SOIC clip on the chip: + + + +### [](#flashrom){#user-content-flashrom .anchor}Flashrom + +[Once it\'s all set up, flashrom works out of the +box.](http://www.flashrom.org/RaspberryPi) + +### [](#sources-1){#user-content-sources-1 .anchor}Sources + +- **Pomona SOIC Clip flashing** + - [Arch Linux Wiki - Installing Arch Linux on + Chromebook](https://wiki.archlinux.org/index.php/Chromebook) + - [Google Drive - Raspberry Pi SOIC Clip + connection](https://drive.google.com/folderview?id=0B9f62MH0umbmRTA2Xzd5WHhjWEU&usp=sharing) + - [rPI with Flashrom and SOIC Clip + Powerpoint](http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf) + - [Tnhh - Unbricking Chromebook with + Beaglebone](http://www.tnhh.net/2014/08/25/unbricking-chromebook-with-beaglebone.html) +- **Use a DIY DIP System to flash an desoldered BIOS chip** + - [Viktak - How to recover laptop after failed BIOS + flash](http://diy.viktak.com/2014/07/how-to-recover-laptop-after-failed-bios.html) + - [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) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/t400_external.html b/docs/install/t400_external.html deleted file mode 100644 index 39f9c930..00000000 --- a/docs/install/t400_external.html +++ /dev/null @@ -1,580 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad T400: flashing tutorial (BeagleBone Black)</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Flashing the T400 with a BeagleBone Black</h1> - - <p>Initial flashing instructions for T400.</p> - <p> - This guide is for those who want libreboot on their ThinkPad T400 - while they still have the original Lenovo BIOS present. This guide - can also be followed (adapted) if you brick your T400, to know how - to recover. - </p> - - <p> - An - <a href="https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/43y6629_05.pdf#page=386"> - "HMM"</a> (Hardware Maintenance Manual) detailing the process of - [dis]assembly is available for this model. - Be careful when reassembling the laptop as 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. - </p> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - - <h1 id="preinstall">T400 laptops with libreboot pre-installed</h1> - - <p> - If you don't want to install libreboot yourself, companies exist that sell these laptops - with libreboot pre-installed, along with a free GNU+Linux distribution. - </p> - <p> - Check the <a href="../../suppliers">suppliers</a> page for more information. - </p> - - </div> - - <div class="section"> - - <h2 id="serial_port">Serial port</h2> - - <p> - 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. - </p> - - </div> - - <div class="section" id="cpu_compatibility"> - - <h1>A note about CPUs</h1> - <p> - <a href="http://www.thinkwiki.org/wiki/Category:T400">ThinkWiki</a> has a list of CPUs - for this system. The Core 2 Duo P8400, P8600 and P8700 are believed to work in libreboot. - The T9600 was confirmed to work, so the T9500/T9550 probably also work. - </p> - - <h2>Quad-core CPUs</h2> - - <p> - Incompatible. Do not use. - </p> - - </div> - - <div class="section" id="switchable_graphics"> - - <h1>A note about GPUs</h1> - - <p> - Some models have an Intel GPU, while others have both an ATI and an Intel GPU; this - is referred to as "switchable graphics". In the <i>BIOS setup</i> program - for lenovobios, you can specify that the system will use one or the other (but not both). - </p> - - <p> - Libreboot is known to work on systems with only the Intel GPU, using native graphics initialization. - On systems with switchable graphics, the Intel GPU is used and the ATI GPU is disabled, so - native graphics initialization works all the same. - </p> - - <h1>CPU paste required</h1> - - <p> - See <a href="#paste">#paste</a>. - </p> - - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br> - # <b>flashrom -p internal -V</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos"> - - <h1 id="macaddress">MAC address</h1> - - <p> - On the T400, the MAC address for the onboard - gigabit ethernet chipset is stored inside the flash chip, - along with other configuration data. - </p> - <p> - Keep a note of the MAC address before disassembly; this is - very important, because you will need to insert this into - the libreboot ROM image before flashing it. - It will be written in one of these locations: - </p> - - <p> - <img src="images/t400/macaddress0.jpg" alt="" /> - <img src="images/t400/macaddress1.jpg" alt="" /> - <img src="images/x200/disassembly/0001.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h1>Initial BBB configuration</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - configure the BBB for flashing. - </p> - - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-16 (clip: Pomona 5252): - </p> -<pre> -POMONA 5252 (correlate with the BBB guide) -=== ethernet jack and VGA port ==== - NC - - 21 - 1 - - 17 - NC - - NC - NC - - NC - NC - - NC - NC - - NC - 18 - - 3.3V (PSU) - 22 - - NC - this is pin 1 on the flash chip -=== SATA port === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/t400/0065.jpg" alt="" /> -</pre> - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): - </p> -<pre> -POMONA 5250 (correlate with the BBB guide) -=== RAM slots ==== - 18 - - 1 - 22 - - NC - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== slot where the AC jack is connected ===<br/> -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/t500/0060.jpg" alt="" /> -</pre> - - <h2> - The procedure - </h2> - - <p> - Remove <i>all</i> screws, placing them in the order that you removed them:<br/> - <img src="images/t400/0001.jpg" alt="" /> - <img src="images/t400/0002.jpg" alt="" /> - </p> - <p> - Remove those three screws then remove the rear bezel:<br/> - <img src="images/t400/0003.jpg" alt="" /> - <img src="images/t400/0004.jpg" alt="" /> - <img src="images/t400/0005.jpg" alt="" /> - <img src="images/t400/0006.jpg" alt="" /> - </p> - <p> - Remove the speakers:<br/> - <img src="images/t400/0007.jpg" alt="" /> - <img src="images/t400/0008.jpg" alt="" /> - <img src="images/t400/0009.jpg" alt="" /> - <img src="images/t400/0010.jpg" alt="" /> - <img src="images/t400/0011.jpg" alt="" /> - </p> - <p> - Remove the wifi:<br/> - <img src="images/t400/0012.jpg" alt="" /> - <img src="images/t400/0013.jpg" alt="" /> - </p> - <p> - Remove this cable:<br/> - <img src="images/t400/0014.jpg" alt="" /> - <img src="images/t400/0015.jpg" alt="" /> - <img src="images/t400/0016.jpg" alt="" /> - <img src="images/t400/0017.jpg" alt="" /> - <img src="images/t400/0018.jpg" alt="" /> - </p> - <p> - Unroute those antenna wires:<br/> - <img src="images/t400/0019.jpg" alt="" /> - <img src="images/t400/0020.jpg" alt="" /> - <img src="images/t400/0021.jpg" alt="" /> - <img src="images/t400/0022.jpg" alt="" /> - <img src="images/t400/0023.jpg" alt="" /> - </p> - <p> - Remove the LCD assembly:<br/> - <img src="images/t400/0024.jpg" alt="" /> - <img src="images/t400/0025.jpg" alt="" /> - <img src="images/t400/0026.jpg" alt="" /> - <img src="images/t400/0027.jpg" alt="" /> - <img src="images/t400/0028.jpg" alt="" /> - <img src="images/t400/0029.jpg" alt="" /> - <img src="images/t400/0030.jpg" alt="" /> - <img src="images/t400/0031.jpg" alt="" /> - </p> - <p> - Disconnect the NVRAM battery:<br/> - <img src="images/t400/0033.jpg" alt="" /> - </p> - <p> - Disconnect the fan:<br/> - <img src="images/t400/0034.jpg" alt="" /> - </p> - <p> - Unscrew these:<br/> - <img src="images/t400/0035.jpg" alt="" /> - <img src="images/t400/0036.jpg" alt="" /> - <img src="images/t400/0037.jpg" alt="" /> - <img src="images/t400/0038.jpg" alt="" /> - </p> - <p> - Unscrew the heatsink, then lift it off:<br/> - <img src="images/t400/0039.jpg" alt="" /> - <img src="images/t400/0040.jpg" alt="" /> - </p> - <p> - Disconnect the power jack:<br/> - <img src="images/t400/0041.jpg" alt="" /> - <img src="images/t400/0042.jpg" alt="" /> - </p> - <p> - Loosen this:<br/> - <img src="images/t400/0043.jpg" alt="" /> - </p> - <p> - Remove this:<br/> - <img src="images/t400/0044.jpg" alt="" /> - <img src="images/t400/0045.jpg" alt="" /> - <img src="images/t400/0046.jpg" alt="" /> - <img src="images/t400/0047.jpg" alt="" /> - <img src="images/t400/0048.jpg" alt="" /> - </p> - <p> - Unscrew these:<br/> - <img src="images/t400/0049.jpg" alt="" /> - <img src="images/t400/0050.jpg" alt="" /> - </p> - <p> - Remove this:<br/> - <img src="images/t400/0051.jpg" alt="" /> - <img src="images/t400/0052.jpg" alt="" /> - </p> - <p> - Unscrew this:<br/> - <img src="images/t400/0053.jpg" alt="" /> - </p> - <p> - Remove the motherboard (the cage is still attached) from - the right hand side, then lift it out:<br/> - <img src="images/t400/0054.jpg" alt="" /> - <img src="images/t400/0055.jpg" alt="" /> - <img src="images/t400/0056.jpg" alt="" /> - </p> - <p> - Remove these screws, placing the screws in the same layout - and marking each screw hole (so that you know what ones - to put the screws back into later): - <img src="images/t400/0057.jpg" alt="" /> - <img src="images/t400/0058.jpg" alt="" /> - <img src="images/t400/0059.jpg" alt="" /> - <img src="images/t400/0060.jpg" alt="" /> - <img src="images/t400/0061.jpg" alt="" /> - <img src="images/t400/0062.jpg" alt="" /> - </p> - <p> - Separate the motherboard:<br/> - <img src="images/t400/0063.jpg" alt="" /> - <img src="images/t400/0064.jpg" alt="" /> - </p> - <p> - Connect your programmer, then connect GND and 3.3V<br/> - <img src="images/t400/0065.jpg" alt="" /> - <img src="images/t400/0066.jpg" alt="" /> - <img src="images/t400/0067.jpg" alt="" /> - <img src="images/t400/0069.jpg" alt="" /> - <img src="images/t400/0070.jpg" alt="" /> - <img src="images/t400/0071.jpg" alt="" /> - </p> - <p> - A dedicated 3.3V PSU was used to create this guide, but - at ATX PSU is also fine:<br/> - <img src="images/t400/0072.jpg" alt="" /> - </p> - - <p> - Of course, make sure to turn on your PSU:<br/> - <img src="images/x200/disassembly/0013.jpg" alt="" /> - </p> - - <p> - Now, you should be ready to install libreboot. - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - <p> - Log in as root on your BBB, using the instructions in <a href="bbb_setup.html#bbb_access">bbb_setup.html#bbb_access</a>. - </p> - <p> - Test that flashrom works:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512</b><br/> - In this case, the output was: - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. -Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" -Please specify which chip definition to use with the -c <chipname> option. -</pre> - <p> - How to backup factory.rom (change the -c option as neeed, for your flash chip):<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom</b><br/> - Note: the <b>-c</b> option is not required in libreboot's patched flashrom, because - the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/> - Now compare the 3 images:<br/> - # <b>sha512sum factory*.rom</b><br/> - 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 behaviour in the original firmware - that could be replicated in coreboot and libreboot. - </p> - <p> - Follow the instructions at <a href="../hcl/gm45_remove_me.html#ich9gen">../hcl/gm45_remove_me.html#ich9gen</a> - 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. <b>Make sure - to always change the MAC address to one that is correct for your system.</b> - </p> - <p> - Now flash it:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V</b> - </p> - <p> - <img src="images/x200/disassembly/0015.jpg" alt="" /> - </p> - <p> - You might see errors, but if it says <b>Verifying flash... VERIFIED</b> at the end, then it's flashed and should boot. - If you see errors, try again (and again, and again); the message <b>Chip content is identical to the requested image</b> - is also an indication of a successful installation. - </p> - <p> - Example output from running the command (see above): - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Reading old flash chip contents... done. -Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 -ERASE FAILED! -Reading current flash chip contents... done. Looking for another erase function. -Erase/write done. -Verifying flash... VERIFIED. -</pre> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos" id="paste"> - - <h1>Thermal paste (IMPORTANT)</h1> - - <p> - Because part of this procedure involved removing the heatsink, you will need to apply new paste. - Arctic MX-4 is ok. You will also need isopropyl alcohol and an anti-static cloth to clean with. - </p> - - <p> - When re-installing the heatsink, you must first clean off all old paste with the alcohol/cloth. - Then apply new paste. Arctic MX-4 is also much better than the default paste used on these systems. - </p> - - <p> - <img src="images/t400/paste.jpg" alt="" /> - </p> - - <p> - 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. - </p> - - </div> - - <div class="section"> - - <h1 id="wifi">Wifi</h1> - - <p> - 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 - <a href="../hcl/#recommended_wifi">../hcl/#recommended_wifi</a>. - </p> - - <p> - Some T400 laptops might come with an Atheros chipset, but this is 802.11g only. - </p> - - <p> - It is recommended that you install a new wifi chipset. This can only - be done after installing libreboot, because the original firmware has - a whitelist of approved chips, and it will refuse to boot if you - use an 'unauthorized' wifi card. - </p> - - <p> - The following photos show an Atheros AR5B95 being installed, to - replace the Intel chip that this T400 came with:<br/> - <img src="images/t400/0012.jpg" alt="" /> - <img src="images/t400/ar5b95.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h1 id="wwan">WWAN</h1> - <p> - 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. - </p> - <p> - Not to be confused with wifi (wifi is fine). - </p> - - </div> - - <div class="section photos"> - - <h1 id="memory">Memory</h1> - - <p> - You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs - (speed/size). Non-matching pairs won't work. You can also install a - single module (meaning, one of the slots will be empty) in slot 0. - </p> - - <p> - Make sure that the RAM you buy is the 2Rx8 density. - </p> - - <p> - <a href="http://www.forum.thinkpads.com/viewtopic.php?p=760721">This page</a> might be useful for RAM compatibility info - (note: coreboot raminit is different, so this page might be BS) - </p> - - <p> - The following photo shows 8GiB (2x4GiB) of RAM installed:<br/> - <img src="images/t400/memory.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h2> - Boot it! - </h2> - <p> - You should see something like this: - </p> - <p> - <img src="images/t400/boot0.jpg" alt="" /> - <img src="images/t400/boot1.jpg" alt="" /> - </p> - - <p> - Now <a href="../gnulinux/">install GNU+Linux</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md new file mode 100644 index 00000000..568d5062 --- /dev/null +++ b/docs/install/t400_external.md @@ -0,0 +1,451 @@ +<div class="section"> + +Flashing the T400 with a BeagleBone Black {#pagetop} +========================================= + +Initial flashing instructions for T400. + +This guide is for those who want libreboot on their ThinkPad T400 while +they still have the original Lenovo BIOS present. This guide can also be +followed (adapted) if you brick your T400, to know how to recover. + +An +[\"HMM\"](https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/43y6629_05.pdf#page=386) +(Hardware Maintenance Manual) detailing the process of \[dis\]assembly +is available for this model. Be careful when reassembling the laptop as +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. + +[Back to main index](./) + +</div> + +<div class="section"> + +T400 laptops with libreboot pre-installed {#preinstall} +========================================= + +If you don\'t want to install libreboot yourself, companies exist that +sell these laptops with libreboot pre-installed, along with a free +GNU+Linux distribution. + +Check the [suppliers](../../suppliers) page for more information. + +</div> + +<div class="section"> + +Serial port {#serial_port} +----------- + +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. + +</div> + +<div id="cpu_compatibility" class="section"> + +A note about CPUs +================= + +[ThinkWiki](http://www.thinkwiki.org/wiki/Category:T400) has a list of +CPUs for this system. The Core 2 Duo P8400, P8600 and P8700 are believed +to work in libreboot. The T9600 was confirmed to work, so the +T9500/T9550 probably also work. + +Quad-core CPUs +-------------- + +Incompatible. Do not use. + +</div> + +<div id="switchable_graphics" class="section"> + +A note about GPUs +================= + +Some models have an Intel GPU, while others have both an ATI and an +Intel GPU; this is referred to as \"switchable graphics\". In the *BIOS +setup* program for lenovobios, you can specify that the system will use +one or the other (but not both). + +Libreboot is known to work on systems with only the Intel GPU, using +native graphics initialization. On systems with switchable graphics, the +Intel GPU is used and the ATI GPU is disabled, so native graphics +initialization works all the same. + +CPU paste required +================== + +See [\#paste](#paste). + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section photos"> + +MAC address {#macaddress} +=========== + +On the T400, the MAC address for the onboard gigabit ethernet chipset is +stored inside the flash chip, along with other configuration data. + +Keep a note of the MAC address before disassembly; this is very +important, because you will need to insert this into the libreboot ROM +image before flashing it. It will be written in one of these locations: + +  + + +</div> + +<div class="section photos"> + +Initial BBB configuration +========================= + +Refer to [bbb\_setup.html](bbb_setup.html) for how to configure the BBB +for flashing. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-16 (clip: Pomona 5252): + + POMONA 5252 (correlate with the BBB guide) + === ethernet jack and VGA port ==== + NC - - 21 + 1 - - 17 + NC - - NC + NC - - NC + NC - - NC + NC - - NC + 18 - - 3.3V (PSU) + 22 - - NC - this is pin 1 on the flash chip + === SATA port === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-8 (clip: Pomona 5250): + + POMONA 5250 (correlate with the BBB guide) + === RAM slots ==== + 18 - - 1 + 22 - - NC + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === slot where the AC jack is connected === + + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +The procedure +------------- + +Remove *all* screws, placing them in the order that you removed them:\ +  + +Remove those three screws then remove the rear bezel:\ +  +  + +Remove the speakers:\ +  +  + + +Remove the wifi:\ +  + +Remove this cable:\ +  +  + + +Unroute those antenna wires:\ +  +  + + +Remove the LCD assembly:\ +  +  +  +  + +Disconnect the NVRAM battery:\ + + +Disconnect the fan:\ + + +Unscrew these:\ +  +  + +Unscrew the heatsink, then lift it off:\ +  + +Disconnect the power jack:\ +  + +Loosen this:\ + + +Remove this:\ +  +  + + +Unscrew these:\ +  + +Remove this:\ +  + +Unscrew this:\ + + +Remove the motherboard (the cage is still attached) from the right hand +side, then lift it out:\ +  + + +Remove these screws, placing the screws in the same layout and marking +each screw hole (so that you know what ones to put the screws back into +later):   +  +  + +Separate the motherboard:\ +  + +Connect your programmer, then connect GND and 3.3V\ +  +  +  + +A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is +also fine:\ + + +Of course, make sure to turn on your PSU:\ + + +Now, you should be ready to install libreboot. + +Flashrom binaries for ARM (tested on a BBB) are distributed in +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:\ +\# **./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) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. + Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" + 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**\ +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**\ +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 +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) +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 +path/to/libreboot/rom/image.rom -V** + + + +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 +installation. + +Example output from running the command (see above): + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Reading old flash chip contents... done. + Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 + ERASE FAILED! + Reading current flash chip contents... done. Looking for another erase function. + Erase/write done. + Verifying flash... VERIFIED. + +[Back to top of page.](#pagetop) + +</div> + +<div id="paste" class="section photos"> + +Thermal paste (IMPORTANT) +========================= + +Because part of this procedure involved removing the heatsink, you will +need to apply new paste. Arctic MX-4 is ok. You will also need isopropyl +alcohol and an anti-static cloth to clean with. + +When re-installing the heatsink, you must first clean off all old paste +with the alcohol/cloth. Then apply new paste. Arctic MX-4 is also much +better than the default paste used on these systems. + + + +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. + +</div> + +<div class="section"> + +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). + +Some T400 laptops might come with an Atheros chipset, but this is +802.11g only. + +It is recommended that you install a new wifi chipset. This can only be +done after installing libreboot, because the original firmware has a +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:\ +  + +</div> + +<div class="section"> + +WWAN +==== + +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. + +Not to be confused with wifi (wifi is fine). + +</div> + +<div class="section photos"> + +Memory +====== + +You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs +(speed/size). Non-matching pairs won\'t work. You can also install a +single module (meaning, one of the slots will be empty) in slot 0. + +Make sure that the RAM you buy is the 2Rx8 density. + +[This page](http://www.forum.thinkpads.com/viewtopic.php?p=760721) might +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:\ + + +</div> + +<div class="section photos"> + +Boot it! +-------- + +You should see something like this: + +  + +Now [install GNU+Linux](../gnulinux/). + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/t500_external.html b/docs/install/t500_external.html deleted file mode 100644 index 6d7dedc5..00000000 --- a/docs/install/t500_external.html +++ /dev/null @@ -1,580 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad T500: flashing tutorial (BeagleBone Black)</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Flashing the T500 with a BeagleBone Black</h1> - - <p>Initial flashing instructions for T500.</p> - <p> - 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. - </p> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - - <h1 id="t400">Libreboot T400</h1> - <p> - You may also be interested in the smaller, more portable <a href="t400_external.html">Libreboot T400</a>. - </p> - - </div> - - <div class="section"> - - <h2 id="serial_port">Serial port</h2> - - <p> - 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. - </p> - - </div> - - <div class="section" id="cpu_compatibility"> - - <h1>A note about CPUs</h1> - <p> - <a href="http://www.thinkwiki.org/wiki/Category:T500">ThinkWiki</a> has a list of CPUs - for this system. The Core 2 Duo P8400, P8600 and P8700 are believed to work in libreboot. - The T9600 was also tested on the T400 and confirmed working, so the T9400/T9500/T9550 probably - also work, but they are untested. - </p> - - <h2>Quad-core CPUs</h2> - - <p> - Incompatible. Do not use. - </p> - - </div> - - <div class="section" id="switchable_graphics"> - - <h1>A note about GPUs</h1> - - <p> - Some models have an Intel GPU, while others have both an ATI and an Intel GPU; this - is referred to as "switchable graphics". In the <i>BIOS setup</i> program - for lenovobios, you can specify that the system will use one or the other (but not both). - </p> - - <p> - Libreboot is known to work on systems with only the Intel GPU, using native graphics initialization. - On systems with switchable graphics, the Intel GPU is used and the ATI GPU is disabled, so - native graphics initialization works all the same. - </p> - - <h1>CPU paste required</h1> - - <p> - See <a href="#paste">#paste</a>. - </p> - - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br/> - # <b>flashrom -p internal -V</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos"> - - <h1 id="macaddress">MAC address</h1> - - <p> - On the T500, the MAC address for the onboard - gigabit ethernet chipset is stored inside the flash chip, - along with other configuration data. - </p> - <p> - Keep a note of the MAC address before disassembly; this is - very important, because you will need to insert this into - the libreboot ROM image before flashing it. - It will be written in one of these locations: - </p> - - <p> - <img src="images/t400/macaddress0.jpg" alt="" /> - <img src="images/t400/macaddress1.jpg" alt="" /> - <img src="images/x200/disassembly/0001.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h1>Initial BBB configuration</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - configure the BBB for flashing. - </p> - - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-16 (clip: Pomona 5252): - </p> -<pre> -POMONA 5252 (correlate with the BBB guide) -=== ethernet jack and VGA port ==== - NC - - 21 - 1 - - 17 - NC - - NC - NC - - NC - NC - - NC - NC - - NC - 18 - - 3.3V (PSU) - 22 - - NC - this is pin 1 on the flash chip -=== SATA port === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/t400/0065.jpg" alt="" /> -</pre> - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): - </p> -<pre> -POMONA 5250 (correlate with the BBB guide) -=== RAM slots ==== - 18 - - 1 - 22 - - NC - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== slot where the AC jack is connected ===<br/> -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/t500/0060.jpg" alt="" /> -</pre> - - <h2> - The procedure - </h2> - - <p> - Remove all screws:<br/> - <img src="images/t500/0000.jpg" alt="" /><br/> - 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:<br/> - <img src="images/t500/0001.jpg" alt="" /> - <img src="images/t500/0002.jpg" alt="" /> - </p> - <p> - Remove the HDD/SSD and optical drive:<br/> - <img src="images/t500/0003.jpg" alt="" /> - <img src="images/t500/0004.jpg" alt="" /> - </p> - <p> - Remove the palm rest:<br/> - <img src="images/t500/0005.jpg" alt="" /> - <img src="images/t500/0006.jpg" alt="" /> - </p> - <p> - Remove the keyboard and rear bezel:<br/> - <img src="images/t500/0007.jpg" alt="" /> - <img src="images/t500/0008.jpg" alt="" /> - <img src="images/t500/0009.jpg" alt="" /> - <img src="images/t500/0010.jpg" alt="" /> - <img src="images/t500/0011.jpg" alt="" /> - <img src="images/t500/0012.jpg" alt="" /> - </p> - <p> - 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:<br/> - <img src="images/t500/0013.jpg" alt="" /> - <img src="images/t500/0017.jpg" alt="" /> - <img src="images/t500/0018.jpg" alt="" /> - </p> - <p> - Remove this frame, and then remove the wifi chip:<br/> - <img src="images/t500/0014.jpg" alt="" /> - <img src="images/t500/0015.jpg" alt="" /> - <img src="images/t500/0016.jpg" alt="" /> - </p> - <p> - Remove the speakers:<br/> - <img src="images/t500/0019.jpg" alt="" /> - <img src="images/t500/0020.jpg" alt="" /> - <img src="images/t500/0021.jpg" alt="" /> - <img src="images/t500/0022.jpg" alt="" /> - <img src="images/t500/0023.jpg" alt="" /> - <img src="images/t500/0024.jpg" alt="" /> - <img src="images/t500/0025.jpg" alt="" /> - </p> - <p> - Remove the NVRAM battery (already removed in this photo):<br/> - <img src="images/t500/0026.jpg" alt="" /> - </p> - <p> - 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:<br/> - <img src="images/t500/0027.jpg" alt="" /> - </p> - <p> - Unroute the antenna wires:<br/> - <img src="images/t500/0028.jpg" alt="" /> - <img src="images/t500/0029.jpg" alt="" /> - <img src="images/t500/0030.jpg" alt="" /> - <img src="images/t500/0031.jpg" alt="" /> - </p> - <p> - Disconnect the LCD cable from the motherboard:<br/> - <img src="images/t500/0032.jpg" alt="" /> - <img src="images/t500/0033.jpg" alt="" /> - </p> - <p> - Remove the LCD assembly hinge screws, and then remove the LCD - assembly:<br/> - <img src="images/t500/0034.jpg" alt="" /> - <img src="images/t500/0035.jpg" alt="" /> - <img src="images/t500/0036.jpg" alt="" /> - </p> - <p> - Remove the fan and heatsink:<br/> - <img src="images/t500/0037.jpg" alt="" /> - <img src="images/t500/0038.jpg" alt="" /> - <img src="images/t500/0039.jpg" alt="" /> - </p> - <p> - Remove this screw:<br/> - <img src="images/t500/0040.jpg" alt="" /> - </p> - <p> - Remove these cables, keeping note of how and in what - arrangement they are connected:<br/> - <img src="images/t500/0041.jpg" alt="" /> - <img src="images/t500/0042.jpg" alt="" /> - <img src="images/t500/0043.jpg" alt="" /> - <img src="images/t500/0044.jpg" alt="" /> - <img src="images/t500/0045.jpg" alt="" /> - <img src="images/t500/0046.jpg" alt="" /> - <img src="images/t500/0047.jpg" alt="" /> - <img src="images/t500/0048.jpg" alt="" /> - <img src="images/t500/0049.jpg" alt="" /> - </p> - <p> - Disconnect the power jack:<br/> - <img src="images/t500/0050.jpg" alt="" /> - <img src="images/t500/0051.jpg" alt="" /> - </p> - <p> - Remove the motherboard and cage from the base - (the marked hole is where those cables were routed through):<br/> - <img src="images/t500/0052.jpg" alt="" /> - <img src="images/t500/0053.jpg" alt="" /> - </p> - <p> - 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):<br/> - <img src="images/t500/0054.jpg" alt="" /> - <img src="images/t500/0055.jpg" alt="" /> - </p> - <p> - Also remove this:<br/> - <img src="images/t500/0056.jpg" alt="" /> - <img src="images/t500/0057.jpg" alt="" /> - </p> - <p> - Separate the motherboard from the cage:<br/> - <img src="images/t500/0058.jpg" alt="" /> - <img src="images/t500/0059.jpg" alt="" /> - </p> - <p> - The flash chip is next to the memory slots. On this - system, it was a SOIC-8 (4MiB or 32Mb) flash chip:<br/> - <img src="images/t500/0060.jpg" alt="" /> - </p> - <p> - Connect your programmer, then connect GND and 3.3V<br/> - <img src="images/t500/0061.jpg" alt="" /><br/> - <img src="images/t400/0067.jpg" alt="" /> - <img src="images/t400/0069.jpg" alt="" /> - <img src="images/t400/0070.jpg" alt="" /> - <img src="images/t400/0071.jpg" alt="" /> - </p> - <p> - A dedicated 3.3V PSU was used to create this guide, but - at ATX PSU is also fine:<br/> - <img src="images/t400/0072.jpg" alt="" /> - </p> - - <p> - Of course, make sure to turn on your PSU:<br/> - <img src="images/x200/disassembly/0013.jpg" alt="" /> - </p> - - <p> - Now, you should be ready to install libreboot. - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - <p> - Log in as root on your BBB, using the instructions in <a href="bbb_setup.html#bbb_access">bbb_setup.html#bbb_access</a>. - </p> - <p> - Test that flashrom works:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512</b><br/> - In this case, the output was: - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. -Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" -Please specify which chip definition to use with the -c <chipname> option. -</pre> - <p> - How to backup factory.rom (change the -c option as neeed, for your flash chip):<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom</b><br/> - Note: the <b>-c</b> option is not required in libreboot's patched flashrom, because - the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/> - Now compare the 3 images:<br/> - # <b>sha512sum factory*.rom</b><br/> - 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 behaviour in the original firmware - that could be replicated in coreboot and libreboot. - </p> - <p> - Follow the instructions at <a href="../hcl/gm45_remove_me.html#ich9gen">../hcl/gm45_remove_me.html#ich9gen</a> - 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. <b>Make sure - to always change the MAC address to one that is correct for your system.</b> - </p> - <p> - Now flash it:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V</b> - </p> - <p> - <img src="images/x200/disassembly/0015.jpg" alt="" /> - </p> - <p> - You might see errors, but if it says <b>Verifying flash... VERIFIED</b> at the end, then it's flashed and should boot. - If you see errors, try again (and again, and again); the message <b>Chip content is identical to the requested image</b> - is also an indication of a successful installation. - </p> - <p> - Example output from running the command (see above): - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Reading old flash chip contents... done. -Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 -ERASE FAILED! -Reading current flash chip contents... done. Looking for another erase function. -Erase/write done. -Verifying flash... VERIFIED. -</pre> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos" id="paste"> - - <h1>Thermal paste (IMPORTANT)</h1> - - <p> - Because part of this procedure involved removing the heatsink, you will need to apply new paste. - Arctic MX-4 is ok. You will also need isopropyl alcohol and an anti-static cloth to clean with. - </p> - - <p> - When re-installing the heatsink, you must first clean off all old paste with the alcohol/cloth. - Then apply new paste. Arctic MX-4 is also much better than the default paste used on these systems. - </p> - - <p> - <img src="images/t400/paste.jpg" alt="" /> - </p> - - <p> - 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. - </p> - - </div> - - <div class="section"> - - <h1 id="wifi">Wifi</h1> - - <p> - 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 - <a href="../hcl/#recommended_wifi">../hcl/#recommended_wifi</a>. - </p> - - <p> - Some T500 laptops might come with an Atheros chipset, but this is 802.11g only. - </p> - - <p> - It is recommended that you install a new wifi chipset. This can only - be done after installing libreboot, because the original firmware has - a whitelist of approved chips, and it will refuse to boot if you - use an 'unauthorized' wifi card. - </p> - - <p> - The following photos show an Atheros AR5B95 being installed, to - replace the Intel chip that this T500 came with:<br/> - <img src="images/t400/0012.jpg" alt="" /> - <img src="images/t400/ar5b95.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h1 id="wwan">WWAN</h1> - <p> - If you have a WWAN/3G card and/or sim card reader, remove them permanently. - The WWAN-3G card has DMA, and proprietary firmware inside; the technology is - identical to what is used in mobile phones, so it can also track your movements. - </p> - <p> - Not to be confused with wifi (wifi is fine). - </p> - - </div> - - <div class="section photos"> - - <h1 id="memory">Memory</h1> - - <p> - You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs - (speed/size). Non-matching pairs won't work. You can also install a - single module (meaning, one of the slots will be empty) in slot 0. - </p> - - <p> - Make sure that the RAM you buy is the 2Rx8 density. - </p> - - <p> - <a href="http://www.forum.thinkpads.com/viewtopic.php?p=760721">This page</a> might be useful for RAM compatibility info - (note: coreboot raminit is different, so this page might be BS) - </p> - - <p> - The following photo shows 8GiB (2x4GiB) of RAM installed:<br/> - <img src="images/t400/memory.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h2> - Boot it! - </h2> - <p> - You should see something like this: - </p> - <p> - <img src="images/t500/0062.jpg" alt="" /> - </p> - - <p> - Now <a href="../gnulinux/">install GNU+Linux</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md new file mode 100644 index 00000000..b7b60bb7 --- /dev/null +++ b/docs/install/t500_external.md @@ -0,0 +1,456 @@ +<div class="section"> + +Flashing the T500 with a BeagleBone Black {#pagetop} +========================================= + +Initial flashing instructions for T500. + +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. + +[Back to main index](./) + +</div> + +<div class="section"> + +Libreboot T400 {#t400} +============== + +You may also be interested in the smaller, more portable [Libreboot +T400](t400_external.html). + +</div> + +<div class="section"> + +Serial port {#serial_port} +----------- + +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. + +</div> + +<div id="cpu_compatibility" class="section"> + +A note about CPUs +================= + +[ThinkWiki](http://www.thinkwiki.org/wiki/Category:T500) has a list of +CPUs for this system. The Core 2 Duo P8400, P8600 and P8700 are believed +to work in libreboot. The T9600 was also tested on the T400 and +confirmed working, so the T9400/T9500/T9550 probably also work, but they +are untested. + +Quad-core CPUs +-------------- + +Incompatible. Do not use. + +</div> + +<div id="switchable_graphics" class="section"> + +A note about GPUs +================= + +Some models have an Intel GPU, while others have both an ATI and an +Intel GPU; this is referred to as \"switchable graphics\". In the *BIOS +setup* program for lenovobios, you can specify that the system will use +one or the other (but not both). + +Libreboot is known to work on systems with only the Intel GPU, using +native graphics initialization. On systems with switchable graphics, the +Intel GPU is used and the ATI GPU is disabled, so native graphics +initialization works all the same. + +CPU paste required +================== + +See [\#paste](#paste). + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section photos"> + +MAC address {#macaddress} +=========== + +On the T500, the MAC address for the onboard gigabit ethernet chipset is +stored inside the flash chip, along with other configuration data. + +Keep a note of the MAC address before disassembly; this is very +important, because you will need to insert this into the libreboot ROM +image before flashing it. It will be written in one of these locations: + +  + + +</div> + +<div class="section photos"> + +Initial BBB configuration +========================= + +Refer to [bbb\_setup.html](bbb_setup.html) for how to configure the BBB +for flashing. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-16 (clip: Pomona 5252): + + POMONA 5252 (correlate with the BBB guide) + === ethernet jack and VGA port ==== + NC - - 21 + 1 - - 17 + NC - - NC + NC - - NC + NC - - NC + NC - - NC + 18 - - 3.3V (PSU) + 22 - - NC - this is pin 1 on the flash chip + === SATA port === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-8 (clip: Pomona 5250): + + POMONA 5250 (correlate with the BBB guide) + === RAM slots ==== + 18 - - 1 + 22 - - NC + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === slot where the AC jack is connected === + + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +The procedure +------------- + +Remove all screws:\ +\ +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:\ +  + +Remove the HDD/SSD and optical drive:\ +  + +Remove the palm rest:\ +  + +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:\ +  + + +Remove this frame, and then remove the wifi chip:\ +  + + +Remove the speakers:\ +  +  +  + + +Remove the NVRAM battery (already removed in this photo):\ + + +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:\ + + +Unroute the antenna wires:\ +  +  + +Disconnect the LCD cable from the motherboard:\ +  + +Remove the LCD assembly hinge screws, and then remove the LCD assembly:\ +  + + +Remove the fan and heatsink:\ +  + + +Remove this screw:\ + + +Remove these cables, keeping note of how and in what arrangement they +are connected:\ +  +  +  +  + + +Disconnect the power jack:\ +  + +Remove the motherboard and cage from the base (the marked hole is where +those cables were routed through):\ +  + +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):\ +  + +Also remove this:\ +  + +Separate the motherboard from the cage:\ +  + +The flash chip is next to the memory slots. On this system, it was a +SOIC-8 (4MiB or 32Mb) flash chip:\ + + +Connect your programmer, then connect GND and 3.3V\ +\ +  +  + +A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is +also fine:\ + + +Of course, make sure to turn on your PSU:\ + + +Now, you should be ready to install libreboot. + +Flashrom binaries for ARM (tested on a BBB) are distributed in +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:\ +\# **./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) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. + Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" + 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**\ +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**\ +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 +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) +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 +path/to/libreboot/rom/image.rom -V** + + + +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 +installation. + +Example output from running the command (see above): + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Reading old flash chip contents... done. + Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 + ERASE FAILED! + Reading current flash chip contents... done. Looking for another erase function. + Erase/write done. + Verifying flash... VERIFIED. + +[Back to top of page.](#pagetop) + +</div> + +<div id="paste" class="section photos"> + +Thermal paste (IMPORTANT) +========================= + +Because part of this procedure involved removing the heatsink, you will +need to apply new paste. Arctic MX-4 is ok. You will also need isopropyl +alcohol and an anti-static cloth to clean with. + +When re-installing the heatsink, you must first clean off all old paste +with the alcohol/cloth. Then apply new paste. Arctic MX-4 is also much +better than the default paste used on these systems. + + + +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. + +</div> + +<div class="section"> + +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). + +Some T500 laptops might come with an Atheros chipset, but this is +802.11g only. + +It is recommended that you install a new wifi chipset. This can only be +done after installing libreboot, because the original firmware has a +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:\ +  + +</div> + +<div class="section"> + +WWAN +==== + +If you have a WWAN/3G card and/or sim card reader, remove them +permanently. The WWAN-3G card has DMA, and proprietary firmware inside; +the technology is identical to what is used in mobile phones, so it can +also track your movements. + +Not to be confused with wifi (wifi is fine). + +</div> + +<div class="section photos"> + +Memory +====== + +You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs +(speed/size). Non-matching pairs won\'t work. You can also install a +single module (meaning, one of the slots will be empty) in slot 0. + +Make sure that the RAM you buy is the 2Rx8 density. + +[This page](http://www.forum.thinkpads.com/viewtopic.php?p=760721) might +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:\ + + +</div> + +<div class="section photos"> + +Boot it! +-------- + +You should see something like this: + + + +Now [install GNU+Linux](../gnulinux/). + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/t60_unbrick.html b/docs/install/t60_unbrick.html deleted file mode 100644 index 40cb3a1e..00000000 --- a/docs/install/t60_unbrick.html +++ /dev/null @@ -1,322 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad T60: Recovery guide</title> -</head> - -<body> - - <div class="section"> - <h1>ThinkPad T60: Recovery guide</h1> - <p>This section documents how to recover from a bad flash that prevents your ThinkPad T60 from booting.</p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - <h2>Table of Contents</h2> - <ul> - <li> - Types of brick: - <ul> - <li><a href="#bucts_brick">Brick type 1: bucts not reset</a></li> - <li><a href="#recovery">Brick type 2: bad rom (or user error), system won't boot</a></li> - </ul> - </li> - </ul> - </div> - - <div class="section"> - <h1 id="bucts_brick">Brick type 1: bucts not reset.</h1> - <p> - 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.<br/><br/> - - 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:<br/> - <img src="../images/t60_dev/0006.JPG" alt="" /><br/><br/> - - *Those dd commands should be applied to all newly compiled T60 ROM images (the ROM images in libreboot binary archives already have this applied!):<br/> - dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k<br/> - dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump<br/> - dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc<br/> - (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, - using those instructions: <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>. - (it says x60, but instructions for t60 are identical) - </p> - </div> - - <div class="section"> - - <h1 id="recovery">bad rom (or user error), system won't boot</h1> - - <p> - In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your system from - booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your system is bricked and will not boot at all. - </p> - <p> - "Unbricking" means flashing a known-good (working) ROM. The problem: 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). - </p> - - <p> - Remove those screws and remove the HDD:<br/> - <img src="../images/t60_dev/0001.JPG" alt="" /> <img src="../images/t60_dev/0002.JPG" alt="" /> - </p> - - <p> - Lift off the palm rest:<br/> - <img src="../images/t60_dev/0003.JPG" alt="" /> - </p> - - <p> - Lift up the keyboard, pull it back a bit, flip it over like that and then disconnect it from the board:<br/> - <img src="../images/t60_dev/0004.JPG" alt="" /> <img src="../images/t60_dev/0005.JPG" alt="" /> <img src="../images/t60_dev/0006.JPG" alt="" /> - </p> - - <p> - Gently wedge both sides loose:<br/> - <img src="../images/t60_dev/0007.JPG" alt="" /> <img src="../images/t60_dev/0008.JPG" alt="" /> - </p> - - <p> - Remove that cable from the position:<br/> - <img src="../images/t60_dev/0009.JPG" alt="" /> <img src="../images/t60_dev/0010.JPG" alt="" /> - </p> - - <p> - Now remove that bezel. Remove wifi, nvram battery and speaker connector (also remove 56k modem, on the left of wifi):<br/> - <img src="../images/t60_dev/0011.JPG" alt="" /> - </p> - - <p> - Remove those screws:<br/> - <img src="../images/t60_dev/0012.JPG" alt="" /> - </p> - - <p> - Disconnect the power jack:<br/> - <img src="../images/t60_dev/0013.JPG" alt="" /> - </p> - - <p> - Remove nvram battery:<br/> - <img src="../images/t60_dev/0014.JPG" alt="" /> - </p> - - <p> - Disconnect cable (for 56k modem) and disconnect the other cable:<br/> - <img src="../images/t60_dev/0015.JPG" alt="" /> <img src="../images/t60_dev/0016.JPG" alt="" /> - </p> - - <p> - Disconnect speaker cable:<br/> - <img src="../images/t60_dev/0017.JPG" alt="" /> - </p> - - <p> - Disconnect the other end of the 56k modem cable:<br/> - <img src="../images/t60_dev/0018.JPG" alt="" /> - </p> - - <p> - Make sure you removed it:<br/> - <img src="../images/t60_dev/0019.JPG" alt="" /> - </p> - - <p> - Unscrew those:<br/> - <img src="../images/t60_dev/0020.JPG" alt="" /> - </p> - - <p> - Make sure you removed those:<br/> - <img src="../images/t60_dev/0021.JPG" alt="" /> - </p> - - <p> - Disconnect LCD cable from board:<br/> - <img src="../images/t60_dev/0022.JPG" alt="" /> - </p> - - <p> - Remove those screws then remove the LCD assembly:<br/> - <img src="../images/t60_dev/0023.JPG" alt="" /> <img src="../images/t60_dev/0024.JPG" alt="" /> <img src="../images/t60_dev/0025.JPG" alt="" /> - </p> - - <p> - Once again, make sure you removed those:<br/> - <img src="../images/t60_dev/0026.JPG" alt="" /> - </p> - - <p> - Remove the shielding containing the motherboard, then flip it over. 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:<br/> - <img src="../images/t60_dev/0027.JPG" alt="" /> <img src="../images/t60_dev/0028.JPG" alt="" /> <img src="../images/t60_dev/0029.JPG" alt="" /> - <img src="../images/t60_dev/0031.JPG" alt="" /> <img src="../images/t60_dev/0032.JPG" alt="" /> <img src="../images/t60_dev/0033.JPG" alt="" /> - </p> - - <p> - Now wire up the BBB and the Pomona with your PSU.<br/> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to setup - the BBB for flashing.<br/> - <b>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)</b><br/> - <img src="../images/t60_dev/0030.JPG" alt="" /><br/> - Correlate the following with the BBB guide linked above: - </p> -<pre> -POMONA 5250: -=== DVD drive ==== - 18 - - 1 - 22 - - NC ---- RAM is on this end - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== audio jacks === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> -</pre> - - <p> - Connect the pomona from the BBB to the flash chip. No pics unfortunately. (use the text diagram above). - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - - <p> - SSH'd into the BBB:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom</b> - </p> - <p> - It should be <b>Verifying flash... VERIFIED</b> at the end. If flashrom complains about multiple flash chip - definitions detected, then choose one of them following the instructions in the output. - </p> - - <p> - Put those screws back:<br/> - <img src="../images/t60_dev/0047.JPG" alt="" /> - </p> - - <p> - Put it back into lower chassis:<br/> - <img src="../images/t60_dev/0048.JPG" alt="" /> - </p> - - <p> - Attach LCD and insert screws (also, attach the lcd cable to the board):<br/> - <img src="../images/t60_dev/0049.JPG" alt="" /> - </p> - - <p> - Insert those screws:<br/> - <img src="../images/t60_dev/0050.JPG" alt="" /> - </p> - - <p> - 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<br/> - <img src="../images/t60_dev/0051.JPG" alt="" /> - </p> - - <p> - Attach the heatsink and install the screws (also, make sure to install the AC jack as highlighted):<br/> - <img src="../images/t60_dev/0052.JPG" alt="" /> - </p> - - <p> - Reinstall that upper bezel:<br/> - <img src="../images/t60_dev/0053.JPG" alt="" /> - </p> - - <p> - Do that:<br/> - <img src="../images/t60_dev/0054.JPG" alt="" /> <img src="../images/t60_dev/0055.JPG" alt="" /> - </p> - - <p> - 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. - </p> - - <p> - Attach keyboard and install nvram battery:<br/> - <img src="../images/t60_dev/0056.JPG" alt="" /> <img src="../images/t60_dev/0057.JPG" alt="" /> - </p> - - <p> - Place keyboard and (sorry, forgot to take pics) reinstall the palmrest and insert screws on the underside:<br/> - <img src="../images/t60_dev/0058.JPG" alt="" /> - </p> - - <p> - It lives!<br/> - <img src="../images/t60_dev/0071.JPG" alt="" /> <img src="../images/t60_dev/0072.JPG" alt="" /> <img src="../images/t60_dev/0073.JPG" alt="" /> - </p> - - <p> - Always stress test ('stress -c 2' and xsensors. below 90C is ok) when replacing cpu paste/heatsink:<br/> - <img src="../images/t60_dev/0074.JPG" alt="" /> - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/t60_unbrick.md b/docs/install/t60_unbrick.md new file mode 100644 index 00000000..c86fd294 --- /dev/null +++ b/docs/install/t60_unbrick.md @@ -0,0 +1,259 @@ +<div class="section"> + +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](./) + +</div> + +<div class="section"> + +Table of Contents +----------------- + +- Types of brick: + - [Brick type 1: bucts not reset](#bucts_brick) + - [Brick type 2: bad rom (or user error), system won\'t + boot](#recovery) + +</div> + +<div class="section"> + +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.\ +\ +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:\ +\ +\ +\*Those dd commands should be applied to all newly compiled T60 ROM +images (the ROM images in libreboot binary archives already have this +applied!):\ +dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s +coreboot.rom) - 0x10000\] count=64k\ +dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] +count=64k | hexdump\ +dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s +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) + +</div> + +<div class="section"> + +bad rom (or user error), system won\'t boot {#recovery} +=========================================== + +In this scenario, you compiled a ROM that had an incorrect +configuration, or there is an actual bug preventing your system from +booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash +while Lenovo BIOS was running. In any case, your system is bricked and +will not boot at all. + +\"Unbricking\" means flashing a known-good (working) ROM. The problem: +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:\ +  + +Lift off the palm rest:\ + + +Lift up the keyboard, pull it back a bit, flip it over like that and +then disconnect it from the board:\ +  + + +Gently wedge both sides loose:\ +  + +Remove that cable from the position:\ +  + +Now remove that bezel. Remove wifi, nvram battery and speaker connector +(also remove 56k modem, on the left of wifi):\ + + +Remove those screws:\ + + +Disconnect the power jack:\ + + +Remove nvram battery:\ + + +Disconnect cable (for 56k modem) and disconnect the other cable:\ +  + +Disconnect speaker cable:\ + + +Disconnect the other end of the 56k modem cable:\ + + +Make sure you removed it:\ + + +Unscrew those:\ + + +Make sure you removed those:\ + + +Disconnect LCD cable from board:\ + + +Remove those screws then remove the LCD assembly:\ +  + + +Once again, make sure you removed those:\ + + +Remove the shielding containing the motherboard, then flip it over. +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:\ +  +  +  + +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.\ +**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)**\ +\ +Correlate the following with the BBB guide linked above: + + POMONA 5250: + === DVD drive ==== + 18 - - 1 + 22 - - NC ---- RAM is on this end + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === audio jacks === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +Connect the pomona from the BBB to the flash chip. No pics +unfortunately. (use the text diagram above). + +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 +yourrom.rom** + +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 it back into lower chassis:\ + + +Attach LCD and insert screws (also, attach the lcd cable to the board):\ + + +Insert those screws:\ + + +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\ + + +Attach the heatsink and install the screws (also, make sure to install +the AC jack as highlighted):\ + + +Reinstall that upper bezel:\ + + +Do that:\ +  + +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:\ +  + +Place keyboard and (sorry, forgot to take pics) reinstall the palmrest +and insert screws on the underside:\ + + +It lives!\ +  + + +Always stress test (\'stress -c 2\' and xsensors. below 90C is ok) when +replacing cpu paste/heatsink:\ + + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/x200_external.html b/docs/install/x200_external.html deleted file mode 100644 index 0d820355..00000000 --- a/docs/install/x200_external.html +++ /dev/null @@ -1,477 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad X200: flashing tutorial (BeagleBone Black)</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Flashing the X200 with a BeagleBone Black</h1> - <p>Initial flashing instructions for X200.</p> - <p> - This guide is for those who want libreboot on their ThinkPad X200 - while they still have the original Lenovo BIOS present. This guide - can also be followed (adapted) if you brick your X200, to know how - to recover. - </p> - - <ul> - <li><a href="#preinstall">X200 laptops with libreboot pre-installed</a></li> - <li><a href="#flashchips">Flash chips</a></li> - <li><a href="#macaddress">MAC address</a></li> - <li><a href="#clip">Initial BBB configuration and installation procedure</a></li> - <li><a href="#boot">Boot it!</a></li> - <li><a href="#wifi">Wifi</a></li> - <li><a href="#wwan">wwan</a></li> - <li><a href="#memory">Memory</a></li> - <li><a href="#gpio33">X200S and X200 Tablet users: GPIO33 trick will not work.</a></li> - </ul> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - - <h1 id="preinstall">X200 laptops with libreboot pre-installed</h1> - - <p> - If you don't want to install libreboot yourself, companies exist that sell these laptops - with libreboot pre-installed, along with a free GNU+Linux distribution. - </p> - <p> - Check the <a href="../../suppliers">suppliers</a> page for more information. - </p> - - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br/> - # <b>flashrom -p internal -V</b> - </p> - - <p> - The X200S and X200 Tablet will use a WSON-8 flash chip, on the - bottom of the motherboard (this requires removal of the - motherboard). <b>Not all X200S/X200T are supported; - see <a href="../hcl/x200.html#x200s">../hcl/x200.html#x200s</a>.</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="macaddress">MAC address</h1> - - <p> - On the X200/X200S/X200T, the MAC address for the onboard - gigabit ethernet chipset is stored inside the flash chip, - along with other configuration data. - </p> - <p> - Keep a note of the MAC address before disassembly; this is - very important, because you will need to insert this into - the libreboot ROM image before flashing it. - It will be written in one of these locations: - </p> - - <p> - <img src="images/x200/disassembly/0002.jpg" alt="" /> - <img src="images/x200/disassembly/0001.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h1 id="clip">Initial BBB configuration</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - set up the BBB for flashing. - </p> - - <p> - The following shows how to connect the clip to the BBB (on the P9 header), for SOIC-16 (clip: Pomona 5252): - </p> -<pre> -POMONA 5252 (correlate with the BBB guide) -=== front (display) on your X200 ==== - NC - - 21 - 1 - - 17 - NC - - NC - NC - - NC - NC - - NC - NC - - NC - 18 - - 3.3V (PSU) - 22 - - NC - this is pin 1 on the flash chip -=== back (palmrest) on your X200 === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> -Here is a photo of the SOIC-16 flash chip. Pins are labelled:<br/> -<img src="images/x200/x200_pomona.jpg" alt="" /> -</pre> - <p> - The following shows how to connect the clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): - </p> -<pre> -POMONA 5250 (correlate with the BBB guide) -=== left side of the X200 (where the VGA port is) ==== - 18 - - 1 - 22 - - NC - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip. in front of it is the screen. -=== right side of the X200 (where the audio jacks are) === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> -Here is a photo of the SOIC-8 flash chip. The pins are labelled:<br/> -<img title="Copyright 2015 Patrick "P. J." McDermott <pj@pehjota.net>, see license notice at the end of this document" src="images/x200/soic8.jpg" /> - -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? -</pre> - <p> - <b>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).<br/> - The following image shows how this is done:</b><br/> - <img src="images/x200/wson_soldered.jpg" title="Copyright 2014 Steve Shenton <sgsit@libreboot.org> see license notice at the end of this document" alt="" /> - <br/> - 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 <a href="../hcl/gm45_remove_me.html#flashchips">../hcl/gm45_remove_me.html#flashchips</a> 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. - </p> - - <h2> - The procedure - </h2> - <p> - 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). - </p> - <p> - Remove these screws:<br/> - <img src="images/x200/disassembly/0003.jpg" alt="" /> - </p> - <p> - Push the keyboard forward, gently, then lift it off and - disconnect it from the board:<br/> - <img src="images/x200/disassembly/0004.jpg" alt="" /> - <img src="images/x200/disassembly/0005.jpg" alt="" /> - </p> - <p> - Pull the palm rest off, lifting from the left and right side at the back of the - palm rest:<br/> - <img src="images/x200/disassembly/0006.jpg" alt="" /> - </p> - <p> - Lift back the tape that covers a part of the flash chip, and - then connect the clip:<br/> - <img src="images/x200/disassembly/0007.jpg" alt="" /> - <img src="images/x200/disassembly/0008.jpg" alt="" /> - </p> - <p> - On pin 2 of the BBB, where you have the ground (GND), connect the - ground to your PSU:<br/> - <img src="images/x200/disassembly/0009.jpg" alt="" /> - <img src="images/x200/disassembly/0010.jpg" alt="" /> - </p> - <p> - Connect the 3.3V supply from your PSU to the flash chip (via - the clip):<br/> - <img src="images/x200/disassembly/0011.jpg" alt="" /> - <img src="images/x200/disassembly/0012.jpg" alt="" /> - </p> - <p> - Of course, make sure that your PSU is also plugged in and - turn on:<br/> - <img src="images/x200/disassembly/0013.jpg" alt="" /> - </p> - <p> - 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):<br/> - <img src="images/x200/disassembly/0014.jpg" alt="" /> - </p> - <p> - Now, you should be ready to install libreboot. - </p> - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - <p> - Log in as root on your BBB, using the instructions in - <a href="bbb_setup.html#bbb_access">bbb_setup.html#bbb_access</a>. - </p> - - <p> - Test that flashrom works:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512</b><br/> - In this case, the output was: - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. -Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" -Please specify which chip definition to use with the -c <chipname> option. -</pre> - <p> - How to backup factory.rom (change the -c option as neeed, for your flash chip):<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom</b><br/> - Note: the <b>-c</b> option is not required in libreboot's patched flashrom, because - the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/> - Now compare the 3 images:<br/> - # <b>sha512sum factory*.rom</b><br/> - 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 behaviour in the original firmware - that could be replicated in coreboot and libreboot. - </p> - <p> - Follow the instructions at <a href="../hcl/gm45_remove_me.html#ich9gen">../hcl/gm45_remove_me.html#ich9gen</a> - 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. <b>Make sure - to always change the MAC address to one that is correct for your system.</b> - </p> - <p> - Now flash it:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V</b> - </p> - <p> - <img src="images/x200/disassembly/0015.jpg" alt="" /> - </p> - <p> - You might see errors, but if it says <b>Verifying flash... VERIFIED</b> at the end, then it's flashed and should boot. - If you see errors, try again (and again, and again); the message <b>Chip content is identical to the requested image</b> - is also an indication of a successful installation. - </p> - <p> - Example output from running the command (see above): - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Reading old flash chip contents... done. -Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 -ERASE FAILED! -Reading current flash chip contents... done. Looking for another erase function. -Erase/write done. -Verifying flash... VERIFIED. -</pre> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="wifi">Wifi</h1> - - <p> - 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 - <a href="../hcl/#recommended_wifi">../hcl/#recommended_wifi</a>. - </p> - - <p> - Some X200 laptops come with an Atheros chipset, but this is 802.11g only. - </p> - - <p> - It is recommended that you install a new wifi chipset. This can only - be done after installing libreboot, because the original firmware has - a whitelist of approved chips, and it will refuse to boot if you - use an 'unauthorized' wifi card. - </p> - - <p> - The following photos show an Atheros AR5B95 being installed, to - replace the Intel chip that this X200 came with:<br/> - <img src="images/x200/disassembly/0016.jpg" alt="" /> - <img src="images/x200/disassembly/0017.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h1 id="wwan">WWAN</h1> - <p> - 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. - </p> - <p> - Not to be confused with wifi (wifi is fine). - </p> - - </div> - - <div class="section"> - - <h1 id="memory">Memory</h1> - - <p> - You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs - (speed/size). Non-matching pairs won't work. You can also install a - single module (meaning, one of the slots will be empty) in slot 0. - </p> - <p> - NOTE: according to users repors, non matching pairs (e.g. 1+2 GiB) might work in some cases. - </p> - <p> - Make sure that the RAM you buy is the 2Rx8 density. - </p> - - <p> - In this photo, 8GiB of RAM (2x4GiB) is installed:<br/> - <img src="images/x200/disassembly/0018.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h2 id="boot"> - Boot it! - </h2> - <p> - You should see something like this: - </p> - <p> - <img src="images/x200/disassembly/0019.jpg" alt="" /> - </p> - - <p> - Now <a href="../gnulinux/">install GNU+Linux</a>. - </p> - - </div> - - <div class="section"> - <h2 id="gpio33"> - X200S and X200 Tablet users: GPIO33 trick will not work. - </h2> - <p> - sgsit found out about a pin called GPIO33, which can be grounded to 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. - </p> - <p> - Look just above the 7 in TP37 (that's GPIO33):<br/> - <img src="../hcl/images/x200/gpio33_location.jpg" alt="" /> - </p> - <p> - By default we would see this in lenovobios, when trying flashrom -p internal -w rom.rom: - </p> -<pre> -FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only. -FREG2: Warning: Management Engine region (0x00001000-0x005f5fff) is locked. -</pre> - <p> - With GPIO33 grounded during boot, this disabled the flash protections as set - by descriptor, and stopped the ME from starting. The output changed to: - </p> -<pre> -The Flash Descriptor Override Strap-Pin is set. Restrictions implied by -the Master Section of the flash descriptor are NOT in effect. Please note -that <b>Protected Range (PR) restrictions still apply.</b> -</pre> - <p> - The part in bold is what got us. This was still observed: - </p> -<pre> -PR0: Warning: 0x007e0000-0x01ffffff is read-only. -PR4: Warning: 0x005f8000-0x005fffff is locked. -</pre> - - <p> - It is actually possible to disable these protections. Lenovobios does, - when updating the BIOS (proprietary one). One possible way to go about this - would be to debug the BIOS update utility from Lenovo, to find out - how it's disabling these protections. Some more research is available here: - <a href="http://www.coreboot.org/Board:lenovo/x200/internal_flashing_research">http://www.coreboot.org/Board:lenovo/x200/internal_flashing_research</a> - </p> - - <p> - On a related note, libreboot has a utility that could help with investigating this: - <a href="../hcl/gm45_remove_me.html#demefactory">../hcl/gm45_remove_me.html#demefactory</a> - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md new file mode 100644 index 00000000..fe936c1f --- /dev/null +++ b/docs/install/x200_external.md @@ -0,0 +1,403 @@ +<div class="section"> + +Flashing the X200 with a BeagleBone Black {#pagetop} +========================================= + +Initial flashing instructions for X200. + +This guide is for those who want libreboot on their ThinkPad X200 while +they still have the original Lenovo BIOS present. This guide can also be +followed (adapted) if you brick your X200, to know how to recover. + +- [X200 laptops with libreboot pre-installed](#preinstall) +- [Flash chips](#flashchips) +- [MAC address](#macaddress) +- [Initial BBB configuration and installation procedure](#clip) +- [Boot it!](#boot) +- [Wifi](#wifi) +- [wwan](#wwan) +- [Memory](#memory) +- [X200S and X200 Tablet users: GPIO33 trick will not work.](#gpio33) + +[Back to main index](./) + +</div> + +<div class="section"> + +X200 laptops with libreboot pre-installed {#preinstall} +========================================= + +If you don\'t want to install libreboot yourself, companies exist that +sell these laptops with libreboot pre-installed, along with a free +GNU+Linux distribution. + +Check the [suppliers](../../suppliers) page for more information. + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V** + +The X200S and X200 Tablet will use a WSON-8 flash chip, on the bottom of +the motherboard (this requires removal of the motherboard). **Not all +X200S/X200T are supported; see +[../hcl/x200.html\#x200s](../hcl/x200.html#x200s).** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +MAC address {#macaddress} +=========== + +On the X200/X200S/X200T, the MAC address for the onboard gigabit +ethernet chipset is stored inside the flash chip, along with other +configuration data. + +Keep a note of the MAC address before disassembly; this is very +important, because you will need to insert this into the libreboot ROM +image before flashing it. It will be written in one of these locations: + + + + +</div> + +<div class="section"> + +Initial BBB configuration {#clip} +========================= + +Refer to [bbb\_setup.html](bbb_setup.html) for how to set up the BBB for +flashing. + +The following shows how to connect the clip to the BBB (on the P9 +header), for SOIC-16 (clip: Pomona 5252): + + POMONA 5252 (correlate with the BBB guide) + === front (display) on your X200 ==== + NC - - 21 + 1 - - 17 + NC - - NC + NC - - NC + NC - - NC + NC - - NC + 18 - - 3.3V (PSU) + 22 - - NC - this is pin 1 on the flash chip + === back (palmrest) on your X200 === + 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-16 flash chip. Pins are labelled: + + + +The following shows how to connect the clip to the BBB (on the P9 +header), for SOIC-8 (clip: Pomona 5250): + + POMONA 5250 (correlate with the BBB guide) + === left side of the X200 (where the VGA port is) ==== + 18 - - 1 + 22 - - NC + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip. in front of it is the screen. + === right side of the X200 (where the audio jacks are) === + 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:**\ +\ +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) +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. + +The procedure +------------- + +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:\ + + +Push the keyboard forward, gently, then lift it off and disconnect it +from the board:\ + + + +Pull the palm rest off, lifting from the left and right side at the back +of the palm rest:\ + + +Lift back the tape that covers a part of the flash chip, and then +connect the clip:\ + + + +On pin 2 of the BBB, where you have the ground (GND), connect the ground +to your PSU:\ + + + +Connect the 3.3V supply from your PSU to the flash chip (via the clip):\ + + + +Of course, make sure that your PSU is also plugged in and turn on:\ + + +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):\ + + +Now, you should be ready to install libreboot. + +Flashrom binaries for ARM (tested on a BBB) are distributed in +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:\ +\# **./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) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. + Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" + 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**\ +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**\ +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 +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) +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 +path/to/libreboot/rom/image.rom -V** + + + +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 +installation. + +Example output from running the command (see above): + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Reading old flash chip contents... done. + Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 + ERASE FAILED! + Reading current flash chip contents... done. Looking for another erase function. + Erase/write done. + Verifying flash... VERIFIED. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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). + +Some X200 laptops come with an Atheros chipset, but this is 802.11g +only. + +It is recommended that you install a new wifi chipset. This can only be +done after installing libreboot, because the original firmware has a +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:\ + + + +</div> + +<div class="section"> + +WWAN +==== + +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. + +Not to be confused with wifi (wifi is fine). + +</div> + +<div class="section"> + +Memory +====== + +You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs +(speed/size). Non-matching pairs won\'t work. You can also install a +single module (meaning, one of the slots will be empty) in slot 0. + +NOTE: according to users repors, non matching pairs (e.g. 1+2 GiB) might +work in some cases. + +Make sure that the RAM you buy is the 2Rx8 density. + +In this photo, 8GiB of RAM (2x4GiB) is installed:\ + + +</div> + +<div class="section"> + +Boot it! {#boot} +-------- + +You should see something like this: + + + +Now [install GNU+Linux](../gnulinux/). + +</div> + +<div class="section"> + +X200S and X200 Tablet users: GPIO33 trick will not work. {#gpio33} +-------------------------------------------------------- + +sgsit found out about a pin called GPIO33, which can be grounded to +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):\ + + +By default we would see this in lenovobios, when trying flashrom -p +internal -w rom.rom: + + FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only. + FREG2: Warning: Management Engine region (0x00001000-0x005f5fff) is locked. + +With GPIO33 grounded during boot, this disabled the flash protections as +set by descriptor, and stopped the ME from starting. The output changed +to: + + The Flash Descriptor Override Strap-Pin is set. Restrictions implied by + the Master Section of the flash descriptor are NOT in effect. Please note + that Protected Range (PR) restrictions still apply. + +The part in bold is what got us. This was still observed: + + PR0: Warning: 0x007e0000-0x01ffffff is read-only. + PR4: Warning: 0x005f8000-0x005fffff is locked. + +It is actually possible to disable these protections. Lenovobios does, +when updating the BIOS (proprietary one). One possible way to go about +this would be to debug the BIOS update utility from Lenovo, to find out +how it\'s disabling these protections. Some more research is available +here: +<http://www.coreboot.org/Board:lenovo/x200/internal_flashing_research> + +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) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/x60_unbrick.html b/docs/install/x60_unbrick.html deleted file mode 100644 index 07c048b6..00000000 --- a/docs/install/x60_unbrick.html +++ /dev/null @@ -1,314 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad X60: Recovery guide</title> -</head> - -<body> - - <div class="section"> - <h1>ThinkPad X60: Recovery guide</h1> - <p>This section documents how to recover from a bad flash that prevents your ThinkPad X60 from booting.</p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - <h1>Table of Contents</h1> - <ul> - <li> - Types of brick: - <ul> - <li><a href="#bucts_brick">Brick type 1: bucts not reset</a></li> - <li><a href="#recovery">Brick type 2: bad rom (or user error), system won't boot</a></li> - </ul> - </li> - </ul> - </div> - - <div class="section"> - <h1 id="bucts_brick">Brick type 1: bucts not reset.</h1> - <p> - 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.<br/><br/> - - 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:<br/> - <img src="../images/x60_unbrick/0004.jpg" alt="" /><br/><br/> - - *Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this applied!):<br/> - dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k<br/> - dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump<br/> - dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc<br/> - (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, - using those instructions: <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>. - </p> - </div> - - <div class="section"> - - <h1 id="recovery">bad rom (or user error), system won't boot</h1> - <p> - In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your system from - booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your system is bricked and will not boot at all. - </p> - <p> - "Unbricking" means flashing a known-good (working) ROM. The problem: 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). - </p> - <p> - Remove those screws:<br/> - <img src="../images/x60_unbrick/0000.jpg" alt="" /> - </p> - <p> - Push the keyboard forward (carefully):<br/> - <img src="../images/x60_unbrick/0001.jpg" alt="" /> - </p> - <p> - Lift the keyboard up and disconnect it from the board:<br/> - <img src="../images/x60_unbrick/0002.jpg" alt="" /> - </p> - <p> - Grab the right-hand side of the chassis and force it off (gently) and pry up the rest of the chassis:<br/> - <img src="../images/x60_unbrick/0003.jpg" alt="" /> - </p> - <p> - You should now have this:<br/> - <img src="../images/x60_unbrick/0004.jpg" alt="" /> - </p> - <p> - Disconnect the wifi antenna cables, the modem cable and the speaker:<br/> - <img src="../images/x60_unbrick/0005.jpg" alt="" /> - </p> - <p> - 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:<br/> - <img src="../images/x60_unbrick/0006.jpg" alt="" /> - </p> - <p> - Disconnect the monitor from the motherboard, and unroute the grey antenna cable, carefully lifting the tape - that holds it into place:<br/> - <img src="../images/x60_unbrick/0008.jpg" alt="" /> - </p> - <p> - Carefully lift the remaining tape and unroute the left antenna cable so that it is loose:<br/> - <img src="../images/x60_unbrick/0009.jpg" alt="" /> - </p> - <p> - Remove the screw that is highlighted (do NOT remove the other one; it holds part of the heatsink (other side) into place):<br/> - <img src="../images/x60_unbrick/0011.jpg" alt="" /> - </p> - <p> - Remove those screws:<br/> - <img src="../images/x60_unbrick/0012.jpg" alt="" /> - </p> - <p> - Carefully remove the plate, like so:<br/> - <img src="../images/x60_unbrick/0013.jpg" alt="" /> - </p> - <p> - Remove the SATA connector:<br/> - <img src="../images/x60_unbrick/0014.jpg" alt="" /> - </p> - <p> - Now remove the motherboard (gently) and cast the lcd/chassis aside:<br/> - <img src="../images/x60_unbrick/0015.jpg" alt="" /> - </p> - <p> - Lift back that tape and hold it with something. Highlighted is the SPI flash chip:<br/> - <img src="../images/x60_unbrick/0016.jpg" alt="" /> - </p> - <p> - Now wire up the BBB and the Pomona with your PSU.<br/> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to setup - the BBB for flashing.<br/> - <b>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)</b> - <img src="../images/x60_unbrick/0017.jpg" alt="" /><br/> - Correlate the following with the BBB guide linked above: - </p> -<pre> -POMONA 5250: -=== golden finger and wifi switch ==== - 18 - - 1 - 22 - - NC ---------- audio jacks are on this end - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== CPU fan === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> -</pre> - - <p> - Connecting the BBB and pomona (in this image, an external 3.3v DC PSU was used):<br/> - <img src="images/x60/th_bbb_flashing.jpg" alt="" /> - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - - <p> - SSH'd into the BBB:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom</b> - </p> - <p> - It should be <b>Verifying flash... VERIFIED</b> at the end. If flashrom complains about multiple flash chip - definitions detected, then choose one of them following the instructions in the output. - </p> - - <p> - Remove the programmer and put it away somewhere. Put back the tape and press firmly over it:<br/> - <img src="../images/x60_unbrick/0026.jpg" alt="" /> - </p> - <p> - Your empty chassis:<br/> - <img src="../images/x60_unbrick/0027.jpg" alt="" /> - </p> - <p> - Put the motherboard back in:<br/> - <img src="../images/x60_unbrick/0028.jpg" alt="" /> - </p> - <p> - Reconnect SATA:<br/> - <img src="../images/x60_unbrick/0029.jpg" alt="" /> - </p> - <p> - Put the plate back and re-insert those screws:<br/> - <img src="../images/x60_unbrick/0030.jpg" alt="" /> - </p> - <p> - Re-route that antenna cable around the fan and apply the tape:<br/> - <img src="../images/x60_unbrick/0031.jpg" alt="" /> - </p> - <p> - 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:<br/> - <img src="../images/x60_unbrick/0032.jpg" alt="" /> - </p> - <p> - Re-insert that screw:<br/> - <img src="../images/x60_unbrick/0033.jpg" alt="" /> - </p> - <p> - Route the black antenna cable like so:<br/> - <img src="../images/x60_unbrick/0034.jpg" alt="" /> - </p> - <p> - Tuck it in neatly like so:<br/> - <img src="../images/x60_unbrick/0035.jpg" alt="" /> - </p> - <p> - Route the modem cable like so:<br/> - <img src="../images/x60_unbrick/0036.jpg" alt="" /> - </p> - <p> - Connect modem cable to board and tuck it in neatly like so:<br/> - <img src="../images/x60_unbrick/0037.jpg" alt="" /> - </p> - <p> - Route the power connection and connect it to the board like so:<br/> - <img src="../images/x60_unbrick/0038.jpg" alt="" /> - </p> - <p> - Route the antenna and modem cables neatly like so:<br/> - <img src="../images/x60_unbrick/0039.jpg" alt="" /> - </p> - <p> - 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):<br/> - <img src="../images/x60_unbrick/0040.jpg" alt="" /> - </p> - <p> - Connect the modem cable:<br/> - <img src="../images/x60_unbrick/0041.jpg" alt="" /> - </p> - <p> - Connect the speaker:<br/> - <img src="../images/x60_unbrick/0042.jpg" alt="" /> - </p> - <p> - You should now have this:<br/> - <img src="../images/x60_unbrick/0043.jpg" alt="" /> - </p> - <p> - Re-connect the upper chassis:<br/> - <img src="../images/x60_unbrick/0044.jpg" alt="" /> - </p> - <p> - Re-connect the keyboard:<br/> - <img src="../images/x60_unbrick/0045.jpg" alt="" /> - </p> - <p> - Re-insert the screws that you removed earlier:<br/> - <img src="../images/x60_unbrick/0046.jpg" alt="" /> - </p> - <p> - Power on!<br/> - <img src="../images/x60_unbrick/0047.jpg" alt="" /> - </p> - <p> - Operating system:<br/> - <img src="../images/x60_unbrick/0049.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md new file mode 100644 index 00000000..a38f862b --- /dev/null +++ b/docs/install/x60_unbrick.md @@ -0,0 +1,271 @@ +<div class="section"> + +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](./) + +</div> + +<div class="section"> + +Table of Contents +================= + +- Types of brick: + - [Brick type 1: bucts not reset](#bucts_brick) + - [Brick type 2: bad rom (or user error), system won\'t + boot](#recovery) + +</div> + +<div class="section"> + +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.\ +\ +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:\ +\ +\ +\*Those dd commands should be applied to all newly compiled X60 ROM +images (the ROM images in libreboot binary archives already have this +applied!):\ +dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s +coreboot.rom) - 0x10000\] count=64k\ +dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] +count=64k | hexdump\ +dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s +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>. + +</div> + +<div class="section"> + +bad rom (or user error), system won\'t boot {#recovery} +=========================================== + +In this scenario, you compiled a ROM that had an incorrect +configuration, or there is an actual bug preventing your system from +booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash +while Lenovo BIOS was running. In any case, your system is bricked and +will not boot at all. + +\"Unbricking\" means flashing a known-good (working) ROM. The problem: +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:\ + + +Push the keyboard forward (carefully):\ + + +Lift the keyboard up and disconnect it from the board:\ + + +Grab the right-hand side of the chassis and force it off (gently) and +pry up the rest of the chassis:\ + + +You should now have this:\ + + +Disconnect the wifi antenna cables, the modem cable and the speaker:\ + + +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:\ + + +Disconnect the monitor from the motherboard, and unroute the grey +antenna cable, carefully lifting the tape that holds it into place:\ + + +Carefully lift the remaining tape and unroute the left antenna cable so +that it is loose:\ + + +Remove the screw that is highlighted (do NOT remove the other one; it +holds part of the heatsink (other side) into place):\ + + +Remove those screws:\ + + +Carefully remove the plate, like so:\ + + +Remove the SATA connector:\ + + +Now remove the motherboard (gently) and cast the lcd/chassis aside:\ + + +Lift back that tape and hold it with something. Highlighted is the SPI +flash chip:\ + + +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.\ +**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)** +\ +Correlate the following with the BBB guide linked above: + + POMONA 5250: + === golden finger and wifi switch ==== + 18 - - 1 + 22 - - NC ---------- audio jacks are on this end + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === CPU fan === + 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):\ + + +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 +yourrom.rom** + +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:\ + + +Your empty chassis:\ + + +Put the motherboard back in:\ + + +Reconnect SATA:\ + + +Put the plate back and re-insert those screws:\ + + +Re-route that antenna cable around the fan and apply the tape:\ + + +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:\ + + +Re-insert that screw:\ + + +Route the black antenna cable like so:\ + + +Tuck it in neatly like so:\ + + +Route the modem cable like so:\ + + +Connect modem cable to board and tuck it in neatly like so:\ + + +Route the power connection and connect it to the board like so:\ + + +Route the antenna and modem cables neatly like so:\ + + +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):\ + + +Connect the modem cable:\ + + +Connect the speaker:\ + + +You should now have this:\ + + +Re-connect the upper chassis:\ + + +Re-connect the keyboard:\ + + +Re-insert the screws that you removed earlier:\ + + +Power on!\ + + +Operating system:\ + + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/install/x60tablet_unbrick.html b/docs/install/x60tablet_unbrick.html deleted file mode 100644 index ecc59a9e..00000000 --- a/docs/install/x60tablet_unbrick.html +++ /dev/null @@ -1,215 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad X60 Tablet: Recovery guide</title> -</head> - -<body> - - <div class="section"> - <h1>ThinkPad X60 Tablet: Recovery guide</h1> - <p>This section documents how to recover from a bad flash that prevents your ThinkPad X60 Tablet from booting.</p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - <h2>Table of Contents</h2> - <ul> - <li> - Types of brick: - <ul> - <li><a href="#bucts_brick">Brick type 1: bucts not reset</a></li> - <li><a href="#recovery">Brick type 2: bad rom (or user error), system won't boot</a></li> - </ul> - </li> - </ul> - </div> - - <div class="section"> - <h1 id="bucts_brick">Brick type 1: bucts not reset.</h1> - <p> - 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.<br/><br/> - - 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:<br/> - <img src="../images/x60t_unbrick/0008.JPG" alt="" /><br/><br/> - - *Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this applied!):<br/> - dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k<br/> - dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump<br/> - dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc<br/> - (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, - using those instructions: <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>. - </p> - </div> - - <div class="section"> - - <h1 id="recovery">bad rom (or user error), system won't boot</h1> - <p> - In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your system from - booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your system is bricked and will not boot at all. - </p> - <p> - "Unbricking" means flashing a known-good (working) ROM. The problem: 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). - </p> - - <p> - <img src="../images/x60t_unbrick/0000.JPG" alt="" /> - </p> - - <p> - Remove those screws:<br/> - <img src="../images/x60t_unbrick/0001.JPG" alt="" /> - </p> - - <p> - Remove the HDD:<br/> - <img src="../images/x60t_unbrick/0002.JPG" alt="" /> - </p> - - <p> - Push keyboard forward to loosen it:<br/> - <img src="../images/x60t_unbrick/0003.JPG" alt="" /> - </p> - - <p> - Lift:<br/> - <img src="../images/x60t_unbrick/0004.JPG" alt="" /> - </p> - - <p> - Remove those:<br/> - <img src="../images/x60t_unbrick/0005.JPG" alt="" /> - </p> - - <p> - - <img src="../images/x60t_unbrick/0006.JPG" alt="" /> - </p> - - <p> - Also remove that (marked) and unroute the antenna cables:<br/> - <img src="../images/x60t_unbrick/0007.JPG" alt="" /> - </p> - - <p> - For some X60T laptops, you have to unroute those too:<br/> - <img src="../images/x60t_unbrick/0010.JPG" alt="" /> - </p> - - <p> - Remove the LCD extend board screws. Also remove those screws (see blue marks) and remove/unroute the cables and remove the metal plate:<br/> - <img src="../images/x60t_unbrick/0008.JPG" alt="" /> - </p> - - <p> - Remove that screw and then remove the board:<br/> - <img src="../images/x60t_unbrick/0009.JPG" alt="" /> - </p> - - <p> - Now wire up the BBB and the Pomona with your PSU.<br/> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to setup - the BBB for flashing.<br/> - <b>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)</b> - <img src="../images/x60t_unbrick/0011.JPG" alt="" /><br/> - Correlate the following with the BBB guide linked above: - </p> -<pre> -POMONA 5250: -=== golden finger and wifi switch ==== - 18 - - 1 - 22 - - NC ---------- audio jacks are on this end - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== CPU fan === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> -</pre> - - <p> - Connecting the BBB and pomona (in this image, an external 3.3v DC PSU was used):<br/> - <img src="images/x60/th_bbb_flashing.jpg" alt="" /> - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - - <p> - SSH'd into the BBB:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom</b> - </p> - <p> - It should be <b>Verifying flash... VERIFIED</b> at the end. If flashrom complains about multiple flash chip - definitions detected, then choose one of them following the instructions in the output. - </p> - - <p> - Reverse the steps to re-assemble your system. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md new file mode 100644 index 00000000..5d8bea51 --- /dev/null +++ b/docs/install/x60tablet_unbrick.md @@ -0,0 +1,178 @@ +<div class="section"> + +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](./) + +</div> + +<div class="section"> + +Table of Contents +----------------- + +- Types of brick: + - [Brick type 1: bucts not reset](#bucts_brick) + - [Brick type 2: bad rom (or user error), system won\'t + boot](#recovery) + +</div> + +<div class="section"> + +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.\ +\ +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:\ +\ +\ +\*Those dd commands should be applied to all newly compiled X60 ROM +images (the ROM images in libreboot binary archives already have this +applied!):\ +dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s +coreboot.rom) - 0x10000\] count=64k\ +dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] +count=64k | hexdump\ +dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s +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>. + +</div> + +<div class="section"> + +bad rom (or user error), system won\'t boot {#recovery} +=========================================== + +In this scenario, you compiled a ROM that had an incorrect +configuration, or there is an actual bug preventing your system from +booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash +while Lenovo BIOS was running. In any case, your system is bricked and +will not boot at all. + +\"Unbricking\" means flashing a known-good (working) ROM. The problem: +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 the HDD:\ + + +Push keyboard forward to loosen it:\ + + +Lift:\ + + +Remove those:\ + + + + +Also remove that (marked) and unroute the antenna cables:\ + + +For some X60T laptops, you have to unroute those too:\ + + +Remove the LCD extend board screws. Also remove those screws (see blue +marks) and remove/unroute the cables and remove the metal plate:\ + + +Remove that screw and then remove the board:\ + + +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.\ +**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)** +\ +Correlate the following with the BBB guide linked above: + + POMONA 5250: + === golden finger and wifi switch ==== + 18 - - 1 + 22 - - NC ---------- audio jacks are on this end + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === CPU fan === + 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):\ + + +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 +yourrom.rom** + +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. + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/misc/bbb_ehci.html b/docs/misc/bbb_ehci.html deleted file mode 100644 index e79cf0ac..00000000 --- a/docs/misc/bbb_ehci.html +++ /dev/null @@ -1,523 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>EHCI debugging on the BeagleBone Black</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">EHCI debugging on the BeagleBone Black</h1> - - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - <h1>EHCI debugging</h1> - <ol class="toc"> - <li><a href="#FindUSBportonthetargetthatsupportsEHCIdebug">Find - USB port on the target that supports EHCI debug</a></li> - <li><a href="#InitialsetupofBBBtoactasEHCIdebugdongle">Initial - setup of BBB to act as EHCI debug dongle</a></li> - <li><a href="#PatchBBBsgdbgpmoduleoptionalbuthighlyrecommended">Patch - BBB's <tt>g_dbgp</tt> module (optional, but highly recommended)</a></li> - <li><a href="#ConfigurelibrebootwithEHCIdebug">Configure - libreboot with EHCI debug</a> - <ol> - <li><a href="#SelectingHCDIndexandUSBDebugport">Selecting - <tt>HCD Index</tt> and <tt>USB Debug port</tt></a></li> - </ol></li> - <li><a href="#Howtogetthedebuglogs">How to get the debug - logs</a></li> - <li><a - href="#EnebleEHCIDebugonthetargetskerneloptionalrecommended">Eneble - EHCI Debug on the target's kernel (optional, recommended)</a></li> - <li><a href="#References">References</a></li> - </ol> - <p> - <strong> - NOTE: this documentation may be outdated, and discusses - configuring EHCI debug on the default Debian system that the BBB - sometimes comes with. If you want an easier time, just use - <a href="https://www.coreboot.org/BBB_screwdriver">BBB ScrewDriver</a> - which comes pre-configured. - </strong> - </p> - <p>If your computer does not boot after installing libreboot, it is - very useful to get debug logs from it, from the payload (grub) and/or - the kernel (if gets to there). All of them stream debug logs on the - available serial (RS-232) by default. However, most of todays laptops - lack RS-232 port. The other option is to stream the logs to USB EHCI - debug port.</p> - <p>This section explains step-by-step how to setup BBB as a - “USB EHCI debug dongle” and configure libreboot and the - linux kernel to stream logs to it (TODO: grub).</p> - <p>I will refer to three computers:</p> - <ul> - <li><b>host</b> - this is the computer you use, have - tools, compiler, Internet, etc</li> - <li><b>BBB</b> - Beaglebone Black (rev. B or higher, i - use rev. C)</li> - <li><b>target</b> - the computer you are trying to - install liberboot</li> - </ul> - <h3 id="FindUSBportonthetargetthatsupportsEHCIdebug">Find USB port - on the target that supports EHCI debug</h3> - <p> - Not all USB controllers support EHCI debug (see: <a - href="http://www.coreboot.org/EHCI_Debug_Port#Hardware_capability">EHCI - Debug Port</a> ). Even more, if a USB controller supports EHCI debug, it - is available only <b>on a single port</b> that might or might - not be exposed externally. - </p> - <ul> - <li>You need running OS (GNU+Linux) on your target for this step - (If you’ve flashed libreboot and it does not boot, you have to - flush back the stock bios)</li> - <li>You need USB memory stick (the data on it will not be - touched).</li> - <li>The EHCI debugging can not be done through external hub, BBB - must be connected directly to the debug port of the controller (so, no - hubs)</li> - </ul> - <ul> - <li>Download<sup class="footnote"><a href="#___fn1">1</a></sup> <a - href="http://www.coreboot.org/pipermail/coreboot/attachments/20080909/ae11c291/attachment.sh">this</a> - shell script. - </li> - </ul> - <ol> - <li>Plug the usb stick in the first available usb port</li> - <li>Run the script, you will get output similar to following:</li> -<pre>The following PCI devices support a USB debug port (says lspci): 0000:00:1a.0 0000:00:1d.0 -The following PCI devices support a USB debug port (says the kernel): 0000:00:1a.0 0000:00:1d.0 -*PCI device 0000:00:1a.0, USB bus 3, USB physical port 1* -*PCI device 0000:00:1d.0, USB bus 4, USB physical port 2* -Currently connected high-speed devices: -/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M - |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M - |__ Port 7: Dev 14, If 0, Class=Hub, Driver=hub/4p, 480M - |__ Port 1: Dev 15, If 0, Class=Hub, Driver=hub/4p, 480M - |__ Port 3: Dev 17, If 0, Class=Hub, Driver=hub/2p, 480M - |__ Port 4: Dev 18, If 0, Class=Hub, Driver=hub/4p, 480M -/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M - |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M -/: *Bus 01*.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M - |__ *Port 3: Dev 31, If 0, Class=Mass Storage, Driver=usb-storage, 480M* -</pre> - <li>The buses the support debug are Bus 3 (0000:00:1a.0) on Port 1 - and Bus 4 (0000:00:1d.0) on port 2. Your usb stick is plugged on Bus - 1, Port 3</li> - <li>Repeat the steps, plugging the USB stick in the next available - port</li> - <li>Go through all available ports and remember(write down) those - for which bus/port of the usb stick matches one of the bus/port that - support debug (bold).</li> - </ol> - <p>Remember (write down) for each port (external plug) you found - that supports debug: <b>PCI device id, the bus id, the port number, and - the physical location of the usb plug.</b></p> - <p>If you do not find a match, you can not get debug over EHCI. - Sorry.</p> - <p id="___fn1" class="footnote"> - <sup>1</sup> The guys from coreboot were talking about including the - script in coreboot distribution (check the status). - </p> - <h3 id="InitialsetupofBBBtoactasEHCIdebugdongle">Initial setup of - BBB to act as EHCI debug dongle</h3> - <p>BBB must be powered with a barrel power connector since the - mini-B USB plug will be used for the EHCI debug stream. So you will - need:</p> - <ul> - <li>power supply (5V, 2A(10W) is sufficient).</li> - <li>an extra usb cable: A to mini-B</li> - </ul> - <p> - (On BBB) The linux kernel includes module (g_dbgp that enables one of the usb ports on a computer to behave as EHCI - debug dongle. Make sure you have this module available on your BBB - (Debian 7.8 that comes with BBB should have it), if not, you should - compile it yourself (see next section): - </p> -<pre>ls /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget/g_dbgp.ko</pre> - <p> - Unload all other - g_* - modules: - </p> -<pre># lsmod -# rmmod g_multi -... -</pre> - <p> - Then load - g_dbgp - : - </p> -<pre># modprobe g_dbgp -# lsmod # should show that g_dbgp is loaded, and no other g_* -</pre> - <p> - Plug the mini-B side of the USB cable in your BBB and the A side in - your target. Then one of the usb devices on your target (with - lsusb - ) should be: - </p> -<pre>Bus 001 Device 024: ID 0525:c0de Netchip Technology, Inc.</pre> - <p>If you see the device on the target, you are good to continue to - the next step.</p> - <h3 id="PatchBBBsgdbgpmoduleoptionalbuthighlyrecommended"> - Patch BBB’s - g_dbgp - module (optional, but highly recommended) - </h3> - <p> - For the reasons why you need this, see: <a - href="http://www.coreboot.org/EHCI_Gadget_Debug">EHCI Gadget Debug</a>.<br />Make - sure that you have cross compiling environment for - arm-linux-gnueabihf - setup on your <em>host</em>. - </p> - <ul> - <li>On BBB: uname -r - this will give you version - number like 3.8.13-bone70 (I will refer to this as: $mav.$miv-$lv: - where mav=3.8, miv=13, lv=bone70 - </li> - <li>Get the BBB kernel ready on your host for cross-compiling:</li> - </ul> -<pre>$ cd $work_dir -$ git clone https://github.com/beagleboard/kernel.git -$ cd kernel -$ 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 -</pre> - <ul> - <li>Download the patch from <a - href="http://www.coreboot.org/images/8/88/Ehci-debug-gadget-patches.tar.gz">here</a></li> - <li>tar -xf Ehci-debug-gadget-patches.tar.gz (will - create dir: usbdebug-gadget)</li> - <li>Note that there are two patches (patch_1 and patch_2) for each - of 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)</li> - <li>cd kernel (note that this is one more level: you - should be in $work_dir/kernel/kernel)</li> - <li>Apply the patches:</li> - </ul> -<pre> -git apply ../usbdebug-gadget/v3.8-debug-gadget/0001-usb-dbgp-gadget-Fix-re-connecting-after-USB-disconne.patch -git apply ../usbdebug-gadget/v3.8-debug-gadget/0002-usb-serial-gadget-no-TTY-hangup-on-USB-disconnect-WI.patch -; -make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- beaglebone_defconfig -j4@ -</pre> - <ul> - <li> - You should also apply the linux-libre <i>deblob</i> script to turn it into linux-libre - (deletes all the blobs from the linux kernel). - <a href="http://www.fsfla.org/ikiwiki/selibre/linux-libre/">fsfla website</a> - - see <a href="http://www.fsfla.org/svn/fsfla/software/linux-libre/scripts/">scripts</a>. - </li> - <li>Get your current BBB kernel config (from: /boot/config-<ver>) - and copy it to your host as $work_dir/kernel/kernel/.config</li> -<pre> -make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- oldconfig - all default answers</pre> - <li>Set proper version number: - <ul> - <li>On your host, edit $work_dir/kernel/kernel/.config - (the one you’ve just copied from BBB), find the line CONFIG_LOCALVERSION="<something - or empty>" and change it to CONFIG_LOCALVERSION="-$lv", - so it will look something like: CONFIG_LOCALVERSION="-bone70"</li> - </ul> - </li> - <li>Also, make sure that: CONFIG_USB_G_DBGP=m (If - not, make menuconfig, and set @Device Drivers-> USB - Support -> USB Gadget Support -> EHCI Debug Device Gadget=m</li> - <li>Build the module:</li> - </ul> -<pre> -$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 (is it possoble to build only the gadget modules) -$ mkdir ../tmp && make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=../tmp modules_install -</pre> - <ul> - <li>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) - </li> - <li>copy the freshly compiled usb/gadget dir to /lib/modules/3.8.13-bone70/kernel/drivers/usb</li> - <li>restart BBB</li> - <li>Remove all g_* modules (rmmod - g_<>) - </li> - <li>modprobpe g_dbgp</li> - </ul> - <h3 id="ConfigurelibrebootwithEHCIdebug">Configure libreboot with - EHCI debug</h3> - <p> - Libreboot(coreboot) should be configured with debug turned on and to - push debug messages to the EHCI debug port.<br />If you’ve - downloaded the binary distribution, you can check if it is properly - configured in the following way: - </p> - <ul> - <li>Go to the libreboot dist root directory cd - $libreboot_bin</li> - <li>Locate the rom image for your target (I will call it: $img_path) - </li> - <li>Running the following command will extract the config in a - file ./my_config: - </li> - </ul> -<pre> -./cbfstool/i686/cbfstool $img_path extract -n config -f ./my_config -</pre> - <ul> - <li>Make sure that the following params in the config are set as - following:</li> - </ul> -<pre> -CONFIG_USBDEBUG=y (Generic Drivers -> USB 2.0 EHCI debug dongle support) -CONFIG_USBDEBUG_IN_ROMSTAGE=y (Generic Drivers -> Enable early (pre-RAM) usbdebug) -CONFIG_USBDEBUG_HCD_INDEX=<HCD Index of usb controller - see below> (Generic Drivers -> Index for EHCI controller to use with usbdebug) -CONFIG_USBDEBUG_DEFAULT_PORT=<USB Debug port - see below> (Generic Drivers -> Default USB port to use as Debug Port) -</pre> - <p> - The following three are behind radio button in the menu. Only the first - one<sup class="footnote"><a href="#___fn2">2</a></sup> should be = y - </p> -<pre> -USBDEBUG_DONGLE_STD=y (Generic Drivers -> Type of dongle (Net20DC or compatible) -> Net20DC or compatible) -CONFIG_USBDEBUG_DONGLE_BEAGLEBONE=n (Generic Drivers -> Type of dongle (Net20DC or compatible) -> BeagleBone) -CONFIG_USBDEBUG_DONGLE_BEAGLEBONE_BLACK=n (Generic Drivers -> Type of dongle (Net20DC or compatible) -> BeagleBone Black) -</pre> - <p id="___fn2" class="footnote"> - <sup>2</sup> The g_dbgp module on BeagleBone Black (Rev. C) reports it self as Net20DC, the - other options are for older BB(B) - ver1. This is documented <a - href="https://johnlewis.ie/coreboot-ehci-debug-gadget-demonstration/">here</a> - (also tested/verified). - </p> - <p> - Then:<br /> -<pre> -CONFIG_CONSOLE_USB=y (Console -> USB dongle console output) -</pre> - </p> - <p> - Also - Debugging ---> Output verbose XYZ - ) (<b>FIXME</b> somebody verify these): - </p> -<pre> -CONFIG_DEBUG_CBFS=y (Output verbose CBFS debug messages ) -CONFIG_HAVE_DEBUG_RAM_SETUP=y (??? What/where is this) -CONFIG_DEBUG_RAM_SETUP=y (Output verbose RAM init debug messages) -CONFIG_DEBUG_SMI=y (Output verbose SMI debug messages) -CONFIG_DEBUG_ACPI=y (Output verbose ACPI debug messages ) -CONFIG_DEBUG_USBDEBUG=y (Output verbose USB 2.0 EHCI debug dongle messages) -</pre> - <p>If some of the above mentioned configuration options are not as - specified, you have to configure and compile libreboot yourself. Please - refer to the doc(<b>FIXME: link</b> about compiling libreboot.</p> - <h4 id="SelectingHCDIndexandUSBDebugport"> - Selecting - HCD Index - and - USB Debug port - </h4> - <p> - This applies (and works) only if the USB controller that supports debug - (found in the first section) is from Intel.<br />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. - </p> - <p> - If the externally exposed port is on a bus with - PCI ID == 0000:00:1a.0 - then for - CONFIG_USBDEBUG_HCD_INDEX - choose 2, otherwise choose 0 - . - </p> - <p> - For - CONFIG_USBDEBUG_DEFAULT_PORT - choose the port from the first section that correspond to the - PCI ID - </p> - <p> - Notes:<br />The above is based on the implementation of - coreboot/src/southbridge/intel/common/usb_debug.c : pci_ehci_dbg_dev() - .<br />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). - </p> - <ul> - <li>On T500 (with switchable GPU) the debug ports for both intel - controllers is exposed.</li> - <li>On x200t the debug ports for both intel controllers is - exposed.</li> - </ul> - <h3 id="Howtogetthedebuglogs">How to get the debug logs</h3> - <ul> - <li>Plug the USB cable in the target’s debug port (the one - you found in step 1) and BBB’s mini-B USB</li> - <li>Make sure no other then g_dbgp of the g_* - modules is loaded on your BBB - </li> - <li>On the BBB:</li> - </ul> -<pre> -stty -icrnl -inlcr -F /dev/ttyGS0 -cat /dev/ttyGS0 -</pre> - <ul> - <li>Power on the target with libreboot</li> - <li>You should see debug logs comming on your BBB console</li> - </ul> - <p> - Note that this is not permanent on BBB, if you reboot it, you have to - rmmod g_* - and - modprobe g_dbgp - </p> - <h3 id="EnebleEHCIDebugonthetargetskerneloptionalrecommended">Eneble - EHCI Debug on the target’s kernel (optional, recommended)</h3> - <p>You have to know how to compile kernel for your target.</p> - <ol> - <li>Check if early debugging is already enabled: grep - CONFIG_EARLY_PRINTK_DBGP /boot/config-<ver></li> - <li>If enabled, you do not have to compile the kernel (skip this - step). Otherwise, prepare kernel source for your distribution and - select (Kernel hacking -> Early printk via EHCI debug - port). Compile and install the new kernel. - </li> - <li>Edit your grub configuration and add following to the kenel - parameters<sup class="footnote"><a href="#___fn20">20</a></sup><sup - class="footnote"><a href="#___fn21">21</a></sup>: earlyprintk=dbgp,keep. - Also, try: earlyprintk=dbgp<N>,keep where N - is the debug port id if the first does not work. - </li> - </ol> - <h3 id="References">References</h3> - <p id="___fn10" class="footnote"> - <sup>10</sup> <a href="http://www.coreboot.org/EHCI_Debug_Port">EHCI - Debug Port</a> - </p> - <p id="___fn11" class="footnote"> - <sup>11</sup> <a - href="https://johnlewis.ie/coreboot-ehci-debug-gadget-demonstration/">coreboot - EHCI debug gadget demonstration</a> - </p> - <p id="___fn12" class="footnote"> - <sup>12</sup> <a href="http://www.coreboot.org/EHCI_Gadget_Debug">EHCI - Gadget Debug</a> - </p> - <p id="___fn13" class="footnote"> - <sup>13</sup> <a - href="http://www.coreboot.org/images/8/88/Ehci-debug-gadget-patches.tar.gz">Ehci-debug-gadget-patches.tar.gz</a> - </p> - <p id="___fn14" class="footnote"> - <sup>14</sup> <a - href="http://wiki.beyondlogic.org/index.php/BeagleBoneBlack_Building_Kernel">Compiling - the BeagleBone Black Kernel</a> - </p> - <p id="___fn15" class="footnote"> - <sup>15</sup> - http://dumb-looks-free.blogspot.ca/2014/06/beaglebone-black-bbb-compile-kernel.html - </p> - <p id="___fn16" class="footnote"> - <sup>16</sup> - http://dumb-looks-free.blogspot.fr/2014/06/beaglebone-black-bbb-kernal-headers.html - </p> - <p id="___fn17" class="footnote"> - <sup>17</sup> <a href="http://elinux.org/Building_BBB_Kernel">Building - BBB Kernel</a> - </p> - <p id="___fn18" class="footnote"> - <sup>18</sup> - http://komposter.com.ua/documents/USB-2.0-Debug-Port%28John-Keys%29.pdf - </p> - <p id="___fn19" class="footnote"> - <sup>19</sup> <a href="http://cs.usfca.edu/~cruse/cs698s10/">Exploring - USB at the Hardware/Software Interface</a> - </p> - <p id="___fn20" class="footnote"> - <sup>20</sup> - https://www.kernel.org/doc/Documentation/x86/earlyprintk.txt - </p> - <p id="___fn21" class="footnote"> - <sup>21</sup> https://wiki.ubuntu.com/Kernel/Debugging/USBearlyprintk - </p> - <p> - <b>TODO</b>: - </p> - <ol> - <li>grub does not send messages to EHCI debug. Investigate.</li> - <li>The section “Configure libreboot with EHCI debug” - can be skipped/simplified if a common configuration works for all - relevant targets is selected as defualt</li> - <li>Patch and compule g_dbgp on BBB instead cross-compile</li> - <li>Find a simple way to send debug messages from targets userland</li> - </ol> - </div> - - <div class="section"> - - <p> - Copyright © 2015 Alex David <opdecirkel@gmail.com><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/misc/bbb_ehci.md b/docs/misc/bbb_ehci.md new file mode 100644 index 00000000..0cb49278 --- /dev/null +++ b/docs/misc/bbb_ehci.md @@ -0,0 +1,398 @@ +<div class="section"> + +EHCI debugging on the BeagleBone Black {#pagetop} +====================================== + +[Back to previous index](./) + +</div> + +<div class="section"> + +EHCI debugging +============== + +1. [Find USB port on the target that supports EHCI + debug](#FindUSBportonthetargetthatsupportsEHCIdebug) +2. [Initial setup of BBB to act as EHCI debug + dongle](#InitialsetupofBBBtoactasEHCIdebugdongle) +3. [Patch BBB\'s `g_dbgp` module (optional, but highly + recommended)](#PatchBBBsgdbgpmoduleoptionalbuthighlyrecommended) +4. [Configure libreboot with EHCI + debug](#ConfigurelibrebootwithEHCIdebug) + 1. [Selecting `HCD Index` and + `USB Debug port`](#SelectingHCDIndexandUSBDebugport) +5. [How to get the debug logs](#Howtogetthedebuglogs) +6. [Eneble EHCI Debug on the target\'s kernel (optional, + recommended)](#EnebleEHCIDebugonthetargetskerneloptionalrecommended) +7. [References](#References) + +**NOTE: this documentation may be outdated, and discusses configuring +EHCI debug on the default Debian system that the BBB sometimes comes +with. If you want an easier time, just use [BBB +ScrewDriver](https://www.coreboot.org/BBB_screwdriver) which comes +pre-configured.** + +If your computer does not boot after installing libreboot, it is very +useful to get debug logs from it, from the payload (grub) and/or the +kernel (if gets to there). All of them stream debug logs on the +available serial (RS-232) by default. However, most of todays laptops +lack RS-232 port. The other option is to stream the logs to USB EHCI +debug port. + +This section explains step-by-step how to setup BBB as a “USB EHCI debug +dongle” and configure libreboot and the linux kernel to stream logs to +it (TODO: grub). + +I will refer to three computers: + +- **host** - this is the computer you use, have tools, compiler, + Internet, etc +- **BBB** - Beaglebone Black (rev. B or higher, i use rev. C) +- **target** - the computer you are trying to install liberboot + +### Find USB port on the target that supports EHCI debug {#FindUSBportonthetargetthatsupportsEHCIdebug} + +Not all USB controllers support EHCI debug (see: [EHCI Debug +Port](http://www.coreboot.org/EHCI_Debug_Port#Hardware_capability) ). +Even more, if a USB controller supports EHCI debug, it is available only +**on a single port** that might or might not be exposed externally. + +- You need running OS (GNU+Linux) on your target for this step (If + you've flashed libreboot and it does not boot, you have to flush + back the stock bios) +- You need USB memory stick (the data on it will not be touched). +- The EHCI debugging can not be done through external hub, BBB must be + connected directly to the debug port of the controller (so, no hubs) + +<!-- --> + +- Download^[1](#___fn1)^ + [this](http://www.coreboot.org/pipermail/coreboot/attachments/20080909/ae11c291/attachment.sh) + shell script. + +1. Plug the usb stick in the first available usb port +2. Run the script, you will get output similar to following: +3. The buses the support debug are Bus 3 (0000:00:1a.0) on Port 1 and + Bus 4 (0000:00:1d.0) on port 2. Your usb stick is plugged on Bus 1, + Port 3 +4. Repeat the steps, plugging the USB stick in the next available port +5. Go through all available ports and remember(write down) those for + which bus/port of the usb stick matches one of the bus/port that + support debug (bold). + +Remember (write down) for each port (external plug) you found that +supports debug: **PCI device id, the bus id, the port number, and the +physical location of the usb plug.** + +If you do not find a match, you can not get debug over EHCI. Sorry. + +^1^ The guys from coreboot were talking about including the script in +coreboot distribution (check the status). + +### Initial setup of BBB to act as EHCI debug dongle {#InitialsetupofBBBtoactasEHCIdebugdongle} + +BBB must be powered with a barrel power connector since the mini-B USB +plug will be used for the EHCI debug stream. So you will need: + +- power supply (5V, 2A(10W) is sufficient). +- an extra usb cable: A to mini-B + +(On BBB) The linux kernel includes module (g\_dbgp that enables one of +the usb ports on a computer to behave as EHCI debug dongle. Make sure +you have this module available on your BBB (Debian 7.8 that comes with +BBB should have it), if not, you should compile it yourself (see next +section): + + ls /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget/g_dbgp.ko + +Unload all other g\_\* modules: + + # lsmod + # rmmod g_multi + ... + +Then load g\_dbgp : + + # modprobe g_dbgp + # lsmod # should show that g_dbgp is loaded, and no other g_* + +Plug the mini-B side of the USB cable in your BBB and the A side in your +target. Then one of the usb devices on your target (with lsusb ) should +be: + + Bus 001 Device 024: ID 0525:c0de Netchip Technology, Inc. + +If you see the device on the target, you are good to continue to the +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).\ +Make sure that you have cross compiling environment for +arm-linux-gnueabihf setup on your *host*. + +- On BBB: uname -r - this will give you version number like + 3.8.13-bone70 (I will refer to this as: \$mav.\$miv-\$lv: where + mav=3.8, miv=13, lv=bone70 +- Get the BBB kernel ready on your host for cross-compiling: + +<!-- --> + + $ cd $work_dir + $ git clone https://github.com/beagleboard/kernel.git + $ cd kernel + $ 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 + +- Download the patch from + [here](http://www.coreboot.org/images/8/88/Ehci-debug-gadget-patches.tar.gz) +- tar -xf Ehci-debug-gadget-patches.tar.gz (will create dir: + usbdebug-gadget) +- Note that there are two patches (patch\_1 and patch\_2) for each of + 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) +- Apply the patches: + +<!-- --> + + git apply ../usbdebug-gadget/v3.8-debug-gadget/0001-usb-dbgp-gadget-Fix-re-connecting-after-USB-disconne.patch + git apply ../usbdebug-gadget/v3.8-debug-gadget/0002-usb-serial-gadget-no-TTY-hangup-on-USB-disconnect-WI.patch + ; + make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- beaglebone_defconfig -j4@ + +- You should also apply the linux-libre *deblob* script to turn it + into linux-libre (deletes all the blobs from the linux kernel). + [fsfla website](http://www.fsfla.org/ikiwiki/selibre/linux-libre/) - + see + [scripts](http://www.fsfla.org/svn/fsfla/software/linux-libre/scripts/). +- Get your current BBB kernel config (from: /boot/config-<ver>) + and copy it to your host as \$work\_dir/kernel/kernel/.config +- Set proper version number: + - On your host, edit \$work\_dir/kernel/kernel/.config (the one + you've just copied from BBB), find the line + CONFIG\_LOCALVERSION=\"<something or empty>\" and change + it to CONFIG\_LOCALVERSION=\"-\$lv\", so it will look something + like: CONFIG\_LOCALVERSION=\"-bone70\" +- Also, make sure that: CONFIG\_USB\_G\_DBGP=m (If not, make + menuconfig, and set @Device Drivers-> USB Support -> USB + Gadget Support -> EHCI Debug Device Gadget=m +- Build the module: + +<!-- --> + + $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 (is it possoble to build only the gadget modules) + $ mkdir ../tmp && make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=../tmp modules_install + +- 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) +- 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\_<>) +- 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.\ +If you've downloaded the binary distribution, you can check if it is +properly configured in the following way: + +- Go to the libreboot dist root directory cd \$libreboot\_bin +- Locate the rom image for your target (I will call it: \$img\_path) +- Running the following command will extract the config in a file + ./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: + +<!-- --> + + CONFIG_USBDEBUG=y (Generic Drivers -> USB 2.0 EHCI debug dongle support) + CONFIG_USBDEBUG_IN_ROMSTAGE=y (Generic Drivers -> Enable early (pre-RAM) usbdebug) + CONFIG_USBDEBUG_HCD_INDEX=<HCD Index of usb controller - see below> (Generic Drivers -> Index for EHCI controller to use with usbdebug) + CONFIG_USBDEBUG_DEFAULT_PORT=<USB Debug port - see below> (Generic Drivers -> Default USB port to use as Debug Port) + +The following three are behind radio button in the menu. Only the first +one^[2](#___fn2)^ should be = y + + USBDEBUG_DONGLE_STD=y (Generic Drivers -> Type of dongle (Net20DC or compatible) -> Net20DC or compatible) + CONFIG_USBDEBUG_DONGLE_BEAGLEBONE=n (Generic Drivers -> Type of dongle (Net20DC or compatible) -> BeagleBone) + CONFIG_USBDEBUG_DONGLE_BEAGLEBONE_BLACK=n (Generic Drivers -> Type of dongle (Net20DC or compatible) -> BeagleBone Black) + +^2^ The g\_dbgp module on BeagleBone Black (Rev. C) reports it self as +Net20DC, the other options are for older BB(B) - ver1. This is +documented +[here](https://johnlewis.ie/coreboot-ehci-debug-gadget-demonstration/) +(also tested/verified). + +Then:\ + + CONFIG_CONSOLE_USB=y (Console -> USB dongle console output) + +Also Debugging \-\--> Output verbose XYZ ) (**FIXME** somebody verify +these): + + CONFIG_DEBUG_CBFS=y (Output verbose CBFS debug messages ) + CONFIG_HAVE_DEBUG_RAM_SETUP=y (??? What/where is this) + CONFIG_DEBUG_RAM_SETUP=y (Output verbose RAM init debug messages) + CONFIG_DEBUG_SMI=y (Output verbose SMI debug messages) + CONFIG_DEBUG_ACPI=y (Output verbose ACPI debug messages ) + CONFIG_DEBUG_USBDEBUG=y (Output verbose USB 2.0 EHCI debug dongle messages) + +If some of the above mentioned configuration options are not as +specified, you have to configure and compile libreboot yourself. Please +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.\ +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. + +If the externally exposed port is on a bus with PCI ID == 0000:00:1a.0 +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:\ +The above is based on the implementation of +coreboot/src/southbridge/intel/common/usb\_debug.c : +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). + +- On T500 (with switchable GPU) the debug ports for both intel + controllers is exposed. +- On x200t the debug ports for both intel controllers is exposed. + +### How to get the debug logs {#Howtogetthedebuglogs} + +- 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 + your BBB +- On the BBB: + +<!-- --> + + stty -icrnl -inlcr -F /dev/ttyGS0 + cat /dev/ttyGS0 + +- Power on the target with libreboot +- 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 + +### Eneble EHCI Debug on the target's kernel (optional, recommended) {#EnebleEHCIDebugonthetargetskerneloptionalrecommended} + +You have to know how to compile kernel for your target. + +1. Check if early debugging is already enabled: grep + CONFIG\_EARLY\_PRINTK\_DBGP /boot/config-<ver> +2. If enabled, you do not have to compile the kernel (skip this step). + Otherwise, prepare kernel source for your distribution and select + (Kernel hacking -> Early printk via EHCI debug port). Compile and + install the new kernel. +3. Edit your grub configuration and add following to the kenel + parameters^[20](#___fn20)[21](#___fn21)^: earlyprintk=dbgp,keep. + Also, try: earlyprintk=dbgp<N>,keep where N is the debug port + id if the first does not work. + +### References {#References} + +^10^ [EHCI Debug Port](http://www.coreboot.org/EHCI_Debug_Port) + +^11^ [coreboot EHCI debug gadget +demonstration](https://johnlewis.ie/coreboot-ehci-debug-gadget-demonstration/) + +^12^ [EHCI Gadget Debug](http://www.coreboot.org/EHCI_Gadget_Debug) + +^13^ +[Ehci-debug-gadget-patches.tar.gz](http://www.coreboot.org/images/8/88/Ehci-debug-gadget-patches.tar.gz) + +^14^ [Compiling the BeagleBone Black +Kernel](http://wiki.beyondlogic.org/index.php/BeagleBoneBlack_Building_Kernel) + +^15^ +http://dumb-looks-free.blogspot.ca/2014/06/beaglebone-black-bbb-compile-kernel.html + +^16^ +http://dumb-looks-free.blogspot.fr/2014/06/beaglebone-black-bbb-kernal-headers.html + +^17^ [Building BBB Kernel](http://elinux.org/Building_BBB_Kernel) + +^18^ +http://komposter.com.ua/documents/USB-2.0-Debug-Port%28John-Keys%29.pdf + +^19^ [Exploring USB at the Hardware/Software +Interface](http://cs.usfca.edu/~cruse/cs698s10/) + +^20^ https://www.kernel.org/doc/Documentation/x86/earlyprintk.txt + +^21^ https://wiki.ubuntu.com/Kernel/Debugging/USBearlyprintk + +**TODO**: + +1. grub does not send messages to EHCI debug. Investigate. +2. The section “Configure libreboot with EHCI debug” can be + skipped/simplified if a common configuration works for all relevant + targets is selected as defualt +3. Patch and compule g\_dbgp on BBB instead cross-compile +4. Find a simple way to send debug messages from targets userland + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/misc/index.html b/docs/misc/index.html deleted file mode 100644 index be54aab7..00000000 --- a/docs/misc/index.html +++ /dev/null @@ -1,366 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Miscellaneous</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Miscellaneous</h1> - <p> - Or <a href="../">Back to main index</a>. - </p> - <ul> - <li><a href="#debian_powertop">High Pitched Whining Noise on Idle (how to remove in Debian or Devuan)</a></li> - <li><a href="#high_pitch_parabola">High Pitched Whining Noise on Idle (how to remove in Parabola)</a></li> - <li><a href="#serial">X60/T60: Serial port - how to use (for dock owners)</a></li> - <li><a href="#powerbeeps">Power Management Beeps on Thinkpads</a></li> - <li><a href="patch.html">Using diff and patch</a></li> - <li><a href="#backlight control">Finetune backlight control on intel gpu’s</a></li> - <li><a href="#get_edid_panelname">Get EDID: Find out the name (model) of your LCD panel</a></li> - <li><a href="bbb_ehci.html">How to enable EHCI debugging on the BeagleBone Black</a></li> - <li><a href="#e1000-hang">e1000e driver trouble shooting (Intel NICs)</a></li> - </ul> - </div> - - <div class="section"> - - <h1 id="debian_powertop">High Pitched Whining Noise on Idle (how to remove in Debian or Devuan)</h1> - - <div class="subsection"> - <h2 id="debian_powertop_autostart">Start powertop automatically at boot time</h2> - - <p>Included with libreboot is a script called 'powertop.debian'. Run this as root and it will setup powertop to run with --auto-tune - at boot time. Load the file in your text editor to see how it does that.</p> - - <p>$ <b>sudo ./resources/scripts/misc/powertop.debian</b></p> - <p> - Might want to run with --calibrate first - </p> - <p> - If powertop doesn't work, another way (reduces battery life slightly) is - to add <i>processor.max_cstate=2</i> to the <i>linux</i> line in grub.cfg, - using <a href="../gnulinux/grub_cbfs.html">this guide</a>. - </p> - </div> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h1 id="high_pitch_parabola">High Pitched Whining Noise on Idle (how to remove in Parabola)</h1> - - <p>The following removes most of the noise. It reduces what is a high frequency whine - (that not everyone can hear) to a slight buzz (which most people can't hear or doesn't bother most people).</p> - - <p>This is not perfect! The full solution is still not discovered but this is a step towards that. - Also, in some instances you will need to run 'sudo powertop --auto-tune' again. - This needs to be implemented properly in coreboot itself!</p> - - <p>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! </p> - - <p>Be root<br/> - <b>$ su -</b></p> - - <p>Installed powertop:<br/> - <b># pacman -S powertop</b></p> - - <p>and added the following to /etc/systemd/system/powertop.service :</p> - -<pre><i> -[Unit] -Description=Powertop tunings - -[Service] -Type=oneshot -RemainAfterExit=no -ExecStart=/usr/bin/powertop --auto-tune -# "powertop --auto-tune" still needs a terminal for some reason. Possibly a bug? -Environment="TERM=xterm" - -[Install] -WantedBy=multi-user.target -</i></pre> - - - <p>Finally, as root do that:<br/> - <b># systemctl enable powertop</b><br/> - <b># systemctl start powertop</b></p> - - <p>The next time you boot the system, the buzz will be gone.</p> - - <p> - Might want to run with --calibrate first - </p> - <p> - If powertop doesn't work, another way (reduces battery life slightly) is - to add <i>processor.max_cstate=2</i> to the <i>linux</i> line in grub.cfg, - using <a href="../gnulinux/grub_cbfs.html">this guide</a>. - </p> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h1 id="serial">X60/T60: Serial port - how to use (for dock owners)</h1> - <p> - For the Thinkpad X60 you can use the <b>"UltraBase X6"</b> dock (for the X60 Tablet it is called - X6 Tablet UltraBase). For the ThinkPad T60, - you can use the <b>"Advanced Mini Dock"</b>. - </p> - <p> - If you are using one of the ROM images with 'serial' in the name, then you have serial port enabled in libreboot - and you have memtest86+ 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. - </p> - <p> - On the 2nd system, you can try this (using GNU Screen):<br/> - <b>$ sudo screen /dev/ttyUSB0 115200</b> - </p> - <p> - How to quit GNU Screen: Ctrl+A then release and press K, and then press Y. - </p> - <p>There are also others like Minicom but I like GNU Screen</p> - <p> - By doing this before booting the X60/T60, you will see console output from libreboot. You will also see - GRUB displaying on the serial output, and you will be able to see MemTest86+ on the serial output aswell. - You can also configure your distro so that a terminal (TTY) is accessible from the serial console. - </p> - <p> - The following guide is for Ubuntu, but it should work in Debian and Devuan, to enable a serial console using GeTTY:<br/> - <a href="https://help.ubuntu.com/community/SerialConsoleHowto">https://help.ubuntu.com/community/SerialConsoleHowto</a> - (we DO NOT recommend Ubuntu, because it contains non-free software in the default repos. Use Debian or Devuan) - </p> - <p> - Note: part of the tutorial above requires changing your grub.cfg. Just change the <b>linux</b> line to add instructions for enabling getty. - See <a href="../gnulinux/grub_cbfs.html">../gnulinux/grub_cbfs.html</a>. - </p> - <p><a href="#pagetop">Back to top of page</a> - - </div> - <div class="section" id="backlight control"> - <h1>Finetune backlight control on intel gpu’s </h1> - <p> - Sometimes the backlight control value (BLC_PWM_CTL) set by libreboot is not ideal. The result is either flicker, which could cause nausea or epilepsy or an uneven backlight and/or coil whine coming from the display. To fix this a different value for the gpu reg BLC_PWM_CTL needs to be set. See p94 of <a href="https://01.org/sites/default/files/documentation/g45_vol_3_register_0_0.pdf">https://01.org/sites/default/files/documentation/g45_vol_3_register_0_0.pdf</a> for more information on this reg. The tool for setting registry values on intel gpu’s is included in intel-gpu-tools. Install intel-gpu-tools: <b>sudo apt-get install intel-gpu-tools</b> - </p> - <p> - You can set values:</br> - <b>sudo intel_reg write 0x00061254 <your_value></b> - </p> - <p> - The value set has the following structure: bits [31:16] is PWM divider. PWM / PWM_divider = frequency bits [15:0] is the duty cycle and determines the portion of the backlight modulation frequency. A value of 0 will mean that the display is off. A value equal to the backlight modulation frequency means full on. The value should not be larger than the backlight modulation frequency. - </p> - <p> - On displays with a CCFL backlight start from: 0x60016001 To verify if all modes work as desired use:</br> - <b>xbacklight -set 10</b> - and gradually increase until 100. Displays with an LED backlight need a lower backlight modulation. Do the same thing but start from 0x01290129 . Try setting different values until you have found a value which presents no issue. - </p> - <p> - It is important to know that there are four failure modes: - <ol> - <li>flickering very fast, which could cause epilepsy (frequency is too low. decrease divider)</li> - <li>randomly flickering in random intervals - driver IC cannot keep up with toggling the mosfet (frequency too fast, increase divider)</li> - <li>frequency is in audible range and causes coils to whine (frequency is too high. increase divider)</li> - <li>backlight is uneven. (CCFL specific, frequency is too high. increase divider)</li> - </ol> - </p> - <p> - To check for flickering try moving your laptop while looking at it. - </p> - <p> - A higher frequency equals higher power consumption. You want to find the highest good working value. - </p> - <p> - Next this value should be set at boot: either add</br> - <pre>intel_reg write 0x00061254 <your_ideal_value></pre> - before exit 0 in /etc/rc.local or create a systemd service file /etc/systemd/system/backlight.service: - <pre> -[Unit] -Description=Set BLC_PWM_CTL to a good value -[Service] -Type=oneshot -RemainAfterExit=no -ExecStart=/usr/bin/intel_reg write 0x00061254 <your_value> -[Install] -WantedBy=multi-user.target - </pre> - Now start and enable it: <b>sudo systemctl start backlight && sudo systemctl enable backlight </b> - </p> - <p> - Special note on i945: - </p> - <p> - i945 behaves differently. Bit 16 needs to be 1 and the duty cycle is not updated when backlight is changed. There are no available datasheets on this target so why it behaves in such a way is not known. So to find a working value BLC_PWM_CTL set bit 16 to 1 and make sure PWM divider == duty cycle. see <a href="https://review.coreboot.org/#/c/10624/">https://review.coreboot.org/#/c/10624/</a> 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:</br> - <verbatim> - if(BPC[7:0] <> xFF) then BPCR[15:0] * BPC[7:0] Else BPCR[15:0] - </verbatim> - </br> - BPC is LBB - PCI Backlight Control Register, described on <a href="http://www.mouser.com/pdfdocs/945gmedatasheet.pdf">http://www.mouser.com/pdfdocs/945gmedatasheet.pdf</a> on page 315. BPCR is BLC_PWM_CTL described in <a href="https://01.org/sites/default/files/documentation/g45_vol_3_register_0_0.pdf">https://01.org/sites/default/files/documentation/g45_vol_3_register_0_0.pdf</a> on page 94. More research needs to be done on this target so proceed with care. - </p> - </div> - - - <div class="section" id="powerbeeps"> - - <h1>Power Management Beeps on Thinkpads</h1> - - <p> - When disconnecting or connecting the charger, a beep occurs. - When the 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. - </p> - - <p> - Disable or enable beeps when removing/adding the charger:<br/> - $ <b>sudo ./nvramtool -w power_management_beeps=Enable</b><br/> - $ <b>sudo ./nvramtool -w power_management_beeps=Disable</b> - </p> - - <p> - Disable or enable beeps when battery is low:<br/> - $ <b>sudo ./nvramtool -w low_battery_beep=Enable</b><br/> - $ <b>sudo ./nvramtool -w low_battery_beep=Disable</b> - </p> - - <p> - A reboot is required, for these changes to take effect. - </p> - - </div> - - <div class="section"> - - <h1 id="get_edid_panelname">Get EDID: Find out the name (model) of your LCD panel</h1> - <p> - Get the panel name with <b>sudo get-edid | strings</b><br/> - Or look in <b>/sys/class/drm/card0-LVDS-1/edid</b> - </p> - <p> - Alternatively you can use i2cdump. In Debian and Devuan, this is in the package i2c-tools.<br/> - $ <b>sudo modprobe i2c-dev</b><br/> - $ <b>sudo i2cdump -y 5 0x50</b> (you might have to change the value for -y)<br/> - $ <b>sudo rmmod i2c-dev</b><br/> - You'll see the panel name in the output (from the EDID dump). - </p> - <p> - If neither of these options work (or they are unavailable), physically removing the LCD panel is an option. - Usually, there will be information printed on the back. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="e1000-hang">e1000e driver trouble shooting (Intel NICs)</h1> - <p> - Example error, ¿may happen on weird and complex routing schemes(citation needed for cause): - </p> -<pre> -e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang -</pre> - <p> - Possible workaround, tested by Nazara: Disable C-STATES.<br/> - <strong> - 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) - </strong> - </p> - <p> - To disable c-states, do this in GNU+Linux:<br/> - <strong> - for i in /sys/devices/system/cpu/cpu/cpuidle/state/disable; do echo 1 > $i; done - </strong> - </p> - <p> - You can reproduce this issue more easily by sending lots of traffic across - subnets on the same interface (NIC). - </p> - <p> - More information, including logs, can be found on - <a href="https://notabug.org/vimuser/libreboot/issues/23">this page</a>. - </p> - - </div> - - <div class="section"> - - <h1 id="usb_keyboard_gm45">USB keyboard wakeup on GM45 laptops</h1> - <p> - Look at resources/scripts/helpers/misc/libreboot_usb_bugfix - </p> - <p> - Put this script in /etc/init.d/ on debian-based systems. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/misc/index.md b/docs/misc/index.md new file mode 100644 index 00000000..6db759a7 --- /dev/null +++ b/docs/misc/index.md @@ -0,0 +1,358 @@ +<div class="section"> + +Miscellaneous {#pagetop} +============= + +Or [Back to main index](../). + +- [High Pitched Whining Noise on Idle (how to remove in Debian or + Devuan)](#debian_powertop) +- [High Pitched Whining Noise on Idle (how to remove in + Parabola)](#high_pitch_parabola) +- [X60/T60: Serial port - how to use (for dock owners)](#serial) +- [Power Management Beeps on Thinkpads](#powerbeeps) +- [Using diff and patch](patch.html) +- [Finetune backlight control on intel gpu's](#backlight%20control) +- [Get EDID: Find out the name (model) of your LCD + panel](#get_edid_panelname) +- [How to enable EHCI debugging on the BeagleBone + Black](bbb_ehci.html) +- [e1000e driver trouble shooting (Intel NICs)](#e1000-hang) + +</div> + +<div class="section"> + +High Pitched Whining Noise on Idle (how to remove in Debian or Devuan) {#debian_powertop} +====================================================================== + +<div class="subsection"> + +Start powertop automatically at boot time {#debian_powertop_autostart} +----------------------------------------- + +Included with libreboot is a script called \'powertop.debian\'. Run this +as root and it will setup powertop to run with \--auto-tune at boot +time. Load the file in your text editor to see how it does that. + +\$ **sudo ./resources/scripts/misc/powertop.debian** + +Might want to run with \--calibrate first + +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). + +</div> + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +High Pitched Whining Noise on Idle (how to remove in Parabola) {#high_pitch_parabola} +============================================================== + +The following removes most of the noise. It reduces what is a high +frequency whine (that not everyone can hear) to a slight buzz (which +most people can\'t hear or doesn\'t bother most people). + +This is not perfect! The full solution is still not discovered but this +is a step towards that. Also, in some instances you will need to run +\'sudo powertop \--auto-tune\' again. This needs to be implemented +properly in coreboot itself! + +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\ +**\$ su -** + +Installed powertop:\ +**\# pacman -S powertop** + +and added the following to /etc/systemd/system/powertop.service : + + [Unit] + Description=Powertop tunings + + [Service] + Type=oneshot + RemainAfterExit=no + ExecStart=/usr/bin/powertop --auto-tune + # "powertop --auto-tune" still needs a terminal for some reason. Possibly a bug? + Environment="TERM=xterm" + + [Install] + WantedBy=multi-user.target + +Finally, as root do that:\ +**\# systemctl enable powertop**\ +**\# systemctl start powertop** + +The next time you boot the system, the buzz will be gone. + +Might want to run with \--calibrate first + +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) + +</div> + +<div class="section"> + +X60/T60: Serial port - how to use (for dock owners) {#serial} +=================================================== + +For the Thinkpad X60 you can use the **\"UltraBase X6\"** dock (for the +X60 Tablet it is called X6 Tablet UltraBase). For the ThinkPad T60, you +can use the **\"Advanced Mini Dock\"**. + +If you are using one of the ROM images with \'serial\' in the name, then +you have serial port enabled in libreboot and you have memtest86+ +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** + +How to quit GNU Screen: Ctrl+A then release and press K, and then press +Y. + +There are also others like Minicom but I like GNU Screen + +By doing this before booting the X60/T60, you will see console output +from libreboot. You will also see GRUB displaying on the serial output, +and you will be able to see MemTest86+ on the serial output aswell. You +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:\ +<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) + +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) + +</div> + +<div id="backlight control" class="section"> + +Finetune backlight control on intel gpu's +========================================= + +Sometimes the backlight control value (BLC\_PWM\_CTL) set by libreboot +is not ideal. The result is either flicker, which could cause nausea or +epilepsy or an uneven backlight and/or coil whine coming from the +display. To fix this a different value for the gpu reg BLC\_PWM\_CTL +needs to be set. See p94 of +<https://01.org/sites/default/files/documentation/g45_vol_3_register_0_0.pdf> +for more information on this reg. The tool for setting registry values +on intel gpu's is included in intel-gpu-tools. Install intel-gpu-tools: +**sudo apt-get install intel-gpu-tools** + +You can set values: **sudo intel\_reg write 0x00061254 +<your\_value>** + +The value set has the following structure: bits \[31:16\] is PWM +divider. PWM / PWM\_divider = frequency bits \[15:0\] is the duty cycle +and determines the portion of the backlight modulation frequency. A +value of 0 will mean that the display is off. A value equal to the +backlight modulation frequency means full on. The value should not be +larger than the backlight modulation frequency. + +On displays with a CCFL backlight start from: 0x60016001 To verify if +all modes work as desired use: **xbacklight -set 10** and gradually +increase until 100. Displays with an LED backlight need a lower +backlight modulation. Do the same thing but start from 0x01290129 . Try +setting different values until you have found a value which presents no +issue. + +It is important to know that there are four failure modes: + +1. flickering very fast, which could cause epilepsy (frequency is too + low. decrease divider) +2. randomly flickering in random intervals - driver IC cannot keep up + with toggling the mosfet (frequency too fast, increase divider) +3. frequency is in audible range and causes coils to whine (frequency + is too high. increase divider) +4. backlight is uneven. (CCFL specific, frequency is too high. increase + divider) + +To check for flickering try moving your laptop while looking at it. + +A higher frequency equals higher power consumption. You want to find the +highest good working value. + +Next this value should be set at boot: either add + + intel_reg write 0x00061254 <your_ideal_value> + +before exit 0 in /etc/rc.local or create a systemd service file +/etc/systemd/system/backlight.service: + [Unit] + Description=Set BLC_PWM_CTL to a good value + [Service] + Type=oneshot + RemainAfterExit=no + ExecStart=/usr/bin/intel_reg write 0x00061254 <your_value> + [Install] + WantedBy=multi-user.target + + +Now start and enable it: **sudo systemctl start backlight && sudo +systemctl enable backlight** +Special note on i945: + +i945 behaves differently. Bit 16 needs to be 1 and the duty cycle is not +updated when backlight is changed. There are no available datasheets on +this target so why it behaves in such a way is not known. So to find a +working value BLC\_PWM\_CTL set bit 16 to 1 and make sure PWM divider == +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\] +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 +<https://01.org/sites/default/files/documentation/g45_vol_3_register_0_0.pdf> +on page 94. More research needs to be done on this target so proceed +with care. + +</div> + +<div id="powerbeeps" class="section"> + +Power Management Beeps on Thinkpads +=================================== + +When disconnecting or connecting the charger, a beep occurs. When the +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**\ +\$ **sudo ./nvramtool -w power\_management\_beeps=Disable** + +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. + +</div> + +<div class="section"> + +Get EDID: Find out the name (model) of your LCD panel {#get_edid_panelname} +===================================================== + +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**\ +\$ **sudo i2cdump -y 5 0x50** (you might have to change the value for +-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 +removing the LCD panel is an option. Usually, there will be information +printed on the back. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +e1000e driver trouble shooting (Intel NICs) {#e1000-hang} +=========================================== + +Example error, ¿may happen on weird and complex routing schemes(citation +needed for cause): + + e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang + +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:\ +**for i in /sys/devices/system/cpu/cpu/cpuidle/state/disable; do echo 1 +> \$i; done** + +You can reproduce this issue more easily by sending lots of traffic +across subnets on the same interface (NIC). + +More information, including logs, can be found on [this +page](https://notabug.org/vimuser/libreboot/issues/23). + +</div> + +<div class="section"> + +USB keyboard wakeup on GM45 laptops {#usb_keyboard_gm45} +=================================== + +Look at resources/scripts/helpers/misc/libreboot\_usb\_bugfix + +Put this script in /etc/init.d/ on debian-based systems. + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/misc/patch.html b/docs/misc/patch.html deleted file mode 100644 index 1e459a1f..00000000 --- a/docs/misc/patch.html +++ /dev/null @@ -1,218 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title> - Libreboot documentation: using diff and patch - </title> - -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Diff and patch</h1> - <p>This is just a quick guide for reference, use 'man' to know more.</p> - <p> - <a href="./">Back to index</a> - </p> - </div> - - <div class="section"> - - <h1> - Apply a patch - </h1> - - <p class="important"> - To apply a patch to a single file, do that in it's directory:<br/> - <b>$ patch < foo.patch</b> - </p> - - <p> - Assuming that the patch is distributed in unified format identifying - the file the patch should be applied to, the above will work. Otherwise:<br/> - <b>$ patch foo.txt < bar.patch</b> - </p> - - <p> - 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 - 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:<br/> - <b>$ patch -p1 < baz.patch</b> - </p> - - <p> - 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:<br/> - <b>/home/user/do/not/panic/yet.c</b> - </p> - - <p> - and you are working in a directory that contains panic/yet.c, use:<br/> - <b>$ patch -p5 < baz.patch</b> - </p> - - <p> - 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. - </p> - - <p> - Removing a patch using the -R flag<br/> - <b>$ patch -p5 -R < baz.patch</b> - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1> - Create a patch with diff - </h1> - - <p> - Diff can create a patch for a single file:<br/> - <b>$ diff -u original.c new.c > original.patch</b> - </p> - - <p> - For diff'ing a source tree:<br/> - <b>$ cp -R original new</b> - </p> - - <p> - Do whatever you want in new/ and then diff it:<br/> - <b>$ diff -rupN original/ new/ > original.patch</b> - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1> - git diff - </h1> - - <p> - git is something special. - </p> - <p> - Note: this won't show new files created. - </p> - - <p> - Just make whatever changes you want to a git clone and then:<br/> - <b>$ git diff > patch.git</b> - </p> - - <p> - Note the git revision that you did this with:<br/> - <b>$ git log</b> - </p> - - <p> - Alternatively (better yet), commit your changes and then use:<br/> - $ <b>git format-patch -N</b><br/> - Replace N with the number of commits that you want to show. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1> - git apply - </h1> - - <p>it really is.</p> - - <p> - Now to apply that patch in the future, just git clone it again and do - with the git revision you found from above:<br/> - <b>$ git reset --hard REVISIONNUMBER</b> - </p> - - <p> - Now put patch.git in the git clone directory and do:<br/> - <b>$ git apply patch.git</b> - </p> - - <p> - If you use a patch from git format-patch, then use <b>git am patch.git</b> instead of <b>git apply patch.git</b>. git-am - will re-create the commits aswell, instead of just applying the patch. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - 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 <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/misc/patch.md b/docs/misc/patch.md new file mode 100644 index 00000000..46d6a15a --- /dev/null +++ b/docs/misc/patch.md @@ -0,0 +1,151 @@ +<div class="section"> + +Diff and patch {#pagetop} +============== + +This is just a quick guide for reference, use \'man\' to know more. + +[Back to index](./) + +</div> + +<div class="section"> + +Apply a 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** + +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 +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** + +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:\ +**/home/user/do/not/panic/yet.c** + +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** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Create a patch with diff +======================== + +Diff can create a patch for a single file:\ +**\$ diff -u original.c new.c > original.patch** + +For diff\'ing a source tree:\ +**\$ cp -R original new** + +Do whatever you want in new/ and then diff it:\ +**\$ diff -rupN original/ new/ > original.patch** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +git diff +======== + +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** + +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) + +</div> + +<div class="section"> + +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** + +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 +aswell, instead of just applying the patch. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +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 +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. + +</div> diff --git a/docs/release.html b/docs/release.html deleted file mode 100644 index 1295a5bf..00000000 --- a/docs/release.html +++ /dev/null @@ -1,330 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('css/main.css'); - </style> - - <title>Libreboot release information</title> -</head> -<body> - <div class="section"> - <h1 id="pagetop">Libreboot release information</h1> - <p> - Updated versions of libreboot can be found at <a href="http://libreboot.org/">libreboot.org</a>. - </p> - </div> - - <div class="section"> - - <h2>Old releases</h2> - <p> - See <a href="archive_old.html">archive_old.html</a> for information about older libreboot releases. - </p> - - </div> - - <div class="section"> - - <h1 id="release20160907">Libreboot 20160907</h1> - - <p> - Release date: 7th September 2016 - </p> - <p> - For existing boards, there are no new board specific changes. - </p> - - <p> - This release adds one new mainboard to libreboot: - </p> - <ul> - <li>Intel D945GCLF desktop motherboard (thanks to Arthur Heymans)</li> - </ul> - - <p> - Other bugfixes: - </p> - <ul> - <li>Various improvements to the documentation</li> - <li>re-added "unset superusers" to the grub.cfg, which was needed for some users - depending on the distros that they used</li> - </ul> - - <h1 id="release20160922">Libreboot 20160902</h1> - - <p> - Release date: 2nd September 2016. - </p> - <p> - This fixes build issues in the previous 20160818 release. See - change log for details. - </p> - - <h1 id="release20160818">Libreboot 20160818</h1> - - <p> - Release date: 18th August 2016. - </p> - - <p> - Installation instructions can be found at <b><i>docs/install/</i></b>. - Building instructions (for source code) can be found at <b><i>docs/git/#build</i></b>. - </p> - - <h2>Machines supported in this release:</h2> - <ul> - <li> - <b>ASUS Chromebook C201</b> - <ul> - <li>Check notes in <b><i>docs/hcl/c201.html</i></b></li> - </ul> - </li> - <li> - <b>Gigabyte GA-G41M-ES2L desktop motherboard</b> - <ul> - <li>Check notes in <b><i>docs/hcl/ga-g41m-es2l.html</i></b></li> - </ul> - </li> - <li> - <b>Intel D510MO desktop motherboard</b> - <ul> - <li>Check notes in <b><i>docs/hcl/d510mo.html</i></b></li> - </ul> - </li> - <li> - <b>Intel D945GCLF desktop motherboard</b> - <ul> - <li>Check notes in <b><i>docs/hcl/d945gclf.html</i></b></li> - </ul> - </li> - <li> - <b>Apple iMac 5,2</b> - <ul> - <li>Check notes in <b><i>docs/hcl/imac52.html</i></b></li> - </ul> - </li> - <li> - <b>ASUS KFSN4-DRE server board</b> - <ul> - <li>PCB revision 1.05G is the best version (can use 6-core CPUs)</li> - <li>Check notes in <b><i>docs/hcl/kfsn4-dre.html</i></b></li> - </ul> - </li> - <li> - <b>ASUS KGPE-D16 server board</b> - <ul> - <li>Check notes in <b><i>docs/hcl/kgpe-d16.html</i></b></li> - </ul> - </li> - <li> - <b>ASUS KCMA-D8 desktop/workstation board</b> - <ul> - <li>Check notes in <b><i>docs/hcl/kcma-d8.html</i></b></li> - </ul> - </li> - <li> - <b>ThinkPad X60/X60s</b> - <ul> - <li> - You can also remove the motherboard from an X61/X61s and replace it with an X60/X60s motherboard. - An X60 Tablet motherboard will also fit inside an X60/X60s. - </li> - </ul> - </li> - <li> - <b>ThinkPad X60 Tablet</b> (1024x768 and 1400x1050) with digitizer support - <ul> - <li>See <b><i>docs/hcl/#supported_x60t_list</i></b> for list of supported LCD panels</li> - <li>It is unknown whether an X61 Tablet can have it's mainboard replaced with an X60 Tablet motherboard.</li> - </ul> - </li> - <li> - <b>ThinkPad T60</b> (Intel GPU) (there are issues; see below): - <ul> - <li>See notes below for exceptions, and <b><i>docs/hcl/#supported_t60_list</i></b> for known working LCD panels.</li> - <li>It is unknown whether a T61 can have it's mainboard replaced with a T60 motherboard.</li> - <li>See <b><i>docs/future/#t60_cpu_microcode</i></b>.</li> - <li>T60P (and T60 laptops with ATI GPU) will likely never be supported: <b><i>docs/hcl/#t60_ati_intel</i></b></li> - </ul> - </li> - <li> - <b>ThinkPad X200</b> - <ul> - <li>X200S and X200 Tablet are also supported, conditionally; see <b><i>docs/hcl/x200.html#x200s</i></b></li> - <li><b>ME/AMT</b>: libreboot removes this, permanently. <b><i>docs/hcl/gm45_remove_me.html</i></b></li> - </ul> - </li> - <li> - <b>ThinkPad R400</b> - <ul> - <li>See <b><i>docs/hcl/r400.html</i></b></li> - <li><b>ME/AMT</b>: libreboot removes this, permanently. <b><i>docs/hcl/gm45_remove_me.html</i></b></li> - </ul> - </li> - <li> - <b>ThinkPad T400</b> - <ul> - <li>See <b><i>docs/hcl/t400.html</i></b></li> - <li><b>ME/AMT</b>: libreboot removes this, permanently. <b><i>docs/hcl/gm45_remove_me.html</i></b></li> - </ul> - </li> - <li> - <b>ThinkPad T500</b> - <ul> - <li>See <b><i>docs/hcl/t500.html</i></b></li> - <li><b>ME/AMT</b>: libreboot removes this, permanently. <b><i>docs/hcl/gm45_remove_me.html</i></b></li> - </ul> - </li> - <li> -<b>Apple MacBook1,1</b> (MA255LL/A, MA254LL/A, MA472LL/A) - <ul> - <li>See <b><i>docs/hcl/#macbook11</i></b>.</li> - </ul> - </li> - <li> -<b>Apple MacBook2,1</b> (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - <ul> - <li>See <b><i>docs/hcl/#macbook21</i></b>.</li> - </ul> - </li> - </ul> - - <h2> -Changes for this release, relative to r20150518 (earliest changes last, recent changes first) - </h2> -<ul> -<li>NEW BOARDS ADDED: -<ul> -<li>ASUS Chromebook C201 (ARM laptop) (thanks to Paul Kocialkowski)</li> -<li>Gigabyte GA-G41M-ES2L motherboard (desktop) (thanks to Damien Zammit)</li> -<li>Intel D510MO motherboard (desktop) (thanks to Damien Zammit)</li> -<li>ASUS KCMA-D8 motherboard (desktop) (thanks to Timothy Pearson)</li> -<li>ASUS KFSN4-DRE motherboard (server) (thanks to Timothy Pearson)</li> -<li>ASUS KGPE-D16 motherboard (server) (thanks to Timothy Pearson)</li> -</ul> -</li> -</ul> -<p> -For details development history on these boards, refer to the git log and documentation. -</p> -<p> -For boards previously supported, many fixes from upstream have been merged. -</p> -<p> -Other changes (compared to libreboot 20150518), for libreboot in general or for previously supported systems: -(this is a summary. For more detailed change list, refer to the git log) -</p> -<p> -256MiB VRAM allocated on GM45 (X200, T400, T500, R400) instead of 32MiB. This is an improvement over both Lenovo BIOS and Libreboot 20150518, allowing video decoding at 1080p to be smoother. (thanks Arthur Heymans) -To clarify, GM45 video performance in libreboot 20160818 is better than on the original BIOS and the previous libreboot release. -</p> -<p> -64MiB VRAM on i945 (X60, T60, MacBook2,1) now supported in coreboot-libre, and used by default (in the previous release, it was 8MiB allocated). Thanks to Arthur Heymans. -</p> -<p> -Higher battery life on GM45 (X200, T400, T500, R400) due to higher cstates now being supported (thanks Arthur Heymans). C4 power states also supported. -</p> -<p> -Higher battery life on i945 (X60, T60, MacBook2,1) due to better CPU C-state settings. (Deep C4, Dynamicl L2 shrinking, C2E). -</p> -<p> -Text mode on GM45 (X200, T400, T500, R400) now works, making it possible to use MemTest86+ comfortably. (thanks to Nick High from coreboot) -</p> -<p> -Dual channel LVDS displays on GM45 (T400, T500) are now automatically detected in coreboot-libre. (thanks Vladimir Serbinenko from coreboot) -</p> -<p> -Partial fix in coreboot-libre for GRUB display on GM45, for dual channel LVDS higher resolution LCD panels (T400, T500). (thanks Arthur Heymans) -</p> -<p> -Massively improved GRUB configuration, making it easier to boot more encrypted systems automatically, and generally a more useful menu for booting the system (thanks go to Klemens Nanni of the autoboot project). -Libreboot now uses the grub.cfg provided by the installed GNU+Linux distribution automatically, if present, switching to that configuration. This is done across many partitions, where libreboot actively searches for a configuration file -(also on LVM volumes and encrypted volumes). This should make libreboot more easy to use for non-technical users, without having to modify the GRUB configuration used in libreboot. -</p> -<p> -Utilities archives is now source only. You will need to compile the packages in there (build scripts included, and a script for installing build dependencies). (binary utility archives are planned again in the next release, when the new build system is merged) -</p> -<p> -SeaGRUB is now the default payload on all x86 boards. (SeaBIOS configured to load a compressed GRUB payload from CBFS immediately, without providing an interface in SeaBIOS. This way, GRUB is still used but now BIOS services are available, so you get the best of both worlds). Thanks go to Timothy Pearson of coreboot for this idea. -</p> -<p> -crossgcc is now downloaded and built as a separate module to coreboot-libre, with a universal revision used to build all boards. -</p> -<p> -Individual boards now have their own coreboot revision and patches, independently of each other board. This makes maintenance easier. -</p> -<p> -Updated all utilities, and modules (coreboot, GRUB, etc) to newer versions, with various bugfixes and improvements upstream. -</p> -<p> -RTC century byte issue now fixed on GM45 in coreboot-libre, so the date should now be correctly displayed when running the latest linux kernel, instead of seeing 1970-01-01 when you boot (thanks to Alexander Couzens from coreboot) -</p> -<p> -Build system now uses multiple CPU cores when building, speeding up building for some people. Manually specifying how many cores are needed is also possible, for those using the build system in a chroot environment. (thanks go to Timothy Pearson from coreboot) -</p> -<p> -In the build system (git repository), https:// is now used when cloning coreboot. http:// is used as a fallback for GRUB, if git:// fails. -</p> -<p> -New payload, the depthcharge bootloader (free bootloader maintained by Google) for use on the ASUS Chromebook C201. (thanks go to Paul Kocialkowski) -</p> -<p> -Various fixes to the ich9gen utility (e.g. flash component density is now set correctly in the descriptor, gbe-less descriptors now supported) -</p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org><br/> - 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 <a href="cc-by-sa-4.0.txt">cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - 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. - </p> - <p> - 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. - </p> - <p> - 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. - </p> - - </div> - -</body> -</html> diff --git a/docs/release.md b/docs/release.md new file mode 100644 index 00000000..d6300129 --- /dev/null +++ b/docs/release.md @@ -0,0 +1,254 @@ +<div class="section"> + +Libreboot release information {#pagetop} +============================= + +Updated versions of libreboot can be found at +[libreboot.org](http://libreboot.org/). + +</div> + +<div class="section"> + +Old releases +------------ + +See [archive\_old.html](archive_old.html) for information about older +libreboot releases. + +</div> + +<div class="section"> + +Libreboot 20160907 {#release20160907} +================== + +Release date: 7th September 2016 + +For existing boards, there are no new board specific changes. + +This release adds one new mainboard to libreboot: + +- Intel D945GCLF desktop motherboard (thanks to Arthur Heymans) + +Other bugfixes: + +- Various improvements to the documentation +- re-added \"unset superusers\" to the grub.cfg, which was needed for + some users depending on the distros that they used + +Libreboot 20160902 {#release20160922} +================== + +Release date: 2nd September 2016. + +This fixes build issues in the previous 20160818 release. See change log +for details. + +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***. + +Machines supported in this release: +----------------------------------- + +- **ASUS Chromebook C201** + - Check notes in ***docs/hcl/c201.html*** +- **Gigabyte GA-G41M-ES2L desktop motherboard** + - Check notes in ***docs/hcl/ga-g41m-es2l.html*** +- **Intel D510MO desktop motherboard** + - Check notes in ***docs/hcl/d510mo.html*** +- **Intel D945GCLF desktop motherboard** + - Check notes in ***docs/hcl/d945gclf.html*** +- **Apple iMac 5,2** + - Check notes in ***docs/hcl/imac52.html*** +- **ASUS KFSN4-DRE server board** + - PCB revision 1.05G is the best version (can use 6-core CPUs) + - Check notes in ***docs/hcl/kfsn4-dre.html*** +- **ASUS KGPE-D16 server board** + - Check notes in ***docs/hcl/kgpe-d16.html*** +- **ASUS KCMA-D8 desktop/workstation board** + - Check notes in ***docs/hcl/kcma-d8.html*** +- **ThinkPad X60/X60s** + - You can also remove the motherboard from an X61/X61s and replace + it with an X60/X60s motherboard. An X60 Tablet motherboard will + 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 + 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 + panels. + - It is unknown whether a T61 can have it\'s mainboard replaced + with a T60 motherboard. + - See ***docs/future/\#t60\_cpu\_microcode***. + - T60P (and T60 laptops with ATI GPU) will likely never be + supported: ***docs/hcl/\#t60\_ati\_intel*** +- **ThinkPad X200** + - X200S and X200 Tablet are also supported, conditionally; see + ***docs/hcl/x200.html\#x200s*** + - **ME/AMT**: libreboot removes this, permanently. + ***docs/hcl/gm45\_remove\_me.html*** +- **ThinkPad R400** + - See ***docs/hcl/r400.html*** + - **ME/AMT**: libreboot removes this, permanently. + ***docs/hcl/gm45\_remove\_me.html*** +- **ThinkPad T400** + - See ***docs/hcl/t400.html*** + - **ME/AMT**: libreboot removes this, permanently. + ***docs/hcl/gm45\_remove\_me.html*** +- **ThinkPad T500** + - See ***docs/hcl/t500.html*** + - **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***. +- **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, + MB063LL/A, MB062LL/A) + - See ***docs/hcl/\#macbook21***. + +Changes for this release, relative to r20150518 (earliest changes last, recent changes first) +--------------------------------------------------------------------------------------------- + +- NEW BOARDS ADDED: + - ASUS Chromebook C201 (ARM laptop) (thanks to Paul Kocialkowski) + - Gigabyte GA-G41M-ES2L motherboard (desktop) (thanks to Damien + Zammit) + - Intel D510MO motherboard (desktop) (thanks to Damien Zammit) + - ASUS KCMA-D8 motherboard (desktop) (thanks to Timothy Pearson) + - ASUS KFSN4-DRE motherboard (server) (thanks to Timothy Pearson) + - ASUS KGPE-D16 motherboard (server) (thanks to Timothy Pearson) + +For details development history on these boards, refer to the git log +and documentation. + +For boards previously supported, many fixes from upstream have been +merged. + +Other changes (compared to libreboot 20150518), for libreboot in general +or for previously supported systems: (this is a summary. For more +detailed change list, refer to the git log) + +256MiB VRAM allocated on GM45 (X200, T400, T500, R400) instead of 32MiB. +This is an improvement over both Lenovo BIOS and Libreboot 20150518, +allowing video decoding at 1080p to be smoother. (thanks Arthur Heymans) +To clarify, GM45 video performance in libreboot 20160818 is better than +on the original BIOS and the previous libreboot release. + +64MiB VRAM on i945 (X60, T60, MacBook2,1) now supported in +coreboot-libre, and used by default (in the previous release, it was +8MiB allocated). Thanks to Arthur Heymans. + +Higher battery life on GM45 (X200, T400, T500, R400) due to higher +cstates now being supported (thanks Arthur Heymans). C4 power states +also supported. + +Higher battery life on i945 (X60, T60, MacBook2,1) due to better CPU +C-state settings. (Deep C4, Dynamicl L2 shrinking, C2E). + +Text mode on GM45 (X200, T400, T500, R400) now works, making it possible +to use MemTest86+ comfortably. (thanks to Nick High from coreboot) + +Dual channel LVDS displays on GM45 (T400, T500) are now automatically +detected in coreboot-libre. (thanks Vladimir Serbinenko from coreboot) + +Partial fix in coreboot-libre for GRUB display on GM45, for dual channel +LVDS higher resolution LCD panels (T400, T500). (thanks Arthur Heymans) + +Massively improved GRUB configuration, making it easier to boot more +encrypted systems automatically, and generally a more useful menu for +booting the system (thanks go to Klemens Nanni of the autoboot project). +Libreboot now uses the grub.cfg provided by the installed GNU+Linux +distribution automatically, if present, switching to that configuration. +This is done across many partitions, where libreboot actively searches +for a configuration file (also on LVM volumes and encrypted volumes). +This should make libreboot more easy to use for non-technical users, +without having to modify the GRUB configuration used in libreboot. + +Utilities archives is now source only. You will need to compile the +packages in there (build scripts included, and a script for installing +build dependencies). (binary utility archives are planned again in the +next release, when the new build system is merged) + +SeaGRUB is now the default payload on all x86 boards. (SeaBIOS +configured to load a compressed GRUB payload from CBFS immediately, +without providing an interface in SeaBIOS. This way, GRUB is still used +but now BIOS services are available, so you get the best of both +worlds). Thanks go to Timothy Pearson of coreboot for this idea. + +crossgcc is now downloaded and built as a separate module to +coreboot-libre, with a universal revision used to build all boards. + +Individual boards now have their own coreboot revision and patches, +independently of each other board. This makes maintenance easier. + +Updated all utilities, and modules (coreboot, GRUB, etc) to newer +versions, with various bugfixes and improvements upstream. + +RTC century byte issue now fixed on GM45 in coreboot-libre, so the date +should now be correctly displayed when running the latest linux kernel, +instead of seeing 1970-01-01 when you boot (thanks to Alexander Couzens +from coreboot) + +Build system now uses multiple CPU cores when building, speeding up +building for some people. Manually specifying how many cores are needed +is also possible, for those using the build system in a chroot +environment. (thanks go to Timothy Pearson from coreboot) + +In the build system (git repository), https:// is now used when cloning +coreboot. http:// is used as a fallback for GRUB, if git:// fails. + +New payload, the depthcharge bootloader (free bootloader maintained by +Google) for use on the ASUS Chromebook C201. (thanks go to Paul +Kocialkowski) + +Various fixes to the ich9gen utility (e.g. flash component density is +now set correctly in the descriptor, gbe-less descriptors now supported) + +</div> + +<div class="section"> + +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 +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. + +</div> |