#Omarchy will not move past initial splash screen or archiso login messages on HP Omen

73 messages · Page 1 of 1 (latest)

wintry oxide
#

Installation method: ISO v3.0.2
Install Location: [PC | W11] HP Omen Transcend 16
CPU: Intel i7-14700HX
GPU(s): Intel UHD & Nvidia GeForce RTX 4060 Laptop

Preinstall steps completed:

  • Disabled Secure Boot
  • Disabled TPM
  • Disabled Device Encryption (prevents having to enter Bitlocker recovery key on startup every time while TPM is disabled)
  • Disabled Fast Startup aka Fast Boot
  • Selected GPU in BIOS is the NVIDIA card (this is machine default)

I am trying to completely wipe windows on my laptop and replace it with Omarchy. I have previously installed Omarchy via ISO v3.0.1 on my HP Z440 workstation and it was a breeze. No issues other than disabling secure boot for that machine.

For my laptop, I have tried almost every ISO boot method I could find in previous posts. This includes these approaches:

  • Simple flash with balenaEtcher
  • Using Rufus (GPT partition scheme - tried with both normal and DD options)
  • Using Ventoy (grub boot - tried to add "nomodeset" as this seemed to help others when it came to installing Omarchy on windows systems with an Nvidia card, not sure if I did it right tbh)

I have been switching attempts and cleaning off the USB drive each time using a combo of dd and windows diskpart.

No matter what I do, I can never even make it to the Omarchy configuration screen. I am either stuck at the "Omarchy" splash screen with no entry options or my laptop enters a command line display with the attached logs and never moves on (two separate cmdline hang issues, the one with Archiso login is from the Rufus non-DD; when I tried DD, it was simply a blank cli screen with a blinking underscore cursor in the top left corner).
Can someone please help? I really would like to use this on my machine and some of my freelance teams are moving to require this for our stack

wintry oxide
#

UPDATE:
I tried again with balenaEtcher and simply waited instead of being impatient with the splash screen. The installer went again to the "archiso login" display and redid that once or twice, then the install failed(I think?) with the attached logs.
I could not gather more info as the system would not respond to any input from my keyboard.

You can see that some of the stack trace towards the top was blanked out for some reason, as if there was some form of graphic or other text in front of it that disappeared. There are also some lines lower on the page where you can tell that there was other text there that was cut off or pasted over. I'm really not sure what to do at this point

shell mural
#

install base arch then omarchy on top of it

wintry oxide
# shell mural Manual install

is that like install arch via ISO and then Omarchy ISO on top of that? or arch ISO -> install omarchy via package management

shell mural
#

It's the curl command in their manual installation section

wintry oxide
#

I know I read somewhere that the errors I'm getting could be from not having arch linux on my system but if that was a requirement what is even the point of the .iso for omarchy? @shell mural

shell mural
#

I haven't installed omarchy via the image, so I don't know what might be the issue

#

It's far easier to do a manual installation at this point

wintry oxide
#

feels like it would be

#

alright I'll just do that I suppose

#

ill let you know how it goes

shell mural
#

Sure

shell mural
#

do use deepseek or any other agents if you're stuck, or don't understand anything

#

especially the encryption section

#

You can tag me, as well

wintry oxide
#

@shell mural figured it out after about 12 hours of banging my head against a wall last night. Turns out that to run any arch-based installer on my specific PC model (HP Omen Transcend) I had to add boot parameters to it, specifically “noapic” and/or “pci=nobar”. Was silently going into kernel panic every time previously and this allowed me to run the archinstall. I also had to add them to limine.conf cmdline for it to boot any time after that, even with Omarchy now running

#

Side note, my laptop touchpad is now disabled so I’m working on fixing that

shell mural
#

but why exactly?

#

so basically the kernel doesn't support your hardware?

wintry oxide
#

Not just arch but any Linux

shell mural
shell mural
wintry oxide
#

Apparently many Omens have an ACPI/interrupt routing bug that causes kernel panic

#

There are some people who came up with a patch so I’m trying to implement it

shell mural
#

Looks like a tedious process to get linux working properly

wintry oxide
#

Me and you both

wintry oxide
#

Kinda wishing I had a diff laptop but this is the one I’ve got and can’t afford another so here we are

shell mural
#

I've got a old crappy hp laptop as well

wintry oxide
#

I mean my home lab is a refurbished HP Z440 tower from like 2014 and it booted the omarchy .iso with absolutely no issues

shell mural
#

It's a 2015 envy

wintry oxide
#

That’s why I was so confused

wintry oxide
shell mural
wintry oxide
shell mural
#

This is what I enjoy most tbh

#

pushing old systems to their limits

wintry oxide
#

It was only $500 and came with 4.5 TBs of storage and 32 gigs of mem

#

Silky smooth with omarchy

wintry oxide
#

While my supposedly “cutting-edge” laptop has an inoperable touchpad and is having screen tearing issues🙃🙃🙃

wintry oxide
#

Refurbished workstations are excellent home labs

shell mural
#

you'll have to make do with patches for now

wintry oxide
#

Ya

wintry oxide
shell mural
#

It's more of a DE

#

like gnome

wintry oxide
#

Meant more as just a “hey this should be a FAQ” or sumn

shell mural
#

I'll see what I can do about it

wintry oxide
#

Oh okay thanks

shell mural
#

Maybe make an issue on github, but it's more of a linux problem

wintry oxide
#

Tru

wintry oxide
#

Omarchy will not move past initial splash screen or archiso login messages on HP Omen

wintry oxide
#

@shell mural fed a bunch of sources and my ACPI dump files into a deep research prompt on Gemini, turns out HP Omens have a bunch of power routing tables that straight up disable themselves if you load up something other than windows. So throw Linux on there and they just shut off. Working on a patch process for my firmware version that I’ll share with the arch community once I finish

#

Hopefully can make it reproducible for other users

#

There is also an alternate solution where you basically throw in a kernel param that pretends you’re running windows so I may try that before I mess with the acpi stuff

wintry oxide
shell mural
#

I'll try to look into it as well

wintry oxide
# shell mural That's a bummer

Update: I managed to fix the speakers & touchpad. Required me to rewrite the ACPI tables that govern how the firmware interacts with hardware but I got it working. Probably going to publish the results on my GitHub so other omen users can get it working in the future