You are not logged in.

Pages: 1 2

#1 2025-06-04 17:32:51

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

[SOLVED] Complete freeze when X starts after last update

This topic is Nouveau specific
Blacklisting nouveau addresses the problem of the freeze when X starts for now

Hi everyone!

I've been using Archlinux for almost two years now, but I'm still basically a "newbie" because, after the first configurations, I stopped experimenting and fortunately I've never had any major problems. I'm on the same installation and configuration for 2 years. But let me know if I have to change room for this topic.

Anyway, the day before yesterday I updated the system and everything seemed ok. But since I turned on the laptop again, I have not been able to start X anymore. The system freezes completely and I have to force shutdown because none of the key respond. The first 2 or 3 times it gave an error 

xauth: (stdin):2: unknown command "some numbers"

but the last couple of times it just froze.

In my laptop I have 2 separate internal NVMe drives where one has Arch installed and the other has Windows, so it's a dual-boot system but on two separate SSDs. Furthermore I use systemd-boot as bootloader and bspwm as WM and I set X to autostart at login.

Here some information that I hope will help:

> uname -r
6.14.9-zen1-1-zen
> lspci -knn | grep -EA3 'VGA|3D|Display'
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA107M [GeForce RTX 3050 Ti Mobile] [10de:25a0] (rev a1)
	DeviceName: NVIDIA Graphics Device
	Subsystem: Hewlett-Packard Company Device [103c:8a22]
	Kernel driver in use: nouveau
--
07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] [1002:1681] (rev c8)
	DeviceName:  Onboard IGD
	Subsystem: Hewlett-Packard Company Device [103c:8a22]
	Kernel driver in use: amdgpu
> env | grep -E 'X|DISPLAY|AUTH'
XDG_SESSION_ID=21
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_TYPE=tty
XDG_SESSION_CLASS=user
XDG_SEAT=seat0
XDG_VTNR=4
> cat /boot/loader/loader.conf
default arch.conf
timeout 0
console-mode keep
editor no
> for entry in /boot/loader/entries/*.conf; do
    sed 's/PARTUUID=\S*/PARTUUID=[REDACTED]/g' "$entry"
title Arch Linux
linux /vmlinuz-linux-zen
initrd /amd-ucode.img
initrd /initramfs-linux-zen.img
options root=PARTUUID=[REDACTED] rw quiet loglevel=3 systemd.show_status=auto nmi_watchdog=0 modprobe.blacklist=sp5100_tco rd.udev.log_level=3 btusb.enable_autosuspend=0
title Arch Linux (Fallback)
linux /vmlinuz-linux-zen
initrd /amd-ucode.img
initrd /initramfs-linux-zen-fallback.img
options root=PARTUUID=[REDACTED] rw
> ls /etc/X11/xorg.conf.d/
00-keyboard.conf
10-monitor.conf
30-touchpad.conf
> lsmod | grep -i 'drm|amdgpu|nouveau'
amdgpu              16347136  0
nouveau              3796992  0
drm_gpuvm              49152  1 nouveau
mxm_wmi                12288  1 nouveau
amdxcp                 12288  1 amdgpu
i2c_algo_bit           24576  2 amdgpu,nouveau
drm_ttm_helper         16384  3 amdgpu,nouveau
ttm                   118784  3 amdgpu,drm_ttm_helper,nouveau
drm_suballoc_helper    12288  1 amdgpu
drm_panel_backlight_quirks    12288  1 amdgpu
drm_exec               12288  3 drm_gpuvm,amdgpu,nouveau
gpu_sched              65536  2 amdgpu,nouveau
drm_buddy              24576  1 amdgpu
drm_display_helper    286720  2 amdgpu,nouveau
cec                   106496  2 drm_display_helper,amdgpu
video                  81920  2 amdgpu,nouveau
wmi                    32768  5 hp_wmi,video,wmi_bmof,mxm_wmi,nouveau
> journalctl -b -p 3 --no-pager
giu 04 11:12:43 archlinux kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.ACDC], AE_ALREADY_EXISTS (20240827/dswload2-326)
giu 04 11:12:43 archlinux kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
giu 04 11:12:43 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20240827/dswload2-162)
giu 04 11:12:43 archlinux kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
giu 04 11:12:43 archlinux kernel: hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19)
giu 04 11:12:47 archpeter (udev-worker)[450]: 1-4:1.1: /etc/udev/rules.d/91-wake-on-device.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb1/1-4/1-4:1.1/power/wakeup}="enabled", ignoring: No such file or directory
giu 04 11:12:47 archpeter (udev-worker)[435]: 1-4:1.2: /etc/udev/rules.d/91-wake-on-device.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb1/1-4/1-4:1.2/power/wakeup}="enabled", ignoring: No such file or directory
giu 04 11:12:47 archpeter (udev-worker)[450]: 1-4:1.1: /etc/udev/rules.d/91-wake-on-device.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb1/1-4/1-4:1.1/driver/1-4/power/wakeup}="enabled", ignoring: No such file or directory
giu 04 11:12:47 archpeter (udev-worker)[435]: 1-4:1.2: /etc/udev/rules.d/91-wake-on-device.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb1/1-4/1-4:1.2/driver/1-4/power/wakeup}="enabled", ignoring: No such file or directory
giu 04 11:12:47 archpeter (udev-worker)[484]: 1-4:1.0: /etc/udev/rules.d/91-wake-on-device.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb1/1-4/1-4:1.0/power/wakeup}="enabled", ignoring: No such file or directory
giu 04 11:12:47 archpeter (udev-worker)[484]: 1-4:1.0: /etc/udev/rules.d/91-wake-on-device.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb1/1-4/1-4:1.0/driver/1-4/power/wakeup}="enabled", ignoring: No such file or directory
giu 04 11:12:47 archpeter kernel: mt7921e 0000:04:00.0: sar cnt = 0
giu 04 11:30:00 archpeter systemd[778]: Failed to start Dunst notification daemon.
giu 04 11:30:00 archpeter systemd[778]: Failed to start Dunst notification daemon.
giu 04 11:30:00 archpeter systemd[778]: Failed to start Dunst notification daemon.
giu 04 11:30:00 archpeter systemd[778]: Failed to start Dunst notification daemon.
giu 04 11:30:00 archpeter systemd[778]: Failed to start Dunst notification daemon.
giu 04 11:30:00 archpeter systemd[778]: Failed to start Dunst notification daemon.

Xorg.1.log:

[  1229.269] 
X.Org X Server [REDACTED_IP]
X Protocol Version 11, Revision 0
[  1229.269] Current Operating System: Linux archpeter 6.14.9-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Thu, 29 May 2025 21:42:00 +0000 x86_64
[  1229.269] Kernel command line: initrd=\amd-ucode.img initrd=\initramfs-linux-zen.img root=PARTUUID=[REDACTED] rw quiet loglevel=3 systemd.show_status=auto nmi_watchdog=0 modprobe.blacklist=sp5100_tco rd.udev.log_level=3 btusb.enable_autosuspend=0
[  1229.269]  
[  1229.269] Current version of pixman: 0.46.0
[  1229.269] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  1229.269] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1229.269] (==) Log file: "/home/USER/.local/share/xorg/Xorg.1.log", Time: Tue Jun  3 22:17:50 2025
[  1229.270] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  1229.270] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1229.271] (==) No Layout section.  Using the first Screen section.
[  1229.271] (==) No screen section available. Using defaults.
[  1229.271] (**) |-->Screen "Default Screen Section" (0)
[  1229.271] (**) |   |-->Monitor "<default monitor>"
[  1229.271] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[  1229.271] (**) Allowing byte-swapped clients
[  1229.271] (==) Automatically adding devices
[  1229.271] (==) Automatically enabling devices
[  1229.271] (==) Automatically adding GPU devices
[  1229.271] (==) Automatically binding GPU devices
[  1229.271] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  1229.271] (WW) The directory "/usr/share/fonts/misc" does not exist.
[  1229.271] 	Entry deleted from font path.
[  1229.272] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[  1229.272] 	Entry deleted from font path.
[  1229.273] (==) FontPath set to:
	/usr/share/fonts/TTF,
	/usr/share/fonts/OTF,
	/usr/share/fonts/100dpi,
	/usr/share/fonts/75dpi
[  1229.273] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1229.273] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[  1229.273] (II) Module ABI versions:
[  1229.273] 	X.Org ANSI C Emulation: 0.4
[  1229.273] 	X.Org Video Driver: 25.2
[  1229.273] 	X.Org XInput driver : 24.4
[  1229.273] 	X.Org Server Extension : 10.0
[  1229.273] (++) using VT number 2

[  1229.274] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[  1229.276] (II) xfree86: Adding drm device (/dev/dri/card1)
[  1229.276] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/drm/card1
[  1229.279] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 12 paused 0
[  1229.280] (II) xfree86: Adding drm device (/dev/dri/card2)
[  1229.280] (II) Platform probe for /sys/devices/pci0000:00/0000:00:08.1/0000:07:00.0/drm/card2
[  1229.280] (II) systemd-logind: got fd for /dev/dri/card2 226:2 fd 13 paused 0
[  1229.287] (--) PCI: (1@0:0:0) 10de:25a0:103c:8a22 rev 161, Mem @ 0xfb000000/16777216, 0xfb00000000/4294967296, 0xfc00000000/33554432, I/O @ 0x0000f000/128, BIOS @ 0x????????/524288
[  1229.287] (--) PCI:*(7@0:0:0) 1002:1681:103c:8a22 rev 200, Mem @ 0xfc10000000/268435456, 0xfc20000000/2097152, 0xfc500000/524288, I/O @ 0x0000d000/256
[  1229.287] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[  1229.287] (II) LoadModule: "glx"
[  1229.288] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1229.291] (II) Module glx: vendor="X.Org Foundation"
[  1229.291] 	compiled for [REDACTED_IP], module version = 1.0.0
[  1229.291] 	ABI class: X.Org Server Extension, version 10.0
[  1229.291] (II) Applying OutputClass "AMDgpu" to /dev/dri/card2
[  1229.291] 	loading driver: amdgpu
[  1229.291] (==) Matched amdgpu as autoconfigured driver 0
[  1229.291] (==) Matched ati as autoconfigured driver 1
[  1229.291] (==) Matched nouveau as autoconfigured driver 2
[  1229.291] (==) Matched nv as autoconfigured driver 3
[  1229.291] (==) Matched modesetting as autoconfigured driver 4
[  1229.291] (==) Matched fbdev as autoconfigured driver 5
[  1229.291] (==) Matched vesa as autoconfigured driver 6
[  1229.291] (==) Assigned the driver to the xf86ConfigLayout
[  1229.291] (II) LoadModule: "amdgpu"
[  1229.291] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so
[  1229.292] (II) Module amdgpu: vendor="X.Org Foundation"
[  1229.292] 	compiled for [REDACTED_IP], module version = 23.0.0
[  1229.292] 	Module class: X.Org Video Driver
[  1229.292] 	ABI class: X.Org Video Driver, version 25.2
[  1229.292] (II) LoadModule: "ati"
[  1229.293] (WW) Warning, couldn't open module ati
[  1229.293] (EE) Failed to load module "ati" (module does not exist, 0)
[  1229.293] (II) LoadModule: "nouveau"
[  1229.293] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[  1229.295] (II) Module nouveau: vendor="X.Org Foundation"
[  1229.295] 	compiled for [REDACTED_IP], module version = 1.0.18
[  1229.295] 	Module class: X.Org Video Driver
[  1229.295] 	ABI class: X.Org Video Driver, version 25.2
[  1229.295] (II) LoadModule: "nv"
[  1229.295] (WW) Warning, couldn't open module nv
[  1229.295] (EE) Failed to load module "nv" (module does not exist, 0)
[  1229.295] (II) LoadModule: "modesetting"
[  1229.295] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1229.296] (II) Module modesetting: vendor="X.Org Foundation"
[  1229.296] 	compiled for [REDACTED_IP], module version = 1.21.1
[  1229.296] 	Module class: X.Org Video Driver
[  1229.296] 	ABI class: X.Org Video Driver, version 25.2
[  1229.296] (II) LoadModule: "fbdev"
[  1229.296] (WW) Warning, couldn't open module fbdev
[  1229.296] (EE) Failed to load module "fbdev" (module does not exist, 0)
[  1229.296] (II) LoadModule: "vesa"
[  1229.296] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[  1229.296] (II) Module vesa: vendor="X.Org Foundation"
[  1229.296] 	compiled for [REDACTED_IP], module version = 2.6.0
[  1229.296] 	Module class: X.Org Video Driver
[  1229.296] 	ABI class: X.Org Video Driver, version 25.2
[  1229.296] (II) AMDGPU: Driver for AMD Radeon:
	All GPUs supported by the amdgpu kernel driver
