Troubles after update Arch.

otacmilutin · 2025-09-27 16:26:49

Today I run yay -Syu and after reboot, Arch started repeatedly to output following outputs?! (I don't know how to stop it, so I cant access journalctl.
Any idea what to do?

Output:

/deu/sdb2: clean, 3375217/45088768 files, 141658417/180355072 blocks
[FAILED] Failed to start nginx web server.
[FAILED] Failed to start nginx web server.
[FAILED] Failed to start GNOME Display Manager.
[FAILED] Failed to start nginx web server.
[FAILED] Failed to start nginx web server.
[FAILED] Failed to start nginx web server.
[FAILED] Failed to start nginx web server.
[FAILED] Failed to start nginx web server.
[FAILED] Failed to start nginx web server.
[FAILED] Failed to start nginx web server.
[FAILED] Failed to start nginx web server.
[FAILED] Failed to start nginx web server.
[FAILED] Failed to start nginx web server.
...

Last edited by otacmilutin (2025-09-27 16:29:20)

ewaller · 2025-09-27 16:41:22

Press Ctrl-Alt-F2 (or F3 thrhough F6) to change to a different console and log in.

Scimmia · 2025-09-27 16:57:02

So it's booting fine, GDM just isn't starting. Did you configure GDM to use X11? If so, you have to undo that as X11 support has been removed.

otacmilutin · 2025-09-27 18:12:03

Thanks!

No, I did not configure GDM to use X11, (I only run system update as usually: yay -Syu) but in journal I've seen X11. So, I need to remove X11?

otacmilutin · 2025-09-27 19:27:35

I've not removed X11. Just commented line in: /etc/gdm/custom.conf

#WaylandEnable=false

And restarted gdm:

sudo systemctl restart gdm

And nothing new happened after reboot.

But in journalctl I found line:

nvidia: module verification failed: signature and or required key missing - tainting kernel.

Looks like I have problem with nvidia driver... or graphic card went out of date.

seth · 2025-09-27 19:44:35

ewaller wrote:

Press Ctrl-Alt-F2 (or F3 thrhough F6) to change to a different console and log in.

Then please post your complete system journal for the boot:

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

otacmilutin · 2025-09-27 20:10:57

http://0x0.st/KaRi.txt

seth · 2025-09-27 20:34:22

The link is 404, is https://0x0.st/KaRI.txt your system?

Sep 27 21:49:07 asus-laptop kernel: nvidia 0000:01:00.0: [drm] Cannot find any crtc or sizes
Sep 27 21:50:27 asus-laptop gnome-shell[1136]: Device '/dev/dri/card0' prefers shadow buffer
Sep 27 21:50:27 asus-laptop gnome-shell[1136]: Added device '/dev/dri/card0' (nvidia-drm) using atomic mode setting.
Sep 27 21:50:29 asus-laptop gnome-shell[1136]: Device '/dev/dri/card1' prefers shadow buffer
Sep 27 21:50:29 asus-laptop gnome-shell[1136]: Added device '/dev/dri/card1' (i915) using atomic mode setting.
Sep 27 21:50:29 asus-laptop gnome-shell[1136]: Created gbm renderer for '/dev/dri/card0'
Sep 27 21:50:29 asus-laptop gnome-shell[1136]: Created gbm renderer for '/dev/dri/card1'
Sep 27 21:50:29 asus-laptop gnome-shell[1136]: GPU /dev/dri/card1 selected primary from builtin panel presence
Sep 27 21:50:29 asus-laptop gnome-shell[1136]: Obtained a high priority EGL context
Sep 27 21:50:32 asus-laptop gnome-shell[1136]: Using public X11 display :1024, (using :1025 for managed services)
Sep 27 21:50:32 asus-laptop gnome-shell[1136]: Using Wayland display name 'wayland-0'
Sep 27 21:50:32 asus-laptop gnome-shell[1136]: Couldn't find suitable cursor plane format for /dev/dri/card0, disabling HW cursor

Looks like you're running on the intel chip (nvidia module loads fine, though), there's no output on the nvidia chip but there's absolutely no

[FAILED] Failed to start GNOME Display Manager.

?
There're some named problems?

otacmilutin · 2025-09-27 21:22:24

It seems works now. After reboot it took too long time to system start. So I tried to switch terminal. But, now it looks works fine. named works. But all works much slower than before.
Maybe Wayland works slower (I never use Wayland before). No big deal, it works now!

Thanks a lot!

otacmilutin · 2025-09-27 21:23:37

named -v
BIND 9.20.13 (Stable Release) <id:1f79fb9>

seth · 2025-09-28 07:35:15

But all works much slower than before.

glxinfo -B

Do you still have X11 logs around to see whether you maybe ran on the nvidia GPU?

otacmilutin · 2025-09-28 17:58:11

Not sure. But i found X11 in some lines in journalcta (last session).

Related to command you asked, here is what wrote:

glxinfo -B       
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) HD Graphics 4600 (HSW GT2) (0x416)
    Version: 25.2.3
    Accelerated: yes
    Video memory: 1536MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 4600 (HSW GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.2.3-arch1.2
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.2.3-arch1.2
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.2.3-arch1.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Last edited by otacmilutin (2025-09-28 18:14:43)

otacmilutin · 2025-09-28 18:02:47

sudo journalctl -b > KaRi1.txt

...
Sep 28 19:36:10 asus-laptop dbus-broker-launch[1232]: Ready
Sep 28 19:36:10 asus-laptop gnome-shell[1156]: Using public X11 display :1024, (using :1025 for managed services)
Sep 28 19:36:10 asus-laptop gnome-shell[1156]: Using Wayland display name 'wayland-0'
Sep 28 19:36:10 asus-laptop gnome-shell[1156]: Couldn't find suitable cursor plane format for /dev/dri/card1, disabling HW cursor
Sep 28 19:36:15 asus-laptop systemd[1037]: Created slice Slice /app/dbus-:1.10-org.a11y.atspi.Registry.
...

Last edited by otacmilutin (2025-09-28 18:15:19)

seth · 2025-09-28 18:03:25

Please use [code][/code] tags. Edit your post in this regard.

You're currently running on the intel intel chip (what's normal on hybrid systems)
Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

