You are not logged in.
Hi everyone,
I've got a strange problem, but I don't know where it came from.
It's almost two weeks I'm suffering it and I thougt it was related to the kernel I was using (-ck), but today I tried with the stock one and I've got the same problem.
I'm using Grub2 and, right after choosing the entry the system is stuck for almost two minutes. Then it boot.
Removing the "quiet" option I saw it "pause" when on display I've got the message: Running early hooks [udev]
How can I know what's wrong?
Thanks
Offline
Damn, no reply to this threat yet. I have exactly the same problem. I have to measure how long the system is stuck at the "::Running early hooks [udev]" but it's definately more than a minute.
Offline
Have you run pacman -Syu and replaced udev with the new systemd-tools - also it may be wise after doing that to run mkinitcpio -p linux and then grub-mkconfig -o /boot/grub/grub.cfg
See the following announcement:
Our enemies are your enemies, Nick. Disorder, war. It's just a matter of time before a dirty bomb goes off in Moscow, or an EMP fries Chicago. --- Alexander Pierce, Captain America: Winter Soldier
Access Denied! De-cryption failed, override denied all files sealed! --- Triskelion, Shield OS
-----
How to ask questions the smart way
Offline
I have 'microcode' in my initramfs (the modules loaded via initramfs are the ones listed in mkinitcpio.conf in MODULES= right?). Do you have any idea how to debug and find out the cause of the problem?
Offline
I have 'microcode' in my initramfs (the modules loaded via initramfs are the ones listed in mkinitcpio.conf in MODULES= right?). Do you have any idea how to debug and find out the cause of the problem?
That's my point. Remove it. It doesn't belong there.
Longer explanation: The microcode module is nothing but a firmware loader. Contrary to the design of most other modules which will not request firmware on module initialization, the microcode module intentionally does block and wait for firmware. Recent udev assumes that modules are well behaved (aka not calling request_firmware during module initialization) and will not prematurely cancel firmware requests while in the initramfs. Since you haven't included the matching CPU firmware blob for microcode to load, udev hangs waiting for a firmware request that will never be fulfilled.
Offline
Thanks a lot for your recommendation! After removing 'microcode' from my 'mkinitcpio.conf' my system boots fast again.
Offline