<div dir="ltr"><div class="gmail_extra"><br><br></div><div class="gmail_quote">On Fri, Aug 30, 2013 at 1:38 PM, Stephen Worthington <span dir="ltr"><<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank">stephen_agent@jsw.gen.nz</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div class="im">On Fri, 30 Aug 2013 12:43:48 -0400, you wrote:<br>
<br>
>I am using a Harmony One on my Mythbuntu 12.04 frontend (MythTV .26, latest<br>
>fixes). I've been able to get it to wake using the Harmony One and an MCE<br>
>USB iR receiver and just about everything works well, but I cannot get it<br>
>to sleep/suspend with the button on the remote. I'm not so much concerned<br>
>with that so I'm trying to use a cron job to evoke pm-suspend daily at 2:30<br>
>a.m. I had this working previously on another front end and it was working<br>
>fine. For some reason, it will not run on this purpose-built frontend.<br>
><br>
>Here are the contents of my crontab file:<br>
><br>
>30 2 * * * root /usr/sbin/pm-suspend 2>&1 ./home/user/Templog/Cron.log<br>
><br>
>The pm-suspend command never runs, so I attempted to force it to log to a<br>
>cron.log log file, which doesn't work either. I can manually run the<br>
>command "sudo pm-suspend" and it suspends just fine, so I'm not sure what<br>
>the issue may be. I don't see any entries about failing to run in the<br>
>syslog, but for some reason<br>
><br>
</div>>*Issue 2*<br>
<div class="im">>If I wake this front end from suspend, it often will not reconnect the NIC<br>
>and just hangs at a black screen until some timeout value is exceeded, at<br>
>which point the Myth frontend tells me it cannot connect to my backend.<br>
>The motherboard is an ASRock B75M-DGS 2.0 with the latest BIOS. This<br>
>motherboard has an onboard Realtek RTL8111E NIC, which, from the best of my<br>
>research should be supported in *buntu. When this happens, if I reboot, it<br>
>resumes working fine. I did try updating the driver to the Unix/Linux<br>
>driver listed on ASRock's website, but this did not change anything.<br>
<br>
</div>The drivers for the RTL8111E are likely the problem. I have an Asus<br>
M5A97 EVO motherboard with an ethernet chip the kernel identifies as<br>
RTL8168E-VL/8111E-VL. That is likely the same chip you have, or very<br>
similar. The builtin driver that loads for this is r8169, which does<br>
not work very well at all as it is not actually the correct driver for<br>
the chip. So I found and installed the r8168 driver and made it work<br>
with DKMS so it automatically gets compiled with each new kernel. This<br>
works much better, but is still problematic as it sometimes simply<br>
stops working under heavy SMB traffic from my Windows PC (eg copying a<br>
DVD image file). So I then wrote a Python script that pings the<br>
WebSmart gigabit switch the MytTV box is connected to, and when the<br>
ping fails, it automatically unloads and reloads the r8168 driver,<br>
which gets the connection working again.<br>
<br>
I have the r8168-8.035.00 driver installed, but a quick google showed<br>
that it has since been updated to r8168-8.036.00 - just search for<br>
that if you want to try it. Let me know if you would like a copy of<br>
my DKMS setup for it. And if anyone needs a copy of my Python script,<br>
let me know about that too.<br>
<br>
I eventually got fed up with the r8168 driver stopping and when I<br>
needed a second ethernet port on the box, I bought an Intel PRO/1000<br>
PT Dual PCIe ethernet card that was going cheap on an auction site.<br>
That works much better - the builtin drivers in Mythbuntu 12.04 seem<br>
to have excellent support for it.<br>
<div class="im"><br>
>This motherboard works well otherwise and was only $54, so the question is,<br>
>do I replace the motherboard (still returnable) with a more expensive one<br>
>without Realtek LAN (I realize that Realtek LAN is supposed to be widely<br>
>supported but this has soured me on it), or should I just add a $30ish<br>
>Intel PCI-e NIC. The problem with adding a PCI-e NIC is that I often use<br>
>wake on LAN and I'm not sure if the motherboard supports it with PCI-e<br>
>devices (my last one didn't, but it was an Intel OEM Dell board).<br>
><br>
>Thanks for any suggestions.<br>
<br>
</div>I can't really help with Wake On Lan as I do not use it. I do know<br>
that my PRO/1000 PT card supports it, and the specifications for the<br>
motherboard in its manual lists "WOR by PME" under "Manageability",<br>
which I think means that PCIe cards can wake the motherboard. So you<br>
might like to check if your motherboard's manual says it has that<br>
option too. And check in your BIOS settings for APM options for<br>
waking from PCIe cards.<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</blockquote></div><p> </p><div>Thanks for the reply. I thought it was probably the drivers, which is why I tried the ones on the ASRock site to no avail. I do have a PCI NIC in another PC that I can experiment with to see if wake on LAN will work from a PCI slot in the motherboard.</div>
<div class="gmail_extra"><br></div></div>