otacmilutin · 2025-09-28 18:05:10

yap. Sorry. I forgot code mark.

seth · 2025-09-28 18:06:43

"code", not "quote" - but the X11 log is currently more relevant as to why things might be "slow" (then we'll need some metric on this)

otacmilutin · 2025-09-28 18:48:05

Log in: ~.local/share/xorg/Xorg.1.log is pretty big. Is there way to upload file instead paste log source?
(this log is one day old. New log Xorg.0.log does not exist there.

Last edited by otacmilutin (2025-09-28 18:51:28)

seth · 2025-09-28 18:51:16

1st link below

cat ~/.local/share/xorg/Xorg.1.log | curl -F 'file=@-' 0x0.st

but you'd usually look for Xorg.0.log - look into the file and check the log date to make sure this isn't from 2015 or so

Last edited by seth (2025-09-28 18:51:29)

otacmilutin · 2025-09-28 18:52:40

http://0x0.st/KBM4.txt

seth · 2025-09-28 18:55:12

Nope, that's regular prime.

But all works much slower than before.

Mind to elaborate?

otacmilutin · 2025-09-28 18:57:21

Or maybe my laptop is entered age to be retired.

# System Details Report
---

## Report details
- **Date generated:**                              2025-09-28 20:55:24

## Hardware Information:
- **Hardware Model:**                              ASUSTeK COMPUTER INC. N750JK
- **Memory:**                                      12.0 GiB
- **Processor:**                                   Intel® Core™ i5-4200H × 4
- **Graphics:**                                    Intel® HD Graphics 4600 (HSW GT2)
- **Disk Capacity:**                               774.2 GB

## Software Information:
- **Firmware Version:**                            N750JK.203
- **OS Name:**                                     Arch Linux
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               49
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.16.8-arch3-1

otacmilutin · 2025-09-28 19:02:18

seth wrote:

Nope, that's regular prime.
But all works much slower than before.
Mind to elaborate? ;)

Huh... long story. After turn laptop on, it took times longer to system start.
Firefox need much more time to load.
VS Code need ~20s to appear on display.
etc.

But, It maybe normal after many changes in last update. Have no idea.

Last edited by otacmilutin (2025-09-28 19:05:30)

otacmilutin · 2025-09-28 19:17:01

Maybe errors like following (not only) cause slow system up?
Obviously something in BIOS I need to change.

...
Sep 28 19:34:29 asus-laptop kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x00000000E) is beyond end of object (length 0xE) (20250404/exoparg2-393)
Sep 28 19:34:29 asus-laptop kernel: ACPI Error: Aborting method \_SB.PCI0.XHC.RHUB.HS15._PLD due to previous error
...

