From: eliot <eliot@web>
Date: Sat, 25 May 2019 18:52:22 +0000 (+0200)
Subject: X200 minor improvements
X-Git-Url: https://git.g-eek.se/?a=commitdiff_plain;h=624cac73f0041aa86c09c3f1b48fc3535116b808;p=inbyggd-frihet-wiki.git

X200 minor improvements
---

diff --git a/guider.mdwn b/guider.mdwn
index 31f1fdc..a52c7fe 100644
--- a/guider.mdwn
+++ b/guider.mdwn
@@ -94,10 +94,9 @@ This works very good with openbsd6.0(and 6.2), read more [here](https://libreboo
 
 [update] I have run openbsd 6.2 with libreboot on thinkpad x200 for about two months now without any errors, still no update on the harddisk crypto
 
-###Building Libreboot [WIP]
-    #Get a newer version of flashrom than in Debian repo
-    #In my case the older version did not detect the exact chip on x200
-    #This was fixed by cloning and building the most recent version
+###Building Libreboot
+This script worked 2019-04, however we noted that the cryptomount program had less features in the version from Git at that time, compared to the 2016 stable release.
+Unlike Coreboot, this build process is fairly automated and does not present any customization choices by default
 
     #!/bin/bash -e
     cd libreboot
@@ -133,7 +132,8 @@ This works very good with openbsd6.0(and 6.2), read more [here](https://libreboo
     cd ./crossgcc/util/cbfstool/
     make
     cd ../../../
-
+    
+    #BUILD COMPLETE, now fix the image
     #finally build the ROM we want
     ./oldbuild roms withgrub x200_8mb
 
@@ -144,11 +144,12 @@ This works very good with openbsd6.0(and 6.2), read more [here](https://libreboo
     mv x200.rom ../../../
     cd ../../../
 
+    #FINALLY add or change the files in the image for customization
     #./cbfstool x200.rom extract -n grub.cfg -f grubtest.cfg
     #./crossgcc/util/cbfstool/cbfstool x200_other_mac.rom remove -n grubtest.cfg
     #./crossgcc/util/cbfstool/cbfstool x200_other_mac.rom add -n grubtest.cfg -f grubtest.cfg -t raw
 
-    ## LASTLY FLASH TO CHIP
+    ## LASTLY FLASH TO CHIP (here internally)
     #sudo ./flashrom/flashrom -p internal -w x200.rom
     
 
@@ -163,12 +164,12 @@ Note these tools are built and ready [at](https://www.mirrorservice.org/sites/li
     #backup current rom
     sudo ./flashrom  -p internal -r libreboot.rom 
 
-    #remove old GRUB (test) config
+    #Optional: remove old GRUB (test) config
     ./cbfstool libreboot.rom remove -n grubtest.cfg
-    #get the new GRUB (test) config into your ROM
+    #Optional: get the new GRUB (test) config into your ROM
     ./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t raw   
     
-    #change background in GRUB menu (dest must be called background.png /jpg)
+    #Optional: change background in GRUB menu (dest must be called background.png /jpg)
     #./cbfstool yourrom.rom remove background.png -n background.png
     #./cbfstool yourrom.rom add -f background.png -n background.png -t raw
 
@@ -213,9 +214,7 @@ Debian Stretch
 
 Nvidia GTX 660, Nouveau drivers but crashes when playing videos. Probably my fault however.
 
-For our software configs, see: [[https://github.com/Eliot-Roxbergh/dotFIles/]]
-
-TODO improve GRUB config
+For one example software config, see: [[https://github.com/Eliot-Roxbergh/dotFIles/]]
 
 ####Flashing
 Buy a couple of flash chips in case of you breaking them, and to test different payloads. Furthermore, one could buy a proprietary chip just to debug the hardware. 
@@ -275,7 +274,7 @@ ROM-chip (eg.): Winbond W25Q16DV (if ROM too small can extend, see: *Extend 2MB
     ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w ~/libreboot_r20160907_grub_kgpe-d16/kgpe-d16_svenska_txtmode.rom
 
     ## NOTE ##
-    # In my case (KGPE-D16) it was very difficult - seemingly at random - to achieve a configuration such as read and write had good reliability.
+    # In my case (KGPE-D16) it was somewhat difficult - seemingly at random - to achieve a configuration such as read and write had good reliability.
     # Furthermore, writing had good success rate while reading was more error prone.
     # Thus, it is possible to write to the ROM and read (e.g.) 10 times and compare the resulting `sha512sum` to that of the ROM downloaded from Libreboot.
     # If the sum EXACTLY matches atleast once, it is reasonable to assume that the write indeed succeeded (we believe).