On 09/25/2016 12:00 PM, Patrick O'Callaghan wrote:
On Sat, 2016-09-24 at 12:06 -0600, jd1008 wrote:
> On 09/24/2016 11:56 AM, Patrick O'Callaghan wrote:
>> On Sat, 2016-09-24 at 11:25 -0600, jd1008 wrote:
>>>> I note that the last line has "true" instead of
"false", so maybe it
>>>> shouldn't have worked before and now is failing correctly ...
>>>>
>>>> poc
>>> Yes - that must be it.
>>> Have you changed it to false, and run
>>> grub2-mkconfig
>>> and rebooted, and hibernated and rebooted to see if it will
>>> resume as it ought to?
>> Just tried it and (somewhat to my surprise) it worked. I'll cross my
>> fingers and hope it keeps working.
>>
>> [One thing I noticed is that alternate lines in the boot menu are now
>> labelled Recovery Mode (i.e. for each kernel version there is now an
>> additional line). This definitely wasn't the case before but I assume
>> it's not related to hibernation, despite the potential confusion
>> between the terms Recover and Restore.]
>>
>> Thanks for your help.
>>
>> poc
>>
>> PS I tried it twice. First time Bluetooth worked, second time it
>> didn't, i.e. it was offline on restore. This is pretty much par for the
>> course.
>>
> I have not figured out the difference between the "recovery" kernels
> and the non "recovery" kernels in the grub.conf file.
> Perhaps someone (a developer) could clarify.
And it failed again, in identical circumstances to the last time when
it worked.
poc
I strongly suspect a HW issue.