Arch Linux

dmg1337

Member

Registered: 2019-01-28

Posts: 13

Stuck during load - up after installing a new kernel

I am running the machine on VMware workstation 14 Player with arch rolling release running(I think up to date, I just pacman -Syu earlier). I tried to install a custom kernel by the guide in wiki https://wiki.archlinux.org/index.php/Ke … ompilation , with stock config and some of the debug options (symbols, and kdgb support), and machine is stuck on the Loading initial ramdisk phase. I am able to chroot into the old system with a live os disk, but I haven't been able to find the source of the problem, and therefore fix it. Note: I am using this system to develop loadable kernel module(a thin hypervisor), so I triple\double faulted it a lot of times, before the kernel update. I don`t think it should really because the lkm is not loaded(maybe net console is) when booting up, but I still thought it was best to let you know. If anyone has any idea on how to debug this problem/solve it I will be happy and grateful to hear.

dmg1337

Member

Registered: 2019-01-28

Posts: 13

Re: Stuck during load - up after installing a new kernel

Anyone ? I can always clean install a new os, but it seems like a drastic measure. There is no way, to isolate from where the error during the boot is happening, and fix it ?

bugsmanagement

Member

Registered: 2017-04-21

Posts: 201

Re: Stuck during load - up after installing a new kernel

Hello there,

Out of curiosity, what boot-loader are you using? By any chance, are suppressing kernel output via kernel command line? Eg, quiet? Have a look at https://github.com/torvalds/linux/blob/ … meters.txt for additional parameters you might be able to use to help diagnose it.

Regards

dmg1337

Member

Registered: 2019-01-28

Posts: 13

Re: Stuck during load - up after installing a new kernel

Hello there,

Out of curiosity, what boot-loader are you using? By any chance, are suppressing kernel output via kernel command line? Eg, quiet? Have a look at https://github.com/torvalds/linux/blob/ … meters.txt for additional parameters you might be able to use to help diagnose it.

Regards

I am using grub, right now my grub_cmdline_linux_default  is: netconsole:... loglevel=7 early_printk=efi. In other words no quiet (before I got the crash I had quiet there, but I saw on some thread to add this options(loglevel and early_printk and remove quiet, to see more debug messages to debug the boot) .