The defaults seem to be 1, 1, 0 respectively - and in 7 iterations you can test the further possibilities. Specifically aspm, s5wol and eee_enable "modinfo r8168" shows these. The Realtek driver does provide interesting-looking parameters. Let me still ask though: are you forwarding the WoL packet (port 9, right?) to the broadcast address for the local net with the to-be-woken machine? I.e., to .255 if .* is said local net? If not, try, but as said, I could not imagine the Windows difference in any router-based scenario so it's likely again not a relevant suggestion. Your problem at its essence and initially sounded familiar - the IP of the target(s) expiring from the ARP cache on your router - but when I then got to the "does work if the systems were suspended from Windows 7" bit (and the difference between the 10/15 minutes and 30+ minutes) that seemed and seems to refute any and all issue at your router. Well, I doubt that, although I agree that finding it seems harder than expected. I start a think that, this, not have solution. Well, I installed a Realtek Driver and this is the log (in terminal) when installed was finished: ![]() Yes, I have LM17.3 with upgrade from older versions, but not problem, I installe a 3.19, restart and by grub I access to kernel 3.19. If it works on 3.19 and if for some reason you do really want to run 4.4, I'll look at what the actual problem was. As said, the script loads the new driver immediately. If indeed you still have it installed, you can just boot it ad compile/install with that autorun.sh script. Try right arrow on the "Avanced"entry in the Grub menu. ![]() Note that certainly if originally you installed 17.3 (i.e., if you didn't upgrade to it from an earlier version) you will have 3.19.0-32 still installed unless you explicitly choose to remove it. It looked likely trivial (something with a non-found directory, IIRC) but I wasn't paying close attention, not having a lot of time. I tested on the standard 3.19.0-32 kernel where things worked well, then noticed that you were using 4.4.0-18 on which I then saw they did not. You could do either, but I suspect you'd have that autorun.sh script that Realtek provides leave you with an error on 4.4. In this moment I use a kernel 4.4, you suggest to me that, I install kernel 3.19.0-32 and try to install the Realtek driver, or try to install in my 4.4 kernel and if I had an issue return to default 3.19.3-32kernel? Parm: debug:Debug verbosity level (0=none. Vermagic: 4.4.0-18-generic SMP mod_unload modversions ![]() If I install the soft Wake Up, and program this soft for wake up after a 8 hours since sleep computer, wake up fine, but only with the soft installed in the computer and programed for wake up at one hour. I search about this but I don't view any and its a problem for me because, win7 I have only for test this issue and I need sleep the computer at the night. This 2 computers, with win7 I can wake up without any problem, I sleep the computer and I can wake up after 24/48/72 hours.since I sleep the machine. I view t hat, I need made 2 clicks (in my smartphone for example) for wake up, but after about 30 minutes I can't wake up the computer, any of my 2 computers. I sleep the computer, and in the first 10 or 15 minutes I can wake up by WOL without any problem, after this 10 or 15 min. I have the 2 computers in differents locations (not are in the same lan). I have configured the router for redirect the port for WOL to my computer and the computer have a static ip assigned by router. I have t his problem in two computers with Linux Mint 17.3 圆4 KDE.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |