[SOLVED] X server does not start

Myphis · 2023-12-20 15:38:36

Hello,
I installed Bspwm-git and effectively il was in conflict with Bspwm, so I confirmed to delete Bspwm, just after this I was redirected to display manager, and I can not any more to start xinit. Any idea?

I tried to start x server like this
startx — -keeptty > ~/.xorg.log 2>&1

In the file I have the following
‘Failed to connect to bus: Connection refused
dbus-update-activation-environment: error: unable to connect to D-Bus:Failed to connect to socket /run/user/1000/bus: connection refused
1
2
3
4
5
[..]
2750
pkill: killing pid 1 failed: Operation not permited
pkill: killing pid 2 failed: Operation not permited
pkill: killing pid 3 failed: Operation not permited
[…]
pkill: killing pid 2750 failed: Operation not permited

Last edited by Myphis (2023-12-23 20:30:26)

seth · 2023-12-20 20:31:04

Please post the entire log, your xinitrc and

pacman -Ql bspwm-git

Myphis · 2023-12-21 09:45:48

My entire log https://termbin.com/5gqj
My .xinitrc https://termbin.com/nssj
My .xserverrc https://termbin.com/fwad
My pacman https://termbin.com/91dq

If it is important I use zsh
.zprofile https://termbin.com/pzs26

Strange thing for me is even if I start x server from another tty I got logout

Last edited by Myphis (2023-12-21 10:31:24)

seth · 2023-12-21 12:45:49

My entire log https://termbin.com/5gqj

Not sure what exactly that is, but /var/log/Xorg.8.log suggests it's from an xwayland instance?

just after this I was redirected to display manager, and I can not any more to start xinit

What exactly is "display manager" and where do you try to run "xinit"?

Please post your complete system journal for the boot:

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

Myphis · 2023-12-21 13:13:08

seth wrote:

My entire log https://termbin.com/5gqj
Not sure what exactly that is, but /var/log/Xorg.8.log suggests it's from an xwayland instance?
just after this I was redirected to display manager, and I can not any more to start xinit
What exactly is "display manager" and where do you try to run "xinit"?
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

So, I tried to reinstall os, but I have the same issue.
Display manager is ly.

.xinitrc is in my user home directory, .xinit and .xserverrc are executable

My new .xorg.log https://termbin.com/dboe
My Xorg.0.log https://termbin.com/t8xm
My boot journal https://termbin.com/vddy

seth · 2023-12-21 13:22:30

Display manager is ly.

Start by not using that. It systematically breaks the session bus.
Also why do you have that ~/.zprofile stanza if you're using ly anyway?

But again: disable ly, log into a console session an either have the zprofile run stratx or run it manually.

Myphis · 2023-12-21 13:30:54

seth wrote:

Display manager is ly.
Start by not using that. It systematically breaks the session bus.
Also why do you have that ~/.zprofile stanza if you're using ly anyway?
But again: disable ly, log into a console session an either have the zprofile run stratx or run it manually.

Done, but always black screen without cursor or else…

seth · 2023-12-21 14:06:05

If you "exec xterm" instead of bspwm, do you get the expected xterm?
If you inspect the running server from a different terminal, what does "xrandr -display :0 -q" show?

Myphis · 2023-12-21 17:09:59

seth wrote:

If you "exec xterm" instead of bspwm, do you get the expected xterm?
If you inspect the running server from a different terminal, what does "xrandr -display :0 -q" show?

I could get bspwm and terminal but only if in .zprofile

exec startx  — -keeptty > .xorg.log 2>&1

If not I still got login terminal after login

This is log when I could enter https://0x0.st/HguV.txt

You can see that I have DP-4 and None-1-1. It was the same before, and for exemple my desktops in poly bar had issue with this, because they think that None-1-1 is monitor too. I will try to disable it

UPDATE

So I can confirme that I can access my session only if .zprofile contains

startx — -keeptty

Here is

xrandr -d :0 -q

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

Update
Just in case here are my files now
.xinitrc https://termbin.com/fgqh
.xserverrc https://termbin.com/1vrk
My .zprofile is now like this https://termbin.com/z36h

