Added more

README.md

@@ -6,7 +6,7 @@ The original issue was posted on reddit by [/u/Kronikaetor](https://www.reddit.c
 
 ## Summary
 
-Kronikaetor has an in-warranty Thinkpad L490. Initially shipped with freedos, he installed Ubuntu 19.04 until it reached EOL, then attempted to install 20.04 at which point his laptop refused to run stably. He attempted:
+Kronikaetor has an in-warranty Thinkpad L490. Initially shipped with [freedos](http://www.freedos.org/), he installed Ubuntu 19.04 until it reached EOL, then attempted to install 20.04 at which point his laptop refused to run stably. He attempted:
 
 * Installation of 18.04
 * Installation of 20.04
@@ -15,13 +15,29 @@ But had no success, each attempt resulted in an OS that would work momentarily,
 
 ## Diagnostics
 
+### Required packages
+
+* curl (for downloading logs and iso files)
+* netcat (for shipping logs to [seashells](https://seashells.io))
+* genisoimage (to produce bootable bios update USB)
+* unzip (to extract zips on the terminal)
+
+To install these on ubuntu:
+```bash
+sudo apt update && sudo apt install \
+genisoimage \
+curl \
+netcat \
+unzip
+```
+
 ### Logs
 
+__Please make sure to install [Required packages](#Required-packages) before following this process.__
+
 During diagnostics on a live usb we ran the following commands to ship logs to [seashells](https://seashells.io):
 
 ```bash
-# Install netcat to perform log-shipping
-apt install netcat
 # Capture static logs once for later consumption
 sudo dmidecode | nc seashells.io 1337
 sudo lscpi | nc seashells.io 1337
@@ -47,3 +63,49 @@ curl https://seashells.io/p/s5SeWhbp > journalctl.log
 * [dmidecode.log](./logs/dmidecode.log)
 * [journalctl.log](./logs/journalctl.log)
 * [lspci.log](./logs/lspci.log)
+
+### Firmware Updates
+
+To ensure BIOS firmware was not the issue, we chose to perform a bios update.
+
+#### Thinkpad L490 BIOS Updates
+
+__Please make sure to install [Required packages](#Required-packages) before following this process.__
+
+The L490 does not have a CD drive, and yet the only way Lenovo provide to update firmware outside of Windows is a non-USB iso file available (available at time of writing [here](https://download.lenovo.com/pccbbs/mobiles/r0zuj12wd.iso)). Thanks Lenovo.
+
+_Before blindly following this guide, you should ensure you have downloaded the correct iso for your hardware by entering your serial on lenovo's website, and be VERY careful with the dd command listed below_
+
+To make this work with USB we had to utilise a tool called [geteltorino](http://manpages.ubuntu.com/manpages/trusty/man1/geteltorito.1.html) to pull a USB bootable el torino disk image out of the iso, and then write it to USB:
+
+```bash
+# Download iso file
+curl https://download.lenovo.com/pccbbs/mobiles/r0zuj12wd.iso -o r0zuj12wd.iso
+# extract el torino file from iso file
+geteltorito r0zuj12wd.iso > bios.img
+# On the assumption your usb device is at /dev/sdb (verify with sudo gdisk -l prior to running this command!!!!)
+sudo dd if=bios.img of=/dev/sdb bs=1M
+# sync disk before unplugging
+sync
+```
+
+This successfully updated the BIOS, however did not resolve the issue.
+
+#### Intel nvme SSD790 firmware Updates
+
+__Please make sure to install [Required packages](#Required-packages) before following this process.__
+
+Lenovo do provide firmware updates for this SSD, however again they are only available in Windows guise. Intel themselves do, however, provide a linux-friendly USB-Bootable iso image [here](https://downloadcenter.intel.com/download/29248/Intel-SSD-Firmware-Update-Tool). This can be downloaded, extracted, and written to usb:
+
+```bash
+### Download zip
+curl https://downloadmirror.intel.com/29248/eng/FirmwareUpdateTool_v3_0_8.zip -o FirmwareUpdateTool_v3_0_8.zip
+### unzip it
+unzip FirmwareUpdateTool_v3_0_8.zip
+# On the assumption your usb device is at /dev/sdb (verify with sudo gdisk -l prior to running this command!!!!)
+sudo dd if=issdfut_64_3.0.8.iso of=/dev/sdb bs=1m
+# sync disk before unplugging
+sync
+```
+
+Unfortunately, the same bug that we are trying to fix seemingly causes the linux-based updater to fail. If you have access to another machine with a spare m.2 nvme slot available, however, this step may still be useful in resolving your issue and so will be left here.