![]() But I'm only 70% sure of that.Netplan - YAML network configuration abstraction for various The funny thing, is I _swear_ it didn't exhibit this behaviour when I first got the motherboard (last June). I tried again, disabling the on-board NIC in the BIOS and the problem is still present. I've even tried WOL on a different (Intel E100) card and it still does the double wake up, which leads me to believe it is not the r8169 hardware, but the ACPI bios itself. Then I moved my cards around, on the off-chance that it was 1992 again and that would fix the problem, it didn't. Then I removed the other NIC (the off-mainboard one) in case that was somehow interfering, problem still persists. Then I checked that I was using the latest firmware for the in-kernel r8169 driver, and I am. Then I tried switching to legacy BIOS + grub, and it didn't make any difference. Hmm, I didn't realize there was an out-of-tree r8168 driver. On the first machine, I had also installed Realtek's r8168 network driver in my quest to solve the wakeup issues. Unfortunately, I have no experience with EFI boots it sounds like it might be a bug, though ( )įor completeness' sake, however, I realized with a fresh install of a second Shuttle DS61 that "acpi=noirq" by itself wasn't enough. Might be because I'm using an EFI only boot and ACPI is necessary? Hmm, unfortunately when I tried acpi=noirq, or pci=noacpi, the kernel does not boot (just black screen). I had the same problem here with a Shuttle DS61, but adding "acpi=noirq" to the grub command line solved it for me (from ) May I ask what your mainboard and BIOS are? At the very least it might help some other users to avoid buggy hw. I have the same issue on a MSI H87/G43 mainboard. Sorry to wake up an old thread, but did you ever get this solved? I see a very similar posting (possibly you?) on bbs.archlinux from last fall. VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-Īrb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-Ĭtrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Ĭaps: LPEVC=0 RefClk=100ns PATEntryBits=1 Subsystem: ASRock Incorporation Device 96b1Ĭontrol: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ ![]() Link partner advertised auto-negotiation: Yesĭrv probe link timer ifdown ifup rx_err tx_errĠ4:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57781 Gigabit Ethernet PCIe (rev 10) Link partner advertised pause frame use: No ![]() ![]() Link partner advertised link modes: 10baseT/Half 10baseT/Full Supported link modes: 10baseT/Half 10baseT/FullĪdvertised link modes: 10baseT/Half 10baseT/Full Here is output of ethtool eth0 after step 2: The same setup worked fine with the previous mainboard. I've tried setting ethtool -s eth0 wol d after 2), but it doesn't help (it is set, see below). It seems like some flag is not cleared after wake up. If not waken by WOL but USB event (keystroke), everything's fine. Hi, I've got the following problem with Wake on LAN on Linux 3.4.4:Ĥ) Machine wakes up immediately after going to suspendĥ) Send machine to suspend mode (S3) => machine sleeps Posted: Thu 11:43 am Post subject: Wake on LAN wakes computer twice ![]() Gentoo Forums Forum Index Networking & Security Gentoo Forums :: View topic - Wake on LAN wakes computer twice ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |