From 4c3d46238022f0c9955ae7e8b10c9f1716dd871a Mon Sep 17 00:00:00 2001 From: Francis Rowe Date: Wed, 04 Feb 2015 04:14:49 -0500 Subject: Documentation: implement theme, drastically improve readability --- (limited to 'docs/hcl') diff --git a/docs/hcl/index.html b/docs/hcl/index.html index 29a587a..6aec1c7 100644 --- a/docs/hcl/index.html +++ b/docs/hcl/index.html @@ -13,156 +13,164 @@ -

Hardware compatibility list

-

- This sections relates to known hardware compatibility in libreboot. -

-

- Or back to main index. -

- - -
- -

List of supported hardware

- -

- Libreboot supports the following machines in this release: -

+
+

Hardware compatibility list

+

+ This sections relates to known hardware compatibility in libreboot. +

+

+ Back to previous index. +

+
-

- 'Supported' means that the build scripts know how to build ROM images for these machines, - and that the machines have been tested (confirmed working). There may be exceptions; - in other words, this is a list of 'officially' supported machines. -

+
-

- It is also possible to build ROM images (from source) for other machines (and virtual machines, e.g. QEMU). -

+

List of supported hardware

-

Back to top of page

+

+ Libreboot supports the following machines in this release: +

+ -
+

+ 'Supported' means that the build scripts know how to build ROM images for these machines, + and that the machines have been tested (confirmed working). There may be exceptions; + in other words, this is a list of 'officially' supported machines. +

-

Recommended wifi chipsets

-

- The following are known to work well: -

- +

+ It is also possible to build ROM images (from source) for other machines (and virtual machines, e.g. QEMU). +

-

Back to top of page

+

Back to top of page

+ +
-
+
-

List of supported ThinkPad X60s

+ +

+ The following are known to work well: +

+ -

- Native gpu initialization ('native graphics') which replaces the proprietary VGA Option ROM - ('Video BIOS' or 'VBIOS'), - all known LCD panels are currently compatible: -

+

Back to top of page

+ +
-

- To find what LCD panel you have, see: ../misc/index.html#get_edid_panelname. -

+
- +

List of supported ThinkPad X60s

-

- You can remove an X61/X61s motherboard from the chassis and install an X60/X60s motherboard in it's place (for flashing libreboot). The chassis is mostly identical - and the motherboards are the same shape/size. -

+

+ Native gpu initialization ('native graphics') which replaces the proprietary VGA Option ROM + ('Video BIOS' or 'VBIOS'), + all known LCD panels are currently compatible: +

-

- The X60 typically comes with an Intel wifi chipset which does not work at all without proprietary firmware, and while Lenovo BIOS is running - the machine will refuse to boot if you replace the card. Fortunately it is very easily replaced; - just remove the card and install another one after libreboot is installed. See #recommended_wifi for replacements. -

+

+ To find what LCD panel you have, see: ../misc/index.html#get_edid_panelname. +

-

Back to top of page.

+ -
+

+ You can remove an X61/X61s motherboard from the chassis and install an X60/X60s motherboard in it's place (for flashing libreboot). The chassis is mostly identical + and the motherboards are the same shape/size. +

-

List of supported ThinkPad X60 Tablets

+

+ The X60 typically comes with an Intel wifi chipset which does not work at all without proprietary firmware, and while Lenovo BIOS is running + the machine will refuse to boot if you replace the card. Fortunately it is very easily replaced; + just remove the card and install another one after libreboot is installed. See #recommended_wifi for replacements. +

-

- Native gpu initialization ('native graphics') which replaces the proprietary VGA Option ROM - ('Video BIOS' or 'VBIOS'). -

+

Back to top of page.

+ +
-

- To find what LCD panel you have, see: ../misc/index.html#get_edid_panelname. -

+
-

- There are 5 known LCD panels for the X60 Tablet: -

- +

List of supported ThinkPad X60 Tablets

-

- Most X60Ts only have digitizer (pen), but some have finger (touch) aswell as pen; finger/multitouch doesn't work, only digitizer (pen) does. -

+

+ Native gpu initialization ('native graphics') which replaces the proprietary VGA Option ROM + ('Video BIOS' or 'VBIOS'). +

-

- You can remove an X61/X61s motherboard from the chassis and install an X60/X60s motherboard in its place (for flashing libreboot). The chassis is mostly identical - and the motherboards are the same shape/size. It is unknown if the same applies between the X60 Tablet and the X61 Tablet. -

+

+ To find what LCD panel you have, see: ../misc/index.html#get_edid_panelname. +

-

- The X60 Tablet typically comes with an Intel wifi chipset which does not work at all without proprietary firmware, and while Lenovo BIOS is running - the machine will refuse to boot if you replace the card. Fortunately it is very easily replaced; - just remove the card and install another one after libreboot is installed. See #recommended_wifi for replacements. -

+

+ There are 5 known LCD panels for the X60 Tablet: +

+ -

- A user with a X60T that has digitizer+finger support, reported that they could get finger input working. They - used linuxwacom at git tag 0.25.99.2 and had the following in their xorg.conf: -

+

+ Most X60Ts only have digitizer (pen), but some have finger (touch) aswell as pen; finger/multitouch doesn't work, only digitizer (pen) does. +

+ +

+ You can remove an X61/X61s motherboard from the chassis and install an X60/X60s motherboard in its place (for flashing libreboot). The chassis is mostly identical + and the motherboards are the same shape/size. It is unknown if the same applies between the X60 Tablet and the X61 Tablet. +

+ +

+ The X60 Tablet typically comes with an Intel wifi chipset which does not work at all without proprietary firmware, and while Lenovo BIOS is running + the machine will refuse to boot if you replace the card. Fortunately it is very easily replaced; + just remove the card and install another one after libreboot is installed. See #recommended_wifi for replacements. +

+ +

+ A user with a X60T that has digitizer+finger support, reported that they could get finger input working. They + used linuxwacom at git tag 0.25.99.2 and had the following in their xorg.conf: + 

 # Now, for some reason (probably a bug in linuxwacom),
@@ -173,33 +181,33 @@
 # tested with linuxwacom git 42a42b2a8636abc9e105559e5dea467163499de7
 
 Section "Monitor"
-    Identifier             "<default monitor>"
-    DisplaySize     245 184
+	 Identifier             "<default monitor>"
+	 DisplaySize     245 184
 EndSection
 
 Section "Screen"
-    Identifier "Default Screen Section"
-    Monitor    "<default monitor<"
+	 Identifier "Default Screen Section"
+	 Monitor    "<default monitor<"
 EndSection
 
 Section "InputDevice"
-    Identifier  "WTouch"
-    Driver      "wacom"
-    Option      "Device" "/dev/ttyS0"
+	 Identifier  "WTouch"
+	 Driver      "wacom"
+	 Option      "Device" "/dev/ttyS0"
 #    Option      "DebugLevel" "12"
-    Option      "BaudRate" "38400"
-    Option      "Type" "touch"
-    Option      "Touch" "on"
-    Option      "Gesture" "on"
-    Option      "ForceDevice" "ISDV4"
+	 Option      "BaudRate" "38400"
+	 Option      "Type" "touch"
+	 Option      "Touch" "on"
+	 Option      "Gesture" "on"
+	 Option      "ForceDevice" "ISDV4"
 #    Option      "KeepShape" "on"
-    Option      "Mode" "Absolute"
-    Option      "RawSample" "2"
+	 Option      "Mode" "Absolute"
+	 Option      "RawSample" "2"
 #    Option      "TPCButton" "off"
