Linux loading initial ramdisk

[fedora 16][x86-64]Долго грузится система

Сабж. Уже было несколько обновлений ядра, проблема осталась. Дефолтная fedora 16, официальная сборка с KDE. Долго держится надпись «Loading initial ramdisk» в консоли, потом через 2-3 минуты запускается kdm. Какие надо конфиги выложу, скажите только какие. Ах да, процессор Intel Core i5.

Долго держится надпись «Loading initial ramdisk» в консоли

Ну дык пересобери ядро без него, в чем проблема-то? 🙂

На моем старом x86 ноуте все грузилось быстро с дефолтным ядром. А что это вообще такое?

На моем старом x86 ноуте все грузилось быстро с дефолтным ядром. А что это вообще такое?

Хотя, по-хорошему, стоит поставить bootchart и нормально по графикам посмотреть что же так долго тупит.

Было такое. Помогло удаление sendmail, правда, вместе с ним уходит хром. По крайней мере, можно попробовать.

Это может быть простой глюк plymouth, например. В ядре 3.2 он работает как-то странно.

А его можно безболезненно удалить?

А он безболезненно и удаляется. Удаляет вместе с собой только Chrome, и возможно Evolution — но если не поможет, можно поставить все обратно, настройки ведь не сбиваются.

Если не поможет — может, ставил какие дрова проприетарные? Тогда удалить akmod (kmod) с зависимостями, загрузиться с последним ядром и sudo dracut —force

Не помогает. Проприетарных дров не ставил.

Все равно можешь попробовать sudo dracut —force. Если ничего — тогда да, придется bootchart

Лоровцы такие лоровцы, прежде чем что-то удалять, может логи посмотреть для начала?

В параметрах загрузки в grub убираешь rhgb и quiet, получаешь полный лог загрузки на экран и в файл /var/log/boot.log Смотреть надо не только на то после какой строчки тормозит, но и перед какой.

Насчет sendmail — там действительно есть часто встречающаяся проблема с долгой загрузкой, но решать её надо не удалением sendmail, а прописыванием в /etc/hosts правильного имени. Должно выглядеть вот так:

Источник

Arch Linux

You are not logged in.

#1 2018-06-01 18:19:09

[Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

This is my first time installing archlinux and I am doing so on a UEFI system with grub as my bootloader. When I try and reboot from my drive I receive the following output:

Loading Linux linux .
Loading initial ramdisk .

and then the system freezes every time. Any ideas on what I could try to fix this? Thanks!

Last edited by mrhodes (2018-06-06 21:40:51)

#2 2018-06-01 18:29:52

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

Can you post output of your fstab?

I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.

#3 2018-06-01 19:27:29

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

Remove the quiet option from Kernel_parameters#GRUB if present and add loglevel=7 does that produce more output if so what is the additional output?

#4 2018-06-01 20:04:52

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

Remove the quiet option from Kernel_parameters#GRUB if present and add loglevel=7 does that produce more output if so what is the additional output?

I removed quiet and added loglevel=7 but there was no additional output, it still froze on loading initial ramdisk.

#5 2018-06-01 20:11:02

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

Can you post output of your fstab?

#6 2018-06-01 20:13:02

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

What hardware is this? Specifically CPU and Graphics, but as much information as you can provide would be helpful.

And which ISO did you use to install Arch?

Sakura:-
Mobo: MSI MEG B550 UNIFY // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

#7 2018-06-01 20:34:25

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

What hardware is this? Specifically CPU and Graphics, but as much information as you can provide would be helpful.

And which ISO did you use to install Arch?

The ISO was ARCH_201805. As for the hardware, I am using a Lenovo Yoga 720 with an Intel i7 7th generation core processor and a NVIDIA GeForce GTX 1050 graphics card.

#8 2018-06-01 20:35:39

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

Are the messages frozen on the screen or does the screen go blank?

#9 2018-06-01 20:44:00

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

Are the messages frozen on the screen or does the screen go blank?

The messages are frozen on the screen.

#10 2018-06-01 20:44:27

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

What happens if you boot with «nomodeset» as kernel parameter?

#11 2018-06-01 20:50:53

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

To stop any of the GPU’s in the system using KMS «nomodeset i915.modeset=0 nouveau.modeset=0»

#12 2018-06-01 21:55:13

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

What happens if you boot with «nomodeset» as kernel parameter?

No further output is achieved. Still freezes on loading initial ramdisk.

#13 2018-06-01 22:16:37

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

If you remove the root and initrd kernel options does the output change?
If you boot the installation media. What kernel version does that have? (from the output of uname -r something like 4.16.5-1-ARCH)
The installed system if you Installation_guide#Chroot and check the version of linux on the installed system with pacman -Q linux..

#14 2018-06-01 22:47:37

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

If you remove the root and initrd kernel options does the output change?
If you boot the installation media. What kernel version does that have? (from the output of uname -r something like 4.16.5-1-ARCH)
The installed system if you Installation_guide#Chroot and check the version of linux on the installed system with pacman -Q linux..

I didn’t see any root option in the kernel settings, but removing the initrd option did not change the output. The installation media used kernel version 4.16.5-1-ARCH but the installed system had kernel version linux 4.16.12-1

#15 2018-06-04 07:43:35

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

What hardware is this? Specifically CPU and Graphics, but as much information as you can provide would be helpful.

And which ISO did you use to install Arch?

The ISO was ARCH_201805. As for the hardware, I am using a Lenovo Yoga 720 with an Intel i7 7th generation core processor and a NVIDIA GeForce GTX 1050 graphics card.

I have the same problem with you. My graphics card is NVIDIA Quadro P620. Both GeForce GTX 1050 and Quadro P620 has the same code: GP107. I think that’s the problem.

#16 2018-06-04 17:28:49

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

What hardware is this? Specifically CPU and Graphics, but as much information as you can provide would be helpful.

And which ISO did you use to install Arch?

The ISO was ARCH_201805. As for the hardware, I am using a Lenovo Yoga 720 with an Intel i7 7th generation core processor and a NVIDIA GeForce GTX 1050 graphics card.

I have the same problem with you. My graphics card is NVIDIA Quadro P620. Both GeForce GTX 1050 and Quadro P620 has the same code: GP107. I think that’s the problem.

That’s unfortunate. Do you happen to know of a prior version of Arch that doesn’t have this bug?

#17 2018-06-04 18:15:02

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

There is nothing such as «a prior version of Arch».

The other thread suggests that this is a problem w/ the nvidia blob only, so you should try nouveau in order to figure whether you’re actually on the same page.

If so, you could try the 390xx nvidia driver (not sure whether it already covers your GPU, though) or pass «nvidia-drm.modeset=1» to the kernel parameters.
In any case, a journal of the failed boot might reveal more about the problem.

#18 2018-06-04 18:34:34

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

You could downgrade the kernel to 4.16.5-1. You can obtain the package from the ALA.

#19 2018-06-04 22:00:23

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

You could downgrade the kernel to 4.16.5-1. You can obtain the package from the ALA.

I tried downgrading the kernel and there was still no additional output.

#20 2018-06-04 22:02:48

Re: [Solved]Booting Error — Frozen on «Loading Initial Ramdisk»

There is nothing such as «a prior version of Arch».

The other thread suggests that this is a problem w/ the nvidia blob only, so you should try nouveau in order to figure whether you’re actually on the same page.

If so, you could try the 390xx nvidia driver (not sure whether it already covers your GPU, though) or pass «nvidia-drm.modeset=1» to the kernel parameters.
In any case, a journal of the failed boot might reveal more about the problem.

When booting off of the installation drive, the nouveau driver was used. I installed it on my hard drive to try it and it still froze on «loading initial ramdisk.»

Источник

Arch Linux

You are not logged in.

#1 2015-11-01 21:09:33

Booting stops at Loading initial ramdisk.

I have two computers that stopped booting today after doing updates. The updates included linux-4.2.5 and nvidia-304xx-304.128-4. The boot process stops at Loading initial ramdisk.

I arch-chrooted in and regenerated grub.cfg but no help.

Is anyone else having similar problems? Any advice would be appreciated.

Last edited by kekules_dream (2015-11-01 21:13:38)

#2 2015-11-01 21:14:46

Re: Booting stops at Loading initial ramdisk.

Have you also tried regenerating the initramfs?

Or booting from the fallback image?

#3 2015-11-01 23:39:00

Re: Booting stops at Loading initial ramdisk.

I had tried rebooting from the fallback image. Now I went ahead with regenerating the initramfs. Unfortunately neither of these made any difference. I see grub trying to start, then I see:

But then, nothing happens. Strange it happened to two computers.

#4 2015-11-01 23:43:36

Re: Booting stops at Loading initial ramdisk.

What is in the journal for one of these failed boots?

Registered Linux User #482438

#5 2015-11-02 00:10:17

Re: Booting stops at Loading initial ramdisk.

I’m having trouble determining that.

gives No entries

gives information for the last good boot before the updates that caused the trouble. I don’t understand that because I obviously booted the machine today and did the updates.

#6 2015-11-02 12:18:18

Re: Booting stops at Loading initial ramdisk.

For rescue, I was using the Arch Linux disk from May 2015, which used the 4.0.1-1 kernel. So I downloaded the new Nov 2015 disk, which includes kernel 4.2.5. Checked the sums of the file and even the md5sum of the burned disk. All good.

This disk could not boot my WIFE’S computer (you can imagine the climate here). It gave a kernel panic.

Booted again from the May disk to get:

Using the May disk, I installed the lts kernel, which Is 4.1.2, but the boot process stopped in the same place with it also.

This doesn’t make sense to me though, because when I checked the pacman.log, I see the the computer was booting fine with linux-4.1.5 from August until yesterday when I upgraded from 4.1.5 to 4.2.5.

#7 2015-11-02 15:10:16

Re: Booting stops at Loading initial ramdisk.

What’s happening after the ‘Loading initial ramdisk’? Does the screen turn black but computer keeps running? If that’s the case try booting with the nomodeset option which helped me with my nvidia card.

#8 2015-11-03 01:53:00

Re: Booting stops at Loading initial ramdisk.

Thank you for your suggestion. No, the screen does not turn black on either affected computer. the following shows and stays:

After adding nomodeset, then I see

and it stays, visible. Although I initially thought it might have something to do with the nvidia 304xx driver, I now doubt that since I can’t boot from the Nov 2015 installation CD.

#9 2015-11-03 02:07:43

Re: Booting stops at Loading initial ramdisk.

If reverting to last working kernel doesn’t help, I’d imagine either systemd or grub is causing your issue.

If you don’t have HOOKS=»systemd» in your mkinitcpio.conf, and you aren’t seeing any kernel boot messages (even without ‘quiet’ kernel boot flag), I’m pretty sure it’s the latter.

I vaguely remember having similar issue that was caused by some syslinux update, and reverting to previous version made my system bootable again.

I haven’t owned a nvidia card for years though, so I don’t know if proprietary drivers could be causing this. Although if you haven’t bundled the nvidia kernel module in your initramfs, I don’t see how that could be the case.

#10 2015-11-03 14:43:20

Re: Booting stops at Loading initial ramdisk.

I had this before when using an old version of UEFI GRUB on a USB stick. I fixed it by just updating grub and then re-installing it. Something along the lines of:

ONLY if you are using UEFI

Your efi-directory might be just /boot especially if you followed the Arch wiki when setting up.

ONLY if you are using BIOS

Where /dev/sda is your boot disk

#11 2015-11-04 09:55:03

Re: Booting stops at Loading initial ramdisk.

I have the same problem, on the only computer of the house (and my wife isn’t happy either !)
I upgraded monday evening, saw Linux was getting updated, but didn’t pay attention to the version and didn’t reboot afterwards to check. [Edit : I remember I checked nevertheless that there was no warning message during the mkinitcpio build, as I do every time.] The next morning my wife reported that it didn’t boot anymore. The symptoms are exactly the same (except the messages are in french, but that’s not relevant). The fallback initramfs produces the same effects, as does an old initramfs that was there in my /boot.

My processor is also an Athlon 64 X2 Dual Core but my graphics card is an ATI, not nvidia. I guess the problem must come from the linux update, which is certainly 4.2.5 version according to this thread.

I couldn’t find a working bootable disc yesterday but now I’m worried that the 2015-11 that I just burned may not boot, as it happens for kekules_dream. maybe I’ll also burn a less recent disk, like 2 or 3 months old, just in case. But I see that kekules_dream still couldn’t fix his computers even with a working disk, so I think I might be stuck the same way.

I really hope someone can help us ! I’ll post tonight’s results as soon as I can.

Last edited by gdeshors (2015-11-04 10:01:10)

#12 2015-11-04 17:00:38

Re: Booting stops at Loading initial ramdisk.

It seems I have the same issue also. I updated yesterday and today, when I booted up, same thing, blank screen just after grub.
intel corei5 and nvidia GTX670.

I am quite a newbie so I tried whatever I could find here and there.

Booted with arch install boot disk, chrooted, pacman -Syu, updated to the latest. Removed whatever I installed yesterday (xboxdrv). Same thing.

I tried to look at the different logs in /var/log but could not find anything that seems to be related.

Which log should I look at to debug boot issues like this?

#13 2015-11-04 18:00:10

Re: Booting stops at Loading initial ramdisk.

just followed [https://wiki.archlinux.org/index.php/Bo … ith_pacman] but no success

#14 2015-11-04 21:07:07

Re: Booting stops at Loading initial ramdisk.

Assuming you use an EFI system, you could try to boot the kernel directly using efibootmgr to circumvent possible bootloader issues.
See https://wiki.archlinux.org/index.php/EF … bootmgr.29

#15 2015-11-04 22:13:35

Re: Booting stops at Loading initial ramdisk.

Update: Just tried the two disks I had burned.
The november disk fails with a kernel panic, just like kekules_dream. I took a photo of the screen, should I post it ?
The september disk goes further but shows read errors and then fails on the seemingly common 30 seconds error, so maybe my image or burn was corrupted. Im really out of luck these days!
Thus I’m still stuck and couldnt even chroot and try anything.

(Just for a check, i tried also i686 kernels on both discs and the repective behavior was identical to the x86 64)

#16 2015-11-04 22:33:07

Re: Booting stops at Loading initial ramdisk.

Are you able to boot anything?
E.g. memtest86+ which is, if I recall correctly, on the arch-install disk.
Don’t know, if this really calls as booting something, but it does not harm to try.

#17 2015-11-05 08:10:49

Re: Booting stops at Loading initial ramdisk.

I didn’t try memtest from the archlinux cd, but tuesday evening I successfully booted from a SystemRescueCD that was probably several years old, in order to chroot on my system.
(This attempt failed because it refused to mount my LVM partitions, and anyway I guess it was probably a i686 kernel so I’m not sure I could have repaired my system with this.)

#18 2015-11-05 09:59:23

Re: Booting stops at Loading initial ramdisk.

Update: Just tried the two disks I had burned.
The november disk fails with a kernel panic, just like kekules_dream. I took a photo of the screen, should I post it ?
The september disk goes further but shows read errors and then fails on the seemingly common 30 seconds error, so maybe my image or burn was corrupted. Im really out of luck these days!
Thus I’m still stuck and couldnt even chroot and try anything.

(Just for a check, i tried also i686 kernels on both discs and the repective behavior was identical to the x86 64)

To get past 30 second problem, either burn to DVD instead of CD, if that does not work at the emergency shell try this:

and wait for boot to complete

assumptions:
/dev/sr0 is your cd drive
ARCH_201509 if your booting september ISO

#19 2015-11-05 21:49:36

Re: Booting stops at Loading initial ramdisk.

Thank you very much, rlees85 : your hint allowed me to boot with the september CD without having to burn it again of find a free usb stick. For anyone reading this later, I had to correct the last ln to «ln /dev/sr0 ./by-label/ARCH_201509″ but it’s quite obvious.

For me, the problem seems solved, at least with the LTS kernel.
I chrooted, installed the LTS kernel (I had to uninstall the linux package because my /boot was too small. ) And as I remembered that doing this didn’t do the trick for kekules_dream and I had seen grub mentioned a few times, I also reinstalled grub on the disk :

Of course I also did a # grub-mkconfig -o /mnt/usb/boot/grub/grub.cfg because I had installed the LTS kernel.

I rebooted, and all worked fine (a few errors during startup, but I think they come from my not-so-good arch CD still in the box). I was then able to make my /boot a little bigger eating a little on my swap partition, reinstalled the standard linux kernel, and I’m now going to reboot to test the classic kernel (4.2.5) and let you know.

If it works, my guess is it came from grub. but why .
And also, there’s still this question : why aren’t we kekules_dream and I able to boot the computer with the november image ? Shouldn’t we file a bug report for this ?

Источник