![]() ![]() I suspect that this causes the strange behaviour of my PC. Normally only a "Magic Packet" will do the job but you can also setup the network card in a way that any incoming network communication will wake up the PC. And it also works perfectly on my machine - as long as I do not install Proxmox.Īs far as I know you can define on what kind of incoming data the network card should wake up the PC. Wake on LAN works simply through the PCI (express) slots. As long as you do not use a very old motherboard you will not need a WOL cable any more (and you will not find any connectors for such a cable). WOL cables are "out of fashion" for quite a while. ![]() But now I cannot use Wake on LAN any more.Īny ideas what is going wrong and what I can do to solve the issue?Īs I already mentioned I do NOT use the onboard card but an Intel PCI-Express gigabit ethernet card. The only method to prevent this is to disable the Wake in PCI feature in UEFI/BIOS. It does not matter what method I use to shut down ("shutdown -h now" on command line or Shutdown-button in Proxmox web interface) - a few seconds after all the lights went off and the harddisks and coolers stopped the machine powers up again. I can wake up the server with a WOL magic packet and can shut down the server without any problems.īut after installing Proxmox the server shows a strange behaviour: The machine powers down normally, but after a few seconds it wakes up again. In BIOS/UEFI I activated the option "Wake on PCI" so that I can use Wake on Lan (WOL).Īfter a fresh install of Debian Squeeze 64 Bit everything works perfectly. ![]() Instead of the Onboard NIC I use an Intel PCI Express Gigabit Ethernet Card. I have built a home server based on an Intel Celeron Dual Core and an ASRock Mainboard H61M/U3S3 (B3), Sockel 1155, mATX. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |