My Omarchy Wi-Fi Died After Hibernate — The Fix Was Embarrassingly Simple

Wassap mga BitLods.

Today's episode of “Linux made me feel like a hacker just to discover I needed to turn something off and on again” involves Omarchy, hibernation, an Intel AX200 Wi-Fi card, roughly 30+ forum and AI results...

...and one ridiculously simple fix.

I hibernated my machine.

I woke it back up.

Everything looked normal.

Except Wi-Fi had apparently decided:

“Boss, hanggang dito na lang ako.”

No Wi-Fi networks.

No wireless interface.

Nothing.

I spent hours looking through forum posts, Linux troubleshooting threads, AI answers, service commands, driver suggestions, and increasingly questionable incantations from Stack Overflow's distant relatives.

The actual problem?

My Intel Wi-Fi card had apparently gotten stuck after hibernation.

The final fix was a complete shutdown and power reset.

Yep.

That's it.

But before you rage-shutdown your computer and throw your keyboard out the window, here's how we figured out what was actually broken.

The Symptoms

After resuming Omarchy from hibernation, Wi-Fi wasn't simply disconnected.

It was gone.

My first instinct was naturally to restart the networking service.

So I tried:

sudo systemctl restart iwd

Linux replied:

Failed to restart iwd.service: Unit iwd.service not found.

Okay.

Maybe NetworkManager?

sudo systemctl restart NetworkManager

Linux:

Failed to restart NetworkManager.service:
Unit NetworkManager.service not found.

Nice.

Very helpful.

10/10 emotional support.

I also tried Omarchy's Wi-Fi restart helper:

omarchy-restart-wifi

It responded:

Unblocking wifi...

Sounds promising!

Except...

Wi-Fi was still dead.

Lesson #1: Don't Immediately Blame the Wi-Fi Manager

This turned out to be important.

The problem wasn't:

• my saved Wi-Fi password
• my router
• NetworkManager
• iwd
• the Wi-Fi menu
• RFKill
• Mercury being in retrograde

The failure was happening lower in the stack.

Basically:

Wi-Fi menu
    ↓
Network management software
    ↓
Wireless interface
    ↓
Linux driver
    ↓
Wi-Fi hardware

If the wireless interface itself doesn't exist, restarting the menu at the top isn't going to resurrect the hardware at the bottom.

Parang pinipindot mo nang pinipindot yung TV remote...

...pero walang kuryente yung TV.

Step 1: Identify the Wi-Fi Hardware

I ran:

lspci -k | grep -A4 -Ei 'network|wireless'

And got:

02:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
        Subsystem: Intel Corporation Wi-Fi 6 AX200NGW
        Kernel modules: iwlwifi

So the machine could still see the Intel AX200 on the PCI bus.

That's good information.

It meant the Wi-Fi card hadn't completely vanished from the computer.

The expected Linux kernel module was:

iwlwifi

So now we knew where to investigate.

Step 2: Check Whether Linux Created a Wi-Fi Interface

Next:

ip -br link

My output looked roughly like this:

lo          UNKNOWN
enp4s0f3u2 UNKNOWN
tailscale0  UNKNOWN

Notice what's missing?

Normally you'd expect a wireless interface with a name similar to:

wlan0

or:

wlp2s0

There was nothing.

That was the big clue.

This wasn't simply:

“Wi-Fi cannot connect.”

It was:

“Linux currently has no usable Wi-Fi interface to connect with.”

Very different problem.

Step 3: Check Whether iwlwifi Is Loaded

I ran:

lsmod | grep iwlwifi

And iwlwifi was there.

So now things got interesting.

The driver module existed and was loaded...

...but it still hadn't created a Wi-Fi interface.

Meaning the module was present, but something had gone wrong while initializing the hardware.

At this point my Wi-Fi card had achieved the Linux equivalent of:

“Present physically, absent emotionally.”

Step 4: Ask the Kernel What Happened

This was the command that exposed the real problem:

sudo dmesg | grep -i iwlwifi | tail -40

Near the bottom was this:

iwlwifi 0000:02:00.0: probe with driver iwlwifi failed with error -110

There we go.

Error -110

On Linux, error -110 corresponds to a timeout condition: ETIMEDOUT.

In plain English:

The driver tried talking to the Wi-Fi hardware, waited for the response it needed, and eventually gave up.

So my situation now looked like this:

Intel AX200 visible through PCI
        ↓
iwlwifi module available
        ↓
Driver tries initializing AX200
        ↓
AX200 does not respond correctly
        ↓
Timeout
        ↓
No Wi-Fi interface

Mystery finally starting to make sense.

I Tried Reloading the Driver

The obvious next experiment was unloading iwlwifi:

sudo modprobe -r iwlwifi

Then loading it again:

sudo modprobe iwlwifi

Both commands completed normally.

Then:

ip -br link

Still no Wi-Fi interface.

And checking dmesg again showed:

probe with driver iwlwifi failed with error -110

Same timeout.

So restarting the driver wasn't enough.

Then I Went Deeper: PCI Reset

At this point we checked whether the AX200 exposed a PCI reset interface:

ls -l /sys/bus/pci/devices/0000:02:00.0/reset

It did.

So after unloading iwlwifi, I triggered a PCI function reset:

