after update, I failed to startx

Snorlax · 2022-02-18 15:30:47

then I reinstalled the system on the root with the original /home preserved, the problem persists......

my Xorg.0.log

https://cdn.discordapp.com/attachments/ … 231849.jpg

https://cdn.discordapp.com/attachments/ … 231902.jpg

https://cdn.discordapp.com/attachments/ … 231911.jpg

https://cdn.discordapp.com/attachments/ … 231928.jpg

https://cdn.discordapp.com/attachments/ … 231941.jpg

https://cdn.discordapp.com/attachments/ … 231951.jpg

https://cdn.discordapp.com/attachments/ … 232004.jpg

https://cdn.discordapp.com/attachments/ … 232021.jpg

https://cdn.discordapp.com/attachments/ … 232029.jpg

wondering what to do. I installed all the missing ones from the log according to my search results before the reinstall. nothing changed. and I was only able to startx after installing nvidia proprietary driver....... but it sucks....... been stuck on this for a day...... buds I need help

Last edited by Snorlax (2022-02-19 03:43:17)

Scimmia · 2022-02-18 15:33:12

I don't see any problems with X. What are you seeing, exactly?

V1del · 2022-02-18 15:36:25

Remove the superfluous cry for help from the title. I can't actually look at these images on the network I'm currently on but if these are your xorg log scrolled page by page as actual pictures then for the love of $DEITY use a pastebin client: https://wiki.archlinux.org/title/List_o … n_services

"Installing all the missing ones" is almost certainly the wrong approach to whatever the issue is.

Could look at the pictures now, as stated there's no issue in that xorg.0.log post

sudo journalctl -b

instead, refer to the link above for how to properly paste that.

Last edited by V1del (2022-02-18 19:16:46)

Snorlax · 2022-02-19 03:38:35

V1del wrote:

Remove the superfluous cry for help from the title. I can't actually look at these images on the network I'm currently on but if these are your xorg log scrolled page by page as actual pictures then for the love of $DEITY use a pastebin client: https://wiki.archlinux.org/title/List_o … n_services
"Installing all the missing ones" is almost certainly the wrong approach to whatever the issue is.
Could look at the pictures now, as stated there's no issue in that xorg.0.log post
sudo journalctl -b
instead, refer to the link above for how to properly paste that.

ty http://ix.io/3Q0B

Snorlax · 2022-02-19 03:40:34

maybe it's an Intel graphics issue? when I do 'systemctl status' I found X server was actually running: http://ix.io/3Q0C

Trilby · 2022-02-19 04:01:07

Snorlax wrote:

maybe it's an Intel graphics issue?

Is there an intel graphics card? In the first post, you alluded to using nvidia. Is this a hybrid graphics system? If so, have you followed the wiki page(s) for hybrid graphics setups?

But before actually digging into all that, you should answer the questions you've already been asked: what are you seeing? What is the problem?

Snorlax · 2022-02-19 04:49:49

Trilby wrote:

Snorlax wrote:
maybe it's an Intel graphics issue?
Is there an intel graphics card? In the first post, you alluded to using nvidia. Is this a hybrid graphics system? If so, have you followed the wiki page(s) for hybrid graphics setups?
But before actually digging into all that, you should answer the questions you've already been asked: what are you seeing? What is the problem?

frozen screen, when I switch to another tty and switch back, I see a black screen and won't be able to switch to another tty again

seth · 2022-02-19 07:31:40

i915 isn't in the journal.
How do you start the graphical.target? startx? Post your xinitrc.
There's a bunch of unresolvable autostart services.

I was only able to startx after installing nvidia proprietary driver

You're currently running on nouveau?

Snorlax · 2022-02-19 09:06:32

seth wrote:

i915 isn't in the journal.
How do you start the graphical.target? startx? Post your xinitrc.
There's a bunch of unresolvable autostart services.
I was only able to startx after installing nvidia proprietary driver
You're currently running on nouveau?

startx
my xinitrc: http://ix.io/3Q1P
actually now I can't even startx after installing nvidia things......

