From d43c6eaec611cc88309a9e09757dfba691e6f354 Mon Sep 17 00:00:00 2001 From: Edgard Schmidt Date: Sat, 25 Nov 2017 17:32:11 +0100 Subject: Markup more code content with code and pre tags --- docs/gnulinux/encrypted_parabola.md | 22 +++++++++++++++++----- docs/gnulinux/grub_hardening.md | 3 ++- 2 files changed, 19 insertions(+), 6 deletions(-) (limited to 'docs/gnulinux') diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index a4d7dd16..99a6fe0d 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -83,7 +83,9 @@ 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; @@ -91,7 +93,9 @@ 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: @@ -192,11 +196,15 @@ equally cleverly named as **rootvol**. 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 **rootvol**: - `# lvcreate -l +100%FREE matrix -n rootvol` + ~~~ + # 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 @@ -313,7 +321,11 @@ There are several modifications that we need to make to the file: Make sure to separate each module by one space. 2. Change the value of the uncommented `HOOKS` line to the following: - “`base udev autodetect modconf block keyboard keymap consolefont encrypt lvm2 filesystems fsck shutdown`”; + + ~~~ + base udev autodetect modconf block keyboard keymap consolefont encrypt lvm2 filesystems fsck shutdown + ~~~ + here's what each module does: * `keymap` adds to *initramfs* the keymap that you specified in **/etc/vconsole.conf** diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md index c32a0534..9eb7237e 100644 --- a/docs/gnulinux/grub_hardening.md +++ b/docs/gnulinux/grub_hardening.md @@ -81,7 +81,8 @@ installing GRUB version 2. Generate a key by giving it a password: grub-mkpasswd-pbkdf2 Its output will be a string of the following form: -grub.pbkdf2.sha512.10000.HEXDIGITS.MOREHEXDIGITS + + grub.pbkdf2.sha512.10000.HEXDIGITS.MOREHEXDIGITS Now open my.grubtest.cfg and put the following before the menu entries (prefered above the functions and after other directives). Of course use -- cgit v1.2.3-70-g09d2 From 44858dd869d6c6e2dd18cf20dd991e187715c108 Mon Sep 17 00:00:00 2001 From: Leah Rowe Date: Fri, 1 Dec 2017 18:45:20 +0000 Subject: link to guide for encrypted hyperbola gnu+linux install --- docs/gnulinux/encrypted_parabola.md | 2 ++ docs/gnulinux/index.md | 2 ++ 2 files changed, 4 insertions(+) (limited to 'docs/gnulinux') diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index 99a6fe0d..b2e40a01 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -3,6 +3,8 @@ title: Installing Parabola or Arch GNU+Linux-Libre, with Full-Disk Encryption (i x-toc-enable: true ... +Also see: +[Installing Hyperbola GNU+Linux, with Full-Disk Encryption (including /boot)](https://wiki.hyperbola.info/en:guide:encrypted_installation) This guide covers how to install Parabola GNU+Linux-Libre, with full disk encryption, including **/boot** (the boot directory). On most systems, **/boot** has diff --git a/docs/gnulinux/index.md b/docs/gnulinux/index.md index f8738d4a..a2a411ab 100644 --- a/docs/gnulinux/index.md +++ b/docs/gnulinux/index.md @@ -20,6 +20,8 @@ However, with Libreboot, GRUB is already included directly (as a payload), so ev - Follow-Up Tutorial: [Configuring Parabola (Post-Install)](configuring_parabola.md) +- [Installing Hyperbola GNU+Linux, with Full-Disk Encryption (including /boot)](https://wiki.hyperbola.info/en:guide:encrypted_installation) + - [Installing Trisquel GNU+Linux-Libre, with Full-Disk Encryption (including /boot)](encrypted_trisquel.md) - [Installing Debian or Devuan GNU+Linux-Libre, with Full-Disk Encryption (including /boot)](encrypted_debian.md) -- cgit v1.2.3-70-g09d2 From 31d9d64e1c64c3eb9f6a1d0286dbb40337108035 Mon Sep 17 00:00:00 2001 From: Leah Rowe Date: Sat, 31 Mar 2018 17:29:50 +0100 Subject: FAQ: Add note for Fedora compatibility with Libreboot --- docs/gnulinux/index.md | 17 +++++++++++++++++ www/faq.md | 8 ++++++++ 2 files changed, 25 insertions(+) (limited to 'docs/gnulinux') diff --git a/docs/gnulinux/index.md b/docs/gnulinux/index.md index a2a411ab..bc7a04f8 100644 --- a/docs/gnulinux/index.md +++ b/docs/gnulinux/index.md @@ -28,6 +28,23 @@ However, with Libreboot, GRUB is already included directly (as a payload), so ev - [How to Harden Your GRUB Configuration, for Security](grub_hardening.md) +Fedora won't boot? +------------------ + +This may also apply to CentOS or Redhat. + +When you use Libreboot's default GRUB config, and libreboot-grub uses fedora's +default grub.cfg (in /boot/grub2/grub.cfg), fedora by default makes use of the +`linux16` command, whereas it should be saying `linux` + +Do this in fedora: + +Open `/etc/grub.d/10_linux` + +Set the `sixteenbit` variable to an empty string, then do: + + grub2-mkconfig -o /boot/grub2/grub.cfg + Copyright © 2014, 2015 Leah Rowe Copyright © 2017 Elijah Smith diff --git a/www/faq.md b/www/faq.md index 78aee27b..9a3dca38 100644 --- a/www/faq.md +++ b/www/faq.md @@ -1012,6 +1012,14 @@ Absolutely! It is well-tested in libreboot, and highly recommended. See Any recent distribution should work, as long as it uses KMS (kernel mode setting) for the graphics. +Fedora won't boot? (may also be applicable to Redhat/CentOS) +----------------------------------------------------------- + +On Fedora, by default the grub.cfg tries to boot linux in 16-bit mode. You +just have to modify Fedora's GRUB configuration. +Refer to [the GNU+Linux page](docs/gnulinux/index.md#fedora-wont-boot). + + Can I use BSD? ---------------------------------- -- cgit v1.2.3-70-g09d2 From 1744d698983ad47623b5904c83e0171d4f68cd04 Mon Sep 17 00:00:00 2001 From: Leah Rowe Date: Sat, 28 Apr 2018 20:12:18 +0100 Subject: docs/gnulinux: fix the debian instructions (grub commands were b0rked) --- docs/gnulinux/grub_boot_installer.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) (limited to 'docs/gnulinux') diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md index 085ad34b..7086b71d 100644 --- a/docs/gnulinux/grub_boot_installer.md +++ b/docs/gnulinux/grub_boot_installer.md @@ -53,18 +53,23 @@ Make sure that the device isn't mounted, with `doas`; if it is, this command wil That's it! You should now be able to boot the installer from your USB drive (the instructions for doing so will be given later). ## Debian or Devuan net install -1. Download the Debian or Devuan net installer. You can download the Debian ISO from [the Debian homepage](https://www.debian.org/), or the Devuan ISO from [the Devuan homepage](https://www.devuan.org/). +Download the Debian or Devuan net installer. You can download the Debian ISO +from [the Debian homepage](https://www.debian.org/), or the Devuan ISO from +[the Devuan homepage](https://www.devuan.org/). -2. Create a bootable USB, using the commands in *Prepare the USB Drive in GNU+Linux*, above. +Secondly, create a bootable USB drive using the commands in +[#prepare-the-usb-drive-in-gnulinux](#prepare-the-usb-drive-in-gnulinux). -3. Boot the USB, and enter these commands in the GRUB terminal (for 64-bit Intel or AMD): +Thirdly, boot the USB and enter these commands in the GRUB terminal +(for 64-bit Intel or AMD): grub> set root='usb0' grub> linux /install.amd/vmlinuz grub> initrd /install.amd/initrd.gz grub> boot -4. If you are on a 32-bit system (e.g. some Thinkpad X60's), you will need to use these commands: +If you are on a 32-bit system (e.g. some Thinkpad X60's) then you will need to +use these commands instead: grub> set root='usb0' grub> linux /install.386/vmlinuz -- cgit v1.2.3-70-g09d2 From fdc116438fe0dfb98af483fd5ee7e1127b170def Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Wed, 9 May 2018 19:14:51 +0200 Subject: encrypted_parabola.md: prabola typofix --- docs/gnulinux/encrypted_parabola.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/gnulinux') diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index b2e40a01..74c74fce 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -284,7 +284,7 @@ directory to the one you created in the previous steps, so that you can modify f and install software onto it, as if it were the host operating 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). +Parabola 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 -- cgit v1.2.3-70-g09d2 From ff2b796271828a8e6271693e199f6d8fc7103458 Mon Sep 17 00:00:00 2001 From: mois Date: Mon, 21 May 2018 15:29:33 +0000 Subject: Update 'docs/gnulinux/grub_cbfs.md' corrected link in command --- docs/gnulinux/grub_cbfs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/gnulinux') diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md index 5283b4fc..ce7acab9 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -164,7 +164,7 @@ using `flashrom`, making sure to save it in the `cbfstool` folder, inside **libr If you are told to specify the chip, add the option `-c {your chip}` to the command, like this: $ sudo flashrom -c MX25L6405 -p internal -r ~/Downloads/libreboot_util/\ - >cbfstool/x86_64/cbfstool/x86_64/libreboot.rom + >cbfstool/x86_64/libreboot.rom Now you are ready to extract the GRUB configuration files from the ROM, and modify them the way you want. -- cgit v1.2.3-70-g09d2 From d58414906e8106f01be0d18616dab41846c9d72e Mon Sep 17 00:00:00 2001 From: mois Date: Mon, 21 May 2018 15:35:25 +0000 Subject: Update 'docs/gnulinux/grub_cbfs.md' deleted duplicate strings in paths --- docs/gnulinux/grub_cbfs.md | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) (limited to 'docs/gnulinux') diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md index ce7acab9..b0d7b0e3 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -152,19 +152,17 @@ used by coreboot native graphics initialization. I'll choose **x200_8mb_usqwerty_vesafb.rom**; I'll copy the file (to the `cbfstool` directory), and rename it with one command: - $ mv "x200_8mb_usqwerty_vesafb.rom" ../cbfstool/x86_64/cbfstool/x86_64/libreboot.rom + $ mv "x200_8mb_usqwerty_vesafb.rom" ../cbfstool/x86_64/libreboot.rom #### 2. Create an Image from the Current ROM The simpler way to get a ROM image is to just create it from your current ROM, using `flashrom`, making sure to save it in the `cbfstool` folder, inside **libreboot\_util**: - $ sudo flashrom -p internal -r ~/Downloads/libreboot_util/cbfstool/\ - >x86_64/cbfstool/x86_64/libreboot.rom + $ sudo flashrom -p internal -r ~/Downloads/libreboot_util/cbfstool/x86_64/libreboot.rom If you are told to specify the chip, add the option `-c {your chip}` to the command, like this: - $ sudo flashrom -c MX25L6405 -p internal -r ~/Downloads/libreboot_util/\ - >cbfstool/x86_64/libreboot.rom + $ sudo flashrom -c MX25L6405 -p internal -r ~/Downloads/libreboot_util/cbfstool/x86_64/libreboot.rom Now you are ready to extract the GRUB configuration files from the ROM, and modify them the way you want. @@ -173,7 +171,7 @@ Now you are ready to extract the GRUB configuration files from the ROM, and modi You can check the contents of the ROM image, inside CBFS, using `cbfstool`. First, navigate to the cbfstool folder: - $ cd ~/Downloads/libreboot_util/cbfstool/x86_64/cbfstool/x86_64/ + $ cd ~/Downloads/libreboot_util/cbfstool/x86_64/ Then, run the `cbfstool` commmand, with the `print` option; this will display a list of all the files located in the ROM: @@ -243,8 +241,7 @@ the main storage for **/boot/grub/libreboot\_grub.cfg** or **/grub/libreboot\_gr Therefore, we need to either copy **libreboot\_grub.cfg** to **/grub**, or to **/boot/grub**: - $ sudo cp ~/Downloads/libreboot_util/cbfstool/x86_64/cbfstool/x86_64/grubtest.cfg \ - >/boot/grub # or /grub + $ sudo cp ~/Downloads/libreboot_util/cbfstool/x86_64/grubtest.cfg /boot/grub # or /grub Now, the next time we boot our computer, GRUB (in Libreboot) will automatically switch to this configuration file. *This means that you do not have to re-flash, @@ -354,7 +351,7 @@ of **grubtest.cfg**, called **grub.cfg**. First, go to the `cbfstool` directory: - $ cd ~/Downloads/libreboot_util/cbfstool/x86_64/cbfstool/x86_64/ + $ cd ~/Downloads/libreboot_util/cbfstool/x86_64/ Then, create a copy of **grubest.cfg**, named **grub.cfg**: -- cgit v1.2.3-70-g09d2 From 09f20baa6d60665e9c8b7a3aff34c06ba3c12d11 Mon Sep 17 00:00:00 2001 From: mois Date: Mon, 21 May 2018 15:55:34 +0000 Subject: Update 'docs/gnulinux/grub_cbfs.md' another typo --- docs/gnulinux/grub_cbfs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/gnulinux') diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md index b0d7b0e3..4879d9cf 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -213,7 +213,7 @@ Or, replace it with this, if you are using a Debian-based distribution (e.g., Tr cryptomount -a set root='lvm/matrix-rootvol' - linux /vmlinuz root=/dev/mapper/matrix-rootvolcryptdevice=/dev/mapper/matrix-rootvol:root + linux /vmlinuz root=/dev/mapper/matrix-rootvol cryptdevice=/dev/mapper/matrix-rootvol:root initrd /initrd.img Remember, that these names come from the instructions to install GNU+Linux -- cgit v1.2.3-70-g09d2 From 89961a3cb7d38575c09ef72c350b7bddadf01756 Mon Sep 17 00:00:00 2001 From: Leah Rowe Date: Wed, 13 Jun 2018 21:43:14 +0100 Subject: Fix/update/remove dead/broken links on the website and documentation Thanks go to skollrc for pointing out these dead links, on this thread: https://www.reddit.com/r/libreboot/comments/8pjjg5/some_dead_links_in_libreboot _website/ --- docs/gnulinux/configuring_parabola.md | 2 +- docs/gnulinux/encrypted_parabola.md | 4 ++-- docs/gnulinux/grub_boot_installer.md | 2 +- docs/hardware/gm45_remove_me.md | 2 +- docs/hardware/x200.md | 6 ------ docs/install/index.md | 2 +- docs/install/rpi_setup.md | 2 +- projects/ich9gen/sources/src/gbe/gbe.h | 2 +- projects/ich9gen/sources/src/ich9deblob.c | 2 +- resources/utilities/ich9deblob/src/gbe/gbe.h | 2 +- resources/utilities/ich9deblob/src/ich9deblob.c | 2 +- www/news/andrew-robbins-new-maintainer.md | 2 +- 12 files changed, 12 insertions(+), 18 deletions(-) (limited to 'docs/gnulinux') diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md index 1e525f59..935ff099 100644 --- a/docs/gnulinux/configuring_parabola.md +++ b/docs/gnulinux/configuring_parabola.md @@ -63,7 +63,7 @@ For more information related to `pacman`, review the following articles on the A * [Configuring pacman](https://wiki.parabolagnulinux.org/Installation_Guide#Configure_pacman) * [Using pacman](https://wiki.archlinux.org/index.php/Pacman) -* [Additional Repositories](https://wiki.parabolagnulinux.org/Official_Repositories>) +* [Additional Repositories](https://wiki.parabolagnulinux.org/Official_Repositories) ## Updating Parabola Parabola is kept up-to-date, using `pacman`. When you are updating Parabola, diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index 74c74fce..48ef5b76 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -102,7 +102,7 @@ You can either fill the header with zeroes, or with random data; again, I chose Also, if you're using an SSD, there are a two things you should keep in mind: - There are issues with TRIM; it's not enabled by default through LUKS, -and there are security issues, if you do enable it. See [this page](https://wiki.archlinux.org/index.php/Dm-cryptSpecialties#Discard.2FTRIM_support_for_solid_state_drives_.28SSD.29) for more info. +and there are security issues, if you do enable it. See [this page](https://wiki.archlinux.org/index.php/Dm-crypt#Specialties) for more info. - Make sure to read [this article](https://wiki.archlinux.org/index.php/Solid_State_Drives), for information on managing SSD's in Arch Linux (the information applies to Parabola, as well). @@ -381,7 +381,7 @@ for the LUKS passphrase, apply here as well. You will set this password with the ### Extra Security Tweaks There are some final changes that we can make to the installation, to make it -significantly more secure; these are based on the [Security](https://wiki.archlinux.org/index.php/Securit) section of the Arch wiki. +significantly more secure; these are based on the [Security](https://wiki.archlinux.org/index.php/Security) section of the Arch wiki. #### Key Strengthening We will want to open the configuration file for password settings, and increase diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md index 7086b71d..7d4375e6 100644 --- a/docs/gnulinux/grub_boot_installer.md +++ b/docs/gnulinux/grub_boot_installer.md @@ -25,7 +25,7 @@ Overwrite the drive, writing your distro ISO to it with `dd`. For example, if we That's it! You should now be able to boot the installer from your USB drive (the instructions for doing so will be given later). ## Prepare the USB drive in NetBSD -[This page](https://wiki.netbsd.org/tutorials how_to_install_netbsd_from_an_usb_memory_stick/) on the NetBSD website shows how to create a NetBSD bootable USB drive, from within NetBSD itself. You should the `dd` method documented there. This will work with any GNU+Linux ISO image. +[This page](https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/) on the NetBSD website shows how to create a NetBSD bootable USB drive, from within NetBSD itself. You should the `dd` method documented there. This will work with any GNU+Linux ISO image. ## Prepare the USB drive in FreeBSD [This page](https://www.freebsd.org/doc/handbook/bsdinstall-pre.html) on the FreeBSD website shows how to create a bootable USB drive for installing FreeBSD. Use the `dd` method documented. This will work with any GNU+Linux ISO image. diff --git a/docs/hardware/gm45_remove_me.md b/docs/hardware/gm45_remove_me.md index 0ac2f49b..26e5f9f6 100644 --- a/docs/hardware/gm45_remove_me.md +++ b/docs/hardware/gm45_remove_me.md @@ -418,7 +418,7 @@ region. According to the datasheet, it's supposed to add up to 0xBABA but can actually be others on the X200. - + *"One of those engineers loves classic rock music, so they selected 0xBABA"* diff --git a/docs/hardware/x200.md b/docs/hardware/x200.md index 10f5f621..fdf992d1 100644 --- a/docs/hardware/x200.md +++ b/docs/hardware/x200.md @@ -132,12 +132,6 @@ comparing it with X200 (factory BIOS) and X200 (gm45 raminit code in coreboot), to see what the differences are. Then tweak raminit code based on that. -Trouble undocking (button doesn't work) ----------------------------------------- - -This person seems to have a workaround: - - LCD compatibility list {#lcd_supported_list} ---------------------- diff --git a/docs/install/index.md b/docs/install/index.md index d4ac2f13..6cefad56 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -169,7 +169,7 @@ ASUS KCMA-D8? ------------- If you have the proprietary BIOS, you need to flash libreboot -externally. See [kcma-d8.md](kgpe-d8.md). +externally. See [kcma-d8.md](kcma-d8.md). If you already have coreboot or libreboot installed, without write protection on the flash chip, then you can do it in software (otherwise, diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md index e46191e7..b083aac9 100644 --- a/docs/install/rpi_setup.md +++ b/docs/install/rpi_setup.md @@ -150,7 +150,7 @@ successfully. If not, just flash again. Pi](http://scruss.com/blog/2013/02/02/simple-adc-with-the-raspberry-pi/) - [Flashing coreboot on a T60 with a Raspberry Pi - the\_unconventional's - blog](https://blogs.fsfe.org/the_unconventional/2015/05/08/flashing-coreboot-on-a-t60-with-a-raspberry-pi/) + blog](https://web.archive.org/web/20150709043222/http://blogs.fsfe.org:80/the_unconventional/2015/05/08/coreboot-t60-raspberry-pi/) - *Pomona SOIC Clip flashing* - [Arch Linux Wiki - Installing Arch Linux on Chromebook](https://wiki.archlinux.org/index.php/Chromebook) diff --git a/projects/ich9gen/sources/src/gbe/gbe.h b/projects/ich9gen/sources/src/gbe/gbe.h index 14548e71..f28f4421 100644 --- a/projects/ich9gen/sources/src/gbe/gbe.h +++ b/projects/ich9gen/sources/src/gbe/gbe.h @@ -35,7 +35,7 @@ * * Info about Gbe region (read whole datasheet): * http://www.intel.co.uk/content/dam/doc/application-note/i-o-controller-hub-9m-82567lf-lm-v-nvm-map-appl-note.pdf - * https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums + * https://web.archive.org/web/20150912070329/https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums */ #ifndef GBESTRUCT_H diff --git a/projects/ich9gen/sources/src/ich9deblob.c b/projects/ich9gen/sources/src/ich9deblob.c index b9153ed6..d7a57c51 100644 --- a/projects/ich9gen/sources/src/ich9deblob.c +++ b/projects/ich9gen/sources/src/ich9deblob.c @@ -42,7 +42,7 @@ * * Info about Gbe region (read whole datasheet): * http://www.intel.co.uk/content/dam/doc/application-note/i-o-controller-hub-9m-82567lf-lm-v-nvm-map-appl-note.pdf - * https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums + * https://web.archive.org/web/20150912070329/https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums */ #include "ich9deblob.h" diff --git a/resources/utilities/ich9deblob/src/gbe/gbe.h b/resources/utilities/ich9deblob/src/gbe/gbe.h index a1350fdd..454ab2a2 100644 --- a/resources/utilities/ich9deblob/src/gbe/gbe.h +++ b/resources/utilities/ich9deblob/src/gbe/gbe.h @@ -35,7 +35,7 @@ * * Info about Gbe region (read whole datasheet): * http://www.intel.co.uk/content/dam/doc/application-note/i-o-controller-hub-9m-82567lf-lm-v-nvm-map-appl-note.pdf - * https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums + * https://web.archive.org/web/20150912070329/https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums */ #ifndef GBESTRUCT_H diff --git a/resources/utilities/ich9deblob/src/ich9deblob.c b/resources/utilities/ich9deblob/src/ich9deblob.c index d79a3a89..d0fc537a 100644 --- a/resources/utilities/ich9deblob/src/ich9deblob.c +++ b/resources/utilities/ich9deblob/src/ich9deblob.c @@ -42,7 +42,7 @@ * * Info about Gbe region (read whole datasheet): * http://www.intel.co.uk/content/dam/doc/application-note/i-o-controller-hub-9m-82567lf-lm-v-nvm-map-appl-note.pdf - * https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums + * https://web.archive.org/web/20150912070329/https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums */ #include "ich9deblob.h" diff --git a/www/news/andrew-robbins-new-maintainer.md b/www/news/andrew-robbins-new-maintainer.md index 50c43d3a..65fd8a3c 100644 --- a/www/news/andrew-robbins-new-maintainer.md +++ b/www/news/andrew-robbins-new-maintainer.md @@ -9,7 +9,7 @@ voted on by the maintainers with community input. These policies formalise our democratic standards. Today, we welcome Andrew Robbins (IRC nick `and_who` and -[NotABug](https://notabug.org) user [kragle](https://notabug.org/kragle)) as +[NotABug](https://notabug.org) user [and_who](https://notabug.org/and_who)) as our first new maintainer under the new policy. Going forward, Andrew will gain push access to Libreboot in order to review patches, as well as voting rights and IRC operator status. -- cgit v1.2.3-70-g09d2 From 57965e5ea62232fe0f0e7123ddf0d2b563718c48 Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Sun, 24 Jun 2018 07:51:59 +0200 Subject: Missing -o in grub-mkconfig --- docs/gnulinux/encrypted_parabola.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/gnulinux') diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index 74c74fce..d65d076e 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -422,7 +422,7 @@ Edit configuration in `/etc/default/grub`, remembering to use UUID when poitning Use `blkid` to get list of devices with their respective UUIDs. Next generate grub.cfg with - # grub-mkconfig /boot/grub/grub.cfg + # grub-mkconfig -o /boot/grub/grub.cfg If you have separate `/boot` partition, don't forget to add `boot` symlink inside that points to current directory -- cgit v1.2.3-70-g09d2 From f1ed499c93eeb8f908ea685fe781759234f87a4d Mon Sep 17 00:00:00 2001 From: "John M. Harris, Jr" Date: Fri, 13 Jul 2018 14:22:26 -0400 Subject: Fix link to information about HDD/SSD firmware --- docs/gnulinux/grub_hardening.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/gnulinux') diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md index 9eb7237e..e1329f21 100644 --- a/docs/gnulinux/grub_hardening.md +++ b/docs/gnulinux/grub_hardening.md @@ -33,7 +33,7 @@ Helpful links: - [GRUB manual](https://www.gnu.org/software/grub/manual/html_node/Security.html#Security) - [GRUB info pages](http://git.savannah.gnu.org/cgit/grub.git/tree/docs/grub.texi) -- [SATA connected storage considered dangerous.](../../faq.md#firmware-hddssd) +- [SATA connected storage considered dangerous.](../../faq.md#hddssd-firmware) - [Coreboot GRUB security howto](https://www.coreboot.org/GRUB2#Security) GRUB Password -- cgit v1.2.3-70-g09d2