[mythtv-users] Screen Goes Blank on Standby, Then Never Wakes Up

[Mike Carron]

On 10/09/2014 10:38 PM, faginbagin wrote:
> On 10/9/2014 3:31 PM, Mike Carron wrote:
>> On 10/08/2014 11:58 PM, faginbagin wrote:
>>> How did you revert to 12.04? If you reinstalled using 12.04.2 or later, you inherited one of the later HWEs (and its kernel) that was introduced with a later version of Ubuntu. You might want to consider reinstalling 12.04.1. That will drop you back to kernel 3.2. Or you could try to play around with package management to try to install the original 3.2 kernel and then uninstall whatever HWE you have right now. You can find the mythbuntu 12.04.1 iso here: http://old-releases.ubuntu.com/releases/mythbuntu/releases/12.04.1/release/ I'm choosing to stick with kernel 3.2 because when you check kernel.org, you'll see it's listed as one with long term support. Something you won't find for the kernels that come with then newer HWEs. I'm not sure if it makes a difference, given I'm getting the kernel from Ubuntu, but it gives me a warm/fuzzy sense of security. HTH, Helen
>> ***
>> I installed 12.04.4 which promptly wanted to upgrade to 12.04.5 to get the Trusty HWE. I'll try the 12.04.1 and see what happens. How do I make sure it doesn't upgrade itself to 12.04.2 or later?
>>
>> mike
> It should be OK to upgrade to 12.04.x. You won't get any of the newer HWEs, your kernel will stay at 3.2. For example, here's what it says when I ssh into one of my 12.04 boxes:
>
> Welcome to Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-68-generic x86_64)
>
> That's after using synaptic to update on Sep 7 (it's overdue for another backup/update...).
>
> HTH,
> Helen
>
***
Thanks, I'm slowly learning how the various upgrades work. I didn't 
realize that 12.04.5 could have the 3.2 kernel but I see that it can 
(3.2.0-70). Now I need to figure out why that particular machine has no 
sound over HDMI on power-up or reboot, I have to enter Setup and 
reselect the correct sound module and then it will have proper sound 
until it is rebooted. It's a bit frustrating since an identical machine 
(both are Zotac ID36) does not have that problem. Both are set up the 
same as best as I can determine, including running the same Nvidia 
graphics drivers.

mike