(no commit message)

diff --git a/guider.mdwn b/guider.mdwn
index fa9440082b75a36280ab3c9993ac91480f6f6b7c..ed92ea37c728d9a5b5e50117ddd93f70c761f929 100644 (file)
--- a/guider.mdwn
+++ b/guider.mdwn
@@ -235,9 +235,9 @@ Unlike Coreboot, this build process is fairly automated and does not present any
     ## LASTLY FLASH TO CHIP (here internally)
     #sudo ./flashrom/flashrom -p internal -w x200.rom
 
-## Specific guides
+# Specific guides
 
-### T400 without blobs (Coreboot)
+## T400 without blobs (Coreboot)
 Here's our config for coreboot, copy it here to this path [coreboot/.config](t400_coreboot/).
 ( Below in the text we refer to it as ~/coreboot_config_t400_8mb )
 
@@ -305,25 +305,25 @@ Here's our config for coreboot, copy it here to this path [coreboot/.config](t40
     ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w ~/t400_8mb_coreboot_flashable.rom
     #Should say "Verified". If you're paranoid you could read it again and check hash.
     
-### X230 (Coreboot)
+## X230 (Coreboot)
 
 Make sure bios has latest EC version. We had EC 1.14 (G2HT35WW), this should be the latest (citation needed).
 
-#### Internally
+### Internally
 
 Due to security weakness in older versions of the proprietary BIOS, it is now possible to flash internally.
 This is the recommended procedure for X230.
 
 See: <https://doc.coreboot.org/mainboard/lenovo/ivb_internal_flashing.html?highlight=x230>
 
-#### Externally (not recommended)
+### Externally (not recommended)
 
-##### Warning
+#### Warning
 
 As we flashed externally, we were not careful enough, and accidentally lost a resistor. This is certainly a risk when flashing by this method, the same issue as described here
 <https://www.reddit.com/r/coreboot/comments/dhwdss/did_i_just_brick_my_x230/fmytpm0/?utm_source=reddit&utm_medium=web2x&context=3> (supposedly a R1378, SMD 33.2Ω resistor). With open circuit here computer cannot boot, however by adding it back or by shorting it it will be able to boot (after booting, the computer can run with an open circuit here ... seemingly).
 
-##### Instructions
+#### Instructions
 
 After asking on IRC the recommendation was to, on the signal lines, add a resistor e.g. 47 Ohm... presumably for both data lines and clock?
 
@@ -361,16 +361,16 @@ Both chips should have the same layout. Read from both chips SPI2 (4MB) and SPI1
 To be continued ...
 
 
-### KGPE-D16 (Libreboot)
+## KGPE-D16 (Libreboot)
 
-#### Summary, using this free computer as a workstation
+### Summary, using this free computer as a workstation
 
 Once you have flashed and found working memory for the system. It works rather well, no need to remove CMOS battery for instance (if no picture/boot, just disconnect PSU for a sec and restart).
 Small annoyance is that the computer won't start with USB _storage_ attached (so instead, you should disconnect these and reconnect when grub is shown).
 It is a good machine for every day use (free firmware & 32 cores and 64GB DDR3 ECC RAM), and possible to find used starting at 5k = 3k+1k+1k (motherboard+cpu&cooler+ram), remember that external GPU and sound cards will be needed.
 The single-thread performance is rubbish and a major bottleneck for certain applications (no you can't play CS:GO or other modern video games, and only slight performance gain can be achieved by forcing all threads to highest clock in Linux with cpupower). The other downside is that the dual CPU system draws ~200 watts IN IDLE (and 400w at full load).
 
-#### General
+### General
 
 Also Raptor Engineering was working on new free features (OpenBMC, IPMI, and Thermal management drivers) for this board, [here](https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php).
 
@@ -388,28 +388,28 @@ Also Raptor Engineering was working on new free features (OpenBMC, IPMI, and The
   * Note: It is necessary to have a dedicated sound card and graphics card, _if_ those features are desired.
 
 
-#### Using
+### Using
   * Both GRUB and SeaBIOS work. But SeaBIOS has worked better when booting from CD-ROM or USB.
   * If problems booting, disconnect power and remove CMOS battery for a couple of seconds.
   * The default script in GRUB does not work with encrypted boot-partition (can manually boot).
   * When booting from GRUB, you might want to use "load config from external device" instead of "boot USB". Recommended when booting LiveCDs etc., if you don't have any particular configuration locally.
 
-#### Quirks SeaBIOS stable
+### Quirks SeaBIOS stable
   * With the stable release and SeaBIOS, most is working well but there is still one issue with USB devices at boot.
 **Example:** A USB stick is connected at the back of the moderboard when the computer boots.
 Suddenly, USB ports does not work, such as the chassi's USB hub which is connected on the moderboard.
 These are completely dead and the peripheral devices does not light up. Only rebooting does not help.
 **Solution**, turn off computer and disconnect power (we did not need to clear CMOS), and disconnect the problematic USB stick on the back. Turn on power. The USB stick can now be plugged in when the hardware has been initialized and GRUB is shown.
 
-#### Quirks with earlier GRUB version
+### Quirks with earlier GRUB version
   * Sometimes we get an error when booting, this is resolved by disconnecting USD devices such as keyboard and mouse until the hardware is initiated.
   * In GRUB the USB keyboard is sometimes unusably slow. Fix: always have a PS/2 keyboard connected, but use the USB keyboard.
   * In some configurations the fans will always be low and the system fail to boot, which would also overheat the already stuck system (!), thus you might want to power the fans with PSU instead of board.
 
-#### Debugging
+### Debugging
   * If you can't boot: reset CMOS (battery and power), make sure your graphic output correctly set (jumper on board). Otherwise, it is most likely a memory, CPU or ROM-image problem. Try to boot with as little RAM as possible or other memory brand, make sure the CPU is properly seated, verify ROM image on chip (e.g. check hashsum) - we have had all these problems. Finally, you can use a serial cable to debug and get an idea about the issue, and ask in Libreboot IRC.
 
-#### Our Tested Systems
+### Our Tested Systems
 
 ##### A
 
@@ -427,7 +427,7 @@ Modern AMD graphics card (not fully free!)
 Sound card (not fully free!)
 
 
-##### B
+#### B
 
 Debian Stretch
 
@@ -438,7 +438,7 @@ ASUS KGPE-D16 (1.03G)
 4x 4GB 1333Mhz Reg-ECC HMT151R7BFR4C-H9 
 
 
-#### Pics: The systems (old)
+### Pics: The systems (old)
 
 [Div pics a](resources/div_pics/d16_a.jpg), [Div pics b](resources/div_pics/d16_b.jpg), [Div pics c](resources/div_pics/d16_c.jpg), [Div pics d](resources/div_pics/d16_d.jpg), [Div pics e](resources/div_pics/d16_e.jpg),
 
@@ -453,13 +453,13 @@ ASUS KGPE-D16 (1.03G)
 [pic 4](resources/div_pics/d16_f.jpg)
 
 
-#### Manuals for flashing
+### Manuals for flashing
 
 [D16-chip](resources/d16_chip.png)
 
 [Beagleboard Black P9 connector](resources/BBB_P9.png)
 
-#### Flashing Instructions
+### Flashing Instructions
 
 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.