After installing nvidia drivers system stuck on loading while booting!

I am using KDE Dr460nized edition. I installed nvidia drivers on my system from install/remove software and when it successfully installed a popup showed 'restart system to take make changes to effect' so i just restarted my system but while loading it got stuck. I don't know what to do next. Thanks in advance. I am using HP-Z200workstation PC, its having 4GB RAM, Intel Core I7 processor and 1GB graphic card!

Nooo... my eyes... Windows... you've blinded me with that pic. :wink:

Please don't post pictures on technical help requests.

Please edit your OP and delete the picture and replace it with the textual output of this command:

inxi -Fxxxza

What instructions have you followed, regarding changing video drivers?
With more power (of System Administrator) comes more responsibility, or else... you can break your system unusable.

1 Like

I just gone through very tedious research. Later I found that we can get access to system through snapshot captured when system updated! somehow i just successfully recovered my Garuda OS. Now I'll install those drivers later as I don't want to take risk anymore!!!!:sweat_smile:......... But while booting it shows 3 dots at the place of buffering symbol with garuda image...... Anyway after entering cmd the output is

inxi -Fxxxza
  Kernel: 5.10.8-112-tkg-bmq x86_64 bits: 64 compiler: gcc v: 10.2.0
  parameters: intel_pstate=passive BOOT_IMAGE=/vmlinuz-linux-tkg-bmq
  root=UUID=55543bda-9cfc-4f4c-8b8c-004abd5be61b rw
  rootflags=subvol=timeshift-btrfs/snapshots/2021-01-21_19-00-56/@ quiet splash
  rd.udev.log_priority=3 vt.global_cursor_default=0
  resume=UUID=45cc3cd1-862b-455b-81fd-c7937f2a1d6c loglevel=3
  Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 dm: SDDM
  Distro: Garuda Linux
  Type: Desktop System: Hewlett-Packard product: HP Z200 Workstation v: N/A
  serial: <filter> Chassis: type: 6 serial: <filter>
  Mobo: Hewlett-Packard model: 0B40h serial: <filter> BIOS: Hewlett-Packard
  v: 786H3 v01.12 date: 11/18/2010
  Info: Quad Core model: Intel Core i7 880 bits: 64 type: MCP arch: Nehalem
  family: 6 model-id: 1E (30) stepping: 5 microcode: A L2 cache: 8 MiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 24556
  Speed: 1200 MHz min/max: 1199/3199 MHz boost: enabled Core speeds (MHz): 1: 1200
  2: 1200 3: 1200 4: 1200
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds
  status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
  mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
  mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
  Device-1: NVIDIA GT218 [GeForce 210] driver: nouveau v: kernel bus ID: 01:00.0
  chip ID: 10de:0a65
  Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: nouveau
  unloaded: modesetting alternate: fbdev,nv,vesa display ID: :0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0")
  s-diag: 414mm (16.3")
  Monitor-1: VGA-1 res: 1366x768 hz: 60 dpi: 85 size: 410x230mm (16.1x9.1")
  diag: 470mm (18.5")
  OpenGL: renderer: NVA8 v: 3.3 Mesa 20.3.3 direct render: Yes
  Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56
  Device-2: NVIDIA High Definition Audio driver: snd_hda_intel v: kernel
  bus ID: 01:00.1 chip ID: 10de:0be3
  Sound Server: ALSA v: k5.10.8-112-tkg-bmq
  Device-1: Intel 82578DM Gigabit Network vendor: Hewlett-Packard driver: e1000e
  v: kernel port: 2100 bus ID: 00:19.0 chip ID: 8086:10ef
  IF: enp0s25 state: down mac: <filter>
  Device-2: TP-Link TL-WN722N v2/v3 [Realtek RTL8188EUS] type: USB driver: 8188eu
  bus ID: 2-1.1:3 chip ID: 2357:010c serial: <filter>
  IF: wlp0s29u1u1 state: up mac: <filter>
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: 2120
  bus ID: 00:1f.2 chip ID: 8086.2822 rev: 05
  Local Storage: total: 465.76 GiB used: 10.61 GiB (2.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD5000AAKS-22V1A0
  size: 465.76 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
  serial: <filter> rev: 1D05
  ID-1: / raw size: 55.19 GiB size: 55.19 GiB (100.00%) used: 10.49 GiB (19.0%)
  fs: btrfs dev: /dev/sda8 maj-min: 8:8
  ID-2: /boot raw size: 300 MiB size: 299.4 MiB (99.80%) used: 119.3 MiB (39.8%)
  fs: vfat dev: /dev/sda6 maj-min: 8:6
  ID-3: /home raw size: 55.19 GiB size: 55.19 GiB (100.00%) used: 10.49 GiB (19.0%)
  fs: btrfs dev: /dev/sda8 maj-min: 8:8
  ID-4: /var/log raw size: 55.19 GiB size: 55.19 GiB (100.00%)
  used: 10.49 GiB (19.0%) fs: btrfs dev: /dev/sda8 maj-min: 8:8
  ID-5: /var/tmp raw size: 55.19 GiB size: 55.19 GiB (100.00%)
  used: 10.49 GiB (19.0%) fs: btrfs dev: /dev/sda8 maj-min: 8:8
Swap: Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100)
           ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda7 maj-min: 8:7
           ID-2: swap-2 type: zram size: 966 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0
           ID-3: swap-3 type: zram size: 966 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1
           ID-4: swap-4 type: zram size: 966 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2
           ID-5: swap-5 type: zram size: 966 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3
Sensors:   System Temperatures: cpu: 37.0 C mobo: N/A gpu: nouveau temp: 45.0 C
           Fan Speeds (RPM): N/A
Info:      Processes: 199 Uptime: 10m wakeups: 0 Memory: 3.77 GiB used: 1.92 GiB (50.8%) Init: systemd v: 247 Compilers:
           gcc: 10.2.0 clang: 11.0.1 Packages: pacman: 1174 lib: 289 Shell: fish v: 3.1.2 running in: alacritty inxi: 3.2.01

@Tejkirar read wiki

wth.. the same happened again after converting my distro into ultimate one! i thinks that's again because of nvidia drivers installed in ultimate update... Is there any way to boot up without loosing ultimate update?????????

Have you booted from the USB stick using NON-free video drivers option from the GRUB menu of the USB stick?

Or did you choose the FREE video drivers?

I have had the exact same issue you describe when I chose the FREE video drivers and once the system was installed I clicked on the AUTO INSTALL PROPRIETARY DRIVERS from the Garuda Settings Manager (GUI). It seemed to have installed properly but on reboot it got stuck in the middle of the boot sequence past grub, in a black scsreen, no TTY available.

The 3 dots are normal it takes time for the USB stick to boot, you think it freezes there but you have to wait a few mins and it'll get through.

Acutally sir i have installed garuda kde as dual boot with bootable usb but while installing it was on default nonfree drivers but with this default settings it was not installing it got stuck (waited for more than 15 mins) on three dots shown after click on boot garuda live screen . After that i had done some research and found that after changing drivers setting from nonfree to free it can be installed.... so i just tried this and the os was successfully installed... later i installed nvidia drivers on it but after reboot that's got stuck on garuda loading screen but note that this time the garuda symbol was bigger than usual. .After that i just read wiki and found that we can recover our system with snapshots so some how i just recovered it................ after that i didn't done anything with drivers to prevent my system from any risk ... but i updated my os to ultimate in that it asked me to install nvidia drivers i think i selected okay and selected many more softwares according to my choice asked in that process.... after 20mins it successfully installed softwares over 1.4GB and converted itself into ultimate.... everything was going fine till then.. and just reboot it again got stuck as previously .... i think this also happened just because of nvidia drivers.... BUT THIS TIME I DON'T KNOW WHY I AM UNABLE TO RECOVER MY SYSTEM FROM SNAPSHOTS!!!!!:neutral_face:

Yes so you did boot with FREE drivers and then had the non-free drivers installed later. That is exactly where I got the same problem, so it seems this is reproducible on different machines.

My solution was to boot with NON-free drivers and wait on the 3 dots and black screen until the USB booted. However it seems that doesn't work for you as you waited 15mins already :frowning:

At this point I cannot help more, but I was hoping my question would help provide a bit more data to the video experts on this forum so they can help you.

First of all thanks! and whether it ever fix or not but you helped me a lot. If i'll get no solution from experts then i'll try to reinstall it with nonfree drivers !!!!!!!!!

Honestly I would give it a try again with the non-free drivers, just in case. It's possible one time it may not work and the other it will, just in case. But I hope this does not cause you too much trouble to re-try...

Your graphics card is not supported by nvidia anymore so using nonfree driver is out of question


Well there you go. That also happened to me last Autumn and forced me to buy another card. I was not with Garuda at that time.

Hi there @anon77022990 .

Several moderators and a distro developer have already responded to your initial post regarding your graphics drivers, so you know the team is already aware of your issue. This is not Telegram (where I'm informed you've been banned for your behavior) and responses are not instantaneous on the forum. Your thread is not even a day old, yet you are too impatient to wait politely for an answer to your issue. That is not the way any forum works, (and I'm pretty sure you should be well aware of that). Forum users are expected to wait their turn patiently for assistance. Users are not to pester the distros developers directly via Private Messaging (PM). The forum is approaching a thousand users and imagine how many PM's would be in every devs inbox each morning if every forum user fired off PM's to the distro devs whenever they felt like it.

When you have an issue on the forum, you are expected to wait politely for assistance (like every other user on the forum). Directly "PM'ing" or "pinging" distro staff is considered rude and presumptuous behavior. We have too many users on the forum these days to accept users constantly attempting to contact devs directly via PM's. This also applies to pinging distro staff frivolously using the forum's "@username" notification feature. Distro staff cannot disable these features (like normal users) as they are essential to managing both the distro and the forum. When PM's and Pings are overused by forum members these features become a severe nuisance, as our daily workflow becomes constantly interrupted by these uninvited intrusions. Never PM distro devs directly regarding a support issue. No distro has their developers providing direct on demand one on one support to individual users in this manner.

If you urgently require direct one on one support from the distro developers, perhaps we can arrange a paid support account on a per incident or per minute rate just for you. Otherwise wait your turn patiently like every other user on the forum for assistance, Garuda is one of the few distro's where its developers kindly volunteer regular daily assistance to their users via the forum. Do not test the forum devs generosity by pestering them with your own personal support issues. Please do not contact distro developers directly again, as your behavior on Telegram has already worn out your goodwill with distro staff. If you incur any further warnings on the forum you may simply have your account pulled here, (as with Telegram because of your repeated shenanigans there). Do not abuse the Garuda forum staff's good will as you did on Telegram or your stay here may be rather brief indeed.

Please do not bother to give another of your faux apologies, as that is neither wanted nor necessary. What is necessary, is to start behaving in a respectful manner towards the distos devs. Unfortunately, it's users like you who are jeopardizing the goodwill of the distro devs to provide daily support for all users on the forum. Straighten up and fly right, before you wear out your welcome on the forum as well.


Yes sir i understand and sorry if i did anything wrong. And I am very happy with your assistance! I appreciate your fast response and sorry again for that..... Sir i have one request can you please delete this account. Is there any way to delete this account if not then can you please do this for me. And sorry once more :disappointed:.... And sir i knew that 'PM' one staff member but didn't done anything abusive in telegram......SORRY :sweat:

As I stated, an apology was not required. If you wish your account wiped that is easily done. I was simply attempting to get through to you that your behavior has been out of line in the past and needs modification.

I can certainly do that for you, but I'll give you a few minutes to think about it. You are welcome to remain in the community, we simply felt you need a bit of direction to ensure you know what behavior is expected in the Garuda community.

1 Like

sir why its not supported????

I am not angry or something like that at all... if any rudeness seems in my words .. i apologize for that ... Sir delete this account and please don't ban it so that i can make it again later if i want any support :slightly_smiling_face:

That is a question best directed at Nvidia. They are the ones who deprecated the driver. This has nothing to do with Garuda (or even Linux for that matter)

I've had several nvidia cards have there drivers deprecated by Nvidia and now I refuse to buy their graphics cards simple for that reason. Nvidia is not Linux friendlily, so steer clear of their products if you don't want these types of problems in the future.

sir thats working with my windows .... and then which driver i should buy??

OK then, I will honor your request and do that.

Keep well, and good health to you.