
P A R T I
C O N N E C T I N G T H E B O A R D
72
It’s highly unlikely that you’ll ever need to boot a Pi using the emergency kernel, but it’s
worth learning how to do so just in case. This is especially important if you’re upgrading your
kernel or are using a new and potentially poorly tested distribution. Sometimes, newly
released software can have
bugs
which aren’t spotted before its release. When encountering
strange errors after upgrading, the emergency kernel can be used to narrow down the prob-
lem to the new kernel version.
The Linux kernel is a single file located in the
/boot
directory called
kernel.img
. When
the Pi is first switched on and begins to load the operating system, it looks for this file, and if
the file is missing, the Pi won’t work. The emergency kernel is a second file, again in the
/
boot
directory, called
kernel_emergency.img
.
The emergency kernel is, in most cases, almost identical to the standard kernel. When
changes are made to the standard kernel, to boost performance or add new features for
example, the emergency kernel is left unaltered. This way, if the changes to the standard
kernel cause stability problems, a user can simply tell the Pi to load the emergency kernel
instead.
There are two ways to boot into the emergency kernel, and both require the use of a PC and
an SD card reader if the Pi can’t boot. Otherwise, the following steps can be carried out on
the Pi itself.
The easiest way to boot the emergency kernel is to rename the existing
kernel.img
file to
kernel.img.bak
, and then rename the
kernel_emergency.img
file to
kernel.img
.
When the Pi loads, it will now load the emergency kernel by default. To go back to the stan-
dard kernel, simply reverse the process: rename
kernel.img
to
kernel_emergency.img
and
kernel.img.bak
to
kernel.img
.
An alternative method to load the emergency kernel is to edit the
cmdline.xt
file (located
in the
/boot
directory) by adding the following entry at the end of the existing command
line:
kernel=kernel_emergency.img
This tells the Pi that it should load the kernel named
kernel_emergency.img
instead of
the usual
kernel.img
. Reversing the process is as simple as opening
cmdline.txt
again
and removing the entry.
You’ll learn more about
cmdline.txt
and how it affects the operation of the Raspberry Pi
in Chapter 7, “Advanced Raspberry Pi Configuration”.
Summary of Contents for A
Page 1: ......
Page 2: ......
Page 3: ...Raspberry Pi User Guide 2nd Edition...
Page 4: ......
Page 5: ...Raspberry Pi User Guide 2nd Edition Eben Upton and Gareth Halfacree...
Page 10: ......
Page 26: ...R A S P B E R R Y P I U S E R G U I D E S E C O N D E D I T I O N 10...
Page 28: ......
Page 29: ...Chapter 1 Meet the Raspberry Pi...
Page 37: ...Chapter 2 Getting Started with the Raspberry Pi...
Page 56: ......
Page 57: ...Chapter 3 Linux System Administration...
Page 79: ...Chapter 4 Troubleshooting...
Page 89: ...Chapter 5 Network Configuration...
Page 109: ...Chapter 6 The Raspberry Pi Software Configuration Tool...
Page 122: ......
Page 123: ...Chapter 7 Advanced Raspberry Pi Configuration...
Page 140: ......
Page 141: ...Chapter 8 The Pi as a Home Theatre PC...
Page 151: ...Chapter 9 The Pi as a Productivity Machine...
Page 160: ......
Page 161: ...Chapter 10 The Pi as a Web Server...
Page 172: ......
Page 173: ...Chapter 11 An Introduction to Scratch...
Page 189: ...Chapter 12 An Introduction to Python...
Page 216: ......
Page 218: ......
Page 219: ...Chapter 13 Learning to Hack Hardware...
Page 234: ......
Page 235: ...Chapter 14 The GPIO Port...
Page 249: ...Chapter 15 The Raspberry Pi Camera Module...
Page 265: ...Chapter 16 Add on Boards...
Page 280: ......
Page 281: ...Appendix A Python Recipes...
Page 287: ...Appendix B Raspberry Pi Camera Module Quick Reference...
Page 293: ...Appendix C HDMI Display Modes...