NapoleonDynamite/website
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

docs: libreboot-guide

Browse source
This commit is contained in:
Filippo Ferrari 2024-03-06 22:09:53 +01:00
parent 4a02eed6df
commit e1fabbb740
1 changed files with 29 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

44
content/post/t400-libreboot-guide/index.md
View file

@ -1,5 +1,5 @@
--- ---
title: My T400 Libreboot Guide title: A simple T400 Libreboot Guide
description: Simplest Libreboot guide I can write description: Simplest Libreboot guide I can write
date: 2024-01-22 00:00:00+0000 date: 2024-01-22 00:00:00+0000
image: libreboot.png image: libreboot.png
@ -12,9 +12,9 @@ tags:
- bios - bios
--- ---
# [DRAFT] // It's a DRAFT, wait a sec dude, im still working on it # It's a DRAFT, wait a sec dude, im still working on it
The first step is to flash libreboot on your T400, the libreboot docs have a ton of information about installing libreboot on any compatible device, but I found it confusing to read given the huge amount of information on the site and the way they are structured. If you're not yet knowledgeable on the matter and you "just" want to libreboot your T400 (or X200), you might want to follow a simpler guide with just the must-know information and not much else. I decided to write this guide after i strugged to understand the correct procedure to libreboot my T400, the libreboot docs have a ton of information about installing libreboot on any compatible device, but I found it confusing to read given the huge amount of information on the site and the way they are structured. If you're not yet knowledgeable on the matter and you "just" want to libreboot your T400 (or X200), you might want to follow a simpler guide with just the must-know information and not much else.
## What hardware is needed: ## What hardware is needed:
@ -24,30 +24,44 @@ The case for the Pi is that if you just plan to flash your device, you will afte
The case of the CH341A is that it is inexpensive (I paid around 5 bucks for it). Still, when you're done, you won't have any use for the CH341A unless you want to flash other devices with an SPI interface.\ The case of the CH341A is that it is inexpensive (I paid around 5 bucks for it). Still, when you're done, you won't have any use for the CH341A unless you want to flash other devices with an SPI interface.\
Given my personal experience, I would suggest the CH341A simply because I tried and tried to flash my T400 with Pi 4 B without any luck. I was not able to read from the chip at any time, though after more research, I think these issues might be due to my clip. Given my personal experience, I would suggest the CH341A simply because I tried and tried to flash my T400 with Pi 4 B without any luck. I was not able to read from the chip at any time, though after more research, I think these issues might be due to my clip.
It's important to be aware that there are multiple versions of the CH341A programmer, the most common one being a version that delivers 3.3 volts to the motherboard chip, a voltage that is too big and could potentially fry the chip (even though multiple people have used it with no issue). If you opt for the CH341A and want to be as safe as possible, you must consider either finding the model that delivers 1.8V or modding the standard 3.3v version for 1.8v delivery. How: [LINK]\ It's important to be aware that there are multiple versions of the CH341A programmer, the most common one being a version that delivers 3.3 volts to the motherboard chip, a voltage that is too big and could potentially fry the chip (even though multiple people have used it with no issue). If you opt for the CH341A and want to be as safe as possible, you must consider either finding the model that delivers 1.8V or modding the standard 3.3v version for 1.8v delivery. How: [LINK]\
The Raspeberry Pi official shop is [here](https://www.raspberrypi.com/products/).\ The Raspberry Pi official shop is [here](https://www.raspberrypi.com/products/).\
The CH341A small ass documentation is [here](https://manuals.plus/m/42a6c56024fa90eeec462f62b17e84ed4725f010689d36a86d3f9368ef1c327d_optim.pdf). The CH341A small ass documentation is [here](https://manuals.plus/m/42a6c56024fa90eeec462f62b17e84ed4725f010689d36a86d3f9368ef1c327d_optim.pdf).
### SOIC clip ### SOIC clip
You will need a SOIC clip to connect to the flash chip and the programmer. I cannot stress enough how important the quality of the clip is. I have struggled for weeks to make awful Chinese clips work due to me being a cheap fuck, but I assure you that a good clip is gonna make the process simpler and less frustrating. The best and most quoted clip is the POMONA clip, which is also way more expensive than the clones that you will find on Aliexpress, eBay, or similar stores, will make your life easier. I'm not saying you HAVE to use it, but it's definitely recommended.\ You will need a SOIC clip to connect to the flash chip and the programmer. I cannot stress enough how important the quality of the clip is. I have struggled for weeks to make awful Chinese clips work due to me being a cheap fuck, but I assure you that a good clip is gonna make the process simpler and less frustrating. The best and most quoted clip is the POMONA clip, which is also way more expensive than the clones that you will find on Aliexpress, eBay, or similar stores, will make your life easier. I'm not saying you HAVE to use it, but it's definitely recommended.\
It is rare, but not impossible, that you will have a chip that will require a different clip, statistically it will be [placeholder], aside from buying a clip that is compatible with your chip the rest of the process is virtually the same.\ It is rare, but not impossible, that you will have a chip that will require a different clip, statistically it will be [placeholder], aside from buying a clip that is compatible with your chip the rest of the process is virtually the same.
#### Clip size #### Clip size
Most T400s will require a SOIC 16 or SOIC 8 depending on the chip size. If your T400 is already disassembled, you can just look at the pins of the clip; a 16-pin chip will require a SOIC 16, and an 8-pin chip will require a SOIC 8. If your T400 is not disassembled yet, you can read the chip with the flashrom package and know, based on the memory size of the chip, what clip you will need: an 8mb chip will correspond to a 16 pins chip and a 4mb chip will correspond to an 8 pins chip.\ Most T400s will require a SOIC 16 clip or SOIC 8 clip depending on the chip size. If your T400 is already disassembled, you can just look at the pins of the clip; a 16-pin chip will require a SOIC 16 clip, and an 8-pin chip will require a SOIC 8 clip. If your T400 is not disassembled yet, you can read the chip with the flashrom package and know, based on the memory size of the chip, what clip you will need: an 8mb chip will correspond to a 16 pins chip and a 4mb chip will correspond to an 8 pins chip.\
More on that later. ##### Reading the chip size
After having installed the flashrom package from your distro repositories, run:
```
flashrom -p internal
```
### Jumper cables ### Jumper cables
Standard jumper cables are fine; have an assortment of female-male, female-female ready depending on what the interface of your programmer and clip will need.\ Standard jumper cables are fine; have an assortment of female-male, female-female ready depending on what the interface of your programmer and clip will need.\
Probably won't need male-male jumpers. Probably won't need male-male jumpers.
### Wireless Card
The standard wifi cards installed on these devices will not longer work due to them requiring non-free software. You will need a new one, compatible with the new BIOS, most atheros will do fine. Take a look at the AR5B22.
## Disassembly ## Disassembly
You will need to disassemble the T400 for the first flashing of libreboot, once it is installed every next flash of the bios can happen internally. You have two options when it comes to disassembly: you can completely disassemble every single component of the pc, including detaching the motherboard from the plastic cage; or you can just remove the battery and palm rest and "mod" (AKA break) the plastic cage to have access to the chip. You will need to disassemble the T400 for the first flashing of libreboot, once it is installed every next flash of the bios can happen internally. You have two options when it comes to disassembly: you can completely disassemble every single component of the pc, including detaching the motherboard from the plastic cage; or you can just remove the battery and palm rest and "mod" (AKA break) the plastic cage to have access to the chip.\
[PHOTOS] Why do I illustrate these two options? Because, in case you just want to libreboot the laptop without doing any additional mods then the less invasive method will save you time and energy, but if you plan to mod further the laptop you can do everything in a single go and disassemble it only once (hopefully).\
Why do I illustrate these two options? Because, in case you just want to libreboot the laptop without doing any additional mods then the less invasive method will save you time and energy, but if you plan to mod further the laptop you can do everything in a single go and disassemble it once (hopefully) The only other mod that will be illustrated in this guide will be the quad-core mod, that allows installing a range of quad-core CPUs on a T400 that would otherwise only have dual-core CPUs compatible. For the cooling mod, that makes sense only after you do the quad-core mod, follow this guide: [LINK] An example might me installing a quad-core CPU on the machine, which would require a complete disassembly, you can find more info on this mod and many more in the article about T400 mods [here](https://bytemeifyoucan.lol/p/t400-mods/).
Flashrom installation: If you're using a raspberry as a programmer, ssh into it to install the flashrom package, if you're using the CH341A install the package on the pc you will be connection the programmer to. The package comes with the "flashrom" command, in most cases, this is all you will need to use (we will see common (and less common) flashing errors and their workarounds. ## Clip to chip connection
After having disassembled the device, you will have access, just on top of the two RAM slots, to the bios chip. Using the jumper cables connect your programmer of choice to the clip and then the clip to the chip.\
REMEMBER to turn on the programmer only AFTER a solid connection between the clip and chip is established, to avoid any kind of voltage issue. Similarly, turn off the programmer BEFORE removing the clip.\
Flashrom reading: TODO ## Read the chip contents
Install the ```flashrom``` package. Installation may vary depending on what distribution you have. I don't know the availability of flashrom on MacOS or Windows, tough luck.\
The next step is to read and save the current BIOS, so that, in case anything goes wrong while writing onto the chip, you will have a backup to use to go back to a working BIOS. It is highly recommended to backup the .bin a couple of times and use the command ```diff``` to check the you have two exact copies of the BIOS, keep trying until you do. This is the safest option, although I have never done it cause I'm a cool guy that likes to live on the edge.\
## Clip -> chip connection ### Using Raspberry or similar boards
If you're using a raspberry or a similar board as your programmer, ssh into it and, if you have not done it already, install the flashrom package.
### Using the CH341A programmer
If you're using the CH341A, install the package on the pc you will be connecting the programmer to.
After having disassembled the device, you will have access, just on top of the two RAM slots, to the bios chip. Using the jumper cables connect your programmer of choice to the Clip and then the clip to the chip. REMEMBER to turn on the programmer only AFTER a solid connection between the clip and chip is established, to avoid any kind of voltage issue. Similarly, turn off the programmer BEFORE removing the clip. TO BE CONTINUED AS SOON AS I HAVE A CRUMB OF TIME
the next step is to read and save the current BIOS, so that, in case anything goes wrong while writing onto the chip, you will have a backup to use to go back to a working BIOS. It is highly recommended to backup the .bin a couple of times and use the command "diff" to check the you have two exact copies of the BIOS, keep trying until you do. This is the safest option, i never do it cause it bothers me trying to have a working BIOS.