[  1229.296] (II) NOUVEAU driver 
[  1229.296] (II) NOUVEAU driver for NVIDIA chipset families :
[  1229.296] 	RIVA TNT            (NV04)
[  1229.296] 	RIVA TNT2           (NV05)
[  1229.296] 	GeForce 256         (NV10)
[  1229.296] 	GeForce 2           (NV11, NV15)
[  1229.296] 	GeForce 4MX         (NV17, NV18)
[  1229.296] 	GeForce 3           (NV20)
[  1229.296] 	GeForce 4Ti         (NV25, NV28)
[  1229.296] 	GeForce FX          (NV3x)
[  1229.296] 	GeForce 6           (NV4x)
[  1229.296] 	GeForce 7           (G7x)
[  1229.296] 	GeForce 8           (G8x)
[  1229.297] 	GeForce 9           (G9x)
[  1229.297] 	GeForce GTX 2xx/3xx (GT2xx)
[  1229.297] 	GeForce GTX 4xx/5xx (GFxxx)
[  1229.297] 	GeForce GTX 6xx/7xx (GKxxx)
[  1229.297] 	GeForce GTX 9xx     (GMxxx)
[  1229.297] 	GeForce GTX 10xx    (GPxxx)
[  1229.297] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  1229.297] (II) VESA: driver for VESA chipsets: vesa
[  1229.297] xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted)
[  1229.297] (WW) Falling back to old probe method for modesetting
[  1229.297] (EE) open /dev/dri/card0: No such file or directory
[  1229.297] (II) [drm] nouveau interface version: 1.4.0
[  1229.297] (EE) Unknown chipset: NV177
[  1229.297] (II) modeset(G0): using drv /dev/dri/card1
[  1229.297] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[  1229.297] (II) AMDGPU(0): AMDGPUPreInit_KMS
[  1229.297] (II) AMDGPU(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[  1229.297] (==) AMDGPU(0): Depth 24, (--) framebuffer bpp 32
[  1229.297] (II) AMDGPU(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[  1229.297] (==) AMDGPU(0): Default visual is TrueColor
[  1229.297] (II) Applying OutputClass "AMDgpu" options to /dev/dri/card2
[  1229.297] (==) AMDGPU(0): RGB weight 888
[  1229.297] (II) AMDGPU(0): Using 8 bits per RGB (8 bit DAC)
[  1229.297] (--) AMDGPU(0): Chipset: "AMD Radeon 680M" (ChipID = 0x1681)
[  1229.297] (II) Loading sub module "fb"
[  1229.297] (II) LoadModule: "fb"
[  1229.297] (II) Module "fb" already built-in
[  1229.297] (II) Loading sub module "dri2"
[  1229.297] (II) LoadModule: "dri2"
[  1229.297] (II) Module "dri2" already built-in
[  1229.404] (II) Loading sub module "glamoregl"
[  1229.404] (II) LoadModule: "glamoregl"
[  1229.404] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[  1229.408] (II) Module glamoregl: vendor="X.Org Foundation"
[  1229.408] 	compiled for [REDACTED_IP], module version = 1.0.1
[  1229.408] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  1229.421] (II) AMDGPU(0): glamor X acceleration enabled on AMD Radeon 680M (radeonsi, rembrandt, LLVM 19.1.7, DRM 3.61, 6.14.9-zen1-1-zen)
[  1229.421] (II) AMDGPU(0): glamor detected, initialising EGL layer.
[  1229.421] (==) AMDGPU(0): TearFree property default: auto
[  1229.421] (==) AMDGPU(0): VariableRefresh: disabled
[  1229.421] (==) AMDGPU(0): AsyncFlipSecondaries: disabled
[  1229.421] (II) AMDGPU(0): KMS Pageflipping: enabled
[  1229.421] (II) AMDGPU(0): Initializing outputs ...
[  1229.423] (II) AMDGPU(0): Output eDP using monitor section eDP
[  1229.423] (**) AMDGPU(0): Option "PreferredMode" "1920x1080_60.00"
[  1229.423] (II) AMDGPU(0): Output DisplayPort-0 has no monitor section
[  1229.423] (II) AMDGPU(0): Output DisplayPort-1 has no monitor section
[  1229.423] (II) AMDGPU(0): Output DisplayPort-2 has no monitor section
[  1229.423] (II) AMDGPU(0): Output DisplayPort-3 has no monitor section
[  1229.423] (II) AMDGPU(0): Output DisplayPort-4 has no monitor section
[  1229.423] (II) AMDGPU(0): Output DisplayPort-5 has no monitor section
[  1229.423] (II) AMDGPU(0): Output DisplayPort-6 has no monitor section
[  1229.423] (II) AMDGPU(0): Output DisplayPort-7 has no monitor section
[  1229.423] (II) AMDGPU(0): 9 crtcs needed for screen.
[  1229.429] (II) AMDGPU(0): Allocated crtc nr. 0 to this screen.
[  1229.429] (II) AMDGPU(0): Allocated crtc nr. 1 to this screen.
[  1229.429] (II) AMDGPU(0): Allocated crtc nr. 2 to this screen.
[  1229.429] (II) AMDGPU(0): Allocated crtc nr. 3 to this screen.
[  1229.429] (WW) AMDGPU(0): 9 ZaphodHeads crtcs unavailable. Some outputs will stay off.
[  1229.431] (II) AMDGPU(0): EDID for output eDP
[  1229.431] (II) AMDGPU(0): Manufacturer: BOE  Model: aad  Serial#: 0
[  1229.431] (II) AMDGPU(0): Year: 2021  Week: 34
[  1229.431] (II) AMDGPU(0): EDID Version: 1.4
[  1229.431] (II) AMDGPU(0): Digital Display Input
[  1229.431] (II) AMDGPU(0): 8 bits per channel
[  1229.431] (II) AMDGPU(0): Digital interface is DisplayPort
[  1229.431] (II) AMDGPU(0): Max Image Size [cm]: horiz.: 36  vert.: 20
[  1229.431] (II) AMDGPU(0): Gamma: 2.20
[  1229.431] (II) AMDGPU(0): No DPMS capabilities specified
[  1229.431] (II) AMDGPU(0): Supported color encodings: RGB 4:4:4 
[  1229.431] (II) AMDGPU(0): First detailed timing is preferred mode
[  1229.431] (II) AMDGPU(0): Preferred mode is native pixel format and refresh rate
[  1229.431] (II) AMDGPU(0): Display is continuous-frequency
[  1229.431] (II) AMDGPU(0): redX: 0.590 redY: 0.350   greenX: 0.340 greenY: 0.557
[  1229.431] (II) AMDGPU(0): blueX: 0.160 blueY: 0.120   whiteX: 0.313 whiteY: 0.329
[  1229.431] (II) AMDGPU(0): Manufacturer's mask: 0
[  1229.431] (II) AMDGPU(0): Supported detailed timing:
[  1229.431] (II) AMDGPU(0): clock: 367.5 MHz   Image Size:  355 x 200 mm
[  1229.431] (II) AMDGPU(0): h_active: 1920  h_sync: 2028  h_sync_end 2076 h_blank_end 2200 h_border: 0
[  1229.431] (II) AMDGPU(0): v_active: 1080  v_sync: 1090  v_sync_end 1100 v_blanking: 1160 v_border: 0
[  1229.431] (II) AMDGPU(0): Supported detailed timing:
[  1229.431] (II) AMDGPU(0): clock: 153.2 MHz   Image Size:  355 x 200 mm
[  1229.431] (II) AMDGPU(0): h_active: 1920  h_sync: 2028  h_sync_end 2076 h_blank_end 2200 h_border: 0
[  1229.431] (II) AMDGPU(0): v_active: 1080  v_sync: 1090  v_sync_end 1100 v_blanking: 1160 v_border: 0
[  1229.431] (II) AMDGPU(0): Unknown vendor-specific block 2
[  1229.431] (II) AMDGPU(0): EDID (in hex):
[  1229.431] (II) AMDGPU(0): 	00ffffffffffff0009e5ad0a00000000
[  1229.431] (II) AMDGPU(0): 	221f0104a52414780322359759578e29
[  1229.431] (II) AMDGPU(0): 	1e505400000001010101010101010101
[  1229.431] (II) AMDGPU(0): 	0101010101018e8f8018713850406c30
[  1229.431] (II) AMDGPU(0): 	aa0063c81000001ad83b801871385040
[  1229.431] (II) AMDGPU(0): 	6c30aa0063c81000001a000000000000
[  1229.431] (II) AMDGPU(0): 	00000000000000000000000000000002
[  1229.431] (II) AMDGPU(0): 	000b40ff0a3c7d3e162b7d0000000089
[  1229.431] (II) AMDGPU(0): Printing probed modes for output eDP
[  1229.431] (II) AMDGPU(0): Modeline "1920x1080_60.00"x60.0  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync (67.2 kHz UP)
[  1229.431] (II) AMDGPU(0): Modeline "1920x1080"x144.0  367.50  1920 2028 2076 2200  1080 1090 1100 1160 +hsync -vsync (167.0 kHz eP)
[  1229.431] (II) AMDGPU(0): Modeline "1920x1080"x60.0  153.20  1920 2028 2076 2200  1080 1090 1100 1160 +hsync -vsync (69.6 kHz e)
[  1229.431] (II) AMDGPU(0): Modeline "1680x1050"x144.0  367.50  1680 2028 2076 2200  1050 1090 1100 1160 +hsync -vsync (167.0 kHz e)
[  1229.431] (II) AMDGPU(0): Modeline "1280x1024"x144.0  367.50  1280 2028 2076 2200  1024 1090 1100 1160 +hsync -vsync (167.0 kHz e)
[  1229.431] (II) AMDGPU(0): Modeline "1440x900"x144.0  367.50  1440 2028 2076 2200  900 1090 1100 1160 +hsync -vsync (167.0 kHz e)
[  1229.431] (II) AMDGPU(0): Modeline "1280x800"x144.0  367.50  1280 2028 2076 2200  800 1090 1100 1160 +hsync -vsync (167.0 kHz e)
[  1229.431] (II) AMDGPU(0): Modeline "1280x720"x144.0  367.50  1280 2028 2076 2200  720 1090 1100 1160 +hsync -vsync (167.0 kHz e)
[  1229.431] (II) AMDGPU(0): Modeline "1024x768"x144.0  367.50  1024 2028 2076 2200  768 1090 1100 1160 +hsync -vsync (167.0 kHz e)
[  1229.431] (II) AMDGPU(0): Modeline "800x600"x144.0  367.50  800 2028 2076 2200  600 1090 1100 1160 +hsync -vsync (167.0 kHz e)
[  1229.431] (II) AMDGPU(0): Modeline "640x480"x144.0  367.50  640 2028 2076 2200  480 1090 1100 1160 +hsync -vsync (167.0 kHz e)
[  1229.431] (II) AMDGPU(0): EDID for output DisplayPort-0
[  1229.431] (II) AMDGPU(0): EDID for output DisplayPort-1
[  1229.431] (II) AMDGPU(0): EDID for output DisplayPort-2
[  1229.431] (II) AMDGPU(0): EDID for output DisplayPort-3
[  1229.431] (II) AMDGPU(0): EDID for output DisplayPort-4
[  1229.431] (II) AMDGPU(0): EDID for output DisplayPort-5
[  1229.431] (II) AMDGPU(0): EDID for output DisplayPort-6
[  1229.431] (II) AMDGPU(0): EDID for output DisplayPort-7
[  1229.431] (II) AMDGPU(0): Output eDP connected
[  1229.431] (II) AMDGPU(0): Output DisplayPort-0 disconnected
[  1229.431] (II) AMDGPU(0): Output DisplayPort-1 disconnected
[  1229.431] (II) AMDGPU(0): Output DisplayPort-2 disconnected
[  1229.431] (II) AMDGPU(0): Output DisplayPort-3 disconnected
[  1229.431] (II) AMDGPU(0): Output DisplayPort-4 disconnected
[  1229.431] (II) AMDGPU(0): Output DisplayPort-5 disconnected
[  1229.431] (II) AMDGPU(0): Output DisplayPort-6 disconnected
[  1229.431] (II) AMDGPU(0): Output DisplayPort-7 disconnected
[  1229.431] (II) AMDGPU(0): Using user preference for initial modes
[  1229.431] (II) AMDGPU(0): Output eDP using initial mode 1920x1080_60.00 +0+0
[  1229.431] (II) AMDGPU(0): mem size init: gart size :1d8d4e000 vram size: s:1e05a000 visible:1e05a000
[  1229.431] (==) AMDGPU(0): DPI set to (96, 96)
[  1229.431] (==) AMDGPU(0): Using gamma correction (1.0, 1.0, 1.0)
[  1229.431] (II) Loading sub module "ramdac"
[  1229.431] (II) LoadModule: "ramdac"
[  1229.431] (II) Module "ramdac" already built-in
[  1229.431] (==) modeset(G0): Depth 24, (==) framebuffer bpp 32
[  1229.431] (==) modeset(G0): RGB weight 888
[  1229.431] (==) modeset(G0): Default visual is TrueColor
[  1229.431] (II) Loading sub module "glamoregl"
[  1229.431] (II) LoadModule: "glamoregl"
[  1229.431] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[  1229.431] (II) Module glamoregl: vendor="X.Org Foundation"
[  1229.431] 	compiled for [REDACTED_IP], module version = 1.0.1
[  1229.431] 	ABI class: X.Org ANSI C Emulation, version 0.4

.xinitrc:

#!/bin/sh

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then







    xrdb -merge $sysresources

fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then







    xrdb -merge "$userresources"

fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

exec bspwm

.xserverrc

#!/bin/sh

exec /usr/bin/Xorg -nolisten tcp -nolisten local "$@" vt$XDG_VTNR -keeptty > ~/.xorg.log 2>&1

.zprofile

if [ -z "$DISPLAY" ] && [ "$XDG_VTNR" = 1 ]; then
  exec startx
fi

I haven't changed anything in the setup for a long time and before the last update everything was working fine.

Already tried
- Deleting .Xauthority to regenerate it as suggested in a topic about the error 

xauth: (stdin):2: unknown command "some numbers"

here on the forum;
- Change tty, login and then start X with 

xinit /usr/bin/bspwm -- :0 -logverbose 6

but the system freezes before showing logs;
- Starting a minimal X session with a .xinitrc with just 

exec xterm

in it, but the system still freezes.

I don't know what else to do, I don't understand what is causing the problem and I will be grateful to anyone who tries to help me to understand and solve it.

Thanks in advance!

Last edited by Peter_Parch (2025-06-27 11:26:37)

Offline

#2 2025-06-04 18:59:50

Caloway
Member
Registered: 2025-06-04
Posts: 5

Re: [SOLVED] Complete freeze when X starts after last update

I had a very similar issue not long ago with my laptop: Ryzen 7 5500U + NVIDIA RTX 3060.
After a system update, trying to start X caused the system to freeze entirely — keyboard unresponsive, no logs, just a full lockup that required a hard shutdown.

In my case, the problem was caused by the nouveau driver trying to handle the NVIDIA GPU.
Newer NVIDIA cards like the RTX 30xx/40xx are poorly supported (or not supported at all) by nouveau. X was trying to initialize both GPUs (AMD and NVIDIA), which triggered conflicts.

In the logs I saw errors like:

(EE) Unknown chipset: NV1XX
xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted)

