Today's update stopped boot process

[VoidByte]

Hello,

I just fired up my System today and watched something on Amazon while a bigger update runs in the background. After it was done, I decided to reboot, because there was a lot of packages and well.. old windows habbit I think..

Now, the system starts. Then a grey screen with 3 lighter-grey dots appear, then text output shows up and .. well.. nothing more. Thats it. After "finished cleanup modules from old kernels" the system is doing nothing.

And it is not frozen, I can still login to the Terminal when using ALT + F2. Which makes me guess that the system is still active but just forget what to do next. Commands like "reboot" also work like a charm. It is disable/stop and kill everything fine and reboots the computer. No errors to spot from my perspektive.

But how do I repair the system? Going from GRUB straight into the purple bootscreen?
I cant give out any logs due to the fact that I only have the bare terminal on hand and no clue how to operate the system from there to post logfiles into internet forums. I could hand out RL-Screenshots like this one where the System stops:

[SGS]

Boot last working snapshot, start garuda-update again and post all from terminal as text, do not update

[VoidByte]

Hey! Thank you for assisting me.
I tried what you sayed. I hope so I guess.
GRUB starts -> I choose "Snapshots" and get this:

I choose the one from my first boot today (where everything was fine) with the "PRE" type and see this:

Knowing nothing, I startet every one of them after another. None of them get past this screen:

I waited like.. 30 minutes or so. But thats all I get.

[Orko]

I had the same issue. Yesterday there was a huge update. I remember that the most of them were QEMU/KVM packages. I didn't do a reboot, because my toaster had to do some work. This morning I did a shutdown. Just a few minutes ago I turned my pc back on, and I had the same issue. System has booted to the first boot “picture”. Then the moving circle in the middle of the screen stopped and nothing else happened. System freeze… I have tried to reboot several times, but the system didn't boot anymore.

So I did another reboot and booted into the most recent snapshot AFTER the huge update. Now everything is back to normal and the system works without any issues. No errors in journald or elsewhere. Everything is fine.

But then there may be a problem with a recently installed package. I could post the packages installed by the update yesterday if this would help.

[SGS]

Welcome back.

@VoidByte

I choose the one from my first boot today

@SGS

Boot last working snapshot

[VoidByte]

It is the last working one. But that doesnt matter. Even booting one from last week don't go further then the "running early hook on [plymouth]" screen I just showed.

[SGS]

I think you use KDE, and you changed the standard kernel.
Change back to zen kernel via chroot.

Or use something else, I update my PCs every day without problems (KDE+i3wm), if you are already in the chroot you can also post your garuda-inxi.

Have you changed anything else?

[VoidByte]

I am using KDE-Dragonized. And I am not sure what you mean with "changed".. Chaning the installed Programms (install/uninstall)? Minor details on my theme?

The zen Kernel is my standard. The others are installed but I never used them. After the initial installation of garuda, there is this "Setup Assistant" that shows me lots of alternative Kernels all with the ("Could improve system Performance on some systems"). So I checked them all in case of needing them once. But I never did and I never saw an option where I can change the Kernel.

So long text short: Never changed ZEN as the standard Kernel.
And no clue how I would do that, If I wanted to. And so I need to google what Chroot exactly does because I thought that it just to lock down the root directory for files, not changing the kernel of an OS.

[SGS]

[VoidByte]

Hey, so … I have read all that and point 4 is obviously exactly my problem.
So I did what they say:

sudo reflector -a6 -f5 --save /etc/pacman.d/mirrorlist

was taking a few minutes and failed every try to rate. It always went on a timeout for each server.

garuda-update

on the other hand, was doing a lot of things. Updating kernel headers, something with nvidia and so forth. But in the end it doesn’t help at all. I still have the exact problem I had in the OP and I am still unable to start a snapshot from whatever date I try…

sudo dkms autoinstall

Did exactly nothing. No errors, no success… no output at all.

BTW. About chroot my Kernel. When I do this ALT+F2 to get a console, the console says that I am on the ZEN Kernel. But if that is source of the problem: Google always keeps advice me “how to safely unsinstall a kernel” topics. Is it a good Idea to do that now or will I make the problem more worse? (because it will probatly overwrite the snapshots even more)

[BluishHumility]

@VoidByte

And it is not frozen, I can still login to the Terminal when using ALT + F2. Which makes me guess that the system is still active but just forget what to do next. Commands like “reboot” also work like a charm. It is disable/stop and kill everything fine and reboots the computer. No errors to spot from my perspektive.

But how do I repair the system?

It kind of sounds like SDDM is having some kind of issue. Check for errors:

sudo systemctl status sddm.service

If it stopped for some reason, see if restarting it is fruitful.

---

SDDM will crash if there is no available disk space. Check the output of:

df -h

---

It could also be a bug with SDDM. Take a look here:

