FS#74203 - [linux] 5.17 kernel enables `CONFIG_SYSFB_SIMPLEFB` which breaks (some) nvidia platform.
Attached to Project:
Arch Linux
Opened by Akatsuki Rui (akiirui) - Wednesday, 23 March 2022, 04:58 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 31 March 2022, 13:44 GMT
Opened by Akatsuki Rui (akiirui) - Wednesday, 23 March 2022, 04:58 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 31 March 2022, 13:44 GMT
|
Details
Description:
Regress of https://bugs.archlinux.org/task/72645 https://github.com/archlinux/svntogit-packages/commit/7f98cfac6f93f0c57b930d42da2f95e77076fbc4#diff-6503b30d816e211d1909eed3e1eff5f9105fdc48f5735921a59f4906f99415beR2288 Additional info: * package version(s) - linux 5.17 * config and/or log files etc. * link to upstream bug report, if any |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Thursday, 31 March 2022, 13:44 GMT
Reason for closing: Fixed
Additional comments about closing: 5.17.1
Thursday, 31 March 2022, 13:44 GMT
Reason for closing: Fixed
Additional comments about closing: 5.17.1
attachment #1 is a screenshot taken with fbgrab which looks boringly normal
attachment #2 is a photo of what actually appears on screen
it's perfectly possible to log into the system and once one starts X/Wayland everything works as expected.
gpu driver is nvidia-dkms 510.54, gpu is a gtx1080ti.
framebuffer-5.17-photo.jpg (1.97 MiB)
And it let my desktop resolution equal 3840*2160(unknown monitor) + 3840*2160(real monitor), and output to my real monitor.
Rollback to 5.16.16 (no SIMPLEFB) can fix it. And I have same issue in 5.15 (with SIMPLEFB)
EDIT: only noticed now - switching VTs causes the display(s) to go blank and eventually turn off due to no input signal detected. going back to the first VT brings the display(s) back. happens regardles of modesetting.