ValveSoftware / ValveSoftware/SteamOS
Green Boot/UEFI Screen after installing SteamOS
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.6k
- Forks
- 83
- Avg merge
- 4m
- Merged PRs (30d)
- 3
Description
Your system information
- Steam client version:
- SteamOS version: 3.8.16
- Opted into Steam client beta?: No
- Opted into SteamOS beta?: No
- Have you checked for updates in Settings > Yes
I built a DIY SteamOS computer and after installing SteamOS, the initial boot screen and uefi are tinted green. Before installing SteamOS the initial boot screen and uefi menus looked the way they should, i.e. not green. The uefi menus are still navigable but look ugly. Here is my hardware setup:
Ryzen 7 7800X3D
Sapphire RX 9600 XT 16 GB
2x16 GB Corsair vengeance DDR5
Asrock B850i lightning wifi motherboard
I updated to the latest bios from Asrock available for my motherboard before installing SteamOS (4.43) and did not encounter the problem until after installing SteamOS. I downgraded the bios to the version it shipped with (4.10) and turned on/off AMD Expo with no change to the green boot screen. I then reupdated to bios 4.43, reinstalled SteamOS, and still have the problem.
Once the kernel loads and you see the SteamOS loading animation all screen behavior is normal. I’ve tried both hdmi ports on my gpu and both produce the same effect. I’ll attach a screenshot after work.
Steps for reproducing this issue:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the reported SteamOS installation sequence and the Ryzen, Sapphire, and ASRock hardware details. Confirm whether the green tint is limited to the initial boot screen and UEFI menus, since the SteamOS loading animation is reported as normal. No repository file, test, or code entry point is identified, and the issue is complete when the cause and a reproducible fix or limitation are established.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100