summaryrefslogtreecommitdiffstats
path: root/docs/src/install/r500_external.texi
blob: 5b46f7f26cb2ae3ad45ab20d5435a7a46f89a00b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
\input texinfo
@documentencoding UTF-8

@ifnottex
@paragraphindent 0
@end ifnottex
@titlepage
@title ThinkPad R500: flashing tutorial (BeagleBone Black)
@end titlepage

@node Top
@top ThinkPad R500: flashing tutorial (BeagleBone Black)

@menu
* Flashing the R500 with a BeagleBone Black::
* LCD compatibly::
* A note about CPUs::
* A note about GPUs::
* CPU paste required::
* Flash chip size::
* MAC address::
* Initial BBB configuration::
* Thermal paste IMPORTANT::
* Wifi::
* WWAN::
* Memory::
@end menu

@node Flashing the R500 with a BeagleBone Black
@chapter Flashing the R500 with a BeagleBone Black
@anchor{#flashing-the-r500-with-a-beaglebone-black}
Initial flashing instructions for R500.

This guide is for those who want libreboot on their ThinkPad R500 while they still have the original Lenovo BIOS present. This guide can also be followed (adapted) if you brick your R500, to know how to recover.

Before following this section, please make sure to setup your libreboot ROM properly first. Although ROM images are provided pre-built in libreboot, there are some modifications that you need to make to the one you chose before flashing. (instructions referenced later in this guide)

@strong{NOTE: This board is unsupported in libreboot 20150518. To use it in libreboot, for now, you must build for it from source using the libreboot git repository.}

@uref{index.html,Back to main index}
@menu
* Serial port::
@end menu

@node Serial port
@section Serial port
@anchor{#serial-port}
EHCI debug might not be needed. It has been reported that the docking station for this laptop has a serial port, so it might be possible to use that instead.

@node LCD compatibly
@chapter LCD compatibly
@anchor{#lcd-compatibly}
Not all LCD panels are known to be compatible yet. See @uref{../hcl/gm45_lcd.html,../hcl/gm45_lcd.html}.

@node A note about CPUs
@chapter A note about CPUs
@anchor{#a-note-about-cpus}
@uref{http://www.thinkwiki.org/wiki/Category:R500,ThinkWiki} has a list of CPUs for this system. The Core 2 Duo P8400, P8600 and P8700 are believed to work in libreboot. The Core 2 Duo T9600 was confirmed to work (on a different laptop, but still GM45), so the T9400 probably also works. @strong{The Core 2 Duo T5870/5670 and Celeron M 575/585 are untested!}
@menu
* Quad-core CPUs::
@end menu

@node Quad-core CPUs
@section Quad-core CPUs
@anchor{#quad-core-cpus}
Although blocked by lenovobios (as was reported), it is reported that there are quad-core CPUs for GM45. This laptop has socketed CPUs, so it might be possible to use them (they are untested in coreboot; support may have to be added). Core 2 Quad Q9000, Q9100 or QX9300.

Look at this link:@* @uref{https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors,https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors}

@node A note about GPUs
@chapter A note about GPUs
@anchor{#a-note-about-gpus}
@uref{http://www.thinkwiki.org/wiki/Category:R500,ThinkWiki} lists two possible GPUs: Intel or ATI. Only the Intel GPUs work in libreboot; the ATI GPUs require a proprietary Video BIOS, and so those are unsupported in libreboot.

On other GM45 laptops in libreboot (e.g. T400, T500), so-called @emph{switchable graphics} is used, which means that the laptop will have @strong{both} an ATI and Intel GPU, or it will only have Intel, depending on which variation you have. On the systems with ATI and Intel, you can disable the ATI GPU and use only the Intel GPU, which works in libreboot.

@strong{It is unknown whether R500 laptops with an ATI GPU still have an Intel GPU, where you could disable the ATI GPU and use the Intel GPU. These are budget laptops, so it's highly likely that Lenovo decided on this model to ship with one GPU or the other, but not both (GPUs cost money).}

@strong{It is **HIGHLY** recommended, when ordering an R500 laptop, to **ENSURE** that the one you're ordering has an Intel GPU.}

@node CPU paste required
@chapter CPU paste required
@anchor{#cpu-paste-required}
See @ref{#paste,#paste}.

@node Flash chip size
@chapter Flash chip size
@anchor{#flash-chip-size}
Use this to find out:@* # @strong{dmidecode | grep ROM\ Size}@*

It is believed that all R500 laptops have only SOIC-8 (4MiB) chips.

@ref{#pagetop,Back to top of page.}

@node MAC address
@chapter MAC address
@anchor{#mac-address}
Unlike other GM45 thinkpads, the R500 has a different onboard gigabit NIC, where the MAC address is built-in. You do not need to change the MAC address at all on this laptop; simply flash the provided ROM images, as-is.

@node Initial BBB configuration
@chapter Initial BBB configuration
@anchor{#initial-bbb-configuration}
Refer to @uref{bbb_setup.html,bbb_setup.html} for how to setup the BBB for flashing.

The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250):

@verbatim
POMONA 5250 (correlate with the BBB guide)
===  VGA and ethernet socket ===
 18              -       - 1
 22              -       - NC
 NC              -       - 21
 3.3V (PSU)      -       - 17 - this is pin 1 on the flash chip
===  DVD drive ===
This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.
@end verbatim

@menu
* Disassembly::
@end menu

@node Disassembly
@section Disassembly
@anchor{#disassembly}
@image{../resources/images/r500/0001,,,,JPG} @image{../resources/images/r500/0002,,,,JPG} @image{../resources/images/r500/0003,,,,JPG} @image{../resources/images/r500/0004,,,,JPG} @image{../resources/images/r500/0005,,,,JPG} @image{../resources/images/r500/0006,,,,JPG} @image{../resources/images/r500/0007,,,,JPG} @image{../resources/images/r500/0008,,,,JPG} @image{../resources/images/r500/0009,,,,JPG} @image{../resources/images/r500/0010,,,,JPG} @image{../resources/images/r500/0011,,,,JPG} @image{../resources/images/r500/0012,,,,JPG} @image{../resources/images/r500/0013,,,,JPG} @image{../resources/images/r500/0014,,,,JPG} @image{../resources/images/r500/0015,,,,JPG} @image{../resources/images/r500/0016,,,,JPG} @image{../resources/images/r500/0017,,,,JPG} @image{../resources/images/r500/0018,,,,JPG} @image{../resources/images/r500/0019,,,,JPG} @image{../resources/images/r500/0020,,,,JPG} @image{../resources/images/r500/0021,,,,JPG} @image{../resources/images/r500/0022,,,,JPG} @image{../resources/images/r500/0023,,,,JPG} @image{../resources/images/r500/0024,,,,JPG} @image{../resources/images/r500/0025,,,,JPG} @image{../resources/images/r500/0026,,,,JPG} @image{../resources/images/r500/0027,,,,JPG} @image{../resources/images/r500/0028,,,,JPG} @image{../resources/images/r500/0029,,,,JPG} @image{../resources/images/r500/0030,,,,JPG} @image{../resources/images/r500/0031,,,,JPG}

Remove the motherboard from the cage, and the SPI flash chip will be next to the memory slots:@* @image{../resources/images/r500/0032,,,,JPG} @image{../resources/images/r500/flashchip,,,,jpg}

The following image is for illustration only, to show how a SOIC-8 clip is connected. This photo is from a T500, which has a different arrangement to the R500:@* @image{../resources/images/t500/0061,,,,jpg}

Connect your programmer, then connect GND and 3.3V@* @image{../resources/images/t400/0067,,,,jpg} @image{../resources/images/t400/0069,,,,jpg} @image{../resources/images/t400/0070,,,,jpg} @image{../resources/images/t400/0071,,,,jpg}

A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is also fine:@* @image{../resources/images/t400/0072,,,,jpg}

Of course, make sure to turn on your PSU:@* @image{../resources/images/x200/disassembly/0013,,,,jpg}

Now, you should be ready to install libreboot.

Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, libreboot also distributes flashrom source code which can be built.

Log in as root on your BBB, using the instructions in @uref{bbb_setup.html#bbb_access,bbb_setup.html#bbb_access}.

Test that flashrom works:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512}@* In this case, the output was:

@verbatim
flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l)
flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK.
Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi.
Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi.
Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi.
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.
@end verbatim

How to backup factory.rom (change the -c option as neeed, for your flash chip):@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom}@* Note: the @strong{-c} option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in @emph{flashchips.c} have been removed.@* Now compare the 3 images:@* # @strong{sha512sum factory*.rom}@* If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This is useful for reverse engineering work, if there is a desirable behaviour in the original firmware that could be replicated in coreboot and libreboot.

Now flash it:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V}

@image{../resources/images/x200/disassembly/0015,,,,jpg}

You might see errors, but if it says @strong{Verifying flash... VERIFIED} at the end, then it's flashed and should boot. If you see errors, try again (and again, and again); the message @strong{Chip content is identical to the requested image} is also an indication of a successful installation.

Example output from running the command (see above):

@verbatim
flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l)
flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK.
Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Erase/write done.
Verifying flash... VERIFIED.
@end verbatim

@ref{#pagetop,Back to top of page.}

@node Thermal paste IMPORTANT
@chapter Thermal paste (IMPORTANT)
@anchor{#thermal-paste-important}
Because part of this procedure involved removing the heatsink, you will need to apply new paste. Arctic Silver 5 is ok. You will also need isopropyl alcohol and an anti-static cloth to clean with.

When re-installing the heatsink, you must first clean off all old paste with the alcohol/cloth. Then apply new paste. AS5 is also much better than the default paste used on these systems.

@image{../resources/images/t400/paste,,,,jpg}

NOTE: the photo above is for illustration purposes only, and does not show how to properly apply the thermal paste. Other guides online detail the proper application procedure.

@node Wifi
@chapter Wifi
@anchor{#wifi}
The R500 typically comes with an Intel wifi chipset, which does not work without proprietary software. For a list of wifi chipsets that work without proprietary software, see @uref{../hcl/index.html#recommended_wifi,../hcl/index.html#recommended_wifi}.

Some R500 laptops might come with an Atheros chipset, but this is 802.11g only.

It is recommended that you install a new wifi chipset. This can only be done after installing libreboot, because the original firmware has a whitelist of approved chips, and it will refuse to boot if you use an 'unauthorized' wifi card.

The following photos show an Atheros AR5B95 being installed, to replace the Intel chip that this R500 came with:@* @image{../resources/images/t400/0012,,,,jpg} @image{../resources/images/t400/ar5b95,,,,jpg}

@node WWAN
@chapter WWAN
@anchor{#wwan}
If you have a WWAN/3G card and/or sim card reader, remove them permanently. The WWAN-3G card has proprietary firmware inside; the technology is identical to what is used in mobile phones, so it can also track your movements.

Not to be confused with wifi (wifi is fine).

@node Memory
@chapter Memory
@anchor{#memory}
You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs (speed/size). Non-matching pairs won't work. You can also install a single module (meaning, one of the slots will be empty) in slot 0.

Make sure that the RAM you buy is the 2Rx8 density.

The following photo shows 8GiB (2x4GiB) of RAM installed:@* @image{../resources/images/t400/memory,,,,jpg}
@menu
* Boot it!::
@end menu

@node Boot it!
@section Boot it!
@anchor{#boot-it}
You should see something like this:

@image{../resources/images/t400/boot0,,,,jpg} @image{../resources/images/t400/boot1,,,,jpg}

Now @uref{../gnulinux/index.html,install GNU/Linux}.

Copyright © 2015 Francis Rowe <info@@gluglug.org.uk>@* 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 the license can be found at @uref{../resources/licenses/gfdl-1.3.txt,gfdl-1.3.txt}

Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html}

UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.

TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.

The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.

@bye