LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 <64usĬlockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ MaxPayload 128 bytes, MaxReadReq 4096 bytesÄevSta:ÄorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend. RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop. Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-Ĭapabilities: MSI: Enable- Count=1/1 Maskable- 64bit+Ĭapabilities: Express (v2) Endpoint, MSI 01ÄevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64usÄ®xtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000WÄevCtl:ÄorrErr- NonFatalErr- FatalErr- UnsupReq. Region 4: Memory at a1100000 (64-bit, non-prefetchable) Ĭapabilities: Power Management version 3įlags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Region 2: Memory at a1104000 (64-bit, non-prefetchable) Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- ![]() BIOS is up-to-date and doesn't show any "obvious" wol settings. Then I have to repeat the manual suspend/resume cycle to make it work again.Ī similar problem was mentioned at, but the proposed solution (forcing autonegotiation on) didn't work for me. I have a weird problem with wake-on-lan on my Realtek card.Īfter turning wake-on-lan flag on (using either ethtool or NetworkManager), to make the PC responsive to wol packets I have to first suspend and wakeup it once manually (hitting any key or power button).Īfter this maneuver, I can wakeup via magic packet from all subsequent suspend transitions AND also from the first shutdown.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |