View previous topic :: View next topic |
Author |
Message |
chrisk2305 Tux's lil' helper
Joined: 05 Sep 2007 Posts: 110
|
Posted: Thu Dec 06, 2018 6:29 pm Post subject: UEFI Boot stuck at "Loading Linux 4.14.xx" |
|
|
Hi,
I am currently facing the problem that my system is stuck at "Loading Linux" without any error message. So Grub2 is loading fine but the Kernel decompression won't even start. Grub.cfg looks fine to me. So it seems that there is an access problem to the Kernel itself. I did all according to the manual but no avail. Also made a backup, recreated all the paritions including the ESP which is vFAT formatted, etc.
Disk Layout:
Code: |
root@sysresccd /mnt/gentoo % parted /dev/nvme0n1
GNU Parted 3.2
Using /dev/nvme0n1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: NVMe Device (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 3146kB 2097kB grub bios_grub
2 3146kB 540MB 537MB fat32 boot boot, esp
3 540MB 1077MB 537MB linux-swap(v1) swap
4 1077MB 500GB 499GB ext4 rootfs
|
fstab:
Code: |
/dev/nvme0n1p2 /boot vfat noatime,noauto 1 2
/dev/nvme0n1p4 / ext4 noatime,commit=120 0 1
/dev/nvme0n1p3 none swap sw,pri=1 0 0
|
grub.cfg
Code: |
root@sysresccd /mnt/gentoo % cat boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root 3e13a553-8e74-4cf0-831a-3346968e6ec8
else
search --no-floppy --fs-uuid --set=root 3e13a553-8e74-4cf0-831a-3346968e6ec8
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Gentoo GNU/Linux' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
load_video
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root D4DA-516D
else
search --no-floppy --fs-uuid --set=root D4DA-516D
fi
echo 'Loading Linux 4.19.7-gentoo ...'
linux /vmlinuz-4.19.7-gentoo root=/dev/nvme0n1p4 ro init=/usr/lib/systemd/systemd bonding.mode=4 bonding.miimon=100
}
submenu 'Advanced options for Gentoo GNU/Linux' $menuentry_id_option 'gnulinux-advanced-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
menuentry 'Gentoo GNU/Linux, with Linux 4.19.7-gentoo' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.7-gentoo-advanced-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
load_video
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root D4DA-516D
else
search --no-floppy --fs-uuid --set=root D4DA-516D
fi
echo 'Loading Linux 4.19.7-gentoo ...'
linux /vmlinuz-4.19.7-gentoo root=/dev/nvme0n1p4 ro init=/usr/lib/systemd/systemd bonding.mode=4 bonding.miimon=100
}
menuentry 'Gentoo GNU/Linux, with Linux 4.19.7-gentoo (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.7-gentoo-recovery-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
load_video
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root D4DA-516D
else
search --no-floppy --fs-uuid --set=root D4DA-516D
fi
echo 'Loading Linux 4.19.7-gentoo ...'
linux /vmlinuz-4.19.7-gentoo root=/dev/nvme0n1p4 ro single init=/usr/lib/systemd/systemd bonding.mode=4 bonding.miimon=100
}
menuentry 'Gentoo GNU/Linux, with Linux 4.14.86-gentoo' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.14.86-gentoo-advanced-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
load_video
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root D4DA-516D
else
search --no-floppy --fs-uuid --set=root D4DA-516D
fi
echo 'Loading Linux 4.14.86-gentoo ...'
linux /vmlinuz-4.14.86-gentoo root=/dev/nvme0n1p4 ro init=/usr/lib/systemd/systemd bonding.mode=4 bonding.miimon=100
}
menuentry 'Gentoo GNU/Linux, with Linux 4.14.86-gentoo (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.14.86-gentoo-recovery-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
load_video
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root D4DA-516D
else
search --no-floppy --fs-uuid --set=root D4DA-516D
fi
echo 'Loading Linux 4.14.86-gentoo ...'
linux /vmlinuz-4.14.86-gentoo root=/dev/nvme0n1p4 ro single init=/usr/lib/systemd/systemd bonding.mode=4 bonding.miimon=100
}
menuentry 'Gentoo GNU/Linux, with Linux 4.14.85-gentoo' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.14.85-gentoo-advanced-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
load_video
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root D4DA-516D
else
search --no-floppy --fs-uuid --set=root D4DA-516D
fi
echo 'Loading Linux 4.14.85-gentoo ...'
linux /vmlinuz-4.14.85-gentoo root=/dev/nvme0n1p4 ro init=/usr/lib/systemd/systemd bonding.mode=4 bonding.miimon=100
}
menuentry 'Gentoo GNU/Linux, with Linux 4.14.85-gentoo (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.14.85-gentoo-recovery-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
load_video
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root D4DA-516D
else
search --no-floppy --fs-uuid --set=root D4DA-516D
fi
echo 'Loading Linux 4.14.85-gentoo ...'
linux /vmlinuz-4.14.85-gentoo root=/dev/nvme0n1p4 ro single init=/usr/lib/systemd/systemd bonding.mode=4 bonding.miimon=100
}
menuentry 'Gentoo GNU/Linux, with Linux 4.14.85-gentoo.old' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.14.85-gentoo.old-advanced-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
load_video
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root D4DA-516D
else
search --no-floppy --fs-uuid --set=root D4DA-516D
fi
echo 'Loading Linux 4.14.85-gentoo.old ...'
linux /vmlinuz-4.14.85-gentoo.old root=/dev/nvme0n1p4 ro init=/usr/lib/systemd/systemd bonding.mode=4 bonding.miimon=100
}
menuentry 'Gentoo GNU/Linux, with Linux 4.14.85-gentoo.old (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.14.85-gentoo.old-recovery-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
load_video
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root D4DA-516D
else
search --no-floppy --fs-uuid --set=root D4DA-516D
fi
echo 'Loading Linux 4.14.85-gentoo.old ...'
linux /vmlinuz-4.14.85-gentoo.old root=/dev/nvme0n1p4 ro single init=/usr/lib/systemd/systemd bonding.mode=4 bonding.miimon=100
}
menuentry 'Gentoo GNU/Linux, with Linux 4.14.76-gentoo' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.14.76-gentoo-advanced-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
load_video
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root D4DA-516D
else
search --no-floppy --fs-uuid --set=root D4DA-516D
fi
echo 'Loading Linux 4.14.76-gentoo ...'
linux /vmlinuz-4.14.76-gentoo root=/dev/nvme0n1p4 ro init=/usr/lib/systemd/systemd bonding.mode=4 bonding.miimon=100
}
menuentry 'Gentoo GNU/Linux, with Linux 4.14.76-gentoo (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.14.76-gentoo-recovery-3e13a553-8e74-4cf0-831a-3346968e6ec8' {
load_video
insmod gzio
insmod part_gpt
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root D4DA-516D
else
search --no-floppy --fs-uuid --set=root D4DA-516D
fi
echo 'Loading Linux 4.14.76-gentoo ...'
linux /vmlinuz-4.14.76-gentoo root=/dev/nvme0n1p4 ro single init=/usr/lib/systemd/systemd bonding.mode=4 bonding.miimon=100
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
|
Content of boot folder:
Code: |
root@sysresccd /mnt/gentoo/boot % ls -la
total 34100
drwxr-xr-x 5 root root 4096 Jan 1 1970 .
drwxr-xr-x 23 root root 4096 Dec 6 14:56 ..
-rwxr-xr-x 1 root root 107119 Dec 5 20:19 config-4.14.85-gentoo
-rwxr-xr-x 1 root root 107119 Dec 5 19:23 config-4.14.85-gentoo.old
-rwxr-xr-x 1 root root 107119 Dec 6 09:58 config-4.14.86-gentoo
-rwxr-xr-x 1 root root 108376 Dec 6 17:18 config-4.19.7-gentoo
drwxr-xr-x 4 root root 4096 Dec 6 17:35 EFI
drwxr-xr-x 7 root root 4096 Dec 6 18:56 grub
drwxr-xr-x 5 root root 4096 Dec 5 19:09 old
-rwxr-xr-x 1 root root 2686762 Dec 5 20:19 System.map-4.14.85-gentoo
-rwxr-xr-x 1 root root 2478049 Dec 5 19:23 System.map-4.14.85-gentoo.old
-rwxr-xr-x 1 root root 2687507 Dec 6 09:58 System.map-4.14.86-gentoo
-rwxr-xr-x 1 root root 2776227 Dec 6 17:18 System.map-4.19.7-gentoo
-rwxr-xr-x 1 root root 4395056 Oct 15 14:09 vmlinuz-4.14.76-gentoo
-rwxr-xr-x 1 root root 4911168 Dec 5 20:19 vmlinuz-4.14.85-gentoo
-rwxr-xr-x 1 root root 4395072 Dec 5 19:23 vmlinuz-4.14.85-gentoo.old
-rwxr-xr-x 1 root root 4911168 Dec 6 09:58 vmlinuz-4.14.86-gentoo
-rwxr-xr-x 1 root root 5189792 Dec 6 17:18 vmlinuz-4.19.7-gentoo
|
Board is a ASUS C246 WS with Intel Xeon 2126G CPU with integrated Graphics.
Do you guys have a clue what I did wrong? Thanks in advance!
Chris |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54300 Location: 56N 3W
|
Posted: Thu Dec 06, 2018 6:51 pm Post subject: |
|
|
chrisk2305,
I'll nit pick a bit before I offer help.
The Code: | Loading Linux 4.19.7-gentoo ... | is displayed by grub just before it actually loads the kernel.
You cannot infer from the last message displayed by grub that nothing else is happening.
I suspect that you don't have a console driver configured in your kernel, or not one that the kernel can use, so lots is happening but you can't see it.
Indeed everything might be working normally, except the console.
If you have sshd configured and runnnig, can you log in over ssh from another system?
Code: | root=/dev/nvme0n1p4 | That's interesting. I suspect that the NVME support is off in your kernel too.
So you have no working console, and the kernel panics when it tries to mount root.
We had one like this the other day :)
Please post the output of so we can see your hardware and put your kernel .config onto a pastebin site.
The .config is far too big to fit into a post. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
chrisk2305 Tux's lil' helper
Joined: 05 Sep 2007 Posts: 110
|
Posted: Thu Dec 06, 2018 7:25 pm Post subject: |
|
|
Thanks for the fast reply. This is a system that was perfectly fine on the previous hardware (Supermicro C236 Board) and has survived over the last 10 years
SSH is not working.
NVMe support is enabled. Here is the config file:
http://pasted.co/b15f4e4a
lspci:
Code: |
root@sysresccd /root % lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3ec6] (rev 07)
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e96]
Subsystem: ASUSTeK Computer Inc. Device [1043:8782]
Kernel modules: i915
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:a36d] (rev 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: xhci_hcd
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:a36f] (rev 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:a360] (rev 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Device [8086:a352] (rev 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: ahci
00:1b.0 PCI bridge [0604]: Intel Corporation Device [8086:a340] (rev f0)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1b.4 PCI bridge [0604]: Intel Corporation Device [8086:a32c] (rev f0)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:a338] (rev f0)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:a330] (rev f0)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.2 PCI bridge [0604]: Intel Corporation Device [8086:a332] (rev f0)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a309] (rev 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:8777]
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:a324] (rev 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (7) I219-LM [8086:15bb] (rev 10)
Subsystem: ASUSTeK Computer Inc. Ethernet Connection (7) I219-LM [1043:8686]
Kernel driver in use: e1000e
Kernel modules: e1000e
02:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd Device [144d:a808]
Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
Kernel driver in use: nvme
Kernel modules: nvme
05:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03)
Subsystem: ASUSTeK Computer Inc. I210 Gigabit Network Connection [1043:8557]
Kernel driver in use: igb
Kernel modules: igb
|
Note that I also tried this on another Board and therefore the lspci is from an ASUS Board and not Supermicro.
Edit: I changed UEFI boot to legacy because I was troubleshooting a different issue at that time and now I wanted to switch back to UEFI. Did everything according to latest manual. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54300 Location: 56N 3W
|
Posted: Thu Dec 06, 2018 8:12 pm Post subject: |
|
|
chrisk2305,
Pleas add Code: | # CONFIG_FB_EFI is not set
# CONFIG_FB_SIMPLE is not set
# CONFIG_DRM_I915 is not set | to your kernel.
They should all produce a framebuffer console on your hardware. The kernel will pick the one it likes best.
Your lspci shows
Code: | 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e96]
Subsystem: ASUSTeK Computer Inc. Device [1043:8782]
Kernel modules: i915 |
I'm not sure if i915 needs firmware with your system or not.
dmesg will tell you all about it though.
Is this kernel running in a VMWare guest?
It has the VMWare DRM options on.
This won't fix it but it should get some more diagnostics. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
chrisk2305 Tux's lil' helper
Joined: 05 Sep 2007 Posts: 110
|
Posted: Fri Dec 07, 2018 8:11 am Post subject: |
|
|
Hey Neddy,
Thanks for your support. After enabling the i915 options you mentioned this indeed helped me a lot. System booted just fine on the ASUS Board with iGFX.
On the Supermicro Board boot process was again stuck after less than a second. I then tried to disable modesetting in Grub and then the System could boot.
I am just wondering if this is a BIOS issue with Supermicro or something I can troubleshoot myself. Strangely on the ASUS Board modesetting works just fine and I have the shell in native resolution (both Intel C246 chipset with new Xeon 2126G).
Kernel is running on physical machine, no VMware - that may be just some leftovers from the past. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54300 Location: 56N 3W
|
Posted: Fri Dec 07, 2018 6:55 pm Post subject: |
|
|
chrisk2305,
You may get some hints from dmesg.
Also the system may boot without a console when you don't pass nomodeset but you won't be able to tell unless you enable sshd and log in remotely.
That would be a dmesg worth having. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
|