Disabling nouveau entirely fixed the issue for me.

Here’s what I did:

  • Created a modprobe config to blacklist nouveau:

    sudo nano /etc/modprobe.d/blacklist-nouveau.conf

    With the contents:

    blacklist nouveau

  • Regenerated initramfs:

    sudo mkinitcpio -P

  • Rebooted the system and tested with:

    startx

After that, X started normally and bspwm loaded without freezing.

If you do need to use the NVIDIA card (e.g., for gaming or whatever), it’s better to:

  • Remove nouveau

  • Install the proprietary drivers: 

    sudo pacman -S nvidia nvidia-utils nvidia-settings

  • Configure proper PRIME offloading or use a tool like optimus-manager

But if you're only using the integrated GPU for daily work, blacklisting nouveau is a much simpler fix that brings back stability.

Hope that helps a little!

Offline

#3 2025-06-04 19:28:44

seth
Member
Registered: 2012-09-03
Posts: 66,183

Re: [SOLVED] Complete freeze when X starts after last update

Kernel driver in use: nouveau

https://bbs.archlinux.org/viewtopic.php?id=305727
https://gitlab.archlinux.org/archlinux/ … ote_274367

Check the journal for zink showing up, if that's not it, please post the entire journal

xf86-video-nouveau does not support that chip family and perhaps never will, but the modesetting driver would.
Incidentally using the nvidia driver would likely sidestep the mesa but and you want to remove all xf86-video-* packages except for maybe xf86-video-amdgpu.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#4 2025-06-05 00:34:59

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