Last edited by Myphis (2023-12-21 19:35:24)

seth · 2023-12-21 20:23:23

That is not your xorg log, you'll find that in /var/log/Xorg.0.log
The "none" output is typically linked to the simpledrm device, so please post the actual Xorg log.

I could get bspwm and terminal but only if in .zprofile
…
If not I still got login terminal after login

I've no idea what you're trying to say => https://deep.com
But your xinitrc doesn't execute an xterm, so I suspect you're talking about a(nother) linux console, not a terminal emulator within the graphical session?

Myphis · 2023-12-21 20:44:30

seth wrote:

That is not your xorg log, you'll find that in /var/log/Xorg.0.log
The "none" output is typically linked to the simpledrm device, so please post the actual Xorg log.
I could get bspwm and terminal but only if in .zprofile
…
If not I still got login terminal after login
I've no idea what you're trying to say => https://deep.com
But your xinitrc doesn't execute an xterm, so I suspect you're talking about a(nother) linux console, not a terminal emulator within the graphical session?

I will try explain, so yes, when I say that after login I get login terminal I mean I stay in Linux console, nothing changes.
I blocked this ghost device within /etc/X11/xorg.config.d

Section "Monitor"
    Identifier "None-1-1"
    Option "Ignore" "true"
EndSection

My current Xorg.0.log with in -keeptty option for x server https://termbin.com/s2dn

seth · 2023-12-21 20:49:53

I blocked this ghost device

remove that and enable https://wiki.archlinux.org/title/NVIDIA … de_setting
If that alone desn't already fix it (check the xorg log that the simpledrm device is gone and the kernel paramters show up) the plan was to

pacman -S xterm # you don't need to re-install it, just make sure it's there

and alter the xinitrc

…

# 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 xterm
# exec bspwm

and then startx in normal fashion and see whether you get an xterm there.

Myphis · 2023-12-21 21:08:43

seth wrote:

I blocked this ghost device
remove that and enable https://wiki.archlinux.org/title/NVIDIA … de_setting
If that alone desn't already fix it (check the xorg log that the simpledrm device is gone and the kernel paramters show up) the plan was to
pacman -S xterm # you don't need to re-install it, just make sure it's there
and alter the xinitrc
…

# 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 xterm
# exec bspwm
and then startx in normal fashion and see whether you get an xterm there.

I put modeset=1 to kernel parameter.
No, I can not get xterm.
Xorg logs https://termbin.com/ypxf I see here that my xorg config for None-1-1 monitor is still here, but I deleted this one
And journalctl -b https://termbin.com/t6ak

Last edited by Myphis (2023-12-21 21:23:23)

seth · 2023-12-21 21:26:11

[    48.375] Kernel command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img cryptdevice=PARTUUID=4df4ad4e-79d0-46ec-8097-4644fa3a43f6:root root=/dev/mapper/root rw rootfstype=btrfs

You did NOT add the kernel parameter as as a consequence

[    48.380] (II) Platform probe for /sys/devices/platform/simple-framebuffer.0/drm/card0

the simpledrm device is still there.

And for the journal

Dec 21 22:03:59 lotis kernel: Command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img cryptdevice=PARTUUID=4df4ad4e-79d0-46ec-8097-4644fa3a43f6:root root=/dev/mapper/root rw rootfstype=btrfs modeset=1

that's the wrong parameter.

Myphis · 2023-12-21 22:10:02

seth wrote:

[    48.375] Kernel command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img cryptdevice=PARTUUID=4df4ad4e-79d0-46ec-8097-4644fa3a43f6:root root=/dev/mapper/root rw rootfstype=btrfs

And for the journal

Dec 21 22:03:59 lotis kernel: Command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img cryptdevice=PARTUUID=4df4ad4e-79d0-46ec-8097-4644fa3a43f6:root root=/dev/mapper/root rw rootfstype=btrfs modeset=1

that's the wrong parameter.

Can you tell me, I should add both, modest and fbdev?

Last edited by Myphis (2023-12-21 22:33:07)

seth · 2023-12-21 22:13:27

