Boot hang after "random: crng init done"

[2bdkid]

I pulled branch rpi-4.9.y from www.github.com/raspberrypi/linux and cross compiled the bcmrpi3 target for arm64. I copied over the kernel and *.dtb files into the boot directory. I also copied bootcode.bin, *.dat, and *.elf from www.github.com/raspberrypi/firmware into /boot. When the system boots, it stops at "random: crng init done" and will not continue. I found some other articles saying it was a power issue or sd card issue, but I built the system on a second sd card and had the same results. I'm thinking it's a kernel issue so would anyone know which kernel to try next?

[2bdkid]

Solution: press enter and the prompt appears.
Can't believe it took me this long...

[tkninja]

By the way, this happens to me, too. You don't have to press Enter to get the prompt, however: just enter in a command, if Raspian automatically logs you in.

[SoNic67]

In my case, pressing enter key or any command does nothing. It just moves the text on the screen one line up.

[Roken]

I was getting this when experimenting with NFS boot - and it usually meant that the system couldn't find rootfs.

Check cmdline.txt

[doomkin]

At boot, the kernel waits for mouse movements to initialize the random number generator.
Kernel messages on boot:

Code: Select all

sudo dmesg | less

The problem:

Code: Select all

kernel: random: crng init done

The solution:

Code: Select all

sudo apt install haveged
sudo systemctl enable haveged

[nana199685]

At boot, the kernel waits for mouse movements to initialize the random number generator.
Kernel messages on boot:

Code: Select all

sudo dmesg | less

The problem:

Code: Select all

kernel: random: crng init done

The solution:

Code: Select all

sudo apt install haveged
sudo systemctl enable haveged

i meet the same problem that the screen stop at "random: crng init done"
i did modify my cmdline.txt before i reboot
but now i can't type any command you mentioned.
when i type something and press enter
it just wraps and happen nothing
i have check my power that was normal
please help me.QQ

[PhilE]

The fact that the message says "crng init done" suggests the fault is with something else it is trying to start afterwards. Try with "initcall_debug=1" on in cmdline.txt, and then see what the last few messages say.

You say:

i did modify my cmdline.txt before i reboot

Can you remember what you changed, and have you tried changing it back?

[Tmpod]

I have the exact same problem. I'm using raspbian lite and I started getting a kernal panic saying that it could not mount root fs onto

Code: Select all

unknown-block(179, 2) 

. After some searching I found a stackoverflow post that suggested changing something in the cmdline.txt file. So I did. And now I'm getting this. I've tried setting

Code: Select all

initcall_debug=1

and no more messages seem to appear. The boot still hangs on

Code: Select all

crng init done

. Here's cmdfile.txt copied and pasted

Code: Select all

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=27504eef-06 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait initcall_debug=1

(what u changed was that last 06 digit at the end of the root part, that was previously 02)

Thanks in advance

[PhilE]

Try using the old method for specifying a root fs, i.e. the name of the block device on which it appears:

Code: Select all

... root=/dev/mmcblk0p2 ...

To get more debug output you probably also need to add something like "loglevel=8'.

[rin67630]

At boot, the kernel waits for mouse movements to initialize the random number generator.
/quote]

Ugh! that seem a valid explanation: I am running headless and HAVE NO MOUSE NOR KEYBOARD.

Pluging a mouse releases the boot process. But that is'nt the purpose of a headless machine!

Installing haveged works!