LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Kernel (https://www.linuxquestions.org/questions/linux-kernel-70/)
-   -   Moving from linux kernel 5.4 to 5.10 causes my screen never to show display again once it has gone to sleep. (https://www.linuxquestions.org/questions/linux-kernel-70/moving-from-linux-kernel-5-4-to-5-10-causes-my-screen-never-to-show-display-again-once-it-has-gone-to-sleep-4175698438/)

folaht 07-29-2021 02:34 AM

Moving from linux kernel 5.4 to 5.10 causes my screen never to show display again once it has gone to sleep.
 
As one can see in this video, I can call xflock4 which locks the screen and I'm able to go back when the screen goes to I think screensaver mode.

But doing it while waiting only a few seconds later as the screen goes into sleep mode, I can no longer bring it back. It's stuck at 'screen saver' mode and does not respond to any input.

This happens in Linux 5.10, but not in Linux 5.4.


What should I do?
Report this here?
https://www.kernel.org/doc/html/late...ng-issues.html

Move to kernel 5.13 and hope for the best?


----

Additional info

Code:

[folaht@pjehrsohmehj ~]$ inxi -SCGM
System:    Host: pjehrsohmehj Kernel: 5.10.53-1-MANJARO x86_64 bits: 64 Desktop: Xfce 4.16.0 Distro: Manjaro Linux
Machine:  Type: Desktop Mobo: ASRock model: J5005-ITX serial: <superuser required> UEFI: American Megatrends v: P1.40
          date: 08/06/2018
CPU:      Info: Quad Core model: Intel Pentium Silver J5005 bits: 64 type: MCP cache: L2: 4 MiB
          Speed: 2695 MHz min/max: 800/2800 MHz Core speeds (MHz): 1: 2695 2: 2696 3: 2738 4: 2748
Graphics:  Device-1: Intel GeminiLake [UHD Graphics 605] driver: i915 v: kernel
          Display: x11 server: X.Org 1.20.11 driver: loaded: intel unloaded: modesetting resolution: 1920x1080~60Hz
          OpenGL: renderer: Mesa Intel UHD Graphics 605 (GLK 3) v: 4.6 Mesa 21.1.5

Monitor

Code:

Philips
MODEL 243V7
SN: UHBA2021041182
1920x1080@60GHz


ondoho 07-29-2021 03:22 AM

Quote:

Originally Posted by folaht (Post 6270592)
As one can see in this video, I can call xflock4 which locks the screen and I'm able to go back when the screen goes to I think screensaver mode.

But doing it while waiting only a few seconds later as the screen goes into sleep mode, I can no longer bring it back. It's stuck at 'screen saver' mode and does not respond to any input.

This happens in Linux 5.10, but not in Linux 5.4.

First of all, how did you change from 5.4 to 5.10? IS that Manjaro's regular kernel upgrade? If not, why don't you stick to 5.4?


Quote:

What should I do?
Report this here?
https://www.kernel.org/doc/html/late...ng-issues.html
Let me quote from this excellent article:

Quote:

Don't rush to claim that you have found a bug

When you are having problems with a piece of software, don't claim you have found a bug unless you are very, very sure of your ground. Hint: unless you can provide a source-code patch that fixes the problem, or a regression test against a previous version that demonstrates incorrect behavior, you are probably not sure enough.

(...)

When asking your question, it is best to write as though you assume you are doing something wrong, even if you are privately pretty sure you have found an actual bug. If there really is a bug, you will hear about it in the answer.

folaht 07-29-2021 04:21 AM

Quote:

Originally Posted by ondoho (Post 6270604)
First of all, how did you change from 5.4 to 5.10? IS that Manjaro's regular kernel upgrade? If not, why don't you stick to 5.4?

I saw it in the manjaro kernel menu as 'LTS' and 'recommended', so I would think it's supported.
https://link.tardigradeshare.io/raw/...9_11-13-56.png

Linux 5.4 has an issue with snapd that has been solved in Linux 5.10.

I'll go back to Linux 5.4 then.

[update]

Okay, now I'm beginning to really need it.

Code:

$ docker run --runtime=sysbox-runc -it dockerfile
docker: Error response from daemon: failed to create shim: OCI runtime create failed: kernel version check failed: manjaro kernel release 5.4.135-1-MANJARO is not supported; need >= 5.5: unknown.
ERRO[0000] error waiting for container: context canceled


ondoho 07-29-2021 01:50 PM

Sorry, which one is the LTS, 5.4 or 5.10?
No, scratch that: which one is the Manjaro default kernel: 5.4 or 5.10?
I seem to remember they ship their own kernel, so unless you have a specific reason to change that, you probably shouldn't.

folaht 07-30-2021 02:09 AM

Quote:

Originally Posted by ondoho (Post 6270756)
No, scratch that: which one is the Manjaro default kernel: 5.4 or 5.10?

https://link.tardigradeshare.io/raw/...0_08-46-51.png

It's actually rather confusing, Since top download https://manjaro.org/downloads/official/xfce/ leads to
https://download.manjaro.org/xfce/21...4-linux510.iso

But then there's also a minimal LTS linux 5.4 version for at the bottom.

I will ask the manjaro forum.

And this is the answer from someone on the manjaro team:

Quote:

Manjaro ships multiple kernels. All that have the LTS badge can be default, but you can use also the maintained kernels that are not LTS. MHWD kernel is a great tool to see that. You can have them all installed if you want, and test what works best for you.
[update]

There's now a second person claiming to face the same issue.

https://forum.manjaro.org/t/manjaro-...crazy/75442/16

ondoho 08-08-2021 03:44 AM

If 5.4 works for you and is one of the officially supported LTS kernels, why not just use that?

Meanwhile, you should definitely do more troubleshooting: try to pin it down on either the kernel or the screensaver/locker used (as one of the posters on Manjaro forums suggested).
General advice for providing output etc. in my signature.


All times are GMT -5. The time now is 06:53 PM.