All of lore.kernel.org
 help / color / mirror / Atom feed
From: PGNet Dev <pgnet.dev@gmail.com>
To: lijo.lazar@amd.com, alexdeucher@gmail.com
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: amdgpu "Fatal error during GPU init"; Ryzen 5600G integrated GPU + kernel 5.14.13
Date: Fri, 29 Oct 2021 21:07:27 -0400	[thread overview]
Message-ID: <2d9179a2-5d80-8609-58ac-64090941e5a2@gmail.com> (raw)
In-Reply-To: <8684c741-4604-440e-870b-5ee81bfc110c@gmail.com>

I got this comment from ASRockRack support re: the 'purple' screen:

"
Did you also get that background color in the BIOS menu? If not, it appears that this is the color may have something to do with video driver and it seems to be common with open source operating system. I came across these two forums with similar experience, there are some solution mentioned that might help you fix the driver issue.

https://forums.linuxmint.com/viewtopic.php?t=202548
https://askubuntu.com/questions/1219150/ubuntu-19-10-stuck-at-purple-screen-during-boot-using-kvm
"

Doesn't seem like either of those two are a specific fit.

But the point is that ASRockRack is suggesting it's the driver/config.

  reply	other threads:[~2021-10-30  1:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24 14:12 amdgpu "Fatal error during GPU init"; Ryzen 5600G integrated GPU + kernel 5.14.13 PGNet Dev
2021-10-25 13:48 ` PGNet Dev
2021-10-25 13:58   ` PGNet Dev
2021-10-25 14:15   ` Alex Deucher
2021-10-25 15:15     ` Lazar, Lijo
2021-10-25 16:32       ` PGNet Dev
2021-10-25 17:48         ` PGNet Dev
2021-10-26 17:02           ` PGNet Dev
2021-10-29 22:13       ` PGNet Dev
2021-10-29 22:34         ` PGNet Dev
2021-10-30  1:07           ` PGNet Dev [this message]
2021-10-30 15:24     ` amdgpu on Ryzen 5600G -- 'purple' background [WAS: Re: amdgpu "Fatal error during GPU init"; Ryzen 5600G integrated GPU + kernel 5.14.13} PGNet Dev
2021-11-02  9:37       ` PGNet Dev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2d9179a2-5d80-8609-58ac-64090941e5a2@gmail.com \
    --to=pgnet.dev@gmail.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=lijo.lazar@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.