Dumping logs

When facing an issue on a unique hardware configuration on the end user side it may prove useful to submit system logs to Dasharo team for diagnosis and possibly problem solution. This section describes how to dump various logs from a running system.

System information

One may use Dasharo Tools Suite HCL report or fwdump-docker image to gather all the hardware configuration information from a running system. The usage of the tools should result in an archive containing various logs from the running system. Submit them via email to contact@dasharo.com or use Dasharo pastebin.

cbmem utility

When already migrated to Dasharo, it is possible to retrieve firmware logs from coreboot on a running system. A utility called cbmem can be used for that purpose. By obtaining the logs Dasharo team will be able to locate any issues with the firmware. This method requires Secure Boot to be disabled.

Options to get cbmem utility:

1. Download precompiled utility from 3mdeb cloud
2. Use Dasharo Tools Suite v1.1.0 or newer which has cbmem utility built in.
3. Compile cbmem utility. See procedure below.

Short instruction how to compile and use cbmem on Ubuntu 22.04 live CD:

1. Launch Ubuntu 22.04 live CD and choose to Try Ubuntu.
2. Right click on the desktop and choose Open in Terminal.

3. Install required packages:

   sudo apt-get install -y build-essential libpci-dev
   

4. Navigate to tmpfs: cd /tmp.

5. Download and extract coreboot source:

   wget https://coreboot.org/releases/coreboot-4.17.tar.xz
   tar xvf coreboot-4.17.tar.xz
   

6. Compile cbmem utility:

   cd coreboot-4.17/util/cbmem
   make
   

Obtaining Dasharo firmware log

One can obtain the firmware logs with:

```bash
sudo ./cbmem -1 > cbmem.log
```

Execute the above command on the target platform. Newer Dasharo distributions will also contain complete logs from UEFI Payload to help debug issues outside of coreboot.

NOTE: UEFI Payload logs are not available on platforms with serial console redirection enabled in the firmware.