You are not logged in.

#1 2023-12-14 16:35:49

thesun
Member
Registered: 2023-12-14
Posts: 8

SDDM not working

Hello, I'm having an issue on arch: When I turn the PC on, GRUB works normally, arch boots, but, on a black screen with a _ on the top left and the cursor, instead of loading sddm like it normally does, nothing happens. And after a few seconds, mouse and keyboard stop working. This happened on the first reboot after moving my config files to here. I have installed on the pc cava, kitty, nitrogen, polybar and picom. There were already installed on it i3, kde, openbox, gnome, and hyprland.
I moved to it the config files for cava, kitty, nitrogen, polybar, i3.

Also, SSH works if I put in username and local ip. the usage seems to be really low. CPU is idling at about 0-1%.

The pc specs are xeon x5650, quadro fx 580, 8gb ram, 500gb ssd,

Can someone please help me? Thank you.

Offline

#2 2023-12-14 16:43:15

thesun
Member
Registered: 2023-12-14
Posts: 8

Re: SDDM not working

edit: I uninstalled SDDM using SSH, now it's not even getting past Loading initial ramdisk ...

Offline

#3 2023-12-14 17:21:29

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,232

Re: SDDM not working

Likely a crash in nouveau. When did this start? After a kernel update? Which? Can you restore functionality when downgrading to a known good kernel?

After "crashing" and sshing in, what's your output for

sudo journalctl -b

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

Offline

#4 2023-12-14 17:34:07

thesun
Member
Registered: 2023-12-14
Posts: 8

Re: SDDM not working

This started after I moved the .config files of cava, i3, kitty, nitrogen and polybar to the PC. Everything worked fine. Then I shut off. I turn it back on and it has this problem

I can't access SSH anymore, the OS won't even boot at all anymore after I tried to remove SDDM

Btw I installed trough archinstall

Offline

#5 2023-12-14 20:49:24

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,056

Re: SDDM not working

Try to boot the multi-user.target, in doubt along "nomodeset" (2nd linke below)
Then post your complete system journal for the previous boot:

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

If this doesn't work, you'll have to fix the system offline, ie. eg. from the install iso.

Offline

#6 2023-12-15 15:03:20

thesun
Member
Registered: 2023-12-14
Posts: 8

Re: SDDM not working

http://0x0.st/HYqz.txt
Here's the output to the command.

Offline

#7 2023-12-15 15:10:39

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,056

Re: SDDM not working

Nouveau is timing out

