Hello Ilya,
On 11/11/21 11:52, Ilya Trukhanov wrote:
> On Thu, Nov 11, 2021 at 10:24:56AM +0100, Javier Martinez Canillas wrote:
>> On 11/11/21 08:31, Javier Martinez Canillas wrote:
>>
>> [snip]
>>
> And for each check /proc/fb, the kernel boot log, and if Suspend-to-RAM
> works.
>
>
On Thu, Nov 11, 2021 at 10:24:56AM +0100, Javier Martinez Canillas wrote:
> On 11/11/21 08:31, Javier Martinez Canillas wrote:
>
> [snip]
>
> >>> And for each check /proc/fb, the kernel boot log, and if Suspend-to-RAM
> >>> works.
> >>>
> >>> If the explanation above is correct, then I would exp
On 11/11/21 08:31, Javier Martinez Canillas wrote:
[snip]
>>> And for each check /proc/fb, the kernel boot log, and if Suspend-to-RAM
>>> works.
>>>
>>> If the explanation above is correct, then I would expect (1) and (2) to
>>> work and
>>> (3) to also fail.
>>>
>
> Your testing confirms my a
On Thu, Nov 11, 2021 at 12:07:19AM +0100, Javier Martinez Canillas wrote:
> [ adding dri-devel mailing list as Cc ]
>
> Hello Ilya,
>
> On 11/10/21 21:02, Ilya Trukhanov wrote:
> > Suspend-to-RAM with elogind under Wayland stopped working in 5.15.
> >
> > This occurs with 5.15, 5.15.1 and latest
Hello Ilya,
On 11/11/21 01:45, Ilya Trukhanov wrote:
[snip]
>> Can you please share the kernel boot log for any of these cases too ?
>
Thanks a lot for the testing and providing the info!
>> This is just a guess though. Would be good if you could test following cases:
>>
>> 1) CONFIG_FB_EFI n
[ adding dri-devel mailing list as Cc ]
Hello Ilya,
On 11/10/21 21:02, Ilya Trukhanov wrote:
> Suspend-to-RAM with elogind under Wayland stopped working in 5.15.
>
> This occurs with 5.15, 5.15.1 and latest master at
> 89d714ab6043bca7356b5c823f5335f5dce1f930. 5.14 and earlier releases work
> fi
