Lines Matching full:kernel
3 Linux kernel release 5.x <http://kernel.org/>
8 kernel, and what to do if something goes wrong.
39 Linux has also been ported to itself. You can now run the kernel as a
53 these typically contain kernel-specific installation notes for some
57 your kernel.
59 Installing the kernel source
62 - If you install the full sources, put the kernel tarball in a
68 Replace "X" with the version number of the latest kernel.
71 incomplete) set of kernel headers that are used by the library header
73 whatever the kernel-du-jour happens to be.
77 newer patch files, enter the top level directory of the kernel source
90 directly to the base 5.x kernel. For example, if your base kernel is 5.0
92 and 5.0.2 patches. Similarly, if you are running kernel version 5.0.2 and
97 Alternatively, the script patch-kernel can be used to automate this
98 process. It determines the current kernel version and applies any
101 linux/scripts/patch-kernel linux
104 kernel source. Patches are applied from the current directory, but
126 Build directory for the kernel
129 When compiling the kernel, all output files will per default be
130 stored together with the kernel source code.
135 kernel source code: /usr/src/linux-5.x
136 build directory: /home/name/build/kernel
138 To configure and build the kernel, use::
141 make O=/home/name/build/kernel menuconfig
142 make O=/home/name/build/kernel
143 sudo make O=/home/name/build/kernel modules_install install
148 Configuring the kernel
222 "make kvmconfig" Enable additional options for kvm guest kernel support.
224 "make xenconfig" Enable additional options for xen dom0 guest kernel
227 "make tinyconfig" Configure the tiniest possible kernel.
229 You can find more information on using the Linux kernel config tools
234 - Having unnecessary drivers will make the kernel bigger, and can
238 - A kernel with math-emulation compiled in will still use the
240 never get used in that case. The kernel will be slightly larger,
244 - The "kernel hacking" configuration details usually result in a
245 bigger or slower kernel (or both), and can even make the kernel
247 break bad code to find kernel problems (kmalloc()). Thus you
251 Compiling the kernel
257 Please note that you can still run a.out user programs with this kernel.
259 - Do a ``make`` to create a compressed kernel image. It is also
261 kernel makefiles, but you may want to check your particular lilo setup first.
266 - If you configured any of the parts of the kernel as ``modules``, you
269 - Verbose kernel compile/build output:
271 Normally, the kernel build system runs in a fairly quiet mode (but not
272 totally silent). However, sometimes you or other kernel developers need
282 - Keep a backup kernel handy in case something goes wrong. This is
285 backup of the modules corresponding to that kernel, as well. If you
286 are installing a new kernel with the same version number as your
287 working kernel, make a backup of your modules directory before you
290 Alternatively, before compiling, use the kernel config option
291 "LOCALVERSION" to append a unique suffix to the regular kernel version.
294 - In order to boot your new kernel, you'll need to copy the kernel
296 to the place where your regular bootable kernel is found.
298 - Booting a kernel directly from a floppy without the assistance of a
302 uses the kernel image as specified in the file /etc/lilo.conf. The
303 kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
304 /boot/bzImage. To use the new kernel, save a copy of the old image
307 the new kernel image.
311 old kernel image (say, /vmlinux.old) in case the new one does not
318 ramdisk size, etc. in the kernel image, use the ``rdev`` program (or
320 recompile the kernel to change these parameters.
322 - Reboot with the new kernel and enjoy.
327 - If you have problems that seem to be due to kernel bugs, please check
329 with the part of the kernel that you are having trouble with. If there
334 - In all bug-reports, *please* tell what kernel you are talking about,
341 unable to handle kernel paging request at address C0000010
350 or similar kernel debugging information on your screen or in your
354 important: it tells something about why the kernel dumped code (in
355 the above example, it's due to a bad kernel pointer). More information
358 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
362 https://www.kernel.org/pub/linux/utils/kernel/ksymoops/ .
368 kernel setup. What you should do is take the hex value from the EIP
369 line (ignore the ``0010:``), and look it up in the kernel namelist to
370 see which kernel function contains the offending address.
372 To find out the kernel function name, you'll need to find the system
373 binary associated with the kernel that exhibited the symptom. This is
375 the EIP from the kernel crash, do::
379 This will give you a list of kernel addresses sorted in ascending
381 offending address. Note that the address given by the kernel
385 point of each kernel function, so by looking for the function that
393 kernel image or similar), telling me as much about your setup as
397 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
399 kernel with -g; edit arch/x86/Makefile appropriately, then do a ``make
402 After you've rebooted with the new kernel, do ``gdb vmlinux /proc/kcore``.
407 gdb'ing a non-running kernel currently fails because ``gdb`` (wrongly)
408 disregards the starting offset for which the kernel is compiled.