Bug 2083098 - Dell laptop stuck on boot when booting on battery power
Summary: Dell laptop stuck on boot when booting on battery power
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 36
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Nicolas Frayer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-09 09:41 UTC by Entodo Ays
Modified: 2023-05-25 18:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 18:05:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Entodo Ays 2022-05-09 09:41:10 UTC
Description of problem:
My Dell Inspiron 5482 2-in-1 laptop doesn't boot when the charger is not connected. If I press F12 to trigger the boot menu and choose the Windows bootloader it boots fine.

Version-Release number of selected component (if applicable):
Gub version 1:2.06-10.fc35

How reproducible:
Always

Steps to Reproduce:
1. Boot without charger connected.
2. It gets stuck on Dell logo or black screen
3. Only powering off is possible. Keyboard input has no effect

Actual results:
Dell logo or black screen

Expected results:
Grub menu showing

Additional info:
https://ask.fedoraproject.org/t/dell-laptop-remains-stuck-on-dell-logo-unless-connected-to-power-supply/21873?u=entodoays

Comment 1 Entodo Ays 2022-05-11 18:40:24 UTC
I updated to Fedora 36 and the problem persists.

Comment 2 Entodo Ays 2022-05-12 06:32:39 UTC
I just discovered a workaround to boot Fedora on battery power. If I press F12 to get to the boot menu, go into the "Change boot options" entry, press Esc, computer reboots and voila! Grub menu shows and Fedora boots normally.

Could this issue be related to the fact that my /boot folder is on a BTFS partition (root)?

Comment 3 Entodo Ays 2022-05-29 11:17:00 UTC
I entered the BIOS configuration utility and added a 5 second POST delay (intended for reading any messages). The issue has been solved or rather worked around.

Comment 4 Fedora Admin user for bugzilla script actions 2023-02-02 00:13:32 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 5 Fedora Admin user for bugzilla script actions 2023-04-25 00:11:01 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 6 Ben Cotton 2023-04-25 17:07:22 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 '36'.

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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 7 Ludek Smid 2023-05-25 18:05:00 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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.