diff options
| author | Alyssa Rosenzweig <alyssa@rosenzweig.io> | 2017-03-17 23:05:29 -0700 |
|---|---|---|
| committer | Alyssa Rosenzweig <alyssa@rosenzweig.io> | 2017-03-17 23:05:29 -0700 |
| commit | c2b25f1e127ff810e4565d553aafc28b7c44d1a2 (patch) | |
| tree | e31f916e6264d3847752290cddcbde0af8a968a5 | |
| parent | 29610c6f3b1b1e78ae7cec11b41368fe9d76c6ed (diff) | |
| download | librebootfr-c2b25f1e127ff810e4565d553aafc28b7c44d1a2.tar.gz librebootfr-c2b25f1e127ff810e4565d553aafc28b7c44d1a2.zip | |
Unbork some things
42 files changed, 451 insertions, 451 deletions
diff --git a/docs/archive_old.md b/docs/archive_old.md index 13433abc..0551e08d 100644 --- a/docs/archive_old.md +++ b/docs/archive_old.md @@ -36,7 +36,7 @@ Release 20150518 {#release20150518} Release date: 18th May 2015. Installation instructions can be found at ***docs/install/***. Building -instructions (for source code) can be found at ***docs/git/\#build***. +instructions (for source code) can be found at ***docs/git/#build***. Machines supported in this release: ----------------------------------- @@ -47,22 +47,22 @@ Machines supported in this release: also fit inside an X60/X60s. - **ThinkPad X60 Tablet** (1024x768 and 1400x1050) with digitizer support - - See ***docs/hcl/\#supported\_x60t\_list*** for list of supported + - See ***docs/hcl/#supported\_x60t\_list*** for list of supported LCD panels - It is unknown whether an X61 Tablet can have it's mainboard replaced with an X60 Tablet motherboard. - **ThinkPad T60** (Intel GPU) (there are issues; see below): - See notes below for exceptions, and - ***docs/hcl/\#supported\_t60\_list*** for known working LCD + ***docs/hcl/#supported\_t60\_list*** for known working LCD panels. - It is unknown whether a T61 can have it's mainboard replaced with a T60 motherboard. - - See ***docs/future/\#t60\_cpu\_microcode***. + - See ***docs/future/#t60\_cpu\_microcode***. - T60P (and T60 laptops with ATI GPU) will likely never be - supported: ***docs/hcl/\#t60\_ati\_intel*** + supported: ***docs/hcl/#t60\_ati\_intel*** - **ThinkPad X200** - X200S and X200 Tablet are also supported, conditionally; see - ***docs/hcl/x200.html\#x200s*** + ***docs/hcl/x200.html#x200s*** - **ME/AMT**: libreboot removes this, permanently. ***docs/hcl/gm45\_remove\_me.html*** - **ThinkPad R400** @@ -78,10 +78,10 @@ Machines supported in this release: - **ME/AMT**: libreboot removes this, permanently. ***docs/hcl/gm45\_remove\_me.html*** - **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) - - See ***docs/hcl/\#macbook11***. + - See ***docs/hcl/#macbook11***. - **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - - See ***docs/hcl/\#macbook21***. + - See ***docs/hcl/#macbook21***. Changes for this release, relative to r20150208 (earliest changes last, recent changes first) --------------------------------------------------------------------------------------------- @@ -271,32 +271,32 @@ Machines supported in this release: also fit inside an X60/X60s. - **Lenovo ThinkPad X60 Tablet** (1024x768 and 1400x1050) with digitizer support - - See **hcl/\#supported\_x60t\_list** for list of supported LCD + - See **hcl/#supported\_x60t\_list** for list of supported LCD panels - It is unknown whether an X61 Tablet can have it's mainboard replaced with an X60 Tablet motherboard. - **Lenovo ThinkPad T60** (Intel GPU) (there are issuesinstall/x200\_external.html; see below): - See notes below for exceptions, and - **hcl/\#supported\_t60\_list** for known working LCD panels. + **hcl/#supported\_t60\_list** for known working LCD panels. - It is unknown whether a T61 can have it's mainboard replaced with a T60 motherboard. - - See **future/\#t60\_cpu\_microcode**. + - See **future/#t60\_cpu\_microcode**. - T60P (and T60 laptops with ATI GPU) will likely never be - supported: **hcl/\#t60\_ati\_intel** + supported: **hcl/#t60\_ati\_intel** - **Lenovo ThinkPad X200** - X200S and X200 Tablet are also supported, conditionally; see - **hcl/x200.html\#x200s** + **hcl/x200.html#x200s** - **ME/AMT**: libreboot removes this, permanently. **hcl/gm45\_remove\_me.html** - **Lenovo ThinkPad R400** (r20150208 and later, only) - **ME/AMT**: libreboot removes this, permanently. **hcl/gm45\_remove\_me.html** - **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) - - See **hcl/\#macbook11**. + - See **hcl/#macbook11**. - **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - - See **hcl/\#macbook21**. + - See **hcl/#macbook21**. Revisions for r20150208 (relative to r20150126) ----------------------------------------------- @@ -377,7 +377,7 @@ Changes for this release (latest changes first, earliest changes last) - buildrom-withgrub: disabled creation of *txtmode*.rom for X200 (only framebuffer graphics work) - Updated SeaBIOS (again) -- docs/install/\#flashrom\_x200: improve instructions +- docs/install/#flashrom\_x200: improve instructions - Updated flashrom (again) - patches updated - Updated GRUB (again) - Updated coreboot (again) @@ -482,23 +482,23 @@ Machines supported in this release: also fit inside an X60/X60s. - **Lenovo ThinkPad X60 Tablet** (1024x768 and 1400x1050) with digitizer support - - See **hcl/\#supported\_x60t\_list** for list of supported LCD + - See **hcl/#supported\_x60t\_list** for list of supported LCD panels - It is unknown whether an X61 Tablet can have its mainboard replaced with an X60 Tablet motherboard. - **Lenovo ThinkPad T60** (Intel GPU) (there are issues; see below): - See notes below for exceptions, and - **hcl/\#supported\_t60\_list** for known working LCD panels. + **hcl/#supported\_t60\_list** for known working LCD panels. - It is unknown whether a T61 can have its mainboard replaced with a T60 motherboard. - - See **future/\#t60\_cpu\_microcode**. + - See **future/#t60\_cpu\_microcode**. - T60P (and T60s with ATI GPU) will likely never be supported: - **hcl/\#t60\_ati\_intel** + **hcl/#t60\_ati\_intel** - **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) - - See **hcl/\#macbook11**. + - See **hcl/#macbook11**. - **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - - See **hcl/\#macbook21**. + - See **hcl/#macbook21**. Changes for this release (latest changes first, earliest changes last) ---------------------------------------------------------------------- @@ -566,22 +566,22 @@ New systems supported in this release: - **Lenovo ThinkPad X60 Tablet** (1024x768 and 1400x1050) with digitizer support - - See **hcl/\#supported\_x60t\_list** for list of supported LCD + - See **hcl/#supported\_x60t\_list** for list of supported LCD panels - It is unknown whether an X61 Tablet can have its mainboard replaced with an X60 Tablet motherboard. - **Lenovo ThinkPad T60** (Intel GPU) (there are issues; see below) - See notes below for exceptions, and - **hcl/\#supported\_t60\_list** for known working LCD panels. + **hcl/#supported\_t60\_list** for known working LCD panels. - It is unknown whether a T61 can have its mainboard replaced with a T60 motherboard. - T60P (and T60s with ATI GPU) will likely never be supported: - **hcl/\#t60\_ati\_intel** + **hcl/#t60\_ati\_intel** - **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) - - See **hcl/\#macbook11**. + - See **hcl/#macbook11**. - **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - - See **hcl/\#macbook21**. + - See **hcl/#macbook21**. Machines no longer supported (compared to previous release): ------------------------------------------------------------ @@ -620,8 +620,8 @@ Revisions for r20140903 (6th beta) (3rd September 2014) buildpac* scripts for Parabola users. - Documentation: added information showing how to enable or disable bluetooth on the X60 -- MacBook1,1 tested! See **hcl/\#macbook11** -- Documentation: fixed typo in \#get\_edid\_panelname (get-edit +- MacBook1,1 tested! See **hcl/#macbook11** +- Documentation: fixed typo in #get\_edid\_panelname (get-edit changed to get-edid) - Documentation: added images/x60\_lcd\_change/ (pics only for now) - Added gcry\_serpent and gcry\_whirlpool to the GRUB module list in @@ -660,7 +660,7 @@ Revisions for r20140903 (6th beta) (3rd September 2014) - Removed grub\_serial*.cfg and libreboot\_serial*.rom, all configs/rom files are now unified (containing same configuration as serial rom files from before). - - Documentation: updated \#rom to reflect the above. + - Documentation: updated #rom to reflect the above. - Updated GRUB to new version from August 14th, 2014. - Unified all grub configurations for all systems to a single grub.cfg under resources/grub/config/ @@ -695,12 +695,12 @@ Revisions for r20140903 (6th beta) (3rd September 2014) manifests (not needed, since release tarballs are GPG-signed) - 'build' script: removed the parts that generated libreboot\_meta directory (not needed anymore, since \_meta will be hosted in git) - - Updated \#build\_meta (and other parts of documentation) to + - Updated #build\_meta (and other parts of documentation) to accomodate this change. -- Documentation: simplified (refactored) the notes in \#rom +- Documentation: simplified (refactored) the notes in #rom - 'build' script: removed the parts that generated libreboot\_bin and added them to a new script: 'build-release' - - Documentation: \#build updated to reflect the above. + - 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 @@ -715,7 +715,7 @@ Revisions for r20140903 (6th beta) (3rd September 2014) buildpac ( updated accordingly) - Renamed buildpac to deps-parabola ( updated accordingly) - Documentation: removed all parts talking about build dependencies, - replaced them with links to \#build\_dependencies + replaced them with links to #build\_dependencies - Documentation: emphasized more strongly on the documentation, the need to re-build bucts and/or flashrom before flashing a ROM image. - build-release: flashrom, nvramtool, cbfstool and bucts are no longer @@ -731,7 +731,7 @@ Revisions for r20140903 (6th beta) (3rd September 2014) - Removed all unused fonts from dejavu-fonts-ttf-2.34/ directory - 'buildrom-withgrub' script: updated it to create 2 sets of ROMs for each system: one with text-mode, one with coreboot framebuffer. -- Documentation: updated \#rom to reflect the above +- Documentation: updated #rom to reflect the above - Deleted unused README and COPYING file from main directory - Removed some rm -Rf .git* instructions from the get* scripts and moved them to build-release script @@ -789,7 +789,7 @@ Revisions for r20140811 (5th beta) (11th August 2014) - Documentation: added preliminary information about preventing/mitigating cold-boot attack in x60\_security.html and t60\_security.html -- Documentation: added info to \#macbook21 warning about issues with +- Documentation: added info to #macbook21 warning about issues with macbook21 - Documentation: X60/T60: added information about checking custom ROMs using dd to see whether or not the top 64K region is duplicated @@ -874,7 +874,7 @@ Revisions for r20140720 (3rd beta) (20th July 2014) background. - Updated resources/grub/config/{x60,t60,x60t}/grub*cfg to use background.jpg background. -- Documentation: updated docs/\#grub\_custom\_keyboard to be more +- Documentation: updated docs/#grub\_custom\_keyboard to be more generally useful. - nvramtool: - Updated builddeps-coreboot script to build it @@ -918,7 +918,7 @@ Revisions for r20140711 (1st beta) (11th July 2014) (macbook21 does not need bucts when flashing libreboot while Apple EFI firmware is running) - Documentation: Added macbook21 ROMs to the list of ROMs in - docs/\#rom + docs/#rom - Documentation: Write documentation linking to Mono Moosbart's macbook21 and parabola page (and include a copy) - Documentation: added a copy of Mono's Parabola install guide (for @@ -960,8 +960,8 @@ Revisions for r20140711 (1st beta) (11th July 2014) 'dmidecode') - Added 'build-x60t' script - Updated 'build' script to use 'build-x60t' - - Documentation: added to \#config section the section - \#config\_x60t (libreboot configuration and dmidecode info) + - Documentation: added to #config section the section + #config\_x60t (libreboot configuration and dmidecode info) - Documentation: added x60t ROMs to the list of ROMs - Tidied up the 'builddeps' script (easier to read) - Tidied up the 'cleandeps' script (easier to read) @@ -1113,7 +1113,7 @@ Revisions for r20140711 (1st beta) (11th July 2014) - Deleted the RELEASE and BACKPORT files (no longer needed) - Documentation: added information about X60/T60 dock (ultrabase x6 and advanced mini dock) to relevant sections. - - Added to docs/\#serial + - Added to docs/#serial [Back to top of page.](#pagetop) diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md index b442d49e..bf364dcb 100644 --- a/docs/bsd/freebsd.md +++ b/docs/bsd/freebsd.md @@ -92,12 +92,12 @@ Check lsblk to confirm which drive it is:\ Check that it wasn't automatically mounted. If it was, unmount it. For example:\ $ sudo umount /dev/sdX* -**\# 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** +**# 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. diff --git a/docs/bsd/netbsd.md b/docs/bsd/netbsd.md index 92204878..7d107c44 100644 --- a/docs/bsd/netbsd.md +++ b/docs/bsd/netbsd.md @@ -88,12 +88,12 @@ Check lsblk to confirm which drive it is:\ Check that it wasn't automatically mounted. If it was, unmount it. For example:\ $ sudo umount /dev/sdX* -**\# 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** +**# 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. diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md index fdfd99d2..93ed01e7 100644 --- a/docs/bsd/openbsd.md +++ b/docs/bsd/openbsd.md @@ -87,12 +87,12 @@ Check lsblk to confirm which drive it is:\ Check that it wasn't automatically mounted. If it was, unmount it. For example:\ $ sudo umount /dev/sdX* -**\# 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** +**# 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. diff --git a/docs/depthcharge/index.md b/docs/depthcharge/index.md index c9682847..d4f7f9f6 100644 --- a/docs/depthcharge/index.md +++ b/docs/depthcharge/index.md @@ -188,26 +188,26 @@ The following parameters can be configured: - Kernels signature verification: - Enabled with:\ - \# **crossystem dev\_boot\_signed\_only=1** + # **crossystem dev\_boot\_signed\_only=1** - Disabled with:\ - \# **crossystem dev\_boot\_signed\_only=0** + # **crossystem dev\_boot\_signed\_only=0** - External media boot: - Enabled with:\ - \# **crossystem dev\_boot\_usb=1** + # **crossystem dev\_boot\_usb=1** - Disabled with:\ - \# **crossystem dev\_boot\_usb=0** + # **crossystem dev\_boot\_usb=0** - Legacy payload boot: - Enabled with:\ - \# **crossystem dev\_boot\_legacy=1** + # **crossystem dev\_boot\_legacy=1** - Disabled with:\ - \# **crossystem dev\_boot\_legacy=0** + # **crossystem dev\_boot\_legacy=0** - Default boot medium: - Internal storage:\ - \# **crossystem dev\_default\_boot=disk** + # **crossystem dev\_default\_boot=disk** - External media:\ - \# **crossystem dev\_default\_boot=usb** + # **crossystem dev\_default\_boot=usb** - Legacy payload:\ - \# **crossystem dev\_default\_boot=legacy** + # **crossystem dev\_default\_boot=legacy** diff --git a/docs/future/index.md b/docs/future/index.md index d4959d81..94453e55 100644 --- a/docs/future/index.md +++ b/docs/future/index.md @@ -114,7 +114,7 @@ LCD panels on i945 - fix incompatible panels {#lcd_i945_incompatibility} ============================================ Fix T60 issues (see incompatible panels listed at -[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list)). +[../hcl/#supported\_t60\_list](../hcl/#supported_t60_list)). Run that tool (resources/utilities/i945gpu/intel-regs.py) as root on systems with the offending panels in: @@ -160,12 +160,12 @@ working and nonworking panels. How to dump EDID: -\# apt-get install i2c-tools -\# modprobe i2c-dev + # apt-get install i2c-tools + # modprobe i2c-dev Find out the correct ID to use:\ -\# i2cdetect -l + # i2cdetect -l Example:\ -\# **i2cdump -y 2 0x50** +# **i2cdump -y 2 0x50** Working panel: EDID dump from LG-Philips LP150E05-A2K1: @@ -260,42 +260,42 @@ You are supposed to: With each boot, make notes about what you see and get logs using the [standard test](#standard_test). You will need the files from -[\#intelvbttool\_results](#intelvbttool_results) for each system. +[#intelvbttool\_results](#intelvbttool_results) for each system. -Results (\# means untested): +Results (# means untested): - **X60/X60s:** - - TMD-Toshiba LTD121ECHB: \# - - CMO N121X5-L06: \# - - Samsung LTN121XJ-L07: \# - - BOE-Hydis HT121X01-101: \# + - TMD-Toshiba LTD121ECHB: # + - CMO N121X5-L06: # + - Samsung LTN121XJ-L07: # + - BOE-Hydis HT121X01-101: # - **X60T XGA:** - - BOE-Hydis HV121X03-100: \# + - BOE-Hydis HV121X03-100: # - **X60T SXGA+:** - - BOE-Hydis HV121P01-100: \# + - BOE-Hydis HV121P01-100: # - **T60 14" XGA:** - - Samsung LTN141XA-L01: \# - - CMO N141XC: \# - - BOE-Hydis HT14X14: \# - - TMD-Toshiba LTD141ECMB: \# + - Samsung LTN141XA-L01: # + - CMO N141XC: # + - BOE-Hydis HT14X14: # + - TMD-Toshiba LTD141ECMB: # - **T60 14" SXGA+** - - TMD-Toshiba LTD141EN9B: \# - - Samsung LTN141P4-L02: \# - - Boe-Hydis HT14P12: \# + - TMD-Toshiba LTD141EN9B: # + - Samsung LTN141P4-L02: # + - Boe-Hydis HT14P12: # - **T60 15" XGA** - - Samsung LTN150XG-L08: \# - - LG-Philips LP150X09: \# - - 13N7068 (IDtech): \# - - 13N7069 (CMO): \# + - Samsung LTN150XG-L08: # + - LG-Philips LP150X09: # + - 13N7068 (IDtech): # + - 13N7069 (CMO): # - **T60 15" SXGA+** - - LG-Philips LP150E05-A2K1: \# - - BOE-Hydis HV150P01-100: \# + - LG-Philips LP150E05-A2K1: # + - BOE-Hydis HV150P01-100: # - **T60 15" UXGA** - - BOE-Hydis HV150UX1-100: \# - - IDTech N150U3-L01: \# - - BOE-Hydis HV150UX1-102: \# + - BOE-Hydis HV150UX1-100: # + - IDTech N150U3-L01: # + - BOE-Hydis HV150UX1-102: # - **T50 15" QXGA** - - IDtech IAQX10N: \# - - IDtech IAQX10S: \# + - IDtech IAQX10N: # + - IDtech IAQX10S: # @@ -330,45 +330,45 @@ Then do (and record the output):\ Backup both files (runningvga.bin and intelvbttool\_out), renaming them to match the system and LCD panel used. -[../misc/\#get\_edid\_panelname](../misc/#get_edid_panelname) will show +[../misc/#get\_edid\_panelname](../misc/#get_edid_panelname) will show you how to get the name (model) of the LCD panel used. -Test results (\# means untested and all had docks, unless noted). +Test results (# means untested and all had docks, unless noted). ----------------------------------------------------------------- - **X60/X60s:** - - TMD-Toshiba LTD121ECHB: \# - - CMO N121X5-L06: \# - - Samsung LTN121XJ-L07: \# - - BOE-Hydis HT121X01-101: \# + - TMD-Toshiba LTD121ECHB: # + - CMO N121X5-L06: # + - Samsung LTN121XJ-L07: # + - BOE-Hydis HT121X01-101: # - **X60T XGA (1024x768):** - - BOE-Hydis HV121X03-100: \# + - BOE-Hydis HV121X03-100: # - **X60T SXGA+ (1400x1050):** - - BOE-Hydis HV121P01-100: \# + - BOE-Hydis HV121P01-100: # - **T60 14" XGA (1024x768):** - - Samsung LTN141XA-L01: \# - - CMO N141XC: \# - - BOE-Hydis HT14X14: \# - - TMD-Toshiba LTD141ECMB: \# + - Samsung LTN141XA-L01: # + - CMO N141XC: # + - BOE-Hydis HT14X14: # + - TMD-Toshiba LTD141ECMB: # - **T60 14" SXGA+ (1400x1050):** - - TMD-Toshiba LTD141EN9B: \# - - Samsung LTN141P4-L02: \# - - Boe-Hydis HT14P12: \# + - TMD-Toshiba LTD141EN9B: # + - Samsung LTN141P4-L02: # + - Boe-Hydis HT14P12: # - **T60 15" XGA (1024x768):** - - Samsung LTN150XG-L08: \# - - LG-Philips LP150X09: \# - - 13N7068 (IDtech): \# - - 13N7069 (CMO): \# + - Samsung LTN150XG-L08: # + - LG-Philips LP150X09: # + - 13N7068 (IDtech): # + - 13N7069 (CMO): # - **T60 15" SXGA+ (1400x1050):** - - LG-Philips LP150E05-A2K1: \# - - BOE-Hydis HV150P01-100: \# + - LG-Philips LP150E05-A2K1: # + - BOE-Hydis HV150P01-100: # - **T60 15" UXGA (1600x1200):** - - BOE-Hydis HV150UX1-100: \# - - IDTech N150U3-L01: \# - - BOE-Hydis HV150UX1-102: \# + - BOE-Hydis HV150UX1-100: # + - IDTech N150U3-L01: # + - BOE-Hydis HV150UX1-102: # - **T60 15" QXGA (2048x1536):** - - IDtech IAQX10N: \# - - IDtech IAQX10S: \# + - IDtech IAQX10N: # + - IDtech IAQX10S: # [Back to top of page.](#pagetop) diff --git a/docs/future/old.md b/docs/future/old.md index 95088d38..e834ad51 100644 --- a/docs/future/old.md +++ b/docs/future/old.md @@ -29,7 +29,7 @@ X60 native graphics initialization (with backlight controls) {#x60_native_notes} **This is now obsolete. A better way was found (included in libreboot): <http://review.coreboot.org/#/c/6731/>** -***Also check [\#5320\_kernel312fix](#5320_kernel312fix) (to fix 3D on +***Also check [#5320\_kernel312fix](#5320_kernel312fix) (to fix 3D on kernel 3.12/higher)*** **The fix below was done on 5320/6 (from review.coreboot.org) but should @@ -46,13 +46,13 @@ That's all! **This has also been backported into libreboot 5th release 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** +**# devmem2 0xe4361254 w** The change is also included in libreboot 6. When doing this, it gave back that value. The same trick was used to get backlight controls for T60 (see -[\#t60\_native\_notes](#t60_native_notes)). +[#t60\_native\_notes](#t60_native_notes)). Further notes ------------- @@ -91,7 +91,7 @@ to calculate it without hardcoded laptop-specific values. Therefore, I am supposed to find out the 'display core frequency' (mtjm says there might be a register for it; also, it might be in 5320 or the replay code) and the PWM modulation frequency. -https://en.wikipedia.org/wiki/Backlight\#Flicker\_due\_to\_backlight\_dimming +https://en.wikipedia.org/wiki/Backlight#Flicker\_due\_to\_backlight\_dimming phcoder (Vladimir Serbinenko) who is author of 5320 (review.coreboot.org) talks about 'duty cycle limit' and 'flickering @@ -106,7 +106,7 @@ T60 native graphics initialization (with backlight controls) {#t60_native_notes} **This is now obsolete. A better way was found (included in libreboot): <http://review.coreboot.org/#/c/6731/>** -***Also check [\#5320\_kernel312fix](#5320_kernel312fix) (to fix 3D on +***Also check [#5320\_kernel312fix](#5320_kernel312fix) (to fix 3D on kernel 3.12/higher)*** **The fix below was done on an earlier version of 5345 changeset @@ -117,15 +117,15 @@ included in libreboot 6** change **gpu\_backlight** to **0x58BF58BE** Hold on! Check -[../misc/\#get\_edid\_panelname](../misc/#get_edid_panelname) to know +[../misc/#get\_edid\_panelname](../misc/#get_edid_panelname) to know what LCD panel you have. This is important for the next step! Supported panels ---------------- -[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list). +[../hcl/#supported\_t60\_list](../hcl/#supported_t60_list). -See [\#lcd\_i945\_incompatibility](./#lcd_i945_incompatibility). +See [#lcd\_i945\_incompatibility](./#lcd_i945_incompatibility). @@ -144,7 +144,7 @@ is also now included in libreboot 6 (using the proper way, not the now obsolete. This needs to be re-done for the latest version of 5320. The fix below is (in practise) only for reference, therefore.** -See [\#x60\_cb5927\_testing](#x60_cb5927_testing) for the original (and +See [#x60\_cb5927\_testing](#x60_cb5927_testing) for the original (and current) fix, for the replay code. Now we want to implement that on top of <http://review.coreboot.org/#/c/5320> which is the current code for native graphics initialization on i945. diff --git a/docs/git/index.md b/docs/git/index.md index 2ab88eeb..11ecc0ff 100644 --- a/docs/git/index.md +++ b/docs/git/index.md @@ -33,13 +33,13 @@ statically compiled executables for the utilities are included.** For Debian Stretch (may also work on Debian Jessie), you can run the following command:\ -$ sudo ./oldbuild dependencies debian + $ sudo ./oldbuild dependencies debian (this will also work in Devuan) For Parabola, you can run the following command:\ -$ sudo ./oldbuild dependencies parabola + $ sudo ./oldbuild dependencies parabola or:\ -\# **./oldbuild dependencies parabola** +# **./oldbuild dependencies parabola** For other GNU+Linux distributions, you can adapt the existing scripts. @@ -63,17 +63,17 @@ 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 + $ 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 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:\ @@ -83,7 +83,7 @@ What this did was download everything (grub, coreboot, memtest86+, bucts, flashrom) at the versions last tested for this release, and patch them. Read the script in a text editor to learn more. -To build the ROM images, see [\#build](#build). +To build the ROM images, see [#build](#build). [Back to top of page.](#pagetop) @@ -105,7 +105,7 @@ file*. This corresponds to the final two 64K regions in the flash chip. Lenovo BIOS will prevent you from writing the final one, so running "**bucts 1**" will set the system to boot from the other block instead (which is writeable along with everything beneath it when using a -patched flashrom. see [\#build\_flashrom](#build_flashrom)). After +patched flashrom. see [#build\_flashrom](#build_flashrom)). After shutting down and booting up after the first flash of libreboot, the final 64K block is writeable so you flash the ROM again with an unpatched flashrom and run "**bucts 0**" to make the system boot from @@ -123,7 +123,7 @@ 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 +**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 @@ -156,7 +156,7 @@ 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 +**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 @@ -211,7 +211,7 @@ 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\_meta](#build_meta). Build all of the components used in libreboot:\ $ **./oldbuild module all** @@ -221,12 +221,12 @@ modulename*. To see the possible values for *modulename*, use:\ $ **./oldbuild module list** After that, build the ROM images (for all boards):\ -$ ./oldbuild roms withgrub + $ ./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 + $ ./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/**. @@ -304,7 +304,7 @@ libreboot\_util, for: 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 flashrom static $ **./oldbuild module bucts static** The same conditions as above apply for ARM (except, building bucts on @@ -315,7 +315,7 @@ restrictions). The command that you used for generating the release archives will also run the following command:\ -$ ./oldbuild release tobuild + $ ./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. diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md index 76870bda..23e22d19 100644 --- a/docs/gnulinux/configuring_parabola.md +++ b/docs/gnulinux/configuring_parabola.md @@ -97,9 +97,9 @@ careful about this when reading anything on the Arch wiki. Some of these steps require internet access. I'll go into networking later but for now, I just connected my system to a switch and did:\ -\# systemctl start dhcpcd.service + # systemctl start dhcpcd.service You can stop it later by running:\ -\# systemctl stop dhcpcd.service + # 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) @@ -129,12 +129,12 @@ 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 + # 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** +# **pacman -Syu** **Before installing packages with 'pacman -S', always update first, using the notes above.** @@ -156,7 +156,7 @@ work. The Arch forum can also be useful, if others have the same issue as you (if you encounter issues, that is). The *Parabola* IRC channel -(\#parabola on freenode) can also help you. +(#parabola on freenode) can also help you. Due to this and the volatile nature of Parabola/Arch, you should only update when you have at least a couple hours of spare time in case of @@ -199,7 +199,7 @@ old package information, updated automatically when you do anything in pacman).** To clean out all old packages that are cached:\ -\# **pacman -Sc** +# **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 @@ -208,7 +208,7 @@ 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 + # 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. @@ -254,9 +254,9 @@ 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* + # useradd -m -G wheel -s /bin/bash *yourusername* Set a password:\ -\# **passwd *yourusername*** +# **passwd *yourusername*** Use of the *diceware method* is recommended, for generating secure passphrases (instead of passwords). @@ -282,7 +282,7 @@ the background behind the decision by Arch (Parabola's upstream supplier) to use systemd. The manpage should also help:\ -\# man systemd + # man systemd The section on 'unit types' is especially useful. According to the wiki, systemd 'journal' keeps logs of a size up to @@ -293,7 +293,7 @@ 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=*\ +*#SystemMaxUse=*\ Change it to say:\ *SystemMaxUse=50M* @@ -302,7 +302,7 @@ The wiki also recommended a method for forwarding journal output to TTY to switch between terminals). I decided not to enable it. Restart journald:\ -\# **systemctl restart systemd-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 @@ -313,9 +313,9 @@ delete older records when the journal size reaches it's limit Finally, the wiki mentions 'temporary' files and the utility for managing them.\ -\# man systemd-tmpfiles + # man systemd-tmpfiles The command for 'clean' is:\ -\# systemd-tmpfiles \--clean + # 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 @@ -325,7 +325,7 @@ 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 + # 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 @@ -349,10 +349,10 @@ and below the 'extra' section add:\ Include = /etc/pacman.d/mirrorlist* Now sync with the repository:\ -\# **pacman -Syy** +# **pacman -Syy** List all available packages in this repository:\ -\# **pacman -Sl kernels** +# **pacman -Sl kernels** In the end, I decided not to install anything from it but I kept the repository enabled regardless. @@ -373,12 +373,12 @@ Read <https://wiki.archlinux.org/index.php/Configuring_Network>. This should be the same as the hostname that you set in /etc/hostname when installing Parabola. You can also do it with systemd (do so now, if you like):\ -\# hostnamectl set-hostname *yourhostname* + # 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** + # 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\ @@ -400,7 +400,7 @@ According to the Arch wiki, 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** +# **lspci -v** Look at the remaining sections *'Kernel driver in use'* and *'Kernel modules'*. In my case it was as follows:\ @@ -409,7 +409,7 @@ Kernel modules: e1000e* Check that the driver was loaded by issuing *dmesg | grep module\_name*. In my case, I did:\ -\# **dmesg | grep e1000e** +# **dmesg | grep e1000e** ### Network device names {#network_devicenames} @@ -431,7 +431,7 @@ For background information, read [Predictable Network Interface Names](http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/) Show device names:\ -\# **ls /sys/class/net** +# **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> @@ -463,7 +463,7 @@ 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 + # pacman -S smartmontools Read <https://wiki.archlinux.org/index.php/S.M.A.R.T.> to learn how to use it. @@ -488,36 +488,36 @@ provide LXDE by default. Based on <https://wiki.archlinux.org/index.php/Xorg>. Firstly, install it!\ -\# pacman -S xorg-server + # pacman -S xorg-server I also recommend installing this (contains lots of useful tools, including *xrandr*):\ -\# **pacman -S xorg-server-utils** +# **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 + # pacman -S xf86-video-intel For other systems you can try:\ -\# pacman -Ss xf86-video- | less + # 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 + # 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** +# **pacman -S xorg-xinit** <optional>\    Arch wiki recommends installing these, for testing that X works:\ -   \# pacman -S xorg-twm xorg-xclock xterm +   # pacman -S xorg-twm xorg-xclock xterm    Refer to <https://wiki.archlinux.org/index.php/Xinitrc>. and test X:\ -   \# startx +   # startx    When you are satisfied, type ***exit*** in xterm, inside the X session.\ -   Uninstall them (clutter. eww): \# **pacman -S xorg-xinit xorg-twm +   Uninstall them (clutter. eww): # **pacman -S xorg-xinit xorg-twm xorg-xclock xterm**\ </optional> @@ -536,7 +536,7 @@ 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** +# **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. @@ -583,27 +583,27 @@ would like to try something different, refer to Refer to <https://wiki.archlinux.org/index.php/LXDE>. Install it, choosing 'all' when asked for the default package list:\ -\# **pacman -S lxde obconf** +# **pacman -S lxde obconf** I didn't want the following, so I removed them:\ -\# **pacman -R lxmusic lxtask** +# **pacman -R lxmusic lxtask** I also lazily installed all fonts:\ -\# **pacman -S $(pacman -Ssq ttf-)** +# **pacman -S $(pacman -Ssq ttf-)** And a mail client:\ -\# **pacman -S icedove** +# **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** +# **pacman -S xsensors stress htop** Enable LXDM (the default display manager, providing a graphical login):\ -\# systemctl enable lxdm.service + # systemctl enable lxdm.service It will start when you boot up the system. To start it now, do:\ -\# **systemctl start lxdm.service** +# **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 @@ -611,15 +611,15 @@ start lxde without lxdm. Read <https://wiki.archlinux.org/index.php/Xinitrc>. Open LXterminal:\ -$ cp /etc/skel/.xinitrc \~ + $ 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\ +*# 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\ +# Start lxde desktop\ exec startlxde\ * Now make sure that it is executable:\ $ **chmod +x .xinitrc** @@ -648,7 +648,7 @@ NOTE TO SELF: come back to this later. ### LXDE - screenlock {#lxde_screenlock} Arch wiki recommends to use *xscreensaver*:\ -\# **pacman -S xscreensaver** +# **pacman -S xscreensaver** Under *Preferences :: Screensaver* in the LXDE menu, I chose *Mode: Blank Screen Only*, setting *Blank After*, *Cycle After* and *Lock @@ -699,30 +699,30 @@ 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** +# **pacman -S networkmanager** You will also want the graphical applet:\ -\# pacman -S network-manager-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** +# **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 + # pacman -S xfce4-notifyd gnome-icon-theme Also, for storing authentication details (wifi) I need:\ -\# **pacman -S gnome-keyring** +# **pacman -S gnome-keyring** I wanted to quickly enable networkmanager:\ -\# systemctl stop dhcpcd -\# systemctl start NetworkManager + # systemctl stop dhcpcd + # systemctl start NetworkManager Enable NetworkManager at boot time:\ -\# **systemctl enable NetworkManager** +# **systemctl enable NetworkManager** Restart LXDE (log out, and then log back in). diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index f04b969a..36a60c61 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -71,12 +71,12 @@ article](https://wiki.archlinux.org/index.php/Solid_State_Drives). Edit 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 + # 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** +# **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 @@ -85,7 +85,7 @@ 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 + # 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). @@ -96,8 +96,8 @@ 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 + # localectl list-keymaps + # loadkeys LAYOUT For me, LAYOUT would have been dvorak-uk. @@ -125,7 +125,7 @@ dm-mod device-mapper will be used - a lot. Make sure that the kernel module is loaded:\ -\# **modprobe dm-mod** +# **modprobe dm-mod** Create LUKS partition --------------------- @@ -139,7 +139,7 @@ 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** +# **cfdisk /dev/sda** I create a single large sda1 filling the whole drive, leaving it as the default type 'Linux' (83). @@ -152,15 +152,15 @@ I am then directed to Parabola forces you to RTFM. Do that. It tells me to run:\ -\# **cryptsetup benchmark** (for making sure the list below is +# **cryptsetup benchmark** (for making sure the list below is populated)\ Then:\ -\# cat /proc/crypto + # 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** +# **man cryptsetup** Following that page, based on my requirements, I do the following based on @@ -169,7 +169,7 @@ 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 +# **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 @@ -187,29 +187,29 @@ Create LVM Now I refer to <https://wiki.archlinux.org/index.php/LVM>. Open the LUKS partition:\ -\# cryptsetup luksOpen /dev/sda1 lvm + # cryptsetup luksOpen /dev/sda1 lvm (it will be available at /dev/mapper/lvm) Create LVM partition:\ -\# pvcreate /dev/mapper/lvm + # pvcreate /dev/mapper/lvm Show that you just created it:\ -\# **pvdisplay** +# **pvdisplay** Now I create the volume group, inside of which the logical volumes will be created:\ -\# vgcreate matrix /dev/mapper/lvm + # vgcreate matrix /dev/mapper/lvm (volume group name is 'matrix' - choose your own name, if you like) Show that you created it:\ -\# **vgdisplay** +# **vgdisplay** Now create the logical volumes:\ -\# **lvcreate -L 2G matrix -n swapvol** (2G swap partition, named +# **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 +# **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 @@ -219,7 +219,7 @@ system (typical use case), a root and a swap will do (really). Verify that the logical volumes were created, using the following command:\ -\# **lvdisplay** +# **lvdisplay** @@ -227,15 +227,15 @@ Create / and swap partitions, and mount --------------------------------------- For the swapvol LV I use:\ -\# mkswap /dev/mapper/matrix-swapvol + # mkswap /dev/mapper/matrix-swapvol Activate swap:\ -\# **swapon /dev/matrix/swapvol** +# **swapon /dev/matrix/swapvol** For the root LV I use:\ -\# **mkfs.btrfs /dev/mapper/matrix-root** +# **mkfs.btrfs /dev/mapper/matrix-root** Mount the root (/) partition:\ -\# **mount /dev/matrix/root /mnt** +# **mount /dev/matrix/root /mnt** @@ -250,8 +250,8 @@ Now I am following the rest of referenced <https://wiki.archlinux.org/index.php/Installation_guide>. Create /home and /boot on root mountpoint:\ -\# mkdir -p /mnt/home -\# **mkdir -p /mnt/boot** + # 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. @@ -259,9 +259,9 @@ 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, + # 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. @@ -272,23 +272,23 @@ 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 +   # 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 +   # 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 +   # 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\] +   # date MMDDhhmm\[\[CC\]YY\]\[.ss\]    I also had to install:\ -   \# pacman -S archlinux-keyring -   \# pacman-key \--populate archlinux +   # 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. @@ -296,13 +296,13 @@ 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 +   # 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 +# **pacstrap /mnt base base-devel wpa\_supplicant dialog iw wpa\_actiond** @@ -313,21 +313,21 @@ 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 + # genfstab -U -p /mnt >> /mnt/etc/fstab Check the created file:\ -\# cat /mnt/etc/fstab + # 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** +# **arch-chroot /mnt /bin/bash** It's a good idea to have this installed:\ -\# **pacman -S linux-libre-lts** +# **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** +# **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 @@ -335,35 +335,35 @@ 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** +# **pacman -S wget** Locale:\ -\# vi /etc/locale.gen + # 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** + # 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 + # vi /etc/vconsole.conf In my case: KEYMAP=dvorak-uk FONT=lat9w-16 Time zone:\ -\# ln -s /usr/share/zoneinfo/Europe/London /etc/localtime + # 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** +# **hwclock \--systohc \--utc** Hostname: Write your hostname to /etc/hostname. For example, if your hostname is parabola:\ -\# echo parabola > /etc/hostname + # echo parabola > /etc/hostname Add the same hostname to /etc/hosts:\ -\# vi /etc/hosts + # vi /etc/hosts #<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost parabola @@ -375,9 +375,9 @@ Configure the network: Refer to Mkinitcpio: Configure /etc/mkinitcpio.conf as needed (see <https://wiki.parabola.nu/Mkinitcpio>). Runtime modules can be found in /usr/lib/initcpio/hooks, and build hooks can be found in -/usr/lib/initcpio/install. (\# **mkinitcpio -H hookname** gives +/usr/lib/initcpio/install. (# **mkinitcpio -H hookname** gives information about each hook.) Specifically, for this use case:\ -\# vi /etc/mkinitcpio.conf + # vi /etc/mkinitcpio.conf Then modify the file like so: - MODULES="i915" @@ -402,18 +402,18 @@ Then modify the file like so: Now using mkinitcpio, you can create the kernel and ramdisk for booting with (this is different from Arch, specifying linux-libre instead of linux):\ -\# mkinitcpio -p linux-libre + # mkinitcpio -p linux-libre Also do it for linux-libre-lts:\ -\# mkinitcpio -p linux-libre-lts + # mkinitcpio -p linux-libre-lts Also do it for linux-libre-grsec:\ -\# **mkinitcpio -p 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 + # vi /etc/pam.d/passwd Add rounds=65536 at the end of the uncommented 'password' line.\ -\# passwd root + # passwd root Make sure to set a secure password! Also, it must never be the same as your LUKS password. @@ -428,17 +428,17 @@ Extra security tweaks Based on <https://wiki.archlinux.org/index.php/Security>. Restrict access to important directories:\ -\# **chmod 700 /boot /etc/{iptables,arptables}** +# **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*\ +*# 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 +# **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. @@ -452,20 +452,20 @@ Unmount, reboot! ---------------- Exit from chroot:\ -\# **exit** +# **exit** unmount:\ -\# umount -R /mnt -\# **swapoff -a** + # umount -R /mnt +# **swapoff -a** deactivate the lvm lv's:\ -\# lvchange -an /dev/matrix/root -\# lvchange -an /dev/matrix/swapvol + # lvchange -an /dev/matrix/root + # lvchange -an /dev/matrix/swapvol Lock the encrypted partition (close it):\ -\# **cryptsetup luksClose lvm** +# **cryptsetup luksClose lvm** -\# shutdown -h now + # shutdown -h now Remove the installation media, then boot up again. @@ -521,14 +521,14 @@ 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 + # 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 + $ ./cbfstool libreboot.rom print Extract grubtest.cfg:\ -$ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg + $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg And modify:\ $ **vi grubtest.cfg** @@ -559,18 +559,18 @@ 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 + $ ./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 + # ./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 + # ./flash forceupdate libreboot.rom You should see "Verifying flash\... VERIFIED." written at the end of the flashrom output. @@ -601,21 +601,21 @@ $ **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 + $ ./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 + $ ./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 + # ./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** +# **pacman -R grub** @@ -637,20 +637,20 @@ 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 +# **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 + # 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" + # FILES="/etc/mykeyfile" Create the initramfs image from scratch:\ -\# mkinitcpio -p linux-libre -\# mkinitcpio -p linux-libre-lts -\# mkinitcpio -p linux-libre-grsec + # 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 + # cryptkey=rootfs:/etc/mykeyfile \ You can also place this inside the grub.cfg that exists in CBFS: [grub\_cbfs.html](grub_cbfs.html). diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md index 592b20f7..8fa8dcb6 100644 --- a/docs/gnulinux/grub_boot_installer.md +++ b/docs/gnulinux/grub_boot_installer.md @@ -38,12 +38,12 @@ Check lsblk to confirm which drive it is:\ Check that it wasn't automatically mounted. If it was, unmount it. For example:\ $ sudo umount /dev/sdX* -**\# 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** +**# 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. diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md index 9eb55c27..7b7c4cf3 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -52,7 +52,7 @@ Introduction Download the latest release from <http://libreboot.org/>\ **If you downloaded from git, refer to -[../git/\#build\_meta](../git/#build_meta) before continuing.** +[../git/#build\_meta](../git/#build_meta) before continuing.** [Back to top of page.](#pagetop) @@ -94,8 +94,8 @@ coreboot payload) that is located in a partition on the main storage. If you want to adapt a copy of the existing *libreboot* GRUB configuration and use that for the libreboot\_grub.cfg file, then follow -[\#tools](#tools), [\#rom](#rom) and -[\#extract\_testconfig](#extract_testconfig) to get the +[#tools](#tools), [\#rom](#rom) and +[#extract\_testconfig](#extract_testconfig) to get the ***grubtest.cfg***. Rename ***grubtest.cfg*** to ***libreboot\_grub.cfg*** and save it to ***/boot/grub/*** on the running system where it is intended to be used. Modify the file at that @@ -123,9 +123,9 @@ 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 +[../git/#build\_flashrom](../git/#build_flashrom)). Flashrom is also available from the repositories:\ -\# **pacman -S flashrom** +# **pacman -S flashrom** [Back to top of page.](#pagetop) @@ -141,11 +141,11 @@ 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 + $ 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** +# **flashrom -c MX25L6405 -p internal -r libreboot.rom** [Back to top of page.](#pagetop) @@ -191,13 +191,13 @@ Testing ------- **Now you have a modified ROM. Refer back to -[../install/\#flashrom](../install/#flashrom) for information on how to +[../install/#flashrom](../install/#flashrom) for information on how to flash it.\ -$ cd /libreboot\_util** \# **./flash update libreboot.rom + $ 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 + # ./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.** @@ -236,7 +236,7 @@ Add the modified version that you just made:\ **$ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw** **Now you have a modified ROM. Again, refer back to -[../install/\#flashrom](../install/#flashrom) for information on how to +[../install/#flashrom](../install/#flashrom) for information on how to flash it. It's the same method as you used before. Shut down and then boot up with your new configuration.** diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md index 26de1399..cad4ca40 100644 --- a/docs/gnulinux/grub_hardening.md +++ b/docs/gnulinux/grub_hardening.md @@ -36,7 +36,7 @@ image: Helpful links: - [GRUB manual - \#security](https://www.gnu.org/software/grub/manual/html_node/Security.html#Security) + #security](https://www.gnu.org/software/grub/manual/html_node/Security.html#Security) - [GRUB info pages](http://git.savannah.gnu.org/cgit/grub.git/tree/docs/grub.texi) - [SATA connected storage considered dangerous until proven diff --git a/docs/hardware/t60_lcd_15.md b/docs/hardware/t60_lcd_15.md index 4d97eb4d..edb41173 100644 --- a/docs/hardware/t60_lcd_15.md +++ b/docs/hardware/t60_lcd_15.md @@ -34,11 +34,11 @@ 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)):\ +[../hcl/#supported\_t60\_list](../hcl/#supported_t60_list)):\  Insert new inverter board (see -[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list) for what is +[../hcl/#supported\_t60\_list](../hcl/#supported_t60_list) for what is recommended on your LCD panel):\  diff --git a/docs/hcl/c201.md b/docs/hcl/c201.md index c816a210..3d4aae4f 100644 --- a/docs/hcl/c201.md +++ b/docs/hcl/c201.md @@ -14,7 +14,7 @@ instructions. The board is supported in libreboot, however, and has been confirmed to work.** Flashing instructions can be found at -[../install/\#flashrom](../install/#flashrom) +[../install/#flashrom](../install/#flashrom) [Back to previous index](./). @@ -118,7 +118,7 @@ require non-free firmware in the Linux kernel in order to work. The libreboot project recommends using an external USB wifi dongle that works with free software. See -[\#recommended\_wifi](./#recommended_wifi). +[#recommended\_wifi](./#recommended_wifi). There are 2 companies (endorsed by Creative Commons, under their *Respects your Freedom* guidelines), that sell USB WiFi dongles diff --git a/docs/hcl/ga-g41m-es2l.md b/docs/hcl/ga-g41m-es2l.md index ef3b7bd3..ef8e3563 100644 --- a/docs/hcl/ga-g41m-es2l.md +++ b/docs/hcl/ga-g41m-es2l.md @@ -15,7 +15,7 @@ Devuan, this would be in the entry for your NIC:\ hwaddress ether macaddressgoeshere Flashing instructions can be found at -[../install/\#flashrom](../install/#flashrom) +[../install/#flashrom](../install/#flashrom) diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md index 19719476..350e048c 100644 --- a/docs/hcl/gm45_remove_me.md +++ b/docs/hcl/gm45_remove_me.md @@ -41,7 +41,7 @@ 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 + $ ./oldbuild module ich9deblob The executable will appear under resources/utilities/ich9deblob/ Run:\ @@ -71,7 +71,7 @@ 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 + $ ./ich9gen \--macaddress XX:XX:XX:XX:XX:XX (replace the XX chars with the hexadecimal chars in the MAC address that you want) @@ -98,7 +98,7 @@ $ **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 +back to [../install/#flashrom](../install/#flashrom) for how to flash it. Write-protecting the flash chip @@ -131,7 +131,7 @@ flashing later on; for example, see [../install/bbb\_setup.html](../install/bbb_setup.html). Change them all to 0x0, then re-compile ich9gen. After you have done -that, follow the notes in [\#ich9gen](#ich9gen) to generate a new +that, follow the notes in [#ich9gen](#ich9gen) to generate a new descriptor+gbe image and insert that into your ROM image, then flash it. The next time you boot, the flash chip will be read-only in software (hardware re-flashing will still work, which you will need for @@ -166,7 +166,7 @@ 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 + $ ./oldbuild module ich9deblob An executable file named **ich9deblob** will now appear under resources/utilities/ich9deblob/ @@ -218,7 +218,7 @@ need for a factory.rom dump! You should now have a **libreboot.rom** image containing the correct 4K descriptor and 8K gbe regions, which will then be safe to flash. Refer -back to [../install/\#flashrom](../install/#flashrom) for how to flash +back to [../install/#flashrom](../install/#flashrom) for how to flash it. @@ -247,7 +247,7 @@ TODO: lenovobios (GM45 thinkpads) still write-protects parts of the flash. Modify the assembly code inside. Note: the factory.rom (BIOS region) from lenovobios is in a compressed format, which you have to extract. bios\_extract upstream won't work, but the following was said -in \#coreboot on freenode IRC: +in #coreboot on freenode IRC: <roxfan> vimuser: try bios_extract with ffv patch http://patchwork.coreboot.org/patch/3444/ <roxfan> or https://github.com/coreboot/bios_extract/blob/master/phoenix_extract.py diff --git a/docs/hcl/index.md b/docs/hcl/index.md index 911ae35b..b47465ad 100644 --- a/docs/hcl/index.md +++ b/docs/hcl/index.md @@ -132,12 +132,12 @@ BIOS](https://en.wikipedia.org/wiki/Video_BIOS)' or 'VBIOS'), all known LCD panels are currently compatible: To find what LCD panel you have, see: -[../misc/\#get\_edid\_panelname](../misc/#get_edid_panelname). +[../misc/#get\_edid\_panelname](../misc/#get_edid_panelname). -- TMD-Toshiba LTD121ECHB: \# -- CMO N121X5-L06: \# -- Samsung LTN121XJ-L07: \# -- BOE-Hydis HT121X01-101: \# +- TMD-Toshiba LTD121ECHB: # +- CMO N121X5-L06: # +- Samsung LTN121XJ-L07: # +- BOE-Hydis HT121X01-101: # You can remove an X61/X61s motherboard from the chassis and install an X60/X60s motherboard in it's place (for flashing libreboot). The @@ -149,7 +149,7 @@ at all without proprietary firmware, and while Lenovo BIOS is running the system will refuse to boot if you replace the card. Fortunately it is very easily replaced; just remove the card and install another one **after** libreboot is installed. See -[\#recommended\_wifi](#recommended_wifi) for replacements. +[#recommended\_wifi](#recommended_wifi) for replacements. [Back to top of page.](#pagetop) @@ -163,7 +163,7 @@ proprietary VGA Option ROM ('[Video BIOS](https://en.wikipedia.org/wiki/Video_BIOS)' or 'VBIOS'). To find what LCD panel you have, see: -[../misc/\#get\_edid\_panelname](../misc/#get_edid_panelname). +[../misc/#get\_edid\_panelname](../misc/#get_edid_panelname). There are 5 known LCD panels for the X60 Tablet: @@ -190,7 +190,7 @@ work at all without proprietary firmware, and while Lenovo BIOS is running the system will refuse to boot if you replace the card. Fortunately it is very easily replaced; just remove the card and install another one **after** libreboot is installed. See -[\#recommended\_wifi](#recommended_wifi) for replacements. +[#recommended\_wifi](#recommended_wifi) for replacements. A user with a X60T that has digitizer+finger support, reported that they could get finger input working. They used linuxwacom at git tag @@ -217,16 +217,16 @@ could get finger input working. They used linuxwacom at git tag Identifier "WTouch" Driver "wacom" Option "Device" "/dev/ttyS0" - # Option "DebugLevel" "12" + #Option "DebugLevel" "12" Option "BaudRate" "38400" Option "Type" "touch" Option "Touch" "on" Option "Gesture" "on" Option "ForceDevice" "ISDV4" - # Option "KeepShape" "on" + #Option "KeepShape" "on" Option "Mode" "Absolute" Option "RawSample" "2" - # Option "TPCButton" "off" + #Option "TPCButton" "off" Option "TopX" "17" Option "TopY" "53" Option "BottomX" "961" @@ -251,10 +251,10 @@ proprietary VGA Option ROM ('[Video BIOS](https://en.wikipedia.org/wiki/Video_BIOS)' or 'VBIOS'). To find what LCD panel you have, see: -[../misc/\#get\_edid\_panelname](../misc/#get_edid_panelname). +[../misc/#get\_edid\_panelname](../misc/#get_edid_panelname). **Some T60s have ATI GPUs, and all T60P laptops have ATI GPUs These are -incompatible! See [\#t60\_ati\_intel](#t60_ati_intel) for how to remedy +incompatible! See [#t60\_ati\_intel](#t60_ati_intel) for how to remedy this.** Tested LCD panels: **working(compatible)** @@ -273,7 +273,7 @@ Tested LCD panels: **working(compatible)** Tested LCD panels: **not working yet (incompatible; see -[../future/\#lcd\_i945\_incompatibility](../future/#lcd_i945_incompatibility))** +[../future/#lcd\_i945\_incompatibility](../future/#lcd_i945_incompatibility))** - Samsung LTN141XA-L01 (14.1" 1024x768) - LG-Philips LP150X09 (15.1" 1024x768) @@ -321,7 +321,7 @@ at all without proprietary firmware, and while Lenovo BIOS is running the system will refuse to boot if you replace the card. Fortunately it is very easily replaced; just remove the card and install another one **after** libreboot is installed. See -[\#recommended\_wifi](#recommended_wifi) for replacements. +[#recommended\_wifi](#recommended_wifi) for replacements. [Back to top of page.](#pagetop) @@ -382,7 +382,7 @@ same i945 chipset as the ThinkPad X60/T60. A developer ported the [MacBook2,1](#macbook21) to coreboot, the ROM images also work on the macbook1,1. -You can refer to [\#macbook21](#macbook21) for most of this. Macbook2,1 +You can refer to [#macbook21](#macbook21) for most of this. Macbook2,1 laptops come with Core 2 Duo processors which support 64-bit operating systems (and 32-bit). The MacBook1,1 uses Core Duo processors (supports 32-bit OS but not 64-bit), and it is believed that this is the only @@ -403,11 +403,11 @@ Specifically (Order No. / Model No. / CPU): Also of interest: -[../git/\#config\_macbook21](../git/#config_macbook21). +[../git/#config\_macbook21](../git/#config_macbook21). Unbricking: [this page shows disassembly guides](https://www.ifixit.com/Device/MacBook_Core_2_Duo) and mono's -page (see [\#macbook21](#macbook21)) shows the location of the SPI flash +page (see [#macbook21](#macbook21)) shows the location of the SPI flash chip on the motherboard. [How to remove the motherboard](https://www.ifixit.com/Guide/MacBook+Core+2+Duo+PRAM+Battery+Replacement/529). @@ -461,7 +461,7 @@ hold Alt/Control once more. The installation (on the HDD) will once again be seen as 'Windows'. (it's not actually Windows, but Apple likes to think that Apple and Microsoft are all that exist.) Now to install libreboot, follow -[../install/\#flashrom\_macbook21](../install/#flashrom_macbook21). +[../install/#flashrom\_macbook21](../install/#flashrom_macbook21). @@ -499,7 +499,7 @@ Specifically (Order No. / Model No. / CPU): Also of interest: -[../git/\#config\_macbook21](../git/#config_macbook21). +[../git/#config\_macbook21](../git/#config_macbook21). Unbricking: [this page shows disassembly guides](https://www.ifixit.com/Device/MacBook_Core_2_Duo) and mono's diff --git a/docs/hcl/kcma-d8.md b/docs/hcl/kcma-d8.md index a3283f20..31059374 100644 --- a/docs/hcl/kcma-d8.md +++ b/docs/hcl/kcma-d8.md @@ -11,7 +11,7 @@ Raptor Engineering Inc. and, working with them, merged into libreboot. recommend avoiding Kingston modules.** Flashing instructions can be found at -[../install/\#flashrom](../install/#flashrom) - note that external +[../install/#flashrom](../install/#flashrom) - note that external flashing is required (e.g. BBB), if the proprietary (ASUS) firmware is currently installed. If you already have libreboot, by default it is possible to re-flash using software running in GNU+Linux on the kcma-d8, @@ -103,7 +103,7 @@ Current issues {#issues} to derive from, for those who want to work on a free replacement. In practise, out-of-band management isn't very useful anyway (or at the very least, it's not a major inconvenience to not have it). -- Graphics: only text-mode works. See [\#graphics](#graphics) +- Graphics: only text-mode works. See [#graphics](#graphics) diff --git a/docs/hcl/kfsn4-dre.md b/docs/hcl/kfsn4-dre.md index 70d5a789..aed86dc1 100644 --- a/docs/hcl/kfsn4-dre.md +++ b/docs/hcl/kfsn4-dre.md @@ -6,7 +6,7 @@ This is a server board using AMD hardware (Fam10h). It can also be used for building a high-powered workstation. Powered by libreboot. Flashing instructions can be found at -[../install/\#flashrom](../install/#flashrom) +[../install/#flashrom](../install/#flashrom) [Back to previous index](./). diff --git a/docs/hcl/kgpe-d16.md b/docs/hcl/kgpe-d16.md index 891c30f4..9038e147 100644 --- a/docs/hcl/kgpe-d16.md +++ b/docs/hcl/kgpe-d16.md @@ -12,7 +12,7 @@ work), merged into libreboot. recommend avoiding Kingston modules.** Flashing instructions can be found at -[../install/\#flashrom](../install/#flashrom) - note that external +[../install/#flashrom](../install/#flashrom) - note that external flashing is required (e.g. BBB), if the proprietary (ASUS) firmware is currently installed. If you already have libreboot, by default it is possible to re-flash using software running in GNU+Linux on the @@ -104,7 +104,7 @@ Current issues {#issues} to derive from, for those who want to work on a free replacement. In practise, out-of-band management isn't very useful anyway (or at the very least, it's not a major inconvenience to not have it). -- Graphics: only text-mode works. See [\#graphics](#graphics) +- Graphics: only text-mode works. See [#graphics](#graphics) @@ -162,7 +162,7 @@ The information here is adapted, from the ASUS website. - **Slot Location 6:** PCI-E x16 (Gen2 X16 Link), Auto turn off if slot 5 is occupied, For 1U FH/FL Card, MIO supported - **Additional Slot 1:** PIKE slot (for SAS drives. See notes above) -- Follow SSI Location\# +- Follow SSI Location# ### Form factor {#form-factor} diff --git a/docs/hcl/r400.md b/docs/hcl/r400.md index d3fc8b10..9bac8134 100644 --- a/docs/hcl/r400.md +++ b/docs/hcl/r400.md @@ -17,7 +17,7 @@ modified descriptor: see [gm45\_remove\_me.html](gm45_remove_me.html)** (contains notes, plus instructions) Flashing instructions can be found at -[../install/\#flashrom](../install/#flashrom) +[../install/#flashrom](../install/#flashrom) [Back to previous index](./). diff --git a/docs/hcl/t400.md b/docs/hcl/t400.md index 9b5f3395..7d2f53d9 100644 --- a/docs/hcl/t400.md +++ b/docs/hcl/t400.md @@ -17,7 +17,7 @@ modified descriptor: see [gm45\_remove\_me.html](gm45_remove_me.html)** (contains notes, plus instructions) Flashing instructions can be found at -[../install/\#flashrom](../install/#flashrom) +[../install/#flashrom](../install/#flashrom) [Back to previous index](./). diff --git a/docs/hcl/t500.md b/docs/hcl/t500.md index 6d814c99..293c46fe 100644 --- a/docs/hcl/t500.md +++ b/docs/hcl/t500.md @@ -17,7 +17,7 @@ modified descriptor: see [gm45\_remove\_me.html](gm45_remove_me.html)** (contains notes, plus instructions) Flashing instructions can be found at -[../install/\#flashrom](../install/#flashrom) +[../install/#flashrom](../install/#flashrom) [Back to previous index](./). @@ -82,7 +82,7 @@ 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 t500gbe x200gbe $ **diff -u t500descriptor x200descriptor** ME VSCC table is in a different place and a different size on the T500. diff --git a/docs/hcl/x200.md b/docs/hcl/x200.md index 4bbc1543..65b6ce23 100644 --- a/docs/hcl/x200.md +++ b/docs/hcl/x200.md @@ -20,7 +20,7 @@ modified descriptor: see [gm45\_remove\_me.html](gm45_remove_me.html)** (contains notes, plus instructions) Flashing instructions can be found at -[../install/\#flashrom](../install/#flashrom) +[../install/#flashrom](../install/#flashrom) [Back to previous index](./). @@ -178,7 +178,7 @@ just simply remove the digitizer). **If your X200 has an LED backlit panel in it, then you also need to get an inverter and harness cable that is compatible with the CCFL panels. To see which panel type you have, see -[\#led\_howtotell](#led_howtotell). If you need the inverter/cable, here +[#led\_howtotell](#led_howtotell). If you need the inverter/cable, here are part numbers: 44C9909 for CCFL LVDS cable with bluetooth and camera connections, and 42W8009 or 42W8010 for the inverter.** @@ -262,7 +262,7 @@ $ **dmesg | sed -n 's/\^.* microcode: CPU0 sig=0x\\(\[\^,\]*\\),.*$/\\1/p'** What pehjota wrote: The laptops that have issues resuming from suspend, -as well as a laptop that (as I mentioned earlier in \#libreboot) won't +as well as a laptop that (as I mentioned earlier in #libreboot) won't boot with any Samsung DIMMs, all have CPUID 0x10676 (stepping M0). What pehjota wrote: Laptops with CPUID 0x167A (stepping R0) resume diff --git a/docs/index.md b/docs/index.md index 5608d6da..fb7cf026 100644 --- a/docs/index.md +++ b/docs/index.md @@ -177,7 +177,7 @@ If it exists, you can also extract this *lbversion* file by using the *cbfstool* utility which libreboot includes, from a ROM image that you either dumped or haven't flashed yet. In your distribution, run cbfstool on your ROM image (*libreboot.rom*, in this example):\ -$ ./cbfstool libreboot.rom extract -n lbversion -f lbversion + $ ./cbfstool 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. diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md index 244bd8e0..3c66a58e 100644 --- a/docs/install/bbb_setup.md +++ b/docs/install/bbb_setup.md @@ -114,10 +114,10 @@ page](https://en.wikipedia.org/wiki/Power_supply_unit_%28computer%29#Wiring_diag You can use pin 1 or 2 (orange wire) on a 20-pin or 24-pin ATX PSU for 3.3V, and any of the ground/earth sources (black cables) for ground. -Short PS\_ON\# / Power on (green wire; pin 16 on 24-pin ATX PSU, or pin +Short PS\_ON# / Power on (green wire; pin 16 on 24-pin ATX PSU, or pin 14 on a 20-pin ATX PSU) to a ground (black; there is one right next to it) using a wire/paperclip/jumper, then power on the PSU by grounding -PS\_ON\# (this is also how an ATX motherboard turns on a PSU). +PS\_ON# (this is also how an ATX motherboard turns on a PSU). **DO **NOT** use pin 4, 6, do **NOT** use pin 19 or 20 (on a 20-pin ATX PSU), and DO **NOT** use pin 21, 22 or 23 (on a 24-pin @@ -128,7 +128,7 @@ do exist, but they are rare. Always check what voltage your chip takes. Most of them take 3.3V).** You only need one 3.3V supply and one ground for the flash chip, after -grounding PS\_ON\#. +grounding PS\_ON#. The male end of a 0.1" or 2.54mm header cable is not thick enough to remain permanently connected to the ATX PSU on its own. When connecting @@ -158,14 +158,14 @@ 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 + # 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** +# **screen /dev/ttyACM0 115200** You can also access the uboot console, using the serial method instead of SSH. @@ -176,7 +176,7 @@ Setting up spidev on the BBB ============================ Log on as root on the BBB, using either SSH or a serial console as -defined in [\#bbb\_access](#bbb_access). Make sure that you have +defined in [#bbb\_access](#bbb_access). Make sure that you have internet access on your BBB. Follow the instructions at @@ -211,14 +211,14 @@ contents of this file with: 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.* + # 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 + # echo BB-SPI0-01 > /sys/devices/bone\_capemgr.*/slots + # cat /sys/devices/bone\_capemgr.*/slots Output: 0: 54:PF--- @@ -230,7 +230,7 @@ Output: 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* + # ls -al /dev/spid* Output: crw-rw---T 1 root spi 153, 0 Nov 19 21:07 /dev/spidev1.0 @@ -253,7 +253,7 @@ 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 + # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 Output: Calibrating delay loop... OK. @@ -348,7 +348,7 @@ not always. That page has some notes about using resistors to affect stability. Currently, we use spispeed=512 (512kHz) but it is possible to use higher speeds while maintaining stability. -tty0\_ in \#libreboot was able to get better flashing speeds with the +tty0\_ in #libreboot was able to get better flashing speeds with the following configuration: - "coax" with 0.1 mm core and aluminum foley (from my kitchen), add diff --git a/docs/install/c201.md b/docs/install/c201.md index da6e3499..2f7240ce 100644 --- a/docs/install/c201.md +++ b/docs/install/c201.md @@ -9,7 +9,7 @@ first time. **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/\#build](../git/#build)).** +the sources first (see [../git/#build](../git/#build)).** Look at the [list of ROM images](#rom) to see which image is compatible @@ -148,20 +148,20 @@ 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 + # chmod a+x cros-flash-replace The SPI flash has to be read first:\ -\# flashrom -p host -r flash.img + # 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 + # ./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 + # flashrom -p host -w flash.img You should also see within the output the following:\ **"Verifying flash\... VERIFIED."** @@ -178,7 +178,7 @@ to be opened. The SPI flash is located next to the write protect screw. Its layout is indicated in the picture below. Note that it is not necessary to connect -**WP\#** since removing the screw already connects it to ground. Before +**WP#** since removing the screw already connects it to ground. Before writing to the chip externally, the battery connector has to be detached. It is located under the heat spreader, that has to be unscrewed from the rest of the case. The battery connector is located on @@ -195,21 +195,21 @@ 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 + # 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 + # 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 + # ./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 + # flashrom -p *programmer* -w flash.img You should also see within the output the following:\ **"Verifying flash\... VERIFIED."** diff --git a/docs/install/d510mo.md b/docs/install/d510mo.md index 056b90cf..84ab442e 100644 --- a/docs/install/d510mo.md +++ b/docs/install/d510mo.md @@ -12,7 +12,7 @@ Flash chip size {#flashchips} =============== Use this to find out:\ -\# **flashrom -p internal -V** +# **flashrom -p internal -V** [Back to top of page.](#pagetop) diff --git a/docs/install/ga-g41m-es2l.md b/docs/install/ga-g41m-es2l.md index ef7bb97e..fbd1052d 100644 --- a/docs/install/ga-g41m-es2l.md +++ b/docs/install/ga-g41m-es2l.md @@ -12,7 +12,7 @@ Flash chip size {#flashchips} =============== Use this to find out:\ -\# **flashrom -p internal -V** +# **flashrom -p internal -V** [Back to top of page.](#pagetop) diff --git a/docs/install/index.md b/docs/install/index.md index ac59f60d..7c28613a 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -77,7 +77,7 @@ as the keymap in GNU+Linux is concerned. Keymaps are named appropriately according to each keyboard layout support in GRUB. To learn how these keymaps are created, see -[../grub/\#grub\_keyboard](../grub/#grub_keyboard) +[../grub/#grub\_keyboard](../grub/#grub_keyboard) QEMU ---- @@ -113,7 +113,7 @@ system. **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/\#build](../git/#build)).** +the sources first (see [../git/#build](../git/#build)).** Look at the [list of ROM images](#rom) to see which image is compatible @@ -127,8 +127,8 @@ coreboot), then the flashing instructions for your system are going to be different. X60/T60 users running the proprietary firmware should refer to -[\#flashrom\_lenovobios](#flashrom_lenovobios). MacBook2,1 users running -Apple EFI should refer to [\#flashrom\_macbook21](#flashrom_macbook21) +[#flashrom\_lenovobios](#flashrom_lenovobios). MacBook2,1 users running +Apple EFI should refer to [#flashrom\_macbook21](#flashrom_macbook21) X200 users, refer to [x200\_external.html](x200_external.html), R400 users refer to [r400\_external.html](r400_external.html), T400 users @@ -231,7 +231,7 @@ onboard ethernet chipset is located inside the flash chip. Libreboot ROM images for these laptops contain a generic MAC address by default, but this is not what you want. *Make sure to change the MAC address inside the ROM image, before flashing it. The instructions on -[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) show how to do this.* It is important that you change the default MAC address, before @@ -254,7 +254,7 @@ Flash chip size --------------- Use this to find out:\ -\# **flashrom -p internal -V** +# **flashrom -p internal -V** All good? --------- @@ -298,14 +298,14 @@ ThinkPad X60/T60: Initial installation guide (if running the proprietary firmwar **This is for the ThinkPad X60 and T60 while running Lenovo BIOS. If you already have coreboot or libreboot running, then go to -[\#flashrom](#flashrom) instead!** +[#flashrom](#flashrom) instead!** **If you are flashing a Lenovo ThinkPad T60, be sure to read -[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list)** +[../hcl/#supported\_t60\_list](../hcl/#supported_t60_list)** **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/\#build](../git/#build)).** +the sources first (see [../git/#build](../git/#build)).** **Warning: this guide will not instruct the user how to backup the @@ -369,15 +369,15 @@ MacBook2,1: Initial installation guide (if running the proprietary firmware) {#f **If you have a MacBook1,1, refer to -[../hcl/\#macbook11](../hcl/#macbook11) for flashing instructions.** +[../hcl/#macbook11](../hcl/#macbook11) for flashing instructions.** **This is for the MacBook2,1 while running Apple EFI firmware. If you already have coreboot or libreboot running, then go to -[\#flashrom](#flashrom) instead!** +[#flashrom](#flashrom) instead!** Be sure to read the information in -[../hcl/\#macbook21](../hcl/#macbook21). +[../hcl/#macbook21](../hcl/#macbook21). **Warning: this guide will not instruct the user how to backup the original Apple EFI firmware. For that, please refer to @@ -385,7 +385,7 @@ original Apple EFI firmware. For that, please refer to **If you are using libreboot\_src or git, then make sure that you built -the sources first (see [../git/\#build](../git/#build)).** +the sources first (see [../git/#build](../git/#build)).** Look at the [list of ROM images](#rom) to see which image is compatible diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md index 19f3a5fd..48016e65 100644 --- a/docs/install/r400_external.md +++ b/docs/install/r400_external.md @@ -65,7 +65,7 @@ initialization works all the same. CPU paste required ================== -See [\#paste](#paste). +See [#paste](#paste). @@ -73,7 +73,7 @@ Flash chip size {#flashchips} =============== Use this to find out:\ -\# flashrom -p internal -V + # flashrom -p internal -V [Back to top of page.](#pagetop) @@ -228,10 +228,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). +[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). Test that flashrom works:\ -\# ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 + # ./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) @@ -245,17 +245,17 @@ In this case, the output was: 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 +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom**\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom**\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +# **./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 + # 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 @@ -263,14 +263,14 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** Now flash it:\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V**  @@ -323,7 +323,7 @@ Wifi The R400 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). Some R400 laptops might come with an Atheros chipset, but this is 802.11g only. diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md index f3cbcb5a..f90819c9 100644 --- a/docs/install/rpi_setup.md +++ b/docs/install/rpi_setup.md @@ -57,7 +57,7 @@ B+ with 40 pins, start counting from the right and leave 14 pins): 1234 ~~~ Palmrest (back) ~~ - Pin \# SPI Pin Name BP (Seeed) BP (Spkfun) [Beagleboard Black](http://beagleboard.org/Support/bone101#headers) [Raspberry Pi](images/rpi/0000.jpg) + Pin # SPI Pin Name BP (Seeed) BP (Spkfun) [Beagleboard Black](http://beagleboard.org/Support/bone101#headers) [Raspberry Pi](images/rpi/0000.jpg) -------- -------------- ------------ ------------- --------------------------------------------------------------------- ------------------------------------- 1 CS White Red Pin 17 24 2 MISO Black Brown Pin 21 21 @@ -160,7 +160,7 @@ successfully. If not, just flash again. ### [](#raspberry-pi-pinout-diagrams){#user-content-raspberry-pi-pinout-diagrams .anchor}Raspberry Pi Pinout Diagrams - MCP 3008 Pin Pi GPIO Pin \# Pi Pin Name + MCP 3008 Pin Pi GPIO Pin # Pi Pin Name ----- ---------- ---------------- -------------------- 16 `VDD` 1 `3.3 V` 15 `VREF` 1 `3.3 V` @@ -285,7 +285,7 @@ text.  - Pin \# SPI Pin Name Raspberry Pi Pin \# + Pin # SPI Pin Name Raspberry Pi Pin \# -------- -------------- --------------------- 1 *not used* *not used* 2 3.3V 1 @@ -293,7 +293,7 @@ text. 4 *not used* *not used* 5 *not used* *not used* 6 *not used* *not used* - 7 CS\# 24 + 7 CS # 24 8 S0/SIO1 21 9 *not used* *not used* 10 GND 25 diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md index 1d9ea3ed..67e1471c 100644 --- a/docs/install/t400_external.md +++ b/docs/install/t400_external.md @@ -70,7 +70,7 @@ initialization works all the same. CPU paste required ================== -See [\#paste](#paste). +See [#paste](#paste). @@ -78,7 +78,7 @@ Flash chip size {#flashchips} =============== Use this to find out:\ -\# **flashrom -p internal -V** +# **flashrom -p internal -V** [Back to top of page.](#pagetop) @@ -234,10 +234,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). +[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). Test that flashrom works:\ -\# ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 + # ./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) @@ -251,17 +251,17 @@ In this case, the output was: 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 +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom**\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom**\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +# **./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 + # 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 @@ -269,14 +269,14 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** Now flash it:\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V**  @@ -329,7 +329,7 @@ Wifi The T400 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). Some T400 laptops might come with an Atheros chipset, but this is 802.11g only. diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md index e49886ec..0843ff87 100644 --- a/docs/install/t500_external.md +++ b/docs/install/t500_external.md @@ -60,7 +60,7 @@ initialization works all the same. CPU paste required ================== -See [\#paste](#paste). +See [#paste](#paste). @@ -68,7 +68,7 @@ Flash chip size {#flashchips} =============== Use this to find out:\ -\# **flashrom -p internal -V** +# **flashrom -p internal -V** [Back to top of page.](#pagetop) @@ -239,10 +239,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). +[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). Test that flashrom works:\ -\# ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 + # ./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) @@ -256,17 +256,17 @@ In this case, the output was: 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 +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom**\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom**\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +# **./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 + # 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 @@ -274,14 +274,14 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** Now flash it:\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V**  @@ -334,7 +334,7 @@ Wifi The T500 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). Some T500 laptops might come with an Atheros chipset, but this is 802.11g only. diff --git a/docs/install/t60_unbrick.md b/docs/install/t60_unbrick.md index 5ca8076a..79dec613 100644 --- a/docs/install/t60_unbrick.md +++ b/docs/install/t60_unbrick.md @@ -157,7 +157,7 @@ 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 +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom** It should be **Verifying flash\... VERIFIED** at the end. If flashrom diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md index 128f80af..12570a8c 100644 --- a/docs/install/x200_external.md +++ b/docs/install/x200_external.md @@ -36,12 +36,12 @@ Flash chip size {#flashchips} =============== Use this to find out:\ -\# **flashrom -p internal -V** +# **flashrom -p internal -V** The X200S and X200 Tablet will use a WSON-8 flash chip, on the bottom of the motherboard (this requires removal of the motherboard). **Not all X200S/X200T are supported; see -[../hcl/x200.html\#x200s](../hcl/x200.html#x200s).** +[../hcl/x200.html#x200s](../hcl/x200.html#x200s).** [Back to top of page.](#pagetop) @@ -114,7 +114,7 @@ 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) +[../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. @@ -168,10 +168,10 @@ libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. Log in as root on your BBB, using the instructions in -[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). +[bbb\_setup.html#bbb\_access](bbb_setup.html#bbb_access). Test that flashrom works:\ -\# ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 + # ./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) @@ -185,17 +185,17 @@ In this case, the output was: 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 +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom**\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom**\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +# **./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 + # 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 @@ -203,14 +203,14 @@ behaviour in the original firmware that could be replicated in coreboot and libreboot. Follow the instructions at -[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +[../hcl/gm45\_remove\_me.html#ich9gen](../hcl/gm45_remove_me.html#ich9gen) to change the MAC address inside the libreboot ROM image, before flashing it. Although there is a default MAC address inside the ROM image, this is not what you want. **Make sure to always change the MAC address to one that is correct for your system.** Now flash it:\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V**  @@ -244,7 +244,7 @@ Wifi The X200 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see -[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). +[../hcl/#recommended\_wifi](../hcl/#recommended_wifi). Some X200 laptops come with an Atheros chipset, but this is 802.11g only. @@ -340,7 +340,7 @@ here: On a related note, libreboot has a utility that could help with investigating this: -[../hcl/gm45\_remove\_me.html\#demefactory](../hcl/gm45_remove_me.html#demefactory) +[../hcl/gm45\_remove\_me.html#demefactory](../hcl/gm45_remove_me.html#demefactory) diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md index c291c584..ae79a40f 100644 --- a/docs/install/x60_unbrick.md +++ b/docs/install/x60_unbrick.md @@ -142,7 +142,7 @@ 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 +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom** It should be **Verifying flash\... VERIFIED** at the end. If flashrom diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md index 3fd64c2b..d918675b 100644 --- a/docs/install/x60tablet_unbrick.md +++ b/docs/install/x60tablet_unbrick.md @@ -121,7 +121,7 @@ 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 +# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom** It should be **Verifying flash\... VERIFIED** at the end. If flashrom diff --git a/docs/misc/index.md b/docs/misc/index.md index ce4ec4ea..c012ce99 100644 --- a/docs/misc/index.md +++ b/docs/misc/index.md @@ -62,7 +62,7 @@ Be root\ **$ su -** Installed powertop:\ -**\# pacman -S powertop** +**# pacman -S powertop** and added the following to /etc/systemd/system/powertop.service : @@ -80,8 +80,8 @@ and added the following to /etc/systemd/system/powertop.service : WantedBy=multi-user.target Finally, as root do that:\ - \# systemctl enable powertop -**\# systemctl start powertop** + # systemctl enable powertop +**# systemctl start powertop** The next time you boot the system, the buzz will be gone. @@ -227,11 +227,11 @@ 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=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=Enable $ **sudo ./nvramtool -w low\_battery\_beep=Disable** A reboot is required, for these changes to take effect. @@ -246,10 +246,10 @@ 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 modprobe i2c-dev $ **sudo i2cdump -y 5 0x50** (you might have to change the value for -y)\ -$ sudo rmmod i2c-dev + $ 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 diff --git a/docs/misc/patch.md b/docs/misc/patch.md index 07b53b03..00454a79 100644 --- a/docs/misc/patch.md +++ b/docs/misc/patch.md @@ -76,7 +76,7 @@ Note the git revision that you did this with:\ **$ git log** Alternatively (better yet), commit your changes and then use:\ -$ git format-patch -N + $ git format-patch -N Replace N with the number of commits that you want to show. [Back to top of page.](#pagetop) diff --git a/docs/release.md b/docs/release.md index a06c5d29..3c718384 100644 --- a/docs/release.md +++ b/docs/release.md @@ -46,7 +46,7 @@ Libreboot 20160818 {#release20160818} Release date: 18th August 2016. Installation instructions can be found at ***docs/install/***. Building -instructions (for source code) can be found at ***docs/git/\#build***. +instructions (for source code) can be found at ***docs/git/#build***. Machines supported in this release: ----------------------------------- @@ -74,22 +74,22 @@ Machines supported in this release: also fit inside an X60/X60s. - **ThinkPad X60 Tablet** (1024x768 and 1400x1050) with digitizer support - - See ***docs/hcl/\#supported\_x60t\_list*** for list of supported + - See ***docs/hcl/#supported\_x60t\_list*** for list of supported LCD panels - It is unknown whether an X61 Tablet can have it's mainboard replaced with an X60 Tablet motherboard. - **ThinkPad T60** (Intel GPU) (there are issues; see below): - See notes below for exceptions, and - ***docs/hcl/\#supported\_t60\_list*** for known working LCD + ***docs/hcl/#supported\_t60\_list*** for known working LCD panels. - It is unknown whether a T61 can have it's mainboard replaced with a T60 motherboard. - - See ***docs/future/\#t60\_cpu\_microcode***. + - See ***docs/future/#t60\_cpu\_microcode***. - T60P (and T60 laptops with ATI GPU) will likely never be - supported: ***docs/hcl/\#t60\_ati\_intel*** + supported: ***docs/hcl/#t60\_ati\_intel*** - **ThinkPad X200** - X200S and X200 Tablet are also supported, conditionally; see - ***docs/hcl/x200.html\#x200s*** + ***docs/hcl/x200.html#x200s*** - **ME/AMT**: libreboot removes this, permanently. ***docs/hcl/gm45\_remove\_me.html*** - **ThinkPad R400** @@ -105,10 +105,10 @@ Machines supported in this release: - **ME/AMT**: libreboot removes this, permanently. ***docs/hcl/gm45\_remove\_me.html*** - **Apple MacBook1,1** (MA255LL/A, MA254LL/A, MA472LL/A) - - See ***docs/hcl/\#macbook11***. + - See ***docs/hcl/#macbook11***. - **Apple MacBook2,1** (MA699LL/A, MA701LL/A, MB061LL/A, MA700LL/A, MB063LL/A, MB062LL/A) - - See ***docs/hcl/\#macbook21***. + - See ***docs/hcl/#macbook21***. Changes for this release, relative to r20150518 (earliest changes last, recent changes first) --------------------------------------------------------------------------------------------- |