Bug 1972985 - Blank screen after "Protected by HP Sure Start"
Summary: Blank screen after "Protected by HP Sure Start"
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-17 02:51 UTC by Rares Vernica
Modified: 2021-11-30 19:05 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-30 19:05:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg w/ 5.11.22 kernel (86.62 KB, text/plain)
2021-08-16 20:02 UTC, Rares Vernica
no flags Details

Description Rares Vernica 2021-06-17 02:51:20 UTC
1. Please describe the problem:

Once the kernel is selected in Grub, "Protected by HP Sure Start" screen appears. After 1-2 seconds the screen becomes blank and stays blank. The keyboard seems active as Caps Lock still works. If I press the power button the laptop goes in Stand-by mode.

Laptop HP EliteBook 840 G5
BIOS Q78 Ver. 01.16.00 04/20/2021

2. What is the Version-Release number of the kernel:

Fedora (5.12.10-200.fc33.x86_64) 33 (Workstation Edition)

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 :

Yes, it works fine with Fedora (5.11.22-100.fc32.x86_64) 32 (Thirty Two)

It brakes with Fedora (5.12.10-200.fc33.x86_64) 33 (Workstation Edition)

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Yes, select the Fedora (5.12.10-200.fc33.x86_64) 33 (Workstation Edition) kernel in Grub.


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``:

Unknown

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

No.

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.

Not available

Comment 1 Rares Vernica 2021-07-20 20:44:44 UTC
This is still an issue with the 5.12.15-200.fc33.x86-64 kernel.

Comment 2 Rares Vernica 2021-08-16 19:48:03 UTC
Still an issue with 5.13.4-100.fc33.x86_64 and 5.13.9-100.fc33.x86_64

Comment 3 Justin M. Forbes 2021-08-16 19:55:36 UTC
Can you at least attach a dmesg from a working boot on the 5.11.22 kernel, that would give me a better idea of what we are dealing with than trying to look up specs on a particular model.

Comment 4 Rares Vernica 2021-08-16 20:02:42 UTC
Created attachment 1814563 [details]
dmesg w/ 5.11.22 kernel

Comment 5 Rares Vernica 2021-08-18 02:37:57 UTC
I'm able to successfully bot and load Fedora if I add "nomodeset" to kernel parameters. 

It looks like the system boots slower and screen dimming (hot keys) is not working.

Comment 6 Ben Cotton 2021-11-04 13:47:15 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2021-11-04 14:16:41 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2021-11-04 15:14:21 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Ben Cotton 2021-11-30 19:05:38 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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. If you experience problems, please add a comment to this
bug.

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


Note You need to log in before you can comment on or make changes to this bug.