aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/gnulinux/configuring_parabola.md41
-rw-r--r--docs/gnulinux/encrypted_debian.md4
-rw-r--r--docs/gnulinux/encrypted_parabola.md90
-rw-r--r--docs/gnulinux/grub_cbfs.md6
-rw-r--r--docs/hardware/c201.md2
-rw-r--r--docs/hardware/gm45_remove_me.md2
-rw-r--r--docs/hardware/kgpe-d16.md3
-rw-r--r--docs/hardware/x200.md9
-rw-r--r--docs/install/bbb_setup.md7
-rw-r--r--docs/install/index.md14
-rw-r--r--docs/install/t400_external.md13
-rw-r--r--docs/install/t500_external.md9
-rw-r--r--docs/install/x200_external.md4
-rw-r--r--docs/misc/bbb_ehci.md4
14 files changed, 121 insertions, 87 deletions
diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md
index 167f147e..1e525f59 100644
--- a/docs/gnulinux/configuring_parabola.md
+++ b/docs/gnulinux/configuring_parabola.md
@@ -24,7 +24,7 @@ Paradoxically, as you get more advanced, Parabola can actually become
compared to what most distributions provide. You will find over time
that other distributions tend to *get in your way*.
-A lot of the steps in this guide will refer to the Arch wiki. Arch is
+A lot of the steps in this guide will refer to ArchWiki. Arch is
the upstream distribution that Parabola uses. Most of this guide will
also tell you to read wiki articles, other pages, manuals, and so on. In
general, it tries to cherry-pick the most useful information, but
@@ -33,10 +33,10 @@ nonetheless, you are encouraged to learn as much as possible.
**NOTE: It might take you a few days to fully install your system how you like,
depending on how much you need to read. Patience is key, especially for new users.**
-The Arch wiki will sometimes use bad language, such as calling the whole
+The ArchWiki will sometimes use bad language, such as calling the whole
system Linux, using the term **open-source**/**closed-source**,
and it will sometimes recommend the use of proprietary software.
-You need to be careful about this when reading anything on the Arch wiki.
+You need to be careful about this when reading anything on ArchWiki.
Some of these steps require internet access. To get initial access
for setting up the system (I'll go into networking later),
@@ -121,14 +121,14 @@ before. In general, keeping notes (such as what I have done with this
page) can be very useful as a reference in the future (e.g, if you wanted to
re-install it, or install the distro on another computer).
-You should also read the Arch wiki article on [System Maintenance](https://wiki.archlinux.org/index.php/System_maintenance),
+You should also read the ArchWiki article on [System Maintenance](https://wiki.archlinux.org/index.php/System_maintenance),
before continuing. Also, read their article on [enhancing system stability](https://wiki.archlinux.org/index.php/Enhance_system_stability).
This is important, so make sure to read them both!*
Install `smartmontools`; it can be used to check smart data. HDDs use
non-free firmware inside; it's transparent to you, but the smart
data comes from it. Therefore, don't rely on it too much), and then read
-the Arch wiki [article](https://wiki.archlinux.org/index.php/S.M.A.R.T.) on it, to learn how to use it:
+the ArchWiki [article](https://wiki.archlinux.org/index.php/S.M.A.R.T.) on it, to learn how to use it:
# pacman -S smartmontools
@@ -195,7 +195,7 @@ for generating secure passphrases.
### Configure sudo
Now that we have a normal user account, we'll want to configure `sudo`,
so that user is able to run commands as **root** (e.g., installing software);
-this will be necessary to flash the ROM later on. Refer to the Arch wiki's [sudo](https://wiki.archlinux.org/index.php/Sudo) documentation.
+this will be necessary to flash the ROM later on. Refer to ArchWiki's [sudo](https://wiki.archlinux.org/index.php/Sudo) documentation.
The first step is to install the `sudo` package:
@@ -237,8 +237,8 @@ a sound manager (to make sure you can hear sound through speakers or headphones)
or DHCP (which allows you to get an IP address, to connect to the internet).
These are just a few examples; there are countless others.
-`systemd` is a controversial init system; [here](https://bbs.archlinux.org/viewtopic.php?pid=1149530#p1149530)
-is an explanation behind the Arch development team's decision to use it.
+`systemd` is a controversial init system; A [forum post](https://bbs.archlinux.org/viewtopic.php?pid=1149530#p1149530)
+has an explanation behind the Arch development team's decision to use it.
The **manpage** should also help:
@@ -280,7 +280,7 @@ To delete the temporary files, you can use the `clean` option:
# 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
+an age parameter"*. According to ArchWiki, this reads information
in **/etc/tmpfiles.d** and **/usr/lib/tmpfiles.d**, to know what actions to perform.
Therefore, it is a good idea to read what's stored in these locations, to get a better understanding.
@@ -319,7 +319,7 @@ In the end, I decided not to install anything from it,
but I kept the repository enabled regardless.
## Setup a Network Connection in Parabola
-Read the Arch wiki guide to [Configuring the Network](https://wiki.archlinux.org/index.php/Configuring_Network).
+Read the ArchWiki guide to [Configuring the Network](https://wiki.archlinux.org/index.php/Configuring_Network).
### Set the Hostname
This should be the same as the hostname that you set in **/etc/hostname**,
@@ -348,7 +348,7 @@ The `hostname` utility is part of the `inetutils` package, and is in the **core*
installed by default (as part of the **base** package).
### Network Status
-According to the Arch wiki, [udev](https://wiki.archlinux.org/index.php/Udev) should already detect
+According to ArchWiki, [udev](https://wiki.archlinux.org/index.php/Udev) should already detect
the ethernet chipset, and automatically load the driver for it at boot time.
You can check this in the **Ethernet controller** section, when running the `lspci` command:
@@ -366,7 +366,7 @@ In my case, I did:
# dmesg | grep e1000e
### Network Device Names
-According to the Arch wiki guide on [Configuring Network Device Names](https://wiki.archlinux.org/index.php/Configuring_Network#Device_names),
+According to the ArchWiki guide on [Configuring Network Device Names](https://wiki.archlinux.org/index.php/Configuring_Network#Device_names),
it is important to note that the old interface names that you might be used to
(e.g., `eth0`, `wlan0`, `wwan0`, etc.), if you come from a distribution like Debian or Trisquel,
are no longer applicable. Instead, `systemd` creates device names
@@ -375,7 +375,7 @@ with a fixed identifier that it automatically generates.
An example device name for your ethernet chipset would be `enp0s25`,
and is never supposed to change.
-If you want to enable the old names, the Arch wiki recommends adding `net.ifnames=0`
+If you want to enable the old names, ArchWiki recommends adding `net.ifnames=0`
to your kernel parameters (in Libreboot context, this would be accomplished by following
the instructions in [How to replace the default GRUB configuration file](grub_cbfs.md)).
@@ -401,7 +401,7 @@ that you could use.
Since we are going with the *MATE Desktop Environment*, we will primarily be following
the instructions on the [Arch Linux Package Repository](https://wiki.mate-desktop.org/archlinux_custom_repo) page,
but will also refer to the [General Recommendations](https://wiki.archlinux.org/index.php/General_recommendations#Graphical_user_interface)
-on the Arch wiki.
+on ArchWiki.
### Installing Xorg
The first step is to install [**Xorg**](https://wiki.archlinux.org/index.php/Xorg);
@@ -433,14 +433,14 @@ Other drivers (not just video) can be found by looking at the `xorg-drivers` gro
so you will notice that the layout you set in **/etc/vconsole.conf** earlier might
not actually be the same in `xorg`.
-Check the Arch wiki's article on [Xorg's keyboard configuration](https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg), for more information.
+Check ArchWiki's article on [Xorg's keyboard configuration](https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg), for more information.
To see what layout you currently use, try this on a terminal emulator in `xorg`:
# setxkbmap -print -verbose 10
I'm simply using the default Qwerty (US) keyboard, so there isn't anything I need
-to change here; if you do need to make any changes, the Arch wiki recommends two ways
+to change here; if you do need to make any changes, ArchWiki recommends two ways
of doing it: manually updating [configuration files](https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_X_configuration_files) or using the [localectl](https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_localectl) command.
### Installing MATE
@@ -450,7 +450,7 @@ if we want all of the MATE Desktop, we need to install two packages:
# pacman -Syy mate mate-extra
The last step is to install a Display Manager; for MATE, we will be using `lightdm`
-(it's the recommended Display Manager for the MATE Desktop); for this, we'll follow the insructions [here](https://wiki.mate-desktop.org/archlinux_custom_repo#display_manager_recommended),
+(it's the recommended Display Manager for the MATE Desktop); for this, we'll folow the instructions [on the MATE wiki](https://wiki.mate-desktop.org/archlinux_custom_repo#display_manager_recommended),
with one small change: the `lightdm-gtk3-greeter` package doesn't exist in Parabola's repositories.
So, instead we will install the `lightdm-gtk-greeter` package; it performs the same function.
@@ -466,14 +466,15 @@ as well as the service that will prompt us with a login window, `accounts-daemon
# systemctl enable accounts-daemon
Now you have installed the *MATE Desktop Environment*,If you wanted
-to install another desktop environment, check out some [other options](https://wiki.archlinux.org/index.php/Desktop_environment) on the the Arch wiki.
+to install another desktop environment, check out some [other options](https://wiki.archlinux.org/index.php/Desktop_environment) on ArchWiki.
### Configuring Network Manager in MATE
Now that we have installed the Mate Desktop environment, and booted into it,
we need to set up the network configuration in our graphical environment.
-The MATE Desktop wiki recommends that we use Network Manager; the Arch wiki article
-about it can be found [here](https://wiki.archlinux.org/index.php/NetworkManager).
+The MATE Desktop wiki recommends that we use Network Manager; an
+article about Network Manager can be found
+[on ArchWiki](https://wiki.archlinux.org/index.php/NetworkManager).
We need to install the NetworkManager package:
diff --git a/docs/gnulinux/encrypted_debian.md b/docs/gnulinux/encrypted_debian.md
index 2b95b2a9..83f0dd28 100644
--- a/docs/gnulinux/encrypted_debian.md
+++ b/docs/gnulinux/encrypted_debian.md
@@ -154,8 +154,8 @@ Choose 'Yes'. It will fail, but don't worry. Then at the main menu,
choose 'Continue without a bootloader'. You could also choose 'No'.
Choice is irrelevant here.
-*You do not need to install GRUB at all, since in libreboot you are
-using the GRUB payload (for libreboot) to boot your system directly.*
+*Don't forget to have grub-coreboot package installed, even though installing grub to MBR is irrelevant
+on libreboot system, grub tools are still needed to eg. generate config (`grub-mkconfig`)*
Clock UTC
=========
diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md
index 2493b4aa..a4d7dd16 100644
--- a/docs/gnulinux/encrypted_parabola.md
+++ b/docs/gnulinux/encrypted_parabola.md
@@ -20,12 +20,15 @@ This guide borrows heavily from the Parabola wiki, and will constantly link to i
For those new to Parabola GNU+Linux-Libre, check their [Beginner section](https://wiki.parabola.nu/Beginners%27_guide#Beginners) for an overview.
## Minumum Requirements
-You can find the minimum requirements to run Parabola GNU+Linux [here](https://wiki.parabola.nu/Beginners%27_guide#Minimum_system_requirements).
+You can find the minimum requirements to run Parabola GNU+Linux
+[on the Parabola wiki](https://wiki.parabola.nu/Beginners%27_guide#Minimum_system_requirements).
## Preparation
### Download the latest ISO
-For this guide, I used the *2016.11.03* ISO; the most current image is available [here](https://wiki.parabola.nu/Get_Parabola#Main_live_ISO).
+For this guide, I used the *2016.11.03* ISO; the most current image is
+available on Parabola's
+[downloads page](https://wiki.parabola.nu/Get_Parabola#Main_live_ISO).
If you are a complete beginner with GNU+Linux, choose the *Mate Desktop ISO*.
it is easier to install Parabola with this version, because it allows you
@@ -80,7 +83,7 @@ if it's not new, then there are two ways to handle it:
you can either choose to fill it with zeroes or random data; I chose random data (e.g., `urandom`),
because it's more secure. Depending on the size of the drive, this could take a while to complete:
- # dd if=/dev/urandom of=/dev/sdX; sync
+ `# dd if=/dev/urandom of=/dev/sdX; sync`
2. If the drive were previously encrypted, all you need to do is wipe the LUKS header.
The size of the header depends upon the specific model of the hard drive;
@@ -88,7 +91,7 @@ you can find this information by doing some research online.
Refer to this [article](https://www.lisenet.com/2013/luks-add-keys-backup-and-restore-volume-header/), for more information about LUKS headers.
You can either fill the header with zeroes, or with random data; again, I chose random data, using `urandom`:
- # head -c 3145728 /dev/urandom > /dev/sdX; sync
+ `# head -c 3145728 /dev/urandom > /dev/sdX; sync`
Also, if you're using an SSD, there are a two things you should keep in mind:
@@ -183,17 +186,17 @@ Check to make sure that the group was created:
Lastly, we need to create the logical volumes themselves, inside the volume group;
one will be our swap, cleverly named **swapvol**, and the other will be our root partition,
-equally cleverly named as **root**.
+equally cleverly named as **rootvol**.
1. We will create the **swapvol** first (again, choose your own name, if you like).
Also, make sure to [choose an appropriate swap size](http://www.linux.com/news/software/applications/8208-all-about-linux-swap-space)
(e.g., **2G** refers to two gigabytes; change this however you see fit):
- # lvcreate -L 2G matrix -n swapvol
+ `# lvcreate -L 2G matrix -n swapvol`
-2. Now, we will create a single, large partition in the rest of the space, for **root**:
+2. Now, we will create a single, large partition in the rest of the space, for **rootvol**:
- # lvcreate -l +100%FREE matrix -n root
+ `# lvcreate -l +100%FREE matrix -n rootvol`
You can also be flexible here, for example you can specify a **/boot**, a **/**,
a **/home**, a **/var**, or a **/usr** volume. For example, if you will be running a
@@ -205,9 +208,9 @@ Verify that the logical volumes were created correctly:
# lvdisplay
-#### Make the root and swap Partitions Ready for Installation
+#### Make the rootvol and swapvol Partitions Ready for Installation
The last steps of setting up the drive for installation are turning **swapvol**
-into an active swap partition, and formatting **root**.
+into an active swap partition, and formatting **rootvol**.
To make **swapvol** into a swap partition, we run the `mkswap` (i.e., make swap) command:
@@ -218,24 +221,24 @@ using `swapon` (i.e., turn swap on) command:
# swapon /dev/matrix/swapvol
-Now I have to format **root**, to make it ready for installation;
+Now I have to format **rootvol**, to make it ready for installation;
I do this with the `mkfs` (i.e., make file system) command.
I choose the **ext4** filesystem, but you could use a different one,
depending on your use case:
- # mkfs.ext4 /dev/mapper/matrix-root
+ # mkfs.ext4 /dev/mapper/matrix-rootvol
-Lastly, I need to mount **root**. Fortunately, GNU+Linux has a directory
+Lastly, I need to mount **rootvol**. Fortunately, GNU+Linux has a directory
for this very purpose: **/mnt**:
- # mount /dev/matrix/root /mnt
+ # mount /dev/matrix/rootvol /mnt
#### Create the /boot and /home Directories
-Now that you have mounted **root**, you need to create the two most important
+Now that you have mounted **rootvol**, you need to create the two most important
folders on it: **/boot** and **/home**; these folder contain your boot files,
as well as each user's personal documents, videos, etc..
-Since you mounted **root** at **/mnt**, this is where you must create them;
+Since you mounted **rootvol** at **/mnt**, this is where you must create them;
you will do so using `mkdir`:
# mkdir -p /mnt/home
@@ -251,7 +254,7 @@ The setup of the drive and partitions is now complete; it's time to actually ins
The first step of the actual installation is to choose the server from where
we will need to download the packages; for this, we will again refer to the [Parabola Wiki](https://wiki.parabola.nu/Beginners%27_guide#Select_a_mirror).
For beginners, I recommend that the edit the file using `nano` (a command-line text editor);
-you can learn more about it [here](https://www.nano-editor.org/); for non-beginners,
+you can learn more about it on [their website](https://www.nano-editor.org/); for non-beginners,
simply edit it with your favorite text editor.
## Install the Base System
@@ -261,7 +264,7 @@ refer to [Install the Base System](https://wiki.parabola.nu/Beginners%27_guide#I
## Generate an fstab
The next step in the process is to generate a file known as an **fstab**;
the purpose of this file is for the operating system to identify the storage device
-used by your installation. [Here](https://wiki.parabola.nu/Beginners%27_guide#Generate_an_fstab) are the instructions to generate that file.
+used by your installation. [On the Parabola beginner's guide](https://wiki.parabola.nu/Beginners%27_guide#Generate_an_fstab) are the instructions to generate that file.
## Chroot into and Configure the System
Now, you need to `chroot` into your new installation, to complete the setup
@@ -270,29 +273,30 @@ of an operating system to a different one; in this instance, it means changing
directory to the one you created in the previous steps, so that you can modify files
and install software onto it, as if it were the host operating system.
-To `chroot` into your installation, follow the instructions [here](https://wiki.parabola.nu/Beginners%27_guide#Chroot_and_configure_the_base_system).
+To `chroot` into your installation, follow the instructions [on the
+Prabola beginner's guide](https://wiki.parabola.nu/Beginners%27_guide#Chroot_and_configure_the_base_system).
### Setting up the Locale
Locale refers to the language that your operating system will use, as well as some
other considerations related to the region in which you live. To set this up,
-follow the instructions [here](https://wiki.parabola.nu/Beginners%27_guide#Locale).
+follow the instructions [in the Parabola beginner's guide](https://wiki.parabola.nu/Beginners%27_guide#Locale).
### Setting up the Consolefont and Keymap
-This will determine the keyboard layout of your new installation; follow the instructions [here](https://wiki.parabola.nu/Beginners%27_guide#Console_font_and_keymap).
+This will determine the keyboard layout of your new installation; follow the instructions [in the Parabola beginner's guide](https://wiki.parabola.nu/Beginners%27_guide#Console_font_and_keymap).
### Setting up the Time Zone
You'll need to set your current time zone in the operating system; this will enable applications
that require accurate time to work properly (e.g., the web browser).
-To do this, follow the instructions [here](https://wiki.parabola.nu/Beginners%27_guide#Time_zone).
+To do this, follow the instructions [in the Parabola beginner's guide](https://wiki.parabola.nu/Beginners%27_guide#Time_zone).
### Setting up the Hardware Clock
To make sure that your computer has the right time, you'll have to set the time in your computer's internal clock.
-Follow the instructions [here](https://wiki.parabola.nu/Beginners%27_guide#Hardware_clock) to do that.
+Follow the instructions [in the Parabola beginner's guide](https://wiki.parabola.nu/Beginners%27_guide#Hardware_clock) to do that.
### Setting up the Kernel Modules
Now we need to make sure that the kernel has all the modules that it needs
to boot the operating system. To do this, we need to edit a file called **mkinitcpio.conf**.
-More information about this file can be found [here](https://wiki.parabola.nu/Mkinitcpio),
+More information about this file can be found [in the Parabola beginner's guide](https://wiki.parabola.nu/Mkinitcpio),
but for the sake of this guide, you simply need to run the following command.
# nano /etc/mkinitcpio.conf
@@ -334,7 +338,7 @@ Then, we update both kernels like this, using the `mkinitcpio` command:
### Setting up the Hostname
Now we need to set up the hostname for the system; this is so that our device
-can be identified by the network. Refer to [this section](https://wiki.parabola.nu/Beginners%27_guide#Hostname)
+can be identified by the network. Refer to [the hostname section](https://wiki.parabola.nu/Beginners%27_guide#Hostname)
of the Parabola wiki's Beginner's Guide. You can make the hostname anything you like;
for example, if you wanted to choose the hostname **parabola**,
you would run the `echo` command, like this:
@@ -351,8 +355,8 @@ And then you would modify **/etc/hosts** like this, adding the hostname to it:
### Configure the Network
Now that we have a hostname, we need to configure the settings for the rest of the network.
-Instructions for setting up a wired connection are [here](https://wiki.parabola.nu/Beginners%27_guide#Wired),
-and instructions for setting up a wireless connection are [here](https://wiki.parabola.nu/Beginners%27_guide#Wireless_2).
+Instructions for setting up a wired connection are [in the Parabola beginner's guide](https://wiki.parabola.nu/Beginners%27_guide#Wired),
+and instructions for setting up a wireless connection are [in the Parabola beginner's guide](https://wiki.parabola.nu/Beginners%27_guide#Wireless_2).
### Set the root Password
The **root** account has control over all the files in the computer; for security,
@@ -398,6 +402,17 @@ This configuration will lock the user out for ten minutes.
You can unlock a user's account manually, using the **root** account, with this command:
# pam_tally --user *theusername* --reset
+
+#### Generate grub.cfg
+Edit configuration in `/etc/default/grub`, remembering to use UUID when poitning to mbr/gpt partition.
+Use `blkid` to get list of devices with their respective UUIDs.
+Next generate grub.cfg with
+
+ # grub-mkconfig /boot/grub/grub.cfg
+
+If you have separate `/boot` partition, don't forget to add `boot` symlink inside that points to current directory
+
+ # cd /boot; ln -s . boot
## Unmount All Partitions and Reboot
Congratulations! You have finished the installation of Parabola GNU+Linux-Libre.
@@ -412,9 +427,9 @@ Unmount all of the partitions from **/mnt**, and "turn off" the swap volume:
# umount -R /mnt
# swapoff -a
-Deactivate the **root** and **swapvol** logical volumes:
+Deactivate the **rootvol** and **swapvol** logical volumes:
- # lvchange -an /dev/matrix/root
+ # lvchange -an /dev/matrix/rootvol
# lvchange -an /dev/matrix/swapvol
Lock the encrypted partition (i.e., close it):
@@ -427,17 +442,18 @@ Shutdown the machine:
After the machine is off, remove the installation media, and turn it on.
-## Booting the New Installation, from GRUB
-When starting your installation for the first time, you have to manually boot
+## Booting the installation manually from GRUB
+When you forget to configure or misconfigure grub on your hdd, you have to manually boot
the system by entering a series of commands into the GRUB command line.
+
After the computer starts, Press `C` to bring up the GRUB command line.
You can either boot the normal kernel, or the LTS kernel we installed;
here are the commands for the normal kernel:
grub> cryptomount -a
- grub> set root='lvm/matrix-root'
- grub> linux /boot/vmlinuz-linux-libre root=/dev/matrix/root cryptdevice=/dev/sda1:root
+ grub> set root='lvm/matrix-rootvol'
+ grub> linux /boot/vmlinuz-linux-libre root=/dev/matrix/rootvol cryptdevice=/dev/sda1:root
grub> initrd /boot/initramfs-linux-libre.img
grub> boot
@@ -445,11 +461,9 @@ If you're trying to boot the LTS kernel, simply add **-lts** to the end
of each command that contains the kernel (e.g., **/boot/vmlinuz-linux-libre**
would be **/boot/vmlinuz/linux-libre-lts**).
-**NOTE: on some Thinkpads, during boot, a faulty DVD drive can cause
-the** `cryptomount -a` **command to fail, as well as the error** `AHCI transfer timed out`
-**(when the Thinkpad X200 is connected to an UltraBase). For both issues,
-the workaround was to remove the DVD drive (if using the UltraBase,
-then the whole device must be removed).**
+**NOTE: on machines with native sata, during boot a (faulty) optical disc drive (like dvd) can cause
+the** `cryptomount -a` **command to fail/hang, as well as the error** `AHCI transfer timed out`
+**The workaround was to remove the DVD drive.**
## Follow-Up Tutorial: Configuring Parabola
The next step of the setup process is to modify the configuration file that
diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md
index 99afe06c..5283b4fc 100644
--- a/docs/gnulinux/grub_cbfs.md
+++ b/docs/gnulinux/grub_cbfs.md
@@ -24,7 +24,7 @@ However, both ways will require us to download the Libreboot Utility Archive.
### Download the Libreboot Utility Archive
The Libreboot Utility Archive contains the programs that we'll need
to get our **grubtest.cfg** file. The latest release of the Libreboot Utility Archive
-can be downloaded from libreboot.org, [here](https://www.mirrorservice.org/sites/libreboot.org/release/stable/20160907/libreboot_r20160907_util.tar.xz).
+can be downloaded [from libreboot.org](https://www.mirrorservice.org/sites/libreboot.org/release/stable/20160907/libreboot_r20160907_util.tar.xz).
The quickest way to download it would be to use the `wget` program,
which (if you don't know) allows you to download files from the internet.
@@ -93,7 +93,7 @@ image file is named **libreboot.rom**, so please make sure to adapt.
There are two ways to get a pre-compiled ROM image:
#### 1. Download a Pre-Compiled Image from the Libreboot Website
-For the current release, **20160907**, they can be found [here](https://www.mirrorservice.org/sites/libreboot.org/release/stable/20160907/rom/grub/);
+For the current release, **20160907**, they can be found [on a Libreboot mirror](https://www.mirrorservice.org/sites/libreboot.org/release/stable/20160907/rom/grub/);
please adopt this guide, if using a different version of Libreboot.
You also need to make sure that you select both the correct ROM for the device you're using,
@@ -219,7 +219,7 @@ Or, replace it with this, if you are using a Debian-based distribution (e.g., Tr
initrd /initrd.img
Remember, that these names come from the instructions to install GNU+Linux
-on Libreboot systems, located [here](index.md). If you followed different instructions,
+on Libreboot systems, located [in the docs](index.md). If you followed different instructions,
(or for some other reason, used different names), simply put the names
of your **root** and **swap** volumes, in place of the ones used here.
diff --git a/docs/hardware/c201.md b/docs/hardware/c201.md
index 1a18e30c..f268e6f6 100644
--- a/docs/hardware/c201.md
+++ b/docs/hardware/c201.md
@@ -99,7 +99,7 @@ The libreboot project recommends using an external USB wifi dongle that
works with free software. See
[\#recommended\_wifi](./#recommended_wifi).
-There are 2 companies (endorsed by Creative Commons, under their
+There are 2 companies (endorsed by Free Software Foundation, under their
*Respects your Freedom* guidelines), that sell USB WiFi dongles
guaranteed to work with free software (i.e. linux-libre kernel):
diff --git a/docs/hardware/gm45_remove_me.md b/docs/hardware/gm45_remove_me.md
index f7ddfe55..b2f8db8b 100644
--- a/docs/hardware/gm45_remove_me.md
+++ b/docs/hardware/gm45_remove_me.md
@@ -24,7 +24,7 @@ More information about the ME can be found at
<http://www.coreboot.org/Intel_Management_Engine> and
<http://me.bios.io/Main_Page>.
-Another project recently found: <http://io.smashthestack.org/me/>
+Another project recently found: <http://io.netgarage.org/me/>
ICH9 gen utility {#ich9gen}
================
diff --git a/docs/hardware/kgpe-d16.md b/docs/hardware/kgpe-d16.md
index e14c447d..45b1ae6c 100644
--- a/docs/hardware/kgpe-d16.md
+++ b/docs/hardware/kgpe-d16.md
@@ -10,6 +10,7 @@ work), merged into libreboot.
*Memory initialization is still problematic, for some modules. We
recommend avoiding Kingston modules.*
+*For working configurations see <https://www.coreboot.org/Board:asus/kgpe-d16>.*
Flashing instructions can be found at
[../install/\#flashrom](../install/#flashrom) - note that external
@@ -125,7 +126,7 @@ The information here is adapted, from the ASUS website.
### Memory compatibility (with libreboot)
- *Total Slots:* 16 (4-channel per CPU, 8 DIMM per CPU), ECC
-- *Capacity:* Maximum up to 256GB RDIMM
+- *Capacity:* Maximum up to 256GB RDIMM (Tested max 128GB)
- *Memory Type that is compatible:*
- DDR3 1600/1333/1066/800 UDIMM\*
- DDR3 1600/1333/1066/800 RDIMM\*
diff --git a/docs/hardware/x200.md b/docs/hardware/x200.md
index be4c2a38..c5f535cb 100644
--- a/docs/hardware/x200.md
+++ b/docs/hardware/x200.md
@@ -42,6 +42,15 @@ only replaces the BIOS firmware, not EC.
Updated EC firmware has several advantages e.g. bettery battery
handling.
+Battery Recall {#batteryrecall}
+=========
+[On 21 April 2015, Lenovo expanded a recall on Lenovo batteries found in some ThinkPad models, which includes the X200 and X200S.](https://pcsupport.lenovo.com/cr/en/solutions/hf004122)
+To find out if you are affected, use [this Lenovo tool.](https://lenovobattery2014.orderz.com/)
+Lenovo advises that owners of the recalled models "should turn off the system, remove the battery,
+and only power your ThinkPad by plugging in the AC adapter and power cord."
+Upon battery verification, Lenovo will replace recalled batteries free of charge.
+Battery replacement instructions for the X200/X200s are found [on this page.](https://pcsupport.lenovo.com/cr/en/parts/pd003507/)
+
Compatibility (without blobs) {#compatibility_noblobs}
-----------------------------
diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md
index 18f0c7be..94cfdc0b 100644
--- a/docs/install/bbb_setup.md
+++ b/docs/install/bbb_setup.md
@@ -40,7 +40,7 @@ Shopping list (pictures of this hardware is shown later):
(rev. C) is highly recommended. You can buy one from
[Adafruit](https://www.adafruit.com) (USA),
[ElectroKit](http://electrokit.com) (Sweden) or any of the
- distributors listed [here](http://beagleboard.org/black) (look below
+ distributors listed on [BeagleBoard's website](http://beagleboard.org/black) (look below
'Purchase'). We recommend this product because we know that it
works well for our purposes and doesn't require any non-free
software.
@@ -328,7 +328,10 @@ PSU to pin 2 on the BBB (P9 header). It is safe to install this now
should.*
if you need to extend the 3.3v psu leads, just use the same colour M-F
-leads, *but* keep all other leads short (10cm or less)
+leads, *but* keep all other leads short and equal length (30cm or less).
+Keep in mind that length isn't inversely proportional to signal quality,
+so trying out different lengths will yield different results.
+Same goes for spispeed.
You should now have something that looks like this:\
![](images/x200/5252_bbb0.jpg) ![](images/x200/5252_bbb1.jpg)
diff --git a/docs/install/index.md b/docs/install/index.md
index ea48632d..d4ac2f13 100644
--- a/docs/install/index.md
+++ b/docs/install/index.md
@@ -264,13 +264,13 @@ executables from the libreboot source code archives.
How to update the flash chip contents:
- $ sudo ./flash update [yourrom.rom](#rom)
+`$ sudo ./flash update `[`yourrom.rom`](#rom)
Ocassionally, coreboot changes the name of a given board. If flashrom
complains about a board mismatch, but you are sure that you chose the
correct ROM image, then run this alternative command:
- $ sudo ./flash forceupdate [yourrom.rom](#rom)
+ `$ sudo ./flash forceupdate `[`yourrom.rom`](#rom)
You should see `Verifying flash... VERIFIED.` written at the end
of the flashrom output. *Shut down* after you see this, and then boot
@@ -305,7 +305,7 @@ the flashing script. do this: *
The first half of the procedure is as follows:
- $ sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom).
+`$ sudo ./flash i945lenovo_firstflash `[`yourrom.rom`](#rom)
You should see within the output the following:
@@ -332,13 +332,11 @@ needed (see below).
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
-
-internal:laptop=force\_I\_want\_a\_brick -w [yourrom.rom](#rom)
+`$ sudo ./flashrom/i686/flashrom -p internal:laptop=force_I_want_a_brick -w `[`yourrom.rom`](#rom)
You should see within the output the following:
@@ -374,7 +372,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)
You should also see within the output the following:
diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md
index d48c15d4..672ea46e 100644
--- a/docs/install/t400_external.md
+++ b/docs/install/t400_external.md
@@ -1,5 +1,5 @@
---
-title: Flashing the T400 with a BeagleBone Black
+title: Flashing the T400 with a BeagleBone Black
...
Initial flashing instructions for T400.
@@ -12,7 +12,7 @@ An
["HMM"](https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/43y6629_05.pdf#page=386)
(Hardware Maintenance Manual) detailing the process of \[dis\]assembly
is available for this model. Be careful when reassembling the laptop as
-the screws on page 144 (with title "1130 Keyboard bezel") are swapped
+the screws on page 114 (with title "1130 Keyboard bezel") are swapped
and if you follow the HMM you will punch a hole through the bezel in the
upper right corner.
@@ -30,12 +30,17 @@ A note about CPUs
CPUs for this system. The Core 2 Duo P8400, P8600 and P8700 are believed
to work in libreboot.
-T9600, T9500 and T9550 are all compatible, as reported by users.
+T9600, T9500, T9550 and T9900 are all compatible, as reported by users.
Quad-core CPUs
--------------
-Incompatible. Do not use.
+Very likely to be compatible, but requires hardware modification.
+Based on info from German forum post about installing Core Quad CPU on T500 found in coreboot mailing list. Currently work in progress and no guide available.
+
+- [Coreboot mailing list post](https://mail.coreboot.org/pipermail/coreboot/2016-November/082463.html)
+- [German forum post about install Core Quad on T500](https://thinkpad-forum.de/threads/199129)
+
A note about GPUs
=================
diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md
index 5490744f..37217337 100644
--- a/docs/install/t500_external.md
+++ b/docs/install/t500_external.md
@@ -1,5 +1,5 @@
---
-title: Flashing the T500 with a BeagleBone Black
+title: Flashing the T500 with a BeagleBone Black
...
Initial flashing instructions for T500.
@@ -31,13 +31,16 @@ CPUs for this system. The Core 2 Duo P8400, P8600 and P8700 are believed
to work in libreboot. The T9600 was also tested on the T400 and
confirmed working.
-T9550 was tested by a user, and is compatible as reported in the IRC channel.
+T9550 and T9900 was tested by a user, and is compatible as reported in the IRC channel.
T9500 and T9400 may also work, but YMMV.
Quad-core CPUs
--------------
+Very likely to be compatible, but requires hardware modification.
+Based on info from German forum post about installing Core Quad CPU on T500 found in coreboot mailing list. Currently work in progress and no guide available.
-Incompatible. Do not use.
+- [Coreboot mailing list post](https://mail.coreboot.org/pipermail/coreboot/2016-November/082463.html)
+- [German forum post about install Core Quad on T500](https://thinkpad-forum.de/threads/199129)
A note about GPUs
=================
diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md
index 1e5b3b23..3ff34501 100644
--- a/docs/install/x200_external.md
+++ b/docs/install/x200_external.md
@@ -17,13 +17,13 @@ GNU+Linux distribution.
Flash chip size
===============
-Use this to find out:
+Run this command on x200 to find out flash chip model and its size:
# 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 [here](../hardware/x200.html#x200s).
+supported; see the [hardware](../hardware/x200.html#x200s) page.
MAC address
===========
diff --git a/docs/misc/bbb_ehci.md b/docs/misc/bbb_ehci.md
index 6f072154..50801a33 100644
--- a/docs/misc/bbb_ehci.md
+++ b/docs/misc/bbb_ehci.md
@@ -143,7 +143,7 @@ arm-linux-gnueabihf setup on your *host*.
$ cp configs/beaglebone kernel/arch/arm/configs/beaglebone_defconfig
- Download the patch from
- [here](http://www.coreboot.org/images/8/88/Ehci-debug-gadget-patches.tar.gz)
+ [coreboot.org](http://www.coreboot.org/images/8/88/Ehci-debug-gadget-patches.tar.gz)
- tar -xf Ehci-debug-gadget-patches.tar.gz (will create dir:
usbdebug-gadget)
- Note that there are two patches (patch\_1 and patch\_2) for each of
@@ -228,7 +228,7 @@ one^[2](#___fn2)^ should be = y
^2^ The g\_dbgp module on BeagleBone Black (Rev. C) reports it self as
Net20DC, the other options are for older BB(B) - ver1. This is
documented
-[here](https://johnlewis.ie/coreboot-ehci-debug-gadget-demonstration/)
+[on John Lewis's blog](https://johnlewis.ie/coreboot-ehci-debug-gadget-demonstration/)
(also tested/verified).
Then:\
generated by cgit v1.2.3-70-g09d2 (git 2.47.0) at 2024-11-22 07:24:21 +0000