From 6ea2b7023b65755d2f68c625646d8927babe270b Mon Sep 17 00:00:00 2001 From: Swift Geek Date: Mon, 13 Nov 2017 05:53:57 +0000 Subject: Clarification on BUC.TS Missing trivia that can cause a brick --- docs/install/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'docs/install') diff --git a/docs/install/index.md b/docs/install/index.md index 70dd554e..ea48632d 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -283,6 +283,8 @@ ThinkPad X60/T60: Initial installation guide (if running the proprietary firmwar already have coreboot or libreboot running, then go to [\#flashrom](#flashrom) instead!* +*If you can, make sure that RTC battery is not discharged. Discharged RTC battery may lead to brick due to not holding BUC register value* + *If you are flashing a Lenovo ThinkPad T60, be sure to read [../hardware/\#supported\_t60\_list](../hardware/#supported_t60_list)* @@ -324,7 +326,7 @@ Seeing this means that the operation was a *resounding* success! See this link for more details: . -If the above is what you see, then *SHUT DOWN*. Wait a few seconds, +If the above is what you see, then *SHUT DOWN* (but do not remove power, especially RTC battery). Wait a few seconds, and then boot; libreboot is running, but there is a 2nd procedure needed (see below). -- cgit v1.2.3-70-g09d2 From dbf207f8f93ebf35b65554634b12210c7d938236 Mon Sep 17 00:00:00 2001 From: "konstantin.grudnev" Date: Mon, 20 Nov 2017 16:06:22 +0300 Subject: Core Quad update info about compatible CPUs for T500 --- docs/install/t500_external.md | 3 +++ 1 file changed, 3 insertions(+) (limited to 'docs/install') diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md index 37217337..c9b85a5d 100644 --- a/docs/install/t500_external.md +++ b/docs/install/t500_external.md @@ -39,6 +39,9 @@ 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. +Q9100 is compatible and confirmed working (after hw mod), as reported by users in the IRC +channel + - [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) -- cgit v1.2.3-70-g09d2 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 ++- docs/install/x60_unbrick.md | 13 ++++++------- docs/install/x60tablet_unbrick.md | 13 ++++++------- 4 files changed, 31 insertions(+), 20 deletions(-) (limited to 'docs/install') 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 diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md index 0f215302..d7cb17a8 100644 --- a/docs/install/x60_unbrick.md +++ b/docs/install/x60_unbrick.md @@ -20,13 +20,12 @@ two:\ \*Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this -applied!):\ -dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s -coreboot.rom) - 0x10000\] count=64k\ -dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] -count=64k | hexdump\ -dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s -coreboot.rom) - 0x20000\] count=64k conv=notrunc\ +applied!): + + dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x10000\] count=64k + dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] count=64k | hexdump + dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] count=64k conv=notrunc + (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, using those instructions: . diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md index f4baebf4..fe4352bc 100644 --- a/docs/install/x60tablet_unbrick.md +++ b/docs/install/x60tablet_unbrick.md @@ -20,13 +20,12 @@ two:\ \*Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this -applied!):\ -dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s -coreboot.rom) - 0x10000\] count=64k\ -dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] -count=64k | hexdump\ -dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s -coreboot.rom) - 0x20000\] count=64k conv=notrunc\ +applied!): + + dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x10000\] count=64k + dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] count=64k | hexdump + dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] count=64k conv=notrunc + (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, using those instructions: . -- cgit v1.2.3-70-g09d2 From 81c76feaebe09c382e0fbfd42e358fc6710d47eb Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Tue, 20 Mar 2018 19:45:38 +0100 Subject: Remove explody bits from guide --- docs/install/rpi_setup.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/install') diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md index e74432d4..e46191e7 100644 --- a/docs/install/rpi_setup.md +++ b/docs/install/rpi_setup.md @@ -283,10 +283,10 @@ your PI. Power on your Pi, and run the following. Ensure you swap out "your\_chip\_name" with the proper name/model of your chip. Check that it can be read successfully. If you cannot read the chip and receive an -error similar to "no EEPROM Detected" or "0x0 Chip detected" then -you may want to try powering off your PI, and switching the two pins -which are connected to the IO ports. I.E. Connect pins (clip)8 to (pi)19 -and pins (clip)15 to (pi)21 +error similar to "no EEPROM Detected" then +you may want to make sure that MISO/MOSI are not swapped around, check +with multimeter whether voltage is right and that ground is connected +between "programmer" and target. pi# cd ~/flashrom -- cgit v1.2.3-70-g09d2 From 796d78c6a5041cd4a5adb451a08837a3e9a9858b Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Wed, 28 Mar 2018 04:17:28 +0200 Subject: Add disclaimer about BBB being example --- docs/install/bbb_setup.md | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'docs/install') diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md index 94cfdc0b..f2bb840b 100644 --- a/docs/install/bbb_setup.md +++ b/docs/install/bbb_setup.md @@ -8,6 +8,16 @@ flash chip with the BeagleBone Black, using the rev. C was used when creating this guide, but earlier revisions may also work. +***NOTE: Use of BeagleBone black is for example purposes only, +don't buy it unless you want _it_ specifically.*** *There are many ARM +Single Board Computers (SBC) that are capable of in system programming +(external flashing) and they perform similarly terrible at that task. +Common use of devicetrees on those devices allows for configuring them +in similar way, but not identical, so a bit of own research is required. +Lastly SBC is an example of self-contained device that is capable of flashing, +but it's possible to use smaller device like stm32 bluepill +with another computer to achieve similar result.* + *NOTE: this documentation may be outdated, and discusses configuring SPI flashing on the default Debian system that the BBB sometimes comes with. If you want an easier time, just use [BBB -- cgit v1.2.3-70-g09d2 From e87f326a7fe2f3493a28f4e25d207f4d05f7c050 Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Wed, 9 May 2018 19:20:15 +0200 Subject: c201.md: fix WP screw description It cannot be pulled low because that would enable #WP So I assume it's pulled up weakly on motherboard with some resistor --- docs/install/c201.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/install') diff --git a/docs/install/c201.md b/docs/install/c201.md index 238c0734..3045b062 100644 --- a/docs/install/c201.md +++ b/docs/install/c201.md @@ -155,7 +155,7 @@ to be opened. The SPI flash is located next to the write protect screw. Its layout is indicated in the picture below. Note that it is not necessary to connect -`WP#` since removing the screw already connects it to ground. Before +`WP#` since after removing the screw it is pulled up weakly to 3v3. Before writing to the chip externally, the battery connector has to be detached. It is located under the heat spreader, that has to be unscrewed from the rest of the case. The battery connector is located on -- cgit v1.2.3-70-g09d2 From 90d88750f81e9c9badd40721fd6868170d51ae2e Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Wed, 9 May 2018 19:26:21 +0200 Subject: c201.md: change phrasing for detaching battery don't tell people to rip out the sockets from the motherboard, this ain't nokia 3310 --- docs/install/c201.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/install') diff --git a/docs/install/c201.md b/docs/install/c201.md index 3045b062..fb39196a 100644 --- a/docs/install/c201.md +++ b/docs/install/c201.md @@ -156,9 +156,9 @@ to be opened. The SPI flash is located next to the write protect screw. Its layout is indicated in the picture below. Note that it is not necessary to connect `WP#` since after removing the screw it is pulled up weakly to 3v3. Before -writing to the chip externally, the battery connector has to be -detached. It is located under the heat spreader, that has to be -unscrewed from the rest of the case. The battery connector is located on +writing to the chip externally, the battery has to be unplugged. +Battery connector is located under the heat spreader, that has to be +unscrewed from the rest of the case. It is located on the right and has colorful cables, as shown on the picture below. [![SPI flash -- cgit v1.2.3-70-g09d2 From e9aa96f3d2b482faddfa9a4d8ebe979692c2d5d4 Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Wed, 9 May 2018 19:30:43 +0200 Subject: bbb_setup.md: lost asterisk --- docs/install/bbb_setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/install') diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md index f2bb840b..5d684a7f 100644 --- a/docs/install/bbb_setup.md +++ b/docs/install/bbb_setup.md @@ -236,7 +236,7 @@ Output: Verify that the spidev device now exists: - # ls -al /dev/spid + # ls -al /dev/spid* Output: -- cgit v1.2.3-70-g09d2 From 5c9c33854efe9285a79d510a90181b5c8eeb4864 Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Sun, 27 May 2018 12:20:52 +0200 Subject: Clarify image verification --- docs/install/x200_external.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'docs/install') diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md index 3ff34501..5dd39877 100644 --- a/docs/install/x200_external.md +++ b/docs/install/x200_external.md @@ -163,7 +163,9 @@ Now compare the 3 images: # sha512sum factory*.rom -If the hashes match, then just copy one of them (the factory.rom) to a +If the hashes match and if hex editor (like `dhex`) shows that +they have valid contents (eg. it's not filled entirely with `0x00`/`0xFF`), +then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This is useful for reverse engineering work, if there is a desirable behaviour in the original firmware that could be replicated in coreboot -- cgit v1.2.3-70-g09d2 From a117c5c29b4c8adc59ec9183d2f5373d41db952a Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Sun, 27 May 2018 12:22:38 +0200 Subject: Remove -V from flashrom command examples --- docs/install/x200_external.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/install') diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md index 5dd39877..83a5c23f 100644 --- a/docs/install/x200_external.md +++ b/docs/install/x200_external.md @@ -19,7 +19,7 @@ Flash chip size Run this command on x200 to find out flash chip model and its size: - # flashrom -p internal -V + # flashrom -p internal 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 @@ -180,7 +180,7 @@ address to one that is correct for your system. Now flash it: - # ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V + # ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom ![](images/x200/disassembly/0015.jpg) -- 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/install') 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 23ca4041a92c5e9f54d60033b3a19f62f628734a Mon Sep 17 00:00:00 2001 From: nicorikken Date: Tue, 19 Jun 2018 06:13:44 +0000 Subject: Pending change for CMOS value naming 'switchable graphics' -> 'dual graphics' I proposed a naming patch for the T400 CMOS value in the Coreboot project: https://review.coreboot.org/#/c/coreboot/+/27158/ As this is the only manual referring to the name of the value, this commit updates the naming to reflect the upstream change. Merging this patch becomes relevant once the coreboot patch has made it's way into Libreboot. --- docs/install/r400_external.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'docs/install') diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md index 366896cb..4036c761 100644 --- a/docs/install/r400_external.md +++ b/docs/install/r400_external.md @@ -44,9 +44,10 @@ A note about GPUs ================= Some models have an Intel GPU, while others have both an ATI and an -Intel GPU; this is referred to as "switchable graphics". In the *BIOS -setup* program for lenovobios, you can specify that the system will use -one or the other (but not both). +Intel GPU; this is referred to as "Dual Graphics" (previously +"switchable graphics"). In the *BIOS setup* program for lenovobios, +you can specify that the system will use one or the other (but not +both). Libreboot is known to work on systems with only the Intel GPU, using native graphics initialization. On systems with switchable graphics, the @@ -365,6 +366,7 @@ You should see something like this: Now [install GNU+Linux](../gnulinux/). Copyright © 2014, 2015 Leah Rowe \ +Copyright © 2018 Nico Rikken \ Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License Version 1.3 or any later -- cgit v1.2.3-70-g09d2 From 608c4e066dd3722269747fc61d238f1513e9237a Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Sun, 24 Jun 2018 08:04:36 +0200 Subject: Clarify memtest86+ section --- docs/install/index.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'docs/install') diff --git a/docs/install/index.md b/docs/install/index.md index d4ac2f13..677fd244 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -62,10 +62,12 @@ they don't have to build anything from source on their own. The ROM images in each archive use the following at the end of the file name, if they are built with the GRUB payload: `*_*keymap*_*mode*.rom` -Available `modes`: `vesafb` or `txtmode`. The `vesafb` ROM images -are recommended, in most cases; `txtmode` ROM images come with -MemTest86+, which requires text-mode instead of the usual framebuffer -used by coreboot native graphics initialization. +Available modes: vesafb or txtmode. The vesafb ROM images are recommended +for regular use, but when flashing for the first time use txtmode version, +as it comes with Memtest86+, which requires text-mode instead of the usual +framebuffer used by coreboot native graphics initialization. +Machine should be tested with Memtest86+ after each reassembly or changing +from vendor bios to libreboot due to differences in raminit code. `keymap` can be one of several keymaps that keyboard supports (there are quite a few), which affects the keyboard layout configuration that is -- cgit v1.2.3-70-g09d2 From 2bac42b742a0217396dd68f4c77c40cf2360f04a Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Sun, 24 Jun 2018 15:09:56 +0200 Subject: Improve T500 sodimm notes --- docs/install/t500_external.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'docs/install') diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md index c9b85a5d..9e114bca 100644 --- a/docs/install/t500_external.md +++ b/docs/install/t500_external.md @@ -362,11 +362,12 @@ Not to be confused with wifi (wifi is fine). Memory ====== -You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs -(speed/size). Non-matching pairs won't work. You can also install a +DDR3 SO-DIMM sticks will work at PC3-8500 clock and voltage, so make sure that +timings of sticks are matched while they operate at its frequency. +Non-matching pairs won't work. You can also install a single module (meaning, one of the slots will be empty) in slot 0. -Make sure that the RAM you buy is the 2Rx8 density. +Make sure that the RAM you buy has 2Rx8 arrangement when buying 4GiB modules. [This page](http://www.forum.thinkpads.com/viewtopic.php?p=760721) might be useful for RAM compatibility info (note: coreboot raminit is -- cgit v1.2.3-70-g09d2 From b10bb838279c1fdd31fb832430b036940f457974 Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Tue, 26 Jun 2018 18:24:13 +0200 Subject: Change space to non-breaking space U+00A0 --- docs/install/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/install') diff --git a/docs/install/index.md b/docs/install/index.md index d4ac2f13..c4ed5dc9 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 -- cgit v1.2.3-70-g09d2 From 1fb8dafbb9e59de5c48b976fe511c58175a731f8 Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Tue, 26 Jun 2018 18:58:59 +0200 Subject: Missed from previous nbsp commit --- docs/install/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/install') diff --git a/docs/install/index.md b/docs/install/index.md index c4ed5dc9..7639c14d 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -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,11 +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: @@ -372,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: -- cgit v1.2.3-70-g09d2 From a5348fe90a197736a020a87905e3d5f27f0a988f Mon Sep 17 00:00:00 2001 From: Sebastian 'Swift Geek' Grzywna Date: Tue, 26 Jun 2018 19:04:01 +0200 Subject: install/index.md: Remove -V from flashrom command --- docs/install/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/install') diff --git a/docs/install/index.md b/docs/install/index.md index 677fd244..67c5d722 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -246,7 +246,7 @@ Flash chip size Use this to find out: - # flashrom -p internal -V + # flashrom -p internal All good? --------- -- cgit v1.2.3-70-g09d2