#Display goes black or sleep after login

1 messages · Page 1 of 1 (latest)

silent vessel
#

Installed fine, no errors on install. I’m using a Razer Blade Stealth 13 so hybrid Nvidia GPU 1650 GTX.

I’m able to login, and then once it fully loads the screen just goes black, it seems as if the display goes to sleep, but nothing wakes it…

Any ideas? Including ‘journalctl -b -p err’ output as well. Then I tried troubleshooting via Grok and may have made it worse 😂

silent vessel
#

After many experiments of using GDM, disabling all forms of hibernate/sleep/suspend… I still have no luck…

Is a Razer Stealth 13 - 2019 just completely incompatible with Omarchy?

sweet ivy
#

I am experiencing similar symptoms.. CTL-ALT-F2 gets to a terminal

fallen ember
#

Did you used manual method? Omarchy works best with SDDM. So having GDM before omarchy script will conflict.
And SGX is disabled, enable it from your BIOS.

silent vessel
#

CTL-Alt-F2 does not work when it’s “hibernated”.

I have to edit the boot config and add “single” to the end to access TTY

GDM I did after Omarchy when nothing was working.

What is SGX I don’t think have that in BIOS menu?

silent vessel
#

So Omarchy + Razer Blade Stealth late 2019 == fucked

1.    Install went fine, but after login the laptop instantly suspends (blinking green LED).
2.    Kernel/driver stack good (6.16.8-arch3-1, nvidia-dkms, headers, limine-mkinitcpio, nvidia-smi works).
3.    TTY is stable, but graphical.target or Hyprland → immediate suspend. Masking sleep/hibernate + editing logind.conf didn’t help.
4.    GDM failed (suspend loop), SDDM + GNOME/Plasma works fine but double-login with Omarchy’s seamless-login service.
5.    Tried manuall installation: curl -fsSL https://omarchy.org/install | bash → configs installed, but Hyprland sessions (via seamless-login or dbus-run-session Hyprland) still instantly suspend.

GNOME/Plasma sessions are stable, but Hyprland on Omarchy always suspends/hibernates on this hardware.

woven field
#

I’m confused why you have GDM or SDDM here. Omarchy is not meant to live alongside anything else so the fact that you have these tells me you likely installed on top of some OS setup that’s unsupported and leading to these issues.

silent vessel
#

I only tried those as alternative display managers since Omarchy kept hibernating my laptop

#

I downloaded the ISO first, after login, screen goes dark can’t do anything…

Troubleshooted within that for awhile and then ChatGPT steered me towards using other DMs to see if that was the issue…

I also tried booting directly into Omarchy and skipping the login event since Razer blades have been known to trigger lid close or something with arch that puts it into hibernate.

No luck on any of those fronts so then to try to understand a root case I tried other DMs and managed to get one working to at least show a UI, then reverted back. Did a wipe and another clean install manually, same issue.

#

Trust me I’ve been desperately trying to get this working over the past 4 days and now finally just gave up… the install blew my battery the first time and corrupted my SSD. Bought a new battery and a new SSD and spent probably 6-8 hours in total troubleshooting and researching to no avail…

woven field
#

Ah..that makes more sense.

#

On a fresh install, are you able to get to TTY2 after boot by chance?

#

you could do it by getting to limine boot loader and hitting e on the entry then just adding nomodeset to the kernelcmd

#

If that works, we'll want to get that added to /etc/default/limine and run sudo limine-update so it persists

silent vessel
#

bro whnat.....

#

I swear i had done that in the past!

#

ofc it fuckin worked lmao

#

I think maybe the full ISO install it didnt work when i tried, but after cleaning and doing a manual install it seems to have done the trick

#

not sure what would be the diff exactly but damn ty!!

silent vessel
#

strange... so after having it work, i decided to remove the sddm and gdm stuff that I installed along with plasma and now, i'm stuck back in that loop...

Something I did in my troubleshooting + the nomodeset change works... I just have no idea what...

#

nomodeset now boots into a terminal no GUI

woven field
#

I wonder if the seamless login got messed up along the way with the SDDM / GDM stuff?

#

You could try something like source $OMARCHY_PATH/install/login/plymouth.sh and it should try to set it all back for you

silent vessel
#

Well it wasnt working before I tried the SDDM/GDM stuff, then after I experimented with those and added your nomodeset flag it worked... Then i stupidly was like okay let me remove that bloat since they are no longer in use and now it's broken again lol...

#

Honestly, the new battery cant even charge anyway... I'm thinking this laptop is just done... Sad I'll have to postpone Omarchy, but maybe eventually I'll get a Framework 13

#

i cant sink anymore time into this lol its driving me nuts

woven field
#

Yeah. It's likely one of those took over in the process and was helping prop it up but with so many changes, it's honestly hard to say for sure. Sounds like in the end; it'd be getting back to normal + nomodeset on your boot flags.