Stuck at initial ramdisk

After update and auto install nvidia driver stuck in initial ramdisk. This is very frustrating. Please someone help me or im going to install more stable os. I cant use my laptop for two days now. Asus strix corei9 nvidia 3060

Restore a snapshot.

1 Like

From live boot it wont do anything when i click it.
I also did this:

  • use the USB and from there chroot into your system
  • run sudo micro /etc/mkinitcpio.conf
  • add the module vmd to the MODULES list
  • run sudo mkinitcpio -P to regenerate all initramfs
  • run sudo micro /etc/default/grub
  • add nvme_load=YES to GRUB_CMDLINE_LINUX line
  • run sudo grub-mkconfig -o /boot/grub/grub.cfg to regenerate the GRUB menu
  • reboot
    But still stuck on initial ramdisk :confused:

From live boot it wont do anything when i click it.
I also did this:

  • use the USB and from there chroot into your system
  • run sudo micro /etc/mkinitcpio.conf
  • add the module vmd to the MODULES list
  • run sudo mkinitcpio -P to regenerate all initramfs
  • run sudo micro /etc/default/grub
  • add nvme_load=YES to GRUB_CMDLINE_LINUX line
  • run sudo grub-mkconfig -o /boot/grub/grub.cfg to regenerate the GRUB menu
  • reboot
    But still stuck on initial ramdisk :confused:

:point_down:

In general, for this type of issues, consider also:

PS:

This is not nice.

2 Likes

I tried manythings mate. I have to use my laptop and stuck in this for two days. I used mint and ubuntu for years now but this is fraustrating. The design part if garuda is perfect but im going to loose hope on this

I tried snapshot it wont work. Chroot wont work. Reinstall with open source driver? Its laggy as hell and i should use nvidia driver. When i use nvidia driver stuck in loading initial ramdisk :confused:

I can understand your frustration, but I'm sure you know that moving to a rolling release this is something that should not be underestimated.
You have to factor in problems like that, which are absolutely not attributable to Garuda, but to the updates around it and what can happen as a result.
You have to get familiar with some of the procedures, and then the resulution of problems like this becomes a matter of minutes.
To indirectly attribute the term "unstable" to update issues is in my opinion insulting to those who work on it (devote their free time) and to the many who have been using Garuda successfully for a few years now.

3 Likes

Comeon mate tell me what should i do.

Start providing your garuda-inxi information from the live USB and let's see.

2 Likes

Maybe i dont used correct word but as you can see im trying to figure out problems mate. No disrespect.

There is an easy way to get garuda-inxi in text. Open up Garuda Assistant > system specs > copy for forum :slight_smile:
It automatically includes the proper formatting so you can pop it straight in here.

4 Likes

(post deleted by author)

1 Like

Have you tried switching to or most likely booting to a TTY, then garuda-update again (just in case of problems in the first update), then (maybe try startx or more likely) try a

sudo dkms autoinstall

Also, if chrooting was not working with the Garuda Welcome button, you could try this manual procedure, so that we can check the error messages.

3 Likes

[[email protected] /]# sudo garuda-chroot /mnt/broken/@
sudo: garuda-chroot: command not found

[[email protected] /]# sudo dkms autoinstall
Sign command: /usr/lib/modules/6.0.2-zen1-1-zen/build/scripts/sign-file
Binary /usr/lib/modules/6.0.2-zen1-1-zen/build/scripts/sign-file not found, modules won't be signed
Error! Your kernel headers for kernel 6.0.2-zen1-1-zen cannot be found at /usr/lib/modules/6.0.2-zen1-1-zen/bu
ild or /usr/lib/modules/6.0.2-zen1-1-zen/source.
Please install the linux-headers-6.0.2-zen1-1-zen package or use the --kernelsourcedir option to tell DKMS whe
re it's located.

Good point that you are in a TTY!
First thing I'd try due to this:

is

sudo pacman -S linux-zen-headers

Then reboot.
That error on garuda-chroot is very strange (never ever happened before), that script is in the system since ages.

1 Like

I did but still stuck on loading initial ramdisk :frowning:

sudo pacman -S linux-zen-headers
warning: linux-zen-headers-6.0.7.zen1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-zen-headers-6.0.7.zen1-1

Total Installed Size:  150.87 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                     [------------------------------------] 100%
(1/1) checking package integrity                                   [------------------------------------] 100%
(1/1) loading package files                                        [------------------------------------] 100%
(1/1) checking for file conflicts                                  [------------------------------------] 100%
(1/1) checking available disk space                                [------------------------------------] 100%
:: Running pre-transaction hooks...
(1/2) Performing snapper pre snapshots for the following configurations...
==> root: 21
(2/2) Remove upgraded DKMS modules
==> dkms remove --no-depmod nvidia/520.56.06 -k 6.0.7-zen1-1-zen
:: Processing package changes...
(1/1) reinstalling linux-zen-headers                               [------------------------------------] 100%
:: Running post-transaction hooks...
(1/8) Arming ConditionNeedsUpdate...
(2/8) Updating module dependencies...
(3/8) Install DKMS modules
==> dkms install --no-depmod nvidia/520.56.06 -k 6.0.7-zen1-1-zen
==> depmod 6.0.7-zen1-1-zen
(4/8) Foreign/AUR package notification
gwe 0.15.5-3
rootactions-servicemenu 2.7.3-1
(5/8) Orphaned package notification...
geocode-glib 3.26.4-2
(6/8) Checking for .pacnew and .pacsave files...
(7/8) Performing snapper post snapshots for the following configurations...
==> root: 22
(8/8) Syncing all file systems...
[[email protected] /]#