-    Option      "TopX" "17"
-    Option      "TopY" "53"
-    Option      "BottomX" "961"
-    Option      "BottomY" "985"
+	 Option      "TopX" "17"
+	 Option      "TopY" "53"
+	 Option      "BottomX" "961"
+	 Option      "BottomY" "985"
 EndSection
 
 Section "ServerLayout"
@@ -210,310 +218,332 @@ EndSection
-

Back to top of page.

- -
- -

Supported T60 list

- -

- Native gpu initialization ('native graphics') which replaces the proprietary VGA Option ROM - ('Video BIOS' or 'VBIOS'). -

+

Back to top of page.

+ +
-

- To find what LCD panel you have, see: ../misc/index.html#get_edid_panelname. -

+
-

- - Some T60s have ATI GPUs, and all T60P laptops have ATI GPUs These are incompatible! See #t60_ati_intel for how to remedy this. - -

+

Supported T60 list

-

- How to dump the EDID:
- -

+

+ Native gpu initialization ('native graphics') which replaces the proprietary VGA Option ROM + ('Video BIOS' or 'VBIOS'). +

-

- Tested LCD panels: working(compatible) -

- +

+ To find what LCD panel you have, see: ../misc/index.html#get_edid_panelname. +

-
+

+ + Some T60s have ATI GPUs, and all T60P laptops have ATI GPUs These are incompatible! See #t60_ati_intel for how to remedy this. + +

