All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202667] amdgpu fails to boot: atombios stuck executing D6A0
Date: Mon, 25 Feb 2019 12:08:13 +0000	[thread overview]
Message-ID: <bug-202667-2300-dqBu8Jx87B@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202667-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202667

--- Comment #6 from Dennis Wagelaar (dwagelaar@gmail.com) ---
Created attachment 281339
  --> https://bugzilla.kernel.org/attachment.cgi?id=281339&action=edit
journalctl --no-hostname -k for kernel-4.20.8-100.fc28.x86_64 with amdgpu.dc=1

Just found out changing stuff in /etc/modprobe.d/ has no effect until the next
run of dracut :$

It turns out I can no longer use amdgpu without DC=1. With that enabled, the
newer kernel run as normal.

What probably happened is that I saw the flicker once, which is mentioned here:
https://wiki.archlinux.org/index.php/AMDGPU : "If you experience flickering add
amdgpu.dc=0 to your kernel parameters." That's when trouble began.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-02-25 12:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24 10:27 [Bug 202667] New: amdgpu fails to boot: atombios stuck executing D6A0 bugzilla-daemon
2019-02-25  9:18 ` [Bug 202667] " bugzilla-daemon
2019-02-25 11:20 ` bugzilla-daemon
2019-02-25 11:20 ` bugzilla-daemon
2019-02-25 11:31 ` bugzilla-daemon
2019-02-25 11:44 ` bugzilla-daemon
2019-02-25 12:08 ` bugzilla-daemon [this message]
2019-02-25 12:09 ` bugzilla-daemon

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=bug-202667-2300-dqBu8Jx87B@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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.