So I thought it would be a GRUB problem, because if I use the grub shell
with following commands, I can actually boot into the new kernel:
set prefix=(hd0,msdos1)/grub/
set root=(hd0,msdos3)
insmod linux
insmod normal
normal
And then choose to boot the newly created entry.
So ok, but here are a few more information.
/etc/fstab:
/dev/sda1 /boot ext4 defaults 0 2 --->
UUID = 0aabf45f-9868-471f-bda2-8d7501983048
/dev/sda3 / ext4 defaults 0 1 --->
UUID = 42eea483-72a2-4bf6-8491-8bfd63e8fc87
/dev/sda2 none swap sw 0 0
/dev/sda4 /home ext4 defaults 0 0
And my /boot/grub/grub.cfg (main part I guess):
menuentry 'Gentoo GNU/Linux' --class gentoo --class gnu-linux --class
gnu --class os $menuentry_id_option
'gnulinux-simple-42eea483-72a2-4bf6-8491-8bfd63e8fc87' {
load_video
if [ "x$grub_platform" = xefi ]; then
set gfxpayload=keep
fi
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1
--hint-baremetal=ahci0,msdos1 0aabf45f-9868-471f-bda2-8d7501983048
else
search --no-floppy --fs-uuid --set=root
0aabf45f-9868-471f-bda2-8d7501983048
fi
echo 'Linux x86_64-4.1.12-gentoo wird geladen …'
linux /kernel-genkernel-x86_64-4.1.12-gentoo
root=UUID=42eea483-72a2-4bf6-8491-8bfd63e8fc87 ro
echo 'Initiale Ramdisk wird geladen …'
initrd /initramfs-genkernel-x86_64-4.1.12-gentoo
}
It is now kernel 4.1.12, because I experimented a little bit.
Am 22.03.2016 um 11:34 schrieb Neil Bothwick:
On Tue, 22 Mar 2016 11:20:46 +0100, Dennis Tants wrote:
I was runnig with 4.0.5, the latest is of course 4.1.15-r1. So I
decided to upgrade my kernel. I started with eselect kernel set
4.1.15-r1 (the number for it). Then 'cd /usr/src/linux/ && make
menuconfig'. I sorted out a few filesystems I didn't need, but thats
all. After I saved the .config file, I did 'make && make
modules_install && make install' like it is written in the handbook.
Last but not least I wanted to create a new GRUB entry with
'grub2-mkconfig -o /boot/grub/grub.cfg'. I thought I did all steps but
after a reboot, I ran into a kernel panic (Not syncing rootfs, IIRC).
Following a tutorial to be able to boot again, I had a look at my
grub.cfg.
A kernel panic means the kernel has loaded, which means GRUB has done its
job and it now out of the way. The error means either you haven't
included a necessary filesystem or device drive in the kernel (not as a
module) or you have given the wrong root device name to the kernel
Yes the GRUB2 config files are longer, but the only part you need to be
concerned with is the menuentry section you are booting, most of the
preamble is distro-agnostic housekeeping.
Can you post the relevant part of grub.cfg (or the whole thing if you're
not sure) and details of your hard disk layout (filesystems used, which
partition does what etc).
--
Dennis Tants
Auszubildender: Fachinformatiker für Systemintegration
ZARM - Zentrum für angewandte Raumfahrttechnologie und Mikrogravitation
ZARM - Center of Applied Space Technology and Microgravity
Universität Bremen
Am Fallturm
28359 Bremen, Germany
Telefon: 57940
E-Mail: dennis.ta...@zarm.uni-bremen.de
www.zarm.uni-bremen.de
