General update for KGPE-D16

diff --git a/guider.mdwn b/guider.mdwn
index 43e572e842be9b329c186049c78eae9f0ee8db5b..ca8268b2be330cef8dec1cffa2c9e35884b58b94 100644 (file)
--- a/guider.mdwn
+++ b/guider.mdwn
@@ -203,27 +203,42 @@ Note these tools are built and ready [at](https://www.mirrorservice.org/sites/li
 
 ####Using
   * GRUB is recommended. But SeaBIOS has worked better when booting from CD-ROM or USB.
-  * When booting from USB, connect the USB-stick NOT BEFORE GRUB menu is shown.
   * 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 dont have any particular configuration locally.
 
 ####Quirks
+  * Sometimes I get an error when booting, this is resolved by disconnecting keyboard and mouse until the hardware is initiated.
+  * When booting from USB, connect the USB-stick NOT BEFORE GRUB menu is shown... if the USB could not be found.
   * In GRUB the USB keyboard is unusably slow. Fix: always have a PS/2 keyboard connected, but use the USB keyboard.
   * In *earlier* versions of Libreboot the boot process could take up to five minutes (!), be patient.
   * 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 or ROM-image problem. You can use a serial cable to debug and get an idea about the issue.
   * When I had major problems booting I had some help by sound cues and measuring current power draw, to recognize when the boot would likely fail (if you cannot use serial cable). When booting successfully the system (1x 6276, 32GB) drew 180->200->218->166w (GRUB), otherwise it had a different behavior. Furthermore, after disconnecting the power the system would never boot without also clearing CMOS. The system would get stuck and the fans would always go high. While in a healthy boot would start fans low and then ramp up when starting GRUB and then stay there (fans connects to board directly). These sound cues were useful as you can be quite sure the system booted successfully without having any graphic output. 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.
 
 ####Our Systems
-Debian Stretch
+Debian Buster
 
-1x 6276 CPU
+ASUS KGPE-D16 (1.03G)
+
+2x 6276 CPU
+
+4x 16GB 1600Mhz Reg-ECC *MT36JSF2G72PZ-1G6E1LG (HP: 672612-081)* [max 32GB/CPU!](https://www.coreboot.org/Board:asus/kgpe-d16/known_bad_configs)
+
+Modern AMD graphics card (not fully free!)
+
+Sound card (not fully free!)
 
-2x 16GB 1600Mhz Reg-ECC *MT36JSF2G72PZ-1G6E1LG (HP: 672612-081)* [max 32GB/CPU!](https://www.coreboot.org/Board:asus/kgpe-d16/known_bad_configs)
+AND 
 
-Nvidia GTX 660, Nouveau drivers but crashes when playing videos. Probably my fault however.
+[RETIRED COMPUTER]
+
+Debian Stretch
+
+ASUS KGPE-D16 (1.03G)
+
+1x 6276 CPU
 
-For one example software config, see: [[https://github.com/Eliot-Roxbergh/dotFIles/]]
+4x 4GB 1333Mhz Reg-ECC HMT151R7BFR4C-H9 
 
 ####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.