Re: [SOLVED] Complete freeze when X starts after last update

Thanks for the replies folks!

Caloway wrote:

Here’s what I did:

    Created a modprobe config to blacklist nouveau:

    sudo nano /etc/modprobe.d/blacklist-nouveau.conf

    With the contents:

    blacklist nouveau

    Regenerated initramfs:

    sudo mkinitcpio -P

    Rebooted the system and tested with:

    startx

After that, X started normally and bspwm loaded without freezing.

I tried it too but unfortunately nothing changed.

seth wrote:

Check the journal for zink showing up, if that's not it, please post the entire journal

I didn't see zink in the 

journalctl -b -1

results and here is the entire journal: https://pastebin.com/Md0TcwtV

As for drivers, is nvidia-open bad too?

Offline

#5 2025-06-05 01:06:52

topcat01
Member
Registered: 2019-09-17
Posts: 197

Re: [SOLVED] Complete freeze when X starts after last update

nouveau is still being loaded. Also, please disable X autostart while testing so that you can run commands from the console to test things.

Last edited by topcat01 (2025-06-05 01:07:51)

Offline

#6 2025-06-05 07:08:10

seth
Member
Registered: 2012-09-03
Posts: 66,183

Re: [SOLVED] Complete freeze when X starts after last update

Did you run some weird sed command on that journal? Did you ask some Artificial Idiocy for it?
There's an enormous amount of irregular tokens, ranging from pci IDs to the invoked targets.
Please don't. I had to clean that junkyard to make it half-wise scan-able.
There's no sensitive data supposed to be in the journal but I feel already tempted to fingerprint and dox you just to make a point.
If you want to obfuscate stuff, put in the effort to figure a proper approach.

On topic:
nouveau is in the initramfs, you either didn't blacklist it or forgot to regenerate the initramfs.
In doubt use https://wiki.archlinux.org/title/Kernel … and_line_2

You've an Ampere chip which is supported by nvidia-open, so you can use that, yes.
But w/ the zen kernel you'll need https://archlinux.org/packages/extra/x8 … open-dkms/ - read the dkms article if you've never used the system before.

Then let's talk about

[  1229.269] (==) Log file: "/home/USER/.local/share/xorg/Xorg.1.log", Time: Tue Jun  3 22:17:50 2025

You're using the xinitrc and no DM shows up in the *doctored* journal, so the .1 log is likely not even relevant (and was ~1d old when you were originally posting yesterday)
Is there no Xorg.0.log ? (the digit is the $DISPLAY, .1 is not inherently newer than .0)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#7 2025-06-05 21:27:59

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

Re: [SOLVED] Complete freeze when X starts after last update

seth wrote:

Did you run some weird sed command on that journal? Did you ask some Artificial Idiocy for it?
There's an enormous amount of irregular tokens, ranging from pci IDs to the invoked targets.
Please don't. I had to clean that junkyard to make it half-wise scan-able.
There's no sensitive data supposed to be in the journal but I feel already tempted to fingerprint and dox you just to make a point.
If you want to obfuscate stuff, put in the effort to figure a proper approach.

I am so sorry, truly. I am mortified. I understand your point and I offer my deepest apologies. Unfortunately, yes, I asked Deepseek for the best commands to provide the right information about the problem here and it advised me to censor sensitive data. It was a terrible idea and I wish I had never done it, obviously I didn't want to complicate things for you. I really opologize for that.

seth wrote:

nouveau is in the initramfs, you either didn't blacklist it or forgot to regenerate the initramfs.
In doubt use https://wiki.archlinux.org/title/Kernel … and_line_2

I don't know what happened, I made the file blacklist-nouveau.conf with 

blacklist nouveau

inside and put it in /etc/modprobe.d/ anyway now I will add 

module_blacklist=nouveau

in my boot loader configuration file.

seth wrote:

You've an Ampere chip which is supported by nvidia-open, so you can use that, yes.
But w/ the zen kernel you'll need https://archlinux.org/packages/extra/x8 … open-dkms/ - read the dkms article if you've never used the system before.

Thank you so much! I will definitely try it after I understand if the system freezes even without Nuoveau or not.

seth wrote:

You're using the xinitrc and no DM shows up in the *doctored* journal, so the .1 log is likely not even relevant (and was ~1d old when you were originally posting yesterday)
Is there no Xorg.0.log ? (the digit is the $DISPLAY, .1 is not inherently newer than .0)

Damn, sorry but I'm afraid I've made a mess. I'll check carefully and try to understand, because I remember that Xorg.0.log had an earlier date, but as I said I think I messed up.

I will try tomorrow after work because today has been a long day.

I apologize to everyone for that mess.

Offline

#8 2025-06-05 21:36:47

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

