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). -- Neil Bothwick "There are no stupid questions, just too many inquisitive idiots."
pgp9J043TCdos.pgp
Description: OpenPGP digital signature