- Tested LCD panels: not working yet (incompatible; see ../future/index.html#lcd_i945_incompatibility) + How to dump the EDID:
+

-
    -
  • Samsung LTN141XA-L01 (14.1" 1024x768)
    • -
  • LG-Philips LP150X09 (15.1" 1024x768)
    • -
  • Samsung LTN150XG (15.1" 1024x768) - EDID dump (taken using sudo i2cdump -y 5 0x50)
    • -
  • LG-Philips LP150E06-A5K4 (15.1" 1400x1050) (also, not an official T60 screen)
    • -
  • Samsung LTN154X3-L0A (15.4" 1280x800)
    • -
  • IDtech IAQX10N (15.1" 2048x1536) (no display in GRUB, display in GNU/Linux is temperamental) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
    • -

- The following LCD panels are UNTESTED. If you have one of these panels - then please submit a report!: + Tested LCD panels: working(compatible)

    -
  • CMO(IDtech?) N141XC (14.1" 1024x768)
    • -
  • BOE-Hydis HT14X14 (14.1" 1024x768)
    • -
  • TMD-Toshiba LTD141ECMB (14.1" 1024x768)
    • -
  • Boe-Hydis HT14P12 (14.1" 1400x1050) (FRU P/N 41W1478 recommended for the inverter board)
    • -
  • CMO (IDtech?) 13N7068 (15.1" 1024x768)
    • -
  • CMO (IDtech?) 13N7069 (15.1" 1024x768)
    • -
  • BOE-Hydis HV150P01-100 (15.1" 1400x1050) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
    • -
  • IDtech N150U3-L01 (15.1" 1600x1200) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
    • -
  • BOE-Hydis HV150UX1-102 (15.1" 1600x1200) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
    • -
  • IDtech IAQX10S (15.1" 2048x1536) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
    • -
  • Samsung LTN154P2-L05 (42X4641 42T0329) (15.4" 1680x1050)
    • -
  • LG-Philips LP154W02-TL10 (13N7020 42T0423) (15.4" 1680x1050)
    • -
  • LG-Philips LP154WU1-TLB1 (42T0361) (15.4" 1920x1200) (for T61p but it might work in T60. Unknown!)
    • -
  • Samsung LTN154U2-L05 (42T0408 42T0574) (15.4" 1920x1200) (for T61p but it might work in T60. Unknown!)
    • +
  • TMD-Toshiba LTD141EN9B (14.1" 1400x1050) (FRU P/N 41W1478 recommended for the inverter board)
    • +
  • Samsung LTN141P4-L02 (14.1" 1400x1050) (FRU P/N 41W1478 recommended for the inverter board)
    • +
  • LG-Philips LP150E05-A2K1 (15.1" 1400x1050) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
    • +
  • Samsung LTN150P4-L01 (15.1" 1400x1050) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board) (not a T60 screen afaik, but it works)
    • +
  • BOE-Hydis HV150UX1-100 (15.1" 1600x1200) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
-

- It is unknown whether the 1680x1050 (15.4") and 1920x1200 (15.4") panels use a different inverter board than the 1280x800 panels. -

+
-

- The T60 typically comes with an Intel wifi chipset which does not work at all without proprietary firmware, and while Lenovo BIOS is running - the machine will refuse to boot if you replace the card. Fortunately it is very easily replaced; - just remove the card and install another one after libreboot is installed. See #recommended_wifi for replacements. -

+

+ Tested LCD panels: not working yet (incompatible; see ../future/index.html#lcd_i945_incompatibility) +

+
    +
  • Samsung LTN141XA-L01 (14.1" 1024x768)
    • +
  • LG-Philips LP150X09 (15.1" 1024x768)
    • +
  • Samsung LTN150XG (15.1" 1024x768) - EDID dump (taken using sudo i2cdump -y 5 0x50)
    • +
  • LG-Philips LP150E06-A5K4 (15.1" 1400x1050) (also, not an official T60 screen)
    • +
  • Samsung LTN154X3-L0A (15.4" 1280x800)
    • +
  • IDtech IAQX10N (15.1" 2048x1536) (no display in GRUB, display in GNU/Linux is temperamental) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
    • +
-
+
+ +
-

Back to top of page.

+

+ The following LCD panels are UNTESTED. If you have one of these panels + then please submit a report!: +

+
    +
  • CMO(IDtech?) N141XC (14.1" 1024x768)
    • +
  • BOE-Hydis HT14X14 (14.1" 1024x768)
    • +
  • TMD-Toshiba LTD141ECMB (14.1" 1024x768)
    • +
  • Boe-Hydis HT14P12 (14.1" 1400x1050) (FRU P/N 41W1478 recommended for the inverter board)
    • +
  • CMO (IDtech?) 13N7068 (15.1" 1024x768)
    • +
  • CMO (IDtech?) 13N7069 (15.1" 1024x768)
    • +
  • BOE-Hydis HV150P01-100 (15.1" 1400x1050) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
    • +
  • IDtech N150U3-L01 (15.1" 1600x1200) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
    • +
  • BOE-Hydis HV150UX1-102 (15.1" 1600x1200) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
    • +
  • IDtech IAQX10S (15.1" 2048x1536) (P/N 42T0078 FRU 42T0079 or P/N 41W1338 recommended for the inverter board)
    • +
  • Samsung LTN154P2-L05 (42X4641 42T0329) (15.4" 1680x1050)
    • +
  • LG-Philips LP154W02-TL10 (13N7020 42T0423) (15.4" 1680x1050)
    • +
  • LG-Philips LP154WU1-TLB1 (42T0361) (15.4" 1920x1200) (for T61p but it might work in T60. Unknown!)
    • +
  • Samsung LTN154U2-L05 (42T0408 42T0574) (15.4" 1920x1200) (for T61p but it might work in T60. Unknown!)
    • +
-
+

+ It is unknown whether the 1680x1050 (15.4") and 1920x1200 (15.4") panels use a different inverter board than the 1280x800 panels. +

-

ThinkPad T60 (ATI GPU) and ThinkPad T60 (Intel GPU) differences.

+

+ The T60 typically comes with an Intel wifi chipset which does not work at all without proprietary firmware, and while Lenovo BIOS is running + the machine will refuse to boot if you replace the card. Fortunately it is very easily replaced; + just remove the card and install another one after libreboot is installed. See #recommended_wifi for replacements. +

-

- If your T60 is a 14.1" or 15.1" model with an ATI GPU, it won't work with libreboot by default but - you can replace the motherboard with another T60 motherboard that has an Intel GPU, and then libreboot should work. -

+
-

- As far as I know, 14.1" (Intel GPU) and 15.1" (Intel GPU) T60 motherboards are the same, where - 'spacers' are used on the 15.1" T60. In any case, it makes sense to find one that is guaranteed to fit in your chassis. -

+

Back to top of page.

+ +
-

- There is also a 15.4" T60 with Intel GPU. -

+
-

- Note: the T60p laptops all have ATI graphics. - The T60p laptops cannot be used with libreboot under any circumstances. -

+

ThinkPad T60 (ATI GPU) and ThinkPad T60 (Intel GPU) differences.

-

- The following T60 motherboard (see area highlighted in white) shows an empty space where the ATI GPU would be (this particular motherboard has an Intel GPU):
- -

+

+ If your T60 is a 14.1" or 15.1" model with an ATI GPU, it won't work with libreboot by default but + you can replace the motherboard with another T60 motherboard that has an Intel GPU, and then libreboot should work. +

-

- The reason that the ATI GPU on T60 is unsupported is due to the VBIOS (Video BIOS) which is non-free. - The VBIOS for the Intel GPU on X60/T60 has been reverse engineered, and replaced with Free Software and - so will work in libreboot. -

+

+ As far as I know, 14.1" (Intel GPU) and 15.1" (Intel GPU) T60 motherboards are the same, where + 'spacers' are used on the 15.1" T60. In any case, it makes sense to find one that is guaranteed to fit in your chassis. +

-

- The 'Video BIOS' is what initializes graphics. -

+

+ There is also a 15.4" T60 with Intel GPU. +

-

- See: https://en.wikipedia.org/wiki/Video_BIOS.
- In fact, lack of free VBIOS in general is a big problem in coreboot, and is one reason (among others) why many ports for coreboot are - unsuitable for libreboot's purpose. -

+

+ Note: the T60p laptops all have ATI graphics. + The T60p laptops cannot be used with libreboot under any circumstances. +

-

- Theoretically, the ThinkPad T60 with ATI GPU can work with libreboot and have ROM images compiled for it, however - in practise it would not be usable as a laptop because there would be no visual display at all. That being said, - such a configuration is acceptable for use in a 'headless' server setup (with serial and/or ssh console as the display). -

+

+ The following T60 motherboard (see area highlighted in white) shows an empty space where the ATI GPU would be (this particular motherboard has an Intel GPU):

+ +

-

Back to top of page.

+

+ The reason that the ATI GPU on T60 is unsupported is due to the VBIOS (Video BIOS) which is non-free. + The VBIOS for the Intel GPU on X60/T60 has been reverse engineered, and replaced with Free Software and + so will work in libreboot. +

-
+

+ The 'Video BIOS' is what initializes graphics. +

-

Information about the macbook1,1

+

+ See: https://en.wikipedia.org/wiki/Video_BIOS.
+ In fact, lack of free VBIOS in general is a big problem in coreboot, and is one reason (among others) why many ports for coreboot are + unsuitable for libreboot's purpose. +

-

- There is an Apple laptop called the macbook1,1 from 2006 which uses the same i945 chipset as the ThinkPad X60/T60. - A developer ported the MacBook2,1 to coreboot, the ROM images also work on the macbook1,1. -

+

+ Theoretically, the ThinkPad T60 with ATI GPU can work with libreboot and have ROM images compiled for it, however + in practise it would not be usable as a laptop because there would be no visual display at all. That being said, + such a configuration is acceptable for use in a 'headless' server setup (with serial and/or ssh console as the display). +

-

- You can refer to #macbook21 for most of this. Macbook2,1 laptops come with Core 2 Duo processors - which support 64-bit operating systems (and 32-bit). The MacBook1,1 uses Core Duo processors (supports 32-bit OS but not 64-bit), - and it is believed that this is the only difference. -

+

Back to top of page.

+ +
-

- It is believed that all models are compatible, listed here: -

- +
+ +

Information about the macbook1,1

-

- Compatible models -

- Specifically (Order No. / Model No. / CPU): + There is an Apple laptop called the macbook1,1 from 2006 which uses the same i945 chipset as the ThinkPad X60/T60. + A developer ported the MacBook2,1 to coreboot, the ROM images also work on the macbook1,1. +

+ +

+ You can refer to #macbook21 for most of this. Macbook2,1 laptops come with Core 2 Duo processors + which support 64-bit operating systems (and 32-bit). The MacBook1,1 uses Core Duo processors (supports 32-bit OS but not 64-bit), + and it is believed that this is the only difference. +

+ +

+ It is believed that all models are compatible, listed here:

+ +
+

+ Compatible models +

+

+ Specifically (Order No. / Model No. / CPU): +

+
    +
  • MA255LL/A / A1181 (EMC 2092) / Core Duo T2500 (tested - working)
    • +
  • MA254LL/A / A1181 (EMC 2092) / Core Duo T2400 (untested)
    • +
  • MA472LL/A / A1181 (EMC 2092) / Core Duo T2500 (untested)
    • +
+
-

- Also of interest: ../git/index.html#config_macbook21. -

- -

- Unbricking: this page shows disassembly guides and mono's page (see #macbook21) - shows the location of the SPI flash chip on the motherboard. How to remove the motherboard. -

+

+ Also of interest: ../git/index.html#config_macbook21. +

-

- No method is yet known for flashing in GNU/Linux while the Apple firmware is running. You will need to disassemble the machine and flash externally. - Reading from flash seems to work. For external flashing, refer to ../install/bbb_setup.html. -

+

+ Unbricking: this page shows disassembly guides and mono's page (see #macbook21) + shows the location of the SPI flash chip on the motherboard. How to remove the motherboard. +

-

Back to top of page.

+

+ No method is yet known for flashing in GNU/Linux while the Apple firmware is running. You will need to disassemble the machine and flash externally. + Reading from flash seems to work. For external flashing, refer to ../install/bbb_setup.html. +

-
+

Back to top of page.

+ +
-

Information about the macbook2,1

+
-

- There is an Apple laptop called the macbook2,1 from late 2006 or early 2007 that uses the same i945 chipset - as the ThinkPad X60 and ThinkPad T60. A developer ported coreboot to his macbook2,1, and now libreboot can run on it. -

-

- Mono Moosbart is the person who wrote the port for macbook2,1. Referenced below are copies (up to date at the time of writing, 20140630) - of the pages he wrote when porting coreboot to the macbook2,1. They are included here in case the main site goes down for - whatever reason, since they include a lot of useful information. -

-

- Backups created using wget:
- $ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/
- $ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/coreboot/
- Use -e robots=off if using this trick for other sites and the site restricts using robots.txt -

+

Information about the macbook2,1

-

- Links to wget backups (and the backups themselves) of Mono's pages (see above) removed temporarily. Mono has given me permission to distribute them, but I need to ask - him to tell me what license these works fall under first. Otherwise, the above URLs should be fine. NOTE TO SELF: REMOVE THIS WHEN DONE -

+

+ There is an Apple laptop called the macbook2,1 from late 2006 or early 2007 that uses the same i945 chipset + as the ThinkPad X60 and ThinkPad T60. A developer ported coreboot to his macbook2,1, and now libreboot can run on it. +

+

+ Mono Moosbart is the person who wrote the port for macbook2,1. Referenced below are copies (up to date at the time of writing, 20140630) + of the pages he wrote when porting coreboot to the macbook2,1. They are included here in case the main site goes down for + whatever reason, since they include a lot of useful information. +

+

+ Backups created using wget:
+ $ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/
+ $ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/coreboot/
+ Use -e robots=off if using this trick for other sites and the site restricts using robots.txt +

-

- Installing GNU/Linux distributions (on Apple EFI firmware) -

-

- How to boot an ISO: burn it to a CD (like you would normally) and hold down the Alt/Control key while booting. - The bootloader will detect the GNU/Linux CD as 'Windows' (because Apple doesn't think GNU/Linux exists). Install it like you normally would. - When you boot up again, hold Alt/Control once more. The installation (on the HDD) will once again be seen as 'Windows'. (it's not actually Windows, - but Apple likes to think that Apple and Microsoft are all that exist.) - Now to install libreboot, follow ../install/index.html#flashrom_macbook21. + Links to wget backups (and the backups themselves) of Mono's pages (see above) removed temporarily. Mono has given me permission to distribute them, but I need to ask + him to tell me what license these works fall under first. Otherwise, the above URLs should be fine. NOTE TO SELF: REMOVE THIS WHEN DONE

-

- Information about coreboot -

- +
+

+ Installing GNU/Linux distributions (on Apple EFI firmware) +

+ +

+ How to boot an ISO: burn it to a CD (like you would normally) and hold down the Alt/Control key while booting. + The bootloader will detect the GNU/Linux CD as 'Windows' (because Apple doesn't think GNU/Linux exists). Install it like you normally would. + When you boot up again, hold Alt/Control once more. The installation (on the HDD) will once again be seen as 'Windows'. (it's not actually Windows, + but Apple likes to think that Apple and Microsoft are all that exist.) + Now to install libreboot, follow ../install/index.html#flashrom_macbook21. +

+
+ +
+

+ Information about coreboot +

+ +
-

- coreboot wiki page -

- +
+

+ coreboot wiki page +

+ +
+ +
+

+ Compatible models +

+

+ It is believed that all models are compatible, listed here: +

+ +

+ Specifically (Order No. / Model No. / CPU): +

+
    +
  • MA699LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T5600 (tested - working)
    • +
  • MA701LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 (tested - working)
    • +
  • MB061LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7200 (untested)
    • +
  • MA700LL/A / A1181 (EMC 2121) / Intel Core 2 Duo T7200 (tested - working)
    • +
  • MB063LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 (untested)
    • +
  • MB062LL/A / A1181 (EMC 2139) / Intel Core 2 Duo T7400 (tested - working)
    • +
+
-

- Compatible models -

- It is believed that all models are compatible, listed here: + Also of interest: ../git/index.html#config_macbook21.

- +

- Specifically (Order No. / Model No. / CPU): + Unbricking: this page shows disassembly guides and mono's page (see above) + shows the location of the SPI flash chip on the motherboard. How to remove the motherboard.

- - -

- Also of interest: ../git/index.html#config_macbook21. -

- -

- Unbricking: this page shows disassembly guides and mono's page (see above) - shows the location of the SPI flash chip on the motherboard. How to remove the motherboard. -

-

- For external flashing, refer to ../install/bbb_setup.html. -

+

+ For external flashing, refer to ../install/bbb_setup.html. +

-

- You need to replace OS X with GNU/Linux before flashing libreboot. (OSX won't run at all in libreboot). -

+

+ You need to replace OS X with GNU/Linux before flashing libreboot. (OSX won't run at all in libreboot). +

-

- There are some issues with this machine (compared to other computers that libreboot supports): -

+

+ There are some issues with this machine (compared to other computers that libreboot supports): +

-

- This is an apple laptop, so it comes with OS X: it has an Apple keyboard, which means that certain keys you expect are missing: - insert, del, home, end, pgup, pgdown. There is also one mouse button only. Battery life is poor compared to X60/T60 (for now). - It also has other issues: for example, the Apple logo on the back is a hole, exposing the backlight, which means that it glows. You should cover it up. -

+

+ This is an apple laptop, so it comes with OS X: it has an Apple keyboard, which means that certain keys you expect are missing: + insert, del, home, end, pgup, pgdown. There is also one mouse button only. Battery life is poor compared to X60/T60 (for now). + It also has other issues: for example, the Apple logo on the back is a hole, exposing the backlight, which means that it glows. You should cover it up. +

-

- The machine does get a bit hotter compared to when running the original firmware. It is certainly hotter - than an X60/T60. The heat issues have been partially fixed by the following patch (now merged in libreboot): - http://review.coreboot.org/#/c/7923/. -

+

+ The machine does get a bit hotter compared to when running the original firmware. It is certainly hotter + than an X60/T60. The heat issues have been partially fixed by the following patch (now merged in libreboot): + http://review.coreboot.org/#/c/7923/. +

-

- - The MacBook2,1 comes with a webcam, which does not work without proprietary software. Also, webcams are a security risk; cover it up! Or remove it. - -

+

+ + The MacBook2,1 comes with a webcam, which does not work without proprietary software. Also, webcams are a security risk; cover it up! Or remove it. + +

-

- A user reported that they could get better response from the touchpad with the following in their xorg.conf: -

+

+ A user reported that they could get better response from the touchpad with the following in their xorg.conf: + 

 Section "InputClass"
@@ -558,21 +588,25 @@ Section "InputClass"
 EndSection
-

Back to top of page.

+

Back to top of page.

+ +
-
+
-

- Copyright © 2014, 2015 Francis Rowe <info@gluglug.org.uk>
- This document is released under the Creative Commons Attribution-ShareAlike 4.0 International Public License and all future versions. - A copy of the license can be found at ../license.txt. -

+

+ Copyright © 2014, 2015 Francis Rowe <info@gluglug.org.uk>
+ This document is released under the Creative Commons Attribution-ShareAlike 4.0 International Public License and all future versions. + A copy of the license can be found at ../license.txt. +

-

- This document is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See ../../license.txt for more information. -

+

+ This document is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See ../license.txt for more information. +

+ +
diff --git a/docs/hcl/x200.html b/docs/hcl/x200.html index 3aa1963..0435efc 100644 --- a/docs/hcl/x200.html +++ b/docs/hcl/x200.html @@ -13,38 +13,39 @@ -

ThinkPad X200

-

- Or back to main index. -

- -

- It is believed that all X200 laptops are compatible. X200S and X200 Tablet will - also work, depending on the configuration. -

-

- It *might* be possible to put an X200 motherboard in an X201 chassis, though this is currently untested - by the libreboot project. The same may also apply between X200S and X201S; again, this is untested. - It's most likely true. -

- -

- There are two possible flash chip sizes for the X200: 4MiB (32Mbit) or 8MiB (64Mbit). - This can be identified by the type of flash chip below the palmrest: 4MiB is SOIC-8, 8MiB - is SOIC-16. -

- -

- The X200 laptops come with the ME (and sometimes AMT in addition) before flashing libreboot. Libreboot disables and removes it - by using a modified descriptor: see x200_remove_me.html (contains notes, plus - instructions) -

- -

- Flashing instructions can be found at ../install/index.html#flashrom -

+
+

ThinkPad X200

+ +

+ It is believed that all X200 laptops are compatible. X200S and X200 Tablet will + also work, depending on the configuration. +

+

+ It *might* be possible to put an X200 motherboard in an X201 chassis, though this is currently untested + by the libreboot project. The same may also apply between X200S and X201S; again, this is untested. + It's most likely true. +

+ +

+ There are two possible flash chip sizes for the X200: 4MiB (32Mbit) or 8MiB (64Mbit). + This can be identified by the type of flash chip below the palmrest: 4MiB is SOIC-8, 8MiB + is SOIC-16. +

+ +

+ The X200 laptops come with the ME (and sometimes AMT in addition) before flashing libreboot. Libreboot disables and removes it + by using a modified descriptor: see x200_remove_me.html (contains notes, plus + instructions) +

-
+

+ Flashing instructions can be found at ../install/index.html#flashrom +

+ +

+ Back to previous index. +

+
@@ -68,22 +69,22 @@ non-descriptor mode would wipe it out).

-

Hardware virtualization (vt-x)

-

- The X200, when run without CPU microcode updates in coreboot, currently kernel panics - if running QEMU with vt-x enabled on 2 cores for the guest. With a single core enabled - for the guest, the guest panics (but the host is fine). Working around this in QEMU - might be possible; if not, software virtualization should work fine (it's just slower). -

-

- The following errata datasheet from Intel might help with investigation: - http://download.intel.com/design/mobile/specupdt/320121.pdf -

+
+

Hardware virtualization (vt-x)

+

+ The X200, when run without CPU microcode updates in coreboot, currently kernel panics + if running QEMU with vt-x enabled on 2 cores for the guest. With a single core enabled + for the guest, the guest panics (but the host is fine). Working around this in QEMU + might be possible; if not, software virtualization should work fine (it's just slower). +

+

+ The following errata datasheet from Intel might help with investigation: + http://download.intel.com/design/mobile/specupdt/320121.pdf +

+
-
-

X200S and X200 Tablet.

@@ -140,140 +141,146 @@ src or git).

-

Proper GS45 raminit

-

- A new northbridge gs45 should be added to coreboot, based on gm45, - and a new port x200st (X200S and X200T) should be added based on - the x200 port. -

-

- This port would have proper raminit. Alternatively, gs45 (if - raminit is taken to be the only issue with it) can be part of - gm45 northbridge support (and X200S/Tablet being part of the X200 - port) with conditional checks in the raminit that make raminit - work differently (as required) for GS45. nico_h and pgeorgi/patrickg - in the coreboot IRC channel should know more about raminit on gm45 - and likely gs45. -

-

- pgeorgi recommends to run SerialICE on the factory BIOS (for X200S), - comparing it with X200 (factory BIOS) and X200 (gm45 raminit code - in coreboot), to see what the differences are. Then tweak raminit - code based on that. -

+
+

Proper GS45 raminit

+

+ A new northbridge gs45 should be added to coreboot, based on gm45, + and a new port x200st (X200S and X200T) should be added based on + the x200 port. +

+

+ This port would have proper raminit. Alternatively, gs45 (if + raminit is taken to be the only issue with it) can be part of + gm45 northbridge support (and X200S/Tablet being part of the X200 + port) with conditional checks in the raminit that make raminit + work differently (as required) for GS45. nico_h and pgeorgi/patrickg + in the coreboot IRC channel should know more about raminit on gm45 + and likely gs45. +

+

+ pgeorgi recommends to run SerialICE on the factory BIOS (for X200S), + comparing it with X200 (factory BIOS) and X200 (gm45 raminit code + in coreboot), to see what the differences are. Then tweak raminit + code based on that. +

+
+ +
-
- -

LCD compatibility list

-

- Unless otherwise noted (italic styling, underlined), these are CCFL 1280x800 screens with TN panels inside. - Please do advise if you spot mistakes here. -

-

- Use the instructions at ../misc/index.html#get_edid_panelname - to get the name of your panel, then check it against the list below. If your panel is untested, then by all means - try it! (and get in touch with the libreboot project to advise whether or not it worked). -

-

- AUO = AU Optronics. List of panels below based on - http://www.thinkwiki.org/wiki/TFT_display -

-

- Tested LCD panels (confirmed working): -

- -

- Untested LCD panels (status unknown): -

- -

- Back to top of page. -

- -

- AFFS/IPS panels -

-

X200

-

- Adapted from https://github.com/bibanon/Coreboot-ThinkPads/wiki/ThinkPad-X200 -

-

- Look at wikipedia for difference between TN and IPS panels. IPS have much better colour/contrast than - a regular TN, and will typically have good viewing angles. -

-

- These seem to be from the X200 tablet. You need to find one without the glass touchscreen protection on it - (might be able to remove it, though). It also must not have a digitizer on it (again, might be possible to - just simply remove the digitizer). -

- -

- If your X200 has an LED backlit panel in it, then you also need to get an inverter and harness cable - that is compatible with the CCFL panels. To see which panel type you have, see - #led_howtotell. If you need the inverter/cable, here are part numbers: - 44C9909 for CCFL LVDS cable with bluetooth and camera connections, and 42W8009 or 42W8010 for the - inverter. -

-

- There are glossy and matte versions of these. Matte means anti-glare, which is what you want (in this authors opinion). -

-

- Refer to the HMM (hardware maintenance manual) for how to replace the screen. -

-

Sources:

- -

X200S

-

- http://forum.thinkpads.com/viewtopic.php?p=618928#p618928 - explains that the X200S screens/assemblies are thinner. You need to replace the whole lid with one from a normal X200/X201. -

+

LCD compatibility list

+

+ Unless otherwise noted (italic styling, underlined), these are CCFL 1280x800 screens with TN panels inside. + Please do advise if you spot mistakes here. +

+

+ Use the instructions at ../misc/index.html#get_edid_panelname + to get the name of your panel, then check it against the list below. If your panel is untested, then by all means + try it! (and get in touch with the libreboot project to advise whether or not it worked). +

+

+ AUO = AU Optronics. List of panels below based on + http://www.thinkwiki.org/wiki/TFT_display +

+

+ Tested LCD panels (confirmed working): +

+ +

+ Untested LCD panels (status unknown): +

+ +

+ Back to top of page. +

+
+

+ AFFS/IPS panels +

+

X200

+

+ Adapted from https://github.com/bibanon/Coreboot-ThinkPads/wiki/ThinkPad-X200 +

+

+ Look at wikipedia for difference between TN and IPS panels. IPS have much better colour/contrast than + a regular TN, and will typically have good viewing angles. +

+

+ These seem to be from the X200 tablet. You need to find one without the glass touchscreen protection on it + (might be able to remove it, though). It also must not have a digitizer on it (again, might be possible to + just simply remove the digitizer). +

+
    +
  • BOE-Hydis HV121WX4-120, HV121WX4-110 or HV121WX4-100 - cheap-ish, might be hard to find
    • +
  • Samsung LTN121AP02-001 - common to find, cheap
    • +
+

+ If your X200 has an LED backlit panel in it, then you also need to get an inverter and harness cable + that is compatible with the CCFL panels. To see which panel type you have, see + #led_howtotell. If you need the inverter/cable, here are part numbers: + 44C9909 for CCFL LVDS cable with bluetooth and camera connections, and 42W8009 or 42W8010 for the + inverter. +

+

+ There are glossy and matte versions of these. Matte means anti-glare, which is what you want (in this authors opinion). +

+

+ Refer to the HMM (hardware maintenance manual) for how to replace the screen. +

+

Sources:

+ +
+
+

X200S

+

+ http://forum.thinkpads.com/viewtopic.php?p=618928#p618928 + explains that the X200S screens/assemblies are thinner. You need to replace the whole lid with one from a normal X200/X201. +

+
+

Back to top of page.

- -
- -

How to tell if it has an LED or CCFL?

- -

- Some X200s have a CCFL backlight and some have an LED backlight, in their LCD panel. This - also means that the inverters will vary, so you must be careful if ever replacing either - the panel and/or inverter. (a CCFL inverter is high-voltage and will destroy an LED backlit panel). -

-

- CCFLs contain mercury. An X200 with a CCFL backlight will (unless it has been changed to an LED, - with the correct inverter. Check with your supplier!) the following: "This product - contains Lithium Ion Battery, Lithium Battery and a lamp which contains mercury; dispose according to - local, state or federal laws" (one with an LED backlit panel will say something different). -

-

- Back to top of page. -

+ +
-
+
+

How to tell if it has an LED or CCFL?

+ +

+ Some X200s have a CCFL backlight and some have an LED backlight, in their LCD panel. This + also means that the inverters will vary, so you must be careful if ever replacing either + the panel and/or inverter. (a CCFL inverter is high-voltage and will destroy an LED backlit panel). +

+

+ CCFLs contain mercury. An X200 with a CCFL backlight will (unless it has been changed to an LED, + with the correct inverter. Check with your supplier!) the following: "This product + contains Lithium Ion Battery, Lithium Battery and a lamp which contains mercury; dispose according to + local, state or federal laws" (one with an LED backlit panel will say something different). +

+

+ Back to top of page. +

+
@@ -299,8 +306,6 @@
-
-

Unsorted notes

@@ -315,19 +320,21 @@
-
+
-

- Copyright © 2014 Francis Rowe <info@gluglug.org.uk>
- This document is released under the Creative Commons Attribution-ShareAlike 4.0 International Public License and all future versions. - A copy of the license can be found at ../license.txt. -

+

+ Copyright © 2014, 2015 Francis Rowe <info@gluglug.org.uk>
+ This document is released under the Creative Commons Attribution-ShareAlike 4.0 International Public License and all future versions. + A copy of the license can be found at ../license.txt. +

-

- This document is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See ../../license.txt for more information. -

+

+ This document is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See ../license.txt for more information. +

+ +
diff --git a/docs/hcl/x200_remove_me.html b/docs/hcl/x200_remove_me.html index 48468c6..ae0a83f 100644 --- a/docs/hcl/x200_remove_me.html +++ b/docs/hcl/x200_remove_me.html @@ -13,181 +13,189 @@ -

ThinkPad X200: remove the ME (manageability engine)

-

- This sections relates to disabling and removing the ME (Intel Management Engine) - on the ThinkPad X200. -

-

- The ME is a blob that typically must be left inside the flash chip (in the ME region, as outlined - by the default descriptor). On the X200, it is possible to remove it without any ill effects. All - other parts of coreboot on the X200 can be blob-free, so removing the ME was the last obstacle to - get X200 support in libreboot (the machine can also work without the microcode blobs). -

-

- The ME is removed and disabled in libreboot by modifying the descriptor. More info about - this can be found in the ich9deblob/ich9gen source code in resources/utilities/ich9deblob/ - in libreboot, or more generally on this page. -

-

- Or back to main X200 compatibility page (x200.html). -

+
+ +

ThinkPad X200: remove the ME (manageability engine)

+

+ This sections relates to disabling and removing the ME (Intel Management Engine) + on the ThinkPad X200. +

+

+ The ME is a blob that typically must be left inside the flash chip (in the ME region, as outlined + by the default descriptor). On the X200, it is possible to remove it without any ill effects. All + other parts of coreboot on the X200 can be blob-free, so removing the ME was the last obstacle to + get X200 support in libreboot (the machine can also work without the microcode blobs). +

+

+ The ME is removed and disabled in libreboot by modifying the descriptor. More info about + this can be found in the ich9deblob/ich9gen source code in resources/utilities/ich9deblob/ + in libreboot, or more generally on this page. +

+

+ Back to main X200 compatibility page (x200.html). +

+ +
-
+
-

ICH9 gen utility

- -

- This is no longer strictly necessary. Libreboot ROM images for X200 now - contain the 12KiB descriptor+gbe generated from ich9gen, by default. -

- -

- It is no longer necessary to use ich9deblob to generate - a deblobbed descriptor+gbe image for the X200. ich9gen is a small utility within - ich9deblob that can generate them from scratch, without a factory.bin dump. -

- -

- Run:
- $ ./ich9gen -

- -

- It is also possible to generate a descriptor+gbe image with your own MAC address - inside (with the Gbe checksum updated to match). Run:
- $ ./ich9gen --macaddress XX:XX:XX:XX:XX:XX
- (replace the XX chars with the hexadecimal chars in the MAC address that you want) -

- -

- You can find out your MAC address from ip addr or ifconfig in GNU/Linux. - Alternatively, if you are running libreboot already (with the correct MAC address in your - ROM), dump it (flashrom -r) and read the first 6 bytes from position 0x1000 (or 0x2000) in a hex editor - (or, rename it to factory.rom and run it in ich9deblob: in the newly created mkgbe.c - will be the individual bytes of your MAC address). If you are currently running the stock firmware - and haven't installed libreboot yet, you can also run that through ich9deblob to get the mac address. -

- -

- An even simpler way to get the MAC address would be to read what's on the little sticker on - the underside. (on the X200, this would be near the VGA port). -

+

ICH9 gen utility

-

- A bash script is also included in libreboot which will change the mac address (using ich9gen) - on all X200 ROM images. For instance:
- $ ./ich9macchange XX:XX:XX:XX:XX:XX -

+

+ This is no longer strictly necessary. Libreboot ROM images for X200 now + contain the 12KiB descriptor+gbe generated from ich9gen, by default. +

-

- Two new files will be created: -

- +

+ It is no longer necessary to use ich9deblob to generate + a deblobbed descriptor+gbe image for the X200. ich9gen is a small utility within + ich9deblob that can generate them from scratch, without a factory.bin dump. +

-

- ich9gen executables can be found under ./ich9deblob/ statically compiled in - libreboot_bin. If you are using src or git, build ich9gen from source with:
- $ ./builddeps-ich9deblob
- The executable will appear under resources/utilities/ich9deblob/ -

- -

- Assuming that your X200 libreboot image is named libreboot.rom, copy - the file to where libreboot.rom is located - and then run, for instance:
- $ dd if=ich9fdgbe_8m.bin of=libreboot.rom bs=1 count=12k conv=notrunc
- or:
- $ dd if=ich9fdgbe_4m.bin of=libreboot.rom bs=1 count=12k conv=notrunc -

- -

- Your X200 libreboot.rom image is now ready to be flashed on the machine. Refer back to - ../install/index.html#flashrom - for how to flash it. -

+

+ Run:
+ $ ./ich9gen +

+ +

+ It is also possible to generate a descriptor+gbe image with your own MAC address + inside (with the Gbe checksum updated to match). Run:
+ $ ./ich9gen --macaddress XX:XX:XX:XX:XX:XX
+ (replace the XX chars with the hexadecimal chars in the MAC address that you want) +

+ +

+ You can find out your MAC address from ip addr or ifconfig in GNU/Linux. + Alternatively, if you are running libreboot already (with the correct MAC address in your + ROM), dump it (flashrom -r) and read the first 6 bytes from position 0x1000 (or 0x2000) in a hex editor + (or, rename it to factory.rom and run it in ich9deblob: in the newly created mkgbe.c + will be the individual bytes of your MAC address). If you are currently running the stock firmware + and haven't installed libreboot yet, you can also run that through ich9deblob to get the mac address. +

+ +

+ An even simpler way to get the MAC address would be to read what's on the little sticker on + the underside. (on the X200, this would be near the VGA port). +

+ +

+ A bash script is also included in libreboot which will change the mac address (using ich9gen) + on all X200 ROM images. For instance:
+ $ ./ich9macchange XX:XX:XX:XX:XX:XX +

+ +

+ Two new files will be created: +

+ + +

+ ich9gen executables can be found under ./ich9deblob/ statically compiled in + libreboot_bin. If you are using src or git, build ich9gen from source with:
+ $ ./builddeps-ich9deblob
+ The executable will appear under resources/utilities/ich9deblob/ +

+ +

+ Assuming that your X200 libreboot image is named libreboot.rom, copy + the file to where libreboot.rom is located + and then run, for instance:
+ $ dd if=ich9fdgbe_8m.bin of=libreboot.rom bs=1 count=12k conv=notrunc
+ or:
+ $ dd if=ich9fdgbe_4m.bin of=libreboot.rom bs=1 count=12k conv=notrunc +

+ +

+ Your X200 libreboot.rom image is now ready to be flashed on the machine. Refer back to + ../install/index.html#flashrom + for how to flash it. +

+ +
-
+
-

ICH9 deblob utility

- -

- This is no longer strictly necessary. Libreboot ROM images for X200 now - contain the 12KiB descriptor+gbe generated from ich9gen, by default. -

+

ICH9 deblob utility

-

- This was the tool originally used to disable the ME on X200. ich9gen now supersedes it; - ich9gen is better because it does not rely on dumping the factory.rom image (whereas, ich9deblob does). -

- -

- This is what you will use to generate the deblobbed descriptor+gbe regions for your libreboot ROM image. -

-

- If you are working with libreboot_src (or git), you can find the source under resources/utilities/ich9deblob/ - and will already be compiled if you ran ./builddeps or ./builddeps-ich9deblob from the main directory (./), - otherwise you can build it like so:
- $ ./builddeps-ich9deblob
- An executable file named ich9deblob will now appear under resources/utilities/ich9deblob/ -

-

- If you are working with libreboot_bin release archive, you can find the utility included, statically compiled - (for i686 and x86_64 on GNU/Linux) under ./ich9deblob/. -

- -

- Place the factory.rom from your X200 - (can be obtained using the guide at ../install/x200_external.html) in - the directory where you have your ich9deblob executable, then run the tool:
- $ ./ich9deblob -

-

- A 12kiB file named deblobbed_descriptor.bin will now appear. Keep this and the factory.rom stored in a safe location! - The first 4KiB contains the descriptor data region for your machine, and the next 8KiB contains the gbe region (config data for your - gigabit NIC). These 2 regions could actually be separate files, but they are joined into 1 file in this case. -

- -

- Assuming that your X200 libreboot image is named libreboot.rom, copy - the deblobbed_descriptor.bin file to where libreboot.rom is located - and then run:
- $ dd if=deblobbed_descriptor.bin of=libreboot.rom bs=1 count=12k conv=notrunc -

- -

- The utility will also generate 4 additional files: -

- -

- These are C source files that can re-generate the very same Gbe and Descriptor structs - (from ich9deblob/ich9gen). To use these, place them in src/ich9gen/ in ich9deblob, then re-build. - The newly built ich9gen executable will be able to re-create the very same 12KiB file from scratch, - based on the C structs, this time without the need for a factory.rom dump! -

+

+ This is no longer strictly necessary. Libreboot ROM images for X200 now + contain the 12KiB descriptor+gbe generated from ich9gen, by default. +

+ +

+ This was the tool originally used to disable the ME on X200. ich9gen now supersedes it; + ich9gen is better because it does not rely on dumping the factory.rom image (whereas, ich9deblob does). +

-

- You should now have a libreboot.rom image containing the correct 4K descriptor and 8K gbe regions, which - will then be safe to flash. Refer back to ../install/index.html#flashrom - for how to flash it. -

+

+ This is what you will use to generate the deblobbed descriptor+gbe regions for your libreboot ROM image. +

+

+ If you are working with libreboot_src (or git), you can find the source under resources/utilities/ich9deblob/ + and will already be compiled if you ran ./builddeps or ./builddeps-ich9deblob from the main directory (./), + otherwise you can build it like so:
+ $ ./builddeps-ich9deblob
+ An executable file named ich9deblob will now appear under resources/utilities/ich9deblob/ +

+

+ If you are working with libreboot_bin release archive, you can find the utility included, statically compiled + (for i686 and x86_64 on GNU/Linux) under ./ich9deblob/. +

+ +

+ Place the factory.rom from your X200 + (can be obtained using the guide at ../install/x200_external.html) in + the directory where you have your ich9deblob executable, then run the tool:
+ $ ./ich9deblob +

+

+ A 12kiB file named deblobbed_descriptor.bin will now appear. Keep this and the factory.rom stored in a safe location! + The first 4KiB contains the descriptor data region for your machine, and the next 8KiB contains the gbe region (config data for your + gigabit NIC). These 2 regions could actually be separate files, but they are joined into 1 file in this case. +

+ +

+ Assuming that your X200 libreboot image is named libreboot.rom, copy + the deblobbed_descriptor.bin file to where libreboot.rom is located + and then run:
+ $ dd if=deblobbed_descriptor.bin of=libreboot.rom bs=1 count=12k conv=notrunc +

+ +

+ The utility will also generate 4 additional files: +

+ +

+ These are C source files that can re-generate the very same Gbe and Descriptor structs + (from ich9deblob/ich9gen). To use these, place them in src/ich9gen/ in ich9deblob, then re-build. + The newly built ich9gen executable will be able to re-create the very same 12KiB file from scratch, + based on the C structs, this time without the need for a factory.rom dump! +

+ +

+ You should now have a libreboot.rom image containing the correct 4K descriptor and 8K gbe regions, which + will then be safe to flash. Refer back to ../install/index.html#flashrom + for how to flash it. +

+ +
-
+

The sections below are adapted from (mostly) IRC logs related to early development getting the ME removed on the X200. They are useful for background information. This could not have been done without sgsit's help.

-
+

Early notes

@@ -216,9 +224,11 @@
-
+
+ +
-
+

Flash chips

@@ -243,11 +253,11 @@
-
+
-
+
-

Early development notes

+

Early development notes

 
@@ -312,35 +322,33 @@ Flash Erase Size = 0x1000
-

- It's a utility called 'Flash Image Tool' for ME 4.x that was used for this. You drag a complete - image into in and the utility decomposes the various components, allowing you to set soft straps. -

-

- This tool is proprietary, for Windows only, but was used to deblob the X200. End justified means, and - the utility is no longer needed since the ich9deblob utility (documented on this page) can now be - used to create deblobbed descriptors. -

- -
+

+ It's a utility called 'Flash Image Tool' for ME 4.x that was used for this. You drag a complete + image into in and the utility decomposes the various components, allowing you to set soft straps. +

+

+ This tool is proprietary, for Windows only, but was used to deblob the X200. End justified means, and + the utility is no longer needed since the ich9deblob utility (documented on this page) can now be + used to create deblobbed descriptors. +

-
+
-
+
-

- GBE (gigabit ethernet) region in SPI flash -

+

+ GBE (gigabit ethernet) region in SPI flash +

-

- Of the 8K, about 95% is 0xFF. - The data is the gbe region is fully documented in this public datasheet: - http://www.intel.co.uk/content/dam/doc/application-note/i-o-controller-hub-9m-82567lf-lm-v-nvm-map-appl-note.pdf -

+

+ Of the 8K, about 95% is 0xFF. + The data is the gbe region is fully documented in this public datasheet: + http://www.intel.co.uk/content/dam/doc/application-note/i-o-controller-hub-9m-82567lf-lm-v-nvm-map-appl-note.pdf +

-

- The only actual content found was: -

+

+ The only actual content found was: + 

 
@@ -358,17 +366,19 @@ DD  CC  18  00  11  20  17  00  DD  DD  18  00  12  20  17  00
-

- The first part is the MAC address set to all 0x1F. It's repeated haly way through - the 8K area, and the rest is all 0xFF. This is all documented in the datasheet. -

+

+ The first part is the MAC address set to all 0x1F. It's repeated haly way through + the 8K area, and the rest is all 0xFF. This is all documented in the datasheet. +

-

- The GBe region starts at 0x20A000 bytes from the *end* of a factory image and is 0x2000 bytes long. - In libreboot (deblobbed) the descriptor is set to put gbe directly after the initial 4K flash descriptor. - So the first 4K of the ROM is the descriptor, and then the next 8K is the gbe region. -

+

+ The GBe region starts at 0x20A000 bytes from the *end* of a factory image and is 0x2000 bytes long. + In libreboot (deblobbed) the descriptor is set to put gbe directly after the initial 4K flash descriptor. + So the first 4K of the ROM is the descriptor, and then the next 8K is the gbe region. +

+
+

GBE region: change MAC address

@@ -399,116 +409,117 @@ DD CC 18 00 11 20 17 00 DD DD 18 00 12 20 17 00 and that has to add up to 0xBABA. In other words, the checksum is 0xBABA minus the total of the first 0x3E 16bit numbers (unsigned), ignoring any overflow. - +

-
+
-
+
-

Flash descriptor region

+

Flash descriptor region

-

- http://www.intel.co.uk/content/dam/doc/datasheet/io-controller-hub-9-datasheet.pdf - from page 850 onwards. This explains everything that is in the flash descriptor, which can be used to understand what libreboot - is doing about modifying it. -

+

+ http://www.intel.co.uk/content/dam/doc/datasheet/io-controller-hub-9-datasheet.pdf + from page 850 onwards. This explains everything that is in the flash descriptor, which can be used to understand what libreboot + is doing about modifying it. +

-

- How to deblob: -

-
    -
  • patch the number of regions present in the descriptor from 5 - 3
    • -
  • originally descriptor + bios + me + gbe + platform
    • -
  • modified = descriptor + bios + gbe
    • -
  • the next stage is to patch the part of the descriptor which defines the start and end point of each section
    • -
  • then cut out the gbe region and insert it just after the region
    • -
  • all this can be substantiated with public docs (ICH9 datasheet)
    • -
  • the final part is flipping 2 bits. Halting the ME via 1 MCH soft strap and 1 ICH soft strap
    • -
  • the part of the descriptor described there gives the base address and length of each region (bits 12:24 of each address)
    • -
  • to disable a region, you set the base address to 0xFFF and the length to 0
    • -
  • and you change the number of regions from 4 (zero based) to 2
    • -
+

+ How to deblob: +

+
    +
  • patch the number of regions present in the descriptor from 5 - 3
    • +
  • originally descriptor + bios + me + gbe + platform
    • +
  • modified = descriptor + bios + gbe
    • +
  • the next stage is to patch the part of the descriptor which defines the start and end point of each section
    • +
  • then cut out the gbe region and insert it just after the region
    • +
  • all this can be substantiated with public docs (ICH9 datasheet)
    • +
  • the final part is flipping 2 bits. Halting the ME via 1 MCH soft strap and 1 ICH soft strap
    • +
  • the part of the descriptor described there gives the base address and length of each region (bits 12:24 of each address)
    • +
  • to disable a region, you set the base address to 0xFFF and the length to 0
    • +
  • and you change the number of regions from 4 (zero based) to 2
    • +
-

- There's an interesting parameter called 'ME Alternate disable', which allows the ME to only handle hardware errata in the southbridge, - but disables any other functionality. This is similar to the 'ignition' in the 5 series and higher but using the standard firmware - instead of a small 128K version. Useless for libreboot, though. -

+

+ There's an interesting parameter called 'ME Alternate disable', which allows the ME to only handle hardware errata in the southbridge, + but disables any other functionality. This is similar to the 'ignition' in the 5 series and higher but using the standard firmware + instead of a small 128K version. Useless for libreboot, though. +

-

- To deblob the x200, you chop out the platform and ME regions and correct the addresses in flReg1-4. - Then you set meDisable to 1 in ICHSTRAP0 and MCHSTRAP0. -

+

+ To deblob the x200, you chop out the platform and ME regions and correct the addresses in flReg1-4. + Then you set meDisable to 1 in ICHSTRAP0 and MCHSTRAP0. +

-

How to patch the descriptor from the factory.rom dump

-
    -
  • map the first 4k into the struct (minus the gbe region)
    • -
  • set NR in FLMAP0 to 2 (from 4)
    • -
  • adjust BASE and LIMIT in flReg1,2,3,4 to reflect the new location of each region (or remove them in the case of Platform and ME)
    • -
  • set meDisable to 1/true in ICHSTRAP0 and MCHSTRAP0
    • -
  • extract the 8k GBe region and append that to the end of the 4k descriptor
    • -
  • output the 12k concatenated chunk
    • -
  • Then it can be dd'd into the first 12K part of a coreboot image.
    • -
  • the GBe region always starts 0x20A000 bytes from the end of the ROM
    • -
+

How to patch the descriptor from the factory.rom dump

+
    +
  • map the first 4k into the struct (minus the gbe region)
    • +
  • set NR in FLMAP0 to 2 (from 4)
    • +
  • adjust BASE and LIMIT in flReg1,2,3,4 to reflect the new location of each region (or remove them in the case of Platform and ME)
    • +
  • set meDisable to 1/true in ICHSTRAP0 and MCHSTRAP0
    • +
  • extract the 8k GBe region and append that to the end of the 4k descriptor
    • +
  • output the 12k concatenated chunk
    • +
  • Then it can be dd'd into the first 12K part of a coreboot image.
    • +
  • the GBe region always starts 0x20A000 bytes from the end of the ROM
    • +
-

- This means that libreboot's descriptor region will simply define the following regions: -

-
    -
  • descriptor (4K)
    • -
  • gbe (8K)
    • -
  • bios (rest of flash chip. CBFS also set to occupy this whole size)
    • -
+

+ This means that libreboot's descriptor region will simply define the following regions: +

+
    +
  • descriptor (4K)
    • +
  • gbe (8K)
    • +
  • bios (rest of flash chip. CBFS also set to occupy this whole size)
    • +
-

- The data in the descriptor region is little endian, and it represents bits 24:12 of the address - (bits 12-24, written this way since bit 24 is nearer to left than bit 12 in the binary representation). -

-

- So, x << 12 = address -

-

- If it's in descriptor mode, then the first 4 bytes will be 5A A5 F0 0F. -

+

+ The data in the descriptor region is little endian, and it represents bits 24:12 of the address + (bits 12-24, written this way since bit 24 is nearer to left than bit 12 in the binary representation). +

+

+ So, x << 12 = address +

+

+ If it's in descriptor mode, then the first 4 bytes will be 5A A5 F0 0F. +

-
+
-
-
+
-

platform data partition in boot flash (factory.rom / lenovo bios)

+

platform data partition in boot flash (factory.rom / lenovo bios)

-

- Basically useless for libreboot, since it appears to be a blob. - Removing it didn't cause any issues in libreboot. -

-

- This is a 32K region from the factory image. It could be data - (non-functional) that the original Lenovo BIOS used, but we don't know. -

- -

- It has only a 448 byte fragment different from 0x00 or 0xFF. -

+

+ Basically useless for libreboot, since it appears to be a blob. + Removing it didn't cause any issues in libreboot. +

+

+ This is a 32K region from the factory image. It could be data + (non-functional) that the original Lenovo BIOS used, but we don't know. +

-
+

+ It has only a 448 byte fragment different from 0x00 or 0xFF. +

+ +
-
+
-

- Copyright © 2014 Francis Rowe <info@gluglug.org.uk>
- This document is released under the Creative Commons Attribution-ShareAlike 4.0 International Public License and all future versions. - A copy of the license can be found at ../license.txt. -

+

+ Copyright © 2014, 2015 Francis Rowe <info@gluglug.org.uk>
+ This document is released under the Creative Commons Attribution-ShareAlike 4.0 International Public License and all future versions. + A copy of the license can be found at ../license.txt. +

-

- This document is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See ../../license.txt for more information. -

+

+ This document is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See ../../license.txt for more information. +

+ +
-- cgit v0.9.1