Re: [SOLVED] Complete freeze when X starts after last update

topcat01 wrote:

please disable X autostart while testing so that you can run commands from the console to test things.

Ok, thanks. Can I do this by just commenting out all the lines in the file .zprofile?

Offline

#9 2025-06-05 22:06:54

seth
Member
Registered: 2012-09-03
Posts: 66,183

Re: [SOLVED] Complete freeze when X starts after last update

Relax, I survived and am not gonna eat you for that. I just seized the opportunity to be grumpy.
The important takeaway: don't ask LLMs for this kind of stuff - if you're worried, ask here (or at least some other human who's not bricking together some sed command based on statistical proximity)

I don't know what happened, I

…apparently did not run mkinitcpio to rebuild the initramfs?

because I remember that Xorg.0.log had an earlier date

The X11 startup might fail entirely, heed topcat01's advice to disable the X11 autostart, run "startx |& tee ~/startx.out" and avoid restarting w/ the power button.
See whether frenetically pressing ctrl+alt+del works and in doubt setup and then invoke the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (the powerbutton will prevent files from being written to disk)
That is, if you cannot sidestep this with avoiding nouveau itfp.

Can I do this by just commenting out all the lines in the file .zprofile?

Depends on what actually is in your .zprofile …

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#10 2025-06-07 22:05:05

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

Re: [SOLVED] Complete freeze when X starts after last update

seth wrote:

Relax, I survived and am not gonna eat you for that. I just seized the opportunity to be grumpy.

I understand. I'm just sorry I made things more difficult for those who are kindly trying to help me.

seth wrote:

The important takeaway: don't ask LLMs for this kind of stuff - if you're worried, ask here (or at least some other human who's not bricking together some sed command based on statistical proximity)

Lesson learned.
Anyway, sorry but I've been busy these days.

seth wrote:

…apparently did not run mkinitcpio to rebuild the initramfs?

I'm sure I did, but apparently I should have then rebooted or otherwise used 

rmmod nouveau

before trying startx again. I ran 

lsmod | grep -E 'drm|amdgpu|nouveau'

when came back to Arch and gave me this output: 

amdgpu              16347136  0
amdxcp                 12288  1 amdgpu
i2c_algo_bit           24576  1 amdgpu
drm_ttm_helper         16384  2 amdgpu
ttm                   118784  2 amdgpu,drm_ttm_helper
drm_exec               12288  1 amdgpu
gpu_sched              65536  1 amdgpu
drm_suballoc_helper    12288  1 amdgpu
drm_panel_backlight_quirks    12288  1 amdgpu
drm_buddy              24576  1 amdgpu
drm_display_helper    286720  1 amdgpu
cec                   106496  2 drm_display_helper,amdgpu
video                  81920  1 amdgpu

Anyway I also ran a 

yay -Syu

before starting testing. After rebooting I disabled X auto-start on login and, since it seems my laptop doesn't have a SysReq key, I proceeded with my fingers crossed. I ran 

startx |& tee ~/startx.out

and X starts. Here's the content of the file startx.out.
I also tried reloading Nouveau to be sure by deleting the blacklist-nouveau file and rebuilding the initramfs and X failed to start but this time without freezing. This time with the 

startx |& tee ~/startx.out

command I only got this instead: 

xauth: (stdin):2:  unknown command "f472b6887a11dbc3d78d838386cefd45"

xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

So definitely was nouveau the problem, even though it had never caused any problems until a few days ago. I will try to install nvidia-open, but for now I will only use the AMD card since I don't have any particular needs.

Anyway, does anyone have any suggestions for the numerous errors shown in the link?

Offline

#11 2025-06-08 08:45:24

seth
Member
Registered: 2012-09-03
Posts: 66,183

Re: [SOLVED] Complete freeze when X starts after last update

Your Xorg log, https://wiki.archlinux.org/title/Xorg#General will be more relevant foor the immediate problem.

[ 07/06/2025 20:28:22.749 session_init FATAL ERROR ] Another composite manager is already running
[ 07/06/2025 20:28:22.749 main FATAL ERROR ] Failed to create new session.

You're probably trying to start picom in multiple ways?

erresc: unknown str

is probably from st?
https://github.com/mrdotx/st/pull/1

even though it had never caused any problems until a few days ago

It is most likely the known mesa bug.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#12 2025-06-08 16:52:10

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

Re: [SOLVED] Complete freeze when X starts after last update

Here's the ~/.local/share/xorg/Xorg.0.log file: https://pastebin.com/nMWjbn7d

seth wrote:

You're probably trying to start picom in multiple ways?

Not as far as I know. Picom is started from the second line in the bspwmrc file:

#! /bin/sh

pgrep -x sxhkd > /dev/null || sxhkd &
pgrep -x picom > /dev/null || picom --config ~/.config/picom/picom.conf &
xsetroot -cursor_name left_ptr &
dex -a &

bspc monitor -d 1 2 3

bspc config border_width         2
bspc config window_gap          12
bspc config bottom_padding	 2
bspc config top_padding		29

bspc config split_ratio          0.52
bspc config borderless_monocle   true
bspc config gapless_monocle      true

#___BSPWM coloring___# 
bspc config focused_border_color	"#BB4808"
bspc config normal_border_color		"#946FF7"

#bspc rule -a Wrapper-2.0 state=floating border=on focus=on

#___Autostart applications___#
numlockx &
~/.config/polybar/launch.sh &
pgrep -x dunst > /dev/null || dunst &
feh --bg-scale /home/archuser/Desktop/Wallpapaers/x.jpg

Is there a way to find out if it is also started by something else?

seth wrote:

It seems like the same, yes. But to clarify this I need time because I configured st some time ago now and I have never updated it... I would do better to reinstall it and reapply the patches (because I still don't know how to update the packages that are installed with git) or change, even temporarily, the terminal emulator.

seth wrote:

It is most likely the known mesa bug.

Ok. But the command

sudo journalctl -b -1 | grep -i zink

doesn't give any results and with the update I performed yesterday, mesa has been updated to version 1:25.1.2-1, is it still buggy?

Anyway thanks for your help!

Offline

#13 2025-06-08 20:16:01

seth
Member
Registered: 2012-09-03
Posts: 66,183

Re: [SOLVED] Complete freeze when X starts after last update

is it still buggy?

https://gitlab.freedesktop.org/mesa/mesa/-/issues/13317

Please post your complete system journal for the boot: 

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

and if you can the log of a failing X11 start.

Is there a way to find out if it is also started by something else?

No, but since your bspwmrc checks for a present instance, https://wiki.archlinux.org/title/XDG_Autostart and https://wiki.archlinux.org/title/Systemd/User are the most likely contenders.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#14 2025-06-09 21:25:04

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

Re: [SOLVED] Complete freeze when X starts after last update

seth wrote:

Please post your complete system journal for the boot:

Here it is: http://0x0.st/8gC7.txt. This is not about a failed X boot, I thought about that afterwards. If I have to share the one related to a failed X boot, tell me and I'll share it.

seth wrote:

and if you can the log of a failing X11 start.

http://0x0.st/8EzX.txt However I am noticing that it no longer gives the error 'xauth: (stdin):2: unknown command'.

No, but since your bspwmrc checks for a present instance, https://wiki.archlinux.org/title/XDG_Autostart

Thank you so much! There was a picom.desktop in /etc/xdg/autostart which I should have now overwritten by adding another picom.desktop file starting with Hidden=true in ~/.config/autostart
I have also an off-topic question, because I also found other files in /etc/xdg/autostart that I don't know if they are needed, like:
at-spi-dbus-bus.desktop

[Desktop Entry]
Type=Application
Name=AT-SPI D-Bus Bus
Exec=/usr/lib/at-spi-bus-launcher --launch-immediately
OnlyShowIn=GNOME;Unity;
NoDisplay=true
AutostartCondition=GSettings org.gnome.desktop.interface toolkit-accessibility
X-GNOME-AutoRestart=true
X-GNOME-Autostart-Phase=Initialization

and xapp-sn-watcher.desktop

[Desktop Entry]
Type=Application
Name=xapp-sn-watcher
Comment=A service that provides the org.kde.StatusNotifierWatcher interface for XApps

Exec=/usr/lib/xapps/xapp-sn-watcher

X-GNOME-Autostart-Phase=Panel


Thank you so much for the help

Offline

#15 2025-06-09 21:52:26

seth
Member
Registered: 2012-09-03
Posts: 66,183

Re: [SOLVED] Complete freeze when X starts after last update

at-spi-dbus-bus.desktop is accessibility stuff (screenreaders for blind users etc)
xapp-sn-watcher.desktop is KDEs riff on system tray icons.

[    72.311] (==) Log file: "/home/arch_peter/.local/share/xorg/Xorg.0.log", Time: Mon Jun  9 22:23:13 2025
[    72.326] (--) PCI: (1@0:0:0) 10de:25a0:103c:8a22 rev 161, Mem @ 0xfb000000/16777216, 0xfb00000000/4294967296, 0xfc00000000/33554432, I/O @ 0x0000f000/128, BIOS @ 0x????????/524288
[    72.326] (--) PCI:*(7@0:0:0) 1002:1681:103c:8a22 rev 200, Mem @ 0xfc10000000/268435456, 0xfc20000000/2097152, 0xfc500000/524288, I/O @ 0x0000d000/256
[    72.338] (EE) Unknown chipset: NV177
[    72.338] (II) modeset(G0): using drv /dev/dri/card0
[    72.469] (II) AMDGPU(0): Output eDP connected
[    72.476] (EE) 
[    72.476] (EE) Backtrace:
[    72.477] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    72.477] (EE) 0: /usr/lib/Xorg (?+0x0) [0x55c39b4bbf7c]
[    72.477] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    72.477] (EE) 1: /usr/lib/libc.so.6 (?+0x0) [0x7ff004a22ef0]
[    72.477] (EE) 
[    72.477] (EE) Segmentation fault at address 0x0
[    72.477] (EE) 
Fatal server error:
[    72.477] (EE) Caught signal 11 (Segmentation fault). Server aborting
[    72.477] (EE) 
[    72.477] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    72.477] (EE) Please also check the log file at "/home/arch_peter/.local/share/xorg/Xorg.0.log" for additional information.
[    72.477] (EE) 
[    72.483] (EE) Server terminated with error (1). Closing log file.

