You are not logged in.

#1 2017-04-02 18:10:50

johanbcn
Member
Registered: 2010-01-03
Posts: 20

[Solved] How can I debug the boot process?

I just did a fresh install on a laptop, a Lenovo T430s, but i'm unable to boot on anything but the fallback ramdisk.

Using the default one, the process stops after the "Loading initial ramdisk" message; the system is still responsive, as I can CTRL+ALT+SUPR my way out, but no error is being shown on the output.
Removing the quiet parameter from the kernel doesn't show anything either, and no boot entry is being registered on systemd's journalctl.

The wiki doesn't provide any notes regarding installation on this laptop, but I have seen many posts from users asking unrelated questions, so I think that it should be working out of the box.

From what I have understood, the default ramdisk includes the minimum amount of kernel modules, and the fallback includes the complete set and an autodetect feature.

So I'm guessing some required module is missing from my mkinicpio configuration.

Which brings me to my question: How can I determine what's wrong or how can I find out the missing module?

Last edited by johanbcn (2017-04-06 08:20:17)

Offline

#2 2017-04-03 12:20:45

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: [Solved] How can I debug the boot process?

Can we have more info? What kind of machine (what video card, etc.). Are you trying to boot to a command prompt or a graphical interface? Since the system is responsive, can you switch to a terminal (Ctl+Alt_Fx...)?


Matt

"It is very difficult to educate the educated."

Offline

#3 2017-04-03 13:10:51

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,546
Website

Re: [Solved] How can I debug the boot process?

In addition to the above, please elaborate on this:

johanbcn wrote:

I can CTRL+ALT+SUPR my way out

Your way out of what?  Out to what?  By "SUPR" do you mean the Mod4/Windows key?  What is the result of that combination?


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#4 2017-04-03 22:44:39

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,892

Re: [Solved] How can I debug the boot process?

Your right arm he's using an azerty keyboard ;-)
https://upload.wikimedia.org/wikipedia/ … fr.svg.png

Offline

#5 2017-04-04 01:40:26

Docbroke
Member
From: India
Registered: 2015-06-13
Posts: 1,475

Re: [Solved] How can I debug the boot process?

johanbcn wrote:

Which brings me to my question: How can I determine what's wrong or how can I find out the missing module?

you can look here to find out all installed modules while using fallback initramfs
https://wiki.archlinux.org/index.php/Kernel_modules

or alternatively you can use same mkinitcpio configuration for your regular initramfs

Offline

#6 2017-04-04 05:59:05

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,892

Re: [Solved] How can I debug the boot process?

On topic:
Boot the fallback initramfs and run

grep HOOKS /etc/mkinitcpio.conf
lsmod
mount | grep boot
mkinitcpio -p linux

and post the outputs.

Offline

#7 2017-04-04 13:12:25

johanbcn
Member
Registered: 2010-01-03
Posts: 20

Re: [Solved] How can I debug the boot process?

My bad, with "CTRL+ALT+SUPR" I meant "CTRL+ALT+DEL" (force of habit, I use a QWERTY spanish keyboard), and with "CTRL+ALT+DEL my way out" I wanted to emphasize that the system isn't freezing but does not seem to respond to anything else but to reboot key combinations.

@seth Thanks, I'll post that info in a few hours when I get back to my laptop.
Anyways, I didn't change a single line of the default mkinitcpio configuration file, and no errors nor unusual warnings were output when building the images.

What I really want to know is that surely there must be a way to log or visualize (verbosely) what the boot manager or the kernel is doing, isn't there?

Last edited by johanbcn (2017-04-04 13:17:35)

Offline

#8 2017-04-04 15:11:09

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,546
Website

Re: [Solved] How can I debug the boot process?

johanbcn wrote:

... surely there must be a way to log or visualize (verbosely) what the boot manager or the kernel is doing, isn't there?

There are several approaches but it really depends on what we're dealing with.  That is why so far in this thread every post has been seeking more information, like the following:

mrunion wrote:

Are you trying to boot to a command prompt or a graphical interface? Since the system is responsive, can you switch to a terminal (Ctl+Alt_Fx...)?

Please answer these questions so we know how to best help you - otherwise it's all just random guess and check which is never productive.

Assuming you are booting to a graphical interface, don't.  Boot to multi-user.target.  If that doesn't prove useful, add 'nomodeset' to the kernel line.  There are many other things that could be done - but again, we really need to know where we're starting from.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#9 2017-04-05 01:42:18

Blasphemist
Member
From: Colorado
Registered: 2013-01-17
Posts: 160

Re: [Solved] How can I debug the boot process?

The boot process section of this page in the wiki may be what you are asking for.
https://wiki.archlinux.org/index.php/Ge … leshooting


Simple and Open

Offline

#10 2017-04-06 08:27:26

johanbcn
Member
Registered: 2010-01-03
Posts: 20

Re: [Solved] How can I debug the boot process?

Well, finally after configuring the bios to boot exclusively in efi mode (with legacy support disabled) I was able to see an error message and got a prompt:

EXT4-fs (sda1): Cannot load crc32c driver

I don't know (yet) why it requires this driver, but surely adding the crc32c_generic and crc32c-intel (as I'm using an Intel CPU) modules to the mkinitcpio configuration and rebuilding the images fixed the issue.

Last edited by johanbcn (2017-04-06 08:28:33)

Offline

Board footer

Powered by FluxBB