...
Sep 28 19:34:41 asus-laptop kernel: input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input19
Sep 28 19:34:41 asus-laptop kernel: asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19
Sep 28 19:34:41 asus-laptop kernel: asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -19
Sep 28 19:34:41 asus-laptop kernel: asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19
Sep 28 19:34:41 asus-laptop kernel: asus_wmi: using asus-wmi for asus::kbd_backlight
Sep 28 19:34:41 asus-laptop kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Sep 28 19:34:41 asus-laptop kernel: cfg80211: failed to load regulatory.db
Sep 28 19:34:41 asus-laptop kernel: spi-nor spi0.0: supply vcc not found, using dummy regulator
Sep 28 19:34:41 asus-laptop kernel: spi-nor spi0.0: probe with driver spi-nor failed with error -22
...

seth · 2025-09-28 19:23:00

You can blacklist spi-nor but I doubt that's relevant and I doubt that the symptoms in #22 are related to gnome/wayland.
Please post your complete system journal for the boot:

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

and the output of "echo $DBUS_SESSION_BUS_ADDRESS"

And see whether "MOZ_ENABLE_WAYLAND=0 firefox" vs. "MOZ_ENABLE_WAYLAND=1 firefox" makes a difference resp. force VSCode to use a native wayland client, https://wiki.archlinux.org/title/Chromi … er_Wayland (ignore symtoms and VSCode is the same as chromium itr. All electron)

otacmilutin · 2025-09-28 19:33:08

sudo journalctl -b -20 | curl -F 'file=@-' 0x0.st (just in case I put 20).

http://0x0.st/KBSa.txt

Arch Linux

#1 2025-09-27 16:26:49

Troubles after update Arch.

#2 2025-09-27 16:41:22

Re: Troubles after update Arch.

#3 2025-09-27 16:57:02

Re: Troubles after update Arch.

#4 2025-09-27 18:12:03

Re: Troubles after update Arch.

#5 2025-09-27 19:27:35

Re: Troubles after update Arch.

#6 2025-09-27 19:44:35

Re: Troubles after update Arch.

#7 2025-09-27 20:10:57

Re: Troubles after update Arch.

#8 2025-09-27 20:34:22

Re: Troubles after update Arch.

#9 2025-09-27 21:22:24

Re: Troubles after update Arch.

#10 2025-09-27 21:23:37

Re: Troubles after update Arch.

#11 2025-09-28 07:35:15

Re: Troubles after update Arch.

#12 2025-09-28 17:58:11

Re: Troubles after update Arch.

#13 2025-09-28 18:02:47

Re: Troubles after update Arch.

#14 2025-09-28 18:03:25

Re: Troubles after update Arch.

#15 2025-09-28 18:05:10

Re: Troubles after update Arch.

#16 2025-09-28 18:06:43

Re: Troubles after update Arch.

#17 2025-09-28 18:48:05

Re: Troubles after update Arch.

#18 2025-09-28 18:51:16

Re: Troubles after update Arch.

#19 2025-09-28 18:52:40

Re: Troubles after update Arch.

#20 2025-09-28 18:55:12

Re: Troubles after update Arch.

#21 2025-09-28 18:57:21

Re: Troubles after update Arch.

#22 2025-09-28 19:02:18

Re: Troubles after update Arch.

#23 2025-09-28 19:17:01

Re: Troubles after update Arch.

#24 2025-09-28 19:23:00

Re: Troubles after update Arch.

#25 2025-09-28 19:33:08

Re: Troubles after update Arch.

Board footer