aboutsummaryrefslogtreecommitdiff
path: root/docs/gnulinux/grub_cbfs.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/gnulinux/grub_cbfs.md')
-rw-r--r--docs/gnulinux/grub_cbfs.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md
index 538a04fd..d15e70d5 100644
--- a/docs/gnulinux/grub_cbfs.md
+++ b/docs/gnulinux/grub_cbfs.md
@@ -138,8 +138,8 @@ flashed. For the purpose of this tutorial it is assumed that your ROM
image file is named *libreboot.rom*, so please make sure to adapt.
ROM images are included pre-compiled in libreboot. You can also dump
-your current firmware, using flashrom:\
-\$ **sudo flashrom -p internal -r libreboot.rom**\
+your current firmware, using flashrom:
+ $ sudo flashrom -p internal -r libreboot.rom
\# **flashrom -p internal -r libreboot.rom**\
If you are told to specify the chip, add the option **-c {your chip}**
to the command, for example:\
@@ -194,8 +194,8 @@ flash it.\
\$ **cd /libreboot\_util** \# **./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:\
-\# **./flash forceupdate libreboot.rom**\
+correct ROM image, then run this alternative command:
+ # ./flash forceupdate libreboot.rom
You should see **"Verifying flash\... VERIFIED."** written at the end
of the flashrom output. Once you have done that, shut down and then boot
up with your new test configuration.**