Bug 2013140

Summary: Fedora 34 on notebook, HP 14-ck0023TU, cannot detect external extra-wide monitor, LG 29WK600-W
Product: [Fedora] Fedora Reporter: nukool <nukool>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 34CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, nukool, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-07 22:48:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
Detect result none

Description nukool@gmail.com 2021-10-12 08:24:00 UTC
Created attachment 1832129 [details]
Detect result

1. Please describe the problem:
I have Fedora 34 installed on my notebook, HP 14-ck0023TU. But Fedora cannot detect external extra-wide 29" monitor, LG 29WK600-W. 
And the problems are as follows: 
1.1 Fedora identified it as LG Electonics 34".
1.2 Fedora cant make this external monitor the "Single Display".
1.3 On The "Joined Display", there will be blackout on both monitors after the screen lock. The notebook must be switched off and on again by the power button.

2. What is the Version-Release number of the kernel:
         .';:cccccccccccc:;,.            ---------------- 
      .;cccccccccccccccccccccc;.         OS: Fedora 34 (Workstation Edition) x8 
    .:cccccccccccccccccccccccccc:.       Host: HP Laptop 14-ck0xxx 
  .;ccccccccccccc;.:dddl:.;ccccccc;.     Kernel: 5.14.10-200.fc34.x86_64 
 .:ccccccccccccc;OWMKOOXMWd;ccccccc:.    Uptime: 1 hour, 39 mins 
.:ccccccccccccc;KMMc;cc;xMMc:ccccccc:.   Packages: 1936 (rpm) 
,cccccccccccccc;MMM.;cc;;WW::cccccccc,   Shell: bash 5.1.0 
:cccccccccccccc;MMM.;cccccccccccccccc:   Resolution: 1366x768 
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc:   DE: GNOME 40.4 
cccccc:0MMKxdd:;MMMkddc.;cccccccccccc;   WM: Mutter 
ccccc:XM0';cccc;MMM.;cccccccccccccccc'   WM Theme: Adwaita 
ccccc;MMo;ccccc;MMW.;ccccccccccccccc;    Theme: Adwaita [GTK2/3] 
ccccc;0MNc.ccc.xMMd:ccccccccccccccc;     Icons: Adwaita [GTK2/3] 
cccccc;dNMWXXXWM0::cccccccccccccc:,      Terminal: gnome-terminal 
cccccccc;.:odl:.;cccccccccccccc:,.       CPU: Intel Pentium Silver N5000 (4) @  
:cccccccccccccccccccccccccccc:'.         GPU: Intel GeminiLake [UHD Graphics 60 
.:cccccccccccccccccccccc:;,..            Memory: 1825MiB / 7702MiB 

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
I have replaced the external monitor, SAMSUNG LS24F350FHEXXT, with LG as mentioned above. There is no problem on that SAMSUNG monitor running on the same kernel as mentioned in #2.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
4.1 Before switching on the notebook, attach the monitor to the notebook on HDMI port.
4.2 Switching on the notebook and it boot Fedora 34.
4.3 On "Settings" > "Displays", Fedora identifies it as " LG Electornics 34" "
4.3 The resolution is correct, 2560 x 1080 (IPS/HDR).
4.4 The speakers on the LG external monitor work well.  

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Sorry, I have no dare to do that for I am just an ordinary user. I have to report for nobody answers my question on Ask Fedora, https://ask.fedoraproject.org/t/blank-screen-after-screen-locked-and-no-response/17151 .

6. Are you running any modules that not shipped with directly Fedora's kernel?:

7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. 
If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
Sorry, I have no dare to do that.

Comment 1 nukool@gmail.com 2021-10-12 08:29:55 UTC
More information:
Installed GNOME Extensions:
1. ArcMenu
2. Background Logo
3. Dash to Panel 
4. Launch new instance
5. Lock Keys

Comment 2 nukool@gmail.com 2021-10-12 13:44:15 UTC
Updated information:
Now both Primary Display and Secondary/External Display,LG 29WK600-W, blackout.
I have to remove and use SAMSUNG LS24F350FHEXXT instead.

Comment 3 Ben Cotton 2022-05-12 15:55:04 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-06-07 22:48:36 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.