Hardware Reference
In-Depth Information
[0.000000] Linux version 3.10.38 (wwg@osx-xpi) \
(gcc version 4.8.2 20130603 (prerelease) \
(crosstool −NG 1.19.0)) \
#3 PREEMPT Mon Jun 23 22:26:50 EST 2014
...
Here we have confirmation that the kernel was built by
wwg@osx-xpi
(on VirtualBox),
using the crosstool-NG development tools and built on June 23. This is confirmation
that the kernel is the new one that was installed. Next, of course, the modules need to be
installed.
Boot Failure
If you see the initial colored flash screen remain on the console, this indicates that the
kernel.img
file failed to load/start.
43
Modules
The modules need to be staged somewhere, so you can transfer them to the Pi's root
file system (on the SD card). Here I'll stage them in
~/work/modules
. Specify the full
pathname to the
staging
directory by using the
INSTALL_MOD_PATH
variable:
$ mkdir −p ~/work/modules
$ make INSTALL_MOD_PATH=$HOME/work/modules modules_install
Note that
$HOME
is safer than the tilde (
~
) in the
make
command, since the shell may
not substitute it properly. The bash shell, version 4.3.8, does seem to handle the tilde,
however.
After this install step completes, you will have a subtree of kernel modules deposited
there. These files now need to be installed in the Pi's root file system. Either mount the
Pi's root file system under Linux, or use the existing kernel on the Pi itself. The following
shows how the modules are put into a tar file for transport to the Pi:
$ cd ~/work/modules
$ tar czf modules.tar.gz .
$ tar tzf modules.tar.gz | head −4
. /
. /modules.tar.gz
. /lib/
. /lib/modules/
$ scp modules.tar.gz pi@rasp:.