seth · 2022-02-19 12:39:10

The xinitrc is broken (see the last link below) and I guess the problem is starting i3.

actually now I can't even startx after installing nvidia things

Do you have an updated xorg log?

Freso · 2022-02-19 13:49:59

If you're using proprietary nvidia drivers, there's a known issue with xorg-server: see https://bbs.archlinux.org/viewtopic.php?id=271450 and https://bugs.archlinux.org/task/73875

Try out 21.1.3-5 from [testing] which should fix it for you. If it doesn't, please drop a comment in https://bugs.archlinux.org/task/73875 letting Andreas know.

Snorlax · 2022-02-19 16:19:40

seth wrote:

The xinitrc is broken (see the last link below) and I guess the problem is starting i3.
actually now I can't even startx after installing nvidia things
Do you have an updated xorg log?

I backup my old one and used

cp /etc/X11/xinit/xinitrc ~/.xinitrc

, then startx still failed to work.

the new xinitrc: http://ix.io/jmE
Xorg.0.log: http://ix.io/3Q49

Trilby · 2022-02-19 16:29:52

Snorlax wrote:

I backup my old one and used ...

Yeah, that wouldn't be expected to do much given that you presumably don't have twm / xterm installed. And the output of the xorg log supports this while also suggesting that it "worked" just fine; the server started, ran, and exited successfully. You really need to read the relevant wiki pages rather than just taking random stabs at solutions. You should also actually tell us about your hardware and which video drivers you formerly used and / or intend to use as this thread is full of would-be-helpers taking wild guesses or offering conditional solutions (e.g., "if this is a nvidia system...").

In my previous post I asked several questions to gather relevant information. While I did emphasize one as a priority, I didn't mean all the others should be ignored.

Last edited by Trilby (2022-02-19 16:31:14)

Snorlax · 2022-02-20 05:20:21

Trilby wrote:

Snorlax wrote:
I backup my old one and used ...
Yeah, that wouldn't be expected to do much given that you presumably don't have twm / xterm installed. And the output of the xorg log supports this while also suggesting that it "worked" just fine; the server started, ran, and exited successfully. You really need to read the relevant wiki pages rather than just taking random stabs at solutions. You should also actually tell us about your hardware and which video drivers you formerly used and / or intend to use as this thread is full of would-be-helpers taking wild guesses or offering conditional solutions (e.g., "if this is a nvidia system...").
In my previous post I asked several questions to gather relevant information. While I did emphasize one as a priority, I didn't mean all the others should be ignored.

yes, there's an Intel graphic card. I've followed the wiki. and maybe it's a hardware problem now?

the output of lspci: http://ix.io/3Q7e
lscpu: http://ix.io/3Q7g
sudo lshw: http://ix.io/3Q7i
I used nouveau, because with that proprietary driver multi screen feature is not supported.

seth · 2022-02-20 08:27:11

1. fix you xinitrc. correctly.
Don't stroll random processes in there that cannot be executed since they're not installed, but make sure to include the systemd bits
2. Run startx, see what happens and post the resulting xorg log if there're still issues
3. "because with that proprietary driver multi screen feature is not supported" is complete nonsense, factually wrong and false.

Snorlax · 2022-02-20 08:47:04

seth wrote:

1. fix you xinitrc. correctly.
Don't stroll random processes in there that cannot be executed since they're not installed, but make sure to include the systemd bits
2. Run startx, see what happens and post the resulting xorg log if there're still issues
3. "because with that proprietary driver multi screen feature is not supported" is complete nonsense, factually wrong and false.

log: http://ix.io/3Q7X
xinitrc now: http://ix.io/3Q7Y
sudo systemctl status: http://ix.io/3Q81

Last edited by Snorlax (2022-02-20 08:56:42)

seth · 2022-02-20 09:02:38

That server ran for ~2 minutes on the modesetting driver - you do get an xterm? What would be the remaining issues?
Edid: yes you do.

Last edited by seth (2022-02-20 09:03:20)