The backtrace is unfortunately somewhat useless, but xf86-video-nouveau doesn't support your GPU, so remove that package.

This is not about a failed X boot, I thought about that afterwards.

Indeed, it's lacking any nouveau/nvidia invocatio (because nouveau is blacklisted) - since the xorg log lacks a proper backtrace, we'll have to look at the relevant journal for hopefully some trace, yes.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#16 2025-06-10 22:48:06

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

Re: [SOLVED] Complete freeze when X starts after last update

seth wrote:

at-spi-dbus-bus.desktop is accessibility stuff (screenreaders for blind users etc)
xapp-sn-watcher.desktop is KDEs riff on system tray icons.

Thank you so much.

seth wrote:

Indeed, it's lacking any nouveau/nvidia invocatio (because nouveau is blacklisted) - since the xorg log lacks a proper backtrace, we'll have to look at the relevant journal for hopefully some trace, yes.

Here it is: http://0x0.st/8ETG.txt

Offline

#17 2025-06-11 06:14:14

seth
Member
Registered: 2012-09-03
Posts: 66,183

Re: [SOLVED] Complete freeze when X starts after last update

giu 10 23:49:26 archlinux kernel: fbcon: amdgpudrmfb (fb0) is primary device
giu 10 23:49:28 archpeter systemd[1]: Reached target Graphical Interface.
giu 10 23:49:48 archpeter login[609]: LOGIN ON tty1 BY arch_peter

There're no indications of crashing display server or session afterwards?

Going from what we have in the xorg log, remove all xf86-video-* packages

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#18 2025-06-11 12:01:45

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

Re: [SOLVED] Complete freeze when X starts after last update

There're no indications of crashing display server or session afterwards?

When I delete the blacklist-nouveau file to cause X to fail, I only see this output in console:

xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Here a journal from the last failed X boot, after deleting al xf86-video-* packages: http://0x0.st/8Eup.txt

Thank you so much for the help

Offline

#19 2025-06-11 14:18:45

seth
Member
Registered: 2012-09-03
Posts: 66,183

Re: [SOLVED] Complete freeze when X starts after last update

Yes, the X11 server crashes - what does the xorg log look like right after that (hopefully w/o xf86-video-whatever we might get a useful backtrace)
However there's nothing ahead of that? The Xorg server should™ start to print some logs.

Do you btw. have https://archlinux.org/packages/extra/x8 … n-nouveau/ installed?
What happens when you first

export NOUVEAU_USE_ZINK=0
export MESA_LOADER_DRIVER_OVERRIDE=llvmpipe
startx

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#20 2025-06-11 23:42:01

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

Re: [SOLVED] Complete freeze when X starts after last update

Yes, the X11 server crashes - what does the xorg log look like right after that (hopefully w/o xf86-video-whatever we might get a useful backtrace)

Before trying I threw a yay - Syu, and this time, despite deleting the blacklist-nouveau file, X started, even though the screen was at extremely low brightness. Here is the Xorg.0.log file of that boot: http://0x0.st/8ELI.txt

Do you btw. have https://archlinux.org/packages/extra/x8 … n-nouveau/ installed?

No I haven't. Should I have?

What happens when you first

export NOUVEAU_USE_ZINK=0
export MESA_LOADER_DRIVER_OVERRIDE=llvmpipe
startx

