I drop into a tty after booting in.

jabuxa · 2022-02-02 00:58:15

My systems boots into a tty no matter what I do, I have already tried removing the symlink between sddm.service and /etc/systemd/system/display-manager.service.

I have tried going in all tty's and when i do chvt 7, I get into a black screen with a blinking dot and nothing else, which is supposed to be sddm since I have specified in /etc/sddm.conf.d/tty.conf that it needs to start in "Minimum VT=7".

This is stressing me out a little bit, I have tried installing other display managers, and it doesn't work.

startx gives me an error saying connection refused, I have written in my .xinitrc "exec dwm" which should work, even though I'm using plasma primarily, but it is not working. Any help?

DeathStar · 2022-02-02 01:13:04

My best guess would be that you do not have your graphics driver setup correctly since startx says connection refused. Are you using Nvidia, ATI or Intel graphics? Try installing xf86-video-intel for Intel graphics or the appropriate Nvidia or ATI packages for your hardware. Also, is mesa installed by chance?

jabuxa · 2022-02-02 01:15:41

DeathStar wrote:

My best guess would be that you do not have your graphics driver setup correctly since startx says connection refused. Are you using Nvidia, ATI or Intel graphics? Try installing xf86-video-intel for Intel graphics or the appropriate Nvidia or ATI packages for your hardware. Also, is mesa installed by chance?

I'm 99% sure I have my drivers installed correctly. I should say that I was using my desktop normally and gaming until 5 hours ago. I turned off my computer and now he doesn't boot up correctly. I also have intel microcodes installed and nvidia proprietary drivers (dkms) properly set up.

V1del · 2022-02-02 08:03:43

Did this use to work? If you didn't enable the sddm.service then this wouldn't surprise me.

The nvidia drivers got updated to 510 recently. Did you put them into your initramfs as a early KMS loading measure and did you ensure to update that, either via the corresponding hook or by manually running

mkinitcpio -P

?

If it's neither of those you need to post more information. Even though xorg "fails" to start it will likely have written a xorg log in /var/log/Xorg.0.log and you can still post a

sudo journalctl -b

regardless.

https://wiki.archlinux.org/title/List_o … n_services

Last edited by V1del (2022-02-02 08:05:24)

jabuxa · 2022-02-02 14:01:40

mkinitcpio -P didn't really solve anything, and I think it might be something with nvidia, I'm trying to see if I maybe installed it wrong or didn't do something right.

pastebin of sudo journalctl -b

http://sprunge.us/m2HIgw

V1del · 2022-02-02 14:11:02

The nvidia kernel module is loaded that's fine and working. There's no attempt at starting SDDM. How exactly did you configure it and which instructions did you follow to configure it? Which instructions did you follow to install Arch in general?

Maybe throw in

pacman -Qs nvidia

Something that's definitely wrong and can lead to all sorts of weird shit, you have dhcpcd and NetworkManager enabled and started at the same time, don't do that, if you expect to have a applet in a GUI when you eventually get there, disable and stop dhcpcd.

seth · 2022-02-02 14:12:14

That boot defaults to the multi-user.target and never attempts the graphical.target.
There're no blatant issues, though.
Please post the most recent xorg log.

jabuxa · 2022-02-02 14:22:27

I disabled dhcpcd, somethings got mixed up because I followed the arch wiki when installing + a video of someone doing an install on physical hardware.

I enabled sddm with systemctl enable sddm.service (or something like that), I have to remember you that it was working fine yesterday, I probably did something wrong or idk.

pacman -Qs nvidia -> http://sprunge.us/4Zz2wv

There is attempt at starting SDDM.

journalctl -u sddm -> http://sprunge.us/yJHu27

jabuxa · 2022-02-02 14:26:20

seth wrote:

That boot defaults to the multi-user.target and never attempts the graphical.target.
There're no blatant issues, though.
Please post the most recent xorg log.

cat /var/log/Xorg.0.log - > http://sprunge.us/9ntnke

and after pacman -Syyu, startx works, it is initializing dwm when I type startx. but I still can't find a way to make my sddm work.

Last edited by jabuxa (2022-02-02 14:40:58)

seth · 2022-02-02 15:28:54

https://wiki.archlinux.org/title/NVIDIA … de_setting - parameter AND initramfs modules.
In doubt post the updated xorg log (from startx/dwm)

jabuxa · 2022-02-02 17:13:49

seth wrote:

https://wiki.archlinux.org/title/NVIDIA … de_setting - parameter AND initramfs modules.
In doubt post the updated xorg log (from startx/dwm)

Hey, I changed my grub configuration and added nvidia-drm.modeset=1 to the GRUB_CMDLINE_LINUX_DEFAULT line, and sddm doesn't start yet, dwm works.

log: http://sprunge.us/NiT2H3

seth · 2022-02-02 17:29:05