No you have not. I don't have to tell you that, the logs do.
The correct parameters are "nvidia_drm.modeset=1 nvidia_drm.fbdev=1"
You do understand that deepl.com is an AI translator that will allow you to understand the wiki (given your native tongue is covered by it)?

Also please stop full-quoting, you're just bloating the thread.

Myphis · 2023-12-21 22:33:53

seth wrote:

[    48.375] Kernel command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img cryptdevice=PARTUUID=4df4ad4e-79d0-46ec-8097-4644fa3a43f6:root root=/dev/mapper/root rw rootfstype=btrfs

And for the journal

Dec 21 22:03:59 lotis kernel: Command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img cryptdevice=PARTUUID=4df4ad4e-79d0-46ec-8097-4644fa3a43f6:root root=/dev/mapper/root rw rootfstype=btrfs modeset=1

I do not understand how is it possible that the kernel parameter are not the same in xorg logs and journalctl…
As per Wiki For nvidia driver version < 545, the nvidia_drm.modeset=1 option must be set through kernel parameters, in order to disable simpledrm, my driver is > 545 so I thought that parameters should be as I mentioned earlier. Thank you for help

Last edited by Myphis (2023-12-21 22:35:29)

seth · 2023-12-21 22:40:13

The xorg log might be from a previous boot if you didn't attempt to startx after the change.
Either way, fix the parameters, reboot and check the impact.

Myphis · 2023-12-21 23:16:27

seth wrote:

The xorg log might be from a previous boot if you didn't attempt to startx after the change.
Either way, fix the parameters, reboot and check the impact.

This is startx logs https://termbin.com/74jx
Journalctl -b https://termbin.com/3w40
And Xorg.0.log https://termbin.com/v5snj

It is worth, my screen blinks and then I am in Linux consol again

Last edited by Myphis (2023-12-21 23:20:46)

Myphis · 2023-12-21 23:32:12

Can I solve this issue from Xorg logs. Failed to bind sideband socket to '/var/run/nvidia-xdriver-5bc3b5f7' Permission denie with this /usr/lib/tmpfiles.d

d /run/nvidia-xdriver 0770 root users

seth · 2023-12-22 08:58:34

Your problem is this here:

Dec 22 00:06:39 lotis kernel: NVRM: Xid (PCI:0000:01:00): 62, pid='<unknown>', name=<unknown>, 2029904c 20297840 20297996 202961a4 202967be 202937d4 00000000 00000000
Dec 22 00:07:25 lotis kernel: NVRM: Xid (PCI:0000:01:00): 109, pid=2173, name=Xorg, Ch 00000008, errorString CTX SWITCH TIMEOUT, Info 0x44000
Dec 22 00:07:31 lotis kernel: NVRM: Xid (PCI:0000:01:00): 109, pid=1495, name=(udev-worker), Ch 00000002, errorString CTX SWITCH TIMEOUT, Info 0x24002
Dec 22 00:09:21 lotis kernel: NVRM: Xid (PCI:0000:01:00): 109, pid=2293, name=Xorg, Ch 00000008, errorString CTX SWITCH TIMEOUT, Info 0x44000

XID 62 is hardware, driver or thermal issue, https://docs.nvidia.com/deploy/xid-errors/index.html
There've been a bunch of issues w/ the 545xx drivers, so you might want to try to downgrade to 535xx-dkms and 535xx-utils
https://wiki.archlinux.org/title/Arch_Linux_Archive
https://wiki.archlinux.org/title/Dkms

Also check the temperature levels (is this a notebook?)

Myphis · 2023-12-22 10:29:47

seth wrote:

There've been a bunch of issues w/ the 545xx drivers, so you might want to try to downgrade to 535xx-dkms and 535xx-utils
Also check the temperature levels (is this a notebook?)

Can you give me your opinion on Open source drivers as nouveau?
Yes it is laptop

Update
It did not work, I installed 535.113.01 driver, same effect, but in logs it is different
Boot logs https://termbin.com/8p0b
User Xorg logs https://termbin.com/7tn8
/var/log Xorg https://termbin.com/bbzh

In journalctl I see that my session is closed as soon as it is opened

