Maybe the driver should have compilation flags per supported GPU. No need to load a bunch of that isn't even relevant. Also, now large in bytes is that damn think if it take 10 seconds to load? π«
PC Gaming
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
How you gonna know what GPU someone is booting to apply the correctly flag, I think that running simpleDRM at early boot and loading AMDGPU in the background is the best solution, that can also help debug the kernel, where you know the issue is in the kernel not in the AMDGPU drivers
Sounds like a long-awaited race condition finally coalescing.
The boot splash screen would expect the drivers to be ready, and will hang/timeout if it isn't ready when it tries to render the splash screen
Just don't use Plymouth and add the module to your initramfs. ez
"Recently there have been a number of reports about the plymouth boot splash not showing properly on PCs using AMD GPUs.
The problem without plymouth and AMD GPUs is that the amdgpu driver is a really really big driver, which easily takes up to 10 seconds to load on older PCs. The delay caused by this may cause plymouth to timeout while waiting for the GPU to be initialized, causing it to fallback to the 3 dot text-mode boot splash."