echo 1 | sudo tee /sys/bus/pci/devices/0000:02:00.0/reset

Then loaded the driver again:

sudo modprobe iwlwifi

Surely this would fix it, right?

Linux:

probe with driver iwlwifi failed with error -110

Bruh.

The PCI reset didn't recover it either.

And Then... The Stupidly Simple Fix

At this point we knew something important:

The AX200 was visible.

The kernel module existed.

Reloading the driver didn't work.

Resetting the PCI function didn't work.

The device kept timing out during initialization.

So instead of doing another normal restart, I performed a complete shutdown:

sudo systemctl poweroff

Then I waited around 30 seconds before turning the machine back on.

Not sleep.

Not hibernate.

Not simply bouncing the Wi-Fi service.

A proper:

OFF.

As in:

“Good night muna tayo, Intel AX200. Pag-isipan mo mga ginawa mo.”

Booted Omarchy again.

Wi-Fi came back.

Immediately.

After HOURS of debugging.

Thirty-plus forum and AI results.

Multiple commands.

Kernel logs.

Driver reloads.

PCI reset.

And the winning solution was basically:

“Have You Tried Turning It Off and On Again?”

I have become the IT support meme.

The circle is complete.

Why Did a Shutdown Work When Restarting the Driver Didn't?

The important distinction is that restarting software doesn't necessarily remove power from the physical Wi-Fi device.

In my case, the symptoms strongly suggested the AX200 ended up in a bad state after hibernation.

Linux could see the PCI device, but iwlwifi couldn't successfully initialize it.

Reloading:

iwlwifi

only restarted the driver.

The underlying hardware apparently remained unhappy.

Even the PCI function reset wasn't enough to recover it.

A complete shutdown gave the system and Wi-Fi hardware a chance to start again from a fresh power state.

After that, iwlwifi could initialize the AX200 normally again.

The Troubleshooting Order I'd Use Next Time

If this happens again, I'm definitely not spending another three hours speedrunning the entire Linux networking knowledge base.

I'd start here.

1. Is the Wi-Fi hardware visible?

lspci -k | grep -A4 -Ei 'network|wireless'

If your Intel Wi-Fi card appears, the PCI system can at least see it.

2. Does a wireless network interface exist?

ip -br link

Look for something resembling:

wlan0

or:

wlp...

If there's no wireless interface at all, don't immediately waste time debugging SSIDs and passwords.

3. Is the driver loaded?

For my Intel AX200:

lsmod | grep iwlwifi

4. What does the kernel say?

sudo dmesg | grep -i iwlwifi | tail -40

If you're seeing something similar to:

probe with driver iwlwifi failed with error -110

then you're no longer looking at a normal “can't connect to Wi-Fi” problem.

5. Save your work and perform a complete shutdown

sudo systemctl poweroff

Wait a little while.

Then power it back on.

For my machine, this was the actual fix.

What I Would NOT Do Immediately

After reading enough forums, it's very tempting to start changing random kernel parameters, reinstalling firmware packages, blacklisting modules, editing boot options, replacing networking software, and sacrificing a USB dongle under the full moon.

Don't.

Not yet.

Especially if:

• Wi-Fi worked perfectly before hibernation
• the problem appeared immediately after resume
• your Wi-Fi hardware still appears in lspci
• your wireless interface disappeared
• your driver reports initialization timeouts

Start by determining which layer is actually broken.

You can save yourself a huge amount of time.

And possibly several hundred browser tabs.

Important Caveat

This article documents my specific failure:

• Omarchy
• Intel Wi-Fi 6 AX200
• iwlwifi
• failure immediately after hibernation
• wireless interface missing
• driver probe returning error -110
• full shutdown restoring the card

Your Wi-Fi problem might look similar while having a completely different cause.

For example, if ip -br link already shows your Wi-Fi interface, your issue could instead involve:

• RFKill
• authentication
• DHCP
• DNS
• your access point
• your network-management software

So don't treat:

sudo systemctl poweroff

as some magical universal Linux Wi-Fi repair command.

The useful part is the diagnostic pattern.

The Actual Lesson I Learned

I originally approached this as:

“My Wi-Fi isn't working.”

That description was too broad.

The useful question became:

“At what layer did Wi-Fi stop working?”

Once we checked:

Hardware detected?        YES
Driver module loaded?     YES
Wireless interface?       NO
Driver initialization?    FAILED
Kernel error?             -110 timeout

the problem became much easier to reason about.

And that's probably the biggest takeaway from this whole adventure.

Don't randomly restart everything.

Find the layer that failed.

Then fix that layer.

Or, apparently...

turn the whole computer off for 30 seconds.

Final Bit

Hours spent debugging: many

Forum tabs opened: 30+

Commands tested: also many

Actual repair time:

30 seconds

Linux remains undefeated.

At least I learned something.

And now you don't have to read all 30+ forum threads I did.

You're welcome. 😂

---

If this exact situation happened to you, the four commands I'd remember are:

lspci -k | grep -A4 -Ei 'network|wireless'
ip -br link
lsmod | grep iwlwifi
sudo dmesg | grep -i iwlwifi | tail -40

They tell you far more than repeatedly clicking the Wi-Fi icon while whispering:

“Come on naman.”

Useful Bit delivered.

Kalokohan included.

Mission accomplished.