Bug 2229416 - Resume from suspend turns on BOOT LED on Gigabyte B650 motherboard AM5 Platform
Summary: Resume from suspend turns on BOOT LED on Gigabyte B650 motherboard AM5 Platform
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://www.reddit.com/r/Fedora/comme...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-05 20:10 UTC by Mohd Yusuf
Modified: 2024-05-28 13:41 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-28 13:41:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mohd Yusuf 2023-08-05 20:10:40 UTC
Gigabyte motherboards come with 4 LED status if issues are related to those areas.
1. GPU
2. RAM
3. CPU
4. BOOT - which would turn ON if we havent entered OS yet

During cold boot, this BOOT LED doesnt turn on. However after resuming from suspend (sleep) this LED turns ON. 

Whether or not this is an issue - I cant say, I didnt find any conclusive documentation on this issue. However I have tried Windows 11 and Linux Mint 21.2 and they worked perfectly.

Reproducible: Always

Steps to Reproduce:
1. Cold boot - see BOOT LED on motherboard OFF (good)
2. Suspend the system - BOOT LED OFF
3. Wake up from suspend - BOOT LED ON
Actual Results:  
BOOT LED turns ON after waking up from suspend.

Expected Results:  
Would need BOOT LED to remain OFF after waking up from suspend.

I have tried Windows 11 and Linux Mint 21.2 and they worked perfectly.

Gigabyte motherboard documentation (page 18):
https://download.gigabyte.com/FileList/Manual/mb_manual_b650-ae-series_e_1101_v1.pdf

Comment 1 Jarod Wilson 2023-08-11 01:21:16 UTC
kernel-utils isn't a valid component, reassigning to kernel.

Comment 2 Aoife Moloney 2024-05-28 13:41:07 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 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.