| 1 |
On 5/13/21 5:06 PM, John Blinka wrote: |
| 2 |
> Hi, Gentooers, |
| 3 |
> |
| 4 |
> New thread, next obstacle in booting new Asus mobo. |
| 5 |
> |
| 6 |
> As the subject says, the boot hangs indefinitely. Output to the screen is |
| 7 |
> |
| 8 |
> Booting a command list |
| 9 |
> |
| 10 |
> Loading Linux 5.10.27-gentoo-x86_64 ... |
| 11 |
> Loading initial ramdisk ... |
| 12 |
> |
| 13 |
> And there it stops forever. |
| 14 |
> |
| 15 |
> The kernel is the latest stable gentoo-sources. I normally do a |
| 16 |
> custom configuration, but in this instance built it with “genkernel |
| 17 |
> all”, using whatever config genkernel produces. I use grub (grub2), |
| 18 |
> and installed the kernel and initrd with “grub-mkconfig -o |
| 19 |
> /boot/grub/grub.cfg”, as I normally do. |
| 20 |
> |
| 21 |
> Googling around shows that this problem tends to occur when grub can’t |
| 22 |
> find the initrd. |
| 23 |
> |
| 24 |
> So I looked at the grub boot script by pressing “e” just before the |
| 25 |
> boot starts to make sure that grub is looking in the right place for |
| 26 |
> the kernel and for the initrd. I think it is, since deliberately |
| 27 |
> misspelling either file name with the grub editor causes error |
| 28 |
> messages saying grub can’t find what I told it to look for. And those |
| 29 |
> error messages do not occur with the boot script that grub generated. |
| 30 |
> |
| 31 |
> Normally, loading the initrd takes only a few seconds. |
| 32 |
> |
| 33 |
> How does one debug this situation? |
| 34 |
> |
| 35 |
> John |
| 36 |
|
| 37 |
I'd start by removing any "quiet" or "splash" from the kernel command |
| 38 |
line. You should be able to see them when you hit "e". I'm not sure |
| 39 |
if it will actually help, but it should be a start. |
Archives