libreboot.org 38 KB
leah rowe's bitcoin wallet
3DU4m2MA1DN4PvZvmRrhoSY9Y3MmM26k1M
localbitcoins.com
<leah> joshuaBPMan: tell you what though, 1 bitcoin is currently worth about
40000 USD [00:43]
<leah> joshuaBPMan: estimates say it's gonna go up to about 150000 this year
<joshuaBPMan> leah, ok. I'll consider donating somewhere it's more needed.
<leah> so like, if you're looking to spend 50-100 USD
<leah> buy that amount in bitcoin
<leah> and wait for bitcoin value to go up
<joshuaBPMan> may I ask what makes you think bitcoin will increase in value?
<leah> then sell your bitcoins
<leah> when bitcoin surges like that, it often goes back down again for a
while [00:44]
<leah> and when that happens, use the money you made to buy more bitcoins
again. and then sell when it goes up again
<leah> this is what i do
<joshuaBPMan> hmmm. interesting.
<leah> joshuaBPMan: what makes me think this is that lots of well respected
financial people are saying it
<leah> and bitcoin always goes up
<leah> as more and more people start using it, the value increases
<leah> and right now the world is in a depression, because of covid. it'll
last years [00:45]
<leah> and that is good business for bitcoin :)
<leah> i'm like
<leah> a really heavy bitcoin user
<leah> it's the best thing ever invented
<leah> like i actually make money off it
<leah> buying it up, selling when value increases, buying again when value
goes down [00:46]
<leah> it's a nice little extra revenue stream, and i don't have to do
anything really
<leah> my accountant loves it too [00:47]
<leah> i taught her how to use it
setting up a different mac address
dd if=libreboot.rom of=descriptor.bin bs=12K count=1 now insert descriptor.bin intoyour retroboot rom: dd if=descriptor.bin of=retroboot.rom bs=12K count=1 conv=notrunc; sync now flash retroboot.rom, then shut down, wait a few seconds, and power up your NIC should work after that. with the new retroboot rom [20:54]
https://libreboot.org/faq.html#how-do-i-pad-a-rom-before-flashing
weird hardware errors
The problem is that I am NOT using the intel CPU microcode updates. During intensive operations, the computer is crashing.
#+BEGIN_SRC Jan 6 10:44:41 localhost vmunix: [ 0.345476] mce: [Hardware Error]: Machine check events logged Jan 6 10:44:41 localhost vmunix: [ 0.345480] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 0: b200004000000800 Jan 6 10:44:42 localhost vmunix: [ 0.345525] mce: [Hardware Error]: TSC 0 Jan 6 10:44:42 localhost vmunix: [ 0.345564] mce: [Hardware Error]: PROCESSOR 0:1067a TIME 1609947820 SOCKET 0 APIC 0 microcode 0 Jan 6 10:44:42 localhost vmunix: [ 0.345607] mce: [Hardware Error]: Machine check events logged Jan 6 10:44:42 localhost vmunix: [ 0.345609] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 5: b200001024000e0f Jan 6 10:44:42 localhost vmunix: [ 0.345649] mce: [Hardware Error]: TSC 0 Jan 6 10:44:42 localhost vmunix: [ 0.345687] mce: [Hardware Error]: PROCESSOR 0:1067a TIME 1609947820 SOCKET 0 APIC 0 microcode 0 #+END_SRC
https://duckduckgo.com/?q=Hardware+Error%5D%3A+PROCESSOR+0%3A1067a+TIME+1609947820+SOCKET+0+APIC+0+microcode+0&ia=web
https://bugzilla.redhat.com/show_bug.cgi?id=1467040
https://askubuntu.com/questions/272324/any-idea-what-type-of-error-this-is-machine-check-kernel-panic/
#+BEGIN_SRC org joshuaBPMan: the problem is lack of CPU microcode updates [21:04] during heavy CPU+RAM usage, you encounter a machine check exception the CPU checks itself regularly, for sanity, and becomes unstable during heavy usage This is a bug in the CPU. However, the microcode in the CPU can be updated to correct it and improve stability. [21:05] With these updates, you will no longer encounter such instability on your machine. However, there is a price: Those updates are non-free binary blobs supplied by Intel. The policy of the Libreboot project is to exclude these updates, so as to meet its own criteria: 100% Free Software However, the CPU already has microcode on it (which implements the instruction set architecture, namely x86). That microcode is buggy, and quite old. [21:06] If you wish to solve this error, you can install the updates. basically the CPU goes wtf and linux kernel see that and just shuts down [21:07] this is to protect your machine joshuaBPMan: you might consider trying Retroboot instead, but please note, I haven't added T400 yet. However, if you'd like I can build you a T400 ROM, with microcode in it. It'll otherwise be identical to libreboot freedom-wise, but will contain the update. [21:08] Either that or: If you want to avoid blobs, you have no choice but to suffer such instability on your machine. [21:09] This is a known problem. There is no way to solve it without applying microcode. is this for only some cpus that t400 uses? or all all CPUs on Gm45 laptops such as X200, T400 etc we don't see such stability on other CPUs, on other platforms in libreboot [21:10] uh we don't see such instability on other CPUs, on other platforms in libreboot * orly_owl: everything you said to joshuaBPMan was wrong btw. no offense [21:11] Disclaimer: MCE (machine check exception) can still occur, even with microcode updates, but they will happen much less frequently (I've never seen it happen when microcode updates are supplied at boot time). [21:12] leah: np [21:14] im happy to learn something well [21:22] opteron 6300 on d16 and 4300 on d8 also has stability issues without microcode updates (on those machines, the libreboot project recommends 6200 or 4200 series) stable is best :) i personally have no issue with microcode, but libreboot says: 100% free software [21:23] and these machines still work well enough without them back in the early days, i was going to just include the microcode. but I wanted FSF's endorsement, and they insisted i remove them and nowadays it's just a legacy of those days that we still exclude them (if you want them, use retroboot instead) good to giver users/customers the option [21:24] you agree to microcode when you purchase an intel or amd processor. if you don't like them, or arm or riscv (or openpower, which uses them but they are unsigned, so could be replaced if you reverse engineer them) [21:25] my processor has them anyway, regardless, so i always install them. [21:26] libreboot.org's server, which runs libreboot (well, ROM is *from* libreboot) has microcode added to the ROM cuz you know, i don't want libreboot.org to crash :) [21:27] back in the day i would rally against them but i always had a voice in the back of my head telling me that what i was saying was bullshit. over the last few years, i decided to listen to that voice being honest with oneself is important leah: thanks for the tip! [22:12] joshuaBPMan: would you like me to build you a ROM [22:13] If you do, and it works, I'd be happy to send a $ tip your way. nah no money is required. ok i'll add T400 to retroboot see: retroboot.org it's a fork of libreboot ok. I'll go check it out. [22:14] also I've never actually updated libreboot via software. From what I've heard it's easy. also thanks for making libreboot. I'm a happy user. :) [22:15]
what are these weird cables coming from my laptop?
red and blue are for 3g modem, white, gray and black are for wifi [16:21] that wide connector on a "tape" is for panel and indicator lights(sometimes microphone) on 3g modem card you should have markings for red and blue. for wifi google it. i don't know [16:23]
I do not even have to build the flashrom! Flashrom is in the debian archive!
https://libreboot.org/docs/gnulinux/grub_cbfs.html
$ sudo apt-get install flashrom
I should edit this is the website, because this website is one caotic mess!
ok I am supposed to use the textmode rom images for the first flash.
https://libreboot.org/docs/gnulinux/grub_cbfs.html
I want to use textmode for the first flash, because textmode includes a memtest, which you should always run after installing libreboot.
Preparing for the installation
If you've decided that you want to use libreboot! Congratulations. You are about to use a free BIOS! To perform the installation you will need:
- a rasberry PI Model B or B+ OR a beagle bone black
- essential things for the PI
- a keyboard
- a mouse (optional, but useful)
- computer screen
- HDMI cable to connect the screen to the PI
- 6 female jumper cables.
- a 16 Panorma clip and/or a 8 clip Panorama clip
If you have Linux already installed on your laptop, then before you
disassemble your T200, T400, T60, etc. laptop, install the flashrom
util apt-get install flashrom, and run the command flashrom -p
internal. The output of that command should tell you the size of
the flash chip. It could be 4MB, 8MB, or 16MB. The utility should
say 8192 Kb if it is a 8MB chip. You can still check your chip
size later on, but this is the easiest way to do it.
After you have done that, you may want to take a look at the guides online about possible upgrading your CPU. Libreboot supports certain CPU models. Since you are taking apart your laptop, now might be a good time to upgrade the CPU. Also take a look at your RAM. You might want to consider upgrading your RAM, since you are going to take apart your laptop. Also libreboot may not support your RAM. You might want to check online, which RAM libreboot supports. 1
After you have done that, ensure that you have a rasberry pi or beagle board and some female wires (10 females wires is plenty), and a panorama clip. Your flash chip will either have 8 or 16 connection points. You will only know once you take your laptop apart. You could buy two panorama clips, or just buy the 16 port one. If you know what you are doing, then you can use the 16 port one on an 8 port chip.
Now that you have all the parts that you need, go ahead and take your laptop apart. This guide, though quick, will give you some idea of how to take everything apart for the T400.
https://invidio.us/watch?v=xH1Gg-OhBH4
https://libreboot.org/docs/install/rpi_setup.html
A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is also fine: (I believe my Macbook has an ATX PSU, this was developed by Intel).
Please note that this guide uses notation to help distinguish that you should run commands on a laptop vs. on the pi. They are:
pi$run this command as a regular user on the pi.pi#run this command as root on the pi.x86$run this command as a regular user on the computer.x86#run this command as a root user on a computer.
Upgrade your EC firmware version
If you are librebooting a Lenovo laptop X60, T60, X200, T400, T500, R400, or W500, then you need to update your laptop to the latest EC firmware version (version 1.06). Lenovo has some firmware for the laptop. Once you install Libreboot, there is no known way to update your EC firmware version.
To find out what firmware version you are using. You can boot into your Lenovo BIOS, and check it. If it says firmware version 1.06, then continue.
Alternatively, in GNU/Linux run this command:
#+BEGIN_SRC sh x86$ grep 'at EC' /proc/asound/cards #+END_SRC
#+RESULTS:
ThinkPad Console Audio Control at EC reg 0x30, fw 7WHT19WW-3.6
7WHT19WW is the version in different notation, use search engine to find out regular version - in this case it’s a 1.06 for x200 tablet
If your EC firmware is outdated, then you can use the Lenovo update utility to update your firmware. There is an option to burn it to a disk, and boot it. This will not work after you install libreboot. Make sure your update your EC firmware before installing libreboot!
More information, such as where to get the Lenovo EC firmware update utility is available here:
https://www.thinkwiki.org/wiki/BIOS_update_without_optical_disk
wiring the beagle bone black (or rasberry pi) and chip together
ONLY connect the panorama clip to the flash chip while the PI is off. Never connect the clip to the chip after you turned the pi on.
Rasberry Pi model B+
Here is a table that shows you all of the pin Locations on the Rasberry Pi B+
|------+-----+-----+----------------+----+----+---------------| | | | | 3v3 Power | 1 | 2 | 5v Power | | | | | BCM 2 (SDA) | 3 | 4 | 5v Power | | | | | BCM 3 (SCL) | 5 | 6 | Ground | | HDMI | | | BCM 4 (GPCLK0) | 7 | 8 | BCM 14 (TXD) | | | | | Ground | 9 | 10 | BCM 15 (RXD) | | | | | BCM 17 | 11 | 12 | BCM 18 (PWM0) | | | | | BCM 27 | 13 | 14 | Ground | | | | | BCM 22 | 15 | 16 | BCM 23 | | | | | 3v3 Power | 17 | 18 | BCM 24 | | | | | BCM 10 (MOSI) | 19 | 20 | Ground | | | | | BCM 9 (MISO) | 21 | 22 | BCM 25 | | | | | BCM 11 (SCLK) | 23 | 24 | BCM 8 (CE0) | | | | | Ground | 25 | 26 | BCM 7 (CE1) | | | | | BCM 0 (ID_SD) | 27 | 28 | BCM 1 (ID_SC) | | | | | BCM 5 | 29 | 30 | Ground | | | | | BCM 6 | 31 | 32 | BCM 12 (PWM0) | | | | | BCM 13 (PWM1) | 33 | 34 | Ground | | | | | BCM 19 (MISO) | 35 | 36 | BCM 16 | | | | | BCM 26 | 37 | 38 | BCM 20 (MOSI) | | | | | Ground | 39 | 40 | BCM 21 (SCLK) | | | | | | | | | | | | | | | | | | | | | | | | | | | USB | USB | | | | | |------+-----+-----+----------------+----+----+---------------|
This image is helpful if you have a 16 pin flash chip https://libreboot.org/docs/install/images/t400/0065.jpg
If you are using a 16 pin on a 16 chip flash, then chart should prove helpful:
# https://libreboot.org/docs/install/rpi_setup.html
|-----+----------+-------------------| | pin | SPI pin | rasberry pi pin # | | 1 | not used | not used | | 2 | 3.3V | 1 | | 3 | not used | not used | | 4 | not used | not used | | 5 | not used | not used | | 6 | not used | not used | | 7 | CS# | 24 | | 8 | S0/S1O1 | 21 | | 9 | not used | not used | | 10 | GND | 25 | | 11 | not used | not used | | 12 | not used | not used | | 13 | not used | not used | | 14 | not used | not used | | 15 | S1/SIO0 | 19 | | 16 | SCLK | 23 | |-----+----------+-------------------|
a note on powering the flash chip
At this point your laptop should be completly disassembled. Please inspect your flash chip to determine which kind you have. If it say "MX", then you have a Macronix chip. If it says something else then you have an SST chip.
In order to operate, the flash chip needs to be supplied with 3.3V power. Note: The raspberry pi 3.3V rail should be sufficient to power the chip during flashing, so no external power supply should be required; however, generally SST chips can use the 3.3V from the Ii to provide power to the chip, but this does not always work for the Macronix chips. If you have an SST chip, then you should have no issues; please skip to the next section. But if you have a Macronix chip, please read on.
While the 3.3V power supply of the pi should be enough in terms of voltage to power the Macronix chip, but it may not necessary provide enough current for flashing. Perhaps you could power up an arduino and use it's 3.3V power supply. Maybe that will work. Or you could use a shutoff laptop, with the power connector plugged in. In that case, you would need a usb to female wire adater to power the Macronix chip. If that fails, then you may need an external PSU (power supply unit) that can provide 3.3V.
ensure that you have spi devices enabled in the pi
https://www.raspberrypi-spy.co.uk/2014/08/enabling-the-spi-interface-on-the-raspberry-pi/
SPI is a communication protocol for microcontrollers. You need to enable it, to reflash your chip.
#+BEGIN_SRC sh pi# sudo raspi-config #+END_SRC
Choose 5 "Interfacing Options"
Choose P4 SPI "Enable/Disable automatic loading"
Would you like the SPI interface to be enabled?
Yes
Ok
testing to see if you can read the chip
Reboot now
Power on your Pi, and run the following. Ensure you swap out “your_chip_name” with the proper name/model of your chip. Check that it can be read successfully. If you cannot read the chip and receive an error similar to “no EEPROM Detected” then you may want to make sure that MISO/MOSI are not swapped around, check with multimeter whether voltage is right and that ground is connected between “programmer” and target.
If you do not know what kind of chip you have, then try running this command. The output should show you what type of chip you have. It should also tell you what size of chip that you have. 8192 kB is an 8MB chip. 4000 kB or so is a 4MB.
#+BEGIN_SRC sh pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 #+END_SRC
#+RESULTS
flashrom v1.2-14 flashrom is free software, get the source at https://flashrom.org Using clock_gettime for delay Found Macronix flash chip "MX25L6405" (8192 kB, SPI) on linux_spi. Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi. Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
:WhatTheOfficialGuideSays: Now that you know what kind and what size your chip is run these commands to read your flash rom three times.
These commands are for the SST chip.
#+BEGIN_SRC sh
pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -r romread1.rom
pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -r romread2.rom
pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -r romread3.rom
#+END_SRC
These commands are for the Macronix chip. You may need to replace
-c "MX25L6405D" with your chip name.
#+BEGIN_SRC sh pi# cd ~/flashrom
pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -c "MX25L6405D" -r romread1.rom
pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -c "MX25L6405D" -r romread2.rom
pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -c "MX25L6405D" -r romread3.rom
#+END_SRC
Now that you have read and save the factory rom image 3 times, verify that the pi has a good connection. Check that all files are the same.
#+BEGIN_SRC sh pi# sha512sum romread*.rom #+END_SRC
If they are identical sha512 hashes then you can generally assume that it’s safe to continue, because flashrom has managed to read the flashchip precisely (but not always accurately). :END:
We are almost ready to flash the chip, but we want to make sure that we can read the rom's contents reliably and that it has not been corrupted.
We will now run two commands. The first command will read the stock proprietary rom image in the chip. The second will verify that what we read is what is in the file, which means that we can probably read the flash rom chip reliably.
These commands are for the SST chip.
#+BEGIN_SRC sh pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -r romread.rom pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -v romread.rom #+END_SRC
These commands are for the Macronix chip. You may need to replace
-c "MX25L6405D" with your chip name.
#+BEGIN_SRC sh pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -c "MX25L6405D" -r romread.rom pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -c "MX25L6405D" -v romread.rom #+END_SRC
Now you need to look at the end of stock rom file. If you see a ton of error messages at the end of the rom, then we will need to patch flashrom. The strings command will find all strings in the binary file, which should give something recognizable.
#+BEGIN_SRC sh strings romread.rom #+END_SRC
Check the end of its output. You should see some garbled strings at the end of its output. Like this:
#+BEGIN_VERSE 2ne0 en22 esmj 2@e# enn43 #+END_VERSE
If instead you see it's filled with output like OxFF/Ox00 2, then you will need to patch flashrom to work with your poor setup.
You may also check the output with hexedit
#+BEGIN_SRC sh sudo apt-get install hexedit hexedit readrom.rom #+END_SRC
Once readrom opens, you need to navigate to the end of the file. type Return or Enter. hexedit will prompt you for a location. If it is an 8MB file type RETURN 0x80000. If it is an 4MB file type 0x40000. Once you are at the end of the file, look for any error messages. The error messages look like "0xFF/0x00". If you see any of those, then you will need to patch flashrom. C-c will close the program.
getting the rom images and libreboot util
HTTPS mirrors
| UK | https://www.mirrorservice.org/sites/libreboot.org/release/ | | USA | https://mirror.math.princeton.edu/pub/libreboot/ | | USA | https://mirror.splentity.com/libreboot/ | | | https://mirror.sugol.org/libreboot/ | | Spain | https://mirrors.qorg11.net/libreboot/ | | Netherlands | https://mirror.koddos.net/libreboot/ | | France | https://elgrande74.net/libreboot/ | | France | https://mirror.swordarmor.fr/libreboot/ | | France | https://mirror.cyberbits.eu/libreboot/ | | Hong Kong | https://mirror-hk.koddos.net/libreboot/ |
Use the 2016 09 07 version. https://libreboot.org/docs/gnulinux/grub_cbfs.html https://mirror.math.princeton.edu/pub/libreboot/stable/20160907/
A good rule of thumb is to flash the libreboot rom as is. Download the rom image. Do not worry about changing the default Mac address yet. You can do that after you reassemble your laptop.
Download libreboot util:
All of the following commands ought to be executed on the pi.
So, now we need to install flash rom, which will let us flash our libreboot image. Then we need to download and unpack the libreboot utilities.
#+BEGIN_SRC sh pi# apt-get install flashrom pi$ wget https://mirror.math.princeton.edu/pub/libreboot/stable/20160907/libreboot_r20160907_util.tar.xz pi$ tar -xf libreboot_r20160907_util.tar.xz pi$ mv "libreboot_r20160907_util" "libreboot_util" #+END_SRC
# https://libreboot.org/docs/gnulinux/grub_cbfs.html
To download the right size rom, you need to know the size of your Macronix chip. It can be either 4mb, 8mb, or 16mb.
If your chip is not 8mb, then change the file so that it says "16mb" or "4mb".
#+BEGIN_SRC sh pi$ cd ~/; pi$ wget pi$ https://mirror.math.princeton.edu/pub/libreboot/stable/20160907/rom/grub/libreboot_r20160907_grub_t400_8mb.tar.xz pi$ tar -xf libreboot_grub_r20160907_grub_t400_8mb.tar.gz pi$ cd libreboot_grub_r20160907_grub_t400_8mb; #+END_SRC
One you are in this directory look for your preferred keyboard layout, and select the roms that say textmode. Those roms include Memtest86+, which you should always run after installing libreboot.
:IGuessWeAreNotDownloadingLibrebootUtil:
#mv libreboot_grub_r20160907/t400_8mb_usdvorak_txtmode.rom ~/libreboot_util/ich9deblob/armv71/; #cd ~/libreboot_util/ich9deblob/armv71/; :END:
the actual command to flash the chip
The first command flashes the chip. The second command verifies that what you put on the chip matches the libreboot rom.
If your chip is an SST, then run this command. #+BEGIN_SRC sh pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -w /path/to/libreboot.rom pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -v /path/to/libreboot.rom #+END_SRC
If your chip is a Macronix, then run this command. #+BEGIN_SRC sh pi# ./flashrom -c "MX25L6405D" -p linux_spi:dev=/dev/spidev0.0 -w /path/to/libreboot.rom pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0 -c "MX25L6405D" -v /path/to/libreboot.rom #+END_SRC
The first command may fail a couple times, but keep trying. You
may even see some error messages, but if the command finishes with
Verifying flash... Verified or Warning: Chip content is
identical to the requested image then you’re done.
The second command should also say finish with something like
Verifying flash... Verified.
Once you have verified that the command succedded successfully, then flash has completed successfully. Congradulations you have just installed libreboot!
Shut down your pi, put your laptop back together and reboot into memtest.
On the first boot of libreboot, run memtest!
You will need to have flashed the libreboot image with txtmode to do this. Memtest3 only works with txtmode.
also test network before you start changing stuff in gbe region *wired network [10:15] everything should work fine with unmodified libreboot image [10:17] (besides memtest with 8GiB of ram, which will break on test #7 block move) [10:18]
** change the mac address in the libreboot rom https://libreboot.org/docs/hardware/mac_address.html
https://libreboot.org/docs/gnulinux/grub_cbfs.html#changeMAC
you attach the keyboard as well if you don't have RTC battery inserted then it will start up by itself
:WhatTheOfficialGuideSays:
Change MAC address in ROM
The last step before flashing the new ROM, is to change the MAC address inside it. Every libreboot ROM image contains a generic MAC address; you want to make sure that your ROM image contains yours, so as to not create any problems on your network (say, for example, that multiple family members had libreboot computers, and used the same ROM image to flash those computers).
To do this, we will use the ich9gen utility, also located in
libreboot_util. Luckily, you are already in the folder that provides
that command!
Once there, run the following command, making sure to use your own MAC address, instead of what’s written below:
My Mac address is 00:1C:25:9A:37:BA
#+BEGIN_SRC sh $ ./ich9gen --macaddress XX:XX:XX:XX:XX:XX #+END_SRC
Three new files will be created:
ich9fdgbe_4m.bin: this is for GM45 laptops with the 4MB flash chip.
ich9fdgbe_8m.bin: this is for GM45 laptops with the 8MB flash chip.
ich9fdgbe_16m.bin: this is for GM45 laptops with the 16MB flash chip.
Look for the one that corresponds to the size of your ROM image; for example, if your flash chip size is 8mb, you’ll want to use ich9fdgbe_8m.bin.
Now, insert this file (called the descriptor+gbe) into the ROM image, using dd:
#+BEGIN_SRC $ dd if=ich9fdgbe_8m.bin of=libreboot.rom bs=1 count=12k conv=notrunc #+END_SRC
Move libreboot.rom back to the libreboot_util directory:
#+BEGIN_SRC sh $ mv libreboot.rom ~/Downloads/libreboot_util; #+END_SRC
You are finally ready to flash the ROM! :END:
:NotNeededInfo: Flash Updated ROM Image
The last step of flashing the ROM requires us to change our current working directory to libreboot_util:
$ cd ~/Downloads/libreboot_util
Now, all we have to do is use the flash script in this directory, with the update option, using libreboot.rom as the argument:
$ sudo ./flash update libreboot.rom
Ocassionally, coreboot changes the name of a given board. If flashrom complains about a board mismatch, but you are sure that you chose the correct ROM image, then run this alternative command:
$ sudo ./flash forceupdate libreboot.rom
:END:
change the mac address in the libreboot rom
https://libreboot.org/docs/hardware/mac_address.html
https://libreboot.org/docs/gnulinux/grub_cbfs.html#changeMAC
FIXME. This needs to be updated. Only change the macaddress after you have successfully flashed libreboot. You should change the macadress via software methods. Change the macaddress via libreboot software updates after you have reassembled your laptop.
Change MAC address in ROM
The last step before flashing the new ROM, is to change the MAC address inside it. Every libreboot ROM image contains a generic MAC address; you want to make sure that your ROM image contains yours, so as to not create any problems on your network (say, for example, that multiple family members had libreboot computers, and used the same ROM image to flash those computers).
To do this, we will use the ich9gen utility, also located in
libreboot_util. Luckily, you are already in the folder that provides
that command!
Once there, run the following command, making sure to use your own MAC address, instead of what’s written below:
My Mac address is 00:1C:25:9A:37:BA
#+BEGIN_SRC sh $ ./ich9gen --macaddress XX:XX:XX:XX:XX:XX #+END_SRC
Three new files will be created:
ich9fdgbe_4m.bin: this is for GM45 laptops with the 4MB flash chip.
ich9fdgbe_8m.bin: this is for GM45 laptops with the 8MB flash chip.
ich9fdgbe_16m.bin: this is for GM45 laptops with the 16MB flash chip.
Look for the one that corresponds to the size of your ROM image; for example, if your flash chip size is 8mb, you’ll want to use ich9fdgbe_8m.bin.
Now, insert this file (called the descriptor+gbe) into the ROM image, using dd:
#+BEGIN_SRC $ dd if=ich9fdgbe_8m.bin of=libreboot.rom bs=1 count=12k conv=notrunc #+END_SRC
Move libreboot.rom back to the libreboot_util directory:
#+BEGIN_SRC sh $ mv libreboot.rom ~/Downloads/libreboot_util; #+END_SRC
You are finally ready to flash the ROM! :NotNeededInfo: Flash Updated ROM Image
The last step of flashing the ROM requires us to change our current working directory to libreboot_util:
$ cd ~/Downloads/libreboot_util
Now, all we have to do is use the flash script in this directory, with the update option, using libreboot.rom as the argument:
$ sudo ./flash update libreboot.rom
Ocassionally, coreboot changes the name of a given board. If flashrom complains about a board mismatch, but you are sure that you chose the correct ROM image, then run this alternative command:
$ sudo ./flash forceupdate libreboot.rom
:END:
I may also need to modify the grub rom.
I can do this after the flashing of libreboot, or I can do with with the pi. Either way is fine apparently.
If I do not modify the grub payload from libreboot, then I will need to type in grub commands at every boot, which would be super annoying. :)
I could also do some grub hardening
https://libreboot.org/docs/gnulinux/grub_hardening.html
GNU Guix System full disk encrypted
If I have a sim card reader I should remove it permantly.
https://libreboot.org/docs/gnulinux/guix_system.html
On reboot your internet may fail
It has proprietary fireware, so it can track my movements.
Essentially, when you tear your laptop apart, you may need to take out the BIOS battery. This may really offset your date. So when you try to connect to the internet, your computer will get weird responses. Your computer may be trying to tell the server that the year is 2120, when the year is actually 2020. If that happens, you may not be able to connect.
#+BEGIN_SRC sh date #+END_SRC
#+RESULTS:
Thu 4 Jan 2120 07:34:49 PM EDT
The fix for this is simple.
#+BEGIN_SRC sh date --set "Thu 26 Mar 2020 07:34:00 PM" #+END_SRC
#+RESULTS:
How to update libreboot (on the T400)
Now you should be able to connect to the internet super easily.
Add this to the linux command line: iomem=relaxed
download the updated rom.
And flash your rom like this: (this will let you keep your current MAC address)
sudo flashrom -c MX25L6405D -p internal --ifd -i bios -w seabios_withgrub_t400_8mb_libgfxinit_txtmode_usdvorak.rom
leah │ yes leah │ sata ssd in ultrabay adapter leah │ linux, openbsd and freebsd software raid all work very well leah │ raid1 highly recommended gnucode │ leah, so raid1 works on a T400 ? leah │ that's right gnucode │ via libreboot? leah │ correct Guest6 │ can any one recommend to buy "freedom" managed switch? Or best way to do swith on 945gc + ICH7? gnucode │ geez. I need to take advantage of that! leah │ the dvd drive leah │ replace it with an ultrabay adapter with the 2nd drive leah │ you set up linux softraid in that leah │ grub can boot from mdraid easily leah │ for bsd, the bsd bootloaders support it, and can run from libreboot gnucode │ leah: I'm actually interested in using OpenBSD. leah │ yes leah │ raid1c works fine leah │ use seabios booting in text mode leah │ txtmode in filename from release gnucode │ cool. leah │ select MBR-style partitioning in openbsd leah │ look at this: leah │ https://www.openbsd.org/faq/faq14.html#softraid gnucode │ ok. leah, by the way, you actually created my libreboot image last time I was having help. :) leah │ you drop to shell before install, in openbsd's installer leah │ follow that guide on their faq gnucode │ will do thanks! leah │ when done, after doing the bioctl command, you havea new sdX device that is the raid1c leah │ then just type command: leah │ install leah │ and go through the normal installer, and select the raid1c one when partitioning leah │ it Just Works gnucode │ leah, should I update to the latest libreboot release? leah │ openbsd 7.2's bootloader is the first obsd bootloader that can boot raid1c gnucode │ "testing"? leah │ raid1c is encrypted raid1 leah │ which i recommend leah │ yes, update to it if you wish, but it's not strictly necessary leah │ unless you have 20220710 or before leah │ in which case yes, upgrade gnucode │ I need to do a dd if=/dev/random of=/dev/sda before I encrypt it. leah │ openbsd has flawless support for your machine gnucode │ I am using the 2016 version that you created for me actually. :) leah │ yeah dump that garbage and switch to the new release leah │ new release makes bsd easier leah │ the 2016 one has problems in it making bsd annoying to use gnucode │ ok. Will do. leah │ anything pre-november 2022 is worthless imo Guest6 │ leah can u recommend to buy "freedom" managed switch? Or best way to do switch on 945gc + ICH7? And do u know what USB to SATA adapter gives top performance on USB 2.0? leah │ well, pre-december leah │ just get a switch leah │ i don't use managed switches gnucode │ flashram -p internal is saying "Intel ICH9M-E" That means I have the 8MB rom right? leah │ you could basically use openwrt like that leah │ lots of openwrt-supported routers can do vlan leah │ which is probably what you want leah │ vlan ports leah │ i don't use that either leah │ yes gnucode you have 8MB flash probably leah │ but that ICH9M is the southbridge device leah │ just flash it and if it doesn't say VERIFIED at the end, tell me leah │ otherwise if it does, you got the new one gnucode │ gotcha. thanks. leah │ the recent libreboot releases add tons of improvements for your hardware leah │ historic stability issues are fixed, like
download the rom.
Footnotes
the ram stick.
gone awfully wrong.
- The T200 and T400 support DDR3 ram. NOT DDR4 ram.
- 0x00/0xFF is an error message that detects that something has
- memtest should be run on any computer after you have touched