All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209159] AMD Vega 20 framebuffer switch fails on 5.9rc2+
Date: Sun, 06 Sep 2020 02:42:36 +0000	[thread overview]
Message-ID: <bug-209159-2300-F0cFa6jGUV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209159-2300@https.bugzilla.kernel.org/>

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

ryan@testtoast.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #4 from ryan@testtoast.com ---
Whoops seems this was PEBKAC, I'd previously overridden (and forgot about
overriding) my dracut.conf to load a specific firmware version and when that
fell off the bottom of the kernel rotation, obviously it didn't load into my
initrd and failed. Cleared that and all well, sorry for the noise.

-- 
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:[~2020-09-06  2:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05 10:19 [Bug 209159] New: AMD Vega 20 framebuffer switch fails on 5.9rc2+ bugzilla-daemon
2020-09-05 15:31 ` [Bug 209159] " bugzilla-daemon
2020-09-06  2:00 ` bugzilla-daemon
2020-09-06  2:01 ` bugzilla-daemon
2020-09-06  2:42 ` bugzilla-daemon [this message]

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-209159-2300-F0cFa6jGUV@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.