From ece5fda25e70409032a16ea1cd64b0457279607b Mon Sep 17 00:00:00 2001 From: Alyssa Rosenzweig Date: Mon, 3 Apr 2017 09:19:08 -0700 Subject: Fix -- bug --- docs/hcl/gm45_remove_me.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/hcl') diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md index 659a878f..fd9ad9b0 100644 --- a/docs/hcl/gm45_remove_me.md +++ b/docs/hcl/gm45_remove_me.md @@ -69,7 +69,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) -- cgit v1.2.3-70-g09d2 From 8c651d9e574d6a12dc64ad9f4a05dfee5a2d8edd Mon Sep 17 00:00:00 2001 From: Alyssa Rosenzweig Date: Mon, 3 Apr 2017 09:48:26 -0700 Subject: More code blocks --- docs/future/index.md | 4 ++-- docs/git/index.md | 4 ++-- docs/gnulinux/configuring_parabola.md | 8 ++++---- docs/gnulinux/encrypted_parabola.md | 8 ++++---- docs/gnulinux/grub_cbfs.md | 8 ++++---- docs/hcl/gm45_remove_me.md | 4 ++-- docs/hcl/t500.md | 4 ++-- docs/index.md | 4 ++-- docs/install/bbb_setup.md | 4 ++-- docs/install/c201.md | 4 ++-- docs/install/r400_external.md | 4 ++-- docs/install/t400_external.md | 4 ++-- docs/install/t500_external.md | 4 ++-- docs/install/x200_external.md | 4 ++-- docs/misc/index.md | 4 ++-- docs/misc/patch.md | 4 ++-- 16 files changed, 38 insertions(+), 38 deletions(-) (limited to 'docs/hcl') diff --git a/docs/future/index.md b/docs/future/index.md index 7b5d2659..d4d6f970 100644 --- a/docs/future/index.md +++ b/docs/future/index.md @@ -158,8 +158,8 @@ 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**\ Example:\ diff --git a/docs/git/index.md b/docs/git/index.md index e9a91ce9..963ff073 100644 --- a/docs/git/index.md +++ b/docs/git/index.md @@ -32,8 +32,8 @@ 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**\ +following command: + $ sudo ./oldbuild dependencies debian (this will also work in Devuan) For Parabola, you can run the following command:\ diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md index 0739038e..ba54dde1 100644 --- a/docs/gnulinux/configuring_parabola.md +++ b/docs/gnulinux/configuring_parabola.md @@ -94,8 +94,8 @@ 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**\ +later but for now, I just connected my system to a switch and did: + # systemctl start dhcpcd.service You can stop it later by running:\ \# **systemctl stop dhcpcd.service**\ For most people this should be enough, but if you don't have DHCP on @@ -610,8 +610,8 @@ is advisable to also create an xinitrc rule in case you ever want to start lxde without lxdm. Read . -Open LXterminal:\ -\$ **cp /etc/skel/.xinitrc \~**\ +Open LXterminal: + $ cp /etc/skel/.xinitrc \~ Open .xinitrc and add the following plus a line break at the bottom of the file.\ *\# Probably not needed. The same locale info that we set before\ diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index afa4d137..f7faf575 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -68,8 +68,8 @@ article](https://wiki.archlinux.org/index.php/Solid_State_Drives). Edit /etc/fstab later on when chrooted into your install. Also, read the whole article and keep all points in mind, adapting them for this guide. -Securely wipe the drive:\ -\# **dd if=/dev/urandom of=/dev/sda; sync**\ +Securely wipe the drive: + # dd if=/dev/urandom of=/dev/sda; sync NOTE: If you have an SSD, only do this the first time. If it was already LUKS-encrypted before, use the info below to wipe the LUKS header. Also, check online for your SSD what the recommended erase block size is. For @@ -523,8 +523,8 @@ adapt:\ 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**\ +would be really nice): + $ ./cbfstool libreboot.rom print Extract grubtest.cfg:\ \$ **./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg**\ And modify:\ diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md index 538a04fd..d15e70d5 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -138,8 +138,8 @@ flashed. For the purpose of this tutorial it is assumed that your ROM image file is named *libreboot.rom*, so please make sure to adapt. ROM images are included pre-compiled in libreboot. You can also dump -your current firmware, using flashrom:\ -\$ **sudo flashrom -p internal -r libreboot.rom**\ +your current firmware, using flashrom: + $ sudo flashrom -p internal -r libreboot.rom \# **flashrom -p internal -r libreboot.rom**\ If you are told to specify the chip, add the option **-c {your chip}** to the command, for example:\ @@ -194,8 +194,8 @@ flash it.\ \$ **cd /libreboot\_util** \# **./flash update libreboot.rom**\ Ocassionally, coreboot changes the name of a given board. If flashrom complains about a board mismatch, but you are sure that you chose the -correct ROM image, then run this alternative command:\ -\# **./flash forceupdate libreboot.rom**\ +correct ROM image, then run this alternative command: + # ./flash forceupdate libreboot.rom You should see **"Verifying flash\... VERIFIED."** written at the end of the flashrom output. Once you have done that, shut down and then boot up with your new test configuration.** diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md index fd9ad9b0..606c0b1f 100644 --- a/docs/hcl/gm45_remove_me.md +++ b/docs/hcl/gm45_remove_me.md @@ -38,8 +38,8 @@ factory.bin dump. ich9gen executables can be found under ./ich9deblob/ statically compiled in libreboot\_util. If you are using src or git, build ich9gen from -source with:\ -\$ **./oldbuild module ich9deblob**\ +source with: + $ ./oldbuild module ich9deblob The executable will appear under resources/utilities/ich9deblob/ Run:\ diff --git a/docs/hcl/t500.md b/docs/hcl/t500.md index 866baaa7..7a88b3ca 100644 --- a/docs/hcl/t500.md +++ b/docs/hcl/t500.md @@ -79,8 +79,8 @@ and The patches above are based on the output from ich9deblob on a factory.rom image dumped from the T500 with a SOIC-8 4MiB flash chip. The patch re-creates the X200 descriptor/gbe source, so the commands -were something like:\ -\$ **diff -u t500gbe x200gbe**\ +were something like: + $ diff -u t500gbe x200gbe \$ **diff -u t500descriptor x200descriptor** ME VSCC table is in a different place and a different size on the T500. diff --git a/docs/index.md b/docs/index.md index 5dc8b261..d44b58e7 100644 --- a/docs/index.md +++ b/docs/index.md @@ -174,8 +174,8 @@ archives that you downloaded (if you are using release archives). If it exists, you can also extract this *lbversion* file by using the *cbfstool* utility which libreboot includes, from a ROM image that you either dumped or haven't flashed yet. In your distribution, run -cbfstool on your ROM image (*libreboot.rom*, in this example):\ -\$ **./cbfstool libreboot.rom extract -n lbversion -f lbversion**\ +cbfstool on your ROM image (*libreboot.rom*, in this example): + $ ./cbfstool libreboot.rom extract -n lbversion -f lbversion You will now have a file, named *lbversion*, which you can read in whatever program it is that you use for reading/writing text files. diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md index 85910bd8..cb1a3d17 100644 --- a/docs/install/bbb_setup.md +++ b/docs/install/bbb_setup.md @@ -155,8 +155,8 @@ 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**\ +the serial console. + # screen /dev/ttyUSB0 115200 Here are some example photos:\ ![](images/x200/ftdi.jpg) ![](images/x200/ftdi_port.jpg)\ diff --git a/docs/install/c201.md b/docs/install/c201.md index 62812986..28473cf7 100644 --- a/docs/install/c201.md +++ b/docs/install/c201.md @@ -145,8 +145,8 @@ 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**\ +**cros-flash-replace** script has to be made executable: + # chmod a+x cros-flash-replace The SPI flash has to be read first:\ \# **flashrom -p host -r flash.img**\ diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md index 00c8e3d4..f8f5123e 100644 --- a/docs/install/r400_external.md +++ b/docs/install/r400_external.md @@ -70,8 +70,8 @@ See [\#paste](#paste). Flash chip size {#flashchips} =============== -Use this to find out:\ -\# **flashrom -p internal -V**\ +Use this to find out: + # flashrom -p internal -V [Back to top of page.](#pagetop) diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md index 029acf0f..e68f86c8 100644 --- a/docs/install/t400_external.md +++ b/docs/install/t400_external.md @@ -234,8 +234,8 @@ source code which can be built. Log in as root on your BBB, using the instructions in [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). -Test that flashrom works:\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ +Test that flashrom works: + # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md index 5b07e6eb..7aec3099 100644 --- a/docs/install/t500_external.md +++ b/docs/install/t500_external.md @@ -239,8 +239,8 @@ source code which can be built. Log in as root on your BBB, using the instructions in [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). -Test that flashrom works:\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ +Test that flashrom works: + # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md index a09e0374..da4aa6a6 100644 --- a/docs/install/x200_external.md +++ b/docs/install/x200_external.md @@ -168,8 +168,8 @@ source code which can be built. Log in as root on your BBB, using the instructions in [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). -Test that flashrom works:\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ +Test that flashrom works: + # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) diff --git a/docs/misc/index.md b/docs/misc/index.md index a2f543a4..f392bdd4 100644 --- a/docs/misc/index.md +++ b/docs/misc/index.md @@ -227,8 +227,8 @@ battery goes to a critically low charge level, a beep occurs. Nvramtool is included in libreboot, and can be used to enable or disable this behaviour. -Disable or enable beeps when removing/adding the charger:\ -\$ **sudo ./nvramtool -w power\_management\_beeps=Enable**\ +Disable or enable beeps when removing/adding the charger: + $ sudo ./nvramtool -w power\_management\_beeps=Enable \$ **sudo ./nvramtool -w power\_management\_beeps=Disable** Disable or enable beeps when battery is low:\ diff --git a/docs/misc/patch.md b/docs/misc/patch.md index 7b44f7be..54c82ecf 100644 --- a/docs/misc/patch.md +++ b/docs/misc/patch.md @@ -73,8 +73,8 @@ Just make whatever changes you want to a git clone and then:\ Note the git revision that you did this with:\ **\$ git log** -Alternatively (better yet), commit your changes and then use:\ -\$ **git format-patch -N**\ +Alternatively (better yet), commit your changes and then use: + $ git format-patch -N Replace N with the number of commits that you want to show. [Back to top of page.](#pagetop) -- cgit v1.2.3-70-g09d2 From a23830654fa620d3982d851c9f8f0f99d282575d Mon Sep 17 00:00:00 2001 From: Alyssa Rosenzweig Date: Mon, 3 Apr 2017 09:51:32 -0700 Subject: Fix another class of code bug --- docs/future/index.md | 4 ++-- docs/git/index.md | 8 ++++---- docs/gnulinux/configuring_parabola.md | 8 ++++---- docs/gnulinux/encrypted_debian.md | 4 ++-- docs/gnulinux/encrypted_parabola.md | 8 ++++---- docs/gnulinux/grub_cbfs.md | 8 ++++---- docs/hcl/gm45_remove_me.md | 4 ++-- docs/install/bbb_setup.md | 4 ++-- docs/install/c201.md | 4 ++-- docs/install/d510mo.md | 4 ++-- docs/install/ga-g41m-es2l.md | 4 ++-- docs/install/index.md | 8 ++++---- docs/install/r400_external.md | 4 ++-- docs/install/t400_external.md | 4 ++-- docs/install/t500_external.md | 4 ++-- docs/install/x200_external.md | 4 ++-- docs/misc/index.md | 4 ++-- 17 files changed, 44 insertions(+), 44 deletions(-) (limited to 'docs/hcl') diff --git a/docs/future/index.md b/docs/future/index.md index d4d6f970..f882967a 100644 --- a/docs/future/index.md +++ b/docs/future/index.md @@ -160,8 +160,8 @@ How to dump EDID: \# **apt-get install i2c-tools** # modprobe i2c-dev -Find out the correct ID to use:\ -\# **i2cdetect -l**\ +Find out the correct ID to use: + # i2cdetect -l\ Example:\ \# **i2cdump -y 2 0x50** diff --git a/docs/git/index.md b/docs/git/index.md index 963ff073..ef7b3174 100644 --- a/docs/git/index.md +++ b/docs/git/index.md @@ -36,10 +36,10 @@ following command: $ sudo ./oldbuild dependencies debian (this will also work in Devuan) -For Parabola, you can run the following command:\ -\$ **sudo ./oldbuild dependencies parabola**\ -or:\ -\# **./oldbuild dependencies parabola** +For Parabola, you can run the following command: + $ sudo ./oldbuild dependencies parabola\ +or: + # ./oldbuild dependencies parabola For other GNU+Linux distributions, you can adapt the existing scripts. diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md index ba54dde1..12c05109 100644 --- a/docs/gnulinux/configuring_parabola.md +++ b/docs/gnulinux/configuring_parabola.md @@ -96,8 +96,8 @@ careful about this when reading anything on the Arch wiki. Some of these steps require internet access. I'll go into networking later but for now, I just connected my system to a switch and did: # systemctl start dhcpcd.service -You can stop it later by running:\ -\# **systemctl stop dhcpcd.service**\ +You can stop it later by running: + # systemctl stop dhcpcd.service\ For most people this should be enough, but if you don't have DHCP on your network then you should setup your network connection first:\ [Setup network connection in Parabola](#network) @@ -621,8 +621,8 @@ export LANG=en\_GB.UTF-8\ \ \# Start lxde desktop\ exec startlxde\ -* Now make sure that it is executable:\ -\$ **chmod +x .xinitrc** +* Now make sure that it is executable: + $ chmod +x .xinitrc [Back to top of page.](#pagetop) diff --git a/docs/gnulinux/encrypted_debian.md b/docs/gnulinux/encrypted_debian.md index b0f0b586..6dfb1435 100644 --- a/docs/gnulinux/encrypted_debian.md +++ b/docs/gnulinux/encrypted_debian.md @@ -200,8 +200,8 @@ ecryptfs If you didn't encrypt your home directory, then you can safely ignore this section. -Immediately after logging in, do that:\ -\$ **sudo ecryptfs-unwrap-passphrase** +Immediately after logging in, do that: + $ sudo ecryptfs-unwrap-passphrase This will be needed in the future if you ever need to recover your home directory from another system, so write it down and keep the note diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index f7faf575..f17fa10e 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -73,8 +73,8 @@ Securely wipe the drive: NOTE: If you have an SSD, only do this the first time. If it was already LUKS-encrypted before, use the info below to wipe the LUKS header. Also, check online for your SSD what the recommended erase block size is. For -example if it was 2MiB:\ -\# **dd if=/dev/urandom of=/dev/sda bs=2M; sync** +example if it was 2MiB: + # dd if=/dev/urandom of=/dev/sda bs=2M; sync If your drive was already LUKS encrypted (maybe you are re-installing your distro) then it is already 'wiped'. You should just wipe the LUKS @@ -525,8 +525,8 @@ option at the end, with the name of your chosen chip is quotes.\ You can check if everything is in there (*grub.cfg* and *grubtest.cfg* would be really nice): $ ./cbfstool libreboot.rom print -Extract grubtest.cfg:\ -\$ **./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg**\ +Extract grubtest.cfg: + $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg\ And modify:\ \$ **vi grubtest.cfg** diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md index d15e70d5..24fd2108 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -122,8 +122,8 @@ Acquire the necessary utilities {#tools} Use ***cbfstool*** and ***flashrom***. There are available in the *libreboot\_util* release archive, or they can be compiled (see [../git/\#build\_flashrom](../git/#build_flashrom)). Flashrom is also -available from the repositories:\ -\# **pacman -S flashrom** +available from the repositories: + # pacman -S flashrom [Back to top of page.](#pagetop) @@ -190,8 +190,8 @@ Testing **Now you have a modified ROM. Refer back to [../install/\#flashrom](../install/#flashrom) for information on how to -flash it.\ -\$ **cd /libreboot\_util** \# **./flash update libreboot.rom**\ +flash it. + $ cd /libreboot\_util** \# **./flash update libreboot.rom\ Ocassionally, coreboot changes the name of a given board. If flashrom complains about a board mismatch, but you are sure that you chose the correct ROM image, then run this alternative command: diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md index 606c0b1f..2001a9c6 100644 --- a/docs/hcl/gm45_remove_me.md +++ b/docs/hcl/gm45_remove_me.md @@ -42,8 +42,8 @@ source with: $ ./oldbuild module ich9deblob The executable will appear under resources/utilities/ich9deblob/ -Run:\ -\$ **./ich9gen** +Run: + $ ./ich9gen Running ich9gen this way (without any arguments) generates a default descriptor+gbe image with a generic MAC address. You probably don't diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md index cb1a3d17..6fb4e045 100644 --- a/docs/install/bbb_setup.md +++ b/docs/install/bbb_setup.md @@ -162,8 +162,8 @@ 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** +directly accessible from SSH, or screen: + # screen /dev/ttyACM0 115200 You can also access the uboot console, using the serial method instead of SSH. diff --git a/docs/install/c201.md b/docs/install/c201.md index 28473cf7..517f5311 100644 --- a/docs/install/c201.md +++ b/docs/install/c201.md @@ -148,8 +148,8 @@ device (e.g. using the *root* account). In addition, the **cros-flash-replace** script has to be made executable: # chmod a+x cros-flash-replace -The SPI flash has to be read first:\ -\# **flashrom -p host -r flash.img**\ +The SPI flash has to be read first: + # flashrom -p host -r flash.img\ **Note: it might be a good idea to copy the produced flash.img file at this point and store it outside of the device for backup purposes.** diff --git a/docs/install/d510mo.md b/docs/install/d510mo.md index 39604c89..572e7224 100644 --- a/docs/install/d510mo.md +++ b/docs/install/d510mo.md @@ -9,8 +9,8 @@ motherboard while they still have the original BIOS present. Flash chip size {#flashchips} =============== -Use this to find out:\ -\# **flashrom -p internal -V** +Use this to find out: + # flashrom -p internal -V [Back to top of page.](#pagetop) diff --git a/docs/install/ga-g41m-es2l.md b/docs/install/ga-g41m-es2l.md index 75ec3dbd..c254d675 100644 --- a/docs/install/ga-g41m-es2l.md +++ b/docs/install/ga-g41m-es2l.md @@ -9,8 +9,8 @@ motherboard while they still have the original BIOS present. Flash chip size {#flashchips} =============== -Use this to find out:\ -\# **flashrom -p internal -V** +Use this to find out: + # flashrom -p internal -V [Back to top of page.](#pagetop) diff --git a/docs/install/index.md b/docs/install/index.md index 25a3ad96..fd8ed008 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -251,8 +251,8 @@ ROM image, and it should work.** Flash chip size --------------- -Use this to find out:\ -\# **flashrom -p internal -V** +Use this to find out: + # flashrom -p internal -V All good? --------- @@ -271,8 +271,8 @@ appropriate executable. It is also possible for you to build these executables from the libreboot source code archives. -How to update the flash chip contents:\ -\$ **sudo ./flash update [yourrom.rom](#rom)** +How to update the flash chip contents: + $ sudo ./flash update [yourrom.rom](#rom) diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md index f8f5123e..c568f18b 100644 --- a/docs/install/r400_external.md +++ b/docs/install/r400_external.md @@ -228,8 +228,8 @@ source code which can be built. Log in as root on your BBB, using the instructions in [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). -Test that flashrom works:\ -\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ +Test that flashrom works: + # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512\ In this case, the output was: flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md index e68f86c8..80868e00 100644 --- a/docs/install/t400_external.md +++ b/docs/install/t400_external.md @@ -75,8 +75,8 @@ See [\#paste](#paste). Flash chip size {#flashchips} =============== -Use this to find out:\ -\# **flashrom -p internal -V** +Use this to find out: + # flashrom -p internal -V [Back to top of page.](#pagetop) diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md index 7aec3099..bccdc620 100644 --- a/docs/install/t500_external.md +++ b/docs/install/t500_external.md @@ -65,8 +65,8 @@ See [\#paste](#paste). Flash chip size {#flashchips} =============== -Use this to find out:\ -\# **flashrom -p internal -V** +Use this to find out: + # flashrom -p internal -V [Back to top of page.](#pagetop) diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md index da4aa6a6..2aa70cc5 100644 --- a/docs/install/x200_external.md +++ b/docs/install/x200_external.md @@ -33,8 +33,8 @@ Check the [suppliers](../../suppliers) page for more information. Flash chip size {#flashchips} =============== -Use this to find out:\ -\# **flashrom -p internal -V** +Use this to find out: + # flashrom -p internal -V The X200S and X200 Tablet will use a WSON-8 flash chip, on the bottom of the motherboard (this requires removal of the motherboard). **Not all diff --git a/docs/misc/index.md b/docs/misc/index.md index f392bdd4..59679ab0 100644 --- a/docs/misc/index.md +++ b/docs/misc/index.md @@ -231,8 +231,8 @@ Disable or enable beeps when removing/adding the charger: $ sudo ./nvramtool -w power\_management\_beeps=Enable \$ **sudo ./nvramtool -w power\_management\_beeps=Disable** -Disable or enable beeps when battery is low:\ -\$ **sudo ./nvramtool -w low\_battery\_beep=Enable**\ +Disable or enable beeps when battery is low: + $ sudo ./nvramtool -w low\_battery\_beep=Enable\ \$ **sudo ./nvramtool -w low\_battery\_beep=Disable** A reboot is required, for these changes to take effect. -- cgit v1.2.3-70-g09d2 From a19ff95539b0f9df2a59abef64f0decf999103f2 Mon Sep 17 00:00:00 2001 From: Alyssa Rosenzweig Date: Mon, 3 Apr 2017 09:54:31 -0700 Subject: Fix another class of code block bugs --- docs/future/index.md | 4 +- docs/git/index.md | 56 +++++++------- docs/gnulinux/configuring_parabola.md | 88 ++++++++++----------- docs/gnulinux/encrypted_parabola.md | 140 +++++++++++++++++----------------- docs/gnulinux/grub_cbfs.md | 4 +- docs/hcl/gm45_remove_me.md | 8 +- docs/hcl/t500.md | 2 +- docs/install/bbb_setup.md | 10 +-- docs/install/c201.md | 12 +-- docs/install/index.md | 8 +- docs/install/r400_external.md | 2 +- docs/install/t400_external.md | 2 +- docs/install/t500_external.md | 2 +- docs/install/x200_external.md | 2 +- docs/misc/index.md | 12 +-- 15 files changed, 176 insertions(+), 176 deletions(-) (limited to 'docs/hcl') diff --git a/docs/future/index.md b/docs/future/index.md index f882967a..cc98bcb5 100644 --- a/docs/future/index.md +++ b/docs/future/index.md @@ -158,12 +158,12 @@ working and nonworking panels. How to dump EDID: -\# **apt-get install i2c-tools** + # apt-get install i2c-tools # modprobe i2c-dev Find out the correct ID to use: # i2cdetect -l\ Example:\ -\# **i2cdump -y 2 0x50** + # i2cdump -y 2 0x50 Working panel: EDID dump from LG-Philips LP150E05-A2K1: diff --git a/docs/git/index.md b/docs/git/index.md index ef7b3174..71faafc1 100644 --- a/docs/git/index.md +++ b/docs/git/index.md @@ -64,21 +64,21 @@ 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 . Another nice config for you (optional, but recommended):\ -\$ **git config --global core.editor nano**\ -\$ **git config --global color.status auto**\ -\$ **git config --global color.branch auto**\ -\$ **git config --global color.interactive auto**\ -\$ **git config --global color.diff auto** + $ git config --global core.editor nano + $ git config --global color.status auto + $ git config --global color.branch auto + $ git config --global color.interactive auto + $ git config --global color.diff auto After that, run the script:\ -\$ **./download all** + $ ./download all What this did was download everything (grub, coreboot, memtest86+, bucts, flashrom) at the versions last tested for this release, and patch @@ -137,10 +137,10 @@ If you have the binary release archive, you'll find executables under First, [install the build dependencies](#build_dependencies). To build bucts, do this in the main directory:\ -\$ **./oldbuild module bucts** + $ ./oldbuild module bucts To statically compile it, do this:\ -\$ **./oldbuild module bucts static** + $ ./oldbuild module bucts static The "builddeps" script in libreboot\_src also makes use of builddeps-bucts. @@ -168,10 +168,10 @@ flashrom from source, continue reading. First, [install the build dependencies](#build_dependencies). To build it, do the following in the main directory:\ -\$ **./oldbuild module flashrom** + $ ./oldbuild module flashrom To statically compile it, do the following in the main directory:\ -\$ **./oldbuild module flashrom static** + $ ./oldbuild module flashrom static After you've done that, under ./flashrom/ you will find the following executables: @@ -215,24 +215,24 @@ If you downloaded libreboot from git, refer to [\#build\_meta](#build_meta). Build all of the components used in libreboot:\ -\$ **./oldbuild module all** + $ ./oldbuild module all You can also build each modules separately, using *./oldbuild module modulename*. To see the possible values for *modulename*, use:\ -\$ **./oldbuild module list** + $ ./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/**. To clean (reverse) everything, do the following:\ -\$ **./oldbuild clean all** + $ ./oldbuild clean all The ROM images will be stored under **bin/*payload*/**, where *payload* could be *grub*, *seabios*, or whatever other payload those images were @@ -260,23 +260,23 @@ in the file names of the archives. Otherwise, whatever git uses for *git describe --tags HEAD* will be used. Utilities (static executables):\ -\$ **./oldbuild release util** + $ ./oldbuild release util Archive containing flashrom and bucts source code:\ -\$ **./oldbuild release tobuild** + $ ./oldbuild release tobuild Documentation archive (**does not work on \_src release archive, only git**):\ -\$ **./oldbuild release docs** + $ ./oldbuild release docs ROM image archives:\ -\$ **./oldbuild release roms** + $ ./oldbuild release roms Source code archive:\ -\$ **./oldbuild release src** + $ ./oldbuild release src SHA512 sums of all other release archives that have been generated:\ -\$ **./oldbuild release sha512sums** + $ ./oldbuild release sha512sums If you are building on an i686 host, this will build statically linked 32-bit binaries in the binary release archive that you created, for: @@ -305,8 +305,8 @@ 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 bucts static** + $ ./oldbuild module flashrom static + $ ./oldbuild module bucts static The same conditions as above apply for ARM (except, building bucts on ARM is pointless, and for flashrom you only need the normal executable @@ -316,7 +316,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 12c05109..8a3f4751 100644 --- a/docs/gnulinux/configuring_parabola.md +++ b/docs/gnulinux/configuring_parabola.md @@ -127,12 +127,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.** @@ -197,7 +197,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 @@ -206,7 +206,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. @@ -252,9 +252,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). @@ -281,7 +281,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 @@ -301,7 +301,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 @@ -312,9 +312,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 @@ -324,7 +324,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 . 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):\ @@ -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 to learn how to use it. @@ -488,27 +488,27 @@ provide LXDE by default. Based on . 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 \    Arch wiki recommends installing these, for testing that X works:\ @@ -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 . 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 @@ -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 . Then I read: . 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:\ . 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 f17fa10e..2771bf34 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -83,7 +83,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). @@ -94,8 +94,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. @@ -123,7 +123,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 --------------------- @@ -137,7 +137,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). @@ -150,15 +150,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 @@ -185,29 +185,29 @@ Create LVM Now I refer to . 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 .\ -\# **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 @@ -217,7 +217,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 @@ -225,15 +225,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 @@ -248,8 +248,8 @@ Now I am following the rest of referenced . 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. @@ -257,9 +257,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. @@ -311,21 +311,21 @@ Configure the system Generate an fstab - UUIDs are used because they have certain advantages (see . 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 @@ -333,35 +333,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 # 127.0.0.1 localhost.localdomain localhost parabola @@ -375,7 +375,7 @@ Mkinitcpio: Configure /etc/mkinitcpio.conf as needed (see /usr/lib/initcpio/hooks, and build hooks can be found in /usr/lib/initcpio/install. (\# **mkinitcpio -H hookname** gives information about each hook.) Specifically, for this use case:\ -\# **vi /etc/mkinitcpio.conf**\ + # vi /etc/mkinitcpio.conf Then modify the file like so: - MODULES="i915" @@ -400,18 +400,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 .\ -\# **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. @@ -426,7 +426,7 @@ Extra security tweaks Based on . 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:\ @@ -436,7 +436,7 @@ Or just delete it. Above it, put:\ 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. @@ -450,20 +450,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. @@ -519,7 +519,7 @@ 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* @@ -528,7 +528,7 @@ would be really nice): Extract grubtest.cfg: $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg\ And modify:\ -\$ **vi grubtest.cfg** + $ vi grubtest.cfg In grubtest.cfg, inside the 'Load Operating System' menu entry, change the contents to: @@ -557,18 +557,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 . 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. @@ -599,21 +599,21 @@ with the following command:\ '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 . 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 @@ -638,17 +638,17 @@ Boot up and login as root or your user. Then generate the key file:\ \# **dd bs=512 count=4 if=/dev/urandom of=/etc/mykeyfile iflag=fullblock**\ Insert it into the luks volume:\ -\# **cryptsetup luksAddKey /dev/sdX /etc/mykeyfile**\ + # 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_cbfs.md b/docs/gnulinux/grub_cbfs.md index 24fd2108..feb16b73 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -140,10 +140,10 @@ 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**\ + # 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) diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md index 2001a9c6..c10c892e 100644 --- a/docs/hcl/gm45_remove_me.md +++ b/docs/hcl/gm45_remove_me.md @@ -69,7 +69,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) @@ -164,7 +164,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/ @@ -176,7 +176,7 @@ Place the factory.rom from your system (can be obtained using the external flashing guides for GM45 targets linked [../install/](../install/)) in the directory where you have your ich9deblob executable, then run the tool:\ -\$ **./ich9deblob** + $ ./ich9deblob A 12kiB file named **deblobbed\_descriptor.bin** will now appear. **Keep this and the factory.rom stored in a safe location!** The first 4KiB @@ -232,7 +232,7 @@ descriptor locks some regions. The idea is that doing this will remove all of those restrictions. Simply run (with factory.rom in the same directory):\ -\$ **./demefactory** + $ ./demefactory It will generate a 4KiB descriptor file (only the descriptor, no GbE). Insert that into a factory.rom image (NOTE: do this on a copy of it. diff --git a/docs/hcl/t500.md b/docs/hcl/t500.md index 7a88b3ca..a17a6fc1 100644 --- a/docs/hcl/t500.md +++ b/docs/hcl/t500.md @@ -81,7 +81,7 @@ factory.rom image dumped from the T500 with a SOIC-8 4MiB flash chip. The patch re-creates the X200 descriptor/gbe source, so the commands were something like: $ diff -u t500gbe x200gbe -\$ **diff -u t500descriptor x200descriptor** + $ diff -u t500descriptor x200descriptor ME VSCC table is in a different place and a different size on the T500. Libreboot disables and removes the ME anyway, so it doesn't matter. diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md index 6fb4e045..4211777e 100644 --- a/docs/install/bbb_setup.md +++ b/docs/install/bbb_setup.md @@ -209,14 +209,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--- @@ -228,7 +228,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 @@ -251,7 +251,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. diff --git a/docs/install/c201.md b/docs/install/c201.md index 517f5311..23cbf1bc 100644 --- a/docs/install/c201.md +++ b/docs/install/c201.md @@ -154,12 +154,12 @@ The SPI flash has to be read first: 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."** @@ -193,21 +193,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/index.md b/docs/install/index.md index fd8ed008..c03237cf 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -279,7 +279,7 @@ How to update the flash chip contents: Ocassionally, coreboot changes the name of a given board. If flashrom complains about a board mismatch, but you are sure that you chose the correct ROM image, then run this alternative command:\ -\$ **sudo ./flash forceupdate [yourrom.rom](#rom)** + $ sudo ./flash forceupdate [yourrom.rom](#rom) @@ -319,7 +319,7 @@ https://notabug.org/vimuser/libreboot/raw/9d850543ad90b72e0e333c98075530b31e5d23 && chmod +x flash*** The first half of the procedure is as follows:\ -\$ **sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom).** + $ sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom). @@ -343,7 +343,7 @@ and then boot; libreboot is running, but there is a 2nd procedure When you have booted up again, you must also do this:\ -\$ **sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom)** + $ sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom) If flashing fails at this stage, try the following:\ \$ **sudo ./flashrom/i686/flashrom -p @@ -392,7 +392,7 @@ with your device. Use this flashing script, to install libreboot:\ -\$ **sudo ./flash i945apple\_firstflash [yourrom.rom](#rom)** + $ sudo ./flash i945apple\_firstflash [yourrom.rom](#rom) diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md index c568f18b..7f2e7c2c 100644 --- a/docs/install/r400_external.md +++ b/docs/install/r400_external.md @@ -253,7 +253,7 @@ 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 diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md index 80868e00..2f8c424f 100644 --- a/docs/install/t400_external.md +++ b/docs/install/t400_external.md @@ -259,7 +259,7 @@ 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 diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md index bccdc620..05e4c112 100644 --- a/docs/install/t500_external.md +++ b/docs/install/t500_external.md @@ -264,7 +264,7 @@ 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 diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md index 2aa70cc5..ac199b2a 100644 --- a/docs/install/x200_external.md +++ b/docs/install/x200_external.md @@ -193,7 +193,7 @@ 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 diff --git a/docs/misc/index.md b/docs/misc/index.md index 59679ab0..15d0ea08 100644 --- a/docs/misc/index.md +++ b/docs/misc/index.md @@ -28,7 +28,7 @@ Included with libreboot is a script called 'powertop.debian'. Run this as root and it will setup powertop to run with --auto-tune at boot time. Load the file in your text editor to see how it does that. -\$ **sudo ./resources/scripts/misc/powertop.debian** + $ sudo ./resources/scripts/misc/powertop.debian Might want to run with --calibrate first @@ -229,11 +229,11 @@ behaviour. Disable or enable beeps when removing/adding the charger: $ sudo ./nvramtool -w power\_management\_beeps=Enable -\$ **sudo ./nvramtool -w power\_management\_beeps=Disable** + $ sudo ./nvramtool -w power\_management\_beeps=Disable Disable or enable beeps when battery is low: $ sudo ./nvramtool -w low\_battery\_beep=Enable\ -\$ **sudo ./nvramtool -w low\_battery\_beep=Disable** + $ sudo ./nvramtool -w low\_battery\_beep=Disable A reboot is required, for these changes to take effect. @@ -247,10 +247,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 i2cdump -y 5 0x50** (you might have to change the value for + $ 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 -- cgit v1.2.3-70-g09d2 From 7bc11816a44e8cd2712e46dc958795d354856419 Mon Sep 17 00:00:00 2001 From: Alyssa Rosenzweig Date: Mon, 3 Apr 2017 09:57:13 -0700 Subject: Fix yet another class of codeblock bugs -- Leah really has no consitency.. --- docs/bsd/freebsd.md | 20 ++++++++++---------- docs/bsd/netbsd.md | 20 ++++++++++---------- docs/bsd/openbsd.md | 20 ++++++++++---------- docs/future/index.md | 2 +- docs/future/old.md | 2 +- docs/gnulinux/grub_boot_installer.md | 20 ++++++++++---------- docs/gnulinux/grub_cbfs.md | 10 +++++----- docs/grub/index.md | 8 ++++---- docs/hcl/index.md | 2 +- docs/misc/index.md | 10 +++++----- docs/misc/patch.md | 24 ++++++++++++------------ 11 files changed, 69 insertions(+), 69 deletions(-) (limited to 'docs/hcl') diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md index fa7c8167..9f0d58e0 100644 --- a/docs/bsd/freebsd.md +++ b/docs/bsd/freebsd.md @@ -60,17 +60,17 @@ If you downloaded your ISO on a LibertyBSD or OpenBSD system, here is how to create the bootable FreeBSD USB drive: Connect the USB drive. Check dmesg:\ -**\$ dmesg | tail**\ + $ dmesg | tail Check to confirm which drive it is, for example, if you think its sd3:\ -**\$ disklabel sd3** + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For example:\ -**\$ doas umount /dev/sd3i**\ + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the FreeBSD installer to it with dd. For example:\ -**\$ doas dd if=freebsd.img of=/dev/rsdXc bs=1M; sync**\ + $ doas dd if=freebsd.img of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. @@ -84,19 +84,19 @@ If you downloaded your ISO on a GNU+Linux system, here is how to create the bootable FreeBSD USB drive: Connect the USB drive. Check dmesg:\ -**\$ dmesg**\ + $ dmesg Check lsblk to confirm which drive it is:\ -**\$ lsblk** + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For example:\ -**\$ sudo umount /dev/sdX\***\ -**\# umount /dev/sdX\*** + $ sudo umount /dev/sdX\* + # umount /dev/sdX\* dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example:\ -**\$ sudo dd if=freebsd.img of=/dev/sdX bs=8M; sync**\ -**\# dd if=freebsd.img of=/dev/sdX bs=8M; sync** + $ sudo dd if=freebsd.img of=/dev/sdX bs=8M; sync + # dd if=freebsd.img of=/dev/sdX bs=8M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. diff --git a/docs/bsd/netbsd.md b/docs/bsd/netbsd.md index 286d9495..ff515c40 100644 --- a/docs/bsd/netbsd.md +++ b/docs/bsd/netbsd.md @@ -56,17 +56,17 @@ If you downloaded your ISO on a LibertyBSD or NetBSD system, here is how to create the bootable NetBSD USB drive: Connect the USB drive. Check dmesg:\ -**\$ dmesg | tail**\ + $ dmesg | tail Check to confirm which drive it is, for example, if you think its sd3:\ -**\$ disklabel sd3** + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For example:\ -**\$ doas umount /dev/sd3i**\ + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the NetBSD installer to it with dd. For example:\ -**\$ doas netbsd.iso of=/dev/rsdXc bs=1M; sync**\ + $ doas netbsd.iso of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. @@ -80,19 +80,19 @@ If you downloaded your ISO on a GNU+Linux system, here is how to create the bootable NetBSD USB drive: Connect the USB drive. Check dmesg:\ -**\$ dmesg**\ + $ dmesg Check lsblk to confirm which drive it is:\ -**\$ lsblk** + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For example:\ -**\$ sudo umount /dev/sdX\***\ -**\# umount /dev/sdX\*** + $ sudo umount /dev/sdX\* + # umount /dev/sdX\* dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example:\ -**\$ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync**\ -**\# dd if=netbsd.iso of=/dev/sdX bs=8M; sync** + $ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync + # dd if=netbsd.iso of=/dev/sdX bs=8M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md index 988b87e6..4a7027d3 100644 --- a/docs/bsd/openbsd.md +++ b/docs/bsd/openbsd.md @@ -38,17 +38,17 @@ If you downloaded your ISO on a LibertyBSD or OpenBSD system, here is how to create the bootable LibertyBSD/OpenBSD USB drive: Connect the USB drive. Check dmesg:\ -**\$ dmesg | tail**\ + $ dmesg | tail Check to confirm which drive it is, for example, if you think its sd3:\ -**\$ disklabel sd3** + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For example:\ -**\$ doas umount /dev/sd3i**\ + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the OpenBSD installer to it with dd. For example:\ -**\$ doas dd if=install60.fs of=/dev/rsdXc bs=1M; sync**\ + $ doas dd if=install60.fs of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. @@ -79,19 +79,19 @@ If you downloaded your ISO on a GNU+Linux system, here is how to create the bootable OpenBSD USB drive: Connect the USB drive. Check dmesg:\ -**\$ dmesg**\ + $ dmesg Check lsblk to confirm which drive it is:\ -**\$ lsblk** + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For example:\ -**\$ sudo umount /dev/sdX\***\ -**\# umount /dev/sdX\*** + $ sudo umount /dev/sdX\* + # umount /dev/sdX\* dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example:\ -**\$ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync**\ -**\# dd if=install60.fs of=/dev/sdX bs=8M; sync** + $ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync + # dd if=install60.fs of=/dev/sdX bs=8M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. diff --git a/docs/future/index.md b/docs/future/index.md index cc98bcb5..3eacbc92 100644 --- a/docs/future/index.md +++ b/docs/future/index.md @@ -325,7 +325,7 @@ Get intelvbttool here: Now dump a copy of the running VGA BIOS: **\$ sudo dd if=/dev/mem bs=64k of=runningvga.bin skip=12 count=1**\ Then do (and record the output):\ -**\$ ./intelvbttool runningvga.bin > intelvbttool\_out** + $ ./intelvbttool runningvga.bin > intelvbttool\_out Backup both files (runningvga.bin and intelvbttool\_out), renaming them to match the system and LCD panel used. diff --git a/docs/future/old.md b/docs/future/old.md index 71107fba..8fc4e273 100644 --- a/docs/future/old.md +++ b/docs/future/old.md @@ -44,7 +44,7 @@ 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. diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md index 08a1c83e..1fd924b1 100644 --- a/docs/gnulinux/grub_boot_installer.md +++ b/docs/gnulinux/grub_boot_installer.md @@ -29,19 +29,19 @@ If you downloaded your ISO on an existing GNU+Linux system, here is how to create the bootable GNU+Linux USB drive: Connect the USB drive. Check dmesg:\ -**\$ dmesg**\ + $ dmesg Check lsblk to confirm which drive it is:\ -**\$ lsblk** + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For example:\ -**\$ sudo umount /dev/sdX\***\ -**\# umount /dev/sdX\*** + $ sudo umount /dev/sdX\* + # umount /dev/sdX\* dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example:\ -**\$ sudo dd if=gnulinux.iso of=/dev/sdX bs=8M; sync**\ -**\# dd if=gnulinux.iso of=/dev/sdX bs=8M; sync** + $ sudo dd if=gnulinux.iso of=/dev/sdX bs=8M; sync + # dd if=gnulinux.iso of=/dev/sdX bs=8M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. @@ -72,17 +72,17 @@ If you downloaded your ISO on a LibertyBSD or OpenBSD system, here is how to create the bootable GNU+Linux USB drive: Connect the USB drive. Check dmesg:\ -**\$ dmesg | tail**\ + $ dmesg | tail Check to confirm which drive it is, for example, if you think its sd3:\ -**\$ disklabel sd3** + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For example:\ -**\$ doas umount /dev/sd3i**\ + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the OpenBSD installer to it with dd. For example:\ -**\$ doas dd if=gnulinux.iso of=/dev/rsdXc bs=1M; sync**\ + $ doas dd if=gnulinux.iso of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md index feb16b73..31192f5a 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -153,7 +153,7 @@ Extract grubtest.cfg from the ROM image {#extract_testconfig} --------------------------------------- You can check the contents of the ROM image, inside CBFS:\ -**\$ cd \.../libreboot\_util/cbfstool** **\$ ./cbfstool libreboot.rom + $ cd \.../libreboot\_util/cbfstool** $ ./cbfstool libreboot.rom print** The files *grub.cfg* and *grubtest.cfg* should be present. grub.cfg is @@ -162,7 +162,7 @@ this tutorial, you will first modify and test *grubtest.cfg*. This is to reduce the possibility of bricking your device, so DO NOT SKIP THIS! Extract grubtest.cfg from the ROM image:\ -**\$ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg** + $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg Modify the grubtest.cfg accordingly. @@ -175,7 +175,7 @@ Re-insert the modified grubtest.cfg into the ROM image {#reinsert_modified_testc Once your grubtest.cfg is modified and saved, delete the unmodified config from the ROM image:\ -**\$ ./cbfstool libreboot.rom remove -n grubtest.cfg** + $ ./cbfstool libreboot.rom remove -n grubtest.cfg Next, insert the modified version:\ **\$ ./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t @@ -228,10 +228,10 @@ the already modified config). From /libreboot\_util/cbfstool, do:\ 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. Again, refer back to [../install/\#flashrom](../install/#flashrom) for information on how to diff --git a/docs/grub/index.md b/docs/grub/index.md index 56cbf470..81e4bd56 100644 --- a/docs/grub/index.md +++ b/docs/grub/index.md @@ -45,10 +45,10 @@ one](http://sourceforge.net/projects/dejavu/files/dejavu/2.34/dejavu-fonts-ttf-2 This is a free font that is also contained in GNU+Linux distributions like Debian, Devuan or Parabola. -**\$ cd libreboot\_src/grub**\ + $ cd libreboot\_src/grub compile grub (the build scripts info on how to do this)\ come back out into libreboot\_src/resources/grub:\ -**\$ cd ../libreboot\_src/resources/grub/font** + $ cd ../libreboot\_src/resources/grub/font I took Dejavu Sans Mono from dejavu (included in this version of libreboot) and did:\ @@ -76,7 +76,7 @@ Custom keyboard layout in GRUB (for reference) {#grub_custom_keyboard} Keymaps are stored in resources/utilities/grub-assemble/keymap/. Example (French Azerty):\ -**\$ ckbcomp fr > frazerty**\ + $ ckbcomp fr > frazerty \ Go in grub directory:\ **cat frazerty | ./grub/grub-mklayout -o frazerty.gkb** @@ -104,7 +104,7 @@ ukdvorak had to be created manually, based on usdvorak. diff them (under resources/utilities/grub-assemble/keymap/original) to see how ukdvorak file was created -**\$ cat ukdvorak | ./grub/grub-mklayout -o ukdvorak.gkb** + $ cat ukdvorak | ./grub/grub-mklayout -o ukdvorak.gkb [Back to top of page](#pagetop) diff --git a/docs/hcl/index.md b/docs/hcl/index.md index 80590568..8adb7fc4 100644 --- a/docs/hcl/index.md +++ b/docs/hcl/index.md @@ -437,7 +437,7 @@ the macbook2,1. They are included here in case the main site goes down for whatever reason, since they include a lot of useful information. Backups created using wget:\ -**\$ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/**\ + $ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/ **\$ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/coreboot/**\ Use **-e robots=off** if using this trick for other sites and the site diff --git a/docs/misc/index.md b/docs/misc/index.md index 15d0ea08..7d73569b 100644 --- a/docs/misc/index.md +++ b/docs/misc/index.md @@ -58,10 +58,10 @@ when idle. So far we have use processor.max\_cstate=2 or idle=halt in GRUB. These consume power. Stop using them! Be root\ -**\$ su -** + $ su - Installed powertop:\ -**\# pacman -S powertop** + # pacman -S powertop and added the following to /etc/systemd/system/powertop.service : @@ -79,8 +79,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. @@ -108,7 +108,7 @@ port on the dock and connect the other end to a 2nd system using your USB Serial adapter. On the 2nd system, you can try this (using GNU Screen):\ -**\$ sudo screen /dev/ttyUSB0 115200** + $ sudo screen /dev/ttyUSB0 115200 How to quit GNU Screen: Ctrl+A then release and press K, and then press Y. diff --git a/docs/misc/patch.md b/docs/misc/patch.md index 54c82ecf..9f22f776 100644 --- a/docs/misc/patch.md +++ b/docs/misc/patch.md @@ -10,11 +10,11 @@ Apply a patch ============= To apply a patch to a single file, do that in it's directory:\ -**\$ patch < foo.patch** + $ patch < foo.patch Assuming that the patch is distributed in unified format identifying the file the patch should be applied to, the above will work. Otherwise:\ -**\$ patch foo.txt < bar.patch** + $ patch foo.txt < bar.patch You can apply a patch to an entire directory, but note the "p level". What this means is that inside patch files will be the files that you @@ -23,7 +23,7 @@ the files ane located on your own computer instead of on the computer where the patch was created. 'p' level instructs the 'patch' utility to ignore parts of the path name to identify the files correctly. Usually a p level of 1 will work, so you would use:\ -**\$ patch -p1 < baz.patch** + $ patch -p1 < baz.patch Change to the top level directory before running this. If a patch level of 1 cannot identify the files to patch, then inspect the patch file for @@ -31,14 +31,14 @@ file names. For example:\ **/home/user/do/not/panic/yet.c** and you are working in a directory that contains panic/yet.c, use:\ -**\$ patch -p5 < baz.patch** + $ patch -p5 < baz.patch You usually count one up for each path separator (forward slash) removed from the beginning of the path, until you are left with a path that exists in the current working directory. The count is the p level. Removing a patch using the -R flag\ -**\$ patch -p5 -R < baz.patch** + $ patch -p5 -R < baz.patch [Back to top of page.](#pagetop) @@ -48,13 +48,13 @@ Create a patch with diff ======================== Diff can create a patch for a single file:\ -**\$ diff -u original.c new.c > original.patch** + $ diff -u original.c new.c > original.patch For diff'ing a source tree:\ -**\$ cp -R original new** + $ cp -R original new Do whatever you want in new/ and then diff it:\ -**\$ diff -rupN original/ new/ > original.patch** + $ diff -rupN original/ new/ > original.patch [Back to top of page.](#pagetop) @@ -68,10 +68,10 @@ git is something special. Note: this won't show new files created. Just make whatever changes you want to a git clone and then:\ -**\$ git diff > patch.git** + $ git diff > patch.git Note the git revision that you did this with:\ -**\$ git log** + $ git log Alternatively (better yet), commit your changes and then use: $ git format-patch -N @@ -88,10 +88,10 @@ it really is. Now to apply that patch in the future, just git clone it again and do with the git revision you found from above:\ -**\$ git reset --hard REVISIONNUMBER** + $ git reset --hard REVISIONNUMBER Now put patch.git in the git clone directory and do:\ -**\$ git apply patch.git** + $ git apply patch.git If you use a patch from git format-patch, then use **git am patch.git** instead of **git apply patch.git**. git-am will re-create the commits -- cgit v1.2.3-70-g09d2 From 78c7b8355832b9f3eb574788ab4c5a7d96f0486e Mon Sep 17 00:00:00 2001 From: Alyssa Rosenzweig Date: Mon, 3 Apr 2017 10:22:40 -0700 Subject: embedded code block top fix --- docs/archive_old.md | 4 +++- docs/bsd/freebsd.md | 4 +++- docs/bsd/index.md | 1 + docs/bsd/netbsd.md | 4 +++- docs/bsd/openbsd.md | 4 +++- docs/depthcharge/index.md | 4 +++- docs/future/index.md | 4 +++- docs/future/old.md | 4 +++- docs/git/index.md | 4 +++- docs/gnulinux/configuring_parabola.md | 4 +++- docs/gnulinux/encrypted_debian.md | 1 + docs/gnulinux/encrypted_parabola.md | 4 +++- docs/gnulinux/grub_boot_installer.md | 4 +++- docs/gnulinux/grub_cbfs.md | 4 +++- docs/gnulinux/grub_hardening.md | 1 + docs/gnulinux/index.md | 1 + docs/grub/index.md | 4 +++- docs/hardware/dock.md | 1 + docs/hardware/index.md | 1 + docs/hardware/t60_heatsink.md | 1 + docs/hardware/t60_security.md | 4 +++- docs/hardware/x60_heatsink.md | 1 + docs/hardware/x60_security.md | 4 +++- docs/hcl/c201.md | 1 + docs/hcl/d945gclf.md | 1 + docs/hcl/gm45_remove_me.md | 4 +++- docs/hcl/index.md | 4 +++- docs/hcl/kcma-d8.md | 1 + docs/hcl/kfsn4-dre.md | 1 + docs/hcl/kgpe-d16.md | 1 + docs/hcl/t400.md | 1 + docs/hcl/t500.md | 1 + docs/hcl/x200.md | 1 + docs/index.md | 4 +++- docs/install/bbb_setup.md | 4 +++- docs/install/c201.md | 4 +++- docs/install/d510mo.md | 1 + docs/install/ga-g41m-es2l.md | 1 + docs/install/index.md | 4 +++- docs/install/kcma-d8.md | 1 + docs/install/kgpe-d16.md | 1 + docs/install/r400_external.md | 4 +++- docs/install/rpi_setup.md | 1 + docs/install/t400_external.md | 4 +++- docs/install/t500_external.md | 4 +++- docs/install/t60_unbrick.md | 1 + docs/install/x200_external.md | 4 +++- docs/install/x60_unbrick.md | 1 + docs/install/x60tablet_unbrick.md | 1 + docs/misc/bbb_ehci.md | 1 + docs/misc/index.md | 4 +++- docs/misc/patch.md | 4 +++- docs/release.md | 1 + www/amd-libre.md | 1 + www/faq.md | 1 + www/git.md | 1 + www/gpg.md | 1 + www/lists.md | 1 + 58 files changed, 112 insertions(+), 27 deletions(-) (limited to 'docs/hcl') diff --git a/docs/archive_old.md b/docs/archive_old.md index f8d3f441..54d9c620 100644 --- a/docs/archive_old.md +++ b/docs/archive_old.md @@ -16,6 +16,7 @@ Releases - [r20150518 (18th May 2015)](#release20150518) - [r20150124 (24th January 2015), r20150126 (26th January 2015), r20150208 (8th February 2015)](#release20150124) + - [r20141015 (15th October 2014)](#release20141015) - [r20140911 (6th release)](#release20140911) (11th September 2014 **pre-release, 7th beta**) @@ -422,7 +423,8 @@ Changes for this release (latest changes first, earliest changes last) - build: Only generate the GRUB configurations once (re-use on all images) - Only build 2 GRUB payload executables, re-use on all boards. -- resources/utilities/grub-assemble/gen.txtmode.sh: Use GNU BASH\ +- resources/utilities/grub-assemble/gen.txtmode.sh: Use GNU BASH + resources/utilities/grub-assemble/gen.vesafb.sh: Use GNU BASH - scripts (error handling): Replace exit with exit 1 (make debugging easier) diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md index 9f0d58e0..31d9df17 100644 --- a/docs/bsd/freebsd.md +++ b/docs/bsd/freebsd.md @@ -59,8 +59,10 @@ Prepare the USB drive (in LibertyBSD or OpenBSD) If you downloaded your ISO on a LibertyBSD or OpenBSD system, here is how to create the bootable FreeBSD USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg | tail + Check to confirm which drive it is, for example, if you think its sd3:\ $ disklabel sd3 diff --git a/docs/bsd/index.md b/docs/bsd/index.md index 8f0aad75..7b2aecbe 100644 --- a/docs/bsd/index.md +++ b/docs/bsd/index.md @@ -11,6 +11,7 @@ instructions have yet to be written.** - [How to install NetBSD on a libreboot system](netbsd.html) - [How to install LibertyBSD or OpenBSD on a libreboot system](openbsd.html) + - [How to install FreeBSD on a libreboot system](freebsd.html) diff --git a/docs/bsd/netbsd.md b/docs/bsd/netbsd.md index ff515c40..3046ef00 100644 --- a/docs/bsd/netbsd.md +++ b/docs/bsd/netbsd.md @@ -55,8 +55,10 @@ Prepare the USB drive (in LibertyBSD or NetBSD) If you downloaded your ISO on a LibertyBSD or NetBSD system, here is how to create the bootable NetBSD USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg | tail + Check to confirm which drive it is, for example, if you think its sd3:\ $ disklabel sd3 diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md index 4a7027d3..4440b665 100644 --- a/docs/bsd/openbsd.md +++ b/docs/bsd/openbsd.md @@ -37,8 +37,10 @@ Prepare the USB drive (in LibertyBSD or OpenBSD) If you downloaded your ISO on a LibertyBSD or OpenBSD system, here is how to create the bootable LibertyBSD/OpenBSD USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg | tail + Check to confirm which drive it is, for example, if you think its sd3:\ $ disklabel sd3 diff --git a/docs/depthcharge/index.md b/docs/depthcharge/index.md index 745b5e8b..4828a390 100644 --- a/docs/depthcharge/index.md +++ b/docs/depthcharge/index.md @@ -10,6 +10,7 @@ This section relates to the depthcharge payload used in libreboot. - Booting from different mediums - Showing device information - Warnings + - [Recovery mode screen](#recovery_mode_screen) - [Recovering from a bad state](#recovering_bad_state) - [Enabling developer mode](#enabling_developer_mode) @@ -185,7 +186,8 @@ security of the device. The following parameters can be configured: - Kernels signature verification: - - Enabled with:\ + - Enabled with: + \# **crossystem dev\_boot\_signed\_only=1** - Disabled with:\ \# **crossystem dev\_boot\_signed\_only=0** diff --git a/docs/future/index.md b/docs/future/index.md index 3eacbc92..f15f40a8 100644 --- a/docs/future/index.md +++ b/docs/future/index.md @@ -15,6 +15,7 @@ Table of contents - [i945 VRAM size](#i945_vram_size) - [LCD panels on i945 - fix incompatible panels](#lcd_i945_incompatibility) + - [i945 X60/T60 VBT implementation (experimental: testing)](#i945_vbt) - [IntelVbtTool results](#intelvbttool_results) - [Fallback patches for i945](#fallback_patches) @@ -162,7 +163,8 @@ How to dump EDID: # modprobe i2c-dev Find out the correct ID to use: # i2cdetect -l\ -Example:\ +Example: + # i2cdump -y 2 0x50 Working panel: EDID dump from LG-Philips LP150E05-A2K1: diff --git a/docs/future/old.md b/docs/future/old.md index 8fc4e273..c68c4385 100644 --- a/docs/future/old.md +++ b/docs/future/old.md @@ -12,6 +12,7 @@ Table of contents - [X60 native graphics initialization (backlight controls)](#x60_native_notes) + - [T60 native graphics initialization (backlight controls)](#t60_native_notes) - [i945: 3D fix (based on 5927) for kernel 3.12+ on @@ -43,7 +44,8 @@ That's all! **This has also been backported into libreboot 5th release (line 1233 in src/mainboard/lenovo/x60/i915io.c)**. GNUtoo (Denis Carikli) told me about the register **BLC\_PWM\_CTL** and that you could set it to control backlight. I read that address using devmem2 while -running the VBIOS:\ +running the VBIOS: + # devmem2 0xe4361254 w The change is also included in libreboot 6. diff --git a/docs/git/index.md b/docs/git/index.md index 71faafc1..fe25cecf 100644 --- a/docs/git/index.md +++ b/docs/git/index.md @@ -16,6 +16,7 @@ the git repository. - [Get the full source code from metadata (git clone)](#build_meta) - [How to build "bucts" (for LenovoBIOS X60/X60S/X60T/T60)](#build_bucts) + - [How to build "flashrom"](#build_flashrom) - [How to build the ROM images](#build) @@ -63,7 +64,8 @@ First, [install the build dependencies](#build_dependencies). Since libreboot makes extensive use of git, you need to configure git properly. If you have not yet configured git, then the minimum -requirement is:\ +requirement is: + $ git config --global user.name "Your Name" $ git config --global user.email your@emailaddress.com This is what will also appear in git logs if you ever commit your own diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md index 8a3f4751..1ba9e366 100644 --- a/docs/gnulinux/configuring_parabola.md +++ b/docs/gnulinux/configuring_parabola.md @@ -19,6 +19,7 @@ Table of Contents - [Pacman command equivalents (compared to other package managers)](#pacman_commandequiv) - [your-freedom](#yourfreedom) + - [Add a user account](#useradd) - [System D](#systemd) - [Interesting repositories](#interesting_repos) @@ -126,7 +127,8 @@ Updating Parabola {#pacman_update} ----------------- In the end, I didn't change my configuration for pacman. When you are -updating, resync with the latest package names/versions:\ +updating, resync with the latest package names/versions: + # pacman -Syy (according to the wiki, -Syy is better than Sy because it refreshes the package list even if it appears to be up to date, which can be useful diff --git a/docs/gnulinux/encrypted_debian.md b/docs/gnulinux/encrypted_debian.md index 6dfb1435..9f65baa5 100644 --- a/docs/gnulinux/encrypted_debian.md +++ b/docs/gnulinux/encrypted_debian.md @@ -77,6 +77,7 @@ Choose 'Manual' partitioning: - Encryption key: passphrase - erase data: Yes (only choose 'No' if it's a new drive that doesn't contain your private data) + - Select 'configure encrypted volumes' - Create encrypted volumes - Select your partition diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index 2771bf34..c4e92c16 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -70,6 +70,7 @@ whole article and keep all points in mind, adapting them for this guide. Securely wipe the drive: # dd if=/dev/urandom of=/dev/sda; sync + NOTE: If you have an SSD, only do this the first time. If it was already LUKS-encrypted before, use the info below to wipe the LUKS header. Also, check online for your SSD what the recommended erase block size is. For @@ -82,7 +83,8 @@ header. showed me how to do this. It recommends doing the first 3MiB. Now, that guide is recommending putting zero there. I'm going to use urandom. Do -this:\ +this: + # head -c 3145728 /dev/urandom > /dev/sda; sync (Wiping the LUKS header is important, since it has hashed passphrases and so on. It's 'secure', but 'potentially' a risk). diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md index 1fd924b1..4609db97 100644 --- a/docs/gnulinux/grub_boot_installer.md +++ b/docs/gnulinux/grub_boot_installer.md @@ -28,8 +28,10 @@ Prepare the USB drive (in GNU+Linux) If you downloaded your ISO on an existing GNU+Linux system, here is how to create the bootable GNU+Linux USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg + Check lsblk to confirm which drive it is:\ $ lsblk diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md index 31192f5a..dbe55206 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -45,6 +45,7 @@ Table of Contents + Introduction ------------ @@ -142,7 +143,8 @@ your current firmware, using flashrom: $ sudo flashrom -p internal -r libreboot.rom # flashrom -p internal -r libreboot.rom If you are told to specify the chip, add the option **-c {your chip}** -to the command, for example:\ +to the command, for example: + # flashrom -c MX25L6405 -p internal -r libreboot.rom [Back to top of page.](#pagetop) diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md index 9c1a819d..81a3452b 100644 --- a/docs/gnulinux/grub_hardening.md +++ b/docs/gnulinux/grub_hardening.md @@ -31,6 +31,7 @@ image: cbfstool my.rom extract -n grubtest.cfg -f my.grubtest.cfg cbfstool my.rom remove -n grubtest.cfg + Helpful links: - [GRUB manual diff --git a/docs/gnulinux/index.md b/docs/gnulinux/index.md index 79983797..49c04dfd 100644 --- a/docs/gnulinux/index.md +++ b/docs/gnulinux/index.md @@ -10,6 +10,7 @@ instructions have yet to be written.** - [How to install GNU+Linux on a libreboot system](grub_boot_installer.html) + - [How to replace the default GRUB configuration file on a libreboot system](grub_cbfs.html) - [Installing Parabola or Arch GNU+Linux-libre with full disk diff --git a/docs/grub/index.md b/docs/grub/index.md index 81e4bd56..0c676da9 100644 --- a/docs/grub/index.md +++ b/docs/grub/index.md @@ -11,6 +11,7 @@ This section relates to the GRUB payload used in libreboot. + Changing the background image in GRUB {#grub_background} ===================================== @@ -47,7 +48,8 @@ like Debian, Devuan or Parabola. $ cd libreboot\_src/grub compile grub (the build scripts info on how to do this)\ -come back out into libreboot\_src/resources/grub:\ +come back out into libreboot\_src/resources/grub: + $ cd ../libreboot\_src/resources/grub/font I took Dejavu Sans Mono from dejavu (included in this version of diff --git a/docs/hardware/dock.md b/docs/hardware/dock.md index f1e86226..079a4e6f 100644 --- a/docs/hardware/dock.md +++ b/docs/hardware/dock.md @@ -8,6 +8,7 @@ Usually when people do full disk encryption, it's not really full disk, instead they still have a /boot in clear. + So an evil maid attack can still be done, in two passes: 1) Clone the hdd, Infect the initramfs or the kernel. 2) Wait for the user to enter its password, recover the password, diff --git a/docs/hardware/index.md b/docs/hardware/index.md index d7262669..f7a119dd 100644 --- a/docs/hardware/index.md +++ b/docs/hardware/index.md @@ -6,6 +6,7 @@ This section relates to hardware maintenance on supported targets. - [ThinkPad X60/X60s/X60T: Change keyboard](x60_keyboard.html) (the procedure on X200/X200S/X200T is almost identical) + - [ThinkPad X60/X60S: change the fan/heatsink](x60_heatsink.html) - [ThinkPad X60/X60s: How to change the LCD panel](x60_lcd_change.html) (incomplete. pics only for now) diff --git a/docs/hardware/t60_heatsink.md b/docs/hardware/t60_heatsink.md index f9fbde2b..a3ff52e3 100644 --- a/docs/hardware/t60_heatsink.md +++ b/docs/hardware/t60_heatsink.md @@ -11,6 +11,7 @@ Hardware requirements {#hardware_requirements} - rubbing alcohol or isopropyl alcohol, and thermal compound for changing CPU heatsink (procedure involves removing heatsink) + - thermal compound/paste (Arctic MX-4 is good. Others are also good.) diff --git a/docs/hardware/t60_security.md b/docs/hardware/t60_security.md index 6103c42d..974f8b43 100644 --- a/docs/hardware/t60_security.md +++ b/docs/hardware/t60_security.md @@ -231,6 +231,7 @@ Not covered yet: - Disable flashing the ethernet firmware - Disable SPI flash writes (can be re-enabled by unsoldering two parts) + - Disable use of xrandr/edid on external monitor (cut 2 pins on VGA) - Disable docking station (might be possible to do it in software, in coreboot upstream as a Kconfig option) @@ -248,7 +249,8 @@ half of the video to see how to do the above. Also not covered yet: --------------------- -- Intrusion detection: randomized seal on screws\ +- Intrusion detection: randomized seal on screws + Just put nail polish with lot of glider on the important screws, take some good pictures. Keep the pictueres and make sure of their integrity. Compare the nail polish with the pictures before powering diff --git a/docs/hardware/x60_heatsink.md b/docs/hardware/x60_heatsink.md index 35a9c48b..4493f954 100644 --- a/docs/hardware/x60_heatsink.md +++ b/docs/hardware/x60_heatsink.md @@ -22,6 +22,7 @@ Hardware requirements {#hardware_requirements} - your new fan and/or heatsink - CPU thermal compound (some say Arctic MX-4 is good, others are also 'ok') + - Something to spread the paste with diff --git a/docs/hardware/x60_security.md b/docs/hardware/x60_security.md index 1e9479ac..23dba9d0 100644 --- a/docs/hardware/x60_security.md +++ b/docs/hardware/x60_security.md @@ -137,6 +137,7 @@ Not covered yet: - Disable flashing the ethernet firmware - Disable SPI flash writes (can be re-enabled by unsoldering two parts) + - Disable use of xrandr/edid on external monitor (cut 2 pins on VGA) - Disable docking station (might be possible to do it in software, in coreboot upstream as a Kconfig option) @@ -152,7 +153,8 @@ half of the video to see how to do the above. Also not covered yet: --------------------- -- Intrusion detection: randomized seal on screws\ +- Intrusion detection: randomized seal on screws + Just put nail polish with lot of glider on the important screws, take some good pictures. Keep the pictueres and make sure of their integrity. Compare the nail polish with the pictures before powering diff --git a/docs/hcl/c201.md b/docs/hcl/c201.md index b04fb525..ddf293ee 100644 --- a/docs/hcl/c201.md +++ b/docs/hcl/c201.md @@ -22,6 +22,7 @@ Flashing instructions can be found at - [Considerations about ChromeOS and free operating systems](#os) - [Caution: Video acceleration requires a non-free blob, software rendering can be used instead.](#videoblobs) + - [Caution: WiFi requires a non-free blob, a USB dongle can be used instead.](#wifiblobs) - [EC firmware is free software!](#ec) diff --git a/docs/hcl/d945gclf.md b/docs/hcl/d945gclf.md index b2ef3cd0..7b2f95d9 100644 --- a/docs/hcl/d945gclf.md +++ b/docs/hcl/d945gclf.md @@ -33,6 +33,7 @@ Remarks about vendor bios: vendor bios is very bad. It cannot boot from any HDD wether it is connected to the SATA port or USB. With libreboot it works just fine. + - The vendor bios write protects the flash so it requires external flashing to install libreboot on this device. Once libreboot is flashed there is no problem to update the firmware internally diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md index c10c892e..485bf731 100644 --- a/docs/hcl/gm45_remove_me.md +++ b/docs/hcl/gm45_remove_me.md @@ -40,6 +40,7 @@ ich9gen executables can be found under ./ich9deblob/ statically compiled in libreboot\_util. If you are using src or git, build ich9gen from source with: $ ./oldbuild module ich9deblob + The executable will appear under resources/utilities/ich9deblob/ Run: @@ -68,7 +69,8 @@ the little sticker on the bottom/base of the laptop. On GM45 laptops that use flash descriptors, the MAC address or the onboard ethernet chipset is flashed (inside the ROM image). You should generate a descriptor+gbe image with your own MAC address inside (with -the Gbe checksum updated to match). Run:\ +the Gbe checksum updated to match). Run: + $ ./ich9gen --macaddress XX:XX:XX:XX:XX:XX (replace the XX chars with the hexadecimal chars in the MAC address that you want) diff --git a/docs/hcl/index.md b/docs/hcl/index.md index 8adb7fc4..6eb810ef 100644 --- a/docs/hcl/index.md +++ b/docs/hcl/index.md @@ -7,6 +7,7 @@ This sections relates to known hardware compatibility in libreboot. - [Servers/workstations](#supported_workstations_x86amd) - [Laptops (ARM)](#supported_laptops_arm) - [Laptops (Intel, x86)](#supported_laptops_x86intel) + - NOTES: - [Updating the EC firmware on i945 and GM45 (recommended)](#ecupdate) @@ -436,7 +437,8 @@ Referenced below are copies (up to date at the time of writing, the macbook2,1. They are included here in case the main site goes down for whatever reason, since they include a lot of useful information. -Backups created using wget:\ +Backups created using wget: + $ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/ **\$ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/coreboot/**\ diff --git a/docs/hcl/kcma-d8.md b/docs/hcl/kcma-d8.md index 901f190e..f8dab9c1 100644 --- a/docs/hcl/kcma-d8.md +++ b/docs/hcl/kcma-d8.md @@ -91,6 +91,7 @@ Current issues {#issues} can put a kernel in CBFS or on SATA and use that to boot GNU, which can be on a SAS drive. The linux kernel can use those SAS drives (via PIKE module) without an option ROM). + - IPMI iKVM module (optional add-on card) uses proprietary firmware. Since it's for remote out-of-band management, it's theoretically a backdoor similar to the Intel Management Engine. Fortunately, unlike diff --git a/docs/hcl/kfsn4-dre.md b/docs/hcl/kfsn4-dre.md index 34804c0f..84b8d455 100644 --- a/docs/hcl/kfsn4-dre.md +++ b/docs/hcl/kfsn4-dre.md @@ -70,6 +70,7 @@ Current issues {#issues} person says that they will look into it. [This config](http://review.coreboot.org/gitweb?p=board-status.git;a=blob;f=asus/kfsn4-dre/4.0-10101-g039edeb/2015-06-27T03:59:16Z/config.txt;h=4742905c185a93fbda8eb14322dd82c70641aef0;hb=055f5df4e000a97453dfad6c91c2d06ea22b8545) doesn't have the issue. + - Text-mode is a bit jittery (but still usable). (the jitter disappears if using KMS, once the kernel starts. The jitter will remain, if booting the kernel in text-mode). diff --git a/docs/hcl/kgpe-d16.md b/docs/hcl/kgpe-d16.md index 97a87a4b..b0490edc 100644 --- a/docs/hcl/kgpe-d16.md +++ b/docs/hcl/kgpe-d16.md @@ -92,6 +92,7 @@ Current issues {#issues} can put a kernel in CBFS or on SATA and use that to boot GNU, which can be on a SAS drive. The linux kernel can use those SAS drives (via PIKE module) without an option ROM). + - IPMI iKVM module (optional add-on card) uses proprietary firmware. Since it's for remote out-of-band management, it's theoretically a backdoor similar to the Intel Management Engine. Fortunately, unlike diff --git a/docs/hcl/t400.md b/docs/hcl/t400.md index c3e0d9d3..e3355f57 100644 --- a/docs/hcl/t400.md +++ b/docs/hcl/t400.md @@ -79,6 +79,7 @@ outputs from the T400: - T400 with **Winbond W25X64** flash chip (8MiB, SOIC-16) and Lenovo BIOS 2.02 (EC firmware 1.01): - [../future/dumps/logs-t400-bios2.02-ec1.01/](../future/dumps/logs-t400-bios2.02-ec1.01/) + - Version of flashrom used for the external flashing/reading logs is the one that libreboot git revision c164960 uses. diff --git a/docs/hcl/t500.md b/docs/hcl/t500.md index a17a6fc1..2b187e54 100644 --- a/docs/hcl/t500.md +++ b/docs/hcl/t500.md @@ -83,6 +83,7 @@ were something like: $ diff -u t500gbe x200gbe $ diff -u t500descriptor x200descriptor + ME VSCC table is in a different place and a different size on the T500. Libreboot disables and removes the ME anyway, so it doesn't matter. diff --git a/docs/hcl/x200.md b/docs/hcl/x200.md index deb212a9..4ab38cba 100644 --- a/docs/hcl/x200.md +++ b/docs/hcl/x200.md @@ -171,6 +171,7 @@ just simply remove the digitizer). - BOE-Hydis HV121WX4-120, HV121WX4-110 or HV121WX4-100 - cheap-ish, might be hard to find + - Samsung LTN121AP02-001 - common to find, cheap **If your X200 has an LED backlit panel in it, then you also need to get diff --git a/docs/index.md b/docs/index.md index d44b58e7..7b0280d7 100644 --- a/docs/index.md +++ b/docs/index.md @@ -32,6 +32,7 @@ Installing operating systems - [List of recommended GNU+Linux distributions for libreboot](distros/) + - [How to install GNU+Linux on a libreboot system](gnulinux/) - [How to install BSD on a libreboot system](bsd/) @@ -101,7 +102,8 @@ The libreboot project has three main goals: - ***Make coreboot easy to use***. Coreboot is notoriously difficult to install, due to an overall lack of user-focussed documentation and support. Most people will simply give up before attempting to - install coreboot.\ + install coreboot. + \ Libreboot attempts to bridge this divide, making sure that everything from building to installing coreboot is automated, as diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md index 4211777e..a52ea103 100644 --- a/docs/install/bbb_setup.md +++ b/docs/install/bbb_setup.md @@ -46,6 +46,7 @@ Shopping list (pictures of this hardware is shown later): 'Purchase'). We recommend this product because we know that it works well for our purposes and doesn't require any non-free software. + - Electrical/insulative tape: cover the entire bottom surface of the BBB (the part that rests on a surface). This is important, when placing the BBB on top of a board so that nothing shorts. Most @@ -208,7 +209,8 @@ contents of this file with: Run **apt-get update** and **apt-get upgrade** then reboot the BBB, before continuing. -Check that the firmware exists:\ +Check that the firmware exists: + # ls /lib/firmware/BB-SPI0-01-00A0.\* Output: diff --git a/docs/install/c201.md b/docs/install/c201.md index 23cbf1bc..1b15c284 100644 --- a/docs/install/c201.md +++ b/docs/install/c201.md @@ -37,6 +37,7 @@ root shell. parameters](#configuring_verified_boot_parameters) - [Removing the write protect screw](#removing_write_protect_screw) + - [Installing Libreboot to the SPI flash]() - [Installing Libreboot internally, from the device](#installing_libreboot_internally) @@ -153,7 +154,8 @@ The SPI flash has to be read first: **Note: it might be a good idea to copy the produced flash.img file at this point and store it outside of the device for backup purposes.** -Then, the **cros-flash-replace** script has to be executed as such:\ +Then, the **cros-flash-replace** script has to be executed as such: + # ./cros-flash-replace flash.img coreboot ro-frid If any error is shown, it is definitely a bad idea to go further than this point. diff --git a/docs/install/d510mo.md b/docs/install/d510mo.md index 572e7224..3a34bdbe 100644 --- a/docs/install/d510mo.md +++ b/docs/install/d510mo.md @@ -12,6 +12,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + [Back to top of page.](#pagetop) diff --git a/docs/install/ga-g41m-es2l.md b/docs/install/ga-g41m-es2l.md index c254d675..ba6a9a30 100644 --- a/docs/install/ga-g41m-es2l.md +++ b/docs/install/ga-g41m-es2l.md @@ -12,6 +12,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + [Back to top of page.](#pagetop) diff --git a/docs/install/index.md b/docs/install/index.md index c03237cf..55fbbe50 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -30,6 +30,7 @@ Setting up programmers, for external flashing via hardware method - [How to program an SPI flash chip with the BeagleBone Black](bbb_setup.html) + - [How to program an SPI flash chip with the Raspberry Pi](rpi_setup.html) @@ -278,7 +279,8 @@ How to update the flash chip contents: Ocassionally, coreboot changes the name of a given board. If flashrom complains about a board mismatch, but you are sure that you chose the -correct ROM image, then run this alternative command:\ +correct ROM image, then run this alternative command: + $ sudo ./flash forceupdate [yourrom.rom](#rom) diff --git a/docs/install/kcma-d8.md b/docs/install/kcma-d8.md index 7789c1c8..0e78b274 100644 --- a/docs/install/kcma-d8.md +++ b/docs/install/kcma-d8.md @@ -17,6 +17,7 @@ TODO: show photos here, and other info. - [kcma-d8 boards (and full systems) with libreboot preinstalled](#preinstall) + - [External programmer](#programmer) diff --git a/docs/install/kgpe-d16.md b/docs/install/kgpe-d16.md index f9751f14..ed470a15 100644 --- a/docs/install/kgpe-d16.md +++ b/docs/install/kgpe-d16.md @@ -17,6 +17,7 @@ TODO: show photos here, and other info. - [KGPE-D16 boards (and full systems) with libreboot preinstalled](#preinstall) + - [External programmer](#programmer) diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md index 7f2e7c2c..40e49415 100644 --- a/docs/install/r400_external.md +++ b/docs/install/r400_external.md @@ -73,6 +73,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + [Back to top of page.](#pagetop) @@ -252,7 +253,8 @@ factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* have been removed.\ -Now compare the 3 images:\ +Now compare the 3 images: + # sha512sum factory\*.rom If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md index 01cab733..9240038c 100644 --- a/docs/install/rpi_setup.md +++ b/docs/install/rpi_setup.md @@ -43,6 +43,7 @@ Guide](http://libreboot.org/docs/install/t60_unbrick.html). - On the X60, the BIOS chip is on the bottom of the motherboard, under a layer of protective black tape. + - On the T60, the BIOS chip is just under the palmrest, but blocked by a magnesium frame (which you will have to remove). diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md index 2f8c424f..4ddb6793 100644 --- a/docs/install/t400_external.md +++ b/docs/install/t400_external.md @@ -78,6 +78,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + [Back to top of page.](#pagetop) @@ -258,7 +259,8 @@ factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* have been removed.\ -Now compare the 3 images:\ +Now compare the 3 images: + # sha512sum factory\*.rom If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md index 05e4c112..2c350081 100644 --- a/docs/install/t500_external.md +++ b/docs/install/t500_external.md @@ -68,6 +68,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + [Back to top of page.](#pagetop) @@ -263,7 +264,8 @@ factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* have been removed.\ -Now compare the 3 images:\ +Now compare the 3 images: + # sha512sum factory\*.rom If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This diff --git a/docs/install/t60_unbrick.md b/docs/install/t60_unbrick.md index fc7a557f..309385b4 100644 --- a/docs/install/t60_unbrick.md +++ b/docs/install/t60_unbrick.md @@ -17,6 +17,7 @@ Table of Contents + Brick type 1: bucts not reset. {#bucts_brick} ============================== diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md index ac199b2a..78048867 100644 --- a/docs/install/x200_external.md +++ b/docs/install/x200_external.md @@ -36,6 +36,7 @@ Flash chip size {#flashchips} Use this to find out: # flashrom -p internal -V + The X200S and X200 Tablet will use a WSON-8 flash chip, on the bottom of the motherboard (this requires removal of the motherboard). **Not all X200S/X200T are supported; see @@ -192,7 +193,8 @@ factory2.rom**\ Note: the **-c** option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in *flashchips.c* have been removed.\ -Now compare the 3 images:\ +Now compare the 3 images: + # sha512sum factory\*.rom If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md index 33a4fef3..b6710a99 100644 --- a/docs/install/x60_unbrick.md +++ b/docs/install/x60_unbrick.md @@ -17,6 +17,7 @@ Table of Contents + Brick type 1: bucts not reset. {#bucts_brick} ============================== diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md index cc62ecaf..0a1801b1 100644 --- a/docs/install/x60tablet_unbrick.md +++ b/docs/install/x60tablet_unbrick.md @@ -17,6 +17,7 @@ Table of Contents + Brick type 1: bucts not reset. {#bucts_brick} ============================== diff --git a/docs/misc/bbb_ehci.md b/docs/misc/bbb_ehci.md index 4833ff93..51fd40df 100644 --- a/docs/misc/bbb_ehci.md +++ b/docs/misc/bbb_ehci.md @@ -9,6 +9,7 @@ EHCI debugging 1. [Find USB port on the target that supports EHCI debug](#FindUSBportonthetargetthatsupportsEHCIdebug) + 2. [Initial setup of BBB to act as EHCI debug dongle](#InitialsetupofBBBtoactasEHCIdebugdongle) 3. [Patch BBB's `g_dbgp` module (optional, but highly diff --git a/docs/misc/index.md b/docs/misc/index.md index 7d73569b..afffbbeb 100644 --- a/docs/misc/index.md +++ b/docs/misc/index.md @@ -3,6 +3,7 @@ - [High Pitched Whining Noise on Idle (how to remove in Debian or Devuan)](#debian_powertop) + - [High Pitched Whining Noise on Idle (how to remove in Parabola)](#high_pitch_parabola) - [X60/T60: Serial port - how to use (for dock owners)](#serial) @@ -57,7 +58,8 @@ On the X60 with coreboot or libreboot, there is a high pitched sound when idle. So far we have use processor.max\_cstate=2 or idle=halt in GRUB. These consume power. Stop using them! -Be root\ +Be root + $ su - Installed powertop:\ diff --git a/docs/misc/patch.md b/docs/misc/patch.md index 9f22f776..a8dffc92 100644 --- a/docs/misc/patch.md +++ b/docs/misc/patch.md @@ -9,9 +9,11 @@ This is just a quick guide for reference, use 'man' to know more. Apply a patch ============= -To apply a patch to a single file, do that in it's directory:\ +To apply a patch to a single file, do that in it's directory: + $ patch < foo.patch + Assuming that the patch is distributed in unified format identifying the file the patch should be applied to, the above will work. Otherwise:\ $ patch foo.txt < bar.patch diff --git a/docs/release.md b/docs/release.md index bb7266a0..5476a63a 100644 --- a/docs/release.md +++ b/docs/release.md @@ -30,6 +30,7 @@ Other bugfixes: - re-added "unset superusers" to the grub.cfg, which was needed for some users depending on the distros that they used + Libreboot 20160902 {#release20160922} ================== diff --git a/www/amd-libre.md b/www/amd-libre.md index 31721c9a..62302eb9 100644 --- a/www/amd-libre.md +++ b/www/amd-libre.md @@ -13,6 +13,7 @@ tell them that you demand libre hardware: - - (has contact links for multiple countries) + - **AMD's CEO, Lisa Su, can be contacted directly via email. Tell her that you demand libre hardware: ** diff --git a/www/faq.md b/www/faq.md index 8eb8df8d..b2a9f239 100644 --- a/www/faq.md +++ b/www/faq.md @@ -40,6 +40,7 @@ service when you connect the ethernet cable: sudo service network-manager restart + On Parabola, you can try: sudo systemctl restart network-manager diff --git a/www/git.md b/www/git.md index 747e013d..ba368f8b 100644 --- a/www/git.md +++ b/www/git.md @@ -34,6 +34,7 @@ Not a developer? You can still help! - Work towards convincing hardware manufacturers and designers to start caring about free software. Perhaps even build your own hardware. + - Spread the word about libreboot! Tell your friends about it, and talk about it on public internet-based discussion networks (e.g. *social networks*). diff --git a/www/gpg.md b/www/gpg.md index b8b7a71f..34453364 100644 --- a/www/gpg.md +++ b/www/gpg.md @@ -4,6 +4,7 @@ title: GPG $ gpg --recv-keys + The GPG key can also be downloaded with this exported dump of the pubkey: [lbkey.asc](lbkey.asc). diff --git a/www/lists.md b/www/lists.md index 70a63061..3c25c6fd 100644 --- a/www/lists.md +++ b/www/lists.md @@ -23,6 +23,7 @@ Backup of old Libreboot mailing lists - [User mailing list (HTML)](old/libreboot/html/lists.gnu.org/archive/html/libreboot) + - [User mailing list (mbox format)](old/libreboot/mbox/lists.gnu.org/libreboot/) - [Developer mailing list -- cgit v1.2.3-70-g09d2 From 6caf836e3390faefaad8257b9cec2eb97bdbfb41 Mon Sep 17 00:00:00 2001 From: Alyssa Rosenzweig Date: Mon, 3 Apr 2017 10:23:37 -0700 Subject: Global fix --- docs/archive_old.md | 12 ++- docs/bsd/freebsd.md | 21 ++-- docs/bsd/netbsd.md | 21 ++-- docs/bsd/openbsd.md | 21 ++-- docs/depthcharge/index.md | 24 +++-- docs/future/index.md | 3 +- docs/git/index.md | 57 +++++++---- docs/gnulinux/configuring_parabola.md | 120 +++++++++++++++-------- docs/gnulinux/encrypted_parabola.md | 174 ++++++++++++++++++++++------------ docs/gnulinux/grub_boot_installer.md | 21 ++-- docs/gnulinux/grub_cbfs.md | 15 ++- docs/grub/index.md | 3 +- docs/hcl/gm45_remove_me.md | 12 ++- docs/index.md | 15 ++- docs/install/bbb_setup.md | 9 +- docs/install/c201.md | 15 ++- docs/install/index.md | 9 +- docs/misc/index.md | 18 ++-- docs/misc/patch.md | 33 ++++--- 19 files changed, 402 insertions(+), 201 deletions(-) (limited to 'docs/hcl') diff --git a/docs/archive_old.md b/docs/archive_old.md index 54d9c620..c9d2c7fe 100644 --- a/docs/archive_old.md +++ b/docs/archive_old.md @@ -627,7 +627,8 @@ Revisions for r20140903 (6th beta) (3rd September 2014) - Added gcry\_serpent and gcry\_whirlpool to the GRUB module list in the 'build' script (for luks users) - **Libreboot is now based on a new coreboot version from August 23rd, - 2014:\ + 2014: + Merged commits (relates to boards that were already supported in libreboot):** - @@ -748,10 +749,13 @@ Revisions for r20140903 (6th beta) (3rd September 2014) ohci, uhci, usb, usbserial\_pl2303, usbserial\_ftdi, usbserial\_usbdebug - set prefix=(memdisk)/boot/grub - - For native graphics (recommended by coreboot wiki):\ - gfxpayload=keep\ + - For native graphics (recommended by coreboot wiki): + + gfxpayload=keep + terminal\_output --append gfxterm - - Play a beep on startup:\ + - Play a beep on startup: + play 480 440 1 - Documentation: updated gnulinux/grub\_cbfs.html to make it safer (and easier) to follow. diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md index 31d9df17..50923d26 100644 --- a/docs/bsd/freebsd.md +++ b/docs/bsd/freebsd.md @@ -63,15 +63,18 @@ Connect the USB drive. Check dmesg: $ dmesg | tail -Check to confirm which drive it is, for example, if you think its sd3:\ +Check to confirm which drive it is, for example, if you think its sd3: + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For -example:\ +example: + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the -FreeBSD installer to it with dd. For example:\ +FreeBSD installer to it with dd. For example: + $ doas dd if=freebsd.img of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. @@ -85,18 +88,22 @@ Prepare the USB drive (in GNU+Linux) If you downloaded your ISO on a GNU+Linux system, here is how to create the bootable FreeBSD USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg -Check lsblk to confirm which drive it is:\ +Check lsblk to confirm which drive it is: + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For -example:\ +example: + $ sudo umount /dev/sdX\* # umount /dev/sdX\* dmesg told you what device it is. Overwrite the drive, writing your -distro ISO to it with dd. For example:\ +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 diff --git a/docs/bsd/netbsd.md b/docs/bsd/netbsd.md index 3046ef00..f632eec5 100644 --- a/docs/bsd/netbsd.md +++ b/docs/bsd/netbsd.md @@ -59,15 +59,18 @@ Connect the USB drive. Check dmesg: $ dmesg | tail -Check to confirm which drive it is, for example, if you think its sd3:\ +Check to confirm which drive it is, for example, if you think its sd3: + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For -example:\ +example: + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the -NetBSD installer to it with dd. For example:\ +NetBSD installer to it with dd. For example: + $ doas netbsd.iso of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. @@ -81,18 +84,22 @@ Prepare the USB drive (in GNU+Linux) If you downloaded your ISO on a GNU+Linux system, here is how to create the bootable NetBSD USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg -Check lsblk to confirm which drive it is:\ +Check lsblk to confirm which drive it is: + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For -example:\ +example: + $ sudo umount /dev/sdX\* # umount /dev/sdX\* dmesg told you what device it is. Overwrite the drive, writing your -distro ISO to it with dd. For example:\ +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 diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md index 4440b665..461a38d6 100644 --- a/docs/bsd/openbsd.md +++ b/docs/bsd/openbsd.md @@ -41,15 +41,18 @@ Connect the USB drive. Check dmesg: $ dmesg | tail -Check to confirm which drive it is, for example, if you think its sd3:\ +Check to confirm which drive it is, for example, if you think its sd3: + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For -example:\ +example: + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the -OpenBSD installer to it with dd. For example:\ +OpenBSD installer to it with dd. For example: + $ doas dd if=install60.fs of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. @@ -80,18 +83,22 @@ Prepare the USB drive (in GNU+Linux) If you downloaded your ISO on a GNU+Linux system, here is how to create the bootable OpenBSD USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg -Check lsblk to confirm which drive it is:\ +Check lsblk to confirm which drive it is: + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For -example:\ +example: + $ sudo umount /dev/sdX\* # umount /dev/sdX\* dmesg told you what device it is. Overwrite the drive, writing your -distro ISO to it with dd. For example:\ +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 diff --git a/docs/depthcharge/index.md b/docs/depthcharge/index.md index 4828a390..13367056 100644 --- a/docs/depthcharge/index.md +++ b/docs/depthcharge/index.md @@ -189,24 +189,32 @@ The following parameters can be configured: - Enabled with: \# **crossystem dev\_boot\_signed\_only=1** - - Disabled with:\ + - Disabled with: + \# **crossystem dev\_boot\_signed\_only=0** - External media boot: - - Enabled with:\ + - Enabled with: + \# **crossystem dev\_boot\_usb=1** - - Disabled with:\ + - Disabled with: + \# **crossystem dev\_boot\_usb=0** - Legacy payload boot: - - Enabled with:\ + - Enabled with: + \# **crossystem dev\_boot\_legacy=1** - - Disabled with:\ + - Disabled with: + \# **crossystem dev\_boot\_legacy=0** - Default boot medium: - - Internal storage:\ + - Internal storage: + \# **crossystem dev\_default\_boot=disk** - - External media:\ + - External media: + \# **crossystem dev\_default\_boot=usb** - - Legacy payload:\ + - Legacy payload: + \# **crossystem dev\_default\_boot=legacy** diff --git a/docs/future/index.md b/docs/future/index.md index f15f40a8..aa5b0da9 100644 --- a/docs/future/index.md +++ b/docs/future/index.md @@ -326,7 +326,8 @@ Get intelvbttool here: Now dump a copy of the running VGA BIOS: **\$ sudo dd if=/dev/mem bs=64k of=runningvga.bin skip=12 count=1**\ -Then do (and record the output):\ +Then do (and record the output): + $ ./intelvbttool runningvga.bin > intelvbttool\_out Backup both files (runningvga.bin and intelvbttool\_out), renaming them diff --git a/docs/git/index.md b/docs/git/index.md index fe25cecf..65755138 100644 --- a/docs/git/index.md +++ b/docs/git/index.md @@ -72,14 +72,16 @@ This is what will also appear in git logs if you ever commit your own changes to a given repository. For more information, see . -Another nice config for you (optional, but recommended):\ +Another nice config for you (optional, but recommended): + $ git config --global core.editor nano $ git config --global color.status auto $ git config --global color.branch auto $ git config --global color.interactive auto $ git config --global color.diff auto -After that, run the script:\ +After that, run the script: + $ ./download all What this did was download everything (grub, coreboot, memtest86+, @@ -138,10 +140,12 @@ If you have the binary release archive, you'll find executables under First, [install the build dependencies](#build_dependencies). -To build bucts, do this in the main directory:\ +To build bucts, do this in the main directory: + $ ./oldbuild module bucts -To statically compile it, do this:\ +To statically compile it, do this: + $ ./oldbuild module bucts static The "builddeps" script in libreboot\_src also makes use of @@ -169,10 +173,12 @@ flashrom from source, continue reading. First, [install the build dependencies](#build_dependencies). -To build it, do the following in the main directory:\ +To build it, do the following in the main directory: + $ ./oldbuild module flashrom -To statically compile it, do the following in the main directory:\ +To statically compile it, do the following in the main directory: + $ ./oldbuild module flashrom static After you've done that, under ./flashrom/ you will find the following @@ -216,24 +222,29 @@ First, [install the build dependencies](#build_dependencies). If you downloaded libreboot from git, refer to [\#build\_meta](#build_meta). -Build all of the components used in libreboot:\ +Build all of the components used in libreboot: + $ ./oldbuild module all You can also build each modules separately, using *./oldbuild module -modulename*. To see the possible values for *modulename*, use:\ +modulename*. To see the possible values for *modulename*, use: + $ ./oldbuild module list -After that, build the ROM images (for all boards):\ +After that, build the ROM images (for all boards): + $ ./oldbuild roms withgrub Alternatively, you can build for a specific board or set of boards. For -example:\ +example: + $ ./oldbuild roms withgrub x60 $ ./oldbuild roms withgrub x200\_8mb $ ./oldbuild roms withgrub x60 x200\_8mb The list of board options can be found by looking at the directory names in **resources/libreboot/config/grub/**. -To clean (reverse) everything, do the following:\ +To clean (reverse) everything, do the following: + $ ./oldbuild clean all The ROM images will be stored under **bin/*payload*/**, where *payload* @@ -261,23 +272,29 @@ Tag the current commit, and that version will appear in both the in the file names of the archives. Otherwise, whatever git uses for *git describe --tags HEAD* will be used. -Utilities (static executables):\ +Utilities (static executables): + $ ./oldbuild release util -Archive containing flashrom and bucts source code:\ +Archive containing flashrom and bucts source code: + $ ./oldbuild release tobuild Documentation archive (**does not work on \_src release archive, only -git**):\ +git**): + $ ./oldbuild release docs -ROM image archives:\ +ROM image archives: + $ ./oldbuild release roms -Source code archive:\ +Source code archive: + $ ./oldbuild release src -SHA512 sums of all other release archives that have been generated:\ +SHA512 sums of all other release archives that have been generated: + $ ./oldbuild release sha512sums If you are building on an i686 host, this will build statically linked @@ -306,7 +323,8 @@ libreboot\_util, for: - flashrom If you are building binaries on a live system or chroot (for -flashrom/bucts), you can use the following to statically link them:\ +flashrom/bucts), you can use the following to statically link them: + $ ./oldbuild module flashrom static $ ./oldbuild module bucts static @@ -317,7 +335,8 @@ an X60/T60 while lenovo bios is present, working around the security restrictions). The command that you used for generating the release archives will also -run the following command:\ +run the following command: + $ ./oldbuild release tobuild The archive **tobuild.tar.xz** will have been created under **release/oldbuildsystem/**, containing bucts, flashrom and all other diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md index 1ba9e366..0c35eacd 100644 --- a/docs/gnulinux/configuring_parabola.md +++ b/docs/gnulinux/configuring_parabola.md @@ -133,7 +133,8 @@ updating, resync with the latest package names/versions: (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:\ +Then, update the system: + # pacman -Syu **Before installing packages with 'pacman -S', always update first, @@ -198,7 +199,8 @@ once in a while, to prevent it from growing too big (it's a cache of old package information, updated automatically when you do anything in pacman).** -To clean out all old packages that are cached:\ +To clean out all old packages that are cached: + # pacman -Sc The wiki cautions that this should be used with care. For example, since @@ -207,7 +209,8 @@ want to revert back to an older package then it's useful to have the caches available. Only do this if you are sure that you won't need it. The wiki also mentions this method for removing everything from the -cache, including currently installed packages that are cached:\ +cache, including currently installed packages that are cached: + # pacman -Scc This is inadvisable, since it means re-downloading the package again if you wanted to quickly re-install it. This should only be used when disk @@ -253,9 +256,11 @@ access to the entire operating system. Read the entire document linked to above, and then continue. -Add your user:\ +Add your user: + # useradd -m -G wheel -s /bin/bash *yourusername* -Set a password:\ +Set a password: + # passwd *yourusername* Use of the *diceware method* is recommended, for generating secure @@ -282,7 +287,8 @@ sshd (openssh), dhcp, etc. There are countless others. the background behind the decision by Arch (Parabola's upstream supplier) to use systemd. -The manpage should also help:\ +The manpage should also help: + # man systemd The section on 'unit types' is especially useful. @@ -302,7 +308,8 @@ The wiki also recommended a method for forwarding journal output to TTY 12 (accessible by pressing ctrl+alt+f12, and you use ctrl+alt+\[F1-F12\] to switch between terminals). I decided not to enable it. -Restart journald:\ +Restart journald: + # systemctl restart systemd-journald The wiki recommends that if the journal gets too large, you can also @@ -313,9 +320,11 @@ delete older records when the journal size reaches it's limit (according to systemd developers). Finally, the wiki mentions 'temporary' files and the utility for -managing them.\ +managing them. + # man systemd-tmpfiles -The command for 'clean' is:\ +The command for 'clean' is: + # systemd-tmpfiles --clean According to the manpage, this *"cleans all files and directories with an age parameter"*. According to the Arch wiki, this reads information @@ -325,7 +334,8 @@ 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:\ +etc.conf, containing information and a reference to this manpage: + # man tmpfiles.d Read that manpage, and then continue studying all the files. @@ -350,10 +360,12 @@ and below the 'extra' section add:\ *\[kernels\]\ Include = /etc/pacman.d/mirrorlist* -Now sync with the repository:\ +Now sync with the repository: + # pacman -Syy -List all available packages in this repository:\ +List all available packages in this repository: + # pacman -Sl kernels In the end, I decided not to install anything from it but I kept the @@ -374,10 +386,12 @@ Read . 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):\ +you like): + # hostnamectl set-hostname *yourhostname* This writes the specified hostname to /etc/hostname. More information -can be found in these manpages:\ +can be found in these manpages: + # man hostname # info hostname # man hostnamectl @@ -401,7 +415,8 @@ According to the Arch wiki, [udev](https://wiki.archlinux.org/index.php/Udev) should already detect the ethernet chipset and load the driver for it automatically at boot time. You can check this in the *"Ethernet controller"* section when -running this command:\ +running this command: + # lspci -v Look at the remaining sections *'Kernel driver in use'* and *'Kernel @@ -410,7 +425,8 @@ modules'*. In my case it was as follows:\ Kernel modules: e1000e* Check that the driver was loaded by issuing *dmesg | grep module\_name*. -In my case, I did:\ +In my case, I did: + # dmesg | grep e1000e ### Network device names {#network_devicenames} @@ -432,7 +448,8 @@ instructions in [grub\_cbfs.html](grub_cbfs.html)). For background information, read [Predictable Network Interface Names](http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/) -Show device names:\ +Show device names: + # ls /sys/class/net Changing the device names is possible (I chose not to do it):\ @@ -464,7 +481,8 @@ 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):\ +data comes from it. Therefore, don't rely on it too much): + # pacman -S smartmontools Read to learn how to use it. @@ -489,27 +507,33 @@ provide LXDE by default. Based on . -Firstly, install it!\ +Firstly, install it! + # pacman -S xorg-server I also recommend installing this (contains lots of useful tools, -including *xrandr*):\ +including *xrandr*): + # pacman -S xorg-server-utils Install the driver. For me this was *xf86-video-intel* on the ThinkPad -X60. T60 and macbook11/21 should be the same.\ +X60. T60 and macbook11/21 should be the same. + # pacman -S xf86-video-intel -For other systems you can try:\ +For other systems you can try: + # pacman -Ss xf86-video- | less Combined with looking at your *lspci* output, you can determine which driver is needed. By default, Xorg will revert to xf86-video-vesa which is a generic driver and doesn't provide true hardware acceleration. Other drivers (not just video) can be found by looking at the -*xorg-drivers* group:\ +*xorg-drivers* group: + # pacman -Sg xorg-drivers Mostly you will rely on a display manager, but in case you ever want to -start X without one:\ +start X without one: + # pacman -S xorg-xinit \ @@ -537,7 +561,8 @@ will notice that the layout you set in /etc/vconsole.conf earlier might not actually be the same in X. To see what layout you currently use, try this on a terminal emulator in -X:\ +X: + # setxkbmap -print -verbose 10 In my case, I wanted to use the Dvorak (UK) keyboard which is quite @@ -584,27 +609,34 @@ would like to try something different, refer to Refer to . -Install it, choosing 'all' when asked for the default package list:\ +Install it, choosing 'all' when asked for the default package list: + # pacman -S lxde obconf -I didn't want the following, so I removed them:\ +I didn't want the following, so I removed them: + # pacman -R lxmusic lxtask -I also lazily installed all fonts:\ +I also lazily installed all fonts: + # pacman -S \$(pacman -Ssq ttf-) -And a mail client:\ +And a mail client: + # pacman -S icedove In IceCat, go to *Preferences :: Advanced* and disable *GNU IceCat Health Report*. -I also like to install these:\ +I also like to install these: + # pacman -S xsensors stress htop -Enable LXDM (the default display manager, providing a graphical login):\ +Enable LXDM (the default display manager, providing a graphical login): + # systemctl enable lxdm.service -It will start when you boot up the system. To start it now, do:\ +It will start when you boot up the system. To start it now, do: + # systemctl start lxdm.service Log in with your standard (non-root) user that you created earlier. It @@ -649,7 +681,8 @@ NOTE TO SELF: come back to this later. ### LXDE - screenlock {#lxde_screenlock} -Arch wiki recommends to use *xscreensaver*:\ +Arch wiki recommends to use *xscreensaver*: + # pacman -S xscreensaver Under *Preferences :: Screensaver* in the LXDE menu, I chose *Mode: @@ -700,30 +733,37 @@ cursor over it, it'll show information about the battery. Refer to . Then I read: . -Install Network Manager:\ +Install Network Manager: + # pacman -S networkmanager -You will also want the graphical applet:\ +You will also want the graphical applet: + # pacman -S network-manager-applet Arch wiki says that an autostart rule will be written at */etc/xdg/autostart/nm-applet.desktop* I want to be able to use a VPN at some point, so the wiki tells me to -do:\ +do: + # pacman -S networkmanager-openvpn LXDE uses openbox, so I refer to:\ . -It tells me for the applet I need:\ +It tells me for the applet I need: + # pacman -S xfce4-notifyd gnome-icon-theme -Also, for storing authentication details (wifi) I need:\ +Also, for storing authentication details (wifi) I need: + # pacman -S gnome-keyring -I wanted to quickly enable networkmanager:\ +I wanted to quickly enable networkmanager: + # systemctl stop dhcpcd # systemctl start NetworkManager -Enable NetworkManager at boot time:\ +Enable NetworkManager at boot time: + # 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 c4e92c16..bf944a14 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -95,7 +95,8 @@ Change keyboard layout ---------------------- Parabola live shell assumes US Qwerty. If you have something different, -list the available keymaps and use yours:\ +list the available keymaps and use yours: + # localectl list-keymaps # loadkeys LAYOUT For me, LAYOUT would have been dvorak-uk. @@ -124,7 +125,8 @@ dm-mod ------ device-mapper will be used - a lot. Make sure that the kernel module is -loaded:\ +loaded: + # modprobe dm-mod Create LUKS partition @@ -138,7 +140,8 @@ prepared cryptsetup command below. Note that the iteration time is for security purposes (mitigates brute force attacks), so anything lower than 5 seconds is probably not ok. -I am using MBR partitioning, so I use cfdisk:\ +I am using MBR partitioning, so I use cfdisk: + # cfdisk /dev/sda I create a single large sda1 filling the whole drive, leaving it as the @@ -151,15 +154,18 @@ I am then directed to Parabola forces you to RTFM. Do that. -It tells me to run:\ +It tells me to run: + # cryptsetup benchmark (for making sure the list below is populated)\ -Then:\ +Then: + # cat /proc/crypto This gives me crypto options that I can use. It also provides a representation of the best way to set up LUKS (in this case, security is a priority; speed, a distant second). To gain a better understanding, I -am also reading:\ +am also reading: + # man cryptsetup Following that page, based on my requirements, I do the following based @@ -186,29 +192,36 @@ Create LVM Now I refer to . -Open the LUKS partition:\ +Open the LUKS partition: + # cryptsetup luksOpen /dev/sda1 lvm (it will be available at /dev/mapper/lvm) -Create LVM partition:\ +Create LVM partition: + # pvcreate /dev/mapper/lvm -Show that you just created it:\ +Show that you just created it: + # pvdisplay Now I create the volume group, inside of which the logical volumes will -be created:\ +be created: + # vgcreate matrix /dev/mapper/lvm (volume group name is 'matrix' - choose your own name, if you like) -Show that you created it:\ +Show that you created it: + # vgdisplay -Now create the logical volumes:\ +Now create the logical volumes: + # lvcreate -L 2G matrix -n swapvol (2G swap partition, named swapvol)\ Again, choose your own name if you like. Also, make sure to choose a swap size of your own needs. It basically depends on how much RAM you have installed. I refer to -.\ +. + # 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 /, @@ -218,7 +231,8 @@ fills up with logs, it won't crash your system). For a home/laptop system (typical use case), a root and a swap will do (really). Verify that the logical volumes were created, using the following -command:\ +command: + # lvdisplay @@ -226,15 +240,19 @@ command:\ Create / and swap partitions, and mount --------------------------------------- -For the swapvol LV I use:\ +For the swapvol LV I use: + # mkswap /dev/mapper/matrix-swapvol -Activate swap:\ +Activate swap: + # swapon /dev/matrix/swapvol -For the root LV I use:\ +For the root LV I use: + # mkfs.btrfs /dev/mapper/matrix-root -Mount the root (/) partition:\ +Mount the root (/) partition: + # mount /dev/matrix/root /mnt @@ -249,7 +267,8 @@ Now I am following the rest of . I also cross referenced . -Create /home and /boot on root mountpoint:\ +Create /home and /boot on root mountpoint: + # mkdir -p /mnt/home # mkdir -p /mnt/boot @@ -258,7 +277,8 @@ 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:\ +server)) and then did: + # pacman -Syy # pacman -Syu # pacman -Sy pacman (and then I did the other 2 steps above, @@ -312,21 +332,26 @@ Configure the system Generate an fstab - UUIDs are used because they have certain advantages (see . If you -prefer labels instead, replace the -U option with -L):\ +prefer labels instead, replace the -U option with -L): + # genfstab -U -p /mnt >> /mnt/etc/fstab -Check the created file:\ +Check the created file: + # cat /mnt/etc/fstab (If there are any errors, edit the file. Do **NOT** run the genfstab command again!) -Chroot into new system:\ +Chroot into new system: + # arch-chroot /mnt /bin/bash -It's a good idea to have this installed:\ +It's a good idea to have this installed: + # pacman -S linux-libre-lts It was also suggested that you should install this kernel (read up on -what GRSEC is):\ +what GRSEC is): + # pacman -S linux-libre-grsec This is another kernel that sits inside /boot, which you can use. LTS @@ -334,35 +359,43 @@ means 'long-term support'. These are so-called 'stable' kernels that can be used as a fallback during updates, if a bad kernel causes issues for you. -Parabola does not have wget. This is sinister. Install it:\ +Parabola does not have wget. This is sinister. Install it: + # pacman -S wget -Locale:\ +Locale: + # vi /etc/locale.gen Uncomment your needed localisations. For example en\_GB.UTF-8 (UTF-8 is -highly recommended over other options).\ +highly recommended over other options). + # locale-gen # echo LANG=en\_GB.UTF-8 > /etc/locale.conf # export LANG=en\_GB.UTF-8 -Console font and keymap:\ +Console font and keymap: + # vi /etc/vconsole.conf In my case: KEYMAP=dvorak-uk FONT=lat9w-16 -Time zone:\ +Time zone: + # ln -s /usr/share/zoneinfo/Europe/London /etc/localtime (Replace Zone and Subzone to your liking. See /usr/share/zoneinfo) -Hardware clock:\ +Hardware clock: + # hwclock --systohc --utc Hostname: Write your hostname to /etc/hostname. For example, if your -hostname is parabola:\ +hostname is parabola: + # echo parabola > /etc/hostname -Add the same hostname to /etc/hosts:\ +Add the same hostname to /etc/hosts: + # vi /etc/hosts # @@ -376,7 +409,8 @@ Mkinitcpio: Configure /etc/mkinitcpio.conf as needed (see ). Runtime modules can be found in /usr/lib/initcpio/hooks, and build hooks can be found in /usr/lib/initcpio/install. (\# **mkinitcpio -H hookname** gives -information about each hook.) Specifically, for this use case:\ +information about each hook.) Specifically, for this use case: + # vi /etc/mkinitcpio.conf Then modify the file like so: @@ -401,18 +435,23 @@ 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):\ +linux): + # mkinitcpio -p linux-libre -Also do it for linux-libre-lts:\ +Also do it for linux-libre-lts: + # mkinitcpio -p linux-libre-lts -Also do it for linux-libre-grsec:\ +Also do it for linux-libre-grsec: + # mkinitcpio -p linux-libre-grsec Set the root password: At the time of writing, Parabola used SHA512 by default for its password hashing. I referred to -.\ +. + # vi /etc/pam.d/passwd -Add rounds=65536 at the end of the uncommented 'password' line.\ +Add rounds=65536 at the end of the uncommented 'password' line. + # passwd root Make sure to set a secure password! Also, it must never be the same as your LUKS password. @@ -427,7 +466,8 @@ Extra security tweaks Based on . -Restrict access to important directories:\ +Restrict access to important directories: + # chmod 700 /boot /etc/{iptables,arptables} Lockout user after three failed login attempts:\ @@ -437,7 +477,8 @@ 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:\ +do: + # pam\_tally --user *theusername* --reset What the above configuration does is lock the user out for 10 minutes, if they make 3 failed login attempts. @@ -451,18 +492,22 @@ don't really need sudo. Unmount, reboot! ---------------- -Exit from chroot:\ +Exit from chroot: + # exit -unmount:\ +unmount: + # umount -R /mnt # swapoff -a -deactivate the lvm lv's:\ +deactivate the lvm lv's: + # lvchange -an /dev/matrix/root # lvchange -an /dev/matrix/swapvol -Lock the encrypted partition (close it):\ +Lock the encrypted partition (close it): + # cryptsetup luksClose lvm # shutdown -h now @@ -520,7 +565,8 @@ possibility of bricking your device! I will go for the re-flash option here. Firstly, cd to the libreboot\_util/cbfstool/{armv7l i686 x86\_64} directory. Dump the current firmware - where *libreboot.rom* is an example: make sure to -adapt:\ +adapt: + # flashrom -p internal -r libreboot.rom If flashrom complains about multiple flash chips detected, add a *-c* option at the end, with the name of your chosen chip is quotes.\ @@ -529,7 +575,8 @@ would be really nice): $ ./cbfstool libreboot.rom print Extract grubtest.cfg: $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg\ -And modify:\ +And modify: + $ vi grubtest.cfg In grubtest.cfg, inside the 'Load Operating System' menu entry, change @@ -558,18 +605,21 @@ detected LUKS volumes. You can also specify -u UUID or -a (device). hardening your GRUB configuration, for security purposes. Save your changes in grubtest.cfg, then delete the unmodified config -from the ROM image:\ +from the ROM image: + $ ./cbfstool libreboot.rom remove -n grubtest.cfg and insert the modified grubtest.cfg:\ \$ **./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t raw**\ Now refer to . Cd (up) to -the libreboot\_util directory and update the flash chip contents:\ +the libreboot\_util directory and update the flash chip contents: + # ./flash update libreboot.rom Ocassionally, coreboot changes the name of a given board. If flashrom complains about a board mismatch, but you are sure that you chose the -correct ROM image, then run this alternative command:\ +correct ROM image, then run this alternative command: + # ./flash forceupdate libreboot.rom You should see "Verifying flash\... VERIFIED." written at the end of the flashrom output. @@ -600,21 +650,25 @@ with the following command:\ \$ **sed -e 's:(cbfsdisk)/grub.cfg:(cbfsdisk)/grubtest.cfg:g' -e 's:Switch to grub.cfg:Switch to grubtest.cfg:g' < grubtest.cfg > grub.cfg**\ -Delete the grub.cfg that remained inside the ROM:\ +Delete the grub.cfg that remained inside the ROM: + $ ./cbfstool libreboot.rom remove -n grub.cfg -Add the modified version that you just made:\ +Add the modified version that you just made: + $ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw Now you have a modified ROM. Once more, refer to . Cd to the libreboot\_util -directory and update the flash chip contents:\ +directory and update the flash chip contents: + # ./flash update libreboot.rom And wait for the "Verifying flash\... VERIFIED." Once you have done that, shut down and then boot up with your new configuration. When done, delete GRUB (remember, we only needed it for the *grub-mkpasswd-pbkdf2* utility; GRUB is already part of libreboot, -flashed alongside it as a *payload*):\ +flashed alongside it as a *payload*): + # pacman -R grub @@ -639,17 +693,21 @@ putting a keyfile inside initramfs would be a bad idea).\ Boot up and login as root or your user. Then generate the key file:\ \# **dd bs=512 count=4 if=/dev/urandom of=/etc/mykeyfile iflag=fullblock**\ -Insert it into the luks volume:\ +Insert it into the luks volume: + # cryptsetup luksAddKey /dev/sdX /etc/mykeyfile and enter your LUKS passphrase when prompted. Add the keyfile to the -initramfs by adding it to FILES in /etc/mkinitcpio.conf. For example:\ +initramfs by adding it to FILES in /etc/mkinitcpio.conf. For example: + # FILES="/etc/mykeyfile" -Create the initramfs image from scratch:\ +Create the initramfs image from scratch: + # mkinitcpio -p linux-libre # mkinitcpio -p linux-libre-lts # mkinitcpio -p linux-libre-grsec Add the following to your grub.cfg - you are now able to do that, see -above! -, or add it in the kernel command line for GRUB:\ +above! -, or add it in the kernel command line for GRUB: + # cryptkey=rootfs:/etc/mykeyfile \ You can also place this inside the grub.cfg that exists in CBFS: diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md index 4609db97..3dafb51b 100644 --- a/docs/gnulinux/grub_boot_installer.md +++ b/docs/gnulinux/grub_boot_installer.md @@ -32,16 +32,19 @@ Connect the USB drive. Check dmesg: $ dmesg -Check lsblk to confirm which drive it is:\ +Check lsblk to confirm which drive it is: + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For -example:\ +example: + $ sudo umount /dev/sdX\* # umount /dev/sdX\* dmesg told you what device it is. Overwrite the drive, writing your -distro ISO to it with dd. For example:\ +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 @@ -73,17 +76,21 @@ Prepare the USB drive (in LibertyBSD or OpenBSD) If you downloaded your ISO on a LibertyBSD or OpenBSD system, here is how to create the bootable GNU+Linux USB drive: -Connect the USB drive. Check dmesg:\ +Connect the USB drive. Check dmesg: + $ dmesg | tail -Check to confirm which drive it is, for example, if you think its sd3:\ +Check to confirm which drive it is, for example, if you think its sd3: + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For -example:\ +example: + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the -OpenBSD installer to it with dd. For example:\ +OpenBSD installer to it with dd. For example: + $ doas dd if=gnulinux.iso of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md index dbe55206..9809785f 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -154,7 +154,8 @@ to the command, for example: Extract grubtest.cfg from the ROM image {#extract_testconfig} --------------------------------------- -You can check the contents of the ROM image, inside CBFS:\ +You can check the contents of the ROM image, inside CBFS: + $ cd \.../libreboot\_util/cbfstool** $ ./cbfstool libreboot.rom print** @@ -163,7 +164,8 @@ loaded by default, with a menuentry for switching to grubtest.cfg. In this tutorial, you will first modify and test *grubtest.cfg*. This is to reduce the possibility of bricking your device, so DO NOT SKIP THIS! -Extract grubtest.cfg from the ROM image:\ +Extract grubtest.cfg from the ROM image: + $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg Modify the grubtest.cfg accordingly. @@ -176,7 +178,8 @@ Re-insert the modified grubtest.cfg into the ROM image {#reinsert_modified_testc ------------------------------------------------------ Once your grubtest.cfg is modified and saved, delete the unmodified -config from the ROM image:\ +config from the ROM image: + $ ./cbfstool libreboot.rom remove -n grubtest.cfg Next, insert the modified version:\ @@ -229,10 +232,12 @@ the already modified config). From /libreboot\_util/cbfstool, do:\ 's:Switch to grub.cfg:Switch to grubtest.cfg:g' < grubtest.cfg > grub.cfg**\ -Delete the grub.cfg that remained inside the ROM:\ +Delete the grub.cfg that remained inside the ROM: + $ ./cbfstool libreboot.rom remove -n grub.cfg -Add the modified version that you just made:\ +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 diff --git a/docs/grub/index.md b/docs/grub/index.md index 0c676da9..30800256 100644 --- a/docs/grub/index.md +++ b/docs/grub/index.md @@ -77,7 +77,8 @@ Custom keyboard layout in GRUB (for reference) {#grub_custom_keyboard} Keymaps are stored in resources/utilities/grub-assemble/keymap/. -Example (French Azerty):\ +Example (French Azerty): + $ ckbcomp fr > frazerty \ Go in grub directory:\ diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md index 485bf731..5b705e44 100644 --- a/docs/hcl/gm45_remove_me.md +++ b/docs/hcl/gm45_remove_me.md @@ -165,7 +165,8 @@ regions for your libreboot ROM image. If you are working with libreboot\_src (or git), you can find the source under resources/utilities/ich9deblob/ and will already be compiled if you ran **./oldbuild module all** or **./oldbuild module ich9deblob** -from the main directory (./), otherwise you can build it like so:\ +from the main directory (./), otherwise you can build it like so: + $ ./oldbuild module ich9deblob An executable file named **ich9deblob** will now appear under resources/utilities/ich9deblob/ @@ -177,7 +178,8 @@ GNU+Linux) under ./ich9deblob/. Place the factory.rom from your system (can be obtained using the external flashing guides for GM45 targets linked [../install/](../install/)) in the directory where you have your -ich9deblob executable, then run the tool:\ +ich9deblob executable, then run the tool: + $ ./ich9deblob A 12kiB file named **deblobbed\_descriptor.bin** will now appear. **Keep @@ -233,7 +235,8 @@ The ME interferes with flash read/write in flashrom, and the default descriptor locks some regions. The idea is that doing this will remove all of those restrictions. -Simply run (with factory.rom in the same directory):\ +Simply run (with factory.rom in the same directory): + $ ./demefactory It will generate a 4KiB descriptor file (only the descriptor, no GbE). @@ -305,7 +308,8 @@ Flash chips {#flashchips} **~~- Page 20 and page 9 refer to SDA\_HDO or SDA\_HDOUT~~** only on series 6 or higher chipsets. ICH9-M (X200) does it with a strap - connected to GPIO33 pin (see IRC notes below)\ + connected to GPIO33 pin (see IRC notes below) + - According to page 29, the X200 can have any of the following flash chips: - ATMEL AT26DF321-SU 72.26321.A01 - this is a 32Mb (4MiB) chip diff --git a/docs/index.md b/docs/index.md index 7b0280d7..fc058419 100644 --- a/docs/index.md +++ b/docs/index.md @@ -104,19 +104,24 @@ The libreboot project has three main goals: and support. Most people will simply give up before attempting to install coreboot. - \ + + Libreboot attempts to bridge this divide, making sure that everything from building to installing coreboot is automated, as much as is feasibly possible. Secondly, the project produces documentation aimed at non-technical users. Thirdly, the project attempts to provide excellent user support via mailing lists and - IRC.\ - \ + IRC. + + + Libreboot already comes with a payload (GRUB), flashrom and other needed parts. Everything is fully integrated, in a way where most of the complicated steps that are otherwise required, are instead done - for the user in advance.\ - \ + for the user in advance. + + + You can download ROM images for your libreboot system and install them, without having to build anything from source. The build system is also fully automated, so building from source is easy if you diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md index a52ea103..89f7ec67 100644 --- a/docs/install/bbb_setup.md +++ b/docs/install/bbb_setup.md @@ -216,7 +216,8 @@ Output: /lib/firmware/BB-SPI0-01-00A0.dtbo -Then:\ +Then: + # echo BB-SPI0-01 > /sys/devices/bone\_capemgr.\*/slots # cat /sys/devices/bone\_capemgr.\*/slots Output: @@ -229,7 +230,8 @@ Output: 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPI0-01 -Verify that the spidev device now exists:\ +Verify that the spidev device now exists: + # ls -al /dev/spid\* Output: @@ -252,7 +254,8 @@ libreboot\_src, and put the ARM binary for it on your BBB. Finally, get the ROM image that you would like to flash and put that on your BBB. -Now test flashrom:\ +Now test flashrom: + # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 Output: diff --git a/docs/install/c201.md b/docs/install/c201.md index 1b15c284..a811404d 100644 --- a/docs/install/c201.md +++ b/docs/install/c201.md @@ -160,7 +160,8 @@ Then, the **cros-flash-replace** script has to be executed as such: If any error is shown, it is definitely a bad idea to go further than this point. -The resulting flash image can then be flashed back:\ +The resulting flash image can then be flashed back: + # flashrom -p host -w flash.img You should also see within the output the following:\ @@ -194,21 +195,25 @@ 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:\ +**cros-flash-replace** script has to be made executable: + # chmod a+x cros-flash-replace -The SPI flash has to be read first (using the right spi programmer):\ +The SPI flash has to be read first (using the right spi programmer): + # flashrom -p *programmer* -r flash.img **Note: it might be a good idea to copy the produced flash.img file at this point and store it outside of the device for backup purposes.** -Then, the **cros-flash-replace** script has to be executed as such:\ +Then, the **cros-flash-replace** script has to be executed as such: + # ./cros-flash-replace flash.img coreboot ro-frid If any error is shown, it is definitely a bad idea to go further than this point. The resulting flash image can then be flashed back (using the right spi -programmer):\ +programmer): + # flashrom -p *programmer* -w flash.img You should also see within the output the following:\ diff --git a/docs/install/index.md b/docs/install/index.md index 55fbbe50..f8ee0e6a 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -320,7 +320,8 @@ the flashing script. do this: *rm -f patch && wget -O flash https://notabug.org/vimuser/libreboot/raw/9d850543ad90b72e0e333c98075530b31e5d23f1/flash && chmod +x flash*** -The first half of the procedure is as follows:\ +The first half of the procedure is as follows: + $ sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom). @@ -344,7 +345,8 @@ and then boot; libreboot is running, but there is a 2nd procedure -When you have booted up again, you must also do this:\ +When you have booted up again, you must also do this: + $ sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom) If flashing fails at this stage, try the following:\ @@ -393,7 +395,8 @@ Look at the [list of ROM images](#rom) to see which image is compatible with your device. -Use this flashing script, to install libreboot:\ +Use this flashing script, to install libreboot: + $ sudo ./flash i945apple\_firstflash [yourrom.rom](#rom) diff --git a/docs/misc/index.md b/docs/misc/index.md index afffbbeb..dabe1e54 100644 --- a/docs/misc/index.md +++ b/docs/misc/index.md @@ -62,7 +62,8 @@ Be root $ su - -Installed powertop:\ +Installed powertop: + # pacman -S powertop and added the following to /etc/systemd/system/powertop.service : @@ -80,7 +81,8 @@ and added the following to /etc/systemd/system/powertop.service : [Install] WantedBy=multi-user.target -Finally, as root do that:\ +Finally, as root do that: + # systemctl enable powertop # systemctl start powertop @@ -109,7 +111,8 @@ included inside the ROM. Connect your null modem cable to the serial port on the dock and connect the other end to a 2nd system using your USB Serial adapter. -On the 2nd system, you can try this (using GNU Screen):\ +On the 2nd system, you can try this (using GNU Screen): + $ sudo screen /dev/ttyUSB0 115200 How to quit GNU Screen: Ctrl+A then release and press K, and then press @@ -234,7 +237,8 @@ Disable or enable beeps when removing/adding the charger: $ 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. @@ -248,10 +252,12 @@ Get the panel name with **sudo get-edid | strings**\ Or look in **/sys/class/drm/card0-LVDS-1/edid** Alternatively you can use i2cdump. In Debian and Devuan, this is in the -package i2c-tools.\ +package i2c-tools. + $ sudo modprobe i2c-dev $ sudo i2cdump -y 5 0x50 (you might have to change the value for --y)\ +-y) + $ sudo rmmod i2c-dev You'll see the panel name in the output (from the EDID dump). diff --git a/docs/misc/patch.md b/docs/misc/patch.md index a8dffc92..73d4979a 100644 --- a/docs/misc/patch.md +++ b/docs/misc/patch.md @@ -15,7 +15,8 @@ To apply a patch to a single file, do that in it's directory: Assuming that the patch is distributed in unified format identifying the -file the patch should be applied to, the above will work. Otherwise:\ +file the patch should be applied to, the above will work. Otherwise: + $ patch foo.txt < bar.patch You can apply a patch to an entire directory, but note the "p level". @@ -24,7 +25,8 @@ intend to patch, identified by path names that might be different when the files ane located on your own computer instead of on the computer where the patch was created. 'p' level instructs the 'patch' utility to ignore parts of the path name to identify the files correctly. -Usually a p level of 1 will work, so you would use:\ +Usually a p level of 1 will work, so you would use: + $ patch -p1 < baz.patch Change to the top level directory before running this. If a patch level @@ -32,14 +34,16 @@ of 1 cannot identify the files to patch, then inspect the patch file for file names. For example:\ **/home/user/do/not/panic/yet.c** -and you are working in a directory that contains panic/yet.c, use:\ +and you are working in a directory that contains panic/yet.c, use: + $ patch -p5 < baz.patch You usually count one up for each path separator (forward slash) removed from the beginning of the path, until you are left with a path that exists in the current working directory. The count is the p level. -Removing a patch using the -R flag\ +Removing a patch using the -R flag + $ patch -p5 -R < baz.patch [Back to top of page.](#pagetop) @@ -49,13 +53,16 @@ Removing a patch using the -R flag\ Create a patch with diff ======================== -Diff can create a patch for a single file:\ +Diff can create a patch for a single file: + $ diff -u original.c new.c > original.patch -For diff'ing a source tree:\ +For diff'ing a source tree: + $ cp -R original new -Do whatever you want in new/ and then diff it:\ +Do whatever you want in new/ and then diff it: + $ diff -rupN original/ new/ > original.patch [Back to top of page.](#pagetop) @@ -69,10 +76,12 @@ git is something special. Note: this won't show new files created. -Just make whatever changes you want to a git clone and then:\ +Just make whatever changes you want to a git clone and then: + $ git diff > patch.git -Note the git revision that you did this with:\ +Note the git revision that you did this with: + $ git log Alternatively (better yet), commit your changes and then use: @@ -89,10 +98,12 @@ git apply it really is. Now to apply that patch in the future, just git clone it again and do -with the git revision you found from above:\ +with the git revision you found from above: + $ git reset --hard REVISIONNUMBER -Now put patch.git in the git clone directory and do:\ +Now put patch.git in the git clone directory and do: + $ git apply patch.git If you use a patch from git format-patch, then use **git am patch.git** -- cgit v1.2.3-70-g09d2