diff options
Diffstat (limited to 'docs')
-rw-r--r-- | docs/gnulinux/encrypted_debian.md | 10 | ||||
-rw-r--r-- | docs/gnulinux/encrypted_parabola.md | 6 | ||||
-rw-r--r-- | docs/gnulinux/encrypted_trisquel.md | 6 | ||||
-rw-r--r-- | docs/gnulinux/grub_boot_installer.md | 5 | ||||
-rw-r--r-- | docs/gnulinux/grub_cbfs.md | 2 | ||||
-rw-r--r-- | docs/hardware/index.md | 3 | ||||
-rw-r--r-- | docs/hardware/kcma-d8.md | 6 | ||||
-rw-r--r-- | docs/hardware/mac_address.md | 107 | ||||
-rw-r--r-- | docs/index.md | 11 | ||||
-rw-r--r-- | docs/install/r400_external.md | 10 | ||||
-rw-r--r-- | docs/install/t400_external.md | 28 | ||||
-rw-r--r-- | docs/install/t500_external.md | 10 | ||||
-rw-r--r-- | docs/install/x200_external.md | 11 | ||||
-rw-r--r-- | docs/misc/codenames.md | 115 |
14 files changed, 267 insertions, 63 deletions
diff --git a/docs/gnulinux/encrypted_debian.md b/docs/gnulinux/encrypted_debian.md index 83f0dd28..23b4503f 100644 --- a/docs/gnulinux/encrypted_debian.md +++ b/docs/gnulinux/encrypted_debian.md @@ -5,6 +5,16 @@ title: Installing Debian or Devuan GNU+Linux with full disk encryption (includin This guide is written for the Debian distribution, but it should also work for Devuan with the net installer. +Gigabyte GA-G41M-ES2L +===================== + +To boot the Trisquel net installer, make sure to specify fb=false on the linux +kernel parameters in GRUB. This will boot the installer in text mode instead +of using a framebuffer. + +Moving on... +============ + Libreboot on x86 uses the GRUB [payload](http://www.coreboot.org/Payloads#GRUB_2) by default, which means that the GRUB configuration file (where your GRUB menu comes from) diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index 99d5dee7..30b9261d 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -181,8 +181,10 @@ Check to make sure tha the partition was created: # pvdisplay Next, we create the volume group, inside of which the logical volumes will -be created. For this example, we will call this group **matrix**. You can call -yours whatever you would like; just make sure that you remember its name: +be created. In libreboot's case, we will call this group **matrix**. +If you want to have it work via *Load Operating System (incl. fully +encrypted disks) [o]* it needs to be called **matrix** (as it is harcoded +in libreboot's grub.cfg on the flash) # vgcreate matrix /dev/mapper/lvm diff --git a/docs/gnulinux/encrypted_trisquel.md b/docs/gnulinux/encrypted_trisquel.md index 8768c5c7..32ff87f6 100644 --- a/docs/gnulinux/encrypted_trisquel.md +++ b/docs/gnulinux/encrypted_trisquel.md @@ -5,6 +5,12 @@ x-toc enable: true This guide is written for the Trisquel 7.0 (Belenos) GNU+Linux distribution, but it should also work for Trisquel 6.0 (Toutatis). +## Gigabyte GA-G41M-ES2L + +To boot the Trisquel net installer, make sure to specify fb=false on the linux +kernel parameters in GRUB. This will boot the installer in text mode instead +of using a framebuffer. + ## Boot the Installation Media Boot your operating system, with the installation media. If you don't know how to do so, refer to [How to Prepare and Boot a USB Installer in Libreboot Systems](grub_boot_installer.md). diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md index 7d4375e6..48ecaa37 100644 --- a/docs/gnulinux/grub_boot_installer.md +++ b/docs/gnulinux/grub_boot_installer.md @@ -69,13 +69,16 @@ Thirdly, boot the USB and enter these commands in the GRUB terminal grub> boot If you are on a 32-bit system (e.g. some Thinkpad X60's) then you will need to -use these commands instead: +use these commands (this is also true for 32-bit running on 64-bit machines): grub> set root='usb0' grub> linux /install.386/vmlinuz grub> initrd /install.386/initrd.gz grub> boot +NOTE FOR G41M USERS (32 bit, 64 bit): On the *linux* line, specify fb=false to +boot in text mode or the installer won't have a display on your monitor. + ## Booting ISOLINUX Images (Automatic Method) Boot it in GRUB using the `Parse ISOLINUX config (USB)` option. A new menu should appear in GRUB, showing the boot options for that distro; this is a GRUB menu, converted from the usual ISOLINUX menu provided by that distro. diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md index 2e68cb0b..fc46180c 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -262,7 +262,7 @@ Then, add the new one to the ROM: $ ./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t raw -#### Change MAC address in ROM +#### Change MAC address in ROM {#changeMAC} The last step before flashing the new ROM, is to change the MAC address inside it. Every libreboot ROM image contains a generic MAC address; you want to make sure that your ROM image contains yours, so as to not create any problems on your network diff --git a/docs/hardware/index.md b/docs/hardware/index.md index 12580cf8..d939fad6 100644 --- a/docs/hardware/index.md +++ b/docs/hardware/index.md @@ -139,10 +139,11 @@ BIOS](https://en.wikipedia.org/wiki/Video_BIOS)' or 'VBIOS'). To find what LCD panel you have, see: [../misc/\#get\_edid\_panelname](../misc/#get_edid_panelname). -There are 5 known LCD panels for the X60 Tablet: +There are 6 known LCD panels for the X60 Tablet: - *X60T XGA (1024x768):* - BOE-Hydis HV121X03-100 (works) + - Toshiba Matsushita LTD121KC9B (works) - Samsung LTN121XP01 (does not work. blank screen) - BOE-Hydis HT12X21-351 (does not work. blank screen) - *X60T SXGA+ (1400x1050):* diff --git a/docs/hardware/kcma-d8.md b/docs/hardware/kcma-d8.md index f6c6fad7..fb7e6eed 100644 --- a/docs/hardware/kcma-d8.md +++ b/docs/hardware/kcma-d8.md @@ -32,9 +32,9 @@ See <https://raptorengineeringinc.com/coreboot/kcma-d8-status.php>. Form factor {#formfactor} =========== -These boards use the SSI EEB 3.61 form factor; make sure that your case -supports this. This form factor is similar to E-ATX in that the size is -identical, but the position of the screws are different. +This board is ATX form factor. While the [ATX standard, version 2.2](https://web.archive.org/web/20120725150314/http://www.formfactors.org/developer/specs/atx2_2.pdf) +specifies board dimensions 305mm x 244mm, this board measures 305mm x 253mm; +ensure your case supports this extra ~centimeter in width. IPMI iKVM module add-on {#ipmi} ======================= diff --git a/docs/hardware/mac_address.md b/docs/hardware/mac_address.md new file mode 100644 index 00000000..0a0d3621 --- /dev/null +++ b/docs/hardware/mac_address.md @@ -0,0 +1,107 @@ +--- +title: Changing the MAC address +... + +Introduction (GM45+e1000) +========================= + +This section is applicable to all Libreboot-supported laptops with the +mobile 4 series chipset (as shown in `$ lspci`) +that use the e1000 ethernet controller (e.g. T400, X200). +The R500 is an exception to this as it does not use the built-in e1000. + +On all these laptops, the +[MAC address](https://en.wikipedia.org/wiki/MAC_address) +for the built-in gigabit ethernet controller is stored inside the flash chip, +along with Libreboot and other configuration data. Therefore, installing +Libreboot will overwrite it. + +Thus, for these laptops, prebuilt Libreboot already contains a generic +MAC address in the configuration section. This address is `00:f5:f0:40:71:fe` +in builds before 2018-01-16 and `00:4c:69:62:72:65` (see the ascii character +set) afterwards. +Unless you change it, your computer will boot and use it. This can lead +to network problems if you have more than one Libreboot computer on +the same layer2 network (e.g. on the same network switch). The switch +(postman) will simply not know who to deliver to as the MAC (house) addresses +will be the same. + +To prevent these address clashes, you can either modify prebuilt Libreboot +to use an address of your own choosing or you can change the address in your +operating system's boot scripts. + +In either case, it is a good idea to write down the address that your +computer originally had. + +Obtaining the existing MAC address +================================== + +The existing MAC address may be obtained by the following methods: + +1. Run `ip link` or `ifconfig` in a terminal/console/shell; + find your ethernet device (e.g., **enpXXX** or **ethXXX**), + and look for a set of 12 colon-delimited + [hexadecimal digits](https://en.wikipedia.org/wiki/Hexadecimal). + For example: `00:f3:f0:45:91:fe`. + + * `$ ip link` + + `... link/ether ??:??:??:??:??:?? brd ...` + + * Alternatively: + + `$ ifconfig` + + `... ether ??:??:??:??:??:?? txqueuelen ...` + + +2. Otherwise you can read the white label that is often found on the + motherboard under the memory sticks: +  + +3. The MAC address is usually listed on the laptop chassis as well. This one + will be incorrect if the motherboard was changed and the stickers were not + updated. + +Changing the MAC address in the operating system +================================================ + +There are three portable ways of doing so: + +1. Using the new iproute2 package: + + `# ip link set <interface> down` + + `# ip link set dev <interface> address 00:4c:69:62:72:65` + + `# ip link set <interface> up` + + +2. Using the old `ifconfig` command: + + `# ifconfig <interface> hw ether 00:4c:69:62:72:65` + + +3. Using the macchanger package. + +You can use use of these three methods in your operating system's +init scripts or you can use your operating system's own networking +configuration. Refer to your operating system's documentation for +how to do this. + +Changing the MAC address in Libreboot +===================================== + +See [here](../gnulinux/grub_cbfs.md#changeMAC). + + + +Copyright © 2017 Fedja Beader <fedja@protonmail.ch> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org> + +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 +version published by the Free Software Foundation +with no Invariant Sections, no Front Cover Texts, and no Back Cover Texts. +A copy of this license is found in [../fdl-1.3.md](../fdl-1.3.md) diff --git a/docs/index.md b/docs/index.md index 64bad0fe..afbd5e23 100644 --- a/docs/index.md +++ b/docs/index.md @@ -32,6 +32,7 @@ Other information ================= - [Miscellaneous](misc/) +- [List of codenames](misc/codenames.md) About the libreboot project =========================== @@ -74,8 +75,8 @@ The libreboot project has three main goals: and support. Most people will simply give up before attempting to install coreboot. -Libreboot attempts to bridge this divide, making sure that everything from -building to installing coreboot is automated, as much as is feasibly possible. +Libreboot attempts to bridge this divide by providing a build system +automating much of the coreboot image creation and customization. Secondly, the project produces documentation aimed at non-technical users. Thirdly, the project attempts to provide excellent user support via mailing lists and IRC. @@ -86,9 +87,9 @@ the complicated steps that are otherwise required, are instead done for the user in advance. You can download ROM images for your libreboot system and install -them, without having to build anything from source. The build system -is also fully automated, so building from source is easy if you -wanted to do that (for whatever reason). +them without having to build anything from source. If, however, you are +interested in building your own image, the build system makes it relatively +easy to do so. Libreboot is a coreboot distribution, not a coreboot fork --------------------------------------------------------- diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md index 4036c761..8f9dd1ff 100644 --- a/docs/install/r400_external.md +++ b/docs/install/r400_external.md @@ -69,15 +69,7 @@ Use this to find out: MAC address {#macaddress} =========== -On the R400, the MAC address for the onboard gigabit ethernet chipset is -stored inside the flash chip, along with other configuration data. - -Keep a note of the MAC address before disassembly; this is very -important, because you will need to insert this into the libreboot ROM -image before flashing it. It will be written in one of these locations: - -  - +Refer to [mac\_address.md](../hardware/mac_address.md). Initial BBB configuration ========================= diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md index 672ea46e..68bfb4ac 100644 --- a/docs/install/t400_external.md +++ b/docs/install/t400_external.md @@ -70,15 +70,7 @@ Use this to find out: MAC address {#macaddress} =========== -On the T400, the MAC address for the onboard gigabit ethernet chipset is -stored inside the flash chip, along with other configuration data. - -Keep a note of the MAC address before disassembly; this is very -important, because you will need to insert this into the libreboot ROM -image before flashing it. It will be written in one of these locations: - -  - +Refer to [mac\_address.md](../hardware/mac_address.md). Initial BBB configuration ========================= @@ -232,20 +224,14 @@ In this case, the output was: Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" Please specify which chip definition to use with the -c <chipname> option. -How to backup factory.rom (change the -c option as neeed, for your flash +How to backup factory.rom (change the -c option as needed, for your flash chip): - # ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r - -factory.rom + # ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom - # ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r + # ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom -factory1.rom - - # ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r - -factory2.rom + # ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom Note: the `-c` option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in `flashchips.c` have been removed. @@ -269,9 +255,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 -V  diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md index 9e114bca..2a29d8ed 100644 --- a/docs/install/t500_external.md +++ b/docs/install/t500_external.md @@ -73,15 +73,7 @@ Use this to find out: MAC address {#macaddress} =========== -On the T500, the MAC address for the onboard gigabit ethernet chipset is -stored inside the flash chip, along with other configuration data. - -Keep a note of the MAC address before disassembly; this is very -important, because you will need to insert this into the libreboot ROM -image before flashing it. It will be written in one of these locations: - -  - +Refer to [mac\_address.md](../hardware/mac_address.md). Initial BBB configuration ========================= diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md index 83a5c23f..c7330ce9 100644 --- a/docs/install/x200_external.md +++ b/docs/install/x200_external.md @@ -28,16 +28,7 @@ supported; see the [hardware](../hardware/x200.html#x200s) page. MAC address =========== -On the X200/X200S/X200T, the MAC address for the onboard gigabit -ethernet chipset is stored inside the flash chip, along with other -configuration data. - -Keep a note of the MAC address before disassembly; this is very -important, because you will need to insert this into the libreboot ROM -image before flashing it. It will be written in one of these locations: - - - +Refer to [mac\_address.md](../hardware/mac_address.md). Initial BBB configuration ========================= diff --git a/docs/misc/codenames.md b/docs/misc/codenames.md new file mode 100644 index 00000000..adaae6be --- /dev/null +++ b/docs/misc/codenames.md @@ -0,0 +1,115 @@ +--- +title: Product Codenames +... + +Introduction +============ + +This document lists product codenames for some hardware. +Please note that just because a certain device is listed here does NOT mean +that it is supported in Libreboot. For supported devices refer to the +installation documentation. + +### A note on GPUs + +Some laptops come with and without a discrete GPU (dGPU). Whether the +motherboard includes one or not can be determined by (in descending order +of reliability): + +- often thorough disassembly and searching for the actual chip +- looking at white PCB markings near RAM slots / under keyboard + and comparing with some known codenames (if not available FRU ID sticker) + listed below. +- sometimes by looking at heatsink grills: on + discrete GPU laptops these will look orange and on intergrated ones + they will appear silver. + +List of models and codenames +============================ + +### Codenames + +- Asus Chromebook C201PA: speedy\_rk3288, veyron-speedy + +- ThinkPad X60: KS Note +- ThinkPad X60s (slim): KS Note-2 / KS-2 +- ThinkPad X60 Tablet: Dali (Same PCB as KS Note-2, different EC firmware) + +- ThinkPad X200: Mocha-1 +- ThinkPad X200s (slim): Pecan-1 +- ThinkPad X200 Tablet: Caramel-1 + +- ThinkPad R400/T400: Malibu-3 + - with discrete GPU (dGPU), at board revision 0: "MLB3D-0 + - with only integrated GPU (iGPU), at board revision 0: "MLB3I-0" + +- ThinkPad T500/W500: Coronado-5 + - with dGPU (radeon): "COR5D-0" (last number is the board revision) + - with only iGPU: "COR5I-0" + +- ThinkPad T400s (slim): Shinai-MV +- ThinkPad R500: Waikiki-3 + +- R6x/T6x (whole family): Davinci. They don't have codename label in +silkscreen so you need to use FRU label of the board, which is placed +under RAM sticks. +- R60/T60: + - with dGPU (radeon): Magi-0 (last number is the board revision) + - with iGPU: Lisa-0 + +- With ThinkPads on Intel platforms newer than Montevina (Except T410), + the codenames become more consistent. All boards have the following + appended based on the type of graphics they have: + - with dGPU: SWG (SWitchable Graphics) + - with only iGPU: UMA (Unified Memory Access) + +*Note that Intel platforms newer than Montevina are not supported by libreboot +yet!. Currently only Calistoga and Montevina (only when using DDR3) +are the supported platforms.* + +- These are the known model codenames: + - ThinkPad T410: NOZOMI-1 # EXT/INT + - ThinkPad T410s: SHINAI-2 # SWG/UMA + - ThinkPad T420: NOZOMI-3 # SWG/UMA + - ThinkPad T420s: SHINAI-3 # SWG/UMA + - ThinkPad T430: NOZOMI-4 # SWG/UMA + - ThinkPad T430s: SHINAI-4 # SWG/UMA + - ThinkPad T520: KENDO-1 + - ThinkPad W520: KENDO-1 WS + - ThinkPad T520: KENDO-3 + - ThinkPad W520: KENDO-3 WS + - ThinkPad T530: KENDO-4 + - ThinkPad W530: KENDO-4 WS + + +### Miscellaneous +- [Calistoga](https://ark.intel.com/products/codename/5950/Calistoga): +945GM/945PM chipset family name +- Napa: calistoga based platform +- [Cantiga](https://ark.intel.com/products/codename/26552/Cantiga): +GM45/GS45/PM45 chipset family name. + This is the chipset used in T400,X200 and similar. +- Montevina: cantiga based platform. +- PMH: the Power Management Hub is a gate array for managing the power + up/down sequence. It is additionally tasked with extending EC's I/O. + Its later version was called "Thinker-1", and eventually it was merged + with PMIC (Rinkan) as ThinkEngine (Do not confuse it with EC chip which is also + has ThinkEngine logo on ThinkPad boards) +- Kozak, Tsurumai, Rinkan: These are successive versions of power management + ICs for Notebook PCs. Tsurumai chip marking is "TB62501F" and datasheet + of it fully describes its operation. + +See also +======== +- Many more Intel codenames can be found at + [Wikipedia](https://en.wikipedia.org/wiki/List_of_Intel_codenames). +- For ThinkPads see [Documentation/thinkpad/codenames.csv @ Coreboot] +(https://review.coreboot.org/cgit/coreboot.git/tree/Documentation/thinkpad/codenames.csv) + +Copyright © 2018 Fedja Beader <fedja@protonmail.ch> + +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 +version published by the Free Software Foundation +with no Invariant Sections, no Front Cover Texts, and no Back Cover Texts. +A copy of this license is found in [../fdl-1.3.md](../fdl-1.3.md) |