I decided it would probably be a good idea to update to 8.5 to get to the latest mythtv version, so I got a new hard drive and used clonezilla to clone my existing hard drive. It would not boot, presumably because the MBR was not properly configured, but instead of manually trying to repair it, I just ran the LinHES upgrade from the disk. Everything seemed to perform well, but there were a couple things that I found needed to be corrected manually after the upgrade.

1) It looks like there should be a symlink from /myth to /data/storage/disk0/media and it was not created automatically, so I did it manually.
2) Mythweb password did not work. On the frontend I had to go into LinHES Settings, Web Security. The password was already entered and correct, I just had to save it and then I could access mythweb again.
3) My nemesis, Mythwelcome is not shutting down. In fact, either the backend or mythwelcome appears to have locked up. The backend log has a flood of these messages:


Time to investigate...

More to come.

After running mythwelcome appears to be shutting the system down properly.

I had playback freeze once already, though... It looks like an issue that has been reported before, but I have not seen a resolution yet. Will keep looking...

I stand corrected. Mythwelcome shutdown the computer as it was supposed to, but it did not wake up...

Also, Wake On Lan is not working, so I am digging into that as well.

Last night I had to make a few updates to my lircrc configuration file. It looks like some button names were changed during this transition:
"|<<" became "PREVIOUS"
">>|" became "NEXT"
"<<" became "REWIND"
">>" became "FOWARD"(sic)

I was away for a few nights, so I let mythwelcome shutdown the system automatically with a wakeup scheduled for the next morning. It never woke up automatically and only started up when the power button was manually pressed. I notice that the file
/etc/adjtime
appears to be changed when the system shut down last. I also notice that:
/etc/rc.shutdown
has a line:
and so I am wondering if the hardware clock is being set on shutdown after the alarm is set and that is breaking the wakeup alarm.
Is there a way to disable this function in Arch? There is a section on the mythtv wiki, but I don't see anything that crosses into Arch:
https://www.mythtv.org/wiki/ACPI_Wakeup ... ck_updates

This is the same hardware (besides HDD) that i used in 8.1 where the wakeup was working flawlessly, so I don't think it a bios setting. Is there anything else that I can look at which may have changed and affected ACPI wakeup?

Just to be sure that my bios didn't get reset disconnecting power when changing out the HDD, I powered up the 8.1 system again and ran then same
8.1 wakes up find.
8.5.1 never wakes up.

There is a file called /var/log/wake_alarm which contains the following for 8.5.1:


and the following for 8.1:


Can I assume that this is written to the BIOS when the log is created? If so, then they appear to be identical besides the dates/times which obviously would be different since I can't test them simultaneously. So is there a way to figure out what is canceling the acpi wakeup on 8.5.1?

I was able to get wake-on-lan working. I downloaded the dkms patch automatic installer from this site:
https://bugzilla.kernel.org/show_bug.cgi?id=61651
Using this link:
https://bugzilla.kernel.org/attachment.cgi?id=255097
It downloaded alx-dmks-installer.tar.gz

I extracted using
when I entered the folder to run setup, it ran into dependency issues.

As I mentioned previously, it wouldn't install with git, patch, and dkms. I installed git, patch, and linux-headers from the linhes repository using pacman, but dkms was not available. So I downloaded the arch package 2.5-1:
https://www.archlinux.org/packages/extra/any/dkms/

using the following link:
https://www.archlinux.org/packages/extr ... /download/

using wget resulted in the file index.html so I renamed it to: dkms-2.5-1-any.pkg.tar.xz
I installed it using:

Then I was able to run setup for the alx dkms module installer with no problem and wake on lan was available after a reboot and it worked after I turned it on with

It also seemed to be persistent throughout reboot. Still no improvement on mythwelcome wakeup, though. FYI, this motherboard is:
ASUS M5A78L-M LX3