aboutsummaryrefslogtreecommitdiff
path: root/www/faq.md
diff options
context:
space:
mode:
authorLeah Rowe <info@minifree.org>2017-07-03 15:04:32 +0000
committerGogs <gogitservice@gmail.com>2017-07-03 15:04:32 +0000
commitf4e5c4bba4403d418044e8c3ed2dd3fbc6eb4c12 (patch)
treef8480b737e0a83785ec654ce048172d3aa6ad47d /www/faq.md
parent24411dc9f293c5dbfdf6750fffd94dc83844f135 (diff)
parentd3c2d28249cb051a1d97160f22357046380a81b1 (diff)
downloadlibrebootfr-f4e5c4bba4403d418044e8c3ed2dd3fbc6eb4c12.tar.gz
librebootfr-f4e5c4bba4403d418044e8c3ed2dd3fbc6eb4c12.zip
Merge branch 'cmdline-markup' of mreed/libreboot into master
Diffstat (limited to 'www/faq.md')
-rw-r--r--www/faq.md14
1 files changed, 7 insertions, 7 deletions
diff --git a/www/faq.md b/www/faq.md
index b0995b58..7da67885 100644
--- a/www/faq.md
+++ b/www/faq.md
@@ -14,10 +14,10 @@ What version of libreboot do I have?
Flashrom complains about DEVMEM access
--------------------------------------
-If running flashrom -p internal for software based flashing, and
+If running `flashrom -p internal` for software based flashing, and
you get an error related to /dev/mem access, you should reboot with
-iomem=relaxed kernel parameter before running flashrom, or use a kernel
-that has CONFIG\_STRICT\_DEVMEM not enabled.
+`iomem=relaxed` kernel parameter before running flashrom, or use a kernel
+that has `CONFIG\_STRICT\_DEVMEM` not enabled.
The backlight is darker on the left side of the screen when lowering the brightness on my X200/T400/T500/R400
---------------------------------------------------------------------------------------------------------------
@@ -37,11 +37,11 @@ both on the original BIOS and in libreboot. It's a quirk in the
hardware. On debian systems, a workaround is to restart the networking
service when you connect the ethernet cable:
- sudo service network-manager restart
+ $ sudo service network-manager restart
On Parabola, you can try:
- sudo systemctl restart network-manager
+ $ sudo systemctl restart network-manager
(the service name might be different for you, depending on your
configuration)
@@ -65,7 +65,7 @@ Libreboot-unstable (or git) now disables loading PCI option ROMs, but
previous releases with SeaGRUB (20160818-20160907) do not. You can work
around this by running the following command:
- ./cbfstool yourrom.rom add-int -i 0 -n etc/pci-optionrom-exec
+ $ ./cbfstool yourrom.rom add-int -i 0 -n etc/pci-optionrom-exec
You can find *cbfstool* in the \_util archive with the libreboot release
that you are using.
@@ -582,7 +582,7 @@ cases.
Libreboot locks the CMOS table, to ensure consistent functionality for
all users. You can use:
- nvramtool -C yourrom.rom -w somesetting=somevalue
+ $ nvramtool -C yourrom.rom -w somesetting=somevalue
This will change the default inside that ROM image, and then you can
re-flash it.