Segfault error 4 in libc-2.29.so

One person noted a somewhat unconventional fix:

Definetly, removing username from User= field in /etc/sddm.conf.d/default.conf configuration file solves the problem under Arch Linux 5.15.79-1-lts and sddm 0.19.0-9 .

[VoidByte]

Hey, thank you for your help.
This hint was promising. It seems we now have the source of the problem.

for me, a newbie, it looks like that sddm try to start and fail. Disc Space is not a problem. I have plenty of free space (over 500gb). But my Linux knowledge is not remotly good enough to understand what I need to do now or how to fix something like that.

[BluishHumility]

@VoidByte

I have plenty of free space

Post df -h anyway, if you can. It would also be handy to take a look at your garuda-inxi if you are able to post from the live environment (to see what graphics card is in use, etc).

That error, “Failed to read display number from pipe”, turns up quite a few hits in the Arch forum that have been resolved by enabling early KMS (such as here and here). I believe this should be already enabled for you on a Garuda box, but it can’t hurt to double-check.

micro /etc/mkinitcpio.conf

Paste into the thread the line that says “MODULES=(blah blah blah)”.

[VoidByte]

I found a way to bring out a few logs. I save them as txt files, use a live usb stick to transfer the files from the btrfs to a fat partition, start windows to post them… quite a way… but here they are:

Modules in mkinitcpio.conf:

MODULES=(crc32c-intel nvidia nvidia_modeset nvidia_uvm nvidia_drm)

Output of: df -h

dev             7,8G       0  7,8G    0% /dev
run             7,8G    1,6M  7,8G    1% /run
/dev/sda2       682G     26G  655G    4% /
tmpfs           7,8G       0  7,8G    0% /dev/shm
/dev/sda2       682G     26G  655G    4% /srv
/dev/sda2       682G     26G  655G    4% /var/cache
/dev/sda2       682G     26G  655G    4% /root
/dev/sda2       682G     26G  655G    4% /home
/dev/sda2       682G     26G  655G    4% /var/tmp
/dev/sda2       682G     26G  655G    4% /var/log
tmpfs           7,8G       0  7,8G    0% /tmp
/dev/sda1       300M    608K  299M    1% /boot/efi
tmpfs           1,6G     48K  1,6G    1% /run/user/1000

Output of garuda-inxi:

System:
  Kernel: 6.0.10-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=38d11f49-afe0-4b6b-953b-9addc52154a9
    rw rootflags=subvol=@ splash rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=6d7a35cf-7ffb-4292-914c-96f115fef57f loglevel=3 ibt=off
  Console: tty 2 DM: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: H97-D3H v: N/A serial: <superuser required> Chassis:
    type: 3 serial: <superuser required>
  Mobo: Gigabyte model: H97-D3H-CF v: x.x serial: <superuser required> UEFI: American Megatrends
    v: F7 date: 09/19/2015
CPU:
  Info: model: Intel Core i7-4790K bits: 64 type: MT MCP arch: Haswell gen: core 4 level: v3
    note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
    microcode: 0x28
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 4400 min/max: 800/4400 scaling: driver: intel_cpufreq governor: performance
    cores: 1: 4400 2: 4400 3: 4400 4: 4400 5: 4400 6: 4400 7: 4400 8: 4400 bogomips: 63850
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: ZOTAC driver: nvidia v: 520.56.06
    alternate: nouveau,nvidia_drm non-free: 520.xx+ status: current (as of 2022-10) arch: Maxwell
    code: GMxxx process: TSMC 28nm built: 2014-19 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max:
    gen: 3 speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:13c2 class-ID: 0300
  Display: server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.5 driver: N/A tty: 102x38
  API: OpenGL Message: GL data unavailable in console. Try -G --display
Audio:
  Device-1: Intel 9 Series Family HD Audio vendor: Gigabyte driver: snd_hda_intel bus-ID: 3-9:6
    v: kernel chip-ID: 08bb:2902 bus-ID: 00:1b.0 class-ID: 0300 chip-ID: 8086:8ca0 class-ID: 0403
  Device-2: NVIDIA GM204 High Definition Audio vendor: ZOTAC driver: snd_hda_intel v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1
    chip-ID: 10de:0fbb class-ID: 0403
  Device-3: Texas Instruments PCM2902 Audio Codec type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Sound API: ALSA v: k6.0.10-zen2-1-zen running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.61 running: no
Network:
  Device-1: Intel Ethernet I217-V vendor: Gigabyte driver: e1000e v: kernel port: f040
    bus-ID: 00:19.0 chip-ID: 8086:153b class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: f020 bus-ID: 00:1f.2
    chip-ID: 8086:2822 rev: class-ID: 0104
