To be continued ...
-##GRUB
-###Boot manually
+## GRUB
+### Boot manually
For some setups the default GRUB script does not work. Either try updating the grub.cfg (next section) or boot manually (below).
#Open commandline in GRUB
initrd=/initrd #if (the symlink) not present, choose latest file, press TAB to list
boot
-###Boot automatically
+### Boot automatically
Add the below to the preferred boot option, in grub.cfg, for automatic boot. It is recommended to test any configuration with grubtest.cfg, before changing the main config grub.cfg
menuentry 'Boot to regular encrypted OS [x]' --hotkey='x' {
}
-##Libreboot
+## Libreboot
-###Our external flashing setup
+### Our external flashing setup
BeagleBone Black (BBB), powered by USB. 5A 2A
Tip: Dont power anything from a regular (computer) ATX power supply, it will work but is unreliable and a time waster.
Current setup is to connect to the BBB via Ethernet to a router and thus SSH. Can also connect directly with the SPI interface, see Libreboot flashing guide.
10cm wires
-###General
+### General
For flashing see this [guide](https://libreboot.org/docs/install/x200_external.html) for a general idea, however each system has their own chip configuration which differs a little.
When installing an OS on a Libreboot (/Coreboot) system, use these [guides](https://libreboot.org/docs/gnulinux/).
[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
+### 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
## LASTLY FLASH TO CHIP (here internally)
#sudo ./flashrom/flashrom -p internal -w x200.rom
-###X200
-####Flashing Internally
+### X200
+#### Flashing Internally
To internally flash your ROM use the kernel parameter "iomem=relaxed". Thus, if you boot manually you would enter e g "linux=vmlinuz.. iomem=relaxed".
Get a newer version of flashrom than in Debian repo. In my case the older version did not detect the exact chip on x200, which was fixed by getting most recent version
sudo ./flashrom -p internal -w libreboot.rom #updated image
-###KGPE-D16
-####General
+### KGPE-D16
+#### General
Note these bugs and fixes were tested 2017 with the stable release _Libreboot-20160907_.
* Do NOT use cheap Chinese 12v connectors, they will melt!
* Note: It might be necessary to have a dedicated sound card or 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
4x 4GB 1333Mhz Reg-ECC HMT151R7BFR4C-H9
-####Flashing
+#### 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.
[D16-chip](resources/d16_chip.png)
```
-##Coreboot
+## Coreboot
-##Fria wifi
+## Fria wifi
Note that many systems come with proprietary wifi, e g the X200 laptop or the S3 phone. In these cases another wifi chip is needed, either external (micro/)USB or internal.
For hardware recommendations see [[rekommenderat]].
-##Fria mobilen
+## Fria mobilen
NEVER HAVE GOOGLE SERVICES ON YOUR PRIMARY PHONE, REGARDLESS OF THE FIRMWARE SITUATION. At _most_ have a seperate phone for this.
Sadly phones are proprietary devices that track you.