English Portuguese (Brazil)
After installing a new kernel with [command]#rpm#, verify that `/boot/grub2/grub.cfg` is correct and reboot the computer into the new kernel. Ensure your hardware is detected by watching the boot process output. If GRUB 2 presents an error and is unable to boot into the new kernel, it is often easiest to try to boot into an alternative or older kernel so that you can fix the problem. Alternatively, use the boot media you created earlier to boot the system.
Alternatively, on systems with a floppy drive, you can create a boot diskette by installing the [package]*mkbootdisk* package and running the [command]#mkbootdisk# command as `root`. See [command]#man mkbootdisk# man page after installing the package for usage information.
Among various code snippets and directives, the `/boot/grub2/grub.cfg` configuration file contains one or more `menuentry` blocks, each representing a single GRUB 2 boot menu entry. These blocks always start with the `menuentry` keyword followed by a title, list of options, and opening curly bracket, and end with a closing curly bracket. Anything between the opening and closing bracket should be indented. For example, the following is a sample `menuentry` block for Fedora 21 with Linux kernel 3.17.6-300.fc21.x86_64:
an `initramfs` file matching our kernel version, `initramfs-3.17.7-300.fc21.x86_64.img`, also exists.
|Architecture|Boot Loader|See
|x86|GRUB 2|xref:Manually_Upgrading_the_Kernel.adoc#s3-kernel-boot-loader-grub[Configuring the GRUB 2 Boot Loader]
|AMD AMD64 *or* Intel 64|GRUB 2|xref:Manually_Upgrading_the_Kernel.adoc#s3-kernel-boot-loader-grub[Configuring the GRUB 2 Boot Loader]
|IBM eServer System i|OS/400|xref:Manually_Upgrading_the_Kernel.adoc#s2-kernel-boot-loader-iseries[Configuring the OS/400 Boot Loader]
|IBM eServer System p|YABOOT|xref:Manually_Upgrading_the_Kernel.adoc#s2-kernel-boot-loader-pseries[Configuring the YABOOT Boot Loader]
|IBM System z|z/IPL|—
As `root`, issue the command [command]#cat /proc/iSeries/mf/side# to determine the default side (either A, B, or C).
As `root`, issue the following command, where _kernel-version_ is the version of the new kernel and _side_ is the side from the previous command:
As `root`, list the contents in the `/boot/` directory and find the kernel (`vmlinuz-_kernel_version_pass:attributes[{blank}]`) and `initramfs-_kernel_version_pass:attributes[{blank}]` with the latest (most recent) version number:
At a shell prompt, change to the directory that contains the kernel RPM packages. Use [option]`-i` argument with the [command]#rpm# command to keep the old kernel. Do *not* use the [option]`-U` option, since it overwrites the currently installed kernel, which creates boot loader problems. For example:
Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.
Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.
boot=/dev/sda1 init-message=Welcome to {MAJOROS}! Hit <TAB> for boot options
partition=2 timeout=30 install=/usr/lib/yaboot/yaboot delay=10 nonvram
Boot loaders by architecture
Causing the GRUB 2 boot menu to display
[command]#dd if=/boot/vmlinitrd-_kernel-version_ of=/proc/iSeries/mf/pass:attributes[{blank}]_side_pass:attributes[{blank}]/vmlinux bs=8k#
[command]#grub2-mkconfig# [option]`-o` [option]`/boot/grub2/grub.cfg`
[command]#ls -l /boot/#
Configuring the GRUB 2 Boot Loader
Configuring the OS/400 Boot Loader
Configuring the YABOOT Boot Loader