Dec 22 12:31:44 lotis login[2111]: LOGIN ON tty1 BY myphis
Dec 22 12:31:44 lotis systemd[2133]: Started PipeWire PulseAudio.
Dec 22 12:31:44 lotis systemd[2133]: Starting Update XDG user dir configuration...
Dec 22 12:31:44 lotis systemd[2133]: Finished Update XDG user dir configuration.
Dec 22 12:31:44 lotis systemd[2133]: Starting D-Bus User Message Bus...
Dec 22 12:31:44 lotis systemd[2133]: Started D-Bus User Message Bus.
…
Dec 22 12:31:44 lotis login[2111]: pam_unix(login:session): session closed for user myphis

Last edited by Myphis (2023-12-22 13:23:20)

seth · 2023-12-22 13:39:09

The nvidia/xid errors are gone .
2nd log is dated

[    48.376] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 21 21:43:29 2023

First log is

[    45.371] (==) Log file: "/home/myphis/.local/share/xorg/Xorg.0.log", Time: Fri Dec 22 12:29:06 2023

The server ran w/o any problems for ~30s

a) is this w/ xterm or bspwm
b) "same effect" like what? "my screen blinks and then I am in Linux consol again"?
Can you then switch to (a) TTY w/ the X11 server (you cannot have a console on all TTYs because one is clearly occupied by the X11 server for 30s, that's above "blink" time)

Myphis · 2023-12-22 14:36:26

seth wrote:

The server ran w/o any problems for ~30s
a) is this w/ xterm or bspwm
b) "same effect" like what? "my screen blinks and then I am in Linux consol again"?
Can you then switch to (a) TTY w/ the X11 server (you cannot have a console on all TTYs because one is clearly occupied by the X11 server for 30s, that's above "blink" time)

I think it was w/ -keeptty option in .zprofile.
Now I rebooted and tried to log in, x server can be initiated on tty1 and tty2, from tty5 I login w/o problem.
Non, now I do not have blinking screen. But I stay in console after login and prompted to login again

New journalctl https://termbin.com/necj
.zprofile https://termbin.com/a0o6

Last edited by Myphis (2023-12-22 14:44:16)

seth · 2023-12-22 14:41:19

So, is there any remaining issue?

Arch Linux

#1 2023-12-20 15:38:36

[SOLVED] X server does not start

#2 2023-12-20 20:31:04

Re: [SOLVED] X server does not start

#3 2023-12-21 09:45:48

Re: [SOLVED] X server does not start

#4 2023-12-21 12:45:49

Re: [SOLVED] X server does not start

#5 2023-12-21 13:13:08

Re: [SOLVED] X server does not start

#6 2023-12-21 13:22:30

Re: [SOLVED] X server does not start

#7 2023-12-21 13:30:54

Re: [SOLVED] X server does not start

#8 2023-12-21 14:06:05

Re: [SOLVED] X server does not start

#9 2023-12-21 17:09:59

Re: [SOLVED] X server does not start

#10 2023-12-21 20:23:23

Re: [SOLVED] X server does not start

#11 2023-12-21 20:44:30

Re: [SOLVED] X server does not start

#12 2023-12-21 20:49:53

Re: [SOLVED] X server does not start

#13 2023-12-21 21:08:43

Re: [SOLVED] X server does not start

#14 2023-12-21 21:26:11

Re: [SOLVED] X server does not start

#15 2023-12-21 22:10:02

Re: [SOLVED] X server does not start

#16 2023-12-21 22:13:27

Re: [SOLVED] X server does not start

#17 2023-12-21 22:33:53

Re: [SOLVED] X server does not start

#18 2023-12-21 22:40:13

Re: [SOLVED] X server does not start

#19 2023-12-21 23:16:27

Re: [SOLVED] X server does not start

#20 2023-12-21 23:32:12

Re: [SOLVED] X server does not start

#21 2023-12-22 08:58:34

Re: [SOLVED] X server does not start

#22 2023-12-22 10:29:47

Re: [SOLVED] X server does not start

#23 2023-12-22 13:39:09

Re: [SOLVED] X server does not start

#24 2023-12-22 14:36:26

Re: [SOLVED] X server does not start

#25 2023-12-22 14:41:19

Re: [SOLVED] X server does not start

Board footer