View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 23 posts ] 
Go to page Previous  1, 2

Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sun Dec 31, 2017 9:10 pm 
Offline
Joined: Thu Sep 27, 2007 5:44 pm
Posts: 516
Alright, I've uninstalled and removed the dkms driver and removed dkms altogether. After a reboot followed by a shutdown, Wake On LAN still works.

Code:
sudo ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: pg
        Wake-on: g
        Current message level: 0x000060e4 (24804)
                               link ifup rx_err tx_err hw wol
        Link detected: yes


"Wake-on: g" represents that it is setup to wake up on magic packets. Thanks for the quick turnaround.


Top
 Profile  
 
PostPosted: Mon Jan 01, 2018 7:58 am 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1167
Location: SC
Ok, thanks. You can change your repos back to release if you want. I am going to let these updates soak on my test systems for a few days and will then push them to release.


Top
 Profile  
 
PostPosted: Sun May 06, 2018 5:54 am 
Offline
Joined: Thu Sep 27, 2007 5:44 pm
Posts: 516
Closing the loop on this, here is the line I added to /usr/LH/bin/mythwelcome-set-alarm.sh
Code:
/home/mythtv/piwol.sh $1


/home/mythtv/piwol.sh contains:
Code:
#!/bin/bash
epoch=$1
pidate="$(/usr/bin/date --d @$epoch '+%H:%M %D')"
echo ${pidate}
ssh pi@192.168.0.205 "/home/pi/clearat.sh"
ssh pi@192.168.0.205 "echo '/home/pi/wol.sh' | at ${pidate}"


192.168.0.205 is my raspberry pi and an ssh key is setup for authentication. The two scripts on the pi are:
/home/pi/clearat.sh
Code:
for i in `atq | awk '{print $1}'`;do atrm $i;done

and /home/pi/wol.sh
Code:
wakeonlan XX:XX:XX:XX:XX:XX
where XX:XX:XX:XX:XX:XX is the MAC address of my LinHES box.


Top
 Profile  
 
PostPosted: Sat Mar 30, 2019 7:14 am 
Offline
Joined: Thu Sep 27, 2007 5:44 pm
Posts: 516
My pi is on Wi-Fi and the router locked up last night and so my machine did not wake. Coincidentally I saw a resolution on the mythtv forums just last night, but I cannot seem to get it to work.

https://forum.mythtv.org/viewtopic.php? ... fdd#p14943

Their resolution is for ubuntu, but I tried making the same change in grub and updating with
Code:
# grub-mkconfig -o /boot/grub/grub.cfg


But hpet still shows as an available clocksource. Any tips on how to completely disable hpet to test if it fixes my wakeup issues? Are there any concerns with disabling it?


Top
 Profile  
 
PostPosted: Sun Mar 31, 2019 3:26 pm 
Offline
Joined: Thu Sep 27, 2007 5:44 pm
Posts: 516
On boot up I checked the kernel parameters and noticed it missing my additions. I entered them manually and ran the mythwelcome-test-wakeup.sh and it woke up as it should. Looking more deeply I see that the grub menu item for the default LinHES launcher is contained in
Code:
/etc/grub.d/09_mythvantge_runit_grub

I think the change to the /etc/default/grub file is ignored because the menu item is not in 10_linux

So I have modified the line in it and re-ran
Code:
# grub-mkconfig -o /boot/grub/grub.cfg


Now it appears to be honoring the kernel parameters that I wanted:
Code:
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=2d4db0d0-59dd-4b83-a93b-9fe98a9e8e23 ro quiet hpet=disable tsc=unstable splash udev.log-priority=3 loglevel=3 init=/sbin/runit


Is there anything that I can do to make this persistent across upgrades?


Top
 Profile  
 
PostPosted: Sun Mar 31, 2019 3:55 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1167
Location: SC
There isn't a way to keep your change persistent right now. I am thinking that the boot lines in /etc/grub.d/09_mythvantge_runit_grub could pull in a var from /etc/default/grub. I am guessing that wasn't done because of the risk of a bad command in /etc/default/grub could make the system not boot.


Top
 Profile  
 
PostPosted: Sun Mar 31, 2019 5:32 pm 
Offline
Joined: Thu Sep 27, 2007 5:44 pm
Posts: 516
No worries. If I get some time I will investigate further. Maybe I can force it after bootup or just before shutdown. It is satisfying just to have this working again. I will try to keep an eye on it during upgrades.


Top
 Profile  
 
PostPosted: Mon Apr 01, 2019 7:55 am 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1167
Location: SC
To clarify you can make it persistent across boot by modifying the lines in /etc/grub.d/09_mythvantge_runit_grub and running the grub-mkconfig command. It won't be persistent across updates to the LinHES-config package.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 23 posts ] 
Go to page Previous  1, 2



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu