FS#69149 - [linux] Desktop won't boot with 5.10.3
Attached to Project:
Arch Linux
Opened by José Miguel Sarasola (alosarjos) - Thursday, 31 December 2020, 07:26 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 14 October 2021, 21:49 GMT
Opened by José Miguel Sarasola (alosarjos) - Thursday, 31 December 2020, 07:26 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 14 October 2021, 21:49 GMT
|
Details
Description: After updating to 5.10.3 and rebooting, during
the boot process the screen looses the signal (After the
BIOS screen) and I have to use the SysRq keys to be able to
boot into the system. Happening with both linux and
linux-zen, booting with linux-lts I do not have this problem
(And haven't seen anything like this before today)
Additional info: * Package versions: - linux 5.10.3.arch1-1 - linux-lts 5.4.85-1 - linux-zen 5.10.3.zen1-1 Steps to reproduce: Boot the system (In my case I use Gnome with GDM enabled on systemd) |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Thursday, 14 October 2021, 21:49 GMT
Reason for closing: Fixed
Additional comments about closing: 2021-10-12: A task closure has been requested. Reason for request: Now it's working as expected
Thursday, 14 October 2021, 21:49 GMT
Reason for closing: Fixed
Additional comments about closing: 2021-10-12: A task closure has been requested. Reason for request: Now it's working as expected
Downgrading back to 5.9.14 solves the problem.
I'm running KDE 5.77.0 / Plasma 5.20.4, CPU: Intel Core i3 M 370 @ 4x 2.4GHz, GPU: GeForce GT 425M, with nvidia-390xx-dkms 390.138-8 driver.
Today the nvidia-390xx-dkms driver was updated to 290.138-10 version, to fix the kernel 5.10.x problem with nvidia.
No additional adjustments were needed to my system.
I am removing my vote here.
I have tested on another Laptop: Lenovo T14s (AMD CPU+internal GPU): No standby/display issues there with 5.10.3 and default (OS) drivers.
Since my T480s needs to get a new screen I created an account for the IT department, removed my account and wiped its data. Logged in with that new account and after updating to kernel 5.10.5 (and now 6.10.6), I no longer can reproduce the issue. So either it was on my side (user setting, unlikely IMHO since I did not set anything special) or it was the kernel (or any other arch) update – works for me now, so I pull back.
@alosarjos: What about your issue with recent kernel? Still present? Please re-try and update this bug, or close it.
This is on linux 5.10.7 generated without the amdgpu module
Rebooted into linux-zen with the module, and working fine, checked the boot logs and found this:
[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:70:crtc-0] flip_done timed out
Which is not showing up on the zen boot (But it's 5.9)