Snorlax · 2022-02-20 09:42:39

seth wrote:

That server ran for ~2 minutes on the modesetting driver - you do get an xterm? What would be the remaining issues?
Edid: yes you do.

the same as before, frozen tty without any xterm there

seth · 2022-02-20 12:55:52

So, try installing the nvidia blob, see whether that helps and then we'll focus on the misconception that you cannot have a multiscreen setup this way.
Also post the system journal for a boot w/ "frozen" X11 server so we can look out for nouveau kernel errors.

V1del · 2022-02-20 13:34:59

Note that if you try to go for the nvidia blob you'd have to opt for nvidia-470xx set of packages from the AUR as you have a kepler GPU. use the DKMS package and make sure to install linux-headers.

Snorlax · 2022-02-20 14:05:33

okay, just installed nvidia packages except nvidia-settings (gtk/gtk.h: No such file or directory, but it installed gtk2 dependency before compilation).

system journal for a boot(with nvidia installed): http://ix.io/3Q9o (this time startx still failed)

seth · 2022-02-20 14:18:24

Feb 20 13:50:44 simputer kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13
Feb 20 13:50:44 simputer kernel: ACPI: SSDT 0x00000000BEFCB000 0019EF (v01 HPQOEM NVIDIAGF 00000001 INTL 20110112)
Feb 20 13:50:44 simputer systemd-modules-load[276]: Failed to find module 'nvidia-uvm'
…
Feb 20 13:51:26 simputer sudo[1848]:      sim : TTY=tty1 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/pacman -S
Feb 20 13:51:29 simputer dbus-daemon[383]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.12' (uid=0 pid=1851 comm="sudo pacman -S nvidia ")
Feb 20 13:51:29 simputer sudo[1851]:      sim : TTY=tty1 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/pacman -S nvidia
Feb 20 13:51:43 simputer sudo[1853]:      sim : TTY=tty1 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/rm /var/lib/pacman/db.lck
Feb 20 13:51:47 simputer sudo[3222]:      sim : TTY=tty1 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/pacman -S --asdeps inetutils gtk2
Feb 20 13:53:02 simputer dbus-daemon[383]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.15' (uid=0 pid=6389 comm="sudo /usr/bin/pacman -U /home/sim/mhwd-nvidia-470x")
Feb 20 13:53:02 simputer sudo[6389]:      sim : TTY=tty1 ; PWD=/home/sim/mhwd-nvidia-470xx ; USER=root ; COMMAND=/usr/bin/pacman -U /home/sim/mhwd-nvidia-470xx/mhwd-nvidia-470xx-470.94-1-any.pkg.tar.zst
Feb 20 14:00:04 simputer sudo[7929]:      sim : TTY=tty2 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/journalctl --boot
Feb 20 14:03:01 simputer sudo[7936]:      sim : TTY=tty2 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/journalctl --boot
Feb 20 14:03:01 simputer sudo[7936]: pam_unix(sudo:session): session opened for user root(uid=0) by sim(uid=1000)

No you didn't.
https://aur.archlinux.org/packages/nvidia-470xx-dkms
https://aur.archlinux.org/packages/nvidia-470xx-utils
and optionally https://aur.archlinux.org/packages/nvid … x-settings

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

Lone_Wolf · 2022-02-20 14:21:20

edit : ninja'ed by seth

Last edited by Lone_Wolf (2022-02-20 14:21:50)

Snorlax · 2022-02-20 14:29:31

seth wrote:

