Lines Matching refs:kernel
1 Linux kernel release 4.x <http://kernel.org/>
5 kernel, and what to do if something goes wrong.
34 Linux has also been ported to itself. You can now run the kernel as a
47 these typically contain kernel-specific installation notes for some
51 your kernel.
54 kernel developers and users. These guides can be rendered in a
59 INSTALLING the kernel source:
61 - If you install the full sources, put the kernel tarball in a
67 Replace "X" with the version number of the latest kernel.
70 incomplete) set of kernel headers that are used by the library header
72 whatever the kernel-du-jour happens to be.
76 newer patch files, enter the top level directory of the kernel source
89 directly to the base 4.x kernel. For example, if your base kernel is 4.0
91 and 4.0.2 patches. Similarly, if you are running kernel version 4.0.2 and
96 Alternatively, the script patch-kernel can be used to automate this
97 process. It determines the current kernel version and applies any
100 linux/scripts/patch-kernel linux
103 kernel source. Patches are applied from the current directory, but
124 BUILD directory for the kernel:
126 When compiling the kernel, all output files will per default be
127 stored together with the kernel source code.
132 kernel source code: /usr/src/linux-4.X
133 build directory: /home/name/build/kernel
135 To configure and build the kernel, use:
138 make O=/home/name/build/kernel menuconfig
139 make O=/home/name/build/kernel
140 sudo make O=/home/name/build/kernel modules_install install
145 CONFIGURING the kernel:
223 You can find more information on using the Linux kernel config tools
228 - Having unnecessary drivers will make the kernel bigger, and can
232 - Compiling the kernel with "Processor type" set higher than 386
233 will result in a kernel that does NOT work on a 386. The
234 kernel will detect this on bootup, and give up.
236 - A kernel with math-emulation compiled in will still use the
238 never get used in that case. The kernel will be slightly larger,
242 - The "kernel hacking" configuration details usually result in a
243 bigger or slower kernel (or both), and can even make the kernel
245 break bad code to find kernel problems (kmalloc()). Thus you
249 COMPILING the kernel:
254 Please note that you can still run a.out user programs with this kernel.
256 - Do a "make" to create a compressed kernel image. It is also
258 kernel makefiles, but you may want to check your particular lilo setup first.
263 - If you configured any of the parts of the kernel as `modules', you
266 - Verbose kernel compile/build output:
268 Normally, the kernel build system runs in a fairly quiet mode (but not
269 totally silent). However, sometimes you or other kernel developers need
279 - Keep a backup kernel handy in case something goes wrong. This is
282 backup of the modules corresponding to that kernel, as well. If you
283 are installing a new kernel with the same version number as your
284 working kernel, make a backup of your modules directory before you
287 Alternatively, before compiling, use the kernel config option
288 "LOCALVERSION" to append a unique suffix to the regular kernel version.
291 - In order to boot your new kernel, you'll need to copy the kernel
293 to the place where your regular bootable kernel is found.
295 - Booting a kernel directly from a floppy without the assistance of a
299 uses the kernel image as specified in the file /etc/lilo.conf. The
300 kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
301 /boot/bzImage. To use the new kernel, save a copy of the old image
304 the new kernel image.
308 old kernel image (say, /vmlinux.old) in case the new one does not
315 ramdisk size, etc. in the kernel image, use the 'rdev' program (or
317 recompile the kernel to change these parameters.
319 - Reboot with the new kernel and enjoy.
323 - If you have problems that seem to be due to kernel bugs, please check
325 with the part of the kernel that you are having trouble with. If there
330 - In all bug-reports, *please* tell what kernel you are talking about,
337 unable to handle kernel paging request at address C0000010
346 or similar kernel debugging information on your screen or in your
350 important: it tells something about why the kernel dumped code (in
351 the above example, it's due to a bad kernel pointer). More information
354 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
358 ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/ .
364 kernel setup. What you should do is take the hex value from the EIP
365 line (ignore the "0010:"), and look it up in the kernel namelist to
366 see which kernel function contains the offending address.
368 To find out the kernel function name, you'll need to find the system
369 binary associated with the kernel that exhibited the symptom. This is
371 the EIP from the kernel crash, do:
375 This will give you a list of kernel addresses sorted in ascending
377 offending address. Note that the address given by the kernel
381 point of each kernel function, so by looking for the function that
389 kernel image or similar), telling me as much about your setup as
392 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
394 kernel with -g; edit arch/i386/Makefile appropriately, then do a "make
397 After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".
402 gdb'ing a non-running kernel currently fails because gdb (wrongly)
403 disregards the starting offset for which the kernel is compiled.