F5F Stay Refreshed Power Users Networks The network adapter stops giving power when it comes back online from a game of World of Warcraft.

The network adapter stops giving power when it comes back online from a game of World of Warcraft.

The network adapter stops giving power when it comes back online from a game of World of Warcraft.

S
Smexy_Potatoe
Member
57
06-13-2026, 09:22 PM
#1
Here is the hard part. I'm trying to turn on my wireless LAN. My computer has a Gigabyte AX370 Gaming K5 board and an AX210 network card. I am using a RPI 3 to wake it up. Using Wireshark, I found that etherwake didn't work with wlan0 on the RPI. I switched to wakeonlan and now I can see packages sent through the broadcast address 192.168.1.255. When I turn off the computer, the light on the network adapter goes out, so I think there is a problem with PCI-e power settings. WOL works perfectly when plugged into the Ethernet cable directly to the Gigabyte motherboard connection. In the BIOS, I have WOL turned on. The network adapter doesn't show up, but the ethernet interface of the MB does and has WOL too. I can't find anything related to PCI-e power states. The funny thing is that I had an old 2.4GHz band TP-LINK network card (the cheapest one), obviously not compatible with WoWLAN. Even though it worked! The new one says it works on paper, but it doesn't work. Anyone who has done this before could give me some advice? I don't know where to look anymore... I've tried everything so far. Thanks.
S
Smexy_Potatoe
06-13-2026, 09:22 PM #1

Here is the hard part. I'm trying to turn on my wireless LAN. My computer has a Gigabyte AX370 Gaming K5 board and an AX210 network card. I am using a RPI 3 to wake it up. Using Wireshark, I found that etherwake didn't work with wlan0 on the RPI. I switched to wakeonlan and now I can see packages sent through the broadcast address 192.168.1.255. When I turn off the computer, the light on the network adapter goes out, so I think there is a problem with PCI-e power settings. WOL works perfectly when plugged into the Ethernet cable directly to the Gigabyte motherboard connection. In the BIOS, I have WOL turned on. The network adapter doesn't show up, but the ethernet interface of the MB does and has WOL too. I can't find anything related to PCI-e power states. The funny thing is that I had an old 2.4GHz band TP-LINK network card (the cheapest one), obviously not compatible with WoWLAN. Even though it worked! The new one says it works on paper, but it doesn't work. Anyone who has done this before could give me some advice? I don't know where to look anymore... I've tried everything so far. Thanks.

M
Mario10Gamer
Member
188
06-14-2026, 05:30 AM
#2
Wake on lan has always been a tricky thing and microsoft's own sleep/bios states make it even more confusing. Sometimes if you shut the machine down in the wrong way, microsoft will override WoL settings. Not sure what is happening there. Even when it works, I had to send multiple wake on wireless packets before it responded. I don't know why wake on wireless lan came about. It's kinda stupid because the wireless card must be very active all the time so that the encrypted session does not drop. I have never seen a bios setting for the wireless version, so I'm unsure if it is the OS or the BIOS doing the function. This needs power to work, but I don't know how much different this is than using one of microsoft's low power sleep modes. This tends to work better than any other form of wake and I doubt there is a significant difference in power. If you really want to turn off the machine and then bring it back up, the simpler way is to use a fancy power outlet. You can set the bios to boot immediately when it sees power. This seems to work almost 100% of the time.
M
Mario10Gamer
06-14-2026, 05:30 AM #2

Wake on lan has always been a tricky thing and microsoft's own sleep/bios states make it even more confusing. Sometimes if you shut the machine down in the wrong way, microsoft will override WoL settings. Not sure what is happening there. Even when it works, I had to send multiple wake on wireless packets before it responded. I don't know why wake on wireless lan came about. It's kinda stupid because the wireless card must be very active all the time so that the encrypted session does not drop. I have never seen a bios setting for the wireless version, so I'm unsure if it is the OS or the BIOS doing the function. This needs power to work, but I don't know how much different this is than using one of microsoft's low power sleep modes. This tends to work better than any other form of wake and I doubt there is a significant difference in power. If you really want to turn off the machine and then bring it back up, the simpler way is to use a fancy power outlet. You can set the bios to boot immediately when it sees power. This seems to work almost 100% of the time.

D
Dardon125
Junior Member
18
06-16-2026, 06:11 AM
#3
I didn't know this choice was there in my BIOS settings. While I'm planning how I set things up at home, it looks like a much easier way is available here. This leaves the RPI ready to use with wired internet and VPNs. I only have one tough concert coming up; if I turn off the computer normally, then I'll have to unplug the plug, leaving the computer without power (no hard shut downs directly from the plug). Is it safe to do that every single day? Thanks for your help!
D
Dardon125
06-16-2026, 06:11 AM #3

I didn't know this choice was there in my BIOS settings. While I'm planning how I set things up at home, it looks like a much easier way is available here. This leaves the RPI ready to use with wired internet and VPNs. I only have one tough concert coming up; if I turn off the computer normally, then I'll have to unplug the plug, leaving the computer without power (no hard shut downs directly from the plug). Is it safe to do that every single day? Thanks for your help!

X
xArcherBunny
Junior Member
48
06-19-2026, 12:01 PM
#4
Yes, basically it's just a two-step stop. You don't need to cut the main electricity right away. It seems like it takes more than just turning on Over the Air (WoL). Even after WoL is set up, you still have to shut down the computer completely for that trick to work. That might be why some times it doesn't start up as expected. When you are done shutting down, you can choose either to unplug the wall socket or leave it plugged in and then turn it off again when you want to restart. Back when I was doing this, I used to try unplugging the plug under the idea that it would protect my computer from bad power. But since I was using one of those really cheap plugs that are hard to tell apart, I can't say for sure if that protection worked or not.
X
xArcherBunny
06-19-2026, 12:01 PM #4

Yes, basically it's just a two-step stop. You don't need to cut the main electricity right away. It seems like it takes more than just turning on Over the Air (WoL). Even after WoL is set up, you still have to shut down the computer completely for that trick to work. That might be why some times it doesn't start up as expected. When you are done shutting down, you can choose either to unplug the wall socket or leave it plugged in and then turn it off again when you want to restart. Back when I was doing this, I used to try unplugging the plug under the idea that it would protect my computer from bad power. But since I was using one of those really cheap plugs that are hard to tell apart, I can't say for sure if that protection worked or not.