# Screen blanks, refuses input after login

**URL:** <https://forum.endeavouros.com/t/screen-blanks-refuses-input-after-login/76396>\
**Category:** Kernel, boot, graphics & hardware\
**Created:** [November 15, 2025, 12:08pm UTC](https://forum.endeavouros.com/t/screen-blanks-refuses-input-after-login/76396 "2025-11-15T12:08:59Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kompaktcat](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/k/59ef9b/32.png) [@kompaktcat](https://forum.endeavouros.com/u/kompaktcat)\
**Post date:** [November 15, 2025, 12:08pm UTC](https://forum.endeavouros.com/t/screen-blanks-refuses-input-after-login/76396/1 "2025-11-15T12:08:59Z")

</div>

Recently did a fresh install following the instructions of a fix posted here:

[Nvidia GPU users attention please! [June 2025]](https://forum.endeavouros.com/t/nvidia-gpu-users-attention-please-june-2025/72058)

As every time password is entered on SDDM, the cursor turns to an X, the screen turns off, and the computer refuses all input. Entering rescue mode and reinstalling the nvidia-open and nvidia-utils packages did NOT fix the issue either.

System is a laptop running an i71065G7 and Nvidia GTX 1650.

I used LTS on my previous install prior to nuke and paving trying to finally fix this problem after days of poring over troubleshooting sections on Arch Wiki. This is extremely frustrating to fight with, but the previous thread was closed/locked. Installing nouveau-vulkan did NOT fix the issue either.

---

<div class="post-metadata">

**Author:** ![1093i3511](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/1093i3511/32/102376_2.png) [@1093i3511](https://forum.endeavouros.com/u/1093i3511)\
**Post date:** [November 15, 2025, 1:23pm UTC](https://forum.endeavouros.com/t/screen-blanks-refuses-input-after-login/76396/2 "2025-11-15T13:23:44Z")

</div>

I recently had the same issue, but more likely due to the fact that I’m using the ALHP repositories and some packages of Qt are still not within those. Thus there has been a version mismatch between those packages which weren’t already updated within the ALHP.

Anyway, to troubleshoot this, you could switch to a different tty (e.g. `crlt` + `alt` + `f3` for the tty 3) and login into your shell environment to either manually launch sddm or to check your journals via `journalctl -b 0 -p 3` which would directly show the errors in the current session ( `-b 0` specifies the boot context, `-p 3` would omit all warnings and other non-critical warnings)

---

<div class="post-metadata">

**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\
**Post date:** [November 15, 2025, 6:27pm UTC](https://forum.endeavouros.com/t/screen-blanks-refuses-input-after-login/76396/3 "2025-11-15T18:27:26Z")

</div>

> [@kompaktcat](#):
>
> Recently did a fresh install following the instructions of a fix posted here:
> 
> [Nvidia GPU users attention please! [June 2025]](https://forum.endeavouros.com/t/nvidia-gpu-users-attention-please-june-2025/72058)

# **ISO is hot fixed, you should not have the issue as long as you have internet connection. [new installs]**

it says there.. from testing and reports there should be no issue ion current ISO as its hotfixed.  
If so it could be about blocking in your country causing hotfix to not get applied.. in case there is a rebuild ISO with latest packages including all fixes:

> **[Release Weekly Rebuild 2025.11.13 · endeavouros-team/Weekly-ISO-Rebuilds](https://github.com/endeavouros-team/Weekly-ISO-Rebuilds/releases/tag/latest)**
>
> Download this 4 files into one folder:
> 
> EndeavourOS\_Mercury-Neo-2025.11.13-x86\_64.iso.split-aa
> EndeavourOS\_Mercury-Neo-2025.11.13-x86\_64.iso.split-ab
> EndeavourOS\_Mercury-Neo-2025.11.13-x86\_64.iso.s...

---

<div class="post-metadata">

**Author:** ![kompaktcat](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/k/59ef9b/32.png) [@kompaktcat](https://forum.endeavouros.com/u/kompaktcat)\
**Post date:** [November 16, 2025, 9:16am UTC](https://forum.endeavouros.com/t/screen-blanks-refuses-input-after-login/76396/4 "2025-11-16T09:16:05Z")

</div>

Hey hi, tried the hotfix ISO and it STILL hitting this problem. I can’t pull journalctl because there’s nothing to be done with the computer once the screen blanks except turn it off. Going back to LTS I guess?

---

<div class="post-metadata">

**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\
**Post date:** [November 16, 2025, 9:40am UTC](https://forum.endeavouros.com/t/screen-blanks-refuses-input-after-login/76396/5 "2025-11-16T09:40:30Z")

</div>

youn installed with nvidia option or default boot from ISO?

> [@kompaktcat](#):
>
> i71065G7 and Nvidia GTX 1650

Has [Intel Iris Plus Graphics](https://www.intel.com/content/www/us/en/products/sku/196597/intel-core-i71065g7-processor-8m-cache-up-to-3-90-ghz/specifications.html)

So mostlikely this is optimus hybrid system.  
It will by default boot with the nvidia gpu disabled, on the igpu.

Nvidia GTX 1650 = NV160 family (Turing) = basically nvidia-open modules compatible.

And even if you can not load X you can try switching to TTY Ctrl+Alt+F4 or [boot without graphical interface](https://discovery.endeavouros.com/system-rescue/how-to-boot-without-a-graphical-environment/2021/03/)

Boot journal could show what is gone wrong `journalctl -b -0` or if you go install LTS from TTY and you are able to boot to X with that show the previous boot journal `journalctl -b -1 | eos-sendlog` Always remind thazt boot jotnal can contain some UUIDS or serials you may not want to post public.. in case send me PM with the url so i can check and its not directly linked to you here.

---

<div class="post-metadata">

**Author:** ![kompaktcat](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/k/59ef9b/32.png) [@kompaktcat](https://forum.endeavouros.com/u/kompaktcat)\
**Post date:** [December 10, 2025, 9:27am UTC](https://forum.endeavouros.com/t/screen-blanks-refuses-input-after-login/76396/6 "2025-12-10T09:27:19Z")

</div>

Hello.  
If I switch to a TTY instead of logging into Plasma wayland via SDDM, the system remains functional and will even boot into x11 properly, to my knowledge. However plasma-wayland specifically will lock out the computer and kill all input. This problem began sometime around kernel 6.15.x this summer and I cannot find a resolution.

I installed nvidia-open and nvidia-utils as specified in the hotfix directions and this problem has persisted through a fresh install.

LTS kernel works fine on 6.12.x, I can use plasma-wayland normally.

I will attempt to pull journalctl logs this week to see if there’s anything diagnosable in them (or pass them to someone that can)