Feb 20 13:50:44 simputer kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13
Feb 20 13:50:44 simputer kernel: ACPI: SSDT 0x00000000BEFCB000 0019EF (v01 HPQOEM NVIDIAGF 00000001 INTL 20110112)
Feb 20 13:50:44 simputer systemd-modules-load[276]: Failed to find module 'nvidia-uvm'
…
Feb 20 13:51:26 simputer sudo[1848]:      sim : TTY=tty1 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/pacman -S
Feb 20 13:51:29 simputer dbus-daemon[383]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.12' (uid=0 pid=1851 comm="sudo pacman -S nvidia ")
Feb 20 13:51:29 simputer sudo[1851]:      sim : TTY=tty1 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/pacman -S nvidia
Feb 20 13:51:43 simputer sudo[1853]:      sim : TTY=tty1 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/rm /var/lib/pacman/db.lck
Feb 20 13:51:47 simputer sudo[3222]:      sim : TTY=tty1 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/pacman -S --asdeps inetutils gtk2
Feb 20 13:53:02 simputer dbus-daemon[383]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.15' (uid=0 pid=6389 comm="sudo /usr/bin/pacman -U /home/sim/mhwd-nvidia-470x")
Feb 20 13:53:02 simputer sudo[6389]:      sim : TTY=tty1 ; PWD=/home/sim/mhwd-nvidia-470xx ; USER=root ; COMMAND=/usr/bin/pacman -U /home/sim/mhwd-nvidia-470xx/mhwd-nvidia-470xx-470.94-1-any.pkg.tar.zst
Feb 20 14:00:04 simputer sudo[7929]:      sim : TTY=tty2 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/journalctl --boot
Feb 20 14:03:01 simputer sudo[7936]:      sim : TTY=tty2 ; PWD=/home/sim/nvidia-470xx-settings ; USER=root ; COMMAND=/usr/bin/journalctl --boot
Feb 20 14:03:01 simputer sudo[7936]: pam_unix(sudo:session): session opened for user root(uid=0) by sim(uid=1000)

No you didn't.
https://aur.archlinux.org/packages/nvidia-470xx-dkms
https://aur.archlinux.org/packages/nvidia-470xx-utils
and optionally https://aur.archlinux.org/packages/nvid … x-settings

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

I did, I really did.
sudo pacman -Qi nvidia-470xx-dkms nvidia-470xx-utils: http://ix.io/3Q9w
the install dates are before the boot

seth · 2022-02-20 14:30:57

dkms status

Edit, since you're booting the lts kernel: https://archlinux.org/packages/core/x86 … s-headers/

Last edited by seth (2022-02-20 14:31:38)

Arch Linux

#1 2022-02-18 15:30:47

after update, I failed to startx

#2 2022-02-18 15:33:12

Re: after update, I failed to startx

#3 2022-02-18 15:36:25

Re: after update, I failed to startx

#4 2022-02-19 03:38:35

Re: after update, I failed to startx

#5 2022-02-19 03:40:34

Re: after update, I failed to startx

#6 2022-02-19 04:01:07

Re: after update, I failed to startx

#7 2022-02-19 04:49:49

Re: after update, I failed to startx

#8 2022-02-19 07:31:40

Re: after update, I failed to startx

#9 2022-02-19 09:06:32

Re: after update, I failed to startx

#10 2022-02-19 12:39:10

Re: after update, I failed to startx

#11 2022-02-19 13:49:59

Re: after update, I failed to startx

#12 2022-02-19 16:19:40

Re: after update, I failed to startx

#13 2022-02-19 16:29:52

Re: after update, I failed to startx

#14 2022-02-20 05:20:21

Re: after update, I failed to startx

#15 2022-02-20 08:27:11

Re: after update, I failed to startx

#16 2022-02-20 08:47:04

Re: after update, I failed to startx

#17 2022-02-20 09:02:38

Re: after update, I failed to startx

#18 2022-02-20 09:42:39

Re: after update, I failed to startx

#19 2022-02-20 12:55:52

Re: after update, I failed to startx

#20 2022-02-20 13:34:59

Re: after update, I failed to startx

#21 2022-02-20 14:05:33

Re: after update, I failed to startx

#22 2022-02-20 14:18:24

Re: after update, I failed to startx

#23 2022-02-20 14:21:20

Re: after update, I failed to startx

#24 2022-02-20 14:29:31

Re: after update, I failed to startx

#25 2022-02-20 14:30:57

Re: after update, I failed to startx

Board footer