Dec 14 16:59:21 thesun kernel: INFO: task kworker/u32:2:58 blocked for more than 122 seconds.
Dec 14 16:59:21 thesun kernel:       Tainted: G          I        6.6.6-arch1-1 #1
Dec 14 16:59:21 thesun kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 14 16:59:21 thesun kernel: task:kworker/u32:2   state:D stack:0     pid:58    ppid:2      flags:0x00004000
Dec 14 16:59:21 thesun kernel: Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau]
Dec 14 16:59:21 thesun kernel: Call Trace:
Dec 14 16:59:21 thesun kernel:  <TASK>
Dec 14 16:59:21 thesun kernel:  __schedule+0x3e7/0x1410
Dec 14 16:59:21 thesun kernel:  schedule+0x5e/0xd0
Dec 14 16:59:21 thesun kernel:  schedule_timeout+0x151/0x160
Dec 14 16:59:21 thesun kernel:  dma_fence_default_wait+0x22a/0x280
Dec 14 16:59:21 thesun kernel:  ? __pfx_dma_fence_default_wait_cb+0x10/0x10
Dec 14 16:59:21 thesun kernel:  dma_fence_wait_timeout+0x10c/0x130
Dec 14 16:59:21 thesun kernel:  drm_atomic_helper_wait_for_fences+0x157/0x1e0
Dec 14 16:59:21 thesun kernel:  nv50_disp_atomic_commit_tail+0x89/0xa10 [nouveau 9dfef29df405a5b4c83b296e7a48dfc928cd5c33]
Dec 14 16:59:21 thesun kernel:  process_one_work+0x174/0x340
Dec 14 16:59:21 thesun kernel:  worker_thread+0x27b/0x3a0
Dec 14 16:59:21 thesun kernel:  ? __pfx_worker_thread+0x10/0x10
Dec 14 16:59:21 thesun kernel:  kthread+0xe8/0x120
Dec 14 16:59:21 thesun kernel:  ? __pfx_kthread+0x10/0x10
Dec 14 16:59:21 thesun kernel:  ret_from_fork+0x34/0x50
Dec 14 16:59:21 thesun kernel:  ? __pfx_kthread+0x10/0x10
Dec 14 16:59:21 thesun kernel:  ret_from_fork_asm+0x1b/0x30
Dec 14 16:59:21 thesun kernel:  </TASK>
Dec 14 16:59:21 thesun kernel: INFO: task Xorg:434 blocked for more than 122 seconds.
Dec 14 16:59:21 thesun kernel:       Tainted: G          I        6.6.6-arch1-1 #1
Dec 14 16:59:21 thesun kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 14 16:59:21 thesun kernel: task:Xorg            state:D stack:0     pid:434   ppid:431    flags:0x00400006
Dec 14 16:59:21 thesun kernel: Call Trace:
Dec 14 16:59:21 thesun kernel:  <TASK>
Dec 14 16:59:21 thesun kernel:  __schedule+0x3e7/0x1410
Dec 14 16:59:21 thesun kernel:  schedule+0x5e/0xd0
Dec 14 16:59:21 thesun kernel:  schedule_preempt_disabled+0x15/0x30
Dec 14 16:59:21 thesun kernel:  __ww_mutex_lock.constprop.0+0x539/0x940
Dec 14 16:59:21 thesun kernel:  drm_modeset_lock+0x91/0xe0
Dec 14 16:59:21 thesun kernel:  drm_crtc_get_sequence_ioctl+0xec/0x190
Dec 14 16:59:21 thesun kernel:  ? __pfx_drm_crtc_get_sequence_ioctl+0x10/0x10
Dec 14 16:59:21 thesun kernel:  drm_ioctl_kernel+0xcd/0x170
Dec 14 16:59:21 thesun kernel:  drm_ioctl+0x26d/0x4b0
Dec 14 16:59:21 thesun kernel:  ? __pfx_drm_crtc_get_sequence_ioctl+0x10/0x10
Dec 14 16:59:21 thesun kernel:  nouveau_drm_ioctl+0x5a/0xb0 [nouveau 9dfef29df405a5b4c83b296e7a48dfc928cd5c33]
Dec 14 16:59:21 thesun kernel:  __x64_sys_ioctl+0x97/0xd0
Dec 14 16:59:21 thesun kernel:  do_syscall_64+0x60/0x90
Dec 14 16:59:21 thesun kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Dec 14 16:59:21 thesun kernel:  ? do_syscall_64+0x6c/0x90
Dec 14 16:59:21 thesun kernel:  ? do_syscall_64+0x6c/0x90
Dec 14 16:59:21 thesun kernel:  ? do_syscall_64+0x6c/0x90
Dec 14 16:59:21 thesun kernel:  ? do_syscall_64+0x6c/0x90
Dec 14 16:59:21 thesun kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Dec 14 16:59:21 thesun kernel: RIP: 0033:0x7fd04ec013af
Dec 14 16:59:21 thesun kernel: RSP: 002b:00007ffe5fd2b940 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Dec 14 16:59:21 thesun kernel: RAX: ffffffffffffffda RBX: 00007ffe5fd2ba30 RCX: 00007fd04ec013af
Dec 14 16:59:21 thesun kernel: RDX: 00007ffe5fd2b9d0 RSI: 00000000c018643b RDI: 0000000000000012
Dec 14 16:59:21 thesun kernel: RBP: 00007ffe5fd2b9d0 R08: 000055575eef2060 R09: 000055575f823590
Dec 14 16:59:21 thesun kernel: R10: 000055575fc368f0 R11: 0000000000000246 R12: 00000000c018643b
Dec 14 16:59:21 thesun kernel: R13: 0000000000000012 R14: 00007ffe5fd2ba30 R15: 000055575eef2dd0
Dec 14 16:59:21 thesun kernel:  </TASK>

Do you have xf86-video-nouveau installed?

pacman -Qs nouveau

(try to remove it)

You could still try the 340xx drivers, https://wiki.archlinux.org/title/NVIDIA … ed_drivers

Offline

#8 2023-12-15 15:38:16

thesun
Member
Registered: 2023-12-14
Posts: 8

Re: SDDM not working

Pacman -Qs nouveau gives out no output, and pacman -R nouveau says it can't find it

Offline

#9 2023-12-15 15:46:50

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,056

Re: SDDM not working

The complete package name would have been xf86-video-nouveau.
If you don't want to use the 340xx drivers you could resort to the LTS kernel and hope that a future mesa update fixes this or try your luck w/ the xf86-video-nouveau driver

Oh, and

Dec 14 16:55:20 thesun kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

Enable https://wiki.archlinux.org/title/NVIDIA … de_setting and in doubt add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters (it doesn't matter that you're not using the nvidia drivers, it's just a hack to get rid of the simplydumb dummy device)

Offline

Board footer

Powered by FluxBB