Drives:
  Local Storage: total: 2.05 TiB used: 25.82 GiB (1.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Hitachi model: HTS541075A9E680 size: 698.64 GiB
    block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: B480 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
    scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Hitachi model: HDP725050GLA360 size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: A52A scheme: MBR
  ID-4: /dev/sdd maj-min: 8:48 vendor: Hitachi model: HDT725050VLA360 size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: A7BA
    scheme: MBR
Partition:
  ID-1: / raw-size: 681.23 GiB size: 681.23 GiB (100.00%) used: 25.82 GiB (3.8%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 608 KiB (0.2%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 681.23 GiB size: 681.23 GiB (100.00%) used: 25.82 GiB (3.8%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 681.23 GiB size: 681.23 GiB (100.00%) used: 25.82 GiB (3.8%)
    fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 681.23 GiB size: 681.23 GiB (100.00%) used: 25.82 GiB (3.8%)
    fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.56 GiB used: 1.8 MiB (0.0%) priority: 100 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 17.11 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3
    maj-min: 8:3
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 197 Uptime: 4m wakeups: 0 Memory: 15.56 GiB used: 633.7 MiB (4.0%) Init: systemd
  v: 252 default: graphical tool: systemctl Compilers: gcc: 12.2.0 clang: 14.0.6 Packages:
  pm: pacman pkgs: 1953 libs: 557 tools: pamac,paru Shell: Bash v: 5.1.16 running-in: tty 2
  inxi: 3.3.23
e[1;34mGaruda (2.6.10-1):e[0m
e[1;34m  System install date:e[0m     2022-11-28
e[1;34m  Last full system update:e[0m 2022-12-01
e[1;34m  Is partially upgraded:  e[0m No
e[1;34m  Relevant software:      e[0m NetworkManager
e[1;34m  Windows dual boot:      e[0m Probably (Run as root to verify)
e[1;34m  Snapshots:              e[0m Snapper
e[1;34m  Failed units:           e[0m 

[TNE]

Xorg is having some trouble starting, can you post /var/log/Xorg.0.log here as well? That should get us closer to the root source.

[VoidByte]

sure.
Here is the output:

[    25.509] (--) Log file renamed from "/var/log/Xorg.pid-720.log" to "/var/log/Xorg.0.log"
[    25.510] 
X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
[    25.510] Current Operating System: Linux desktop 6.0.10-zen2-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Sat, 26 Nov 2022 16:51:24 +0000 x86_64
[    25.510] Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=38d11f49-afe0-4b6b-953b-9addc52154a9 rw rootflags=subvol=@ splash rd.udev.log_priority=3 vt.global_cursor_default=0 resume=UUID=6d7a35cf-7ffb-4292-914c-96f115fef57f loglevel=3 ibt=off
[    25.510]  
[    25.510] Current version of pixman: 0.42.2
[    25.510] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    25.510] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    25.510] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec  1 17:39:23 2022
[    25.510] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    25.510] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    25.510] (==) No Layout section.  Using the first Screen section.
[    25.510] (==) No screen section available. Using defaults.
[    25.510] (**) |-->Screen "Default Screen Section" (0)
[    25.510] (**) |   |-->Monitor "<default monitor>"
[    25.510] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    25.510] (==) Automatically adding devices
[    25.510] (==) Automatically enabling devices
[    25.510] (==) Automatically adding GPU devices
[    25.510] (==) Automatically binding GPU devices
[    25.510] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    25.510] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/misc".
[    25.510] 	Entry deleted from font path.
[    25.510] 	(Run 'mkfontdir' on "/usr/share/fonts/misc").
[    25.510] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF".
[    25.510] 	Entry deleted from font path.
[    25.510] 	(Run 'mkfontdir' on "/usr/share/fonts/TTF").
[    25.510] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF".
[    25.510] 	Entry deleted from font path.
[    25.510] 	(Run 'mkfontdir' on "/usr/share/fonts/OTF").
[    25.510] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    25.510] 	Entry deleted from font path.
[    25.510] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    25.510] 	Entry deleted from font path.
[    25.510] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    25.510] 	Entry deleted from font path.
[    25.510] (==) FontPath set to:
	
[    25.510] (==) ModulePath set to "/usr/lib/xorg/modules"
[    25.510] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    25.510] (II) Module ABI versions:
[    25.510] 	X.Org ANSI C Emulation: 0.4
[    25.510] 	X.Org Video Driver: 25.2
[    25.510] 	X.Org XInput driver : 24.4
[    25.510] 	X.Org Server Extension : 10.0
[    25.511] (++) using VT number 1

[    25.511] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    25.511] (II) xfree86: Adding drm device (/dev/dri/card0)
[    25.511] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
[    25.511] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[    25.512] (--) PCI:*(1@0:0:0) 10de:13c2:19da:2370 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[    25.512] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    25.512] (II) LoadModule: "glx"
[    25.512] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    25.513] (II) Module glx: vendor="X.Org Foundation"
[    25.513] 	compiled for 1.21.1.4, module version = 1.0.0
[    25.513] 	ABI class: X.Org Server Extension, version 10.0
[    25.513] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[    25.513] 	loading driver: nvidia
[    25.513] (==) Matched nvidia as autoconfigured driver 0
[    25.513] (==) Matched nouveau as autoconfigured driver 1
[    25.513] (==) Matched nv as autoconfigured driver 2
[    25.513] (==) Matched modesetting as autoconfigured driver 3
[    25.513] (==) Matched fbdev as autoconfigured driver 4
[    25.513] (==) Matched vesa as autoconfigured driver 5
[    25.513] (==) Assigned the driver to the xf86ConfigLayout
[    25.513] (II) LoadModule: "nvidia"
[    25.513] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    25.513] (II) Module nvidia: vendor="NVIDIA Corporation"
[    25.513] 	compiled for 1.6.99.901, module version = 1.0.0
[    25.513] 	Module class: X.Org Video Driver
[    25.513] (II) LoadModule: "nouveau"
[    25.514] (WW) Warning, couldn't open module nouveau
[    25.514] (EE) Failed to load module "nouveau" (module does not exist, 0)
[    25.514] (II) LoadModule: "nv"
[    25.514] (WW) Warning, couldn't open module nv
[    25.514] (EE) Failed to load module "nv" (module does not exist, 0)
[    25.514] (II) LoadModule: "modesetting"
[    25.514] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    25.514] (II) Module modesetting: vendor="X.Org Foundation"
[    25.514] 	compiled for 1.21.1.4, module version = 1.21.1
[    25.514] 	Module class: X.Org Video Driver
[    25.514] 	ABI class: X.Org Video Driver, version 25.2
[    25.514] (II) LoadModule: "fbdev"
[    25.514] (WW) Warning, couldn't open module fbdev
[    25.514] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    25.514] (II) LoadModule: "vesa"
[    25.514] (WW) Warning, couldn't open module vesa
[    25.514] (EE) Failed to load module "vesa" (module does not exist, 0)
[    25.514] (II) NVIDIA dlloader X Driver  525.60.11  Wed Nov 23 22:56:57 UTC 2022
[    25.514] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    25.514] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    25.514] (II) Loading sub module "fb"
[    25.514] (II) LoadModule: "fb"
[    25.514] (II) Module "fb" already built-in
[    25.515] (II) Loading sub module "wfb"
[    25.515] (II) LoadModule: "wfb"
[    25.515] (II) Loading /usr/lib/xorg/modules/libwfb.so
[    25.515] (II) Module wfb: vendor="X.Org Foundation"
[    25.515] 	compiled for 1.21.1.4, module version = 1.0.0
[    25.515] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    25.515] (II) Loading sub module "ramdac"
[    25.515] (II) LoadModule: "ramdac"
[    25.515] (II) Module "ramdac" already built-in
[    25.515] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[    25.515] (EE) NVIDIA:     system's kernel log for additional error messages and
[    25.515] (EE) NVIDIA:     consult the NVIDIA README for details.
[    25.515] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[    25.515] (EE) NVIDIA:     system's kernel log for additional error messages and
[    25.515] (EE) NVIDIA:     consult the NVIDIA README for details.
[    25.515] (WW) Falling back to old probe method for modesetting
[    25.515] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[    25.515] (EE) NVIDIA:     system's kernel log for additional error messages and
[    25.515] (EE) NVIDIA:     consult the NVIDIA README for details.
[    25.515] (EE) Screen 0 deleted because of no matching config section.
[    25.515] (II) UnloadModule: "modesetting"
[    25.515] (EE) Device(s) detected, but none match those in the config file.
[    25.515] (EE) 
Fatal server error:
[    25.515] (EE) no screens found(EE) 
[    25.515] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    25.515] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    25.515] (EE) 
[    25.516] (EE) Server terminated with error (1). Closing log file.

Does that means that my graphic driver is broken? I guess its not like windows, where I would just uninstall and reinstall it right? On the other side.. why is nouveau failing then? I mean, an update that crash one driver might happen for Proprietary Drivers, but breaking the free driver as well at the same time?

[TNE]

@VoidByte

Does that means that my graphic driver is broken? I guess its not like windows, where I would just uninstall and reinstall it right?

Yes, it’s broken, and what you said is almost always accurate, but not with DKMS, so give that a shot: sudo pacman -S nvidia-dkms

@VoidByte

On the other side… why is nouveau failing then? I mean, an update that crash one driver might happen for Proprietary Drivers, but breaking the free driver as well at the same time?

The nouveau driver is added to the blacklist on purpose so it’s not loaded instead of the Nvidia module.

[VoidByte]

That did the trick! Thank you very much for your help guys!