That's from a server that ran sucessfully for ~1s
SDDM likely crashes (unrelated to the server), check the system journal and coredumpctl

jabuxa · 2022-02-02 18:31:30

coredumpctl gave me http://sprunge.us/dytCMT

~/.local/share/xorg/Xorg.0.log -> http://sprunge.us/IsIHNf

system journal: http://sprunge.us/rCUcdF

Last edited by jabuxa (2022-02-02 18:32:27)

seth · 2022-02-02 20:16:11

No SDDM coredump, but http://sprunge.us/rCUcdF doesn't boot the graphical target (and there's no attempt being made to start SDDM either)
You can access older journals, eg. "sudo journalctl -b -2" for the second to last one.

jabuxa · 2022-02-02 20:25:16

sudo journalctl -u sddm -> http://sprunge.us/aHNxSs

I think I'll just fresh install, this is too complicated and I don't think it can be solved.

seth · 2022-02-02 20:28:01

The last sddm service was started 24h ago…

pacman -Qikk sddm

jabuxa · 2022-02-02 20:38:44

seth wrote:

The last sddm service was started 24h ago…
pacman -Qikk sddm

http://sprunge.us/tP0EnY

satura · 2022-02-02 20:49:34

Was plasma working prior to your .xinitrc configuration?
Also, please include your full .xinitrc. Try to remove anything which isn't default from the config file, and see if you get the X window manager when you do "startx". If that works, then perhaps try to bring up dwm from the tty.
It looks like various things are configured incorrectly. Your X server and your sddm could be configured incorrectly. Posting Xorg logs and other relevant information would be very helpful in narrowing down the issue.

seth · 2022-02-02 20:52:54

SDDM is intact, have you tried to start it ("sudo systemctl start sddm")?

jabuxa · 2022-02-02 22:33:56

seth wrote:

SDDM is intact, have you tried to start it ("sudo systemctl start sddm")?

Yes but it didn't bring up nothing.

satura wrote:

Was plasma working prior to your .xinitrc configuration?
Also, please include your full .xinitrc. Try to remove anything which isn't default from the config file, and see if you get the X window manager when you do "startx". If that works, then perhaps try to bring up dwm from the tty.
It looks like various things are configured incorrectly. Your X server and your sddm could be configured incorrectly. Posting Xorg logs and other relevant information would be very helpful in narrowing down the issue.

I didn't even have an .xinitrc, I created a blank one with just exec dwm.

I have fresh-installed arch linux and it is working, I have no idea what happened and no idea of how to recreate it.
Thanks for everyone that helped. I learned a lot. It was probably not the best decision for me to fresh-install it but I am in a desperate need of a working desktop right now.

headkase · 2022-02-04 04:15:56

jabuxa wrote:

seth wrote:
That boot defaults to the multi-user.target and never attempts the graphical.target.
There're no blatant issues, though.
Please post the most recent xorg log.
cat /var/log/Xorg.0.log - > http://sprunge.us/9ntnke
and after pacman -Syyu, startx works, it is initializing dwm when I type startx. but I still can't find a way to make my sddm work.

Don't use Syyu. That can leave your system in a partial-upgrade state. Which is bad, and if you keep using it you will eventually be bitten by it.

Arch Linux

#1 2022-02-02 00:58:15

I drop into a tty after booting in.

#2 2022-02-02 01:13:04

Re: I drop into a tty after booting in.

#3 2022-02-02 01:15:41

Re: I drop into a tty after booting in.

#4 2022-02-02 08:03:43

Re: I drop into a tty after booting in.

#5 2022-02-02 14:01:40

Re: I drop into a tty after booting in.

#6 2022-02-02 14:11:02

Re: I drop into a tty after booting in.

#7 2022-02-02 14:12:14

Re: I drop into a tty after booting in.

#8 2022-02-02 14:22:27

Re: I drop into a tty after booting in.

#9 2022-02-02 14:26:20

Re: I drop into a tty after booting in.

#10 2022-02-02 15:28:54

Re: I drop into a tty after booting in.

#11 2022-02-02 17:13:49

Re: I drop into a tty after booting in.

#12 2022-02-02 17:29:05

Re: I drop into a tty after booting in.

#13 2022-02-02 18:31:30

Re: I drop into a tty after booting in.

#14 2022-02-02 20:16:11

Re: I drop into a tty after booting in.

#15 2022-02-02 20:25:16

Re: I drop into a tty after booting in.

#16 2022-02-02 20:28:01

Re: I drop into a tty after booting in.

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

Re: I drop into a tty after booting in.

#18 2022-02-02 20:49:34

Re: I drop into a tty after booting in.

#19 2022-02-02 20:52:54

Re: I drop into a tty after booting in.

#20 2022-02-02 22:33:56

Re: I drop into a tty after booting in.

#21 2022-02-04 04:15:56

Re: I drop into a tty after booting in.

Board footer