Something strange happened after that: X started with low brightness like the previous start but polybar showed %percentage% insted of the real percentage of the battery and when I open the terminal it was unusable because the cursor was frozen. Unfortunately I lost the Xorg log because after re-adding blacklist-nouveau and reboot, while I was writing this post, the system crashed randomly. I thought I could recover that log from Xorg.0.log.old but since I had to force shutdown (my laptop doesn't have a SysRq key) that log was lost.
Anyway, in the last boot (w/o nouveau) I received another time the error 

xauth: (stdin):2:  unknown command "8c90f66e6371ad34ffff1700314f13cd"

Offline

#21 2025-06-12 05:18:42

seth
Member
Registered: 2012-09-03
Posts: 66,183

Re: [SOLVED] Complete freeze when X starts after last update

[   115.740] (II) xfree86: Adding drm device (/dev/dri/card1)
[   115.740] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/drm/card1
[   115.741] (EE) systemd-logind: failed to take device /dev/dri/card1: Invalid argument
[   115.748] (--) PCI: (1@0:0:0) 10de:25a0:103c:8a22 rev 161, Mem @ 0xfb000000/16777216, 0xfb00000000/4294967296, 0xfc00000000/33554432, I/O @ 0x0000f000/128, BIOS @ 0x????????/524288

Sure nouveau wasn't blacklisted at the time?
The chip remains completely unused by X11

Only "export NOUVEAU_USE_ZINK=0" and/or install vulkan-nouveau, MESA_LOADER_DRIVER_OVERRIDEwill ffect the AMD chip what's likely the symptoms you witness.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#22 2025-06-12 09:18:20

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

Re: [SOLVED] Complete freeze when X starts after last update

Sure nouveau wasn't blacklisted at the time?

Yes, before launching startx, after I delete the blacklist-nouveau file, I check if nouveau is loaded with lsmod | grep -E 'drm|amdgpu|nouveau'

Only "export NOUVEAU_USE_ZINK=0" and/or install vulkan-nouveau, MESA_LOADER_DRIVER_OVERRIDEwill ffect the AMD chip what's likely the symptoms you witness.

I'm so sorry but I'm not sure I understood correctly. Should I install vulkan-nouveau and then try the

export NOUVEAU_USE_ZINK=0
export MESA_LOADER_DRIVER_OVERRIDE=llvmpipe

commands again? Because the system behaved 'strangely' when I ran those commands. In addition to the battery percentage not being recognized and the terminal freezing, the enter key was not responding.
The error 

xauth: (stdin):2:  unknown command "some numbers"

still appearing on the last X starts.
Thank you so much for the supprt

Offline

#23 2025-06-12 11:24:09

seth
Member
Registered: 2012-09-03
Posts: 66,183

Re: [SOLVED] Complete freeze when X starts after last update

Installing vulkan-nouveau and exporting "NOUVEAU_USE_ZINK=0" are two different approaches to the same problem. You'd test or the other, not both together.
Stay away from MESA_LOADER_DRIVER_OVERRIDE=llvmpipe as I suspect that's causing the other breakages because it'll also affect amdgpu.

xauth: (stdin):2:  unknown command "some numbers"

Is the "some numbers" there *literal*?
Seems you copypasted some placeholder into your xinitrc, please post that file.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#24 2025-06-12 18:51:35

Peter_Parch
Member
Registered: 2025-06-04
Posts: 32

Re: [SOLVED] Complete freeze when X starts after last update

Installing vulkan-nouveau and exporting "NOUVEAU_USE_ZINK=0" are two different approaches to the same problem. You'd test or the other, not both together.

Ok, thank you.

Stay away from MESA_LOADER_DRIVER_OVERRIDE=llvmpipe as I suspect that's causing the other breakages because it'll also affect amdgpu.

I ran this command just when you ask me

What happens when you first

    export NOUVEAU_USE_ZINK=0
    export MESA_LOADER_DRIVER_OVERRIDE=llvmpipe
    startx

Is it temporary or do I need to do something to undo it?

Is the "some numbers" there *literal*?

Here it is:

xauth: (stdin):2:  unknown command "8c90f66e6371ad34ffff1700314f13cd"

Seems you copypasted some placeholder into your xinitrc, please post that file.

Here it is:

#!/bin/sh

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then







    xrdb -merge $sysresources

fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then







    xrdb -merge "$userresources"

fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

exec bspwm

I installed vulkan-nouveau, X starts just with a lower brightnes (I still don't know if it can be adjusted because I don't remember how to do it with bsowm and sxhkd). I ran a 

startx -- -logverbose 9 -verbose 9

and here is the output: http://0x0.st/8EvC.txt
Here also the Xorg.0.log: http://0x0.st/8Ewo.txt
Thanks for your time

Offline

#25 2025-06-12 21:28:24

seth
Member
Registered: 2012-09-03
Posts: 66,183

Re: [SOLVED] Complete freeze when X starts after last update

Is it temporary or do I need to do something to undo it?

The environment will not survive the shell where you exported it (logging out or rebooting will clear that, otherwise you can also https://man.archlinux.org/man/unset.n variables)

unknown command "8c90f66e6371ad34ffff1700314f13cd"

is less likely a placeholder wink
That's gonna be a stale XAuthority entry, https://bbs.archlinux.org/viewtopic.php?id=304410
It's not an issue per se, but you can have a look at the magic cookies and remove it (or your .XAuthority, is should™ be recreated automatically)

[   179.275] (II) xfree86: Adding drm device (/dev/dri/card1)
[   179.275] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/drm/card1
[   179.275] (EE) systemd-logind: failed to take device /dev/dri/card1: Invalid argument
[   179.282] (--) PCI: (1@0:0:0) 10de:25a0:103c:8a22 rev 161, Mem @ 0xfb000000/16777216, 0xfb00000000/4294967296, 0xfc00000000/33554432, I/O @ 0x0000f000/128, BIOS @ 0x????????/524288
[   179.660] (II) config/udev: Adding drm device (/dev/dri/card1)
[   179.660] (II) xfree86: Adding drm device (/dev/dri/card1)
[   179.660] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/drm/card1
[   179.660] (EE) systemd-logind: failed to take device /dev/dri/card1: Invalid argument

You cannot access the nvidia GPU (because nouveau is still blacklisted? "lsmod  | grep nouveau")

[   179.410] (II) modeset(0): glamor X acceleration enabled on AMD Radeon 680M (radeonsi, rembrandt, LLVM 20.1.6, DRM 3.63, 6.15.2-zen1-1-zen)
[   179.470] (II) modeset(0): [DRI2]   DRI driver: radeonsi
[   179.470] (II) modeset(0): [DRI2]   VDPAU driver: radeonsi
[   179.480] (II) AIGLX: Loaded and initialized radeonsi

but the AMD chip runs on radeonsi, no no problems there…

just with a lower brightnes (I still don't know if it can be adjusted

https://wiki.archlinux.org/title/Backlight

The cards are reversed, try to add "nvidia_drm.modeset=1" to the https://wiki.archlinux.org/title/Kernel_parameters (all that does is to block the simpledrm device, restore the normal card order and hopfully fix your backlight?)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

Pages: 1 2

Board footer

Powered by FluxBB